248 files changed, 140078 insertions, 0 deletions

diff --git a/doc/gettext/alsa-guide.xml.pot b/doc/gettext/alsa-guide.xml.pot
new file mode 100644
index 0000000..8805f55
--- /dev/null
+++ b/doc/gettext/alsa-guide.xml.pot
@@ -0,0 +1,703 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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>\n0000: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 "\nDevice 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>\nOpen Sound System   ---&gt;\n   &lt; &gt; Open Sound System (DEPRECATED)\n\n<comment>(Move one step back and enter ALSA)</comment>\nAdvanced 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,\nyou will have one type of device and not more. If you have more than one\nsound card, please enable them all here.)</comment>\n\n<comment>(Mostly for testing and development purposes, not needed for normal\nusers unless you know what you are doing.)</comment>\nGeneric devices  ---&gt;\n   \n<comment>(For ISA Sound cards)</comment>\nISA 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\nPCI devices)</comment>\nPCI 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>\nUSB 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>\nAdding 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>\nMPEG 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>\nAudio Device:   Advanced Linux Sound Architecture (ALSA) output\n\nPlaying: Paul Oakenfold - Dread Rock.ogg\nOgg Vorbis stream: 2 channel, 44100 Hz\nGenre: Soundtrack\nTranscoded: mp3;160\nTitle: Dread Rock\nArtist: Paul Oakenfold\nDate: 2003\nAlbum: Matrix Reloaded\nTime: 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\npicked up your sound card fine.)</comment>\n# <i>cat /proc/asound/cards</i>\n0 [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>\nAdvanced 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>\nSound Driver:3.8.1a-980706 (ALSA v1.0.8 emulation code)\nKernel: Linux airwolf.zion 2.6.11ac1 #2 Wed May 4 00:35:08 IST 2005 i686\nConfig options: 0\n\nInstalled drivers:\nType 10: ALSA emulation\n\nCard config:\nSound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11\n\nAudio devices:\n0: EMU10K1 (DUPLEX)\n\nSynth devices: NOT ENABLED IN CONFIG\n\nMidi devices:\n0: EMU10K1 MPU-401 (UART)\n\nTimers:\n7: system timer\n\nMixers:\n0: 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 ...\nWARNING: Error inserting snd_mixer_oss\n(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-mixer-oss.ko): Unknown\nsymbol in module, or unknown parameter (see dmesg) FATAL: Error inserting\nsnd_pcm_oss\n(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-pcm-oss.ko): Unknown\nsymbol in module, or unknown parameter (see dmesg)                             \n                                                                          [ !! ]\n *   Loading: snd-mixer-oss ...\nFATAL: Error inserting snd_mixer_oss\n(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-mixer-oss.ko): Unknown\nsymbol 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>\nACPI: PCI Interrupt 0000:02:06.0[A] -&gt; Link [APC3] -&gt; GSI 18 (level, low) -&gt; IRQ 209\nsnd_mixer_oss: Unknown symbol snd_unregister_oss_device\nsnd_mixer_oss: Unknown symbol snd_register_oss_device\nsnd_mixer_oss: Unknown symbol snd_mixer_oss_notify_callback\nsnd_mixer_oss: Unknown symbol snd_oss_info_register\nsnd_pcm_oss: Unknown symbol snd_unregister_oss_device\nsnd_pcm_oss: Unknown symbol snd_register_oss_device\nsnd_pcm_oss: Unknown symbol snd_mixer_oss_ioctl_card\nsnd_pcm_oss: Unknown symbol snd_oss_info_register\nsnd_mixer_oss: Unknown symbol snd_unregister_oss_device\nsnd_mixer_oss: Unknown symbol snd_register_oss_device\nsnd_mixer_oss: Unknown symbol snd_mixer_oss_notify_callback\nsnd_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>\nsnd: 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 "\noptions snd-emu10k1 index=0\noptions 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 "\noptions snd-ymfpci index=0\noptions 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/altinstall.xml.pot b/doc/gettext/altinstall.xml.pot
new file mode 100644
index 0000000..d82a4df
--- /dev/null
+++ b/doc/gettext/altinstall.xml.pot
@@ -0,0 +1,638 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):7
+msgid "The Gentoo Linux alternative installation method HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):9 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):12 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):15 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):18 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):21 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):24 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):27 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):30
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):10
+msgid "gerrynjr@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):10
+msgid "Gerald Normandin Jr."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):13
+msgid "lordviram@rebelpacket.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):13
+msgid "Travis Tilley"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):16
+msgid "volontir@yahoo.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):16
+msgid "Oleg Raisky"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):19
+msgid "luminousit@hotmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):19
+msgid "Alex Garbutt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):22
+msgid "alex@openvs.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):22
+msgid "Alexandre Georges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):25
+msgid "vargen@b0d.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):25
+msgid "Magnus Backanda"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):28
+msgid "davoid@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):28
+msgid "Faust A. Tanasescu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):31
+msgid "aliz@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):31
+msgid "Daniel Ahlberg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):33 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):39 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):42 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):45 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):48
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):34
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):34
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):36
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author):36
+msgid "Ken Nowack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):40
+msgid "blubber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):40
+msgid "Tiemo Kieft"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):43
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):43
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):46
+msgid "smithj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):46
+msgid "Jonathan Smith"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):49
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(abstract):52
+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):62
+msgid "6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(date):63
+msgid "2010-09-27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):66
+msgid "About this document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):70
+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):85
+msgid "Booting the Install CD with Smart BootManager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):89
+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):98
+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):104
+msgid "Smart BootManager Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):104
+#, no-wrap
+msgid "\nsbminst [-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):134
+msgid "Using sbminst to build the boot floppy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):134
+#, no-wrap
+msgid "\n# <i>sbminst -t us  -d /dev/fd0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(note):138
+msgid "Replace <path>fd0</path> with your respective floppy device name if yours is different."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):143
+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):149
+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):155
+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):165
+msgid "Installation from non-Gentoo LiveCDs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):167
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(impo):170
+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):178
+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):185
+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):194
+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):204
+msgid "Installation instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):207
+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):214
+msgid "Creating the /mnt/gentoo mountpoint"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):214
+#, no-wrap
+msgid "\n# <i>mkdir /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):218
+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):225
+msgid "Bind-mounting the proc pseudo filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):225
+#, no-wrap
+msgid "\n# <i>mount -o bind /proc /mnt/gentoo/proc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):229
+msgid "When you're ready to unpack the stage tarball in <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=5_sect4\">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):236
+msgid "Unpacking the stage tarball"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):236
+#, no-wrap
+msgid "\n# <i>tar --numeric-owner -xvjpf stage3-*.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):240
+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):247
+msgid "Chrooting into the new environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):247
+#, no-wrap
+msgid "\n<comment>(Some LiveCDs use a funny environment setup, hence the -i option for\ncleaning 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):256
+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):291
+msgid "Diskless install using PXE boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):293 ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):556
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):296
+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):305
+msgid "Server base setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):308
+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):315
+msgid "Directory setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):315
+#, 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):321
+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):326
+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):333
+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):340
+msgid "dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):340
+#, no-wrap
+msgid "\noption option-150 code 150 = text ;\nddns-update-style none ;\nhost eta {\nhardware ethernet 00:00:00:00:00:00;\nfixed-address <i>ip.add.re.ss</i>;\noption option-150 \"/eta/boot/grub.lst\";\nfilename \"/eta/boot/pxegrub\";\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):351
+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):357
+msgid "/etc/conf.d/net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):357
+#, no-wrap
+msgid "\n<comment>(Replace eth0 with the correct interface)</comment>\nconfig_eth0=( \"noop\" )\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):362
+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):367
+msgid "in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):367
+#, no-wrap
+msgid "\nINTFTPD_PATH=\"/diskless\"\nINTFTPD_USER=\"nobody\"\nINTFTPD_OPTS=\"-u ${INTFTPD_USER} -l -vvvvvv -p -c -s ${INTFTPD_PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):373
+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):379
+msgid "Grub setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):379
+#, 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):386
+msgid "grub.lst"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):386
+#, no-wrap
+msgid "\ndefault 0\ntimeout 30\n\ntitle=Diskless Gentoo\nroot (nd)\nkernel /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\nthe 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):398
+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):403
+msgid "/etc/exports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):403
+#, 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):409
+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):414
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):414
+#, no-wrap
+msgid "\n127.0.0.1 localhost\n\n192.168.1.10 eta.example.com eta\n192.168.1.20 sigma.example.com sigma\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):424
+msgid "Creating the system on the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):427
+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):439
+msgid "Mounting the filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):439
+#, no-wrap
+msgid "\n#<i> mount /dev/hdaX /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):443
+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):450
+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):455
+msgid "Extracting the stage tarball"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):455
+#, 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):465
+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):471
+msgid "menuconfig options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):471
+#, 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):490
+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):496
+msgid "/etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):496
+#, no-wrap
+msgid "\n# <i>nano -w /etc/fstab</i>\n/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0\nproc /proc proc defaults 0 0\ntmpfs /dev/shm tmpfs nodev,nosuid,noexec 0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):503
+msgid "You also need to prevent the client to run a filesystem check:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):507
+msgid "Preventing the client to run a filesystem check"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):507
+#, 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):512
+msgid "Install <c>nfs-utils</c> since your client will heavily depend on it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):516
+msgid "Installing nfs-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):516
+#, no-wrap
+msgid "\n# <i>emerge nfs-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):520
+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):526
+msgid "Starting services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):526
+#, 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):535
+msgid "Booting the new client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):538
+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):554
+msgid "Installing Gentoo from an existing Linux distribution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):559
+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):571
+msgid "Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):574
+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):585
+msgid "How should we make space for Gentoo?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):588
+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):597
+msgid "Filesystem information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):597
+#, no-wrap
+msgid "\n# <i>mount</i>\n/dev/hdb2 on / type ext3 (rw)\nnone on /proc type proc (rw)\nnone on /dev/pts type devpts (rw,gid=5,mode=620)\nnone on /dev/shm type tmpfs (rw,nodev,nosuid,noexec)\n# <i>df -h </i>\nFilesystem           Size Used Avail Use% Mounted on\n/dev/hdb2            4.0G 1.9G  2.4G  82% /\nnone                  38M    0   38M   0% /dev/shm\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):609
+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):620
+msgid "Building parted to resize partition"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):623
+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):631
+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):637
+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):650
+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):655
+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):662
+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):670
+msgid "Utility disk creation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):670
+#, no-wrap
+msgid "\n# <i>mkfs.minix /dev/fd0</i>\n480 inodes\n1440 blocks\nFirstdatazone=19 (19)\nZonesize=1024\nMaxsize=268966912\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):679
+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):686
+msgid "Building the utility floppy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):686
+#, no-wrap
+msgid "\n# <i> mkdir /floppy; mount -t minix /dev/fd0 /floppy &amp;&amp;\nexport 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):692
+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):706
+msgid "Commands to run once logged into mininux system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):706
+#, 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>\nDisk geometry for /dev/hdb: 0.000-9787.148 megabytes\nDisk label type: msdos\nMinor    Start       End     Type      Filesystem  Flags\n1          0.031   2953.125  primary   ntfs\n3       2953.125   3133.265  primary   linux-swap\n2       3133.266   5633.085  primary   ext3\n4       5633.086   9787.148  extended\n5       5633.117   6633.210  logical\n6       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):729
+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):734
+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):741
+msgid "Flushing the environment during chroot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):741
+#, 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):747
+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/anothertest.xml.pot b/doc/gettext/anothertest.xml.pot
new file mode 100644
index 0000000..dfdff48
--- /dev/null
+++ b/doc/gettext/anothertest.xml.pot
@@ -0,0 +1,68 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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/apache-troubleshooting.xml.pot b/doc/gettext/apache-troubleshooting.xml.pot
new file mode 100644
index 0000000..9ae709c
--- /dev/null
+++ b/doc/gettext/apache-troubleshooting.xml.pot
@@ -0,0 +1,52 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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/apache-upgrading.xml.pot b/doc/gettext/apache-upgrading.xml.pot
new file mode 100644
index 0000000..26b80fd
--- /dev/null
+++ b/doc/gettext/apache-upgrading.xml.pot
@@ -0,0 +1,52 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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/arm-requirements.xml.pot b/doc/gettext/arm-requirements.xml.pot
new file mode 100644
index 0000000..03f91a5
--- /dev/null
+++ b/doc/gettext/arm-requirements.xml.pot
@@ -0,0 +1,104 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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/ati-faq.xml.pot b/doc/gettext/ati-faq.xml.pot
new file mode 100644
index 0000000..26ef473
--- /dev/null
+++ b/doc/gettext/ati-faq.xml.pot
@@ -0,0 +1,290 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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/bind-guide.xml.pot b/doc/gettext/bind-guide.xml.pot
new file mode 100644
index 0000000..e968550
--- /dev/null
+++ b/doc/gettext/bind-guide.xml.pot
@@ -0,0 +1,377 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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 "\noptions {\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 "\nview \"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 "\nview \"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 "\nlogging {\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\nYOUR_DOMAIN.\t\tIN MX\t0 mail.YOUR_DOMAIN.\nYOUR_DOMAIN.\t\tIN TXT\t\"v=spf1 ip4:YOUR_PUBLIC_IP/32 mx ptr mx:mail.YOUR_DOMAIN ~all\"\nYOUR_DOMAIN.\t\tIN NS\tns.YOUR_DOMAIN.\nYOUR_DOMAIN.\t\tIN NS\tSLAVE_DNS_SERVER\nwww.YOUR_DOMAIN.\tIN A\t192.168.1.3\nns.YOUR_DOMAIN.\t\tIN A\t192.168.1.5\nmail.YOUR_DOMAIN.\tIN A\t192.168.1.3\nrouter.YOUR_DOMAIN.\tIN A\t192.168.1.1\nhell.YOUR_DOMAIN.\tIN A\t192.168.1.3\nheaven.YOUR_DOMAIN.\tIN A\t192.168.1.5\ndesktop.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\nYOUR_DOMAIN.\t\tIN MX\t0 mail.YOUR_DOMAIN.\nYOUR_DOMAIN.\t\tIN TXT\t\"v=spf1 ip4:YOUR_PUBLIC_IP/32 mx ptr mx:mail.YOUR_DOMAIN ~all\"\nYOUR_DOMAIN.\t\tIN NS\tns.YOUR_DOMAIN.\nYOUR_DOMAIN.\t\tIN NS\tSLAVE_DNS_SERVER\nwww.YOUR_DOMAIN.\tIN A\tYOUR_PUBLIC_IP\nns.YOUR_DOMAIN.\t\tIN A\tYOUR_PUBLIC_IP\nmail.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 "\nsearch YOUR_DOMAIN\nnameserver 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>\nwww.gentoo.org has address 209.177.148.228\nwww.gentoo.org has address 209.177.148.229\n\n$ <i>host hell</i>\nhell.YOUR_DOMAIN has address 192.168.1.3\n\n$ <i>host router</i>\nrouter.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 "\niptables -A INPUT -p udp --sport 53 -m state --state ESTABLISHED,RELATED -j ACCEPT\niptables -A INPUT -p udp --dport 53 -j ACCEPT\niptables -A INPUT -p tcp --sport 53 -j ACCEPT\niptables -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/bluetooth-guide.xml.pot b/doc/gettext/bluetooth-guide.xml.pot
new file mode 100644
index 0000000..569aa0d
--- /dev/null
+++ b/doc/gettext/bluetooth-guide.xml.pot
@@ -0,0 +1,523 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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 "\nNetworking ---&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\nBluetooth 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\nshow 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\nenabled. This is required if you use a Bluetooth dongle, which are mostly USB\nbased.)</comment>\nUSB 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>\nT:  Bus=02 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#=  4 Spd=12  MxCh= 0\nD:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1\nP:  Vendor=0a12 ProdID=0001 Rev= 5.25\n<comment>(Some might show up on lsusb from sys-apps/usbutils)</comment>\n# <i>lsusb</i>\nBus 003 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse\nBus 003 Device 001: ID 0000:0000\nBus 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>\nhci0:   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\noptions {\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\ndevice {\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>\n123456\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>\n26050 ?        00:00:00 hcid\n# <i>ps -ae | grep sdpd</i>\n26054 ?        00:00:00 sdpd\n\n# <i>hciconfig -a</i>\nhci0:   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>\nDevices:\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>\nScanning ...\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>\nInquiring ...\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>\nPing: 00:0A:0B:0C:0D:0E from 00:01:02:03:04:05 (data size 20) ...\n20 bytes from 00:0A:0B:0C:0D:0E id 200 time 69.85ms\n20 bytes from 00:0A:0B:0C:0D:0E id 201 time 9.97ms\n20 bytes from 00:0A:0B:0C:0D:0E id 202 time 56.86ms\n20 bytes from 00:0A:0B:0C:0D:0E id 203 time 39.92ms\n4 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>\nrfcomm0 {\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>\nConnected /dev/rfcomm0 to 00:0A:0B:0C:0D:0E on channel 1\nPress 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>\nConnected /dev/rfcomm0 to 00:0F:DE:69:50:24 on channel 1\nPress 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>\nWaiting 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>\nWaiting 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/bugzilla-howto.xml.pot b/doc/gettext/bugzilla-howto.xml.pot
new file mode 100644
index 0000000..5d3dc44
--- /dev/null
+++ b/doc/gettext/bugzilla-howto.xml.pot
@@ -0,0 +1,1240 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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>\nSegmentation 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:\nwarning: #warning This file includes at least one deprecated or antiquated\nheader. Please consider using one of the 32 headers found in section 17.4.1.2 of\nthe C++ standard. Examples include substituting the &lt;X&gt; header for the &lt;X.h&gt;\nheader for C++ includes, or &lt;sstream&gt; instead of the deprecated header\n&lt;strstream.h&gt;. To disable this warning use -Wno-deprecated.\nIn file included from main.cc:40:\nmenudef.h:55: error: brace-enclosed initializer used to initialize `\nOXPopupMenu*'\nmenudef.h:62: error: brace-enclosed initializer used to initialize `\nOXPopupMenu*'\nmenudef.h:70: error: brace-enclosed initializer used to initialize `\nOXPopupMenu*'\nmenudef.h:78: error: brace-enclosed initializer used to initialize `\nOXPopupMenu*'\nmain.cc: In member function `void OXMain::DoOpen()':\nmain.cc:323: warning: unused variable `FILE*fp'\nmain.cc: In member function `void OXMain::DoSave(char*)':\nmain.cc:337: warning: unused variable `FILE*fp'\nmake[1]: *** [main.o] Error 1\nmake[1]: Leaving directory\n`/var/tmp/portage/xclass-0.7.4/work/xclass-0.7.4/example-app'\nmake: *** [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 "\nCFLAGS=\"-O1 -pipe -ggdb\"\nCXXFLAGS=\"${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>\nGNU gdb 6.3\nCopyright 2004 Free Software Foundation, Inc.\nGDB is free software, covered by the GNU General Public License, and you are\nwelcome to change it and/or distribute copies of it under certain conditions.\nType \"show copying\" to see the conditions.\nThere is absolutely no warranty for GDB. Type \"show warranty\" for details.\nThis 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>\nStarting program: /home/chris/bad_code\n\nProgram received signal SIGSEGV, Segmentation fault.\n0xb7ec6dc0 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>\nThe 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>\nConfiguration 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 "\nopen(\".foobar2/config\", O_RDONLY)       = 3\nread(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 "\ngcc -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\ngcc -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\ngcc -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\ngcc -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\nfoobar2.c:1:17: ogg.h: No such file or directory\nmake: *** [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>\ngcc -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\ngcc -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\ngcc -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\ngcc -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>\nfoobar2.c:1:17: ogg.h: No such file or directory\nmake: *** [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>\ntotal 16\ndrwxrws---   2 root root 4096 Jun 30 10:08 .\ndrwxr-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 "\nmenudef.h:78: error: brace-enclosed initializer used to initialize `OXPopupMenu'\n<comment>(Remove the quotes ' ')</comment>\nmenudef.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;\nFoobar2 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 "\nconfigure: 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 "\nPORTDIR_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\nThese are the packages that I would merge, in order:\n\nCalculating dependencies ...done!\n[ebuild  N    ] sys-apps/foobar2-1.0  0 kB [1]\n\nTotal size of downloads: 0 kB\nPortage 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/change-chost.xml.pot b/doc/gettext/change-chost.xml.pot
new file mode 100644
index 0000000..f4968f5
--- /dev/null
+++ b/doc/gettext/change-chost.xml.pot
@@ -0,0 +1,347 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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>\ni686-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>\ni686-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>\n05gcc-i386-pc-linux-gnu:PATH=\"/usr/i386-pc-linux-gnu/gcc-bin/4.1.1\"\n05gcc-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>\n05binutils:MANPATH=/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/man\n05binutils:INFOPATH=/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/info\n05binutils:LDPATH=/usr/i686-pc-linux-gnu/lib\n05gcc:PATH=\"/usr/i686-pc-linux-gnu/gcc-bin/4.1.1\"\n05gcc:ROOTPATH=\"/usr/i686-pc-linux-gnu/gcc-bin/4.1.1\"\n05gcc:MANPATH=\"/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man\"\n05gcc:INFOPATH=\"/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info\"\n05gcc: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>\ntotal 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>\nCURRENT=2.16.1\n# <i>cat i686-pc-linux-gnu-2.16.1</i>\nTARGET=\"i686-pc-linux-gnu\"\nVER=\"2.16.1\"\nLIBPATH=\"/usr/lib/binutils/i686-pc-linux-gnu/2.16.1\"\nFAKE_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>\ntotal 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>\nCURRENT=i686-pc-linux-gnu-4.1.1\n\n# <i>cat config-i386-pc-linux-gnu</i>\nCURRENT=i386-pc-linux-gnu-4.1.1\n\n# <i>cat i686-pc-linux-gnu-4.1.1</i>\nPATH=\"/usr/i686-pc-linux-gnu/gcc-bin/4.1.1\"\nROOTPATH=\"/usr/i686-pc-linux-gnu/gcc-bin/4.1.1\"\nLDPATH=\"/usr/lib/gcc/i686-pc-linux-gnu/4.1.1\"\nGCCBITS=\"32\"\nMANPATH=\"/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man\"\nINFOPATH=\"/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info\"\nSTDCXX_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 "\nerror 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/conky-howto.xml.pot b/doc/gettext/conky-howto.xml.pot
new file mode 100644
index 0000000..e8c3813
--- /dev/null
+++ b/doc/gettext/conky-howto.xml.pot
@@ -0,0 +1,188 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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/cron-guide.xml.pot b/doc/gettext/cron-guide.xml.pot
new file mode 100644
index 0000000..39cf7ca
--- /dev/null
+++ b/doc/gettext/cron-guide.xml.pot
@@ -0,0 +1,649 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(guide:link):5
+msgid "/doc/en/cron-guide.xml"
+msgstr ""
+
+#: ../../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 "1.9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(date):27
+msgid "2008-01-26"
+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 "\nall\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 "\nwepy\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>\n35    1     4     *     mon-wed  /bin/false\n\n<comment># Run /bin/true at 22:25 on the 2nd of March</comment>\n25    22    2     3     *        /bin/true\n\n<comment># Run /bin/false at 2:00 every Monday, Wednesday and Friday</comment>\n0     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>\n10     3      1      1       *       /bin/echo \"I don't really like cron\"\n30     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 "\n5 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>slocate</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 "\n22 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 "\n22 2 * * 1    /usr/bin/updatedb\n30 6 * * *    /usr/bin/emerge --sync\n<comment>(if you're using anacron, add this line)</comment>\n30 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\n0  *  * * *      rm -f /var/spool/cron/lastrun/cron.hourly\n0  3  * * *      rm -f /var/spool/cron/lastrun/cron.daily\n15 4  * * 6      rm -f /var/spool/cron/lastrun/cron.weekly\n30 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/cross-compiling-distcc.xml.pot b/doc/gettext/cross-compiling-distcc.xml.pot
new file mode 100644
index 0000000..9feca75
--- /dev/null
+++ b/doc/gettext/cross-compiling-distcc.xml.pot
@@ -0,0 +1,181 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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>\ntotal 0\nlrwxrwxrwx  1 root root 15 Dec 23 20:13 c++ -&gt; /usr/bin/distcc\nlrwxrwxrwx  1 root root 15 Dec 23 20:13 cc -&gt; /usr/bin/distcc\nlrwxrwxrwx  1 root root 15 Dec 23 20:13 g++ -&gt; /usr/bin/distcc\nlrwxrwxrwx  1 root root 15 Dec 23 20:13 gcc -&gt; /usr/bin/distcc\nlrwxrwxrwx  1 root root 15 Dec 23 20:13 sparc-unknown-linux-gnu-c++ -&gt; /usr/bin/distcc\nlrwxrwxrwx  1 root root 15 Dec 23 20:13 sparc-unknown-linux-gnu-g++ -&gt; /usr/bin/distcc\nlrwxrwxrwx  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\nexec /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>\ntotal 4\nlrwxrwxrwx  1 root root 25 Jan 18 14:20 c++ -&gt; sparc-unknown-linux-gnu-wrapper\nlrwxrwxrwx  1 root root 25 Jan 18 14:20 cc -&gt; sparc-unknown-linux-gnu-wrapper\nlrwxrwxrwx  1 root root 25 Jan 18 14:20 g++ -&gt; sparc-unknown-linux-gnu-wrapper\nlrwxrwxrwx  1 root root 25 Jan 18 14:20 gcc -&gt; sparc-unknown-linux-gnu-wrapper\nlrwxrwxrwx  1 root root 15 Nov 21 10:42 sparc-unknown-linux-gnu-c++ -&gt; /usr/bin/distcc\nlrwxrwxrwx  1 root root 15 Nov 21 10:42 sparc-unknown-linux-gnu-g++ -&gt; /usr/bin/distcc\nlrwxrwxrwx  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/cvs-tutorial.xml.pot b/doc/gettext/cvs-tutorial.xml.pot
new file mode 100644
index 0000000..be06d83
--- /dev/null
+++ b/doc/gettext/cvs-tutorial.xml.pot
@@ -0,0 +1,792 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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 "\nCVSROOT=/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 "\nCVSROOT=: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 "\nCVSROOT=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)\nCVS password: <comment>(enter password here)</comment>\n\n# <i>cvs -z5 co samba</i>\nU samba/COPYING\nU samba/Manifest\nU samba/README\nU samba/Read-Manifest-Now\nU samba/Roadmap\nU 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 "\nexport 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 "\ncvs -q\ndiff -u -b -B\ncheckout -P\nupdate -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>\ncvs 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>\nDirectory /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>\ncvs add: cannot open CVS/Entries for reading: No such file or directory\ncvs [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 "\nU [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 "\nA [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 "\nR [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 "\nM [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 "\nC [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 "\ndate 25 Feb 2001\n\nThis 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 "\ndate 25 Feb 2001\n\nThis 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 "\nRCS file: /var/cvsroot/gentoo-x86/ChangeLog,v\nretrieving revision 1.362\nretrieving revision 1.363\nMerging differences between 1.362 and 1.363 into ChangeLog\nrcsmerge: warning: conflicts during merge\ncvs server: conflicts found in ChangeLog\nC 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\ndate 25 Feb 2001\n\nThis is the thing I added myself\n\n=======\ndate 25 Feb 2001\n\nThis 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 "\ndate 25 Feb 2001\n\nThis is the thing I added myself\n\nThis 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/desktop.xml.pot b/doc/gettext/desktop.xml.pot
new file mode 100644
index 0000000..ac93b8a
--- /dev/null
+++ b/doc/gettext/desktop.xml.pot
@@ -0,0 +1,60 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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/devfs-guide.xml.pot b/doc/gettext/devfs-guide.xml.pot
new file mode 100644
index 0000000..31e3294
--- /dev/null
+++ b/doc/gettext/devfs-guide.xml.pot
@@ -0,0 +1,397 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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>\nbrw-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 "\ncdroms/     cpu/        discs/          floppy/\nide/        input/      loop/           misc/\nnetlink/    printers/   pts/            pty/\nscsi/       sg/         shm/            sound/\nsr/         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>\nlr-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>\nREGISTER        .*  MKOLDCOMPAT\nUNREGISTER      .*  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 "\nLOOKUP      .*  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 "\nREGISTER    ^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 "\nREGISTER        ^pt[sy]/.*   IGNORE\nCHANGE          ^pt[sy]/.*   IGNORE\nCREATE          ^pt[sy]/.*   IGNORE\nDELETE          ^pt[sy]      IGNORE\nREGISTER        ^log         IGNORE\nCHANGE          ^log         IGNORE\nCREATE          ^log         IGNORE\nDELETE          ^log         IGNORE\nREGISTER        .*           COPY    /lib/dev-state/$devname $devpath\nCHANGE          .*           COPY    $devpath /lib/dev-state/$devname\nCREATE          .*           COPY    $devpath /lib/dev-state/$devname\nDELETE          .*           CFUNCTION GLOBAL unlink\n/lib/dev-state/$devname\nRESTORE         /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 "\nmount --bind /dev /lib/dev-state\nmount -t devfs none /dev\ndevfsd /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/diskless-howto.xml.pot b/doc/gettext/diskless-howto.xml.pot
new file mode 100644
index 0000000..8720c0f
--- /dev/null
+++ b/doc/gettext/diskless-howto.xml.pot
@@ -0,0 +1,1048 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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 "\nCode maturity level options  ---&gt;\n  [*] Prompt for development and/or incomplete code/drivers\n\nDevice 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\nFile systems ---&gt;\n  Network File Systems  ---&gt;\n    &lt;*&gt; NFS server support\n    [*]   Provide NFSv3 server support\n\n<comment>\nIf you want to access the internet through your master node and/or have a\nsecure 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 "\nCode maturity level options  ---&gt;\n  [*] Prompt for development and/or incomplete code/drivers\n\nDevice 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\nFile 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 "\neth0      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>\nddns-update-style none;\nshared-network LOCAL-NET {\n<comment># shared network options here</comment>\nsubnet 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\nddns-update-style none;\n\n# Assume one default gateway for IP traffic will do\noption routers 192.168.1.1;\n\n# Provide DNS info to clients\noption domain-name-servers 192.168.1.1;\noption domain-name \"mydomain.com\";\n\n# Specify the TFTP server to be used\nnext-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\noption space PXE;\noption PXE.mtftp-ip               code 1 = ip-address;\noption PXE.mtftp-cport            code 2 = unsigned integer 16;\noption PXE.mtftp-sport            code 3 = unsigned integer 16;\noption PXE.mtftp-tmout            code 4 = unsigned integer 8;\noption PXE.mtftp-delay            code 5 = unsigned integer 8;\noption PXE.discovery-control      code 6 = unsigned integer 8;\noption PXE.discovery-mcast-addr   code 7 = ip-address;\n\n# Declare the subnet where our diskless nodes will live\nsubnet 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 "\nIFACE=\"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 "\nDHCPDISCOVER from 00:00:00:00:00:00 via eth0\nDHCPOFFER on 192.168.1.21 to 00:00:00:00:00:00 via eth0\nDHCPREQUEST for 192.168.1.21 from 00:00:00:00:00:00 via eth0\nDHCPACK 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 "\nno 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 "\nINTFTPD_PATH=\"/diskless\"\nINTFTPD_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>\n01-00-40-63-c2-ca-c9\n\n<comment>(Assigned IP in hexadecimal)</comment>\nC0A80115\nC0A8011\nC0A801\nC0A80\nC0A8\nC0A\nC0\nC\n\ndefault\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 "\nDEFAULT /bzImage\nAPPEND 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 "\nCONFIG_PACKET=y\n# CONFIG_PACKET_MMAP is not set\n# CONFIG_NETFILTER is not set\nCONFIG_NFS_FS=y\nCONFIG_NFS_V3=y\n# CONFIG_NFS_V4 is not set\n# CONFIG_NFS_DIRECTIO is not set\nCONFIG_NFSD=y\nCONFIG_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>\nmaster:/diskless/192.168.1.21   /         nfs     sync,hard,intr,rw,nolock,rsize=8192,wsize=8192    0 0\nmaster:/opt                     /opt      nfs     sync,hard,intr,ro,nolock,rsize=8192,wsize=8192    0 0\nmaster:/usr                     /usr      nfs     sync,hard,intr,ro,nolock,rsize=8192,wsize=8192    0 0\nmaster:/home                    /home     nfs     sync,hard,intr,rw,nolock,rsize=8192,wsize=8192    0 0\nnone                            /proc     proc    defaults                                     0 0\n<comment># useful but superfluous</comment>\nmaster:/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\nRPCNFSDCOUNT=8\n\n# Options to pass to rpc.mountd\nRPCMOUNTDOPTS=\"\"\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>\nconfig_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/:\ntotal 16\ndrwxr-xr-x    2 root     root         4096 2003-11-09 15:27 boot\ndrwxr-xr-x    2 root     root         4096 2003-10-01 21:10 default\ndrwxr-xr-x    2 root     root         4096 2003-03-13 19:05 nonetwork\ndrwxr-xr-x    2 root     root         4096 2003-02-23 12:26 single\n\n/diskless/192.168.1.21/etc/runlevels/boot:\ntotal 0\nlrwxrwxrwx    1 root     root           20 2003-10-18 17:28 bootmisc -&gt; /etc/init.d/bootmisc\nlrwxrwxrwx    1 root     root           19 2003-10-18 17:28 checkfs -&gt; /etc/init.d/checkfs\nlrwxrwxrwx    1 root     root           17 2003-10-18 17:28 clock -&gt; /etc/init.d/clock\nlrwxrwxrwx    1 root     root           22 2003-10-18 17:28 domainname -&gt; /etc/init.d/domainname\nlrwxrwxrwx    1 root     root           20 2003-10-18 17:28 hostname -&gt; /etc/init.d/hostname\nlrwxrwxrwx    1 root     root           22 2003-10-18 17:28 localmount -&gt; /etc/init.d/localmount\nlrwxrwxrwx    1 root     root           19 2003-10-18 17:28 modules -&gt; /etc/init.d/modules\nlrwxrwxrwx    1 root     root           18 2003-10-18 17:28 net.lo -&gt; /etc/init.d/net.lo\nlrwxrwxrwx    1 root     root           20 2003-10-18 17:28 netmount -&gt; /etc/init.d/netmount\nlrwxrwxrwx    1 root     root           21 2003-10-18 17:28 rmnologin -&gt; /etc/init.d/rmnologin\nlrwxrwxrwx    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:\ntotal 0\nlrwxrwxrwx    1 root     root           23 2003-10-18 17:28 consolefont -&gt; /etc/init.d/consolefont\nlrwxrwxrwx    1 root     root           19 2003-10-18 17:28 distccd -&gt; /etc/init.d/distccd\nlrwxrwxrwx    1 root     root           19 2003-10-18 17:28 keymaps -&gt; /etc/init.d/keymaps\nlrwxrwxrwx    1 root     root           17 2003-10-18 17:28 local -&gt; /etc/init.d/local\nlrwxrwxrwx    1 root     root           16 2003-10-18 17:28 sshd -&gt; /etc/init.d/sshd\nlrwxrwxrwx    1 root     root           21 2003-10-18 17:28 syslog-ng -&gt; /etc/init.d/syslog-ng\nlrwxrwxrwx    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:\ntotal 0\nlrwxrwxrwx    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:\ntotal 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/distcc.xml.pot b/doc/gettext/distcc.xml.pot
new file mode 100644
index 0000000..05f4590
--- /dev/null
+++ b/doc/gettext/distcc.xml.pot
@@ -0,0 +1,401 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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>\nMAKEOPTS=\"-jN\"\n<comment>(Add distcc to your FEATURES)</comment>\nFEATURES=\"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 "\n192.168.0.1          192.168.0.2                       192.168.0.3\n192.168.0.1/2        192.168.0.2                       192.168.0.3/10\n192.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 \ndistcc manpage for more details.)</comment>\n<comment>If you wish to compile on the local machine you should put 'localhost'\nin the hosts list.  Conversely if you do not wish to use the local machine to\ncompile (which is often the case) omit it from the hosts list.  On a slow\nmachine using localhost may actually slow things down. Make sure to test your\nsettings 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\nset 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>\nFEATURES=\"distcc\"\n<comment>(Modify MAKEOPTS to include -jN, where N is twice the number of CPUs\n+1 available)</comment>\nMAKEOPTS=\"-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\nparticipating 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\n192.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/doc-languages.xml.pot b/doc/gettext/doc-languages.xml.pot
new file mode 100644
index 0000000..7dcedbf
--- /dev/null
+++ b/doc/gettext/doc-languages.xml.pot
@@ -0,0 +1,36 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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/dri-howto.xml.pot b/doc/gettext/dri-howto.xml.pot
new file mode 100644
index 0000000..b055976
--- /dev/null
+++ b/doc/gettext/dri-howto.xml.pot
@@ -0,0 +1,360 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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>\nlrwxrwxrwx 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 "\nProcessor type and features ---&gt;\n&lt;*&gt; MTRR (Memory Type Range Register) support\nDevice 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...\nSection \"Module\"\n  Load \"dri\"\n  Load \"glx\"\n  ...\nEndSection\n...\nSection \"Device\"\n  Driver \"radeon\"\n  <comment>(Replace radeon with the name of your driver.)</comment>\n  ...\nEndSection\n...\nSection \"dri\"\n  Mode 0666\nEndSection\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>\nintel-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>\ndirect 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\nsignificantly higher than before configuring DRM. Do this while the CPU is as idle as\npossible.)</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 "\nOption \"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/ebuild-submit.xml.pot b/doc/gettext/ebuild-submit.xml.pot
new file mode 100644
index 0000000..90fb9fc
--- /dev/null
+++ b/doc/gettext/ebuild-submit.xml.pot
@@ -0,0 +1,177 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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 "\nHi!\n\nPlease find attached gramps-0.7.0.ebuild and a patch so that it will\ncompile against python-2.2\n\ngramps is the Genealogical Research and Analysis Management Programming\nSystem.  It is a very cool gnome/python app.  If you are in the US, you\ncan head over to http://www.familysearch.com/ and you can probably find a\nGEDCOM file for your family tree to import into gramps. (Mormons sure do like\ngeneaology)\n\nI suggest app-misc/gramps Also, this ebuild depend on Imaging and ReportLab\npreviously submitted\n\ntod\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/faq.xml.pot b/doc/gettext/faq.xml.pot
new file mode 100644
index 0000000..3a8350c
--- /dev/null
+++ b/doc/gettext/faq.xml.pot
@@ -0,0 +1,666 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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 "\nhttp_proxy=\"http://username:password@yourproxybox.org:portnumber\"\nftp_proxy=\"ftp://username:password@yourproxybox.org:portnumber\"\nRSYNC_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 "\ntitle 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 "\nother=/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/fluxbox-config.xml.pot b/doc/gettext/fluxbox-config.xml.pot
new file mode 100644
index 0000000..fe5f6da
--- /dev/null
+++ b/doc/gettext/fluxbox-config.xml.pot
@@ -0,0 +1,546 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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 "\nDISPLAYMANAGER=\"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>\nMod4 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>\nMod1 f   :ExecCommand firefox\nMod1 t   :ExecCommand thunderbird\nMod1 o   :ExecCommand oowriter\nMod1 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>\nMod1 e   :ExecCommand Eterm -name alsa -e alsamixer\n\n<comment># This launches fbrun, which in turn launches other programs</comment>\nMod1 r   :ExecCommand fbrun\n\n<comment># Program Control. It just makes life simpler...</comment>\nMod1 4   :Close\nMod1 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>\nMod1 a   :ExecCommand aterm -name aterm -sl 3000 -tr +sb -sr -sk -bg black -fg \\\nwhite -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>\nMod1 s   :ExecCommand aterm -name aterm -sl 3000 -tr +sb -sr -sk -bg black -fg \\\nwhite -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>\nexec /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/gcc-optimization.xml.pot b/doc/gettext/gcc-optimization.xml.pot
new file mode 100644
index 0000000..0f355f9
--- /dev/null
+++ b/doc/gettext/gcc-optimization.xml.pot
@@ -0,0 +1,422 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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 "\nCFLAGS=\"-march=athlon64 -O2 -pipe\"\nCXXFLAGS=\"${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 "\nCFLAGS=\"-march=pentium3\"\nCXXFLAGS=\"${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 "\nCFLAGS=\"-march=athlon64\"\nCXXFLAGS=\"${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 "\nif (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 "\nCFLAGS=\"-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/gcc-upgrading.xml.pot b/doc/gettext/gcc-upgrading.xml.pot
new file mode 100644
index 0000000..eb77c65
--- /dev/null
+++ b/doc/gettext/gcc-upgrading.xml.pot
@@ -0,0 +1,379 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\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\nversion 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\nexample) 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\nversion 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\nversion 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\nexample) 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\nversion 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/genkernel.xml.pot b/doc/gettext/genkernel.xml.pot
new file mode 100644
index 0000000..e8fd47f
--- /dev/null
+++ b/doc/gettext/genkernel.xml.pot
@@ -0,0 +1,625 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(guide:link):5
+msgid "/doc/en/genkernel.xml"
+msgstr ""
+
+#: ../../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 ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author:title):12
+msgid "Contributor"
+msgstr ""
+
+#. folajimi@speakeasy.net
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author):12
+msgid "Jimi Ayodele"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author:title):16
+msgid "NFS Support"
+msgstr ""
+
+#. thseiler@gmail.com
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author):16
+msgid "Thomas Seiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author:title):19
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(mail:link):20
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(abstract):23
+msgid "This guide intends to provide a reference of all the functions provided by genkernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(version):30
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(date):31
+msgid "2008-06-22"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):34
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):36
+msgid "Rationale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):39
+msgid "For users who are not privy to kernel compilation, genkernel is a tool to automate this process. It can help you create a kernel image akin to those available on Gentoo Installation CDs, which are designed to auto-detect the hardware configuration of your system. Some users may also be interested in using genkernel for hardware requiring initialization and a working kernel before the system starts up. Since genkernel automatically compiles your kernel modules, you can use hardware that may require certain module parameters to be loaded for proper operation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):53
+msgid "Target Audience"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):56
+msgid "If you are either uncertain about how to compile a kernel, or are just unfamiliar with your hardware configuration, genkernel is a very handy tool. It is designed to take the pain out of the kernel compiling process, and supports most hardware by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):63
+msgid "However, if you know what drivers are required by your system, you may be able to further reduce the time taken to compile the kernel. This is possible since you can direct genkernel to only build drivers relevant to your hardware. Oftentimes, the number of drivers required by your system will be fewer (implying a shorter kernel compilation time) than the default configuration provides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):75
+msgid "Installing genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):78
+msgid "To obtain genkernel, run <c>emerge genkernel</c> from the command line. If you are using the <uri link=\"/doc/en/handbook/2005.1/hb-install-about.xml#doc_chap2_sect1\">Gentoo Reference Platform</uri> (GRP), remember to install binary packages by passing the <c>-k</c> flag to emerge. Since the GRP is bundled with an older version of genkernel, the flags may be different. In any case, consult <c>genkernel --help</c> for help on how to use the version of genkernel installed on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):94
+msgid "Working with genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):96
+msgid "How to use genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):99
+msgid "Although there are several ways to run genkernel, the least-intrusive approach is provided by <c>genkernel all</c>. Here, a generic configuration which works well for most systems is used. As was mentioned earlier, this approach is not without drawbacks; most of the modules created are useless to the average user and may increase compile time. Below is an illustration of a more efficient approach, achieved by passing certain flags to genkernel as root:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):108
+msgid "Running genkernel (with flags)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):108
+#, no-wrap
+msgid "\n# <i>genkernel --splash --no-install --no-clean --menuconfig all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):112
+msgid "The above operation causes genkernel to create a framebuffer splash-enabled kernel (<c>--splash</c>) that will have to be manually installed (<c>--no-install</c>). While preparing the kernel source tree, genkernel will refrain from cleaning out any preexisting object files present in the source tree (<c>--no-clean</c>). A menu-driven kernel configuration utility will be displayed that allows the user to select which modules will be built for the system (<c>--menuconfig</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):122
+msgid "There are other flags which alter the result provided by genkernel. For instance, replacing <c>--no install</c> with the <c>--install</c> flag allows genkernel to automatically install the new kernel in the <path>/boot</path> directory. Using the <c>--mountboot</c> flag allows genkernel to mount your <path>/boot</path> partition automatically, if necessary."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):130
+msgid "Remember, genkernel is designed to make kernel compilation easy and stress-free. For this reason, genkernel features several flags to ease the kernel compilation effort. For example, there are flags to help with kernel configuration, while others affect the actual compilation. Some flags even help debug the compilation process. For those interested in further optimization, there are flags that affect kernel assembling, packaging and even kernel initialization."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):140
+msgid "The rest of this chapter examines the functionality of various flags and actions available for genkernel. Some of the flags have variants which perform a converse operation. The converse variants carry the <b><c>no-</c></b> prefix, and their effects are enclosed within the square brackets, []."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):150
+msgid "Configuration Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):153
+msgid "The configuration flags listed below exist to help you decide what features should be enabled or disabled in the kernel prior to compilation. You can even choose whether or not the configuration file created in the process should be saved. The following are the primary configuration flags:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):161
+msgid "<b>--<c>no-</c>menuconfig</b>: Activates <e>[or deactivates]</e> the <c>make menuconfig</c> command (which invokes an interactive, menu-based kernel configuration utility), before building the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):166
+msgid "<b>--gconfig</b>: Provides a kernel configuration utility which depends on the GTK+ libraries. The advantage of this option is that most users find it easier and clearer to configure the kernel using this tool, since it relies on the X-windowing system. The disadvantage of this option is that you <b>need</b> the X-windowing system to use it, so it will not work on the command line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):174
+msgid "<b>--xconfig</b>: Provides a kernel configuration utility which depends on the QT libraries. The advantage of this option is that most users find it easier and clearer to configure the kernel using this tool, since it relies on the X-windowing system. The disadvantage of this option is that you <b>need</b> the X-windowing system to use it, so it will not work on the command line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):182
+msgid "<b>--<c>no-</c>save-config</b>: Saves <e>[or does not save]</e> the kernel configuration to a file in the <path>/etc/kernels/</path> directory for later use."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):192
+msgid "Compilation Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):195
+msgid "The following flags usually take effect during the actual compilation:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):200
+msgid "<b>--kerneldir=<path>/path/to/sources/</path></b>: Specifies an alternative kernel source location, rather than the default <path>/usr/src/linux/</path> location."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):205
+msgid "<b>--kernel-config=<path>/path/to/config-file</path></b>: Specifies what alternative kernel configuration will be used, rather than the default <path>/path/to/sources/.config</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):210
+msgid "<b>--module-prefix=<path>/path/to/prefix-directory/</path></b>: Specifies a prefix to the directory where kernel modules will be installed (default path is the <path>/lib/modules/</path> directory.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):218
+msgid "<b>--<c>no-</c>clean</b>: Activates <e>[or deactivates]</e> the <c>make clean</c> command before compiling your kernel. The <c>make clean</c> command removes all object files and dependencies from the kernel's source tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):224
+msgid "<b>--<c>no-</c>mrproper</b>: Activates <e>[or deactivates]</e> the <c>make mrproper</c> command before kernel compilation. Like the <c>make clean</c> command, <c>make mrproper</c> removes all object files and dependencies from the kernel's source tree. However, any previous configuration files (in <path>/path/to/sources/.config</path> or <path>/path/to/sources/.config.old</path>) will <b>also</b> be purged from the kernel's source tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):233
+msgid "<b>--oldconfig</b>: Issues the <c>make oldconfig</c> command, which attempts to collect configuration information for the system's architecture from a generic script in <path>/usr/share/genkernel/</path>. This is a non-interactive process; no user input is entertained. Also, if <c>--oldconfig</c> is used in conjunction with <c>--clean</c>, the latter flag is negated, resulting in the activation of the <c>--no-clean</c> flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):244
+msgid "<b>--callback=\"<c>echo hello</c>\"</b>: Calls the specified arguments (<c>echo hello</c>, in this case) after the kernel and the relevant modules have been built, but before building the initrd image. This may be useful if you want to install external modules in the initrd image by emerging the relevant item(s) with the callback feature, and then redefining a genkernel module group."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):255
+msgid "<b>--<c>no-</c>install</b>: Activates <e>[or deactivates]</e> the <c>make install</c> command, which installs your new kernel image, configuration file, initrd image and system map onto your mounted boot partition. Any compiled modules will be installed as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):261
+msgid "<b>--<c>no-</c>initrdmodules</b>: Refrains from copying any modules to the genkernel-created initrd image. This flag is an exception to the rule about the <c>no-</c> prefix; omission of this prefix creates an invalid genkernel flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):267
+msgid "<b>--genzimage</b>: Creates the initrd image, prior to the kernel image. (This hack currently applies only to PPC Pegasos systems.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):276
+msgid "Compiler Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):279
+msgid "The following flags are supported by genkernel, and are passed to the relevant applications while the kernel is being assembled. These flags affect the <e>compiler</e> used for the kernel compilation process, albeit at a much lower level."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):287
+msgid "<b>--kernel-cc=<c>someCompiler</c></b>: Specifies the compiler employed during the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):291
+msgid "<b>--kernel-ld=<c>someLinker</c></b>: Specifies the linker employed during the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):295
+msgid "<b>--kernel-as=<c>someAssembler</c></b>: Specifies the assembler employed during the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):299
+msgid "<b>--kernel-make=<c>someMake</c></b>: Specifies an alternative to the <e>GNU make</e> utility employed during the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):306
+msgid "<b>--utils-cc=<c>someCompiler</c></b>: Specifies the compiler employed during the compilation of support utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):310
+msgid "<b>--utils-ld=<c>someLinker</c></b>: Specifies the linker employed during the compilation of support utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):314
+msgid "<b>--utils-as=<c>someAssembler</c></b>: Specifies the assembler employed during the compilation of support utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):318
+msgid "<b>--utils-make=<c>someMake</c></b>: Specifies an alternative to the <e>GNU make</e> utility employed during the compilation of support utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):325
+msgid "<b>--makeopts=<c>-jX</c></b>: Specifies the number of concurrent threads that the make utility can implement while the kernel (and utilities) are being compiled. The variable <b>'X'</b> is a number obtained by adding one (1) to the number of CPUs used by the system. So, for a system with one CPU, the appropriate flag is <c>-j2</c>; a system with two CPUs will use the <c>-j3</c> flag, and so on. <e>(A system with one processor that supports Hyper-Threading&trade; (HT) Technology can use the </e><c>-j3</c><e> flag, provided Symmetric Multi-Processing (SMP) support is enabled in the kernel.)</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):341
+msgid "Debugging Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):344
+msgid "The use of debugging flags during the kernel compilation process controls the amount of information reported, as well as the presentation of said data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):350
+msgid "<b>--debuglevel=<c>verblevel</c></b>: Controls the level of verbosity for information provided by genkernel. The variable <c>verblevel</c> is an integer between 0 and 5. The level '0' represents minimal output, while '5' provides as much information as possible about genkernel's activities during the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):357
+msgid "<b>--debugfile=<path>/path/to/outputfile</path></b>: Ignores the value set by the <c>--debuglevel</c> argument, and sends <b>all</b> debugging data produced by genkernel to the specified output file, which is located at <path>/var/log/genkernel.log</path> by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):363
+msgid "<b>--no-color</b>: Activates <e>[or deactivates]</e> colored output of debugging information (reported by genkernel) using escape sequences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):373
+msgid "Initialization Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):376
+msgid "The flags here are used to create certain effects during system startup. Some of these flags are primarily for aesthetics, while others may be essential for enabling certain features on the system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):383
+msgid "<b>--<c>no-</c>splash</b>: Activates <e>[or deactivates]</e> support for <uri link=\"http://fbsplash.berlios.de/wiki/doku.php\">framebuffer splash</uri> support in the genkernel-built initrd image. To override the default theme used by fbsplash, use <b>--splash=<c>PreferredTheme</c></b> (where <c>PreferredTheme</c> is the title of one of the directories inside the <path>/etc/splash/</path> directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):391
+msgid "<b>--splash-res=<c>PreferredResolution</c></b>: This flag allows you to select which splash screen resolutions will be supported in the initrd during the start-up of the system. This is useful for two reasons: First, you are able to select only the splash screen resolution(s) relevant to your system. Second, you avoid the unnecessary increase in the disk space required by initrd (since the initrd does not have to support resolutions that are irrelevant for your system configuration.) However, you may want to omit this flag if the kernel is being compiled for an Installation CD; this allows splash support for all possible resolutions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):402
+msgid "<b>--do-keymap-auto</b>: Force keymap selection during the boot sequence."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):405
+msgid "<b>--lvm2</b>: Includes support for storage using via <uri link=\"http://sources.redhat.com/lvm2/\">Logical Volume Management</uri> (LVM2) from <e>static</e> binaries, if available to the system. Relevant (static) LVM2 binaries are compiled if they are unavailable. Be sure to install the lvm2 package on your system with <c>emerge lvm2</c> before enabling this flag, and review the <uri link=\"/doc/en/lvm2.xml\">Gentoo LVM2 Installation</uri> guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):414
+msgid "<b>--evms2</b>: Includes support for storage using the <uri link=\"http://evms.sourceforge.net/\">Enterprise Volume Management System</uri> (EVMS2), if available. Be sure to install the evms package on your system with <c>USE=static emerge evms2</c> before using this (genkernel) flag. <e>(Omitting the </e><c>USE=static</c><e> flag during package installation will fail to include the necessary static binaries.)</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):423
+msgid "<b>--dmraid</b>: Includes support for <uri link=\"http://people.redhat.com/~heinzm/sw/dmraid/readme\">DMRAID</uri>; the utility which creates RAID mappings using the kernel device-mapper subsystem. DMRAID discovers, activates, deactivates and displays properties of software RAID sets (ATARAID, for example) and contained DOS partitions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):430
+msgid "<b>--luks</b>: Includes support for <uri link=\"http://luks.endorphin.org/\">Linux Unified Key Setup</uri> or LUKS. This will allow you to use a device encrypted by LUKS which contains the root filesystem. On the bootloader, you then set that encrypted device as the value of crypt_root (and real_root shall be the unencrypted device LUKS creates)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):438
+msgid "<b>--linuxrc=/path/to/your/linuxrc</b>: Specifies a user-created <e>linuxrc</e>&mdash; a script that is initialized during the start-up stage of the kernel, prior to the actual boot process. (A default linuxrc script should be in the <path>/usr/share/genkernel/</path> directory.) This script allows you to boot into a small, modularized kernel and load the drivers that are needed (as modules) by the system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):446
+msgid "<b>--cachedir=/path/to/alt/dir/</b>: Overrides the default cache location used while compiling the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):450
+msgid "<b>--tempdir=/path/to/new/tempdir/</b>: Specifies the location of the temporary directory used by genkernel while compiling the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):454
+msgid "<b>--unionfs</b>: Includes support for the <uri link=\"http://www.fsl.cs.sunysb.edu/project-unionfs.html\">Unification File System</uri> in the initrd image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):464
+msgid "Miscellaneous Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):467
+msgid "The assortment of flags listed below are supported by genkernel, but do not fit neatly into any of the other categories:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):473
+msgid "<b>--mountboot</b>: Detects whether or not the <path>/boot/</path> directory needs to be mounted on a separate partition. It will check <path>/etc/fstab</path> script for instructions on how to mount the boot partition on a file system (if needed)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):479
+msgid "<b>--kernname=<c>NickName</c></b>: Allows you to modify the name of the kernel and initrd images in the <path>/boot/</path> directory, so that the images produced are kernel-<c>NickName</c>-version and initramfs-<c>NickName</c>-version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):490
+msgid "Possible Actions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):493
+msgid "An action tells genkernel what to build. Currently, the following actions are supported:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):499
+msgid "<c>initrd</c>: Only builds the initrd image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):500
+msgid "<c>bzImage</c>: Only builds the kernel image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):501
+msgid "<c>kernel</c>: Only builds the kernel image and modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):502
+msgid "<c>all</c>: Builds all stages &mdash; the initrd, kernel image and modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):507
+msgid "The last action, <c>all</c>, is recommended for most users since it builds the stages required for a functional kernel. Remember, an <e>action</e> simply tells genkernel what to <e>build</e>, not <e>install</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):516
+msgid "Bootloader Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):519
+msgid "To set up genkernel to work with your bootloader, three or four changes should be applied to the bootloader's configuration file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):525
+msgid "Add <c>root=/dev/ram0</c> and <c>init=/linuxrc</c> to the kernel parameters passed to the kernel image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):529
+msgid "Add <c>real_root=/dev/hda3</c>, for example, to the kernel parameters passed to the kernel image, if <path>/dev/hda3</path> contains your root partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):534
+msgid "If you are using splash, add a suitable mode line such as <c>vga=0x317</c> to the parameters passed to the kernel and also add <c>splash=verbose</c> or <c>splash=silent</c> depending on the verboseness you require from your bootloader."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):540
+msgid "Add the initrd information as required by the bootloader. Consult the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=10\">Bootloader Configuration Chapter</uri> of the Gentoo Handbook for details on how to make your bootloader initrd-aware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):553
+msgid "Configuration Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):555
+msgid "Editing /etc/genkernel.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):558
+msgid "Passing flags to genkernel from the command line can be cumbersome, especially if you have about a dozen flags:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):563
+msgid "Running genkernel (overloaded with flags)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):563
+#, no-wrap
+msgid "\n# <i>genkernel --debuglevel=5 --no-color --no-mrproper --clean --splash \\\n--kerneldir=/path/to/alternate/kernel/sources --install --menuconfig \\\n--kernel-config=/path/to/preferred/configfile --save-config --mountboot all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):569
+msgid "Fortunately, there is a configuration file where most of the basic options can be set (or changed) as necessary. What follows is a rundown of the more relevant options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):576
+msgid "<b>MENUCONFIG=<c>[yes|no]</c></b>: This option is equivalent to the <c>--menuconfig</c> flag used by genkernel, which in turn uses the <c>make menuconfig</c> command to invoke a command-line based kernel configuration utility. To invoke the utility automatically during kernel configuration via this script, set this option to 'yes' here; otherwise, choose 'no'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):583
+msgid "<b>CLEAN=<c>[yes|no]</c></b>: Setting this option to 'yes' is equivalent to the <c>--clean</c> flag used by genkernel, and invokes the <c>make clean</c> command to remove all object files and dependencies from the kernel's source tree. Setting this option to 'no' creates a cascade effect — it is equivalent to genkernel's <c>--no-clean</c> flag, which disables the <c>make clean</c> command and implies genkernel's <c>--no-mrproper</c> flag &mdash; essentially nullifying the <c>make mrproper</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):593
+msgid "<b>MRPROPER=<c>[yes|no]</c></b>: Setting this option to 'yes' is equivalent to <c>--mrproper</c> flag used by genkernel, and invokes the <c>make mrproper</c> command, which purges the kernel source tree of any configuration files. Selecting 'no' here is equivalent to genkernel's <c>--no-mrproper</c> flag, which disables the <c>make mrproper</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):600
+msgid "<b>MOUNTBOOT=<c>[yes|no]</c></b>: Setting this option to 'yes' is equivalent to the <c>--mountboot</c> flag, and automatically mounts the <path>/boot/</path> directory (if needed) at compile time. If the <path>/boot/</path> directory is on a separate partition, consider enabling this option; it will make for one less (essential) step to remember later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):607
+msgid "<b>SAVE_CONFIG=<c>[yes|no]</c></b>: After configuring the kernel, the selected options are stored as <path>.config</path> in the kernel source tree. This script may be overwritten during the next kernel compilation, or even purged from the kernel source tree. Choosing 'yes' here is equivalent to the <c>--save-config</c> flag, and stores all options selected during kernel configuration as a script in the <path>/etc/kernels/</path> directory. Choosing 'no' preserves the <e>status quo</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):616
+msgid "<b>USECOLOR=<c>[yes|no]</c></b>: Setting this option to 'yes' is equivalent to the <c>--color</c> flag, which colors genkernel's output to ease debugging (when needed.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):621
+msgid "<b>DEBUGLEVEL=<c>[0|1|2|3|4|5]</c></b>: This option is for adjusting the verbosity of the output produced by genkernel &mdash; setting this option to '0' with <c>--debuglevel=0</c> will suppress all output produced by genkernel; setting this option to '5' with <c>--debuglevel=5</c> provides the user with all output produced by genkernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):630
+msgid "By choosing the appropriate options in <path>/etc/genkernel.conf</path>, you can halve the number of flags passed to genkernel from the command line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):635
+msgid "Running genkernel (with flags), after employing genkernel.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):635
+#, no-wrap
+msgid "\n# <i>genkernel --splash --kerneldir=/path/to/alternate/kernel/sources \\\n--kernel-config=/path/to/preferred/configfile --install all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):640
+msgid "Identical results are obtained from both approaches, but the latter has most of the options stored in a script that can be modified at a later date."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):650
+msgid "Network-Booting with genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):652
+msgid "Network Booting from an Installation CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):655
+msgid "The genkernel utility can build kernel and initrd images that provide support for network booting, or <e>netboot</e>ing. With any luck, you should be able to netboot any recent computer into the environment provided by the Installation CD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):662
+msgid "The magic lies in genkernel's linuxrc script: it will try to <e>netmount</e> the Installation CD using NFS. From there, <e>the init scripts</e> of the Installation CD can take over, as if the CD was present locally."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):671
+msgid "Building Kernel and Initrd Images with Support for Netbooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):674
+msgid "To enable support for netbooting, include the following options while configuring the kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(warn):679
+msgid "Support for netbooting with genkernel is experimental and may contain bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):683
+msgid "First, the kernel image must include the drivers for your Network Interface Cards (NIC). Normally, drivers for such devices will be compiled as modules. However, it is essential (for netbooting) that you have such drivers compiled directly into the kernel image and <b>not</b> as modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):690
+msgid "Configuring a 2.6.x series kernel to support your NIC driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):690
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\n   Networking Support ---&gt;\n      Ethernet (10 or 100Mbit)  ---&gt;\n         [*] Ethernet (10 or 100Mbit)\n         &lt;*&gt;   the driver for your network card\n<comment>(Be sure to select &lt;*&gt; and not &lt;M&gt;)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):699
+msgid "Secondly, we suggest that you enable <c>IP: kernel level autoconfiguration</c> and the <c>IP: DHCP support</c> options. This avoids an unnecessary layer of complexity since the IP address and the NFS path to the Installation CD can be configured on a DHCP server. Of course, this means the kernel command line will remain constant for any machine &mdash; which is very important for <e>etherbooting</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):708
+msgid "Configuring a 2.6.x series kernel to support DHCP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):708
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\n   Networking Support ---&gt;\n      Networking options\n         [*] TCP/IP networking---&gt;\n         [*]   IP: kernel level autoconfiguration\n         [*]     IP: DHCP support\n<comment>(These options tell the kernel to send a DHCP request at bootup.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):718
+msgid "Additionally, you should enable SquashFS because most modern Gentoo Installation CDs require it. Support for SquashFS is not included with the generic kernel source tree. To enable SquashFS, apply the necessary patches to the generic kernel source or install <c>gentoo-sources</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):725
+msgid "Configuring the kernel to support SquashFS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):725
+#, no-wrap
+msgid "\nFile systems---&gt;\n   Miscellaneous filesystems ---&gt;\n      [*] SquashFS 2.X - Squashed file system support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):731
+msgid "Once the compilation process is completed, create a compressed <e>tarball</e> (tar.gz) that contains the kernel's modules. This step is only necessary if your kernel version does not match the kernel image version on the Installation CD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):738
+msgid "Creating a compressed tarball containing the kernel modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):738
+#, no-wrap
+msgid "\n<comment>(Create a tar.gz containing all the modules)</comment>\n# <i>cd /</i>\n# <i>tar -cf /tmp/modules-X.Y.Z.tar.gz /lib/modules/X.Y.Z/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):744
+msgid "Depending on your network boot mechanism, you will need to do some of the following steps:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):749
+msgid "Creating a boot image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):749
+#, no-wrap
+msgid "\n<comment>(Create an etherboot image)</comment>\n# <i>emerge mknbi</i>\n# <i>cd /boot</i>\n# <i>mkelf-linux -params=\"root=/dev/ram0 init=/linuxrc ip=dhcp\" kernel... initrd... &gt; etherboot.img</i>\n\n<comment>(Create a OpenBoot / SPARC64 TFTP image)</comment>\n# <i>emerge sparc-utils</i>\n# <i>cd /boot</i>\n# <i>elftoaout kernel... -o kernel.aout</i>\n# <i>piggyback64 kernel.aout System.map-... initrd-...</i>\n# <i>mv kernel.aout openboot.img</i> <comment>(This is the boot image)</comment>\n\n<comment>(PXE does not need any more steps, the kernel and initrd can be used as is)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):765
+msgid "Finally, copy this kernel to your TFTP server. The details are architecture-dependent and are beyond the scope of this guide. Please refer to the documentation for your platform."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):774
+msgid "NFS Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):777
+msgid "To setup a NFS share that contains the Installation CD, use the loop device to mount the ISO image and then copy the contents of the CD into the NFS share. As a nice extra, genkernel's initrd scripts will extract all tar.gz files located in the <path>/nfs/livecd/add/</path> directory. All you have to do here is copy the <c>modules-X.Y.Z.tar.gz</c> archive to the <path>/nfs/livecd/add/</path> directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):786
+msgid "Preparing the NFS share"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):786
+#, no-wrap
+msgid "\n<comment>(This assumes that /nfs/livecd is an exported NFS share)</comment>\n# <i>mount /tmp/gentoo-livecd.iso /mnt/cdrom -o loop</i>\n# <i>cp -p /mnt/cdrom /nfs/livecd</i>\n# <i>umount /mnt/cdrom</i>\n\n<comment>(Copy the modules.tar.gz into /add)</comment>\n# <i>mkdir /nfs/livecd/add</i>\n# <i>cp /tmp/modules-X.Y.Z.tar.gz /nfs/livecd/add</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):800
+msgid "DHCP Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):803
+msgid "The netboot images will ask your DHCP server for an IP as well as a root-path parameter. Both can be specified per host using a MAC address to identify machines:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):809
+msgid "Sample client dhcpd.conf setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):809
+#, no-wrap
+msgid "\n...\n\nhost netbootableMachine {\n         hardware ethernet 11:22:33:44:55:66;\n         fixed-address 192.168.1.10;\n         option root-path \"192.168.1.2:/nfs/livecd\";\n}\n<comment># Here, 192.168.1.2 is the NFS server\n# While 192.168.1.10 will be the IP address of the netbooted machine</comment>\n...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):825 ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):836
+msgid "Netbooting Instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):828
+msgid "Netbooting itself is again very platform-specific. The important part is to specify the <c>ip=dhcp</c> and <c>init=/linuxrc</c> parameters on the kernel command line, as this will bring up the network interface and tell the initrd scripts to mount the Installation CD via NFS. Here are some platform-specific tips:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):836
+#, no-wrap
+msgid "\n<comment># Etherboot - insert the etherboot disk into the drive and reboot\n# The kernel command line was specified when the image was constructed</comment>\n\n<comment># Sparc64 - Hit Stop-A at the boot prompt</comment>\nok boot net ip=dhcp init=/linuxrc\n\n<comment># PXE - Setup pxelinux (part of syslinux),\nthen create a pxelinux.cfg/default along the lines of:</comment>\n\nDEFAULT gentoo\nTIMEOUT 40\nPROMPT 1\n\nLABEL gentoo\n    KERNEL kernel-X.Y.Z\n    APPEND initrd=initrd-X.Y.Z root=/dev/ram0 init=/linuxrc ip=dhcp\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):860
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):862
+msgid "To Automate or not to Automate?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):865
+msgid "The purpose of genkernel is to provide an (easier) alternative to the time-tested approach to kernel compilation. As always, you are free to decide on whether or not you want to automate the kernel compilation process."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-alpha-faq.xml.pot b/doc/gettext/gentoo-alpha-faq.xml.pot
new file mode 100644
index 0000000..1eaae25
--- /dev/null
+++ b/doc/gettext/gentoo-alpha-faq.xml.pot
@@ -0,0 +1,476 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(guide:link):5
+msgid "/doc/en/gentoo-alpha-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):7
+msgid "Gentoo Linux/Alpha Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail:link):9
+msgid "tcort@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail):9
+msgid "Thomas Cort"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail:link):12
+msgid "grknight2k@bluebottle.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail):12
+msgid "Brian Evans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(abstract):18
+msgid "This FAQ is intended to answer some of the most frequently asked questions relating to Gentoo/Alpha and Linux/Alpha in general."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(version):27
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(date):28
+msgid "2008-01-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):31
+msgid "About this Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):34
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):37
+msgid "This document contains answers to the most commonly asked questions about Gentoo/Alpha and Alpha/Linux. It's aimed at both new users and experienced users alike."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):48
+msgid "About the Gentoo/Alpha Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):50
+msgid "What is Gentoo/Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):53
+msgid "The Gentoo/Alpha project is responsible for keeping the Gentoo distribution updated and current for the Alpha platform. This primarily includes keywording packages, porting software, and making new releases. The Gentoo/Alpha project aims to provide a usable environment for both desktops and servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):63
+msgid "What is the current status of the Gentoo/Alpha Project?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):66
+msgid "You can find out about the current status of the Gentoo/Alpha project via status reports. These reports inform the public about what we've been up to. New status reports will be posted about once every 6 months. Current and past status report can be found on the <uri link=\"/proj/en/base/alpha/status/index.xml\">Status Reports Project page</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):79
+msgid "The Alpha Architecture"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):81
+msgid "Isn't the Alpha architecture dead?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):84
+msgid "Not quite! HP stopped taking orders for new Alpha systems on April 27, 2007. They will take orders for Alpha options and upgrades until April 25, 2008. See their <uri link=\"http://h18002.www1.hp.com/alphaserver/evolution.html\">planning page</uri> for more details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):94
+msgid "Can I run 32-bit applications?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):97
+msgid "No, all Alpha systems use a pure 64 bit kernel and a pure 64 bit userland. You cannot even force gcc to output 32 bit code using the <c>-m32</c> compiler flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):106
+msgid "Is Alpha big endian or little endian?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):109
+msgid "All Alpha systems support both little and big endian. However, Linux only uses little endian."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):117
+msgid "Can I run Linux/x86 applications on Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):120
+msgid "No, not without a full x86 system emulator like <uri link=\"http://bochs.sourceforge.net/\">bochs</uri>. In the past DEC/Compaq/HP maintained a program called <c>em86</c> which allowed Linux/x86 applications to be run on Linux/Alpha systems. However, the program is closed source and no longer maintained upstream. There are no <c>em86</c> binaries available that are compatible with gcc3's ABI."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):132
+msgid "Why install Gentoo on Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):135
+msgid "Admittedly, you can find faster 64-bit systems out there, like amd64. However, that doesn't mean that Alpha systems are useless. The following are a few good reasons why you'd want to install Linux on this sort of hardware:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):142
+msgid "You can turn an old computer into something useful. Older Alphas make great routers and servers. Their desktop performance isn't that bad either."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):146
+msgid "You will learn about unusual computer hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):147
+msgid "It's cool. How many people can say they've got Linux running on an Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):155
+msgid "Where can I buy Alpha hardware?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):158
+msgid "Alpha hardware generally isn't available at your local computer store. If you want a new Alpha you're going to have to contact <uri link=\"http://h18002.www1.hp.com/alphaserver/\">HP</uri>. If you want a used Alpha (more economical), <uri link=\"http://ebay.com\">eBay</uri> is usually a good option, assuming that the shipping doesn't cost you too much. There are several used equipment dealers that can be found via google, however most of them charge too much."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):173
+msgid "Hardware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):175
+msgid "I opened up the case on an AlphaServer and now it won't power on, what do I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):179
+msgid "Make sure the top panel of the case is on and properly in place. The middle of the top panel of the case has a small piece of metal oriented downwards. When the top panel is put back in place properly, the small piece of metal will press down on a switch. When the switch isn't pressed down, the system will refuse to power on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):192
+msgid "Alpha Specific Compiler Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):194
+msgid "Is the use of Alpha specific compiler flags recommended?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):197
+msgid "As with all compiler optimizations, don't over do it. Use these flags with care and they will give you a stable, speedy system; use them too aggressively and you could seriously break your system. When in doubt, leave it out. If you need further clarification, check the <c>gcc</c> man page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):207
+msgid "How do I optimize for a specific instruction set and scheduling model?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):212
+msgid "You can optimize for a specific instruction set and scheduling model with <c>-mcpu=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</c>, <c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and <c>ev67</c>. If you do not use the <c>-mcpu=XXX</c> flag, then <c>gcc</c> will default to the cpu type of the machine it was compiled on. <c>-mcpu=</c> is equivalent to the <c>-march=</c> flag on x86."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(note):221
+msgid "AlphaServer 800 users should set <c>ev5</c>. There are known issues setting <c>ev56</c> particularly with Xorg causing a full system lock up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):229
+msgid "How do I specify the scheduling model without changing the instruction set?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):234
+msgid "You can specify the scheduling model without changing the instruction set with <c>-mtune=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</c>, <c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and <c>ev67</c>. <c>-mtune=</c> is implied by <c>-mcpu=</c>, so you don't need to specify this with if you set <c>-mcpu=</c>. <c>-mtune=</c> is equivalent to the <c>-mcpu=</c> flag on x86."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):246
+msgid "How do I enable software assisted floating point numbers?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):249
+msgid "You can enable software assisted floating point numbers with <c>-mieee</c>. This will enable software assistance to correctly support denormalized numbers and exceptional IEEE values such as not-a-number and plus/minus infinity."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):255
+msgid "This should be in your global <c>CFLAGS</c> unless you really know what you are doing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):263
+msgid "How do I specify the memory latency of my system?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):266
+msgid "You can specify the memory latency of your system with <c>-mmemory-latency=XXX</c>, where XXX is the number of clock cycles. This sets the latency time that the scheduler should assume for memory references. <c>gcc</c> has some predefined \"typical\" values that are also accepted by <c>-mmemory-latency=XXX</c>. Those values are <c>L1</c> for Dcache, <c>L2</c> for Scache, <c>L3</c> for Bcache, and <c>main</c> for main memory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):275
+msgid "This flag should probably not be use in your global <c>CFLAGS</c> as the value you choose is highly dependent on the memory access pattern of the application you are compiling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):284
+msgid "How do I specify that static data should be placed in the small data area?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):289
+msgid "You can specify that static data should be placed in the small data area with <c>-msmall-data</c>. This will cause <c>gcc</c> to take advantage of some features of the Alpha architecture by storing heavily used pieces of data in specific sections called the small memory sections. The sections are limited to 64kb which means accessing anything stored in them will only take one instruction."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):298
+msgid "<c>-fPIC</c> will override <c>-msmall-data</c>, so you should use the <c>-fpic</c> flag instead if you do not want <c>-msmall-data</c> to be overridden."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):304
+msgid "This flag should probably not be used in your global <c>CFLAGS</c> as some objects require more than 64kb to be stored, and this will cause a gp_overflow ld error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):313
+msgid "How do I specify that object code should be placed in the small text area?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):318
+msgid "You can specify that object code should be placed in the small text area with <c>-msmall-text</c>. This will cause <c>gcc</c> to assume that the entire program (or library) fits in 4MB, and is thus reachable with a branch instruction. This reduces the number of instructions required for a function call from 4 to 1."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):326
+msgid "This flag should probably not be used in your global <c>CFLAGS</c> as some programs (or libraries) are larger than 4MB, and this will cause an ld error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):334
+msgid "What do I do if any of these compiler flags cause a compile, linker, or runtime error?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):340
+msgid "As <uri link=\"#CFLAGS\">already mentioned</uri>, please use these <c>CFLAGS</c> cautiously. They may break your system. If you experience problems, try using less aggressive <c>CFLAGS</c> before <uri link=\"#bugs\">filing a bug report</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):352
+msgid "Alpha Booting and Bootloaders"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):354
+msgid "What is SRM?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):357
+msgid "SRM is based on the Alpha Console Subsystem specification, which provides an operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. See the <uri link=\"http://www.alphalinux.org/faq/SRM-HOWTO/\"> SRM Howto</uri> for more information about SRM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):367
+msgid "What is ARC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):370
+msgid "ARC is based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):378
+msgid "How can I tell if which firmware my Alpha has, ARC or SRM?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):381
+msgid "When you power your system on you will see a screen with a blue background and white text if it is using SRM. You will see a graphical boot system if it is using ARC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):390
+msgid "Which bootloader do I use?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):393
+msgid "If your Alpha system supports SRM, then you should use aboot. If your system supports both SRM and ARCs (ARC, AlphaBIOS, ARCSBIOS), then you should follow <uri link=\"http://www.alphalinux.org/faq/x31.html\">the SRM Firmware Howto</uri> for switching to SRM and use aboot. If your system can only use ARCs (Ruffian, nautilus, xl, etc.) then you will need to choose milo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):404
+msgid "Can aboot boot kernels from xfs, reiserfs, or jfs partitions?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):407
+msgid "No, <c>aboot</c> only supports booting kernels from <c>ext2</c> and <c>ext3</c> partitions. You may still use other files systems for your root partition, you just need to create a <path>/boot</path> partition with either <c>ext2</c> or <c>ext3</c> on it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):414
+msgid "Support for reiserfs and xfs is planned. In fact, there are patches floating around that add support for those two file systems. However, the use of those patches is unsupported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):424
+msgid "Software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):427
+msgid "How is Java support in Gentoo/Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):430
+msgid "There was only one option for Java VM and Java SDK on Gentoo/Alpha. The packages were called <c>compaq-jre</c> and <c>compaq-jdk</c>. Sadly, Compaq/HP stopped all support and the packages were removed from Gentoo on October 11, 2006."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):441
+msgid "Will there ever be working Java support?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):444
+msgid "We really hope so. We are following the development of the jdk from <uri link=\"http://sablevm.org\">SableVM</uri>. It isn't ready yet, but we hope with time that it will be a full drop in replacement jdk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):453
+msgid "How is .NET support in Gentoo/Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):456
+msgid "Neither of the two main open source efforts, <uri link=\"http://www.mono-project.com/Main_Page\">mono</uri> nor <uri link=\"http://www.dotgnu.org/\">DotGNU</uri>, support the alpha architecture."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):465
+msgid "What is needed for .NET support?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):468
+msgid "Bringing .NET to alpha isn't a simple task. It requires coding all of the assembly language code generation macros for the JIT (just in time) compiler and coding architecture specific functions (register allocators, etc)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):479
+msgid "Alpha Linux Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):481
+msgid "Which kernel sources should I use?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):484
+msgid "We recommend using <c>gentoo-sources</c> but <c>vanilla-sources</c> is also supported by Gentoo/Alpha. You should read the <uri link=\"/doc/en/gentoo-kernel.xml\">Gentoo Kernel Guide</uri> to determine which one is right for your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):494
+msgid "My system is broken with kernel-2.6, Can I build a 2.4 bassed system?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):497
+msgid "Gentoo/Alpha stopped supporting 2.4 kernel and profile in January 2008. Technically you can build a 2.4 Gentoo System (the kernel is in the tree) but you will have to mask all the 2.6 only packages by yourself and you won't have support from developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):504
+msgid "Gentoo/Alpha will review all bug reports about non working 2.6 systems and will try to help as much as we can."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):513
+msgid "Are hardened-sources supported?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):516
+msgid "Short answer is no. They were supported some time ago, but we lost the hardware and the maintainer so right now they are not supported. If you are interested and want to continue the initial work, please let us know."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):525
+msgid "Does the 2.6 kernel support Alpha SMP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):528
+msgid "There were some times in the past when it was broken. However, <c>2.6.15.1</c> and <c>2.6.16.19</c> are both known to work well. If you find that SMP is broken and want SMP support you will need revert to the one of the versions mentioned above or use a 2.4 kernel. If you really need to run the latest 2.6 kernel on an SMP box and you don't care that only one of your processors is getting used, then you could configure the 2.6 kernel without SMP support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):542
+msgid "Helping out the Gentoo/Alpha Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):544
+msgid "How do I report bugs?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):547
+msgid "If you find a bug or you want to send us patches, then you need to file a bug report. It only takes you a little bit of your time, and your help is really appreciated. Please follow the <uri link=\"/doc/en/bugzilla-howto.xml\">Gentoo Bug Reporting Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):557
+msgid "How can I help the Gentoo/Alpha Project?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):560
+msgid "Users can help us by:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):565
+msgid "Filing clear and concise <uri link=\"#bugs\">bug reports</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):566
+msgid "Testing software that does not yet have the <c>~alpha</c> keyword."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):567
+msgid "Answering questions on the <uri link=\"/main/en/lists.xml\">mailing lists</uri>, <uri link=\"http://forums.gentoo.org/viewforum-f-32.html\"> forum</uri> and IRC channel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):572
+msgid "Sending patches"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):573
+msgid "Becoming an <uri link=\"http://www.gentoo.org/proj/en/base/alpha/AT/index.xml\">AT</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):581
+msgid "Is there an Alpha Arch Testers Project?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):584
+msgid "Yes, see the <uri link=\"http://www.gentoo.org/proj/en/base/alpha/AT/index.xml\"> Gentoo Linux Alpha Arch Testers Project</uri> page for details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):594
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):596
+msgid "Why is my Xorg locking up my Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):599
+msgid "This is usually caused by a bad -mcpu setting. For example, the AlphaServer 800 needs to be compiled with the <c>ev5</c> flag for xorg <b>and</b> glibc. Failing to do so will cause undesired results."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):610
+msgid "Other Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):612
+msgid "Why is there no Gentoo on Alpha forum?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):615
+msgid "On the <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri> there are several arch specific categories like <uri link=\"http://forums.gentoo.org/viewforum-f-24.html\">Gentoo on PPC</uri> and <uri link=\"http://forums.gentoo.org/viewforum-f-24.html\">Gentoo on Sparc</uri>. There is no Gentoo on Alpha category because there simply isn't enough Gentoo/Alpha activity on the forums to warrant one. All Alpha related posts should go in the <uri link=\"http://forums.gentoo.org/viewforum-f-32.html\"> Gentoo on Alternative Architectures</uri> category."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):630
+msgid "Where can I get more help or information about Gentoo/Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):633
+msgid "If any of your questions weren't answered here, you can try other resources like the <uri link=\"/doc/en/handbook/handbook-alpha.xml\">Alpha Handbook</uri> or <uri link=\"/proj/en/base/alpha/\">our project homepage</uri>. You can also ask us at <c>#gentoo-alpha</c> on <c>irc.freenode.net</c>, <uri link=\"http://forums.gentoo.org/viewforum-f-32.html\">Gentoo on Alternative Architectures Forum</uri>, or on the <mail>gentoo-alpha@lists.gentoo.org</mail> mailing list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):646
+msgid "Where can I get more help or information about Alpha/Linux?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):649
+msgid "<uri link=\"http://alphalinux.org/\">AlphaLinux.org</uri> is a central repository for all things Alpha/Linux."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-alpha-install.xml.pot b/doc/gettext/gentoo-alpha-install.xml.pot
new file mode 100644
index 0000000..42a6365
--- /dev/null
+++ b/doc/gettext/gentoo-alpha-install.xml.pot
@@ -0,0 +1,52 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(guide:redirect):3
+msgid "/doc/en/handbook/handbook-alpha.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(title):4 ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(title):20
+msgid "Gentoo Alpha Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(author:title):6
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(mail:link):7
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(mail):7
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(abstract):10
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(version):16
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(date):17
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(p):24
+msgid "As of 2004.0, the individual architecture-specific installation guides have been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/handbook/handbook-alpha.xml\">Gentoo Handbook</uri>. For more information please read up on the <uri link=\"/doc/en/handbook\">Gentoo Handbook Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-amd64-faq.xml.pot b/doc/gettext/gentoo-amd64-faq.xml.pot
new file mode 100644
index 0000000..fed8d9f
--- /dev/null
+++ b/doc/gettext/gentoo-amd64-faq.xml.pot
@@ -0,0 +1,332 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):6
+msgid "Gentoo Linux/AMD64 Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):9
+msgid "blubb@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail):9
+msgid "Simon Stelling"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):12
+msgid "metalgod@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail):12
+msgid "Luis Medinas"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):15
+msgid "gerrynjr@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail):15
+msgid "Gerald J. Normandin Jr."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):18
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail):18
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):21
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(abstract):24
+msgid "This is the Gentoo Linux/AMD64 Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(version):32
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(date):33
+msgid "2010-07-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):36
+msgid "Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):38
+msgid "Introduction to Gentoo/AMD64 FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):41
+msgid "This document contains the most commonly asked questions about Gentoo/AMD64. We intend to help and provide useful information about Gentoo/AMD64. Some of these questions can be found in forums, IRC, or mailing lists. If you have suggestions or questions about this FAQ, you are welcome to send an e-mail to <mail>amd64@gentoo.org</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):54
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):56
+msgid "What's the difference between AMD64 and EM64T?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):59
+msgid "Both refer to 64-bit processors from AMD (AMD64) and Intel (EM64T). AMD's 64-bit processors include the Athlon 64, Turion, Neo, Phenom, and Opteron families. Intel's 64-bit processors include the Core2, Core i<e>X</e>, Celeron, Xeon, and Pentium (all based on the Core2 architecture). The <uri link=\"http://en.wikipedia.org/wiki/Em64t#Intel_64\">last few versions</uri> of the old Pentium 4 and Xeon chips also support EM64T."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):68
+msgid "The AMD line of 64-bit processors were released well ahead of Intel's offering. Therefore, for historical reasons the arch keyword for all x86-64 compatible architectures is amd64. As such, <e>AMD64</e> is a generic reference to 64-bit chips, whether AMD or Intel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):78
+msgid "What CFLAGS should I use for AMD64/EM64T?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):81
+msgid "You should use simple <c>CFLAGS</c> to avoid future problems with your system. Supported <c>CFLAGS</c> are <c>-O2 -march=k8 -pipe</c> for AMD systems. Intel Core2-based systems (EM64T) should use <c>-O2 -march=core2 -pipe</c>. If you're on an old Intel Pentium 4 that supports EM64T, then use <c>-O2 -march=nocona -pipe</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):92
+msgid "What kernel should I use for AMD64?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):95
+msgid "You can use almost all kernel sources available in Portage. We recommend using <c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux. It contains lots of AMD64-specific patches and therefore is the only kernel officially supported by Gentoo/AMD64."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(warn):102
+msgid "You should watch out for some kernel features which are not well tested, such as <c>PREEMPT</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):107
+msgid "Make sure you have the <c>IA32_EMULATION</c> option activated in the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre:caption):111
+msgid "Activating IA32 Emulation in Kernel source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre):111
+#, no-wrap
+msgid "\n# <i>cd /usr/src/linux</i>\n# <i>make menuconfig</i>\n\nExecutable file formats / Emulations  ---&gt;\n  [*] IA32 Emulation\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(warn):119
+msgid "You may experience build failures on multilib-systems if you deactivate this option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):127
+msgid "Will I have a performance upgrade if I use a 64bit system instead of 32bit?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):130
+msgid "That is a difficult question to answer. In some cases, you will experience a performance improvement, in other cases you will not. For everyday use, there is nearly no difference between 64bit and 32bit. 64bit is generally faster when it comes to floating point computing which is normally the case in multimedia applications and 3D rendering. This <uri link=\"http://www.linux.com/articles/114024?tid=121\">article</uri> (and a <uri link=\"http://www.linux.com/feature/43873\">related</uri> article) may interest you. There's also a nice <uri link=\"http://forums.gentoo.org/viewtopic-t-349691.html\">thread</uri> in our <uri link=\"http://forums.gentoo.org\">forums</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):146
+msgid "What is multilib and how can I use it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):149
+msgid "Every AMD64 processor is able to run 32bit code as well as 64bit code. However, when you have a 32bit application, you are unable to mix it with 64bit libraries or vice versa. You can, however, natively run 32bit applications if all shared libraries it needs are available as 32bit objects. You can choose whether you want multilib support or not by selecting the according profile. The default is a multilib-enabled profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(warn):158
+msgid "Currently you cannot switch from a no-multilib to a multilib-enabled profile, so think over your decision twice before you use the no-multilib profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):166
+msgid "How do I create a 32bit chroot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):169
+msgid "Please read the <uri link=\"/proj/en/base/amd64/howtos/chroot.xml\">32bit chroot guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):177
+msgid "Can I upgrade from my x86 system to amd64 by doing emerge -e world?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):180
+msgid "Due to several differences between an <c>x86</c> and an <c>amd64</c> installation, it is impossible to upgrade. Please perform a fresh install. The installation is slightly different than an x86 one, so please use the <uri link=\"/doc/en/handbook/handbook-amd64.xml\">AMD64 Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):187
+msgid "Also, binary files created on an x86 system most likely cannot be read by packages on an amd64 system. In particular, databases such as MySQL, innoDB, Berkeley DB, SQLite, OpenLDAP, etc. cannot simply be copied as-is. You will need to dump the database into an architecture-independent format, such as a text file, before attempting to restore it on an amd64 system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):198
+msgid "Can I use Reiser4?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):201
+msgid "Reiser4 is not available from any kernel offered by the Gentoo Kernel project, thus the AMD64 team doesn't support it. The answer is no."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):211
+msgid "Hardware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):213
+msgid "Will my binary NVIDIA/ATI drivers work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):216
+msgid "Yes, NVIDIA and ATI provide drivers that work on AMD64. You can install them by executing <c>emerge nvidia-drivers</c> or <c>emerge ati-drivers</c>. If you have more questions about these drivers, you should read the <uri link=\"/doc/en/nvidia-guide.xml\">Nvidia guide</uri> or the <uri link=\"/doc/en/ati-faq.xml\">ATI FAQ</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):227
+msgid "How do I use Cool'n'Quiet/PowerNow/SpeedStep features?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):230
+msgid "You have to compile your kernel with support for these features. You just need to enable the features below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre:caption):235
+msgid "Kernel options for Cool'n'Quiet/PowerNow/SpeedStep"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre):235
+#, no-wrap
+msgid "\nPower management options ---&gt;\n  [*] Power Management support\n  [*] ACPI (Advanced Configuration and Power Interface) Support ---&gt;\n    &lt;*&gt;   Processor\n    &lt;*&gt;     Thermal Zone\n  CPU Frequency scaling ---&gt;\n  [*] CPU Frequency scaling\n         Default CPUFreq governor (ondemand) ---&gt;\n  -*-   'performance' governor\n  &lt;*&gt;   'userspace' governor for userspace frequency scaling\n  -*-   'ondemand' cpufreq policy governor\n  &lt;*&gt;   ACPI Processor P-States driver\n  &lt;*&gt;   AMD Opteron/Athlon64 PowerNow!\n-*- CPU idle PM support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):252
+msgid "Then <c>emerge cpufrequtils</c> and edit <path>/etc/conf.d/cpufrequtils</path> with your favorite editor."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre:caption):257
+msgid "Example of /etc/conf.d/cpufrequtils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre):257
+#, no-wrap
+msgid "\n# Options when starting cpufreq (given to the 'cpufreq-set' program)\nSTART_OPTS=\"--governor ondemand\"\n\n# Options when stopping cpufreq (given to the 'cpufreq-set' program)\nSTOP_OPTS=\"--governor performance\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):265
+msgid "Now you only have to run <c>rc-update add cpufrequtils boot</c> to make sure it is started every time you boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(note):270
+msgid "You may want to read the <uri link=\"/doc/en/power-management-guide.xml#doc_chap3\">Power Management Guide</uri> for more tips on CPU power management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):281
+msgid "Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):283
+msgid "Can I get Adobe Flash working?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):286
+msgid "Yes. Just <c>emerge adobe-flash</c>. Be sure to read any messages displayed by the ebuild once it has been emerged."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):301
+msgid "Can I get OpenOffice.org working?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):304
+msgid "Yes. Run <c>emerge openoffice</c>. It may take several hours and use most of your system resources. If you don't think your machine is up to it, you can try installing the precompiled binary, <c>openoffice-bin</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):313
+msgid "I want to install package foo, but emerge says: (masked by: ~amd64 keyword)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):316
+msgid "This means that the package is still in the 'testing' tree. Please read <c>man portage</c> or the <uri link=\"/doc/en/handbook/handbook-amd64.xml?part=3&amp;chap=3\">Mixing Software Branches</uri> chapter of the <uri link=\"/doc/en/handbook/handbook-amd64.xml\">AMD64 Handbook</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):328
+msgid "I want to install package foo, but emerge says: (masked by: missing keyword)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):331
+msgid "This means that the package has not been tested yet. It does <e>not necessarily</e> mean that the package does not work. You can unmask it by accepting another architecture for the package. The following example shows you can tell Portage to accept any keyword for a given package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre:caption):338
+msgid "Example of adding package keywords"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre):338
+#, no-wrap
+msgid "\n# <i>echo \"category/packagename **\" &gt;&gt; /etc/portage/package.keywords</i>\n# <i>emerge packagename</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):343
+msgid "If it works fine for you, please let us know and file a bug on <uri link=\"http://bugs.gentoo.org/\">Gentoo's Bugzilla</uri>, so that the AMD64 team can keyword the package and other users can benefit from your test."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(warn):349
+msgid "Do not try commands like <c>ACCEPT_KEYWORDS=\"~x86\" emerge packagename</c>. It will most certainly break your tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):359
+msgid "How can I help the Gentoo/AMD64 project?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):361
+msgid "How can I help?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):364
+msgid "With a growing popularity of the amd64 architecture, we also increasingly need more help. There's still much work to be done to improve the quality of Gentoo/AMD64. An average user can help us by:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):371
+msgid "Filing general bug reports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):372
+msgid "Testing software that does not yet have the <c>~amd64</c> keyword"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):373
+msgid "Participating in the <uri link=\"/proj/en/base/amd64/at/\">Arch Testers project</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):377
+msgid "Help answering questions on the mailing lists, forums and IRC channels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):380
+msgid "Sending patches"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):388
+msgid "Other Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):390
+msgid "Where can I get more help or information about Gentoo/AMD64?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):393
+msgid "If any of your questions wasn't answered here, you can try other resources listed on <uri link=\"/proj/en/base/amd64/\">our project homepage</uri>. You can also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri link=\"http://forums.gentoo.org/viewforum-f-46.html\">Gentoo/AMD64 Forums</uri>, or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-freebsd.xml.pot b/doc/gettext/gentoo-freebsd.xml.pot
new file mode 100644
index 0000000..3d755b3
--- /dev/null
+++ b/doc/gettext/gentoo-freebsd.xml.pot
@@ -0,0 +1,749 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):6
+msgid "A short guide to Gentoo/FreeBSD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):20
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):9
+msgid "ignacio.arquelatour@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):9
+msgid "Ignacio Arque-Latour"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):12
+msgid "citizen428@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):12
+msgid "Michael Kohl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):15
+msgid "angusyoung@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):15
+msgid "Otavio R. Piske"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):18
+msgid "ka0ttic@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):18
+msgid "Aaron Walker"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):21
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):21
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):23
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):24
+msgid "flameeyes@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):24
+msgid "Diego Pettenò"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):26 ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):29
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):27
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):27
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):30
+msgid "cam@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):30
+msgid "Camille Huot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(abstract):33
+msgid "This document gives some general information on FreeBSD, as well as installation instructions for Gentoo/FreeBSD. It also includes some reference for people interested in helping out with development."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(version):43
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(date):44
+msgid "2010-08-08"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):47
+msgid "Introduction to FreeBSD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):49
+msgid "What is FreeBSD?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):52
+msgid "<uri link=\"http://www.freebsd.org/\">FreeBSD</uri> is a free (<uri link=\"http://www.freebsd.org/copyright/freebsd-license.html\">license</uri>) Unix-like operating system. Back in 1993 when development of <uri link=\"http://www.386bsd.org/\">386BSD</uri> stopped, two projects were born: <uri link=\"http://www.netbsd.org/\">NetBSD</uri>, commonly known to run on a huge number of architectures, and FreeBSD which supports the x86, amd64, ia64, sparc64 and alpha platforms. FreeBSD is renowned for its stability, performance and security, thus being used from small to huge companies all over the world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):63
+msgid "FreeBSD's current production release is version 7.1. Gentoo/FreeBSD is based on version 6.2 and older versions of Gentoo/FreeBSD are discontinued and no longer supported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):72
+msgid "What is Gentoo/FreeBSD?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):75
+msgid "<uri link=\"/proj/en/gentoo-alt/bsd/fbsd/\">Gentoo/FreeBSD</uri> is a subproject of the <uri link=\"/proj/en/gentoo-alt/\">Gentoo/Alt project</uri>, with the goal of providing a fully-capable FreeBSD operating system featuring design sensibilities taken from Gentoo Linux, such as the init system and the Portage package management system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):86
+msgid "FreeBSD and Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):89
+msgid "Users migrating from Linux to FreeBSD commonly consider the two operating systems \"almost the same\". In fact, FreeBSD really shares a lot of similarities with Linux distributions in general. Nevertheless, it has some key differences that are worth noting:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):97
+msgid "Contrary to Linux, which actually only refers to the kernel, FreeBSD is a complete operating system, consisting of a C library, userland tools and much more. This development approach makes the overall system very consistent."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):103
+msgid "Contrary to the Linux kernel, FreeBSD development is not led by one person, but instead managed by a small group of people called the <uri link=\"http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html\">Core Team</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):111
+msgid "Besides, FreeBSD also has some technical differences which set it apart from Linux. Some of them are very important to know, even if you don't plan on joining the Gentoo/FreeBSD development effort:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):118
+msgid "To get run-time dynamic linking functions like <c>dlopen()</c>, programs do not need to be linked against libdl like on GNU/Linux. Instead they are linked against libc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):123
+msgid "FreeBSD doesn't have an official tool for kernel compilation, thus you'll have to resolve feature dependencies on your own."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):127
+msgid "FreeBSD uses UFS/UFS-2 as its filesystems and has no official support for e.g. ReiserFS or XFS. However, there are projects for adding read-only support for these filesystems. Accessing ext2/ext3 partitions is already possible, but you cannot install your system on them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):140
+msgid "Installing Gentoo/FreeBSD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):142
+msgid "Booting the CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):145
+msgid "After this short introduction, it's about time to finally install Gentoo/FreeBSD. Unfortunately, we currently lack our own installation media, so you have to choose between two alternative installation methods. The first would be to use an existing FreeBSD installation to partition your hard drive and use it as a base for installing Gentoo/FreeBSD. This guide will describe how to use the <uri link=\"http://www.freesbie.org/\">FreeSBIE LiveCD</uri> as an installation medium for Gentoo/FreeBSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):155
+msgid "If you are intending to use FreeSBIE for installing Gentoo/FreeBSD, please make sure to use a version based on FreeBSD 6.x, such as FreeSBIE 2.0 (or one of its release candidates). You can download it from <uri link=\"http://torrent.freesbie.org/\">FreeSBIE's Bittorrent tracker</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):162
+msgid "First, boot the CD in order to begin the installation process. You'll be presented with a login screen. The username is <c>freesbie</c>, and there is no password. Next, run <c>sudo su</c> to become root, and optionally setup a password. If you want to pass time during the installation process, you can run <c>startx</c> to enter into an Xfce environment, suitable for web browsing, AIM, and other things. Unlike Linux, FreeBSD bases the name of your interface on the driver for the interface. For example, the Intel EtherExpress driver (fxp) appears as fxp0 (driver fxp, first network card). To see what your interface is, use <c>ifconfig</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):174
+msgid "Finding out the network interface name using ifconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):174
+#, no-wrap
+msgid "\n# <i>ifconfig</i>\nfxp0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500\n        options=8&lt;VLAN_MTU&gt;\n        inet6 fe80::2d0::b7ff:febc:4fe3%fxp0 prefixlen 64 scopeid 0x1\n        inet 192.168.0.106 netmask 0xffffff00 broadcast 192.168.0.255\n        ether 00:d0:b7:bc:4f:e3\n        media: Ethernet autoselect (100baseTX &lt;full-duplex&gt;)\n        status: active\nlo0: flags=8007&lt;LOOPBACK,MULTICAST&gt; mtu 16384\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):186
+msgid "If the original DHCP request during the CD bootup failed, you can use the <c>dhclient</c> command to obtain an IP:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):191
+msgid "Obtaining a DHCP address using dhclient"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):191
+#, no-wrap
+msgid "\n# <i>dhclient fxp0</i>\nDHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 9\nDHCPOFFER from 192.168.0.1\nDHCPREQUEST on fxp0 to 255.255.255.255 port 67\nDHCPACK from 192.168.0.1\nbound to 192.168.0.106 -- renewal in 302400 seconds\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):200
+msgid "The output presented here will differ based on your network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):207
+msgid "Partitioning the Drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):210
+msgid "Now that we have a mount point, it's time to partition the drive. This is done with the <c>sysinstall</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):215
+msgid "Running the sysinstall command to fdisk the drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):215
+#, no-wrap
+msgid "\n# <i>sysinstall diskPartitionEditor diskPartitionWrite</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):219
+msgid "We recommend that you use the default layout. Press enter at the dialog, then press <b>a</b> followed by <b>q</b> to accept the default layout. The next screen will present you with the option of a bootloader. For this option, choose \"None\" as we'll be installing the bootloader later on. Next comes the actual partition sizing and mount points."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):227
+msgid "This next step also uses <c>sysinstall</c>, but with different arguments:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):231
+msgid "Running sysinstall to setup partition sizing and mount points"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):231
+#, no-wrap
+msgid "\n# <i>sysinstall diskLabelEditor diskLabelCommit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):235
+msgid "Here, we'll refrain from using the automatic layout, and create one giant root partition, followed by a swap partition. Hit <b>c</b> to create a new partition. A dialog prompts you to enter a size. Go ahead and do so, using MB/GB for setting different sizes, or C for cylinders. For root, choose FS as the partition type, and set the mount point as <path>/mnt/</path>. <e>If you do not adjust the mount point, it will overwrite the FreeSBIE environment!</e> As <path>/boot</path> is not a separate partition, you'll need to disable soft-updates, or your system will not boot! To do so, use the arrow keys to navigate to your newly created partition, then hit the <b>s</b> key, until \"Newfs\" contains no <b>+S</b>. Now navigate the arrow keys until the \"Disk\" line is highlighted, and hit <b>c</b> again to create a swap partition. Generally, we recommend a swap space that is twice the size of your RAM. Choose SWAP as the partition type, and don't worry about soft-updates, as it does not apply to swap. Now we're finished, so hit <b>q</b> to finish the process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):253
+msgid "When choosing a different mountpoint than <path>/</path> for your partition, <c>sysinstall</c> will actually create a 'd' slice, which the bootloader won't boot from. To fix this, run the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):259
+msgid "Please, make sure ad0s1 is unmounted before running the following command, otherwise it will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):264
+msgid "Fixing the root partition letter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):264
+#, no-wrap
+msgid "\n# <i>disklabel ad0s1 | sed 's/^  d:/  a:/' | disklabel -R ad0s1 /dev/stdin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):268
+msgid "This will finalize the partitioning process, and format the drive in UFS for FreeBSD to utilize. This will also mount the drive for you at the mount point specified earlier (<path>/mnt/</path>). You can verify this worked by running <c>mount</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):275
+msgid "Verifying the new disk layout was mounted with mount"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):275
+#, no-wrap
+msgid "\n# <i>mount</i>\n...\n/dev/ad0s1a on /mnt (ufs, local)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):281
+msgid "Now that you have mounted the target partition, it is time to start on the Gentoo setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):289
+msgid "Gentoo Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):292
+msgid "First, we need to download a stage3 tarball and unpack it into the chroot. Point your browser to <uri>http://distfiles.gentoo.org/experimental/x86/freebsd/stages/</uri>, grab the latest snapshot, and unpack it into the mountpoint:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):299
+msgid "Obtaining and unpacking a stage3 tarball"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):299
+#, no-wrap
+msgid "\n# <i>cd /mnt/</i>\n<comment>(Any other Gentoo mirror which includes the experimental/ directory will also work.)</comment>\n# <i>wget http://distfiles.gentoo.org/experimental/x86/freebsd/stages/stage3-x86-freebsd-6.2-r1.tar.bz2</i>\n# <i>tar -jxvpf stage3-x86-freebsd-6.2-r1.tar.bz2</i>\n<comment>(You can delete the tarball with the following command if you want to.)</comment>\n# <i>rm stage3-x86-freebsd-6.2-r1.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):308
+msgid "If you want you can use the transition overlay that contains semi-experimental ebuilds with patches not yet in the main Portage tree, but does allow a wider range of supported packages, please refer to the <uri link=\"/proj/en/gentoo-alt/contribute/index.xml?part=1&amp;chap=3\">Gentoo/ALT overlay documentation</uri>. Please note that the overlay is not critical and you can easily install and use Gentoo/FreeBSD without it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):317
+msgid "In order for your install to work, you need to mount the <path>/dev</path> filesystem from the currently running system into the Gentoo/FreeBSD mount point before proceeding with the chroot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):323
+msgid "Mounting the /dev filesystem and chrooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):323
+#, no-wrap
+msgid "\n# <i>mount -t devfs none /mnt/dev/</i>\n# <i>cp /etc/resolv.conf /mnt/etc/</i>\n# <i>chroot /mnt/ /bin/bash</i>\n# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):330
+msgid "After you obtain the Gentoo/FreeBSD overlay, it's time to link <path>/etc/make.profile</path> to the correct profile and get your <path>/etc/make.conf</path> ready for Gentoo/FreeBSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):336
+msgid "Now, you have to obtain a copy of the main Gentoo Portage tree, which depending on your connection might take quite a while."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):341
+msgid "Obtaining the Portage tree"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):341
+#, no-wrap
+msgid "\n# <i>emerge --sync</i>\n<comment>(It's also possible to retrieve the Portage tree in another way:)</comment>\n# <i>cd /</i>\n# <i>wget http://distfiles.gentoo.org/snapshots/portage-latest.tar.bz2</i>\n# <i>tar -xjf portage-latest.tar.bz2 -C /usr/</i>\n# <i>emerge --metadata</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):350
+msgid "Setting up the profile and editing /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):350
+#, no-wrap
+msgid "\n# <i>ln -sf /usr/portage/profiles/default-bsd/fbsd/6.2/x86/ /etc/make.profile</i>\n# <i>nano /etc/make.conf</i>\n<comment>(Please make sure you add at least the following entries:)</comment>\nCHOST=\"i686-gentoo-freebsd6.2\"\nFEATURES=\"collision-protect\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):358
+msgid "The <c>~x86-fbsd</c> keyword does not yet fully cover the same tree as <c>~x86</c>, but please <e>do not</e> put <c>~x86</c> in ACCEPT_KEYWORDS. Rather use <path>/etc/portage/package.keywords</path> to test packages, and report working packages on <uri link=\"http://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%2FAlt\">Bugzilla</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):366
+msgid "If you want, you can now rebuild the system's core packages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):370
+msgid "Rebuilding the FreeBSD core packages (optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):370
+#, no-wrap
+msgid "\n# <i>emerge -e system</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):378
+msgid "Setting up for Booting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):380
+msgid "Set your time zone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):383
+msgid "First make sure your date and time is set correctly using <c>date yyyymmddHHMM</c>. Use UTC time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):388
+msgid "Set the date and UTC time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):388
+#, no-wrap
+msgid "\n<comment>(Check the clock)</comment>\n# <i>date</i>\nMon Mar  6 00:14:13 UTC 2006\n\n<comment>(Set the current date and time if required)</comment>\n# <i>date 200603060016</i> <comment>(Format is yyyymmddHHMM)</comment>\nMon Mar  6 00:16:00 UTC 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):398
+msgid "Next, set your time zone information by using the correct listing in <path>/usr/share/zoneinfo</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):403
+msgid "Setting your timezone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):403
+#, no-wrap
+msgid "\n# <i>ls /usr/share/zoneinfo</i>\n<comment>(Using Brussels as an example)</comment>\n# <i>cp /usr/share/zoneinfo/Europe/Brussels /etc/localtime</i>\n\n# <i>date</i>\nWed Mar  8 00:46:05 CET 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):412
+msgid "Edit <path>/etc/conf.d/clock</path> to define the time zone you used previously."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):417
+msgid "Edit /etc/conf.d/clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):417
+#, no-wrap
+msgid "\n# <i>nano -w /etc/conf.d/clock</i>\nTIMEZONE=\"Europe/Brussels\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):425
+msgid "Kernel Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):428
+msgid "If you ran <c>emerge -e system</c>, the sources for the FreeBSD kernel were installed to <path>/usr/src/sys</path>. If you skipped this step, you can get them in the following way:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):434
+msgid "Getting the FreeBSD kernel sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):434
+#, no-wrap
+msgid "\n# <i>emerge freebsd-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):438
+msgid "Configuring and compiling a custom kernel is quite different from compiling Linux, so if you are not familiar with the process we encourage you to have a look at <uri link=\"http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html\"> chapter 8</uri> of the FreeBSD handbook. For now, you can do an installation of the GENERIC kernel, which works on most systems. To begin, enter the source directory for the kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(impo):448
+msgid "Please note that currently only the \"Traditional\" way of building the kernel is supported on Gentoo/FreeBSD!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):453
+msgid "Entering the kernel source directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):453
+#, no-wrap
+msgid "\n# <i>cd /usr/src/sys/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):457
+msgid "Looking over the layout, you'll see various architectures and subdirectories for various parts of the kernel. To begin the installation, we head into the <path>i386/conf/</path> directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):463
+msgid "The kernel configuration directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):463
+#, no-wrap
+msgid "\n# <i>cd i386/conf/</i>\n# <i>ls</i>\n.cvsignore      GENERIC         Makefile        PAE\nDEFAULTS        GENERIC.hints   NOTES           SMP\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):470
+msgid "The main files to note are <path>GENERIC</path> and <path>GENERIC.hints</path>. As it will be needed by the installation of the kernel, go ahead and copy <path>GENERIC.hints</path> file to <path>/boot/device.hints</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):476
+msgid "Copying over the GENERIC.hints file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):476
+#, no-wrap
+msgid "\n# <i>cp GENERIC.hints /boot/device.hints</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):480
+msgid "This file is used by the kernel drivers for basic configuration information such as IRQ settings. Now it's time to configure the kernel. FreeBSD uses the <c>config</c> command to do this. <c>config</c> uses the given file (in this instance GENERIC) to copy over the required build files to a <path>compile</path> directory in the parent directory. <path>GENERIC</path> is similiar to the <path>.config</path> file for the Linux kernel. Run <c>config</c> to produce the build directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):490
+msgid "Configuring the kernel build"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):490
+#, no-wrap
+msgid "\n# <i>config GENERIC</i>\nKernel build directory is ../compile/GENERIC\nDon't forget to ''make cleandepend; make depend''\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):496
+msgid "<c>config</c> has created a GENERIC build directory for us in the parent directory. <c>cd</c> into it, then run the following to do a complete build:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):501
+msgid "Building and installing the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):501
+#, no-wrap
+msgid "\n# <i>cd ../compile/GENERIC</i>\n# <i>make cleandepend &amp;&amp; make depend &amp;&amp; make &amp;&amp; make install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):506
+msgid "This will give us a complete kernel to work with. Now we'll need to setup the bootloader for the kernel to boot. The next chapter will discuss two methods of setting up the bootloader: <c>boot0</c> and <c>grub</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):515
+msgid "Setting up the bootloader (boot0)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(impo):518
+msgid "<c>boot0</c> is the FreeBSD bootloader. Previously, it was the only supported bootloader until <c>grub</c> was introduced into ports with UFS slice support. To install and configure <c>boot0</c>, run the following. Remember to replace <c>adXsY</c> with the actual number and slice of your disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):525
+msgid "Installing and setting up boot0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):525
+#, no-wrap
+msgid "\n# <i>emerge boot0</i>\n<comment>(Leave the chroot environment)</comment>\n# <i>exit</i>\n<comment>(Issued from outside the chroot)</comment>\n# <i>fdisk -B -b /mnt/boot/boot0 /dev/adX</i>\n# <i>chroot /mnt/ /bin/bash</i>\n# <i>disklabel -B adXsY</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):535
+msgid "If you need additional information on setting up <c>boot0</c>, please consult <uri link=\"http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot.html\">chapter 12</uri> of the FreeBSD handbook. Now it's time to do some basic system configuration and settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):543
+msgid "The next section will look at using the alternative bootloader, <c>grub</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):550
+msgid "Setting up the bootloader (grub)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):553
+msgid "As of grub 0.97-r1, UFS slices are readable to <c>grub</c>. This lets us use <c>grub</c> as a bootloader, the prefered method for those coming from a Linux background. To begin, emerge <c>grub</c> and setup the label as bootable. Remember to replace <c>adXsY</c> with the actual number and slice of your disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):560
+msgid "Emerge grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):560
+#, no-wrap
+msgid "\n# <i>emerge grub</i>\n# <i>disklabel -B adXsY</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):565
+msgid "Now run <c>grub</c> to bring up the command prompt, and set up the partition as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):570
+msgid "Setting up grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):570
+#, no-wrap
+msgid "\n<comment>(This is done to prevent disk error 29)</comment>\n# <i>sysctl kern.geom.debugflags=16</i>\n# <i>grub</i>\n<comment>(Example using ad0s1d)</comment>\ngrub&gt; <i>root (hd0,0,d)</i>\n Filesystem type is ufs2, partition type 0xa5\n\ngrub&gt; <i>setup (hd0)</i>\n Checking if \"/boot/grub/stage1\" exists... yes\n Checking if \"/boot/grub/stage2\" exists... yes\n Checking if \"/boot/grub/ufs2_stage1_5\" exists... yes\n Running \"embed /boot/grub/ufs2_stage1_5 (hd0)\"... 14 sectors are embedded.\nsucceeded\n Running \"install /boot/grub/stage1 (hd0) (hd0)1+14 p (hd0,0,d)/boot/grub/stage\n2 /boot/grub/menu.lst\"... succeeded\nDone.\n\ngrub&gt; quit\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):591
+msgid "To make the loader find the kernel on a specific slice (the default is 'a'), add a <c>vfs.root.mountfrom</c> line to the <path>/boot/loader.conf</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):597
+msgid "Tell the loader where to look for the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):597
+#, no-wrap
+msgid "\n# <i>echo 'vfs.root.mountfrom=\"ufs:ad0s1d\"' &gt;&gt; /boot/loader.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):601
+msgid "When you first boot, you may not receive a grub menu. If so, run this at the prompt:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):606
+msgid "Booting the kernel with no menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):606
+#, no-wrap
+msgid "\ngrub&gt; <i>find /boot/grub/stage1</i>\n<comment>(The output here is what you'll use in the next command)</comment>\n (hd0,0,d)\n\ngrub&gt; <i>kernel (hd0,0,d)/boot/loader</i>\n  [FreeBSD-a.out, loadaddr=0x200000, text=0x1000, data=0x3a000, bss=0x0, entry=0x200000]\n\ngrub&gt; <i>boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):617
+msgid "For more information on configuring grub, please refer to the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=10#doc_chap2\">Gentoo Linux Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(warn):623
+msgid "Grub doesn't follow UFS symlinks so be sure to delete the <path>/boot/grub/menu.lst</path> symlink and to use <path>menu.lst</path> to setup Grub (<path>grub.conf</path> isn't used)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):632
+msgid "System configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):635
+msgid "First, we are going to setup the filesystem mounting points in <path>/etc/fstab</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):640
+msgid "Editing the filesystem in /etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):640
+#, no-wrap
+msgid "\n# <i>nano /etc/fstab</i>\n<comment>(This is an example, replace X and Y with the correct numbers for your hard disk.)</comment>\n#Device         Mountpoint      Fstype          Options         Dump    Pass\n/dev/adXsYb     none            swap            sw              0       0\n/dev/adXsYa     /               ufs             rw              1       1\n/dev/adXsYe     /usr/home       ufs             rw              2       2\n/dev/adXsYd     /tmp            ufs             rw              2       2\n/dev/acdX       /cdrom          cd9660          ro,noauto       0       0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):651
+msgid "Now would also be a good time to set up your network connection before the final reboot. You can find all the information necessary to configure your network in the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=4&amp;chap=1\">Gentoo Handbook</uri>. To have your network interface activated at boot time, you have to add it to the default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):659
+msgid "Adding your network adapter to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):659
+#, no-wrap
+msgid "\n# <i>rc-update add net.fxp0 default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):663
+msgid "Your system's hostname can be changed in <path>/etc/conf.d/hostname</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):667
+msgid "Setting up the machine's hostname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):667
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/hostname</i>\n<comment>(Set the HOSTNAME variable to your hostname)</comment>\nHOSTNAME=\"tux\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):673
+msgid "You should also configure your domain name, which is done in the <path>/etc/conf.d/domainname</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):678
+msgid "Setting the domainname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):678
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/domainname</i>\n<comment>(Set the dns_domain variable to your domain name, and lo to your local\nnetwork interface)</comment>\ndns_domain_lo=\"homenetwork\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):685
+msgid "If you have a NIS domain, you need to define it in the <path>/etc/conf.d/domainname</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):690
+msgid "Setting the NIS domainname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):690
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/domainname</i>\n<comment>(Set the nis_domain variable to your NIS domain name, and lo to your local network interface)</comment>\nnis_domain_lo=\"my-nisdomain\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):696
+msgid "For more information on domainnames and networking, please refer to the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=8#doc_chap2\">Gentoo Linux Handbook</uri>, and please read the documentation in <path>/etc/conf.d/net.example</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):703
+msgid "In case you need to use another keyboard layout for your language, you have to set the correct value in <path>/etc/conf.d/syscons</path>. The following example uses the Spanish layout, so you'll have to adjust it to your need if you want to use another one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):710
+msgid "Changing your keyboard layout (Optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):710
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/syscons</i>\nKEYMAP=\"spanish.iso.acc\"\n<comment>(Possible layouts can be found in /usr/share/syscons/keymaps).</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):716
+msgid "Now would be a good time to set a password for the <c>root</c> user and to add another user account for your day-to-day work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):721
+msgid "Changing the root password and adding a new user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):721
+#, no-wrap
+msgid "\n# <i>passwd</i>\n# <i>adduser</i>\nUsername: <i>fred</i>\nFull Name: <i>Fred Smith</i>\n<comment>(Accepting the default here, just hit Enter.)</comment>\nUid (Leave empty for default):\n<comment>(OK to accept the default here as well; hit Enter.)</comment>\nLogin group [fred]:\n<comment>(Enter your groups here, space separated. They must exist.)</comment>\nLogin group is fred. Invite fred into other groups? []: wheel portage\n<comment>(OK to accept the default here, hit Enter)</comment>\nLogin class [default]:\n<comment>(Somewhat of a personal preference.  Make sure the shell exists in /etc/shells)</comment>\nShell (sh bash tcsh csh esh ksh zsh sash nologin) [sh] <i>bash</i>\n<comment>(OK to accept the default here, hit Enter for all these)</comment>\nUser password-based authentication [yes]\nUse an empty password (yes/no) [no]:\nUse a random password? (yes/no) [no]:\nEnter password: <i>password goes here</i>\nEnter password again: <i>retype it</i>\n<comment>(OK to accept the default here, hit Enter)</comment>\nLock out the account after creation? [no]:\nUsername    : fred\nPassword    : *****\nFull Name   : Fred Smith\n<comment>(This will vary)</comment>\nUid         : 1002\nClass       :\nGroups      : fred wheel portage\nHome        : /home/fred\nShell       : /bin/bash\nLocked      : no\n<comment>(Confirm the information is correct)</comment>\nOK? (yes/no): <i>yes</i>\nadduser: INFO: Sucessfully added (fred) to the user database\nAdd another user? (yes/no): <i>no</i>\nGoodbye!\n#\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):762
+msgid "Congratulations, you have just finished your Gentoo/FreeBSD installation which you can start exploring after the final reboot. Have fun!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):767
+msgid "Rebooting the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):767
+#, no-wrap
+msgid "\n# <i>exit</i>\n# <i>reboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):777
+msgid "Developing for Gentoo/FreeBSD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):779
+msgid "How to help"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):782
+msgid "There are many things you could help with, depending on your skill level and spare time:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):788
+msgid "Working on current ebuilds: this means working closely with ebuild maintainers in order to create patches or modify ebuilds in a way that can be accepted into the main tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):793
+msgid "Security: if you are into security, we need you! Although security advisories from the FreeBSD project are tracked and fixed, we can always use help in this area."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):798
+msgid "Contacts: we need people who can get in touch with FreeBSD developers to maintain contacts between us and the original project to exchange patches and discuss various problems and their solutions. Note that this should never involve any kind of spamming of mailing lists or IRC channels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):804
+msgid "Testing: the more people are actively using Gentoo/FreeBSD, the more bugs will be discovered, which helps us improving the quality of the port. If you are good at describing bugs or problems, we definitely want to hear from you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):810
+msgid "Other areas where we need help include: system ebuilds, creation of installation CDs, documentation, kernel hacking."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):820
+msgid "Known issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):823
+msgid "At the moment, there are still quite a lot of known issues. Here are the ones really worth noting:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):829
+msgid "Some init scripts depend on the clock service which we don't provide right now. You can just remove it from the dependencies of the script and report that on our <uri link=\"http://bugs.gentoo.org/\">Bugzilla</uri>. Please remember to use the \"Gentoo/Alt\" product for your submission."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):842
+msgid "Contact"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):846
+msgid "A list of Gentoo/FreeBSD developers can be found at the <uri link=\"/proj/en/gentoo-alt/bsd/fbsd/\">project page</uri>. Other ways to contact Gentoo/FreeBSD developers include our IRC Channel <c>#gentoo-bsd</c> on Freenode, as well as the <uri link=\"/main/en/lists.xml\">gentoo-bsd mailing list</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-hppa-install.xml.pot b/doc/gettext/gentoo-hppa-install.xml.pot
new file mode 100644
index 0000000..9601462
--- /dev/null
+++ b/doc/gettext/gentoo-hppa-install.xml.pot
@@ -0,0 +1,52 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(guide:redirect):3
+msgid "/doc/en/handbook/handbook-hppa.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(title):4 ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(title):20
+msgid "Gentoo HPPA Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(author:title):6
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(mail:link):7
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(mail):7
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(abstract):10
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(version):16
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(date):17
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(p):24
+msgid "As of 2004.0, the individual architecture-specific installation guides have been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/handbook/handbook-hppa.xml\">Gentoo Handbook</uri>. For more information please read up on the <uri link=\"/doc/en/handbook\">Gentoo Handbook Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-kernel.xml.pot b/doc/gettext/gentoo-kernel.xml.pot
new file mode 100644
index 0000000..cc22b73
--- /dev/null
+++ b/doc/gettext/gentoo-kernel.xml.pot
@@ -0,0 +1,400 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):6
+msgid "Gentoo Linux Kernel Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):11
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):12
+msgid "lostlogic@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):12
+msgid "Brandon Low"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):20 ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):23 ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):26 ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):29 ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):32
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):15
+msgid "dsd@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):15
+msgid "Daniel Drake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):18
+msgid "carl@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):18
+msgid "Carl Anderson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):21
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):21
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):24
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):24
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):27
+msgid "greg_g@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):27
+msgid "Gregorio Guidi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):30
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):30
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):33
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):33
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(abstract):36
+msgid "This document gives you an overview on all kernel sources that Gentoo provides through Portage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(version):45
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(date):46
+msgid "2010-09-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):49
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):53
+msgid "As with everything else in Gentoo Linux, the philosophy of the Gentoo Kernel team is to give you, the user, as much freedom of choice as possible. If you take a look at the output of <c>emerge -s sources</c> you see a large variety of kernels to choose from. In this document, I will attempt to give you a brief rundown of the goals of each of the patch sets, which we at Gentoo design, and also explain the other kernel sources we make available to you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):63
+msgid "Linux 2.4 is maintained by Willy Tarreau. Linus Torvalds, the original creator of Linux, handed maintainership of the Linux 2.4 branch over to Marcelo Tosatti when Linus went off to start developing the newer 2.6 kernel tree. Marcelo did a fine job of keeping 2.4 stable and secure, and has since handed over maintainership to Willy. Note that only security and bug fixes are accepted into the 2.4 kernel tree. Actual development happens in the Linux 2.6 kernel tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):72
+msgid "Linux 2.6 is maintained by Andrew Morton, who works closely with Linus Torvalds to deliver a fast, powerful, and feature-packed Linux kernel. Development is happening at incredible pace and this kernel tree is now very mature."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):79
+msgid "Some of the more uncommon system architectures are not fully compatible with Linux 2.6, and some users prefer the tried-and-tested Linux 2.4 kernel. However, please note that Linux 2.4 is currently not being developed further - only bug and security fixes are being included in the newer releases. If you are able to, we suggest that you upgrade to Linux 2.6. You may find the <uri link=\"/doc/en/migration-to-2.6.xml\">migration document</uri> useful."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):93
+msgid "Supported kernel packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):95
+msgid "genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):98
+msgid "<c>Genkernel</c> is a kernel toolset that can be used to autodetect your hardware and configure your kernel automatically. This is usually recommended for users who do not feel comfortable about compiling a kernel manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):104
+msgid "For more information, please read the <uri link=\"/doc/en/genkernel.xml\">Gentoo Linux Genkernel Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):112
+msgid "General purpose: gentoo-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):115
+msgid "For most users, we recommend the <c>gentoo-sources</c> kernel. <c>gentoo-sources</c> is a kernel based on Linux 2.6, lightly patched to fix security problems, kernel bugs, and to increase compatibility with the more uncommon system architectures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):122
+msgid "The <c>gentoo-sources</c> package absorbs most of the resources of the Gentoo kernel team. They are brought to you by a group of talented developers, which can count on the expertise of popular kernel hacker Greg Kroah-Hartman, maintainer of udev and responsible for the USB and PCI subsystems of the official Linux kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):133
+msgid "For servers: hardened-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):136
+msgid "<c>hardened-sources</c> is based on the official Linux kernel and is targeted at our users running Gentoo on server systems. It provides patches for the various subprojects of Gentoo Hardened (such as support for <uri link=\"http://www.nsa.gov/selinux/\">LSM/SELinux</uri> and <uri link=\"http://grsecurity.net\">grsecurity</uri>), together with stability/security-enhancements. Check <uri>http://www.gentoo.org/proj/en/hardened/</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(impo):146
+msgid "This kernel provides powerful patches for enhanced security. Please read the <uri link=\"/proj/en/hardened/\">documentation</uri> before you use it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):154
+msgid "ck-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):157
+msgid "<c>ck-sources</c> is Con Kolivas's kernel patch set. This patchset is primarily designed to improve system responsiveness and interactivity and is configurable for varying workloads (from servers to desktops). The patchset includes a different scheduler, BFS, designed to keep systems responsive and smooth even when under heavy load. Support and information is available at <uri>http://kernel.kolivas.org</uri> and in <c>#ck</c> on <c>irc.oftc.net</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):169
+msgid "git-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):172
+msgid "The <c>git-sources</c> package tracks daily snapshots of the upstream development kernel tree. You should run these kernels if you are interested in kernel development or testing. Bugreports should go to the <uri link=\"http://bugzilla.kernel.org/\">Linux Kernel Bug Tracker</uri> or LKML (Linux Kernel Mailing List)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):183
+msgid "xen-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):186
+msgid "<c>xen-sources</c> lets you run multiple operating systems on a single physical system. You can create virtual environments in which one or more guest operating systems run on a <uri link=\"http://www.xensource.com\">Xen</uri>-powered host operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):193
+msgid "For more information on Xen and Gentoo, read the <uri link=\"/doc/en/xen-guide.xml\">Gentoo Xen Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):201
+msgid "Architecture dependent kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):204
+msgid "<c>cell-sources</c>, <c>mips-sources</c>, <c>sparc-sources</c>, and <c>xbox-sources</c> are, as their names suggest, patched to run best on specific architectures. They also contain some of the patches for hardware and features support from the other patch sets mentioned above and below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):216
+msgid "Unsupported kernel packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):220
+msgid "Now I'm going to try to briefly describe some of the other <path>sys-kernel/*-sources</path> which you saw scroll by when you ran <c>emerge -s sources</c>. Let's take them in alphabetical order. These kernels are provided as a courtesy only and the various patch sets are not supported by the Gentoo kernel team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):232
+msgid "mm-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):235
+msgid "The <c>mm-sources</c> are based on the <c>vanilla-sources</c> and contain Andrew Morton's patch set. They include the experimental and bleeding-edge features that are going to be included in the official kernel (or that are going to be rejected because they set your box on fire). They are known to be always moving at a fast pace and can change radically from one week to the other; kernel hackers use them as a testing ground for new stuff."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):244
+msgid "If you really want to live on the edge and you think <c>vanilla-sources</c> are for wussies, then try out <c>mm-sources</c>. Be warned that this kernel is highly experimental and doesn't always work as expected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):254
+msgid "pf-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):257
+msgid "The <c>pf-sources</c> kernel brings together parts of several different kernel patches. It includes the BFS patchset from <c>ck-sources</c>, the <c>tuxonice</c> patches, <uri link=\"http://www.linuximq.net\">LinuxIMQ</uri>, and the <uri link=\"http://algo.ing.unimo.it/people/paolo/disk_sched/patches/\">BFQ</uri> I/O <uri link=\"http://kerneltrap.org/Linux/Budget_Fair_Queuing_IO_Scheduler\">scheduler</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):270
+msgid "openvz-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):273
+msgid "OpenVZ is a server virtualization solution built on Linux. OpenVZ creates isolated, secure virtual private servers (VPSs) or virtual environments on a single physical server enabling better server utilization and ensuring that applications do not conflict. For more information, see <uri>http://www.openvz.org</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):284
+msgid "tuxonice-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):287
+msgid "The <c>tuxonice-sources</c> (formerly <c>suspend2-sources</c>) are patched with both genpatches which includes the patches found in gentoo-sources, and <uri link=\"http://www.tuxonice.net\">TuxOnIce</uri> which is an improved implementation of suspend-to-disk for the Linux kernel, formerly known as <e>suspend2</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):295
+msgid "This kernel is recommended for laptop users who often rely on being able to suspend their laptop and resume work elsewhere."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):303
+msgid "usermode-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):306
+msgid "<c>usermode-sources</c> are the User Mode Linux kernel patches. This kernel is designed to allow Linux to run within Linux to run within Linux to ... User Mode Linux is intended for testing and virtual server support. For more information about this amazing tribute to the stability and scalability of Linux, see <uri>http://user-mode-linux.sourceforge.net</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):314
+msgid "For more information on UML and Gentoo, read the <uri link=\"/doc/en/uml.xml\">Gentoo UML Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):322
+msgid "vanilla-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):325
+msgid "The next kernel sources that many of you will probably be familiar with as Linux users are the <c>vanilla-sources</c>. These are the official kernel sources released on <uri>http://www.kernel.org/</uri>. Please note that we do not patch these kernels at all - these are purely for people who wish to run a completely unmodified Linux kernel. We recommend that you use <c>gentoo-sources</c> instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):334
+msgid "Two versions of the kernel can be found under this package: 2.4 and 2.6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):341
+msgid "zen-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):344
+msgid "<c>zen-sources</c> is designed for desktop systems. It includes code not found in the mainline kernel. The zen kernel has patches that add new features, support additional hardware, and contain various tweaks for desktops."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):355
+msgid "Previously provided kernel packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):357
+msgid "aa-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):360
+msgid "<c>aa-sources</c> was a heavily modified kernel with all kinds of patches. The upstream maintainer has stopped releasing kernel patchsets, this package was removed as it went out of date."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):369
+msgid "alpha-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):372
+msgid "<c>alpha-sources</c> was a 2.4 kernel with patches applied to improve hardware compatibility for the Alpha architecture. These patches have been developed and included in the mainline kernel. Alpha users can now run any recent kernel with no need for extra patches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):382
+msgid "development-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):385
+msgid "<c>development-sources</c>, the official 2.6 kernel from kernel.org, can now be found under the <c>vanilla-sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):393
+msgid "gentoo-dev-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):396
+msgid "<c>gentoo-dev-sources</c>, a 2.6 kernel patched with bug, security and stability fixes, can now be found under the <c>gentoo-sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):404
+msgid "grsec-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):407
+msgid "The <c>grsec-sources</c> kernel source used to be patched with the latest grsecurity updates (grsecurity version 2.0 and up) which included, amongst other security-related patches, support for PaX. As grsecurity patches are included in <c>hardened-sources</c>, this package is no longer in Portage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):417
+msgid "hardened-dev-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):420
+msgid "<c>hardened-dev-sources</c> can now be found under the <c>hardened-sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):428
+msgid "hppa-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):431
+msgid "<c>hppa-sources</c> was a 2.6 kernel with patches applied to improve hardware compatibility for the HPPA architecture. These patches have been developed and included in the mainline kernel. HPPA users can now run any recent kernel with no need for extra patches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):441
+msgid "rsbac-dev-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):444
+msgid "The <c>rsbac-dev-sources</c> kernels can now be found under the <c>rsbac-sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):452
+msgid "rsbac-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):455
+msgid "<c>rsbac-sources</c> was a 2.6-based kernel. It contained patches to use Rule Set Based Access Controls (<uri link=\"http://www.rsbac.org\">RSBAC</uri>). It has been removed due to lack of maintainers. Use <c>hardened-sources</c> if you need additional security features."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):465
+msgid "selinux-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):468
+msgid "<c>selinux-sources</c>, a 2.4 kernel including lots of security enhancements, has been obsoleted by security development in the 2.6 tree. SELinux functionality can be found in the <c>hardened-sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):477
+msgid "sh-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):480
+msgid "<c>sh-sources</c> was a 2.6 kernel with patches applied to improve hardware compatibility for the SuperH architecture. These patches have been developed and included in the mainline kernel. SuperH users can now run any recent kernel with no need for extra patches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):490
+msgid "uclinux-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):493
+msgid "The <c>uclinux-sources</c> are meant for CPUs without MMUs as well as embedded devices. For more information, see <uri>http://www.uclinux.org</uri>. Lack of security patches as well as hardware to test on were the reasons this is no longer in the tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):503
+msgid "win4lin-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):506
+msgid "<c>win4lin-sources</c> were patched to support the userland win4lin tools that allow Linux users to run many Microsoft Windows (TM) applications at almost native speeds. This was removed due to security issues."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-mips-faq.xml.pot b/doc/gettext/gentoo-mips-faq.xml.pot
new file mode 100644
index 0000000..7420bb5
--- /dev/null
+++ b/doc/gettext/gentoo-mips-faq.xml.pot
@@ -0,0 +1,525 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(guide:link):5
+msgid "/doc/en/gentoo-mips-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):7
+msgid "Gentoo Linux/MIPS Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(mail:link):10
+msgid "redhatter@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(mail):10
+msgid "Stuart Longland"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(abstract):13
+msgid "This FAQ is intended to answer some of the most frequently asked questions relating to Gentoo/MIPS and Linux/MIPS in general."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(version):22
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(date):23
+msgid "2005-09-08"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):26
+msgid "About this document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):31
+msgid "This FAQ is intended to answer frequently asked questions about Gentoo/MIPS and Linux/MIPS that we receive from various users. It's aimed at both new users and experienced users alike. It has been split into a number of categories to make navigation easier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):38
+msgid "If you have anything to contribute to the FAQ or, having read this guide, you still have questions that are left unanswered, feel free to <uri link=\"http://mips.gentoo.org\">drop us a line</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):49
+msgid "About the Gentoo/MIPS Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):51
+msgid "What is Gentoo/MIPS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):54
+msgid "Gentoo/MIPS is a small project within the Gentoo Foundation, responsible for looking after the MIPS port of Gentoo Linux. We currently look after two main sub architectures of the MIPS family specifically: Silicon Graphics systems and MIPS-based Cobalt servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):64
+msgid "Why install Gentoo Linux on MIPS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):67
+msgid "Okay, sure, some MIPS machines aren't the fastest boxes on the block these days. However, despite the age of some of these beasts, they still can make very functional, useful machines. A Cobalt Qube 2 could make a very nice broadband Internet router, capable of hosting websites, email, IRC and numerous other tasks. There are a number of reasons why you'd want to install Linux on this sort of hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):77
+msgid "It teaches you a lot about computer hardware by giving you an alternate frame of reference"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):81
+msgid "It allows you to turn what would otherwise be useless junk into a very functional system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):85
+msgid "Status Symbol: Linux on x86 is so common these days it's not funny. However, Linux on MIPS is a lot less common and quite a talking point."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):94
+msgid "Why don't you port Gentoo to NetBSD/MIPS or IRIX?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):97
+msgid "Hey, great idea. Unfortunately, a lot of the Gentoo/MIPS team already have their hands full looking after Linux/MIPS as well as other commitments. However, you're welcome to give it a try. May I suggest raising this on the <uri link=\"http://forums.gentoo.org/viewforum-f-32.html\">Gentoo Forums</uri> and see what the interest is first. Also, have a look at some of the other threads on porting Gentoo to other architectures such as <uri link=\"http://forums.gentoo.org/viewtopic-t-113387.html\">Solaris/SPARC</uri>, <uri link=\"http://forums.gentoo.org/viewtopic-t-319607.html\">IBM OS/2</uri> and <uri link=\"http://forums.gentoo.org/viewtopic-t-319691.html\">Microsoft Services For Unix</uri> for hints on how to proceed. If after some hacking you get something useful out of it... chances are a few developers will pick up on this and help you get it to the next stage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):117
+msgid "MIPS Hardware FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):119
+msgid "What is MIPS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):122
+msgid "<uri link=\"http://www.mips.com\">MIPS Technologies</uri> is a company that produce a number of RISC CPU cores which implement the MIPS Instruction Set Architecture. These processors appear in all sorts of hardware ranging from small embedded devices to large servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):129
+msgid "It also happens to be an acronym; <b>M</b>illions of <b>I</b>nstructions <b>P</b>er <b>S</b>econd."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):137
+msgid "What sort of hardware uses MIPS processors?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):140
+msgid "Good question. In short... Heaps. MIPS Processors see use inside all sorts of machines, ranging from small PDAs (such as the early Windows CE powered Casio PDAs), X Terminals (e.g. Tektronix TekXPress XP330 series), through to workstations such as the Silicon Graphics Indy and O2 and even high end servers such as the Silicon Graphics Origin 2000."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):148
+msgid "Here is a list of some of the more famous MIPS-based systems in use. A more comprehensive list can be found on the <uri link=\"http://www.linux-mips.org/wiki/index.php/Systems\">Linux/MIPS website</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):156
+msgid "Sony Game Consoles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):158
+msgid "http://www.linux-mips.org/wiki/index.php/PS1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):158
+msgid "PlayStation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):160
+msgid "http://www.linux-mips.org/wiki/index.php/PS2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):160
+msgid "PlayStation 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):162
+msgid "http://www.linux-mips.org/wiki/index.php/PSP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):162
+msgid "PlayStation Pocket"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):167
+msgid "Nintendo Game Consoles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):169
+msgid "http://www.linux-mips.org/wiki/index.php/Nintendo_64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):169
+msgid "Nintendo 64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):175
+msgid "Silicon Graphics Machines"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):177
+msgid "http://www.linux-mips.org/wiki/index.php/IP12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):177
+msgid "Iris Indigo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):179 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):181
+msgid "http://www.linux-mips.org/wiki/index.php/IP19"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):179
+msgid "Challenge"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):181
+msgid "Onyx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):183 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):185 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):187
+msgid "http://www.linux-mips.org/wiki/index.php/IP22"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):183
+msgid "Indy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):185
+msgid "Indigo 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):187
+msgid "Challenge S"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):189 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):191 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):193
+msgid "http://www.linux-mips.org/wiki/index.php/IP27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):189
+msgid "Origin 200"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):191
+msgid "Origin 2000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):193
+msgid "Onyx 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):195 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):197
+msgid "http://www.linux-mips.org/wiki/index.php/IP30"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):195
+msgid "Octane"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):197
+msgid "Octane 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):199
+msgid "http://www.linux-mips.org/wiki/index.php/IP32"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):199
+msgid "O2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):201
+msgid "http://www.linux-mips.org/wiki/index.php/IP34"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):201
+msgid "Fuel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):203
+msgid "http://www.linux-mips.org/wiki/index.php/IP35"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):203
+msgid "Origin 3000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):205
+msgid "http://www.linux-mips.org/wiki/index.php/IP45"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):205
+msgid "Origin 300"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):207 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):209
+msgid "http://www.linux-mips.org/wiki/index.php/IP53"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):207
+msgid "Origin 350"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):209
+msgid "Tezro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):214
+msgid "DECStations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):216
+msgid "http://www.linux-mips.org/wiki/index.php/Deskstation_rPC44"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):216
+msgid "rPC44"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):218
+msgid "http://www.linux-mips.org/wiki/index.php/Deskstation_Tyne"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):218
+msgid "Tyne"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):223
+msgid "Cobalt Microservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):225 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):227 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):229 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):231
+msgid "http://www.linux-mips.org/wiki/index.php/Cobalt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):225
+msgid "Qube 2700"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):227
+msgid "Qube 2800"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):229
+msgid "RaQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):231
+msgid "RaQ 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):236
+msgid "Broadcom-based 802.11g<br/> Broadband Internet Routers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):241
+msgid "http://openwrt.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):241
+msgid "Linksys WRT54G"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):246
+msgid "... and that's only just scratching the surface. These machines are wide and varied. Many of them do not currently run Linux. Of those that do, we only support a handful, although you're welcome to port Gentoo/MIPS to any MIPS machine if you so wish. Some of these machines are also the focus of the <uri link=\"http://embedded.gentoo.org\">Embedded Gentoo Project</uri> such as the Linksys WRT54G."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):258
+msgid "Is my machine supported?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):261
+msgid "This question is difficult to answer. Your machine could fall into one of three different baskets:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):267
+msgid "Your machine is supported by Gentoo/MIPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):268
+msgid "Your machine is supported by Linux/MIPS, but not by Gentoo/MIPS (yet)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):269
+msgid "Your machine is not supported by Linux/MIPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):272
+msgid "For the first one an easy way to find out is to have a look at the <uri link=\"/doc/en/mips-requirements.xml\">Gentoo/MIPS requirements page</uri>. This will tell you if the system you've got can theoretically run Gentoo/MIPS. Stuart has also written a <uri link=\"http://stuartl.longlandclan.hopto.org/gentoo/mips/\">hardware support database</uri> in which users may contribute their experiences. This can help measure how well Gentoo/MIPS runs on a particular machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):282
+msgid "If you don't find your machine listed there, you may wish to have a look on the <uri link=\"http://www.linux-mips.org/wiki/index.php/Systems\">Linux/MIPS website</uri> to find it there. Installation won't be straightforward however, as the actual process of producing a kernel and suitable boot media for your hardware will have to be done largely by yourself. Naturally though, we'll try to help where we can."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):294
+msgid "Why don't you support machine X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):297
+msgid "If you've looked at the Gentoo/MIPS Hardware Requirements page, you've probably noticed there are a LOT of machines we don't support. In the case of SGI hardware, very little is known about some of them, not enough to successfully port Linux to them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):304
+msgid "If you managed to get Linux working on a box currently listed as <e>unsupported</e> however, feel free to tell us. We'd be interested to know."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):314
+msgid "MIPS Software FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):316
+msgid "Which stage tarball do I use?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):319
+msgid "This will depend on the CPU type running in your system. The stage filename is named as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(pre:caption):324
+msgid "Stage Tarball Naming Scheme"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(pre):324
+#, no-wrap
+msgid "\n  stage3-mipsel4-2005.0.tar.bz2\n  \\____/ \\_____/ \\____/\n     |      |       |\n     |      |       `--- Gentoo Release (e.g. 1.4, 2004.3, 2005.0)\n     |      |\n     |      `----------- Endianness and ISA Level\n     |                     mips   ==&gt; Big Endian\n     |                     mipsel ==&gt; Little Endian\n     |\n     |                     R3xxx and earlier: ISA Level 1\n     |                     R4xxx series:      ISA Level 3\n     |                     R5000 and above:   ISA Level 4\n     |\n     `------------------ Stage Tarball type: 1, 2 or 3.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):341
+msgid "So for those of you who are running R4000-class CPUs, try a <c>mips3</c> or <c>mipsel3</c> stage tarball."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):346
+msgid "For those running R5000-class or later CPUs, try a <c>mips4</c> or <c>mipsel4</c> stage tarball."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):351
+msgid "Sometimes the filename will have <c>n32</c> or <c>n64</c> in the filename as well. These refer to 64-bit userland images. At the moment, support for 64-bit userlands is still quite flaky and a lot of packages are broken. I'd suggest leaving these alone unless you're particularly brave and don't mind a rather bumpy ride."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):362
+msgid "I got told \"Illegal Instruction\" or \"Cannot Execute Binary File\" when chrooting. What did I do wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):366
+msgid "This is generally caused by using the wrong stage tarball. If you try to run a <c>mips4</c> userland on a <c>mips3</c> CPU, you'll get an <e>illegal instruction</e> error message. Likewise, if you have a Big Endian CPU and you try running Little Endian code on it, you'll get told <e>cannot execute binary file</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):374
+msgid "The fix is simple... clean out your partition, then unpack the correct tarball. Which one is that I hear you ask? Have a read of the previous FAQ entry."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):384
+msgid "Silicon Graphics Specific FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):386
+msgid "Why doesn't my SGI machine netboot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):389
+msgid "This could be for any number of reasons, ranging from cabling issues, through to issues on the server. The best way to troubleshoot any problem is a step-by-step approach..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):396
+msgid "<b>Have you got the SGI machine (and server) plugged into the right network ports?</b><br/> Make sure the network is cabled correctly. Also note that some machines have special needs. For instance the Challenge S cannot obtain network connectivity under Linux via its UTP port, you need to use the AUI port via a transceiver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):404
+msgid "<b>Are there any firewalls in use?</b><br/> Make sure your firewall is not blocking DHCP/BOOTP requests (ports 67 and 68 on UDP) or TFTP (port 69 on UDP).<br/><c>iptables -I INPUT 1 -p udp --dport 67:69 -j ACCEPT</c> should get things rolling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):411
+msgid "<b>Have you disabled packet MTU discovery and set the port range?</b><br/> SGI boxes require <path>/proc/sys/net/ipv4/ip_no_pmtu_disc</path> = 1 and <path>/proc/sys/net/ipv4/ip_local_port_range</path> = \"2048 32767\". See <uri link=\"/doc/en/handbook/handbook-mips.xml?part=1&amp;chap=2#doc_chap4\">the Gentoo/MIPS handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):419
+msgid "<b>Is the server giving out the correct details via BOOTP?</b><br/> Double check your <path>/etc/dhcp/dhcpd.conf</path>. ISC's dhcpd won't dish out addressing information via BOOTP unless the machine has been statically defined with a fixed address."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):425
+msgid "<b>Which TFTP server are you using?</b><br/><c>tftp-hpa</c> and <c>netkit-tftp</c> are known to work. <c>atftp</c> is a lot more advanced, this can cause problems. If in doubt, try installing <c>tftp-hpa</c> and see if the problem clears up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):431
+msgid "<b>Are the daemons running?</b><br/><c>dhcpd</c> should show up when typing <c>ps ax</c>. As for TFTP, it'll largely depend on whether its a standalone server, or if its running from <c>(x)inetd</c>. <c>tftp-hpa</c> runs as a process called <c>in.tftpd</c>. Look for that in the <c>ps ax</c> output and start any services not currently running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):439
+msgid "<b>Does the kernel exist in <path>/tftpboot</path>?</b><br/> Make sure you place the kernel image to be booted in this directory and that it is world-readable. (<c>chmod 644 /tftpboot/foo</c>) Also, in your <path>/etc/dhcp/dhcpd.conf</path>, note that the path to the kernel will be relative to the <path>/tftpboot</path> directory if you're using <c>tftp-hpa</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):447
+msgid "<b>Have you unset the <c>netaddr</c> and <c>dlserver</c> PROM variables?</b><br/> Try running <c>unsetenv netaddr</c> and <c>unsetenv dlserver</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):457
+msgid "The machine downloads the kernel, but then \"hangs\" (using a monitor and keyboard -- not serial console)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):461
+msgid "Unfortunately, not all graphics frame buffers are supported under Linux yet. This doesn't mean you can't use the machine... it just means you'll need a null-modem serial cable to interact with it. It is quite possible that the machine is in fact running, however, the system is outputting to the serial console rather than the screen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):474
+msgid "Cobalt Specific FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):476
+msgid "Why won't my Cobalt machine boot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):479
+msgid "This could be for a number of reasons. Our easiest bet however is to run through a checklist and make sure everything is correct."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):485
+msgid "<b>Have you got the Cobalt machine (and server) plugged into the right network ports?</b><br/> Make sure the network is cabled correctly. Please note, the Cobalt firmware will only boot via the Primary network port."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):491
+msgid "<b>Are there any firewalls in use?</b><br/> Make sure your firewall is not blocking DHCP/BOOTP requests (ports 67 and 68 on UDP) or RPC/Portmap (port 111 on UDP and TCP).<br/><c>iptables -I INPUT 1 -p udp --dport 67:68 -j ACCEPT</c><br/><c>iptables -I INPUT 1 -p udp --dport 111 -j ACCEPT</c><br/><c>iptables -I INPUT 1 -p tcp --dport 111 -j ACCEPT</c> should get things rolling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):500
+msgid "<b>Is the server giving out the correct details via BOOTP?</b><br/> Double check your <path>/etc/dhcp/dhcpd.conf</path>. ISCs dhcpd won't dish out addressing information via BOOTP unless the machine has been statically defined with a fixed address."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):506
+msgid "<b>Are you exporting <path>/nfsroot</path> in your <path>/etc/exports</path>?</b><br/> Make sure you are exporting that to the Cobalt machine. It only needs read-only access. Also remember to run <c>exportfs -av</c> after you edit the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):513
+msgid "<b>Are the daemons running?</b><br/><c>dhcpd</c> should show up when typing <c>ps ax</c>. Likewise with <c>portmap</c> and the other RPC daemons. The following commands should look after this for you:<br/><c>/etc/init.d/dhcp start</c><br/><c>/etc/init.d/nfs start</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):521
+msgid "<b>Does the kernel exist in <path>/nfsroot</path>?</b><br/> Make sure you place the kernel image to be booted in this directory and that it is world-readable. (<c>chmod 644 /nfsroot/foo</c>)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):531
+msgid "Why don't you support the Qube 2700?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):534
+msgid "The Qube 2700 was the first of the Cobalt servers. While they are very nice machines, unfortunately, they lack a serial port. In other words, any interaction with the machine has to be done through a network. At present, our netboot images do not support this, although plans are in the works that may enable support for this machine."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-mips-install.xml.pot b/doc/gettext/gentoo-mips-install.xml.pot
new file mode 100644
index 0000000..5b3c99d
--- /dev/null
+++ b/doc/gettext/gentoo-mips-install.xml.pot
@@ -0,0 +1,52 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(guide:redirect):3
+msgid "/doc/en/handbook/handbook-mips.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(title):4 ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(title):20
+msgid "Gentoo MIPS Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(author:title):6
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(mail:link):7
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(mail):7
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(abstract):10
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(version):16
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(date):17
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(p):24
+msgid "As of 2004.0, the individual architecture-specific installation guides have been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/handbook/handbook-mips.xml\">Gentoo Handbook</uri>. For more information please read up on the <uri link=\"/doc/en/handbook\">Gentoo Handbook Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-ppc-faq.xml.pot b/doc/gettext/gentoo-ppc-faq.xml.pot
new file mode 100644
index 0000000..6091ec1
--- /dev/null
+++ b/doc/gettext/gentoo-ppc-faq.xml.pot
@@ -0,0 +1,1034 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(guide:link):5
+msgid "/doc/en/gentoo-ppc-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):6
+msgid "Gentoo Linux/PowerPC Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):9
+msgid "rajiv@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail):9
+msgid "Rajiv Manglani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):12
+msgid "pylon@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail):12
+msgid "Lars Weiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):15
+msgid "sejo@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail):15
+msgid "Jochen Maes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):18
+msgid "josejx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail):18
+msgid "Joseph Jezak"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):21
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(abstract):24
+msgid "The Gentoo/PPC FAQ is a collection of questions and answers collected from the Gentoo/PPC mailing lists and from IRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(version):33
+msgid "1.41"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(date):34
+msgid "2009-04-15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):37
+msgid "Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):39
+msgid "Introduction to the Gentoo/PPC FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):42
+msgid "This FAQ is a collection of questions and answers collected from the Gentoo/PPC mailing lists and from IRC. If you have any questions (or answers!), please contact either an author or a member of the documentation team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):54
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):56
+msgid "What kind of PowerPC computer do I have and where can I find more information about it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):62
+msgid "Welcome to Gentoo PPC! The PowerPC processor has been used in a number of popular computing devices, here are some links to help you figure out what type of hardware is in the machine on your desk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):70
+msgid "http://www.info.apple.com/support/applespec.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):70
+msgid "Apple Product Pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):75
+msgid "http://lowendmac.com/profiles.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):75
+msgid "Apple Product History and Details"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):80
+msgid "http://www.pegasosppc.com/products.php"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):80
+msgid "Genesi Model Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):85
+msgid "http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.pseries.doc/hardware_docs/selectbysystem.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):85
+msgid "IBM Documentation by Model"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):90
+msgid "http://kurobox.com/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):90
+msgid "KuroBox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):93
+msgid "http://penguinppc.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):93
+msgid "PenguinPPC - Linux on PowerPC Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):102
+msgid "How can I verify with OSX that the downloaded ISO is not corrupted?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):105
+msgid "First be sure you did not mount the ftp server with <e>Finder</e> and then copy the file with drag'n'drop. This will corrupt the ISO. Instead, use <c>curl</c> (with <c>curl -O http://path/to/iso</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):111
+msgid "You can check your MD5 sum using the <c>md5sum</c> tool provided with OSX. On versions of OSX without md5sum, you can use <c>openssl</c> capability to produce an md5 checksum."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):117
+msgid "Creating an md5sum with openssl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):117
+#, no-wrap
+msgid "\n<comment>(This could take some time depending of the size of the ISO and your CPU)</comment>\n$ <i>openssl md5 /path/to/iso</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):122
+msgid "Now compare this output with the appropriate file found on the server where you downloaded the ISO (the file will end with <path>.md5</path>). If it is the same, the ISO image downloaded correctly. Be sure you have <e>not</e> mounted it (e.g. with Disk Copy) yet!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):132
+msgid "Can I dual-boot Gentoo Linux and Mac OS X?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):135
+msgid "Yes you can! In fact, <e>yabootconfig</e> will automatically detect and setup <path>/etc/yaboot.conf</path> with Linux, Mac OS X and even classic Mac OS (see the <uri link=\"/doc/en/handbook/handbook-ppc.xml?part=1&amp;chap=10\">Gentoo Handbook</uri> for details on yabootconfig). The trick is in how you partition your hard drive. Before installing Gentoo, startup with the Mac OS X Install CD. Use the <c>Disk Utility</c> to partition the drive in your machine into two or three partitions. Alternatively, use <c>parted</c> from a recent Gentoo InstallCD, since that has been patched to handle HFS and HFS+ partitions. Parted is also able to shrink a partition so you don't need to delete your existing install. The first partition should be big enough to contain all your Linux partitions (root+swap+/home etc.). The format of this partition does not matter. The second partition should be for OS X. The third (and optional) partition should be for classic Mac OS. It is only required if you intend of being able to triple boot, since OS9 must be on a separate partition from OSX for this to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):153
+msgid "After partitioning, install Mac OS X and Mac OS 9 onto their respective partitions. Once installation is complete, start following the <uri link=\"/doc/en/handbook/handbook-ppc.xml\">Gentoo Handbook</uri>. When you get to the section on partitioning, use <c>mac-fdisk</c> to <e>delete</e> the large partition you created for Gentoo. In its place, create a bootstrap partition, root, swap, and any other partitions you wish to use with Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):162
+msgid "If you have an OldWorld Macintosh (pre-iMac), follow a similar procedure as described above. However, use the Mac OS 9 install CD and the <c>Drive Setup</c> utility. OldWorld machines do not need a bootstrap partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):168
+msgid "If yabootconfig does not detect your MacOS partitions, you can manually add them to your yaboot.config. See the example yaboot.conf in the <uri link=\"/doc/en/handbook/handbook-ppc.xml?part=1&amp;chap=10#doc_chap2_pre6\"> handbook</uri> for details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):178
+msgid "I have an early NewWorld Mac such as the Blue and White G3. It should be compatible with the InstallCD, but on boot it returns an \"Unknown or corrupt filesystem\" error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):185
+msgid "As a workaround, boot into Open Firmware by holding down the Apple + Option + O + F keys on startup. When the prompt appears, type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):190
+msgid "Early NewWorld Mac Open Firmware work around"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):194
+msgid "The CD should boot as expected now, thanks to John Plesmid for this workaround."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):201
+msgid "I have an OldWorld Macintosh and need to use BootX. However, I am having trouble opening the BootX installer archive. What can I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):207
+msgid "You will need a new version of <e>StuffIt Expander</e> to open the archive. You can <uri link=\"http://www.stuffit.com/expander/download.html\">download it</uri> for free."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):216
+msgid "I have a Beige G3 machine. Can I install Gentoo Linux/PPC on a second IDE hard drive?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):222
+msgid "Early Beige G3 machines (those with a \"Rev 1\" motherboard with an ATI RageII+ chip) do not support slave IDE drives. To use a second hard drive with this machine, you would have to attach it to the internal or external SCSI connector or install a PCI IDE card. Later G3 machines do not have this limitation. See <uri>http://www.xlr8yourmac.com/G3-ZONE/IDE/index.html</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):234
+msgid "I have a revision A or B iMac. I've replaced the hard drive with a larger one and now I can't boot into anything!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):240
+msgid "There is an 8GB limit for the root partition on these machines. Ensure that your root partition is less than 8GB and it should work as expected. This also applies to OS X and later versions of OS 9."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):249
+msgid "My /etc/fstab file has /dev/BOOT in it. Do I need to setup this line for my Apple bootstrap partition?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):255
+msgid "No. If you are not using a separate boot partition (<path>/boot</path>) then you do not need this line and can safely just delete it from <path>/etc/fstab</path>. The Apple bootstrap partition is <e>not</e><path>/boot</path> and is not related in any way. In general, Apple PowerPC machines do not need a separate <path>/boot</path> partition, and the bootstrap partition should not be mounted or referred to in your fstab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):267
+msgid "When I rebooted, yaboot didn't work! Now, I'm stuck. How can I fix this?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):272
+msgid "It's probably just a misconfigured yaboot.conf. The easiest way to fix this is to boot the InstallCD again, mount your gentoo partition and check yaboot.conf for errors. You'll also need to run <c>ybin -v -C /mnt/gentoo/etc/yaboot.conf</c> to update the boot loader once you have finished. This can all be done without chrooting back into your install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):281
+msgid "If you <e>really</e> just need to get back to OSX, try holding down the Option key on startup. This should give you a graphical selection of bootable disks. Choose OSX and remember to fix your boot problems later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):290
+msgid "When I try to boot, yaboot only says \"read error\"! Why can't I boot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):295
+msgid "You're probably using XFS for your root partition. While this is an option, yaboot has some issues accessing files with holes. To ensure that your kernel will boot, instead of copying the vmlinux file to /boot, simply <c>cat</c> the kernel as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):302
+msgid "Fixing yaboot read errors on XFS with cat"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):302
+#, no-wrap
+msgid "\n# <i>cat /usr/src/linux/vmlinux &gt; /boot/vmlinux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):309
+msgid "I installed an OSX update and now my computer only boots into OSX! How can I fix it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):315
+msgid "Hold down the option key on boot. This will bring you to a graphical boot device selector. Wait until a hard drive with a penguin shows up and click on the icon. This will boot your linux install as usual. Once you've booted, rerun <c>ybin -v</c> to fix the bootloader."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):325
+msgid "I can't boot the InstallCD! It stops while trying to set the hardware clock. What do I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):331
+msgid "Unfortunately, there was a bug in some versions of the baselayout scripts. To get the system booting, the hardware clock will need to be set. To set the clock boot into Open Firmware (using the key combination of Apple + O + F). Once you are at the Open Firmware prompt, you can set the clock using the command below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):339
+msgid "Setting the clock at the open firmware prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):339
+#, no-wrap
+msgid "\n<comment># decimal dev rtc sec min hour day month year set-time</comment>\n<comment># The example below sets the clock to 1:23:45 June, 7th, 2000</comment>\n ok\n0 &gt; decimal dev rtc 45 23 1 6 7 2000 set-time\n ok\n1 &gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):348
+msgid "Open Firmware will return with an ok after the clock is set. The system should boot normally now. Type <c>mac-boot</c> to continue booting after the clock is set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):359
+msgid "Hardware Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):361
+msgid "I'm running Gentoo on a PowerPC laptop. What packages should I install to enable laptop-specific functionality?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):367
+msgid "There are four main packages you will need to install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):372
+msgid "<e>pbbuttonsd</e> is a tool that enables the brightness and volume keys on most ppc laptops as well as other apple laptop specific functionality. The current versions also work as a power manager and replaces <e>pmud</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):377
+msgid "<e>powerprefs</e> provides a graphical configuration editing tool for configuring pbbuttonsd including settings such as power-management, trackpad options and various other preferences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):382
+msgid "<e>powernowd</e> allows cpu speed scaling for longer battery life. Other packages also provide the same functionality, such as <e>cpudyn</e>, <e>cpufreqd</e> and <e>speedfreq</e>. It doesn't really matter which you chose, just ensure that you have the <e>userspace</e> cpu frequency scaling governor enabled in your kernel. This is the only governor that will work on PPC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):392
+msgid "These packages can be installed by running the appropriate commands from the list below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):397
+msgid "Installing laptop-specific packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):397
+#, no-wrap
+msgid "\n# <i>emerge pbbuttonsd</i>\n# <i>emerge powerprefs</i>\n# <i>emerge powernowd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):403
+msgid "You should edit <path>/etc/pbbuttonsd.conf</path> or use <e>powerprefs</e> to better suit your needs. The behaviour of the Fx-keys can be controlled here as well as many sleep options. To switch the Fx-keys to the OSX behaviour, set KBDMode to fkeyslast. You can turn off touchpad tapping by setting TPMode to notap. Many other options are available, see man pbbuttonsd.conf for details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):411
+msgid "It is useful to add pbbuttonsd and powernowd to your boot runlevel so that they're started when your computer starts. To do this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):416
+msgid "Adding pbbuttonsd and cpudyn to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):416
+#, no-wrap
+msgid "\n# <i>rc-update add pbbuttonsd boot</i>\n# <i>rc-update add powernowd boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):424
+msgid "I only have one mouse-button. How can I make use of the second and third one, since ctrl-button does not work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):430
+msgid "There is no way to use ctrl-button like on Mac OS X, but you can map just about any key or combination of keys to emulate the second and third mouse-button. The values can be obtained with the command line utility <c>showkey</c> from the console. Note that this program does not work as expected from X and should only be run from the console. To use this feature, enable the following options in your kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):439
+msgid "Macintosh Device Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):439
+#, no-wrap
+msgid "\n[*] Apple Desktop Bus (ADB) support\n[*]    Use input layer for ADB devices\n[*]      Support for mouse button 2+3 emulation\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):445
+msgid "You will also need to set the keyboard to mouse button mapping values in <path>/etc/sysctl.conf</path>. Here is an example using F11 and F12:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):450
+msgid "Mouse button emulation with F11 and F12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):450
+#, no-wrap
+msgid "\n<comment># Enable mouse button emulation</comment>\ndev.mac_hid.mouse_button_emulation = 1\n<comment># Set 2nd button to 87 - F11</comment>\ndev.mac_hid.mouse_button2_keycode = 87\n<comment># Set 3rd button to 88 - F12</comment>\ndev.mac_hid.mouse_button3_keycode = 88\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):459
+msgid "Other commonly used keycodes are 125 (The Apple key) and 96 (The Keypad Enter)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):463
+msgid "To activate these settings:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):467
+msgid "Applying the sysctl changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):467
+#, no-wrap
+msgid "\n# <i>sysctl -p /etc/sysctl.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):474
+msgid "How can I configure my Airport card?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):477
+msgid "The Airport card is an 802.11b device based on the Lucent Orinoco chipset. To use this card in Linux, enable these kernel options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):482
+msgid "Wireless LAN"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):482
+#, no-wrap
+msgid "\n[*] Wirless LAN Drivers &amp; Wireless Extensions\n&lt;*&gt; Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)\n&lt;*&gt;   Apple Airport support (build-in)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):488
+msgid "Once the kernel is configured, you'll also need some userland tools to configure the wireless settings. Emerge the <c>wireless-tools</c> for iwconfig and other wireless tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):494
+msgid "As an example of using iwconfig, to set your ESSID to home_essid:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):498
+msgid "Setting an ESSID"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):498
+#, no-wrap
+msgid "\n# <i>iwconfig eth1 essid home_essid</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):502 ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):543
+msgid "For a generic guide to setting up wireless with Gentoo, please see the <uri link=\"/doc/en/handbook/handbook-ppc.xml?part=4&amp;chap=4\">Gentoo Wireless Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):511
+msgid "How can I configure my Airport Extreme card?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):514
+msgid "The Airport Extreme is an 802.11b/g card that is included with modern Apple portable computers. It is based on the Broadcom 43xx chipset which is supported by the native b43 driver project. It has been included in the 2.6.24 kernel. Note that the driver should select the proper driver between b43 and b43-legacy. The firmware used for these two drivers is different, with the legacy version supporting older 4306 cards. If you have a 4306 card, build both, otherwise, it should be safe to only build b43. Also, to enable either driver, mac80211 must be selected first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):525
+msgid "Adding b43 support to the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):525
+#, no-wrap
+msgid "\nNetworking --&gt; Wireless --&gt;\n     &lt;M&gt;   Generic IEEE 802.11 Networking Stack (mac80211)\n\nDevice Drivers --&gt; Network device support --&gt;\n     [*] Wireless LAN (IEEE 802.11)\n     &lt;M&gt;   Broadcom 43xx wireless support (mac80211 stack)\n     [*]     Broadcom 43xx debugging\n     &lt;M&gt;   Broadcom 43xx-legacy wireless support (mac80211 stack)\n     [*]     Broadcom 43xx-legacy debugging\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):537
+msgid "After compiling your kernel, you'll need to emerge <c>b43-fwcutter</c> to install the firmware. For additional information, please see this <uri link=\"http://forums.gentoo.org/viewtopic-t-409194.html\">forum post.</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):552
+msgid "Will the internal modem work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):555
+msgid "On older Macs, the internal modem is a regular serial device. In addition to ppp support and i2c support, enable this kernel option to use it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):560
+msgid "Serial Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):560
+#, no-wrap
+msgid "\n&lt;*&gt; PowerMac z85c30 ESCC support (CONFIG_SERIAL_PMACZILOG)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):564
+msgid "Newer Macs use a USB device which only has a driver from Linuxant. Unless you have purchased a key from Linuxant, this driver will only work at 14.4 and will not support FAX. To install the driver, emerge <c>net-dialin/hcfusbmodem</c> which will provide <path>/dev/ttySHCF0</path>. Then set up ppp like usual. Further information about the installation can be found at <uri>http://www.linuxant.com/drivers/hcf/install.html</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):576
+msgid "Does sleep work on my iBook/PowerBook?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):579
+msgid "Sleep (suspend to ram) works very well on all G3 iBooks and TiBooks. Recently, a kernel patch has been released that adds sleep support for G4 iBooks and Radeon based AlBooks. If you have one of these laptops, use gentoo-sources 2.6.11 (or newer) for built in support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):586
+msgid "Note that the 12\" PowerBook is not yet supported due to its nVidia chipset."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):593
+msgid "How do I get sound playback working?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):596
+msgid "There are two approaches to sound on modern kernels: OSS or ALSA. OSS is the older of the two options and has been deprecated, but still functions well for many older Macs. ALSA is the newer method and will continue to be supported in the future. We recommend that you use ALSA unless you have problems with it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):603
+msgid "If you include the OSS driver in your kernel, the ALSA driver will not load."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):607
+msgid "In addition to configuring the kernel, users who should have access to the audio devices need to be added to the appropriate group with the command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):612
+msgid "Adding users to the audio group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):612
+#, no-wrap
+msgid "\n# <i>gpasswd -a username audio</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):616
+msgid "If the kernel is set up correctly, but you can't hear any sound, ensure that the main mixer volume is turned up and that the device isn't muted!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):621
+msgid "The sound card on Macs is connected through the i2c Keywest/PowerMac bus, not the PCI bus. You will not see the card listed when viewing the PCI bus or when using alsaconf. This is less of a problem then you might imagine, because all Macs use the same driver for sound, but you will need to insure that you have i2c Keywest/PowerMac support in your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(impo):629
+msgid "If you compile in ALSA support, you need to also compile in i2c Keywest/PowerMac support. Failure to do this will result in kernel panics on boot!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):638
+msgid "Sound setup with ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):641
+msgid "For ALSA, we'll set up both the regular ALSA drivers and the OSS emulation layer so that we can still use legacy OSS only programs. In <c>make menuconfig</c> you'll need to select:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):647
+msgid "Kernel options for ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):647
+#, no-wrap
+msgid "\nDevice Drivers - I2c support ---&gt;\n  I2C Hardware Bus Support ---&gt;\n    &lt;*&gt; Powermac I2C interface (Keywest on 2.6.15 and older)\n\nDevice Drivers - Sound ---&gt;\n&lt;*&gt; Sound card support\n    Advanced Linux Sound Architecture ---&gt;\n    &lt; &gt;   PowerMac DMA sound support\n      &lt;*&gt; Advanced Linux Sound Architecture\n      &lt;*&gt; Sequencer support\n      &lt;*&gt; Sequencer dummy client\n      &lt;*&gt; OSS Mixer API\n      &lt;*&gt; OSS PCM (digital audio) API\n      [*] OSS Sequencer API\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):664
+msgid "Depending on the age of the machine, the correct sound driver should also be enabled. On more modern machines such as Aluminum PowerBooks, new iBooks or G5's the <c>Apple On-board Audio</c> driver should be used. For older machines, try the ALSA PowerMac driver instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):671
+msgid "ALSA Drivers - Choose only one"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):671
+#, no-wrap
+msgid "\n<comment>Older Machines</comment>\n    ALSA PowerMac devices ---&gt;\n        &lt;*&gt; PowerMac (AWACS, DACA, Burgundy, Tumbler, Keywest)\n<comment>Newer Machines</comment>\n    Apple Onboard Audio driver ---&gt;\n        &lt;*&gt; Apple Onboard Audio driver\n        &lt;*&gt;   layout-id fabric\n        &lt;*&gt;   support Onyx chip\n        &lt;*&gt;   support TAS chip\n        &lt;*&gt;   support Toonie chip\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):684
+msgid "You can also configure these as modules and ensure they're loaded on boot, but it's easier to simply compile it all in."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):689
+msgid "Please make sure that <c>PowerMac DMA sound support</c> is turned off, otherwise the ALSA module will not be able to load."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):694
+msgid "For more information on configuring ALSA, please see the <uri link=\"/doc/en/alsa-guide.xml\">Gentoo ALSA Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):699
+msgid "If you are using the alsa-driver package instead of building it into your kernel, the ALSA_CARDS variable should be set to <c>powermac</c> for older Macs or all of <c>aoa</c>, <c>aoa-fabric-layout</c>, <c>aoa-soundbus</c>, <c>aoa-soundbus-i2c</c>, <c>aoa-onyx</c>, <c>aoa-tas</c> and <c>aoa-toonie</c> for newer Macs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):710
+msgid "Sound setup with OSS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):713
+msgid "Again, only use this if you're not using ALSA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):715
+msgid "In <c>make menuconfig</c> you'll need to select:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):719
+msgid "Kernel options for OSS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):719
+#, no-wrap
+msgid "\nDevice Drivers - I2c support ---&gt;\n  I2C Hardware Bus Support ---&gt;\n    &lt;*&gt; Powermac I2C interface (Keywest on 2.6.15 and older)\n\nDevice Drivers - Sound ---&gt;\n&lt;*&gt; Sound card support\n  &lt;*&gt;   PowerMac DMA sound support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):729
+msgid "(or configure as modules and ensure they're loaded on boot)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):733
+msgid "If the <c>dmasound_pmac</c> module does not load, you probably need to enable <c>i2c-core</c> in the kernel or as a module."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):738
+msgid "If you are still using OSS sound, please test the ALSA drivers instead and report any regressions to the ALSA bugzila. Thanks!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):746
+msgid "How do I make my Mac power up after a power failure?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):749
+msgid "The Power Management Unit (PMU) in most Macs has the ability to turn the Mac on again after a power loss. This feature is controlled by the PMU options found in <path>/proc</path>. To enable this feature, set <c>server_mode</c> to 1, to disable it, set <c>server_mode</c> to 0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):756
+msgid "Enabling power on after power failure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):756
+#, no-wrap
+msgid "\n# <i>echo \"server_mode=1\" &gt; /proc/pmu/options</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):760
+msgid "Unfortunately, this setting is turned off again after the machine restarts. To ensure that your system always starts with power on after power failure enabled, add the line above to <path>/etc/conf.d/local.start</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):769
+msgid "I see lots of \"IN from bad port\" errors in my kernel dmesg, how do I fix that?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):774
+msgid "This is caused by drivers written for devices that you don't have on your system. These messages are usually harmless, but it's a good idea to disable the unused drivers anyway. See below to match up port numbers with kernel configuration options. Note that even if the numbers don't match, try disabling these kernel options anyway, most PPC machines don't use these drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):783
+msgid "IN from bad port 61 - Disable PC Speaker support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):783
+#, no-wrap
+msgid "\nDevice Drivers - Input device support ---&gt;\n[*] Miscellanous devices ---&gt;\n      &lt; &gt; PC Speaker Support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):789
+msgid "IN from bad port 64 - Disable i8042 keyboard support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):789
+#, no-wrap
+msgid "\nDevice Drivers - Input device support ---&gt;\nHardware I/O Ports ---&gt;\n      &lt; &gt; Serial I/O support\n        &lt; &gt; i8042 PC Keyboard controller\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):796
+msgid "IN from bad port 2E9,2F9,3E9,3F9 - Disable 8250/16550 support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):796
+#, no-wrap
+msgid "\nDevice Drivers - Character devices ---&gt;\nSerial drivers ---&gt;\n      &lt; &gt; 8250/16550 and compatible serial support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):802
+msgid "If you have another IN from bad port message that you're not sure about, please let us know!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):812
+msgid "Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):814
+msgid "I can't emerge a package, and get an error about it being masked. What should I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):820
+msgid "There are two common reasons why a package will not emerge: either it hasn't been tested on PPC or it has been tested, but hasn't yet been marked stable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):825
+msgid "The Package Hasn't Been Tested on PPC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):825
+#, no-wrap
+msgid "\n!!! All ebuilds that could satisfy \"bar\" have been masked.\n!!! One of the following masked packages is required to complete your request:\n- app-foo/bar-1.0 (masked by: missing keyword)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):831
+msgid "If your package hasn't yet been tested on PPC, you'll need to first mark the ebuild with the ppc keyword. This is done using the ekeyword tool which is part of the gentoolkit-dev package. To mark the ebuild ppc and regenerate the manifest file so that it reflects the changes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):838
+msgid "Adding the ppc keyword to app-foo/bar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):838
+#, no-wrap
+msgid "\n# <i>ekeyword ppc /usr/portage/app-foo/bar/bar-1.0.ebuild</i>\n# <i>ebuild /usr/portage/app-foo/bar/bar-1.0.ebuild manifest</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):843
+msgid "Once the ebuild has been keyworded, you can now emerge it as usual. Test the application and if it works, <b>please</b> report it as a bug so one of the developers can add the keyword."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):849
+msgid "This change will only last until the next sync. If you need a more permanent fix, you can maintain a portage overlay. See the portage documentation for more information on maintaining an overlay."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):855
+msgid "The Package Hasn't Been Marked Stable on PPC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):855
+#, no-wrap
+msgid "\n!!! All ebuilds that could satisfy \"bar\" have been masked.\n!!! One of the following masked packages is required to complete your request:\n- app-foo/bar-1.0 (masked by: ~ppc keyword)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):861
+msgid "If your package already has the ~ppc keyword, you have two options. Either follow the above instructions and replace the ~ppc keyword with ppc, or you can use /etc/portage to unmask the specific package. The second option is preferred simply because it won't be undone by an emerge sync."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):868
+msgid "Using /etc/portage to unmask app-foo/bar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):868
+#, no-wrap
+msgid "\n$ <i>echo \"=app-foo/bar-1.0 ~ppc\" &gt; /etc/portage/package.keywords</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):872
+msgid "If the /etc/portage directory does not exist, make sure to create it first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):876
+msgid "Now emerge the package as normal. Once you're sure the app is stable, <b>please</b> report this as a bug so the developers can add the keyword."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):884
+msgid "Does Gentoo/PPC have support for Flash?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):887
+msgid "Well, not really. Macromedia has not supplied a linux/ppc binary and open source implementations are incomplete at this time. However, there are two projects that can play many flash objects, <uri link=\"http://www.gnu.org/software/gnash/\">gnash</uri> and <uri link=\"http://swfdec.freedesktop.org/\">swfdec</uri>. Both are capable of playing back Youtube movies and lots of other popular content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):900
+msgid "Does Gentoo/PPC have a Java plugin?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):903
+msgid "Yes, a Java plugin is now available with IBM's Java 1.5 and 1.6. Note that not all Java applications work with these Java versions yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):911
+msgid "Is there an easy way to configure X?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):914
+msgid "Simply emerge <c>xac</c>. Once the package has been emerged, run <c>xac</c> to generate the config for your setup. If you would like to set a keyboard layout, you can use the --kbd-layout option. Note that although <c>xac</c> does set up DRM for most users, you may need to change your kernel configuration and emerge additional drivers to support the suggested configuration. Be sure that you've configured your kernel as shown in the question below for optimal performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):926
+msgid "What is required for DRM?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):929
+msgid "When emerging xorg-server, make sure the dri use flag is enabled. You should also set the VIDEO_CARDS variable in make.conf with your video card, VIDEO_CARDS=\"radeon\" for radeon support, VIDEO_CARDS=\"nv\" for nvidia support and so on. For a backup option, add fbdev to the list of VIDEO_CARDS, this driver should always work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):937
+msgid "Make sure in your kernel config you have the following options set:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):941
+msgid "Rage128 DRM kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):941
+#, no-wrap
+msgid "\nDevice Drivers - Character devices ---&gt;\n  &lt;*&gt; /dev/agpgart (AGP Support)\n  [*] Apple UniNorth support\n  [*] Direct Rendering Manager (DRI support)\n  &lt;*&gt;   ATI Rage 128\nDevice Drivers - Graphics Support ---&gt;\n  &lt;*&gt;   ATI Rage 128 display support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):951
+msgid "Radeon DRM kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):951
+#, no-wrap
+msgid "\nDevice Drivers - Character devices ---&gt;\n  &lt;*&gt; /dev/agpgart (AGP Support)\n  [*] Apple UniNorth support\n  [*] Direct Rendering Manager (DRI support)\n  &lt;*&gt;   ATI Radeon\nDevice Drivers - Graphics Support ---&gt;\n  &lt;*&gt;   ATI Radeon display support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):961
+msgid "nVidia kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):961
+#, no-wrap
+msgid "\nDevice Drivers - Graphics Support ---&gt;\n  &lt;*&gt;   nVidia Framebuffer Support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):966
+msgid "There is currently no support for DRM on nVidia cards since nVidia has not released any drivers for PPC and there are no open drivers for 3D acceleration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):971
+msgid "Rebuild and install the kernel if necessary. After this, make sure you have booted to the native framebuffer (i.e. radeonfb or atyfb128 and <e>not</e> from offb or ofonly video), and run <c>xac</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(impo):977
+msgid "You may need to edit your <path>/etc/X11/xorg.conf</path> file depending on your card setup. Ensure that the device driver selected is either ati or your specific driver (r128 or radeon). Also check that the DRI extension is loaded and not commented out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):987
+msgid "I've installed X.org and configured it correctly, but the radeon driver is missing. What's wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):993
+msgid "Add the appropriate VIDEO_CARDS line to <path>/etc/make.conf</path> (specify r128 or radeon) and recompile <c>xorg-server</c> and <c>mesa</c> to rebuild the driver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1002
+msgid "I have a VBIOS or \"Invalid I/O allocation\" error in my xorg.log. Is this a problem?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1008
+msgid "No, this is simply X.org probing your video card. It attempts to open the x86 only video BIOS and fails, leaving one of these messages. It's harmless, don't worry about it!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1017
+msgid "When using OpenGL DRI or playing movies, the system sometimes freezes hard unexpectedly. What can I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1023
+msgid "Your system may not cope properly with AGP support. The easiest solution is to add the following line to the \"Device\" section of <path>/etc/X11/xorg.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):1029
+msgid "Forcing PCI mode for AGP-Cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):1029
+#, no-wrap
+msgid "\nOption       \"ForcePCIMode\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1033
+msgid "Also, there are some known issues with the composite extension, please disable this extension if you're having problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1038
+msgid "Finally, if you are still having trouble, please try disabling dri in your xorg.conf and see if the problems go away."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1046
+msgid "I recently emerged Xorg, but when using it, my international keyboard layout does not work correctly. The main keys work fine but I am unable to compose special characters like the \"at\" sign. The startx output says something like \"could not load keymap, falling back to default keymap\". What is wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1054
+msgid "Check that the permissions on <path>/var/tmp</path> are set to <path>drwxrwxrwx</path>. If not, change them by typing <c>chmod a+rwx /var/tmp</c>. This will allow Xorg to load keymaps properly again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1063
+msgid "How do I play Audio CDs?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1066
+msgid "NewWorld machines have no audio connection between their CD-ROM drive and their sound hardware. Therefore, audio information must be read as data and then piped to the sound hardware. This is possible using <e>Audacious</e>, which reads the audio off the CD over the ATA cable, decodes it in software and sends it to the sound card over the PCI bus as digital data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):1074
+msgid "Emerge audacious"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):1074
+#, no-wrap
+msgid "\n# <i>emerge audacious</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1078
+msgid "To play a CD, just fire up <c>audacious</c>. If you're having playback trouble, you may need to open up the Preferences--&gt;Plugins--&gt;CD Audio Plugin menu and select your CD drive. Make sure that \"Digital audio extraction\" is checked."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1087
+msgid "Can I run Mac OS 9 or Mac OS X under Gentoo Linux?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1090
+msgid "Yes, as long as you are running Gentoo Linux on 32 bit PPC hardware, you can use <uri link=\"http://www.maconlinux.org/\">Mac-on-Linux</uri> which allows you to run an instance of OS 9, OS X or Linux as a process on Linux. Simply <c>emerge mol</c> to install this package. MOL supports Mac OS 7.5.2 to 9.2.2, as well as any version of OS X. It can be run from a console framebuffer or run in a window on X."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):1099
+msgid "Currently, there is no support for running MOL on 64 bit PowerPC Processors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):1103
+msgid "To run MOL fullscreen, you'll need to compile MOL with the fbcon use flag enabled and run it in a console framebuffer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1108
+msgid "For networking and sound you should install the drivers in the folder <path>MOL-Install</path> on your Mac OS X-Desktop. If errors with networking occur, make sure you have the following kernel options enabled:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1114
+msgid "For OSX Networking:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1119
+msgid "Universal TUN/TAP device driver support (CONFIG_TUN)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1122
+msgid "For the DHCP server:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1127
+msgid "Socket Filtering (CONFIG_FILTER)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1128
+msgid "Packet Socket (CONFIG_PACKET)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1131
+msgid "For NAT:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1136
+msgid "Network packet filtering (CONFIG_NETFILTER)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1137
+msgid "Connection tracking (CONFIG_IP_NF_CONNTRACK)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1138
+msgid "IP tables support (CONFIG_IP_NF_IPTABLES)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1139
+msgid "Packet filtering (CONFIG_IP_NF_FILTER)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1140
+msgid "Full NAT (CONFIG_IP_NF_NAT)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1141
+msgid "MASQUERADE target support (CONFIG_IP_NF_TARGET_MASQUERADE)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1147
+msgid "Can I access my ext2/ext3 partitions from OSX?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1150
+msgid "OSX can support the reading and writing of ext2/ext3 partitions by using the kernel extension provided by the <uri link=\"http://sourceforge.net/projects/ext2fsx\">ext2fsx project.</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):1156
+msgid "When using MOL, you cannot access a partition that is currently being used by Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1164
+msgid "Which Portage USE flags do not work on PowerPC machines?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1167
+msgid "If you're using an old flat profile, (deprecated, pre 2005.0) look at <path>/etc/make.profile/use.mask</path> for a list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1172
+msgid "If you're using a cascaded profile, (2005.0 and onwards) look at <path>/usr/portage/profiles/default-linux/ppc/use.mask</path> for a list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1180
+msgid "How can I set up distcc with my x86 box?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1183
+msgid "If you've got another faster computer, you can set up distcc to compile binaries for your slower ppc processor. It's better to do as much building as possible on the faster machine; if possible, don't even build on the slower computer. Read the <uri link=\"/doc/en/cross-compiling-distcc.xml\">DistCC Cross-compiling Guide</uri> to learn how. You may also want to read the <uri link=\"/proj/en/base/embedded/handbook/\">Gentoo Embedded Handbook</uri> to learn more about cross-compiling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1196
+msgid "Why does gcc keep segfaulting during ebuilds?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1199
+msgid "If gcc segfaults during ebuilds, this probably isn't a bug with gcc and isn't even a problem with your hardware. Most of the time this problem is due to kernel preemption being enabled. Although this option is safe on x86, it can cause cache corruption on PPC which is why it is noticed most frequently during compiles. To prevent this from happening, simply recompile the kernel with preempt turned off. To check if preempt is enabled:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):1208
+msgid "Check if preempt is enabled"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):1208
+#, no-wrap
+msgid "\n$ <i>grep PREEMPT /usr/src/linux/.config</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1212
+msgid "If returns: \"# CONFIG_PREEMPT is not set\", then you should report the segfault as a bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1217
+msgid "If it returns: \"CONFIG_PREEMPT=y\", then you'll need to disable it and rebuild your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1227
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1229
+msgid "Can I buy a CD of Gentoo Linux/PPC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1232
+msgid "Yes! We sell Gentoo on CD-ROM in our <uri link=\"http://store.gentoo.org/\">Gentoo store</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1240
+msgid "This FAQ hasn't answered my question. What do I do now?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1243
+msgid "A good first step is to browse through the relevant <uri link=\"/doc/en/index.xml\">documentation on www.gentoo.org</uri>. Two PPC-specific <uri link=\"/main/en/lists.xml\">mailing lists</uri> currently exist, gentoo-ppc-dev and gentoo-ppc-user. <uri link=\"http://forums.gentoo.org/viewforum.php?f=24\">Gentoo on PPC</uri> (on forums.gentoo.org) is an open bulletin-board for discussion of all PowerPC issues. Also, there is usually a lively discussion on IRC. Join us on <c>#gentoo-ppc</c> on <c>irc.freenode.net</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1254
+msgid "General information about Linux on PowerPC can be found at <uri link=\"http://penguinppc.org/\">penguinppc.org</uri>. General Linux information is at <uri link=\"http://www.linuxdoc.org/\">www.linuxdoc.org</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-ppc-install.xml.pot b/doc/gettext/gentoo-ppc-install.xml.pot
new file mode 100644
index 0000000..e8158ca
--- /dev/null
+++ b/doc/gettext/gentoo-ppc-install.xml.pot
@@ -0,0 +1,56 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(guide:link):4
+msgid "/doc/en/gentoo-ppc-install.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(guide:redirect):4
+msgid "/doc/en/handbook/handbook-ppc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(title):5 ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(title):21
+msgid "Gentoo PPC Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(mail:link):8
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(mail):8
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(abstract):11
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(version):17
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(date):18
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(p):25
+msgid "As of 2004.0, the individual architecture-specific installation guides have been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/handbook/handbook-ppc.xml\">Gentoo Handbook</uri>. For more information please read up on the <uri link=\"/doc/en/handbook\">Gentoo Handbook Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-security.xml.pot b/doc/gettext/gentoo-security.xml.pot
new file mode 100644
index 0000000..b61c993
--- /dev/null
+++ b/doc/gettext/gentoo-security.xml.pot
@@ -0,0 +1,60 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(guide:link):5
+msgid "/doc/en/gentoo-security.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(guide:redirect):5
+msgid "/doc/en/security/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(title):6
+msgid "Obsolete Gentoo Linux Security Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(mail:link):8
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(mail):8
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(abstract):11
+msgid "This was a step-by-step guide for hardening Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(version):15
+msgid "1.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(date):16
+msgid "2005-06-01"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(title):19
+msgid "Obsolete"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(p):23
+msgid "This guide has been replaced by the <uri link=\"/doc/en/security/\">Gentoo Security Handbook</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-sparc-faq.xml.pot b/doc/gettext/gentoo-sparc-faq.xml.pot
new file mode 100644
index 0000000..c49fe5c
--- /dev/null
+++ b/doc/gettext/gentoo-sparc-faq.xml.pot
@@ -0,0 +1,563 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):6
+msgid "Gentoo Linux/SPARC Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(author:title):8
+msgid "SPARC Developer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(mail:link):9
+msgid "weeve"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(abstract):15
+msgid "This FAQ is designed to help answer the most commonly asked questions about Gentoo/SPARC and Linux on SPARC architecture. Feel free to send revisions and corrections to the Gentoo/SPARC team or the doc team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(version):25
+msgid "1.12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(date):26
+msgid "2010-03-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):29
+msgid "Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):31
+msgid "Documentation Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):34
+msgid "These are some notes to elaborate on acronyms and terms used in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):38
+msgid "When mentioning <c>SPARC</c>, this refers to the type of <c>sun4x</c> system. SPARC represents the <c>sun4u</c> architecture seen in the UltraSPARC series of systems (Ultras, Blades, SunFires, etc). Older 32-bit systems are no longer supported by the Gentoo/SPARC team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):45
+msgid "Acronyms: <c>OBP</c> = OpenBoot PROM, <c>SS</c> = SPARCstation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):54
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):56
+msgid "How do I install/use my SPARC over a serial console?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):59
+msgid "First, make sure you do not have a keyboard and monitor plugged in. OBP will use the monitor for output by default if either are plugged in. You will need a null modem cable or a regular serial cable with a null modem adapter to be able to view output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):66
+msgid "Standard serial port settings:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):71
+msgid "9600 baud"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):72
+msgid "8 data bits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):73
+msgid "None for parity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):74
+msgid "1 stop bits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):77
+msgid "Below is a list of commonly used programs for viewing a serial console. Check to see if your serial console application has the ability to send a break, as it can be very useful on a SPARC. The break signal on a serial console is the equivalent to issuing the Stop+A command on the keyboard."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(th):86
+msgid "Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(th):87
+msgid "Windows"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):90
+msgid "Minicom"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):91
+msgid "Hyperterm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):94
+msgid "Kermit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):95
+msgid "TeraTerm Pro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):98
+msgid "Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):102
+msgid "Seyon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):111
+msgid "I have a CRT/LCD monitor attached to my SPARC that selects a resolution my monitor can't handle when the kernel boots. How do I get a visible and/or non-distorted display on my monitor?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):116
+msgid "This problem is a result of the framebuffer support the Linux kernel loads at boot time, and the modelines available on SPARC systems. Here we will assume your monitor and video card will agree on a resolution of 1024 by 768 at a refresh rate of 60 Hz. In OBP, you can set the resolution by adjusting the setting for <c>output-device</c>. To view the current setting, use the command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):124
+msgid "View current settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):124
+#, no-wrap
+msgid "\nok <i>printenv output-device</i>\n\n<comment>&lt;output-device&gt;        &lt;screen&gt;          &lt;screen&gt;</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):130
+msgid "Now, to set this so it will start the display using the above mentioned resolution, we will use the <c>setenv</c> command as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):135
+msgid "Setting display"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):135
+#, no-wrap
+msgid "\nok <i>setenv output-device screen:r1024x768x60</i>\n\noutput-device =       screen:r1024x768x60\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):141
+msgid "In order for this to take effect, you will need to reset the machine:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):145
+msgid "Resetting the machine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):145
+#, no-wrap
+msgid "\nok <i>reset</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):149
+msgid "Additionally, for users using the onboard video card based on the ATI Mach64 chipset (Ultra 5/10 and Blade 100/150), you will want to append the following to your kernel boot options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):155
+msgid "Appending a kernel boot option"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):155
+#, no-wrap
+msgid "\nvideo=atyfb:1024x768@60\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):159
+msgid "If you are booting from SILO, you can append the above string onto the end of a given boot image. The following example would be if you were booting from the LiveCD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):165
+msgid "Booting a Gentoo LiveCD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):165
+#, no-wrap
+msgid "\nboot: <i>gentoo video=atyfb:1024x768@60</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):169
+msgid "If you were booting from the network, you would append the string onto the end of the boot net command in OBP as illustrated below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):174
+msgid "Booting from the net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):174
+#, no-wrap
+msgid "\nok <i>boot net video=atyfb:1024x768@60</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):181
+msgid "I'm new to SPARC and am not sure what kernel options to use, HELP!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):185
+msgid "Most of the time, the default kernel options will be acceptable for hardware support. You will need to make sure that <c>virtual memory</c> and <c>/proc filesystem</c> support is enabled in the kernel as instructed in the <uri link=\"/doc/en/handbook/handbook-sparc.xml\">Installation Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):195
+msgid "How do I dual boot Gentoo Linux/SPARC with Solaris?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):198
+msgid "Dual booting Gentoo/SPARC and Solaris can be done one of two ways. The two ways are: having both Gentoo/SPARC and Solaris on the same drive, or having them on separate drives. Below are example SILO configurations for each scenario. In the example configs, the following things are assumed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):205
+msgid "Single Drive Setup:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):210
+msgid "Boot drive is SCSI ID 0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):211
+msgid "Gentoo boots from partition 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):212
+msgid "Solaris boots from partition 5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):215
+msgid "Separate Drive Setup:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):220
+msgid "Second drive is SCSI ID 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):221
+msgid "Gentoo is on SCSI ID 0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):222
+msgid "Solaris is on SCSI ID 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):223
+msgid "boot-device in OBP is SCSI ID 0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):227
+msgid "Sample silo.conf for a single drive installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):227
+#, no-wrap
+msgid "\n<comment># Generic config options</comment>\npartition = 1\ntimeout = 50\n\n<comment># Gentoo/SPARC options</comment>\nimage = /boot/vmlinux\n    label = linux\n    root=/dev/sda4\n\n<comment># Solaris options</comment>\nother=5\n    label = Solaris\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):242
+msgid "Sample silo.conf for separate disk installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):242
+#, no-wrap
+msgid "\n<comment># Generic config options</comment>\nparition = 1\ntimeout = 50\n\n<comment># Gentoo/SPARC options</comment>\nimage = /boot/vmlinux\n    label = linux\n    root=/dev/sda4\n\n<comment># Solaris options</comment>\nother = /sbus/espdma/esp/sd@1,0;1\n    label = solaris\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):262
+msgid "Hardware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):264
+msgid "Will Gentoo run on my SPARC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):267
+msgid "It depends on the type of SPARC, but chances are yes. One exception seems to be the SPARC based laptops from Tadpole, particularly the newer models. If you have a working Tadpole on Gentoo/SPARC, please contact us and let us know the details on the model and anything special needed to get it to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):274
+msgid "The Gentoo/SPARC team maintains a <uri link=\"/proj/en/base/sparc/sunhw.xml\">hardware compatibility list</uri> for SPARC64 systems. In general, support for SPARC64 systems is good enough to allow some users to run it successfully in production environments."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):284
+msgid "What additional hardware is supported under Gentoo/SPARC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):287
+msgid "For a list of additionally supported Sun hardware, consult the following list from the <uri link=\"http://www.ultralinux.org/faq.html#q_2_2.\">UltraLinux homepage</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):293
+msgid "A partial list of Sun devices which do NOT currently have support under Gentoo/SPARC or SPARC/Linux in general are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):299
+msgid "SunPCI cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):300
+msgid "SBUS or PCI PCMCIA controllers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):301
+msgid "Smart card readers on some Sun Blade workstations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):302
+msgid "Floppy drive on some Sun Blade workstations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):305
+msgid "Also, the Gentoo/SPARC team maintains a <uri link=\"/proj/en/base/sparc/hwlist.xml\">list of non-Sun PCI hardware that has been tested on Gentoo/SPARC</uri>. To submit additions to the list, email <mail>sparc@gentoo.org</mail> with the information on the hardware as displayed in the existing hardware list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):316
+msgid "How do I know which SPARC I have?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):319
+msgid "The <uri link=\"http://www.ultralinux.org/faq.html#q_2_1\">UltraLinux FAQ</uri> has the answer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):327
+msgid "My box has more than one Sun Ethernet device. Why do they all have the same MAC address and how do I fix it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):331
+msgid "First, the reason they all they all have the same setting is due to a value in OpenBoot PROM (OBP). The story goes that in times past, it was assumed that if a host had multiple interfaces, the interfaces would not reside on the same Ethernet and therefore having the MAC address unique to a machine rather than to a NIC wouldn't be a problem. As time went on and different technologies developed, the opposite was proven."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):340
+msgid "As for fixing the issue, there are two ways to it; from OBP and from Linux. The OBP variable <c>local-mac-address?</c> controls this behavior. The following commands will help you to determine what <c>local-mac-address?</c> is set to:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):346
+msgid "View local-mac-address? setting from OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):346
+#, no-wrap
+msgid "\nok <i>printenv local-mac-address?</i>\nlocal-mac-address? =  false\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):351
+msgid "View local-mac-address? setting from Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):351
+#, no-wrap
+msgid "\n# <i>eeprom local-mac-address?</i>\nlocal-mac-address?=false\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):356
+msgid "As you'll notice from the samples above, <c>local-mac-address?</c> is set to <b>false</b>. This will cause all interfaces on a SPARC to use the same MAC address. To change this behavior, use either of the commands below (depending on whether you do it from OBP or Linux):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):363
+msgid "Set local-mac-address? from OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):363
+#, no-wrap
+msgid "\nok <i>setenv local-mac-address?=true</i>\nlocal-mac-address? =  true\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):368
+msgid "Set local-mac-address? from Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):368
+#, no-wrap
+msgid "\n# <i>eeprom local-mac-address?=true</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):372
+msgid "Note that you may need to reboot to see the changes take affect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):379
+msgid "Is SPARC big-endian or little-endian?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):382
+msgid "The version supported by Gentoo/SPARC (v9) is bi-endian. It uses big-endian instructions, but can access data in little-endian byte-order, such as PCI devices, which are little-endian by nature."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):393
+msgid "Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):395
+msgid "How do I get Xorg to find a usable modeline on my Ultra 5/10 or Blade 100/150?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):400
+msgid "The ATI Framebuffer normally expects a PC's BIOS to set the Reference Clock speed for the video card. However, on non-x86 architectures, this doesn't happen. So what needs to be done is to set the Reference Clock speed in the <path>/etc/X11/xorg.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):407
+msgid "In the \"Device\" section of your <path>/etc/X11/xorg.conf</path>, you will want to add a line similar to the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):412
+msgid "Add to xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):412
+#, no-wrap
+msgid "\nOption      \"reference_clock\"   \"28.636 MHz\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):416
+msgid "Other common speeds are 14.318 MHz and 29.5 MHz. If you have issues you might want to try without a similar setting first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):424
+msgid "How come package foo is masked on SPARC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):427
+msgid "Chances are this is due to the fact that none of the Gentoo/SPARC developers have gotten around to testing this yet, and/or the package is currently marked with the <c>~sparc</c> keyword (meaning it's in a testing phase)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):433
+msgid "If you still want to install the package, you can follow the instructions from the <uri link=\"/doc/en/handbook/handbook-sparc.xml?part=3&amp;chap=3\">Portage Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):442
+msgid "How can I help get package foo marked stable?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):445
+msgid "If you want to help ensure a package gets marked stable in a timely fashion, particularly if it's an application with a small userbase (i.e. net-im/bitlbee), install the package and test to make sure it works. If it appears to be working well, feel free to file a bug via the <uri link=\"http://bugs.gentoo.org\">Gentoo Bugzilla</uri> and assign it to the Gentoo/SPARC team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):457
+msgid "I tried to emerge a package, but emerge failed complaining that a dependency is masked. How can I fix this?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):461
+msgid "This is a bug. Please file a bug report via the <uri link=\"http://bugs.gentoo.org\">Gentoo Bugzilla</uri> for the Gentoo/SPARC team indicating what package you tried to emerge, the error message emerge gave you, and the output of <c>emerge --info</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):471
+msgid "Why am I getting an error related to 32/64-bit when compiling a kernel?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):475
+msgid "The way SPARC/Linux handles the cross-compiler has changed with 2.6.25 (<uri link=\"http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=54cd6ddec77b75e6926d73d263aec72255b24030\">commit</uri>), thus when building a recent kernel you'd get the following error message:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):481
+msgid "SPARC/Linux compile error message"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):481
+#, no-wrap
+msgid "\nCHK     include/linux/version.h \nCHK     include/linux/utsrelease.h \nCC      arch/sparc64/kernel/asm-offsets.s \narch/sparc64/kernel/asm-offsets.c:1: error: -m64 is not supported by this configuration \narch/sparc64/kernel/asm-offsets.c:1: error: -mlong-double-64 not allowed with -m64 \narch/sparc64/kernel/asm-offsets.c:1: error: -mcmodel= is not supported on 32 bit systems \nmake[1]: *** [arch/sparc64/kernel/asm-offsets.s] Error 1 \nmake: *** [prepare0] Error 2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):492
+msgid "Because, for the moment (there's an <b>experimental</b><uri link=\"/proj/en/base/sparc/multilib.xml\">multilib</uri> profile), Gentoo/SPARC native compiler can't generate 64-bit code (that's what sys-devel/kgcc64 is for)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):499
+msgid "What you need to do is to tell the SPARC/Linux Makefile what is your cross-compiler's binary, by issuing the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):504
+msgid "Gentoo/SPARC kernel &gt;=2.6.25 kernel compilation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):504
+#, no-wrap
+msgid "\n# <i>cd /usr/src/linux</i>\n# <i>make CROSS_COMPILE=sparc64-unknown-linux-gnu-</i>\n# <i>make CROSS_COMPILE=sparc64-unknown-linux-gnu- image modules_install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):515
+msgid "Miscellaneous"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):517
+msgid "I'm interested in becoming more involved with Gentoo/SPARC. How do I go about doing that?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):521
+msgid "There are various ways to improve the project:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):526
+msgid "The best way is to become an <uri link=\"/proj/en/base/sparc/at/index.xml\">Arch Tester</uri>, and aid the developers with package testing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):530
+msgid "File bug reports such as <uri link=\"http://dev.gentoo.org/~tcunha/reports/imlate-sparc.txt\">stable, and keyword</uri> requests."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):534
+msgid "Join the <uri link=\"irc://irc.gentoo.org/gentoo-sparc\">#gentoo-sparc</uri> IRC channel on the FreeNode IRC network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):538
+msgid "Make use of the <uri link=\"http://forums.gentoo.org/viewforum.php?f=27\">Gentoo/SPARC forum</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):541
+msgid "Propose solutions for Gentoo/SPARC related bugs via the <uri link=\"http://bugs.gentoo.org\">Gentoo Bugzilla</uri>. The bugs will be assigned, or CCed to sparc@gentoo.org."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):552
+msgid "Additional Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):554
+msgid "Where can I get more help or information about SPARC/Linux?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):558
+msgid "<uri link=\"http://docs.sun.com/app/docs/coll/216.2\">OBP Reference Guide</uri> - Sun's guide to the OpenBoot PROM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):562
+msgid "<uri link=\"http://www.sunstuff.org\">OSIAH</uri> - Online Sun Information Archive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):566
+msgid "<uri link=\"http://www.obsolyte.com\">Obsolyte</uri> - Information on older SPARC systems and links to a lot of other great SPARC related sites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):570
+msgid "<uri link=\"http://docs.sun.com\">Sun Microsystems Documentation</uri> - Additional hardware and software information for SPARC systems, including instructions for flashing OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):575
+msgid "<uri link=\"http://sunsolve.sun.com\">Sunsolve</uri> - Great resource for Sun hardware documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):579
+msgid "<uri link=\"http://www.ultralinux.org\">UltraLinux Homepage</uri> - Homepage of the SPARC/Linux port"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-sparc-install.xml.pot b/doc/gettext/gentoo-sparc-install.xml.pot
new file mode 100644
index 0000000..369b621
--- /dev/null
+++ b/doc/gettext/gentoo-sparc-install.xml.pot
@@ -0,0 +1,56 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(guide:link):4
+msgid "/doc/en/gentoo-sparc-install.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(guide:redirect):4
+msgid "/doc/en/handbook/handbook-sparc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(title):5 ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(title):21
+msgid "Gentoo SPARC Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(mail:link):8
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(mail):8
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(abstract):11
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(version):17
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(date):18
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(p):25
+msgid "As of 2004.0, the individual architecture-specific installation guides have been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/handbook/handbook-sparc.xml\">Gentoo Handbook</uri>. For more information please read up on the <uri link=\"/doc/en/handbook/\">Gentoo Handbook Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-sparc-netboot-howto.xml.pot b/doc/gettext/gentoo-sparc-netboot-howto.xml.pot
new file mode 100644
index 0000000..9050b0c
--- /dev/null
+++ b/doc/gettext/gentoo-sparc-netboot-howto.xml.pot
@@ -0,0 +1,611 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):6
+msgid "Gentoo Linux based Netboot HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(author:title):8
+msgid "SPARC Developer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(mail:link):9
+msgid "weeve"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(abstract):15
+msgid "Guide for setting up a netboot server for use with the Gentoo/SPARC netboot installation images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(version):24
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(date):25
+msgid "2010-10-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):32
+msgid "This howto is currently very SPARC-centric and expecting that you will be setting up your netboot server on an existing Gentoo Linux machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):37
+msgid "This document will describe how to setup a network booting environment for a Sun Microsystems SPARC or UltraSPARC based computer. The document assumes that you have an existing Gentoo Linux computer available to act as the netboot server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):44
+msgid "Both the netboot server and netboot client will need to be on the same network subnet, as the ARP protocol is typically not forwarded across different network subnets."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):50
+msgid "A generic overview of what happens during the netboot process is as follows;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):55
+msgid "Client machine sends out a reverse ARP (RARP) request to get an IP address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):58
+msgid "A server machine returns a response to the client with the IP address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):59
+msgid "The client then attempts to download a boot image from the RARP server using the TFTP protocol"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):63
+msgid "Once the image is downloaded, the netboot client then boots the image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):66
+msgid "Based on this overview, we will need to install software for a reverse ARP daemon and a TFTP daemon."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):76
+msgid "Software Installation And Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):78
+msgid "The Reverse ARP Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):81
+msgid "A reverse ARP daemon is already installed on your system; it's part of the <c>net-misc/iputils</c> package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):86
+msgid "<b>Setting up common rarpd elements</b>: <path>/etc/ethers</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):90
+msgid "You will need to setup the <path>/etc/ethers</path> file. This file indicates which hosts <c>rarpd</c> should respond to when a request is seen, and what address to reply with."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):96
+msgid "The format of <path>/etc/ethers</path> is the MAC address of the NIC the machine will be netbooting and its hostname. Whitespace delimits the MAC address from the hostname, and each entry should have its own line. The following example is for a host named sparc-netboot.gentoo.org:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):103
+msgid "Example /etc/ethers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):103
+#, no-wrap
+msgid "\n08:00:20:77:1f:3e  sparc-netboot.gentoo.org\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):107
+msgid "If a given hexadecimal number in the MAC address starts or is 0, you can chose to omit the first 0 (i.e. 08:00:20:77:1f:3e becomes 8:0:20:77:1f:3e)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):112
+msgid "If you desire to add additional hosts to <path>/etc/ethers</path>, you do not need to restart the <c>rarpd</c> services as the file is checked each time a request is received."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):118
+msgid "<b>Resolving hostnames</b>: <path>/etc/hosts</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):122
+msgid "Since each entry in <path>/etc/ethers</path> has a hostname, the netboot server needs to be able to resolve the hostname into its IP address. This can be done two ways, <path>/etc/hosts</path> or the nameserver the netboot server uses."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):128
+msgid "An <path>/etc/hosts</path> entry for resolving a hostname will look very similar to the one that probably exists from when you installed Gentoo on the netboot server. For our example host, sparc-netboot.gentoo.org, we'll assume that it has an IP address of 10.0.1.15. So the <path>/etc/hosts</path> entry would look like;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):136
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):136
+#, no-wrap
+msgid "\n10.0.1.15  sparc-netboot.gentoo.org\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):141
+msgid "Depending on the environment, you may need to consult your network administrator to get an appropriate IP address or addresses to netboot the host with."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):147
+msgid "If you use a nameserver, then the DNS server administrator will need to add a record for the hostname, in our example sparc-netboot.gentoo.org, to point to the appropriate IP address. Please consult your DNS server administrator and/or the documentation for the DNS server's DNS software for how to add the entry."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):154
+msgid "If both <path>/etc/hosts</path> and the nameserver have an entry for the host to be netbooted, <path>/etc/hosts</path> will be used first (granted the order of <path>/etc/nsswitch.conf</path> has not been changed from the default)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):164
+msgid "First, we will need to determine the options to use for <c>rarpd</c>. While there are more options than we'll cover here, these options should get you started As there is currently no <path>init.d</path> script for <c>rarpd</c>, an entry will need to be added to <path>/etc/conf.d/local.start</path> if you want to enable <c>rarpd</c> services at boot time. A sample entry is as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):172 ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):265
+msgid "/etc/conf.d/local.start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):172
+#, no-wrap
+msgid "\n/usr/sbin/rarpd -v -e eth0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):176
+msgid "An explanation of the above <c>rarpd</c> options (as taken from the man page):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):181
+msgid "<c>-v</c> Be verbose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):182
+msgid "<c>-e</c> Do not check for the presence of a boot image, reply if MAC address resolves to a valid IP address using <path>/etc/ethers</path> database and DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):187
+msgid "eth0 represents the interface <c>rarpd</c> should bind to"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):190
+msgid "For more options, consult <c>man 8 rarpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):197
+msgid "The tftpd Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):200
+msgid "Here there are three options for a TFTP daemon, <c>net-ftp/atftp</c>, <c>net-ftp/netkit-tftp</c> and <c>net-ftp/tftp-hpa</c>. You only need to install one of the TFTP daemons for proper operation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):210
+msgid "Each TFTP daemon will need a directory from which to serve files to tftp clients. The directory we will use for this howto will be <path>/tftpboot</path>. This will appear as the root (<path>/</path>) directory to the clients when requests are received. Additionally, we'll setup the system to run the TFTP daemon with the user and group <c>nobody</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):218
+msgid "If the directory you have chosen does not currently exist, it will need to be created with the <c>mkdir</c> command. The command for the example <path>/tftpboot</path> is:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):224
+msgid "Creating /tftpboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):224
+#, no-wrap
+msgid "\n# <i>/bin/mkdir /tftpboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):228
+msgid "Then we will need to change the owner of <path>/tftpboot</path> so that it is owned by user nobody and group <c>nobody</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):233
+msgid "Changing ownership"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):233
+#, no-wrap
+msgid "\n# <i>chown nobody:nobody /tftpboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):240
+msgid "The atftp Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):243
+msgid "First, install the <c>atftp</c> package as follows;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):247
+msgid "Installing atftp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):247
+#, no-wrap
+msgid "\n# <i>emerge atftp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):251
+msgid "After the <c>atftp</c> package has been installed, it will need to be configured. If tftpd services are desired at boot time, an entry to <path>/etc/conf.d/local.start</path> will need to be added as <c>atftp</c> has no <path>init.d</path>, <c>inetd</c> or <c>xinetd</c> scripts of its own. If you want to use <c>inetd</c> or <c>xinetd</c> for controlling the tftpd service, please see their respective man pages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):260
+msgid "Below is an example entry for <c>atftpd</c> in <path>/etc/conf.d/local.start</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):265
+#, no-wrap
+msgid "\n/usr/sbin/in.tftpd -v --daemon /tftpboot\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):269
+msgid "An explanation of the above options (as taken from the man page);"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):274
+msgid "<c>-v</c> Increase or set the logging level. No args will increase by one the current value. Default is LOG_NOTICE, see syslog(3) for log level. Current value range from 0 (LOG_EMERG) to 7 (LOG_DEBUG)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):279
+msgid "<c>--daemon</c> Run as a daemon. Do not use this option if atftpd is started by inetd."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):285
+msgid "For more options, consult <c>man 8 atftpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):292
+msgid "The netkit-tftp Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):295
+msgid "First, install the <c>netkit-tftp</c> package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):299
+msgid "Installing netkit-tftp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):299
+#, no-wrap
+msgid "\n# <i>emerge netkit-tftp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):303
+msgid "Second, install <c>sys-apps/xinetd</c> if it is not currently present. After the <c>netkit-tftp</c> and <c>sys-apps/xinetd</c> packages have been installed, <c>netkit-tftp</c> will need to be configured. <c>netkit-tftp</c> needs to be run from <c>xinetd</c>, however it does not provide example scripts of its own. A sample <c>xinetd</c> file is provided below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):311
+msgid "Sample /etc/xinetd.d/tftp file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):311
+#, no-wrap
+msgid "\nservice tftp\n{\n    protocol        = udp\n    port            = 69\n    socket_type     = dgram\n    wait            = yes\n    user            = nobody\n    group           = nobody\n    server          = /usr/sbin/in.tftpd\n    server_args     = /tftpboot\n    only_from       = 10.0.1.0\n    disable         = no\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):327
+msgid "This sample <c>xinetd</c> configuration file for tftp uses the line <c>disable = no</c>, which enables the service by default. This is opposite of the default way packages in Gentoo provide their respective <c>xinetd</c> configuration files, which have <c>disable</c> set to <c>yes</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):334
+msgid "An explanation of the above options which can be changed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):339
+msgid "<b>user</b>: the user in.tftpd requests are handled as"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):340
+msgid "<b>group</b>: the group in.tftpd requests are handled as"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):341
+msgid "<b>server_args</b>: the root directory for the TFTP daemon to serve files from"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):345
+msgid "<b>only_from</b>: tells xinetd which hosts to allow TFTP connections from"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):350
+msgid "Additional information on <c>xinetd</c> configuration files can be found in <c>man 5 xinetd.conf</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):355
+msgid "If <c>xinetd</c> is running, you can send it the HUP signal to have it re-read its configuration files:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):360
+msgid "Sending HUP signal to xinetd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):360
+#, no-wrap
+msgid "\n# <i>/bin/killall -HUP xinetd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):364
+msgid "If <c>xinetd</c> is not running, start it with the init.d command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):368
+msgid "Starting xinetd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):368
+#, no-wrap
+msgid "\n# <i>/etc/init.d/xinetd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):372
+msgid "For more information, consult <c>man 8 in.tftpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):379
+msgid "The tftp-hpa Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):382
+msgid "First, install the <c>tftp-hpa</c> package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):386
+msgid "Installing tftp-hpa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):386
+#, no-wrap
+msgid "\n# <i>emerge tftp-hpa</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):390
+msgid "<c>tftp-hpa</c> comes with an <path>init.d</path> and the accompanying <path>conf.d</path> configuration file. Check to make sure that INTFTPD_PATH and INTFTP_OPTS in <path>/etc/conf.d/in.tftpd</path> match those below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):396
+msgid "/etc/conf.d/in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):396
+#, no-wrap
+msgid "\nINTFTPD_PATH=\"/tftpboot\"\nINTFTPD_OPTS=\"-s -v -l ${INTFTPD_PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):401
+msgid "The TFTP daemon can then be started via the <path>init.d</path> script:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):405
+msgid "Starting in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):405
+#, no-wrap
+msgid "\n# <i>/etc/init.d/in.tftpd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):409
+msgid "For more options, consult <c>man 8 tftpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):418
+msgid "Preparing a tftpboot image for use by a client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):422
+msgid "Make sure you have an image you want to use for netbooting. Please check your <uri link=\"/main/en/mirrors.xml\">local</uri> Gentoo <uri link=\"http://distfiles.gentoo.org/experimental/sparc/tftpboot/sparc64/\">distfiles mirror</uri> for the appropriate image. We'll assume you are planning to boot using the <path>gentoo-sparc64-20100128.tftpboot</path> image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):430
+msgid "Once you have an image, copy the image into <path>/tftpboot</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):434
+msgid "Copying the image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):434
+#, no-wrap
+msgid "\n# <i>cp gentoo-sparc64-20100128.tftpboot /tftpboot</i>\n# <i>chmod 644 /tftpboot/gentoo-sparc64-20100128.tftpboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):439
+msgid "Now, when the netboot client makes a TFTP request, it looks for a file that is the hexadecimal number of its current IP address, and on some platforms an <path>.ARCH</path> suffix. The hexadecimal number should use <e>capital</e> characters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):446
+msgid "So for our example IP address, 10.0.1.15, let's look at its hexadecimal equivalent:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):451
+msgid "Convert to hexadecimal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):451
+#, no-wrap
+msgid "\n# <i>printf \"%.2X%.2X%.2X%.2X\\n\" 10 0 1 15</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):455
+msgid "Example IP address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):455
+#, no-wrap
+msgid "\ndecimal       10  0   1   15\nhexadecimal   0A  00  01  0F\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):460
+msgid "So for the example netboot client, it would look for a file named <path>0A00010F</path> when it tftpboots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):465
+msgid "Iif you are really, really lazy (like me), you can netboot the host to get the filename the client is looking for from the netboot server logs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):470
+msgid "Make sure that both the <c>rarpd</c> and TFTP daemon you've chosen are currently running, then boot the host as described below in <uri link=\"#netbootingclient\">Netbooting the client</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):476
+msgid "The client will appear to hang after the boot net command is issued. Then on the netboot server, check the system logs for an entry for <c>in.tftpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):481
+msgid "An example entry from a netboot server running <c>sysklogd</c> and <c>tftp-hpa</c> looks like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):486
+msgid "Log entry for netboot server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):486
+#, no-wrap
+msgid "\nJan  3 22:48:59 stargazer in.tftpd[8368]: RRQ from 10.0.1.15 filename 0A00010F\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):490
+msgid "The filename is shown above after \"filename\" in the log entry, which in this case is <path>0A00010F</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):495
+msgid "As a way to keep track of what netboot image you are using, and to allow multiple machines to use the same netboot image, you can use a soft link to create the file with the hexadecimal value. To create this using our sample sparc64 host and the <path>gentoo-sparc64-20100128.tftpboot</path>, use the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):503
+msgid "Linking the image files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):503
+#, no-wrap
+msgid "\n# <i>/bin/ln -s /tftpboot/gentoo-sparc64-20100128.tftpboot \\\n/tftpboot/0A00010F</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):508
+msgid "Now everything should be set for netbooting!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):517
+msgid "Netbooting the client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):521
+msgid "From OpenBoot PROM (OBP) on the SPARC, enter the command;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):525
+msgid "Booting OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):525
+#, no-wrap
+msgid "\nok <i>boot net</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):529
+msgid "Other methods for certain machines are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):533
+msgid "Booting OBP, alternative"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):533
+#, no-wrap
+msgid "\nok <i>boot net-tpe</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):537
+msgid "If your system doesn't present you with an OBP at boot time, you will either need to press the Stop and A key, or send a break signal via serial console before the system boots an OS. If your system cannot find an OS, it should either try to boot via the network interface (which is what we want), or leave you at an OBP prompt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):545
+msgid "This will initiate the networking booting process. A constantly changing string of hexadecimal digits should appear. When the image has finished loading, the kernel will take over and start the OS booting process. In the case of our sparc64 install image, you will be left at a shell prompt from which you can begin the install process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):558
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):566
+msgid "If the netboot server is a Gentoo Linux system and experiences problems after installing the rarpd and tftpd packages, please search the <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri> and <uri link=\"http://bugs.gentoo.org\">Gentoo Bugzilla</uri> to see if this problem has been encountered by anyone else. If it has not, or the solutions found do not work, then please open a new bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):579
+msgid "This is presumably because the file your system is trying to load from the tftpboot server is not available. On a SPARC system, you would probably see the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):585
+msgid "Booting appears to hang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):585
+#, no-wrap
+msgid "\nRebooting with command: boot\nBoot device: net  File and args:\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):590
+msgid "Double check that the file the client needs does exist in <path>/tftpboot</path>. You can confirm the filename it is requesting by looking in the system logs. Also, once this file exists, the client will try to load it. Sometimes, when the file is missing originally, it will freeze downloading the file once it appears. To resolve this, just get back to an OBP prompt, and issue the \"boot net\" command again. The host should then start downloading the tftpboot image and boot the OS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):605
+msgid "This could be due to a few different problems;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):610
+msgid "Make sure the entry in <path>/etc/ethers</path> exists for the client in question. If the MAC address is incorrect and/or the netboot server cannot resolve the hostname for the client, it cannot respond with the needed information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):616
+msgid "Verify that the network hub or switch the netboot server and client are connected to allow RARP traffic to flow freely. If the client's request cannot reach the server, or vice versa, the host will be unable to continue."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):622
+msgid "No one is responding to the RARPD request because no services are listening. Verify that the rarpd service is up and running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):626
+msgid "The client does not think its NIC has a link to the network hub/switch it is plugged into. Check to see if the NIC and the port on the network hub or switch has a link light. If the link light is on, check to see what the setting of tpe-link-test? is in OBP with the command; <c>printenv tpe-link-test?</c>. You should receive something like <path>tpe-link-test? false true</path>. The first column represents the parameter name, the second column shows the current value for the the parameter, and the third column shows the default value for the parameter. In the example above, we can see that the current value is false, which means that the client is not checking to see if the client and network hub or switch can establish a link before issuing its RARP request. Often times this can cause the problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):642
+msgid "To change the value of tpe-link-test? from an OBP prompt, issue the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):647
+msgid "Changing tpe-link-test value"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):647
+#, no-wrap
+msgid "\nok <i>setenv tpe-link-test? true</i>\ntpe-link-test? =      true\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):652
+msgid "This shows the value of tpe-link-test? is now true. Try netbooting the client again."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-sparc-obpreference.xml.pot b/doc/gettext/gentoo-sparc-obpreference.xml.pot
new file mode 100644
index 0000000..ae41cda
--- /dev/null
+++ b/doc/gettext/gentoo-sparc-obpreference.xml.pot
@@ -0,0 +1,405 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(guide:link):6
+msgid "/doc/en/gentoo-sparc-obpreference.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):7
+msgid "OpenBoot PROM (OBP) Reference"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(mail:link):10
+msgid "ciaranm@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(mail):10
+msgid "Ciaran McCreesh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(abstract):13
+msgid "The OpenBoot PROM (OBP) Reference provides a list of useful OBP commands that can help when booting, configuring and performing diagnostics upon Sun SPARC hardware and clones."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(version):20
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(date):21
+msgid "2004-08-27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):24
+msgid "About this Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):28
+msgid "This document provides a list of useful OBP commands that can be helpful when booting, configuring and performing diagnostics upon Sun SPARC hardware and clones."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):34
+msgid "Note that not all commands are available on all PROM versions. In particular, sun4c systems have a different input mode, and some JavaStation models are missing a lot of OBP functionality."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):40
+msgid "OBP is somewhat inconsistent when it comes to command names. Sometimes hyphens are used to seperate words, sometimes they are not. Some commands which display information start with or contain a dot (this is a FORTH convention)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):46
+msgid "The terms \"OBP\", \"OpenBoot PROM\" and \"PROM\" are used interchangably in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):56
+msgid "Entering OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):58
+msgid "Systems with Sun Keyboards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):61
+msgid "On regular Sun systems (and clones which use Sun keyboards), press <c>Stop+A</c> when the system boots to enter OBP. The <c>Stop</c> key is the top left key on the extra block of keys on the left hand side of the keyboards (on really old systems it might be marked <c>L1</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):68
+msgid "The <c>Stop+N</c> keyboard combination at boot will reset many systems to the default PROM settings. <c>Stop+D</c> will enable diagnostics on some boards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):76
+msgid "Over Serial Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):79
+msgid "To enter OBP over serial console, send a break. In minicom, do this by pressing <c>ctrl+A F</c>. In xc, use <c>ctrl+A B</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):87
+msgid "Systems with Non-Sun (PC Style) Keyboards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):90
+msgid "On systems with PC-style keyboards (such as JavaStations and some Ultra clones), <c>ctrl+break</c> or <c>alt+ctrl+break</c> is generally used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):95
+msgid "Note that on the JavaStation JK, <c>ctrl+break</c> will restart the box rather than enter PROM. To get at OBP, you will need to set jumper J1300 pins 7-8 on the mainboard."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):106
+msgid "Basic System Commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):108
+msgid "Halting and Restarting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):111
+msgid "The <c>power-off</c> command will halt the box and turn off power. This command is sometimes screwy on Ultra5/10 systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):116
+msgid "The <c>reset</c> command will perform a soft reset. If diagnostics are enabled, they will <e>not</e> be rerun. In some documents, this command is refered to as <c>reset-all</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):122
+msgid "The <c>boot</c> command boots the system. A parameter may be provided to override the default boot device -- this can be a full device name or a device alias such as <c>disk</c>, <c>cdrom</c> or <c>net</c>. Any additional arguments are passed to the bootloader or operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):132
+msgid "PROM and System Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):135
+msgid "The <c>.version</c> command will show the OBP version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):139
+msgid ".version output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):139
+#, no-wrap
+msgid "\n{0} ok .version\nRelease 3.7 Version 0 created 1997/01/09 13:06\nOBP 3.7.0 1997/01/09 13:06\nPOST 3.2.1 1996/12/20 03:01\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):146
+msgid "The <c>banner</c> command will show the system information banner."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):150
+msgid "banner output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):150
+#, no-wrap
+msgid "\n{0} ok banner\nSun Ultra 2 UPA/SBus (2 X UltraSPARC-II 296MHz), No Keyboard\nOpenBoot 3.7, 704 MB memory installed, Serial #9705521.\nEthernet address 8:0:20:94:18:31, Host ID: 80941831\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):157
+msgid "The <c>.speed</c> command will show bus speeds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):161
+msgid ".speed output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):161
+#, no-wrap
+msgid "\n{0} ok .speed\nCPU  Speed : 296.00 MHz\nUPA  Speed : 098.66 MHz\nSBus Speed : 025.00 MHz\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):171
+msgid "Device Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):174
+msgid "The <c>show-devs</c> command will give a list of devices available to the system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):179
+msgid "The <c>probe-scsi</c> command will show internal SCSI devices available to the system. The <c>probe-scsi-all</c> command will show both internal and external devices on every SCSI interface. After running either of these commands, you <e>must</e> issue a <c>reset-all</c> before trying to boot an operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):187
+msgid "probe-scsi-all output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):187
+#, no-wrap
+msgid "\n{0} ok probe-scsi-all\nThis command may hang the system if a Stop-A or halt command\nhas been executed.  Please type reset-all to reset the system\nbefore executing this command.\nDo you wish to continue? (y/n) y\n/sbus@1f,0/SUNW,fas@e,8800000\nTarget 1\n  Unit 0   Disk     SEAGATE ST34371W SUN4.2G74629710B00491\n                    Copyright (c) 1997 Seagate\n                    All rights reserved\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):200
+msgid "The <c>probe-ide</c> command is also available on IDE-based systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):204
+msgid "probe-ide output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):204
+#, no-wrap
+msgid "\nok probe-ide\n  Device 0  ( Primary Master )\n          ATA Model: ST320420A\n\n  Device 1  ( Primary Slave )\n          ATA Model: Maxtor 6E040L0\n\n  Device 2  ( Secondary Master )\n         Not Present\n\n  Device 3  ( Secondary Slave )\n         Not Present\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):224
+msgid "Environment Variables and Device Aliases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):226
+msgid "Getting and Setting Environment Variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):229
+msgid "Use <c>printenv</c> to get a list of environment variables. To see the value of a specific variable, use <c>printenv fnord</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):234
+msgid "To set a variable, use <c>setenv myvar the new value</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):238
+msgid "To restore a variable's default value, use <c>set-default blah</c>. To revert <e>all</e> variables to default, use <c>set-defaults</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):243
+msgid "Note that boolean variables usually end in a <c>?</c>, and that they are seperate from variables of the same name without the question mark. The values <c>true</c> and <c>false</c> are used for booleans."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):252
+msgid "Useful Environment Variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):255
+msgid "Some useful environment variables:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(th):261
+msgid "Variable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(th):262
+msgid "Meaning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):266
+msgid "Sets the baud rate and related settings used by the serial console. By default <c>9600,8,n,1,-</c> is used, meaning 9600 baud, 8 bits, no parity, one stop bit, no flow control."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):274
+msgid "By default OBP will automatically boot upon startup. Set this to <c>false</c> if you'd rather send the boot command manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):281
+msgid "When auto-booting, and when <c>boot</c> is issued with no arguments, this variable is used to determine the boot device. More than one value can be provided (space seperated), in which case each is tried in turn. Each value can be a full device path or a device alias."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):290
+msgid "As <c>boot-device</c>, but used when <c>diag-switch?</c> is enabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):296
+msgid "If set, network interfaces will use their own MAC rather than the system-wide MAC. This is consistent with how PCs behave, and in violation of the Ethernet specification."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):304
+msgid "If set, additional diagnostic checks will be run at power on. Note that this can take a <e>very</e> long time on SMP and / or HyperSparc systems. In addition, the <c>diag-device</c> variable will also be used to determine the boot device rather than <c>boot-device</c>. Some systems have a mainboard jumper or a switch on the front of the machine which forces this setting on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):318
+msgid "Getting and Setting Device Aliases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):321
+msgid "Device aliases can be used to simplify the arguments to many commands. Instead of typing <c>boot /sbus/SUNW,hme@e,8c00000</c>, for example, one could use <c>boot net</c>. A number of device aliases are defined by default on every system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):328
+msgid "To view all device aliases, use the <c>devalias</c> command. To view a specific alias, use <c>devalias whatever</c>. To set a device alias, use <c>devalias whatever newvalue</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):337
+msgid "Changing Monitor Resolutions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):340
+msgid "The <c>output-device</c> variable can be used to control which framebuffer is used, and at what resolution it is run, for PROM console. For example, to use the Creator card on an Ultra 1C or 2 at a resolution of 1024x768@76Hz:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):346
+msgid "Changing Monitor Settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):346
+#, no-wrap
+msgid "\n{0} ok devalias screen /SUNW,ffb\n{0} ok setenv output-device screen:r1024x768x76\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):351
+msgid "Changes will not take effect until after a reset. Not all resolutions and refresh are available on all cards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):361
+msgid "Diagnostics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):363
+msgid "Entering Diagnostic Mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):366
+msgid "Before running any diagnostics, it is best to enable <c>diag-switch?</c> and do a full power off / on cycle (hard power off). Additional diagnostic information will be provided over the serial console when the machine boots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):375
+msgid "Basic Tests"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):378
+msgid "If the power on self test (POST) succeeds, additional tests can be performed using the <c>test</c>, <c>test-all</c>, <c>watch-net</c> and <c>watch-clock</c> commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):384
+msgid "The <c>test somedevice</c> command will perform checks upon the specified device (this can be a full device path or a device alias)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):389
+msgid "Example Tests"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):389
+#, no-wrap
+msgid "\n{0} ok test scsi\n        CE DMA fill from address fff8e000 for 80 bytes   succeeded.\n         Dma register test -- succeeded.\n         Esp register test -- succeeded.\n         Dma read test -- succeeded.\n         Dma write test -- succeeded.\n{0} ok test /sbus/SUNW,hme\nInternal loopback test -- succeeded.\nTransceiver check  -- Using Onboard Transceiver - Link Up.\npassed\n{0} ok test ttya\n !\"#$%&amp;'()*+,-./0123456789:;&lt;=&gt;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmn\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):404
+msgid "The <c>test-all</c> command will perform checks upon every device capable of self tests."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):409
+msgid "The <c>watch-net</c> command can be used to watch for broadcast packets being sent over the network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):414
+msgid "The <c>watch-clock</c> command can be used to verify that the internal clock is working. It should count from 0 to 59 in a loop with an interval of one second."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):423
+msgid "Extended Diagnostics Using obdiag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(note):426
+msgid "The <c>obdiag</c> routines are only available on the Ultra 5/10 and later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):430
+msgid "To enable extended diagnostics mode, run the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):434
+msgid "Entering obdiag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):434
+#, no-wrap
+msgid "\nok setenv mfg-mode on\nmfg-mode =            on\nok setenv diag-switch? true\ndiag-switch? =        true\nok setenv auto-boot? false\nauto-boot? =          false\nok reset-all\nok obdiag\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):445
+msgid "This should display a menu. First, select <c>16</c> to enable verbose messages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):450
+msgid "obdiag menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):450
+#, no-wrap
+msgid "\n          OBDiag Menu\n\n  0 ..... PCI/Cheerio\n  1 ..... EBUS DMA/TCR Registers\n  2 ..... Ethernet\n  3 ..... Keyboard\n  4 ..... Mouse\n  5 ..... Floppy\n  6 ..... Parallel Port\n  7 ..... Serial Port A\n  8 ..... Serial Port B\n  9 ..... NVRAM\n 10 ..... Audio\n 11 ..... EIDE\n 12 ..... Video\n 13 ..... All Above\n 14 ..... Quit\n 15 ..... Display this Menu\n 16 ..... Toggle script-debug\n 17 ..... Enable External Loopback Tests\n 18 ..... Disable External Loopback Tests\n\n Enter (0-13 tests, 14 -Quit, 15 -Menu) ===&gt; 16\n Enter (0-13 tests, 14 -Quit, 15 -Menu) ===&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):477
+msgid "Individual tests can then be run by selecting the relevant number. Note that some tests (for example, serial ports) assume that an external loopback connector is attached. The Ethernet test assumes that a cable is attached and connected to a switch."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):484
+msgid "To exit, use <c>14</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):492
+msgid "References"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(li):497
+msgid "OpenBoot 3.x Quick Reference, Sun P/N 802-3240 (<uri link=\"http://sunsolve.sun.com/data/802/802-3240/pdf/802-3240-10.pdf\">PDF Version)</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(li):502
+msgid "OpenBoot 3.x Command Reference, Sun P/N 802-3242 (<uri link=\"http://sunsolve.sun.com/data/802/802-3242/html/TOC.html\">HTML Version)</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(li):507
+msgid "OpenBoot 3.x Supplement for PCI, Sun P/N 802-7679 (<uri link=\"http://sunsolve.sun.com/data/802/802-7679/pdf/\">Collection of PDF files)</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(li):512
+msgid "<uri link=\"http://firmworks.com/QuickRef.html\">Open Firmware Quick Reference</uri> (Not Sun OBP specific)"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-upgrading.xml.pot b/doc/gettext/gentoo-upgrading.xml.pot
new file mode 100644
index 0000000..706de04
--- /dev/null
+++ b/doc/gettext/gentoo-upgrading.xml.pot
@@ -0,0 +1,596 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(guide:link):5
+msgid "/doc/en/gentoo-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):6
+msgid "Gentoo Upgrading Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail:link):9
+msgid "greg_g@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail):9
+msgid "Gregorio Guidi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail:link):12
+msgid "wolf31o2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail):12
+msgid "Chris Gianelloni"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail:link):15
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail):15
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(abstract):18
+msgid "This document explains how new Gentoo releases affect existing installs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(version):26
+msgid "2.11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(date):27
+msgid "2008-07-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):30
+msgid "Gentoo and Upgrades"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):32
+msgid "Philosophy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):35
+msgid "Here in Gentoo land, the concept of upgrading is quite different compared to the rest of the Linux world. You probably already know that we never got in touch with the \"classic\" way of upgrading software: waiting for a new release, downloading it, burning, putting it in the cdrom drive and then following the upgrade instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):43
+msgid "You know (being a Gentoo user after all) that this process is extremely frustrating for power users that want to live on the bleeding edge. Even power users from other distributions probably share the same feelings, given the popularity and spread of tools like apt or apt-rpm which make it possible to have quick and frequent updates. However, no distribution is more suited than Gentoo to satisfy these kind of demanding users. From the beginning, Gentoo was designed around the concept of fast, incremental updates."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):54
+msgid "Ideally, you install once and never bother with releases: just follow the instructions in <uri link=\"/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1\">A Portage Introduction</uri> in the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri> that explain how to keep your system up to date. While that's the way things usually go, sometimes changes are made to the core system which require updates to be done manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):67
+msgid "Releases and Profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):70
+msgid "A recurring question about the Gentoo release process is: \"Why roll out new releases frequently, if they are not intended to let users update software?\" There are various reasons:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(li):77
+msgid "A new release means new Installation CDs with bugfixes and more features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(li):80
+msgid "A new release provides an updated set of GRP packages, so that users that choose \"the fast way\" to install (stage3 + precompiled packages) end up with a system that is not outdated"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(li):85
+msgid "Finally, a new release may, from time to time, implement some features that are incompatible with previous releases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):91
+msgid "When a release includes new incompatible features, or provides a set of core packages and settings that deeply modify the behavior of the system, we say that it provides a new <e>profile</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):97
+msgid "A <e>profile</e> is a set of configuration files, stored in a subdirectory of <path>/usr/portage/profiles</path>, that describe things such as the ebuilds that are considered <e>system</e> packages, the default USE flags, the default mapping for virtual packages, and the architecture on which the system is running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):104
+msgid "The profile in use is determined by the symbolic link <path>/etc/make.profile</path>, which points to a subdirectory of <path>/usr/portage/profiles</path> which holds the profile files. For instance, the default x86 2008.0 profile can be found at <path>/usr/portage/profiles/default/linux/x86/2008.0</path>. The files in the parent directories are part of the profile as well (and are therefore shared by different subprofiles). This is why we call these <e>cascaded profiles</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):115
+msgid "Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> along with the current ones, but they are marked as deprecated. When that happens a file named <path>deprecated</path> is put in the profile directory. The content of this file is the name of the profile that should be \"upgraded to\"; Portage uses this information to automatically warn you when you should update to a new profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):124
+msgid "There are various reasons that a new profile may be created: the release of new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or <c>glibc</c>) that are incompatible with previous versions, a change in the default USE flags or in the virtual mappings, or maybe a change in system-wide settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):137
+msgid "Keeping up with new releases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):139
+msgid "Releases without profile changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):142
+msgid "If a new Gentoo release does not include a new profile then you can safely pretend that it never happened. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):147
+msgid "If you update your installed packages <uri link=\"/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1\">as explained in the Gentoo Handbook</uri>, then your system will be exactly the same as one that has been installed using the new release."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):157
+msgid "Releases with profile changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):160
+msgid "If a release (such as 2008.0 for x86) introduces a new profile, you have the choice to migrate to the new profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):165
+msgid "Naturally, you are not forced to do so, and you can continue to use the old profile and just update your packages <uri link=\"/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1\">as explained in the Gentoo Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):172
+msgid "However, Gentoo strongly recommends updating your profile if it becomes deprecated. When this happens, it means that Gentoo developers no longer plan on supporting it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):178
+msgid "If you decide to migrate to the new profile, then you will have to manually perform the update. The way you update may vary significantly from release to release; it depends on how deep the modifications introduced in the new profile are."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):185
+msgid "In the simplest case you only have to change the <path>/etc/make.profile</path> symlink, in the worst case you may have to recompile your system from scratch while doing a neat voodoo dance. Migration is usually covered in the release notes. You can also find <uri link=\"#instructions\">instructions</uri> at the end of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):196
+msgid "Supported profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):199
+msgid "You can view the list of profiles on your architecture officially supported by Gentoo developers when you <c>emerge eselect</c> and then run the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):205
+msgid "Viewing supported profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):205
+#, no-wrap
+msgid "\n# <i>eselect profile list</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):214
+msgid "Profile updating instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):216
+msgid "General instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(impo):219
+msgid "Make sure your Portage is updated before performing any profile changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):223
+msgid "First, run <c>emerge eselect</c>. The <c>eselect</c> utility will let you view and select profiles easily, without needing to create or remove symlinks by hand."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):229
+msgid "Profile selection with eselect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):229
+#, no-wrap
+msgid "\n<comment>(View available profiles)</comment>\n# <i>eselect profile list</i>\n\n<comment>(Select the number of your desired profile from the list)</comment>\n# <i>eselect profile set &lt;number&gt;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):237
+msgid "If you'd still prefer to change profiles manually, then simply do the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):241
+msgid "Changing profiles manually"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):241 ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):315 ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):365 ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):526
+#, no-wrap
+msgid "\n# <i>rm /etc/make.profile</i>\n# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(note):246
+msgid "There are <b>desktop</b> and <b>server</b> subprofiles for most architectures. Examine these profiles carefully, as they may serve your needs better than the extremely minimal default profiles."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(note):252
+msgid "The <c>developer</c> subprofile is specifically for Gentoo Linux development tasks. It is <e>not</e> meant to help set up general development environments."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):260
+msgid "Updating to 2008.0, 2007.0, or 2006.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):263
+msgid "If you intend to upgrade to these profiles, you should be aware that they expect the system to be set to a Unicode locale by default; specifically that UNICODE=\"yes\" is set in <path>/etc/rc.conf</path>. For this to work, you must have created a Unicode locale for your system to use. Please read our <uri link=\"/doc/en/utf-8.xml\">UTF-8 guide</uri> to learn how to create the proper locale."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):272
+msgid "Alternatively, if you do not wish to set a locale, you should specify UNICODE=\"no\" in <path>/etc/rc.conf</path>, and re-emerge <c>baselayout</c> (or wait until your next <c>baselayout</c> update) with the <c>-unicode</c> USE flag. You can set <c>-unicode</c> just for <c>baselayout</c>, or you can set it globally for all packages by adding it to your USE variable in <path>/etc/make.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):281
+msgid "Optional: removing Unicode support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):281
+#, no-wrap
+msgid "\n<comment>(To remove Unicode support just for baselayout)</comment>\n# <i>echo \"sys-apps/baselayout -unicode\" &gt;&gt; /etc/portage/package.use</i>\n# <i>emerge -a baselayout</i>\n\n<comment>(To remove Unicode support from your whole system)</comment>\n# <i>nano -w /etc/make.conf</i>\nUSE=\"-unicode\"\n# <i>emerge -a baselayout</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(note):292
+msgid "If you are updating to a 2007.0 profile on the Sparc architecture, then you will need to follow the <uri link=\"/doc/en/gcc-upgrading.xml\">GCC Upgrading Guide</uri>, as <c>gcc-4</c> is the default compiler."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):298
+msgid "Finally, follow the <uri link=\"#general\">general instructions</uri> for updating your profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):306
+msgid "Updating to 2006.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):309
+msgid "To switch to the 2006.0 profile, point the <path>/etc/make.profile</path> symlink to the new location. Make sure your Portage is updated before you change your profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):315
+msgid "Changing to a 2006.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):320
+msgid "<b>alpha</b> - Users that use a 2.4 kernel or don't want to use NPTL should use the default-linux/alpha/no-nptl profile. More information is available in <uri link=\"/proj/en/releng/release/2006.0/alpha-release-notes.xml\">the alpha release notes</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):327
+msgid "<b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The ppc32 profile has been changed in a way that offers a minimalistic generic profile for all purposes, located in default-linux/ppc/ppc32. The release-dependent profile is optimized for desktop-usage and located in default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop Workstation. Make sure you choose the correct subprofile for your system when migrating to a 2006.0 profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):338
+msgid "<b>sparc</b> - Upgrading to the <b>2.4</b>-kernel based 2006.0/2.4 profile requires manual user intervention (unmerging java stuff) and an <c>emerge -e world</c> because of the <uri link=\"/doc/en/gcc-upgrading.xml\">gcc upgrade</uri>.<br/> Upgrading to the <b>2.6</b>-kernel based 2006.0 profile which is not considered stable also requires an entry in <path>/etc/portage/package.unmask</path> to umask a 2.6 version of <c>gentoo-sources</c> and a full rebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):348
+msgid "<b>All other archs</b> - There are no fundamental changes in this profile. No specific action needs to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):356
+msgid "Updating to 2005.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):359
+msgid "To switch to the 2005.1 profile, point the <path>/etc/make.profile</path> symlink to the new location. Make sure your Portage is updated before you change your profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):365
+msgid "Changing to a 2005.1 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):370
+msgid "<b>All archs</b> - There are no fundamental changes in this profile. No specific action needs to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):375
+msgid "<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged and a number of subprofiles for specific subarchitectures were created. Make sure you choose the correct subprofile for your system when migrating to a 2005.1 profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):385
+msgid "Updating to 2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):388
+msgid "With the introduction of 2005.0, several architectures have decided to define additional profiles. Make sure you read the description of said profiles before you decide to migrate to one of them. Most architectures now also default to the 2.6 kernel tree where 2.4 was chosen previously."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):395
+msgid "Some architectures require a bit more actions to be completed in order to convert from one profile to another. If that is the case, the step-by-step guides are linked from the table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(th):403
+msgid "Profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(th):404
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(th):405
+msgid "Specific Upgrade Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):408
+msgid "default-linux/alpha/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):409
+msgid "Default Alpha 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):413
+msgid "default-linux/alpha/2005.0/2.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):414
+msgid "Alpha 2005.0 profile for 2.4 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):418
+msgid "default-linux/amd64/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):419
+msgid "Default AMD64 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):423
+msgid "default-linux/amd64/2005.0/no-multilib"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):424
+msgid "AMD64 2005.0 profile for multilib-disabled system installations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):428
+msgid "default-linux/arm/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):429
+msgid "Default ARM 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):433
+msgid "default-linux/hppa/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):434
+msgid "Default HPPA 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):438
+msgid "default-linux/hppa/2005.0/2.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):439
+msgid "HPPA 2005.0 profile for 2.4 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):443
+msgid "default-linux/mips/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):444
+msgid "Default MIPS 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):448
+msgid "default-linux/mips/cobalt/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):449
+msgid "Cobalt specific MIPS 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):453
+msgid "default-linux/mips/mips64/n32/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):454
+msgid "2005.0 profile for n32-supporting MIPS platforms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):458
+msgid "default-linux/mips/mips64/ip28/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):459
+msgid "Indigo2 Impact specific 64-bit 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):463
+msgid "default-linux/mips/mips64/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):464
+msgid "64-bit MIPS 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):468
+msgid "default-linux/ppc/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):469
+msgid "Default PPC 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):473
+msgid "default-linux/ppc64/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):474
+msgid "Default PPC64 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):478
+msgid "default-linux/s390/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):479
+msgid "Default S390 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):483
+msgid "default-linux/sparc/sparc32/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):484
+msgid "Default Sparc 32-bit 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):496
+msgid "default-linux/sparc/sparc64/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):497
+msgid "Default Sparc 64-bit 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):509
+msgid "default-linux/x86/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):510
+msgid "Default x86 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):514
+msgid "default-linux/x86/2005.0/2.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):515
+msgid "x86 2005.0 profile for 2.4 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):520
+msgid "To switch to the selected profile, point the <path>/etc/make.profile</path> symlink to the new location. Make sure your Portage is updated before you change your profile!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):526
+msgid "Changing to a 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):531
+msgid "If you are running a Linux 2.4-based system but want to migrate to a 2.6-based kernel, make sure you read our <uri link=\"/doc/en/migration-to-2.6.xml\">Gentoo Linux 2.6 Migration Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):540
+msgid "Updating to 2004.3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):543
+msgid "With the introduction of the 2004.3 profiles, users are not going to see huge modifications of their systems (see below for details). However, Gentoo developers decided to push out this new profile and to deprecate quite a few of the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the profiles that follow the new layout of the <path>/usr/portage/profiles</path> directory, for instance <path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by Portage 2.0.51 or later)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):554
+msgid "To switch to the 2004.3 profile, point the <path>/etc/make.profile</path> symlink to the new location:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(warn):559 ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(warn):624
+msgid "Don't forget to upgrade Portage <e>before</e> you change your profile!!!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):563 ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):628 ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):659
+msgid "Updating the /etc/make.profile symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):563
+#, no-wrap
+msgid "\n<comment>substitute &lt;arch&gt; with your arch</comment>\n# <i>rm /etc/make.profile</i>\n# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):569
+msgid "<b>All archs</b> - As said above, there are no big changes introduced in this profile. However, it should be noted that <c>sys-apps/slocate</c> and <c>net-misc/dhcpcd</c> are no longer considered system packages. This means that if you run <c>emerge --depclean</c>, Portage will try to remove them from your system. If you need any of those packages, add them to <path>/var/lib/portage/world</path> after the profile switch, or manually emerge them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):579
+msgid "<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/devfs</c> for newly installed machines. This has no effect on already installed machines, though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):588
+msgid "Updating Portage to Support Cascading Profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):591
+msgid "Although this section does not seem to integrate well in this upgrading guide, it is quite important. Any profile listed above this section requires a Portage version that supports cascading profiles. However, some obsoleted profiles don't allow the user to upgrade Portage or the user is using a profile that isn't available anymore - any attempt to upgrade Portage will result in a failure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):599
+msgid "To work around this problem, users can set a temporary symbolic link to the <e>obsolete</e> profile, allowing them to upgrade their Portage after which they can continue with the upgrade procedure set forth in this guide. Please substitute <c>&lt;arch&gt;</c> with your respective architecture:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):606
+msgid "Updating Portage through the obsolete profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):606
+#, no-wrap
+msgid "\n# <i>rm /etc/make.profile</i>\n# <i>cd /etc</i>\n# <i>ln -sf ../usr/portage/profiles/obsolete/&lt;arch&gt; make.profile</i>\n# <i>emerge -n '&gt;=sys-apps/portage-2.0.51'</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):616
+msgid "Updating to 2004.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):619
+msgid "To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink to the new location:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):628
+#, no-wrap
+msgid "\n<comment>substitute &lt;arch&gt; with your arch</comment>\n# <i>rm /etc/make.profile</i>\n# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):634
+msgid "<b>x86</b> - This profile changes the default X11 implementation from <c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches the <e>default</e> value, and is only relevant for those who have not installed an X server yet. If you already have one installed, then it will not affect you at all; you are free to switch from one X server to the other exactly as before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):643
+msgid "<b>amd64</b> - There are no fundamental changes from previous profiles, no specific action needs to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):651
+msgid "Updating to 2004.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):654
+msgid "To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> symlink to the new location:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):659
+#, no-wrap
+msgid "\n<comment>substitute &lt;arch&gt; with your arch</comment>\n# <i>rm /etc/make.profile</i>\n# <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):665
+msgid "<b>All archs</b> - There are no fundamental changes from previous profiles, no specific action needs to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):673
+msgid "Updating from profiles older than 1.4 to 1.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):676
+msgid "The instructions for this upgrade are quite complex, you can find them <uri link=\"/doc/en/new-upgrade-to-gentoo-1.4.xml\">here</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-x86+raid+lvm2-quickinstall.xml.pot b/doc/gettext/gentoo-x86+raid+lvm2-quickinstall.xml.pot
new file mode 100644
index 0000000..d5a9a1d
--- /dev/null
+++ b/doc/gettext/gentoo-x86+raid+lvm2-quickinstall.xml.pot
@@ -0,0 +1,309 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):6
+msgid "Gentoo Linux x86 with Software Raid and LVM2 Quick Install Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(key):9
+msgid "yes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(key):10
+msgid "/dev/md3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(author:title):13 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(author:title):16 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(author:title):19
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(mail:link):14
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(mail:link):17
+msgid "swift"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(author):19
+msgid "Steven Wagner"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(abstract):21
+msgid "The Quick Install guide covers the Gentoo install process in a non-verbose manner. Its purpose is to allow users to perform a stage3 install with software RAID and LVM2 in no time. Users should already have prior experience with installing Gentoo Linux if they want to follow this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(version):32
+msgid "16"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(date):33
+msgid "2010-06-15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):36
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):40
+msgid "This guide contains all commands you should use to complete a stage3 installation including LVM2 on top of software RAID. This guide is targeted at experienced users. You need a connection to the Internet to download the stage3 and Portage snapshots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(impo):47
+msgid "New users should read the <uri link=\"/doc/en/handbook/index.xml\">Handbook</uri> as it gives a better overview about the installation process. The Quick Install guide is designed for experienced users who just need a checklist to follow."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):53
+msgid "Timing output follows all commands that take more than a couple of seconds to finish. Commands were timed on an AMD 2000 1.66 Ghz PC with 512 Mb of RAM and two SATA disks connected to a hardware controller configured as JBOD (i.e. two separate hard disks are seen by Gentoo). If you have a \"hardware\" RAID controller on your motherboard, it is most likely <b>not</b> a hardware controller."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):62
+msgid "Test box specs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):62
+#, no-wrap
+msgid "\n<comment>(The following specs and the timing information should help you determine\na rough estimate of the time you need to complete your install)</comment>\n\n# <i>grep bogo /proc/cpuinfo</i>\nbogomips       : 3337.81\n\n# <i>hdparm -tT /dev/sda /dev/sdb</i>\n/dev/sda:\nreads:   1048 MB in  2.00 seconds = 524.00 MB/sec\n Timing buffered disk reads:  152 MB in  3.01 seconds =  50.50 MB/sec\n\n/dev/sdb:\n Timing cached reads:   1048 MB in  2.00 seconds = 524.00 MB/sec\n Timing buffered disk reads:  152 MB in  3.01 seconds =  50.50 MB/sec\n\n# <i>grep MemTotal /proc/meminfo</i>\nMemTotal:       509248 kB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):87
+msgid "Quick Install Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):92
+msgid "Preparing the Disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):95
+msgid "Load the software RAID and LVM2 modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):99
+msgid "Load RAID and LVM2 modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):99
+#, no-wrap
+msgid "\nlivecd ~ # <i>modprobe raid0</i>\nlivecd ~ # <i>modprobe raid1</i>\n<comment>(raid5, raid6 and raid10 are also available)</comment>\n\nlivecd ~ # <i>modprobe dm-mod</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):107
+msgid "Use <c>fdisk</c> or <c>cfdisk</c> to create your partition layout. The device names are likely to be either <path>/dev/sda</path> and <path>/dev/sdb</path> for a SATA or SCSI disks, or <path>/dev/hda</path> and <path>/dev/hdb</path> for IDE disks. The following layout will be used in this guide:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):119
+msgid "Type"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):125 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):137
+msgid "Raid-1 (mirroring)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):129 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):130
+msgid "swap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):131
+msgid "Normal partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):141
+msgid "LVM2 volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):142
+msgid "Raid-0 (striped)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(impo):146
+msgid "The partition you boot from must not be striped. It may not be raid-5 or raid-0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(note):151
+msgid "On the one hand, if you want extra stability, consider using raid-1 (or even raid-5) for your swap partition(s) so that a drive failure would not corrupt your swap space and crash applications that are using it. On the other hand, if you want extra performance, just let the kernel use distinct swap partitions as it does striping by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):159
+msgid "Create the partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):159
+#, no-wrap
+msgid "\nlivecd ~ # <i>fdisk /dev/sda</i>\n<comment>(Make sure you use type fd and set the bootable flag)</comment>\n\n<comment>(The rest of this guide uses the following partitioning scheme)</comment>\nlivecd ~ # <i>fdisk -l /dev/sda</i>\n\nDisk /dev/sda: 299.9 GB, 299989204992 bytes\n255 heads, 63 sectors/track, 36471 cylinders\nUnits = cylinders of 16065 * 512 = 8225280 bytes\n\n   Device Boot      Start         End      Blocks   Id  System\n/dev/sda1   *           1          11       88326   fd  Linux raid autodetect\n/dev/sda2              12          61      401625   82  Linux swap / Solaris\n/dev/sda3              62         311     2008125   fd  Linux raid autodetect\n/dev/sda4             312       36471   290455200   fd  Linux raid autodetect\n\n<comment>(Partition the second disk exactly as the first)</comment>\nlivecd ~ # <i>fdisk /dev/sdb</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):180
+msgid "Then create the RAID device nodes and devices. Please bear in mind that the <c>/boot</c> and <c>/</c> mount points should use an older metadata format which can be specified by the <c>--metadata=0.90</c> flag:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):186
+msgid "Create device nodes and devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):186
+#, no-wrap
+msgid "\nlivecd ~ # <i>mknod /dev/md1 b 9 1</i>\nlivecd ~ # <i>mknod /dev/md3 b 9 3</i>\nlivecd ~ # <i>mknod /dev/md4 b 9 4</i>\n\nlivecd ~ # <i>mdadm --create /dev/md1 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 /dev/sdb1</i>\nmdadm: array /dev/md1 started.\nlivecd ~ # <i>mdadm --create /dev/md3 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3</i>\nmdadm: array /dev/md3 started.\nlivecd ~ # <i>mdadm --create /dev/md4 --level=0 --raid-devices=2 /dev/sda4 /dev/sdb4</i>\nmdadm: array /dev/md4 started.\n\n<comment>(Wait until all units are ready)</comment>\nlivecd ~ # <i>cat /proc/mdstat</i>\nPersonalities : [raid0] [raid1]\nmd4 : active raid0 sdb4[1] sda4[0]\n581006592 blocks 64k chunks\n\nmd3 : active raid1 sdb3[1] sda3[0]\n1959808 blocks [2/2] [UU]\n\nmd1 : active raid1 sdb1[1] sda1[0]\n88256 blocks [2/2] [UU]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):211
+msgid "Then create the LVM2 volumes in <path>/dev/md4</path>. The following scheme is used as an <b>example</b>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):218
+msgid "Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):219
+msgid "Size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):220
+msgid "File system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):223
+msgid "/usr"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):224
+msgid "8 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):225 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):240 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):245 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):250
+msgid "ext3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):228
+msgid "/usr/portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):229 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):259
+msgid "2 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):230
+msgid "ext2, small block size, many inodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):233
+msgid "/usr/portage/distfiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):234 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):244 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):249
+msgid "4 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):235
+msgid "ext2, large block size, less inodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):238
+msgid "/home"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):239
+msgid "10 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):243
+msgid "/opt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):248
+msgid "/var"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):253
+msgid "/var/tmp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):254
+msgid "6 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):255 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):260
+msgid "ext2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):258
+msgid "/tmp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):264
+msgid "Create LVM2 volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):264
+#, no-wrap
+msgid "\nlivecd ~ # <i>vgscan</i>\n  Reading all physical volumes.  This may take a while...\n  No volume groups found\nlivecd ~ # <i>vgchange -a y</i>\n  No volume groups found\n\n<comment>(Create physical volumes, we have only one in our example)</comment>\nlivecd ~ # <i>pvcreate /dev/md4</i>\n  Physical volume \"/dev/md4\" successfully created\n\n<comment>(Create volume groups, again, we have only one in our example)</comment>\nlivecd ~ # <i>vgcreate vg /dev/md4</i>\n  Volume group \"vg\" successfully created\n\n<comment>(Create logical volumes)</comment>\nlivecd ~ # <i>lvcreate -L8G -nusr vg</i>\n  /dev/cdrom: open failed: Read-only file system\n  Logical volume \"usr\" created <comment>(Further similar messages not displayed)</comment>\nlivecd ~ # <i>lvcreate -L2G -nportage vg</i>\nlivecd ~ # <i>lvcreate -L4G -ndistfiles vg</i>\nlivecd ~ # <i>lvcreate -L10G -nhome vg</i>\nlivecd ~ # <i>lvcreate -L4G -nopt vg</i>\nlivecd ~ # <i>lvcreate -L4G -nvar vg</i>\nlivecd ~ # <i>lvcreate -L6G -nvartmp vg</i>\nlivecd ~ # <i>lvcreate -L2G -ntmp vg</i>\n\n<comment>(Display volume groups and logical volumes)</comment>\nlivecd ~ # <i>vgs</i>\n  VG   #PV #LV #SN Attr  VSize   VFree\n  vg     1   8   0 wz--n 554.09G 514.09G\nlivecd ~ # <i>lvs</i>\n  LV        VG   Attr   LSize  Origin Snap%  Move Copy%\n  distfiles vg   -wi-a-  4.00G\n  home      vg   -wi-a- 10.00G\n  opt       vg   -wi-a-  4.00G\n  portage   vg   -wi-a-  2.00G\n  tmp       vg   -wi-a-  2.00G\n  usr       vg   -wi-a-  8.00G\n  var       vg   -wi-a-  4.00G\n  vartmp    vg   -wi-a-  6.00G\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):307
+msgid "Use <c>mke2fs</c>, <c>mke2fs -j</c>, <c>mkreiserfs</c>, <c>mkfs.xfs</c> and <c>mkfs.jfs</c> to create file systems. Initialize swap using <c>mkswap</c> and <c>swapon</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):313
+msgid "Create the file systems and activate swap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):313
+#, no-wrap
+msgid "\n<comment>(ext2 is all you need on the /boot partition)</comment>\nlivecd ~ # <i>mke2fs /dev/md1</i>\n\n<comment>(Let's use ext3 on the root partition)</comment>\nlivecd ~ # <i>mke2fs -j /dev/md3</i>\n\n<comment>(Create file systems on logical volumes)</comment>\nlivecd ~ # <i>mke2fs -b 4096 -T largefile /dev/vg/distfiles</i>\nlivecd ~ # <i>mke2fs -j /dev/vg/home</i>\nlivecd ~ # <i>mke2fs -j /dev/vg/opt</i>\nlivecd ~ # <i>mke2fs -b 1024 -N 200000 /dev/vg/portage</i>\nlivecd ~ # <i>mke2fs /dev/vg/tmp</i>\nlivecd ~ # <i>mke2fs -j /dev/vg/usr</i>\nlivecd ~ # <i>mke2fs -j /dev/vg/var</i>\nlivecd ~ # <i>mke2fs /dev/vg/vartmp</i>\n\n<comment>(Create and activate swap)</comment>\nlivecd ~ # <i>mkswap /dev/sda2 &amp;&amp; mkswap /dev/sdb2</i>\nlivecd ~ # <i>swapon -p 1 /dev/sda2 &amp;&amp; swapon -p 1 /dev/sdb2</i>\n<comment>(Check that all swap partitions use the same priority)</comment>\nlivecd ~ # <i>swapon -v -s</i>\nFilename                   Type            Size    Used    Priority\n/dev/sda2                  partition       401616  0       1\n/dev/sdb2                  partition       401616  0       1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):340
+msgid "Mount the freshly created file systems on <path>/mnt/gentoo</path>. Create directories for the other mount points and mount them too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):345
+msgid "Mount the file systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):345
+#, no-wrap
+msgid "\nlivecd ~ # <i>mount /dev/md3 /mnt/gentoo</i>\nlivecd ~ # <i>cd /mnt/gentoo</i>\nlivecd gentoo # <i>mkdir boot home usr opt var tmp</i>\nlivecd gentoo # <i>mount /dev/md1 /mnt/gentoo/boot</i>\nlivecd gentoo # <i>mount /dev/vg/usr /mnt/gentoo/usr</i>\nlivecd gentoo # <i>mount /dev/vg/home /mnt/gentoo/home</i>\nlivecd gentoo # <i>mount /dev/vg/opt /mnt/gentoo/opt</i>\nlivecd gentoo # <i>mount /dev/vg/tmp /mnt/gentoo/tmp</i>\nlivecd gentoo # <i>mount /dev/vg/var /mnt/gentoo/var</i>\nlivecd gentoo # <i>mkdir usr/portage var/tmp</i>\nlivecd gentoo # <i>mount /dev/vg/vartmp /mnt/gentoo/var/tmp</i>\nlivecd gentoo # <i>mount /dev/vg/portage /mnt/gentoo/usr/portage</i>\nlivecd gentoo # <i>mkdir usr/portage/distfiles</i>\nlivecd gentoo # <i>mount /dev/vg/distfiles /mnt/gentoo/usr/portage/distfiles</i>\n\n<comment>(Set proper perms on tmp directories)</comment>\nlivecd gentoo # <i>chmod 1777 /mnt/gentoo/tmp /mnt/gentoo/var/tmp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):373
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):376
+msgid "Install a kernel source (usually <c>gentoo-sources</c>), configure it, compile it and copy the <path>arch/i386/boot/bzImage</path> file to <path>/boot</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):381
+msgid "Install a kernel source, compile it and install the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):381
+#, no-wrap
+msgid "\nlivecd etc # <i>time emerge gentoo-sources</i>\n\nreal  3m3.110s\nuser  1m2.320s\nsys   0m34.990s\nlivecd etc # <i>cd /usr/src/linux</i>\nlivecd linux # <i>make menuconfig</i>\n\n<comment>(Configure your kernel as usual and make sure the raid and lvm modules you need are\ncompiled in, i.e. <b>not</b> as modules. The same applies to the disk drivers and filesystems.)</comment>\nMulti-device support (RAID and LVM)  ---&gt;\n[*] Multiple devices driver support (RAID and LVM)\n  &lt;*&gt;   RAID support\n  &lt; &gt;     Linear (append) mode (NEW)\n  &lt;*&gt;     RAID-0 (striping) mode\n  &lt;*&gt;     RAID-1 (mirroring) mode\n  &lt; &gt;     RAID-10 (mirrored striping) mode (EXPERIMENTAL) (NEW)\n  &lt; &gt;     RAID-4/RAID-5 mode (NEW)\n  &lt; &gt;     RAID-6 mode (NEW)\n  &lt; &gt;     Multipath I/O support (NEW)\n  &lt; &gt;     Faulty test module for MD (NEW)\n  &lt;*&gt;   Device mapper support\n  &lt; &gt;     Crypt target support (NEW)\n  &lt; &gt;     Snapshot target (EXPERIMENTAL) (NEW)\n  &lt; &gt;     Mirror target (EXPERIMENTAL) (NEW)\n  &lt; &gt;     Zero target (EXPERIMENTAL) (NEW)\n  &lt; &gt;     Multipath target (EXPERIMENTAL) (NEW)\n  &lt; &gt;     Bad Block Relocation Device Target (EXPERIMENTAL) (NEW)\n\nlivecd linux # <i>time make -j2</i>\n\n<comment>(Elapsed time depends highly on the options you selected)</comment>\nreal  5m5.869s\nuser  4m32.320s\nsys   0m32.930s\n\nlivecd linux # <i>make modules_install</i>\nlivecd linux # <i>cp arch/i386/boot/bzImage /boot/kernel</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):430 ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):437
+msgid "Reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):433
+msgid "Exit the chrooted environment, unmount all file systems and reboot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):437
+#, no-wrap
+msgid "\nlivecd conf.d # <i>exit</i>\nlivecd / # <i>umount /mnt/gentoo/usr/portage/distfiles /mnt/gentoo/usr/portage \\\n/mnt/gentoo/usr /mnt/gentoo/var/tmp /mnt/gentoo/tmp /mnt/gentoo/var \\\n/mnt/gentoo/opt /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo/home \\\n/mnt/gentoo/boot /mnt/gentoo</i>\nlivecd / # <i>reboot</i>\n<comment>(Don't forget to remove the CD)</comment>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-x86-install.xml.pot b/doc/gettext/gentoo-x86-install.xml.pot
new file mode 100644
index 0000000..ccf2b4c
--- /dev/null
+++ b/doc/gettext/gentoo-x86-install.xml.pot
@@ -0,0 +1,56 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(guide:link):5
+msgid "/doc/en/gentoo-x86-install.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(guide:redirect):5
+msgid "/doc/en/handbook/handbook-x86.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(title):6 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(title):22
+msgid "Gentoo x86 Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(abstract):12
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(version):18
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(date):19
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(p):26
+msgid "As of 2004.0, the individual architecture-specific installation guides have been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/handbook/handbook-x86.xml\">Gentoo Handbook</uri>. For more information please read up on the <uri link=\"/doc/en/handbook/\">Gentoo Handbook Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-x86-quickinstall-after-reboot.xml.pot b/doc/gettext/gentoo-x86-quickinstall-after-reboot.xml.pot
new file mode 100644
index 0000000..fe3d8a8
--- /dev/null
+++ b/doc/gettext/gentoo-x86-quickinstall-after-reboot.xml.pot
@@ -0,0 +1,165 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(version):7
+msgid "5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(date):8
+msgid "2010-10-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(title):11
+msgid "Finalizing the Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(note):14
+msgid "The <b>total</b> elapsed time between the display of the boot prompt on the minimal CD and the display of the login prompt after the reboot was <b>00:42:31</b> on our test box. Yes, less than one hour! Note that this time also includes the stage3, Portage snapshot and several packages download time and the time spent configuring the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):22
+msgid "Log in as <c>root</c>, then add one or more users for daily use with <c>useradd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):27
+msgid "Connect to your new box from another PC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):27
+#, no-wrap
+msgid "\n<comment>(Clean up your known_hosts file because your new box\nhas generated a new definitive hostkey)</comment>\n$ <i>nano -w ~/.ssh/known_hosts</i>\n<comment>(Look for the IP of your new PC and delete the line,\nthen save the file and exit nano)</comment>\n\n<comment>(Use the IP address of your new box)</comment>\n$ <i>ssh root@192.168.1.10</i>\nThe authenticity of host '192.168.1.10 (192.168.1.10)' can't be established.\nRSA key fingerprint is 96:e7:2d:12:ac:9c:b0:94:90:9f:40:89:b0:45:26:8f.\nAre you sure you want to continue connecting (yes/no)? <i>yes</i>\nWarning: Permanently added '192.168.1.10' (RSA) to the list of known hosts.\nPassword: <comment>type_the_password</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):43
+msgid "Add a new user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):43
+#, no-wrap
+msgid "\nmybox ~ # <i>useradd -g users -G lp,wheel,audio,cdrom,portage,cron -m john</i>\nmybox ~ # <i>passwd john</i>\nNew UNIX password: <comment>Set John's password</comment>\nRetype new UNIX password: <comment>Type John's password again</comment>\npasswd: password updated successfully\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(title):54
+msgid "Last configuration touches"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):57
+msgid "Start by selecting nearby mirrors either by defining the <c>SYNC</c> and <c>GENTOO_MIRRORS</c> variables in <path>/etc/make.conf</path> or by using <c>mirrorselect</c>. You can also define the number of concurrent compilation processes at this point."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):64
+msgid "Use mirrorselect and set MAKEOPTS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):64
+#, no-wrap
+msgid "\nmybox ~ # <i>emerge mirrorselect</i>\nmybox ~ # <i>mirrorselect -i -o &gt;&gt; /etc/make.conf</i>\nmybox ~ # <i>mirrorselect -i -r -o &gt;&gt; /etc/make.conf</i>\n<comment>(Usually, (the number of processors + 1) is a good value)</comment>\nmybox ~ # <i>echo 'MAKEOPTS=\"-j2\"' &gt;&gt; /etc/make.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):72
+msgid "Now is a good time to enable or disable some USE flags. Run <c>emerge -vpe world</c> to list all currently installed packages and their enabled and disabled USE flags. Either edit <path>/etc/make.conf</path> or use the following command to define the USE variable:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):79
+msgid "View USE flags in use and enable or disable some"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):79
+#, no-wrap
+msgid "\nmybox ~ # <i>emerge -vpe world</i>\n<comment>(Portage displays the packages and their USE flags, as an example, let's\ndisable ipv6 and fortran, and enable unicode)</comment>\nmybox ~ # <i>echo 'USE=\"nptl nptlonly -ipv6 -fortran unicode\"' &gt;&gt; /etc/make.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):86
+msgid "Recent versions of glibc use <path>/etc/locale.gen</path> to define locale settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):91
+msgid "Define locales"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):91
+#, no-wrap
+msgid "\nmybox ~ # <i>cd /etc</i>\nmybox etc # <i>nano -w locale.gen</i>\nmybox etc # <i>locale-gen</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):97
+msgid "Last but not least, you may want to alter the <c>CFLAGS</c> variable in your <path>/etc/make.conf</path> to optimise the code to your specific needs. Please note that using a long list of flags is rarely needed and can even lead to a broken system. It is recommended to specify the processor type in the <c>march</c> option and stick to <c>-O2 -pipe</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):105
+msgid "You may also want to switch to <b>~x86</b>. You should only do this if you can deal with the odd broken ebuild or package. If you'd rather keep your system stable, <e>don't</e> add the <c>ACCEPT_KEYWORDS</c> variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):111
+msgid "Last edit of make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):111
+#, no-wrap
+msgid "\nmybox etc # <i>nano -w make.conf</i>\n<comment>(Set -march to your CPU type in CFLAGS)</comment>\nCFLAGS=\"-O2 -march=<i>athlon-xp</i> -pipe\"\n<comment>(Only add the following if you know what you're doing)</comment>\nACCEPT_KEYWORDS=\"~x86\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):119
+msgid "You might want to recompile your whole system twice to make full use of your latest configuration changes. It would take quite a long time to complete and yield minimal speed benefits. You can let your system optimise itself gradually over time when new versions of packages are released. However, recompiling is a still good idea from the standpoint of maintaining system consistency. Please see the <uri link=\"/doc/en/gcc-upgrading.xml\">Gentoo GCC Upgrading Guide</uri> for a discussion on the benefits of ensuring a consistently built system and world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):130
+msgid "Recompiling only the packages that have already been updated since the release or that are affected by your new USE flags will take enough time. You might also have to remove packages that block your upgrade. Look for \"[blocks <brite>B</brite> ]\" in the output of <c>emerge -vpuD --newuse world</c> and use <c>emerge -C</c> to remove them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):138
+msgid "Update your packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):138
+#, no-wrap
+msgid "\n<comment>(Please note that the switch to ~x86 causes many packages to be upgraded)</comment>\nmybox etc # <i>emerge -vpuD --newuse world</i>\n<comment>(Take a good look at the package list and their USE flags,\nremove blocking packages if any, and start the lengthy process)</comment>\nmybox etc # <i>time emerge -vuD --newuse world</i>\n<comment>(79 packages have been (re)compiled)</comment>\n\nreal  180m13.276s\nuser  121m22.905s\nsys   36m31.472s\n\n<comment>(Remerge libtool to avoid further potential problems)</comment>\nmybox etc # <i>emerge --oneshot libtool</i>\n\n<comment>(Update config files, make sure you <b>do not</b> let dispatch-conf\nupdate config files you have edited)</comment>\nmybox etc # <i>dispatch-conf</i>\n\n<comment>(If perl has been updated, you should run the perl-cleaner script)</comment>\nmybox etc # <i>time perl-cleaner all</i>\nreal  1m6.495s\nuser  0m42.699s\nsys   0m10.641s\n\n<comment>(In case of a major upgrade of python, you should run the python-updater script)</comment>\nmybox etc # <i>python-updater</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(title):170
+msgid "What to do next"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):173
+msgid "Depending on what your new Gentoo machine is supposed to do, you will probably want to install server applications or a desktop system. Just as an example, <c>emerge gnome</c> and <c>emerge kde</c> have been timed on the ~x86 system installed as describe above. Both have been installed from the same starting point."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):181
+msgid "You should check our <uri link=\"/doc/en/\">documentation index</uri> to find out how to install and configure the applications of your choice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(impo):186
+msgid "The following is only an example. It is in no way meant as a recommended setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):190
+msgid "Emerge GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):190
+#, no-wrap
+msgid "\nmybox etc # <i>emerge -vp gnome</i>\n<comment>(Look at the list of packages and their USE flags,\nthen edit make.conf if required.</comment>\nmybox etc # <i>nano -w /etc/make.conf</i>\n<comment>(The following USE flags have been defined)</comment>\nUSE=\"nptl nptlonly -ipv6 -fortran unicode svg hal dbus \\\n     -kde -qt4 -arts -eds -esd gnome gstreamer gtk firefox\"\n\nmybox etc # <i>time emerge gnome</i>\n<comment>(326 packages have been emerged)</comment>\n\nreal  520m44.532s\nuser  339m21.144s\nsys   146m22.337s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):207
+msgid "Emerge KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):207
+#, no-wrap
+msgid "\nmybox etc # <i>emerge -vp kde-meta</i>\n<comment>(Look at the list of packages and their USE flags,\nthen edit make.conf if required.</comment>\nmybox etc # <i>nano -w /etc/make.conf</i>\n<comment>The following USE flags have been defined)</comment>\nUSE=\"nptl nptlonly -ipv6 -fortran unicode svg hal dbus \\\n     kde qt4 -arts -eds -esd -gnome -gstreamer -gtk -firefox\"\n\nmybox etc # <i>time emerge kde-meta</i>\n<comment>(391 packages have been emerged)</comment>\n\nreal  1171m25.318s\nuser  851m26.393s\nsys   281m45.629s\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-x86-quickinstall-media.xml.pot b/doc/gettext/gentoo-x86-quickinstall-media.xml.pot
new file mode 100644
index 0000000..e0e75b2
--- /dev/null
+++ b/doc/gettext/gentoo-x86-quickinstall-media.xml.pot
@@ -0,0 +1,155 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(version):7
+msgid "5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(date):8
+msgid "2009-10-04"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):11
+msgid "Installation Media"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):14
+msgid "Download a CD from one of our <uri link=\"/main/en/mirrors.xml\">mirrors</uri>. You can find the minimal CD ISO in <path>releases/x86/current-iso/</path>. The <e>minimal</e> installation CD is only useful for Internet-based installations. This guide will use the minimal CD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):21
+msgid "<uri link=\"/doc/en/faq.xml#isoburning\">Burn</uri> the CD and boot it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):28
+msgid "Booting the CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):31
+msgid "Press <c>F2</c> at the boot screen to find out what boot options exist. You can either start <c>gentoo</c> or <c>gentoo-nofb</c>, the latter disables the framebuffer. If you booted the LiveCD, don't forget to add the <c>nox</c> option to prevent the X graphical environment from starting. Several options allow to enable or disable some features. If all goes well, your hardware will be detected and all modules will be loaded. If the kernel fails to boot properly or if your computer hangs during the boot procedure, you may have to experiment with different configurations. The safest way is probably to use the <c>nodetect</c> option and then load required modules explicitly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):43
+msgid "Boot the minimal CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):43
+#, no-wrap
+msgid "\nGentoo Linux Installation LiveCD                     http://www.gentoo.org\nEnter to Boot; F1 for kernels  F2 for options.\nboot: <i>gentoo-nofb</i>\n  <comment>(or in case of problems)</comment>\nboot: <i>gentoo-nofb nodetect</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):54
+msgid "Optional: loading modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):57
+msgid "If you used the <c>nodetect</c> option, once booted, load the required modules. You need to enable networking and have access to your disks. The <c>lspci</c> command can help you identify your hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):63
+msgid "Load required modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):63
+#, no-wrap
+msgid "\nlivecd root # <i>lspci</i>\n<comment>(Use lspci's output to identify required modules)</comment>\n\n<comment>(The following is an example, adapt it to your hardware)</comment>\nlivecd root # <i>modprobe 3w-9xxx</i>\nlivecd root # <i>modprobe r8169</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):75
+msgid "Network Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):78
+msgid "If your network does not work already, you can use <c>net-setup</c> to configure your network. You might need to load support for your network card using <c>modprobe</c> prior to the configuration. If you have ADSL, use <c>pppoe-setup</c> and <c>pppoe-start</c>. For PPTP support, first edit <path>/etc/ppp/chap-secrets</path> and <path>/etc/ppp/options.pptp</path> and then use <c>pptp &lt;server&nbsp;ip&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):87
+msgid "For wireless access, use <c>iwconfig</c> to set the wireless parameters and then use either <c>net-setup</c> again or run <c>ifconfig</c>, <c>dhcpcd</c> and/or <c>route</c> manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):93
+msgid "If you are behind a proxy, do not forget to initialize your system using <c>export http_proxy</c>, <c>ftp_proxy</c> and <c>RSYNC_PROXY</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):98
+msgid "Configure networking the guided way"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):98
+#, no-wrap
+msgid "\nlivecd root # <i>net-setup eth0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):102
+msgid "Alternatively, you can start networking manually. The following example assigns the IP address 192.168.1.10 to your PC and defines 192.168.1.1 as your router and name server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):108
+msgid "Configure networking the manual way"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):108
+#, no-wrap
+msgid "\nlivecd root # <i>ifconfig eth0 192.168.1.10/24</i>\nlivecd root # <i>route add default gw 192.168.1.1</i>\nlivecd root # <i>echo nameserver 192.168.1.1 &gt; /etc/resolv.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):114
+msgid "The installation CD allows you to start an <c>sshd</c> server, add additional users, run <c>irssi</c> (a command-line chat client) and surf the web using <c>links</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):123
+msgid "Optional: connect to your new box over ssh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):126
+msgid "The most interesting feature is of course <c>sshd</c>. You can start it and then connect from another machine and cut and paste commands from this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):131
+msgid "Start sshd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):131
+#, no-wrap
+msgid "\nlivecd root # <i>time /etc/init.d/sshd start</i>\n * Generating hostkey ...\n<comment>(sshd generates the key and displays more output)</comment>\n * starting sshd ...                            [ok]\n\nreal   0m13.688s\nuser   0m9.420s\nsys    0m0.090s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):142
+msgid "Now, set the root password on the liveCD so that you can connect to it from another PC. Please note that allowing root to connect over ssh is not recommended under normal circumstances. If you can't trust your local network, use a long and complex password, you should use it only once as it will disappear after your first reboot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):150
+msgid "Set the root password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):150
+#, no-wrap
+msgid "\nlivecd root # <i>passwd</i>\nNew UNIX password: <comment>type_a_password</comment>\nRetype new UNIX password: <comment>type_a_password</comment>\npasswd: password updated successfully\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):157
+msgid "Now, you can start a terminal on another PC and connect to your new box, follow the rest of this guide in another window, and cut and paste commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):162
+msgid "Connect to your new box from another PC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):162
+#, no-wrap
+msgid "\n<comment>(Use the IP address of your new box)</comment>\n$ <i>ssh root@192.168.1.10</i>\nThe authenticity of host '192.168.1.10 (192.168.1.10)' can't be established.\nRSA key fingerprint is 96:e7:2d:12:ac:9c:b0:94:90:9f:40:89:b0:45:26:8f.\nAre you sure you want to continue connecting (yes/no)? <i>yes</i>\nWarning: Permanently added '192.168.1.10' (RSA) to the list of known hosts.\nPassword: <comment>type_the_password</comment>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-x86-quickinstall-stage.xml.pot b/doc/gettext/gentoo-x86-quickinstall-stage.xml.pot
new file mode 100644
index 0000000..ebd1c0b
--- /dev/null
+++ b/doc/gettext/gentoo-x86-quickinstall-stage.xml.pot
@@ -0,0 +1,140 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(version):7
+msgid "10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(date):8
+msgid "2009-10-04"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(title):11
+msgid "Setting Up The Stage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):14
+msgid "First make sure your date and time is set correctly using <c>date MMDDhhmmYYYY</c>. Use UTC time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):19
+msgid "Set the date and UTC time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):19
+#, no-wrap
+msgid "\n<comment>(Check the clock)</comment>\nlivecd gentoo # <i>date</i>\nMon Mar  6 00:14:13 UTC 2006\n\n<comment>(Set the current date and time if required)</comment>\nlivecd gentoo # <i>date 030600162006</i> <comment>(Format is MMDDhhmmYYYY)</comment>\nMon Mar  6 00:16:00 UTC 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):29
+msgid "Next, download a stage from one of our <uri link=\"/main/en/mirrors.xml\">mirrors</uri>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):34
+msgid "Download a stage3 archive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):34
+#, no-wrap
+msgid "\nlivecd gentoo # <i>links http://www.gentoo.org/main/en/mirrors.xml</i>\n<comment>(Pick a mirror, move to the releases/x86/current-stage3/ directory, highlight the stage3 of your choice, probably the i686 stage3 and press D to download it)</comment>\n\n<comment>(<b>Or</b> download it directly with wget without choosing a nearby mirror)</comment>\nlivecd gentoo # <i>wget ftp://distfiles.gentoo.org/pub/gentoo/releases/x86/current-stage3/stage3-i686-*.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):42
+msgid "Go to <path>/mnt/gentoo</path> and unpack the stage using <c>tar xjpf &lt;stage3 tarball&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):47
+msgid "Unpack the stage3 archive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):47
+#, no-wrap
+msgid "\nlivecd gentoo # <i>time tar xjpf stage3*</i>\n\nreal  1m14.157s\nuser  1m2.920s\nsys   0m7.530s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):55
+msgid "Install the latest Portage snapshot. Proceed as for the stage3 archive: choose a nearby mirror from our <uri link=\"/main/en/mirrors.xml\">list</uri>, download the latest snapshot and unpack it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):61
+msgid "Download the latest Portage snapshot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):61
+#, no-wrap
+msgid "\nlivecd gentoo # <i>cd /mnt/gentoo/usr</i>\nlivecd usr # <i>links http://www.gentoo.org/main/en/mirrors.xml</i>\n<comment>(Pick a mirror, move to the snapshots/ directory,\nhighlight <b>portage-latest.tar.bz2</b> and press D to download it)</comment>\n\n<comment>(<b>Or</b> download it directly with wget without choosing a nearby mirror)</comment>\nlivecd gentoo # <i>cd /mnt/gentoo/usr</i>\nlivecd usr # <i>wget http://distfiles.gentoo.org/snapshots/portage-latest.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):72
+msgid "Unpack the Portage snapshot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):72
+#, no-wrap
+msgid "\nlivecd usr # <i>time tar xjf portage-lat*</i>\n\nreal  0m40.523s\nuser  0m28.280s\nsys   0m8.240s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(title):83
+msgid "Chrooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):86
+msgid "Mount the <path>/proc</path> &amp; <path>/dev</path> file systems, copy over the <path>/etc/resolv.conf</path> file, then chroot into your Gentoo environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):92
+msgid "Chroot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):92
+#, no-wrap
+msgid "\nlivecd usr # <i>cd /</i>\nlivecd / # <i>mount -t proc proc /mnt/gentoo/proc</i>\nlivecd / # <i>mount -o bind /dev /mnt/gentoo/dev</i>\nlivecd / # <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/</i>\nlivecd / # <i>chroot /mnt/gentoo /bin/bash</i>\nlivecd / # <i>env-update &amp;&amp; source /etc/profile</i>\n&gt;&gt;&gt; Regenerating /etc/ld.so.cache...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(title):105
+msgid "Set your time zone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):108
+msgid "Set your time zone information by using the correct listing in <path>/usr/share/zoneinfo</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):113
+msgid "Setting your timezone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):113
+#, no-wrap
+msgid "\nlivecd / # <i>ls /usr/share/zoneinfo</i>\n<comment>(Using Brussels as an example)</comment>\nlivecd / # <i>cp /usr/share/zoneinfo/Europe/Brussels /etc/localtime</i>\n\nlivecd / # <i>date</i>\nWed Mar  8 00:46:05 CET 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(title):125
+msgid "Set your host name and domain name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):128
+msgid "Set your host name in <path>/etc/conf.d/hostname</path> and <path>/etc/hosts</path>. In the following example, we use <c>mybox</c> as host name and <c>at.myplace</c> as domain name. You can either edit the config files with <c>nano</c> or use the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):135
+msgid "Set host and domain name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):135
+#, no-wrap
+msgid "\nlivecd / # <i>cd /etc</i>\nlivecd etc # <i>echo \"127.0.0.1 mybox.at.myplace mybox localhost\" &gt; hosts</i>\nlivecd etc # <i>sed -i -e 's/HOSTNAME.*/HOSTNAME=\"mybox\"/' conf.d/hostname</i>\n<comment>(Use defined host name and check)</comment>\nlivecd etc # <i>hostname mybox</i>\nlivecd etc # <i>hostname -f</i>\nmybox.at.myplace\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-x86-quickinstall-system.xml.pot b/doc/gettext/gentoo-x86-quickinstall-system.xml.pot
new file mode 100644
index 0000000..7289539
--- /dev/null
+++ b/doc/gettext/gentoo-x86-quickinstall-system.xml.pot
@@ -0,0 +1,197 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(version):7
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(date):8
+msgid "2008-03-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):11
+msgid "Configure the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):15
+msgid "Edit your <path>/etc/fstab</path> and replace <c>BOOT</c>, <c>ROOT</c> and <c>SWAP</c> with the actual partition names. Don't forget to check that the file systems match your installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):21 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):38
+msgid "Example fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):21
+#, no-wrap
+msgid "\nlivecd linux # <i>cd /etc</i>\nlivecd etc # <i>nano -w fstab</i>\n/dev/<i>sda1</i>   /boot     ext2    noauto,noatime     1 2\n/dev/<i>sda3</i>   /         ext3    noatime            0 1\n/dev/<i>sda2</i>   none      swap    sw                 0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):32
+msgid "Edit your <path>/etc/fstab</path> and replace <c>BOOT</c>, <c>ROOT</c> and <c>SWAP</c> with the actual partition names and add your logical volumes. Don't forget to check that the file systems match your installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):38
+#, no-wrap
+msgid "\nlivecd linux # <i>cd /etc</i>\nlivecd etc # <i>nano -w fstab</i>\n/dev/<i>md1</i>          /boot                   ext2  noauto,noatime  1 2\n/dev/<i>md3</i>          /                       ext3  noatime         0 1\n/dev/<i>sda2</i>         none                    swap  sw,pri=1        0 0\n/dev/<i>sdb2</i>         none                    swap  sw,pri=1        0 0\n/dev/vg/usr       /usr                    ext3  noatime         1 2\n/dev/vg/portage   /usr/portage            ext2  noatime         1 2\n/dev/vg/distfiles /usr/portage/distfiles  ext2  noatime         1 2\n/dev/vg/home      /home                   ext3  noatime         1 2\n/dev/vg/opt       /opt                    ext3  noatime         1 2\n/dev/vg/tmp       /tmp                    ext2  noatime         1 2\n/dev/vg/var       /var                    ext3  noatime         1 2\n/dev/vg/vartmp    /var/tmp                ext2  noatime         1 2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):58
+msgid "Configure your network in <path>/etc/conf.d/net</path>. Add the <c>net.eth0</c> init script to the default run level. If you have multiple NICs, symlink them to the <c>net.eth0</c> init script and add them to the default run level as well. Either edit <path>/etc/conf.d/net</path> with <c>nano</c> or use the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):66
+msgid "Configure networking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):66
+#, no-wrap
+msgid "\nlivecd etc # <i>cd conf.d</i>\nlivecd conf.d # <i>echo 'config_eth0=( \"192.168.1.10/24\" )' &gt;&gt; net</i>\nlivecd conf.d # <i>echo 'routes_eth0=( \"default via 192.168.1.1\" )' &gt;&gt; net</i>\nlivecd conf.d # <i>rc-update add net.eth0 default</i>\n<comment>(If you compiled your network card driver as a module,\nadd it to /etc/modules.autoload.d/kernel-2.6)</comment>\nlivecd conf.d # <i>echo r8169 &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n<comment>(If you want to reconnect via ssh after you have rebooted your new box)</comment>\nlivecd conf.d # <i>rc-update add sshd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):78
+msgid "Emerge <c>pcmciautils</c> if you need support for PCMCIA cards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):82
+msgid "Set the root password using <c>passwd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):86
+msgid "Set the root password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):86
+#, no-wrap
+msgid "\nlivecd conf.d # <i>passwd</i>\nNew UNIX password: <comment>type_the_password</comment>\nRetype new UNIX password: <comment>type_the_password_again</comment>\npasswd: password updated successfully\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):93
+msgid "Edit <path>/etc/conf.d/clock</path> to define the time zone you used previously."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):98
+msgid "Edit /etc/conf.d/clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):98
+#, no-wrap
+msgid "\nlivecd conf.d # <i>nano -w /etc/conf.d/clock</i>\nTIMEZONE=\"Europe/Brussels\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):103
+msgid "Check the system configuration in <path>/etc/rc.conf</path>, <path>/etc/conf.d/rc</path>, <path>/etc/conf.d/keymaps</path> and edit any of those files if required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):109
+msgid "Optional: edit some config files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):109
+#, no-wrap
+msgid "\nlivecd conf.d # <i>nano -w /etc/rc.conf</i>\nlivecd conf.d # <i>nano -w /etc/conf.d/rc</i>\nlivecd conf.d # <i>nano -w /etc/conf.d/keymaps</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):118
+msgid "Installing System Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):122
+msgid "Install RAID and LVM2 utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):126
+msgid "Install RAID LVM2 tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):126
+#, no-wrap
+msgid "\nlivecd conf.d # <i>emerge mdadm lvm2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):133
+msgid "Install a system logger like <c>syslog-ng</c> and a cron daemon like <c>vixie-cron</c>, and add them to the default run level."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):138
+msgid "Cron daemons depend on an MTA. <c>mail-mta/ssmtp</c> will be pulled in as a dependency. If you want to use a more advanced MTA, you might want to install it now. If you are in a hurry, let ssmtp be installed and remove it later when you install the MTA of your choice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):145
+msgid "Install a syslogger and a cron daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):145
+#, no-wrap
+msgid "\nlivecd conf.d # <i>time emerge syslog-ng vixie-cron</i>\n\nreal  1m54.099s\nuser  1m2.630s\nsys   0m34.620s\nlivecd conf.d # <i>rc-update add syslog-ng default</i>\nlivecd conf.d # <i>rc-update add vixie-cron default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):155
+msgid "Install the necessary file system tools (<c>xfsprogs</c>, <c>reiserfsprogs</c> or <c>jfsutils</c>) and networking tools (<c>dhcpcd</c> or <c>ppp</c>) if you need any."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):161
+msgid "Install extra tools if required"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):161
+#, no-wrap
+msgid "\nlivecd conf.d # <i>emerge xfsprogs</i>       <comment>(If you use the XFS file system)</comment>\nlivecd conf.d # <i>emerge jfsutils</i>       <comment>(If you use the JFS file system)</comment>\nlivecd conf.d # <i>emerge reiserfsprogs</i>  <comment>(If you use the Reiser file system)</comment>\nlivecd conf.d # <i>emerge dhcpcd</i>         <comment>(If you need a DHCP client)</comment>\nlivecd conf.d # <i>emerge ppp</i>            <comment>(If you need PPPoE ADSL connectivity)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):173
+msgid "Configuring the Bootloader"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):176
+msgid "Emerge <c>grub</c> and configure it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):180
+msgid "Emerge grub and edit its configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):180
+#, no-wrap
+msgid "\nlivecd conf.d # <i>time emerge grub</i>\n\nreal  1m4.634s\nuser  0m39.460s\nsys   0m15.280s\nlivecd conf.d # <i>nano -w /boot/grub/grub.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):189
+msgid "Example grub.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):189
+#, no-wrap
+msgid "\ndefault 0\ntimeout 10\n\ntitle Gentoo\nroot (hd0,0)\nkernel /boot/kernel root=<keyval id=\"root\"></keyval>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):198
+msgid "Install grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):198
+#, no-wrap
+msgid "\nlivecd conf.d # <i>grub</i>\nProbing devices to guess BIOS drives. This may take a long time.\n\ngrub&gt; <i>root (hd0,0)</i>\n Filesystem type is ext2fs, partition type 0xfd\n\ngrub&gt; <i>setup (hd0)</i>\n Checking if \"/boot/grub/stage1\" exists... yes\n Checking if \"/boot/grub/stage2\" exists... yes\n Checking if \"/boot/grub/e2fs_stage1_5\" exists... yes\n Running \"embed /boot/grub/e2fs_stage1_5 (hd0)\"...  16 sectors are embedded.\nsucceeded\n Running \"install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/\ngrub/menu.lst\"... succeeded\nDone.\n\ngrub&gt; <i>quit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):218
+msgid "Install grub on both disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):218
+#, no-wrap
+msgid "\nlivecd conf.d # <i>grub</i>\nProbing devices to guess BIOS drives. This may take a long time.\n\ngrub&gt; <i>root (hd0,0)</i>\n Filesystem type is ext2fs, partition type 0xfd\n\ngrub&gt; <i>setup (hd0)</i>\n Checking if \"/boot/grub/stage1\" exists... yes\n Checking if \"/boot/grub/stage2\" exists... yes\n Checking if \"/boot/grub/e2fs_stage1_5\" exists... yes\n Running \"embed /boot/grub/e2fs_stage1_5 (hd0)\"...  16 sectors are embedded.\nsucceeded\n Running \"install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/\ngrub/menu.lst\"... succeeded\nDone.\n\ngrub&gt; <i>root (hd1,0)</i>\n Filesystem type is ext2fs, partition type 0xfd\n\ngrub&gt; <i>setup (hd1)</i>\n\ngrub&gt; <i>quit</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-x86-quickinstall.xml.pot b/doc/gettext/gentoo-x86-quickinstall.xml.pot
new file mode 100644
index 0000000..dddeba1
--- /dev/null
+++ b/doc/gettext/gentoo-x86-quickinstall.xml.pot
@@ -0,0 +1,158 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):6
+msgid "Gentoo Linux x86 Quick Install Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(key):9
+msgid "no"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(key):10
+msgid "/dev/sda3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(author:title):13 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(author:title):16 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(author:title):19
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(mail:link):14
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(mail:link):17
+msgid "swift"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(author):19
+msgid "Steven Wagner"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(abstract):21
+msgid "The Quick Install guide covers the Gentoo install process in a non-verbose manner. Its purpose is to allow users to perform a stage3 install in no time. Users should already have prior experience with installing Gentoo Linux if they want to follow this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(version):32
+msgid "25"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(date):33
+msgid "2010-01-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):36
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):40
+msgid "This guide contains all the commands you should use to complete a stage3 installation of Gentoo. You need a connection to the Internet to download the stage3 and Portage snapshots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(impo):46
+msgid "New users should read the <uri link=\"/doc/en/handbook/index.xml\">Handbook</uri> as it gives a better overview about the installation process. The Quick Install guide is designed for experienced users who just need a checklist to follow."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):52
+msgid "Timing output follows all commands that take more than a couple of seconds to finish. Commands were timed on an AMD 2000 1.66 Ghz PC with 512 MB of RAM and two SATA disks connected to a hardware controller."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):58
+msgid "Test box specs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):58
+#, no-wrap
+msgid "\n<comment>(The following specs and the timing information should help you determine\na rough estimate of the time you need to complete your install)</comment>\n\n# <i>grep bogo /proc/cpuinfo</i>\nbogomips       : 3337.81\n\n# <i>hdparm -tT /dev/sda</i>\n/dev/sda:\n Timing cached reads:   1100 MB in  2.00 seconds = 549.97 MB/sec\n Timing buffered disk reads:  224 MB in  3.01 seconds =  74.36 MB/sec\n\n# <i>grep MemTotal /proc/meminfo</i>\nMemTotal:       509248 kB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):79
+msgid "Quick Install Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):86
+msgid "Preparing the Disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):89
+msgid "Use <c>fdisk</c> or <c>cfdisk</c> to create your partition layout. You need at least a swap partition (type 82) and one Linux partition (type 83). The following scenario creates a <path>/boot</path>, a swap and a main partition as used in our handbook. Replace <path>sda</path> with your disk. Most systems ignore the bootable flag, but a few need it. Set this flag on your boot partition with fdisk's <c>a</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):98
+msgid "Create the partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):98
+#, no-wrap
+msgid "\nlivecd ~ # <i>fdisk /dev/sda</i>\n\n<comment>(The rest of this guide uses the following partitioning scheme)</comment>\nlivecd ~ # <i>fdisk -l /dev/sda</i>\n\nDisk /dev/sda: 599.9 GB, 599978409984 bytes\n255 heads, 63 sectors/track, 72943 cylinders\nUnits = cylinders of 16065 * 512 = 8225280 bytes\n\n   Device Boot      Start         End      Blocks   Id  System\n/dev/sda1   *           1          12       96358+  83  Linux\n/dev/sda2              13         110      787185   82  Linux swap / Solaris\n/dev/sda3             111       72943   585031072+  83  Linux\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):114
+msgid "Use <c>mke2fs</c>, <c>mke2fs -j</c>, <c>mkreiserfs</c>, <c>mkfs.xfs</c> and <c>mkfs.jfs</c> to create file systems on your Linux partitions. Initialize your swap partition using <c>mkswap</c> and <c>swapon</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):120
+msgid "Create the file systems and activate swap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):120
+#, no-wrap
+msgid "\n<comment>(ext2 is all you need on the /boot partition)</comment>\nlivecd ~ # <i>mke2fs /dev/sda1</i>\n\n<comment>(Let's use ext3 on the main partition)</comment>\nlivecd ~ # <i>mke2fs -j /dev/sda3</i>\n\n<comment>(Create and activate swap)</comment>\nlivecd ~ # <i>mkswap /dev/sda2 &amp;&amp; swapon /dev/sda2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):131
+msgid "Mount the freshly created file systems on <path>/mnt/gentoo</path>. Create directories for the other mount points (like <path>/mnt/gentoo/boot</path>) if you need them and mount them too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):137
+msgid "Mount the file systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):137
+#, no-wrap
+msgid "\nlivecd ~ # <i>mount /dev/sda3 /mnt/gentoo</i>\nlivecd ~ # <i>mkdir /mnt/gentoo/boot</i>\nlivecd ~ # <i>mount /dev/sda1 /mnt/gentoo/boot</i>\nlivecd ~ # <i>cd /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):152
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):155
+msgid "Install a kernel source (usually <c>gentoo-sources</c>), configure it, compile it and copy the <path>arch/i386/boot/bzImage</path> file to <path>/boot</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):160
+msgid "Install a kernel source, compile it and install the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):160
+#, no-wrap
+msgid "\nlivecd etc # <i>time emerge gentoo-sources</i>\n\nreal  2m51.435s\nuser  0m58.220s\nsys   0m29.890s\nlivecd etc # <i>cd /usr/src/linux</i>\nlivecd linux # <i>make menuconfig</i>\n<comment>(Configure your kernel)</comment>\nlivecd linux # <i>time make -j2</i>\n\n<comment>(Elapsed time depends highly on the options you selected)</comment>\nreal  3m51.962s\nuser  3m27.060s\nsys   0m24.310s\n\nlivecd linux # <i>make modules_install</i>\nlivecd linux # <i>cp arch/i386/boot/bzImage /boot/kernel</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):188 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):195
+msgid "Reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):191
+msgid "Exit the chrooted environment, unmount all file systems and reboot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):195
+#, no-wrap
+msgid "\nlivecd conf.d # <i>exit</i>\nlivecd / # <i>umount /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i>\nlivecd / # <i>reboot</i>\n<comment>(Don't forget to remove the CD)</comment>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoo-x86-tipsntricks.xml.pot b/doc/gettext/gentoo-x86-tipsntricks.xml.pot
new file mode 100644
index 0000000..6bd6af0
--- /dev/null
+++ b/doc/gettext/gentoo-x86-tipsntricks.xml.pot
@@ -0,0 +1,454 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(guide:link):5
+msgid "/doc/en/gentoo-x86-tipsntricks.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):6
+msgid "Gentoo/x86 Installation Tips &amp; Tricks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(mail:link):12
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(mail):12
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(abstract):15
+msgid "The Gentoo installation allows for very flexible approaches to the various installation methods. As it is almost impossible to insert every single tip or trick in the installation instructions this document tries to deal with all submitted tips and tricks for reference purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(version):26
+msgid "1.15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(date):27
+msgid "2007-09-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):30
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):32
+msgid "Preliminary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):35
+msgid "This document contains various tips and tricks for the Gentoo/x86 installation. Most of them are discussed in a dense way - they are meant as an addendum to the installation instructions and not as a replacement."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):44
+msgid "Contents"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):52
+msgid "#software-raid"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):52 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):82
+msgid "Software RAID"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):53
+msgid "#ata-raid-2.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):53 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):182
+msgid "ATA RAID using 2.4 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):54
+msgid "#livecd-kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):54 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):257
+msgid "Using the Installation CD kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):62
+msgid "#leave_terminal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):62
+msgid "Leaving the Terminal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):70
+msgid "#checking-disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):70 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):393
+msgid "Extensive Testing of your Disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):72
+msgid "#recover"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):72 ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):411
+msgid "Recovering from a malfunctioning installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):80
+msgid "Advanced Installations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(note):85
+msgid "If you are not familiar with software raid, please read the <uri link=\"http://tldp.org/HOWTO/Software-RAID-HOWTO.html\">Software-RAID-HOWTO</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(note):90
+msgid "A more detailed procedure can be found in our <uri link=\"/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml\">Software Raid and LVM2 x86 Quick Install Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):96
+msgid "Once you are booted from the Installation CD, load the appropriate RAID modules. For instance, if you plan on using RAID-1:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):101
+msgid "Loading the RAID-1 module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):101
+#, no-wrap
+msgid "\n# <i>modprobe raid1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):105
+msgid "When you partition your disks, make sure that your partitions use <c>fd</c> (Linux raid autodetect) as Partition Type instead of <c>83</c> (Linux native). You can alter the partition type using the <c>t</c> command in <c>fdisk</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):111
+msgid "Now before we start creating the RAID arrays, we need to create the metadevice nodes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):116
+msgid "Creating metadevice nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):116
+#, no-wrap
+msgid "\n# <i>mknod /dev/md1 b 9 1</i>\n# <i>mknod /dev/md2 b 9 2</i>\n# <i>mknod /dev/md3 b 9 3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):122
+msgid "After partitioning, create the <path>/etc/mdadm.conf</path> file (yes, indeed, on the Installation CD environment) using <c>mdadm</c>, an advanced tool for <uri link=\"http://www.linuxdevcenter.com/pub/a/linux/2002/12/05/RAID.html\">RAID management</uri>. For instance, to have your boot, swap and root partition mirrored (RAID-1) covering <path>/dev/sda</path> and <path>/dev/sdb</path>, you can use:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):131
+msgid "Creating raid devices with the mdadm command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):131
+#, no-wrap
+msgid "\n# <i>mdadm --create --verbose /dev/md1 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1</i>\n# <i>mdadm --create --verbose /dev/md2 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2</i>\n# <i>mdadm --create --verbose /dev/md3 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(impo):137
+msgid "You should not use any form of striping such as RAID-0 or RAID-5 on the partition you boot from."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):142
+msgid "The Linux Software RAID driver will start creating the metadevices. You can see its progress in <path>/proc/mdstat</path>. Wait until the metadevices are completely finished before proceeding."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):148
+msgid "Saving information about the created devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):148
+#, no-wrap
+msgid "\n# <i>mdadm --detail --scan &gt; /etc/mdadm.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):152
+msgid "From now onwards, use <path>/dev/md1</path> for the boot partition, <path>/dev/md2</path> for the swap partition and <path>/dev/md3</path> for the root partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):158
+msgid "Right before chrooting, don't forget to copy over <path>/etc/mdadm.conf</path> to <path>/mnt/gentoo/etc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):163
+msgid "When you're configuring your kernel, make sure you have the appropriate RAID support <e>in</e> your kernel and not as module."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):168
+msgid "When installing extra tools, emerge <c>mdadm</c> as well. Note that this isn't available on all Installation CDs so you might not be able to install Gentoo on a Software RAID when using a networkless installation!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):174
+msgid "When configuring your bootloader, make sure it gets installed in the MBR of <e>both</e> disks if you use mirroring."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):185
+msgid "Make sure you boot your Installation CD using the <c>doataraid</c> option. Once booted, check the contents of <path>/dev/ataraid</path>. It should contain various <path>disc*</path> directories for each harddisk available in the ATA RAID. An entire disk is displayed as <path>disc</path> while partitions are <path>part*</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):193
+msgid "Write down the various <path>/dev/ataraid/disc*/*</path> device files that you use to install Gentoo on. You will need to substitute the <path>/dev/hda</path> examples in the installation with this path."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):199
+msgid "Before chrooting, bind-mount the <path>/dev</path> structure in the new environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):204
+msgid "Bind-mounting /dev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):204
+#, no-wrap
+msgid "\n# <i>mount -o bind /dev /mnt/gentoo/dev</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):208
+msgid "When configuring your kernel, make sure you enable support for your ATA RAID chipset and options. For instance, a popular ATA RAID system is a <e>Promise FastTrack built-in RAID</e> in which case you definitely need <c>Promise FastTrack Options</c> built in into your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):215
+msgid "When configuring GRUB, you first have to create a GRUB bootdisk. This is not as hard as you think. First install GRUB as you would, but when you come to the part where GRUB is getting installed in the MBR, follow the following instructions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):222
+msgid "Creating a GRUB bootdisk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):222
+#, no-wrap
+msgid "\n# <i>cd /boot/grub</i>\n# <i>dd if=stage1 of=/dev/fd0 bs=512 count=1</i>\n# <i>dd if=stage2 of=/dev/fd0 bs=512 seek=1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):228
+msgid "You still need to write your <path>grub.conf</path> file. This is no different from the installation instructions, just make sure that your <c>root=</c> points to the ATA RAID device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):234
+msgid "After finishing the installation, boot with your GRUB bootdisk. You will be greeted by a GRUB prompt. Now configure GRUB to boot from the ATA RAID device:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):239
+msgid "Installing GRUB on the ATA RAID"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):239
+#, no-wrap
+msgid "\ngrub&gt; root (hd0,x)\ngrub&gt; setup (hd0)\ngrub&gt; quit\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):245
+msgid "Now reboot (with the GRUB bootfloppy removed)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):249
+msgid "LILO users can safely use the instructions mentioned in the installation instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):260
+msgid "If you don't want to compile a kernel yourself you can use the kernel from the Installation CD and copy it to your system. When you come to the point that you're asked to compile a kernel, go to another terminal (press Alt-F2) and log in with the root password you've supplied at the beginning of the installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):268
+msgid "Copy over the kernel and modules to your Gentoo system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):272
+msgid "Copying over the Installation CD kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):272
+#, no-wrap
+msgid "\n<comment>(${KN} is the kernel name, usually something like 'gentoo' or 'smp')</comment>\ncdimage ~# <i>cp /mnt/cdrom/isolinux/${KN} /mnt/cdrom/isolinux/${KN}.igz /mnt/gentoo/boot</i>\ncdimage ~# <i>mkdir -p /mnt/gentoo/lib/modules</i>\ncdiamge ~# <i>cp -Rp /lib/modules/`uname -r` /mnt/gentoo/lib/modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):279
+msgid "To have all modules that are currently running (from the Installation CD) loaded during bootup of your Gentoo system, run the following command from within the chrooted environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):285
+msgid "Adding all running modules to the modules.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):285
+#, no-wrap
+msgid "\n# <i>cat /proc/modules | cut -d ' ' -f 1 &gt;&gt; \\</i>\n  <i>/etc/modules.autoload.d/kernel-`uname -r | cut -d . -f -2`</i>\n# <i>update-modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):296
+msgid "Simplifying the Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):298
+msgid "Leaving your Terminal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):301
+msgid "Many people want to leave their system when it's compiling. In certain cases this is rather difficult as the installation is done in a public environment where you cannot trust everyone. If this is the case, you want to be able to perform the compilation in the background and log out from all terminals."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):308
+msgid "There are several possible solutions for this. The first one is to use <c>screen</c>. After booting the Installation CD, set your root password and start a screen session:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(note):314
+msgid "Not all Installation CDs provide screen. If this is the case, you will have to use one of the other methods described in this section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):319
+msgid "Starting a screen session"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):319
+#, no-wrap
+msgid "\n# <i>screen -S gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):323
+msgid "Once inside the screen session you can perform the entire installation. When you want to leave your terminal, press <c>Ctrl-a, d</c> (that is, control and a at the same time, then followed by a d) to <e>detach</e> your screen session. You can now safely log out of your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):330
+msgid "To regain access to your terminal, log in as root again and <e>attach</e> to the running screen session:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):335
+msgid "Attaching to a screen session"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):335
+#, no-wrap
+msgid "\n# <i>screen -x gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):339
+msgid "If you can't use screen, there is still a way to leave your terminal. Follow the installation instructions, but when you come to the point where a long-term compilation would be started (for instance the <c>./scripts/bootstrap.sh</c> step), use <c>nohup</c> which allows for a process to continue even when you log out. Don't forget the trailing \"&amp;\", otherwise the process won't be placed in the background! Remember where you are (the <c>pwd</c> command will show you that) as you will need to know this later on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):349
+msgid "Using nohup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):349
+#, no-wrap
+msgid "\n# <i>pwd</i>\n/usr/portage\n# <i>nohup ./scripts/bootstrap.sh &amp;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):355
+msgid "Now exit the chrooted environment (<c>exit</c>) and the Installation CD session. Your compilation will continue in the background."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):360
+msgid "When you want to check the compilation, log in as root (on the Installation CD) and chroot back into your environment and go to the directory where you left off:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):366
+msgid "Chrooting back"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):366
+#, no-wrap
+msgid "\n# <i>chroot /mnt/gentoo /bin/bash</i>\n# <i>env-update &amp;&amp; source /etc/profile</i>\n# <i>cd /usr/portage</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):372
+msgid "Now use the <c>less</c> command on the <path>nohup.out</path> file that is situated inside that directory. The compilation will append its output to that file, so if you want to follow the compilation progress, run <c>less nohup.out</c> and press <c>F</c> to follow the changes. When the compilation is finished, you can continue with the next step of the installation instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):380
+msgid "If you ever get tired of following the changes, press <c>Ctrl-C</c> followed by a <c>q</c>. This won't stop the compilation process, only the <c>less</c> process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):391
+msgid "Fixing Errors/Issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):396
+msgid "If you think your disk needs to be thoroughly checked for consistency (bad sectors and such), you can use the <c>-c</c> option while placing the ext2 or ext3 filesystem on it (using <c>mke2fs</c>). This will format, perform a read-test and mark all bad blocks as such. If you are really paranoid, use <c>-c -c</c> to format your disk and perform an extensive read/write test."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):404
+msgid "Checking for disk consistency"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):404
+#, no-wrap
+msgid "\n# <i>mke2fs -j -c /dev/hda3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):414
+msgid "If for some reason your Gentoo installation fails, you don't have to redo the installation all over again. Instead, you can safely \"go\" to the point where you think you made a mistake (or where you think the instructions are flawed) and try a different approach."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):421
+msgid "First of all you need to chroot back into your Gentoo Linux environment. Follow the instructions again, but ignore the partitioning steps as your partitions are already created and even populated. You can therefore immediately mount those partitions at <path>/mnt/gentoo</path>. You should also ignore the steps about stage extraction and modifying <path>make.conf</path> - you don't want to overwrite your files do you?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):430
+msgid "Once chrooted inside your Gentoo Linux environment, immediately go to the step where you think you should try a different approach. Don't redo all the steps like bootstrapping and such unless that is the place where you think things went wrong."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):437
+msgid "For instance, if you believe that you have a wrongly configured <path>grub.conf</path>, you can immediately fire up your editor to update <path>/boot/grub/grub.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):443
+msgid "Once you have tried a different approach for your situation, you should consider how much of the subsequent steps you need to perform again. If the subsequent steps are depending on your change, you will need to redo those."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):449
+msgid "For instance,"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(li):454
+msgid "if you have changed a variable inside <path>make.conf</path> you will need to do all subsequent compiling since those depend on the settings inside <path>make.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(li):459
+msgid "if you have altered <path>/boot/grub/grub.conf</path> you can immediately exit the chrooted environment and reboot as no subsequent steps are depending on <path>grub.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(li):464
+msgid "if you have recompiled your kernel you only need to make sure that your bootloader configuration points to the correct kernel image (double-check that you mounted your <path>/boot</path>!), then you can exit the chrooted environment and reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(li):470
+msgid "if you have altered <path>/etc/fstab</path> you can exit the chrooted environment and reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):476
+msgid "As you can see, for most recovery operations you can immediately reboot. Only in certain cases will you need to redo the subsequent installation steps."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gentoolkit.xml.pot b/doc/gettext/gentoolkit.xml.pot
new file mode 100644
index 0000000..0e17bd7
--- /dev/null
+++ b/doc/gettext/gentoolkit.xml.pot
@@ -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: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):6
+msgid "Gentoolkit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):9
+msgid "mbutcher@aleph-null.tv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):9
+msgid "Matt Butcher"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):20 ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):23 ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):26 ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):29
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author):11
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):15
+msgid "erwin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):15
+msgid "Erwin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):18
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):18
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):21
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):21
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):24
+msgid "karltk@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):24
+msgid "Karl Trygve"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):27
+msgid "yoswink@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):27
+msgid "José Luis Rivero"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):30
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):30
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(abstract):33
+msgid "Gentoolkit is a suite of tools to ease the administration of a Gentoo system. This document covers the basics of some of the tools present in Gentoolkit."
+msgstr ""
+
+#. Licensed under GFDL
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(version):40
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(date):41
+msgid "2010-10-03"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):44 ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):112 ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):443
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):46
+msgid "What is Gentoolkit?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):49
+msgid "Gentoo is a unique distribution and presents some complexities that simply don't exist for other distributions. As Gentoo developers and contributors discovered some of these complexities, they also wrote tools to help users and administrators work around them. Many of these tools have been contributed to the Gentoo project and are included in the package <c>app-portage/gentoolkit</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):58
+msgid "As of now, there are two versions of gentoolkit: <c>app-portage/gentoolkit</c> and <c>app-portage/gentoolkit-dev</c>. While the former contains administration scripts, the latter contains scripts specific to help development on Gentoo. If you are a developer, you can have your scripts included into <c>gentoolkit-dev</c> by contacting the Gentoolkit maintainer. This document discusses gentoolkit only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):67
+msgid "Gentoolkit contains a whole bunch of useful tools to help manage your packages and keep track of what is going on in your system. Most users --&nbsp;particularly those who update systems often&nbsp;-- will benefit from having gentoolkit installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):77
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):80
+msgid "Just as with any Gentoo package, installation is just a simple emerge."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):84
+msgid "Getting gentoolkit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):84
+#, no-wrap
+msgid "\n# <i>emerge gentoolkit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):88
+msgid "Many of the tools in gentoolkit reveal important information about your system or require root privilege. For that reason, some of the programs may only be executed (or only function properly) if run by a user with root permission."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):97
+msgid "Finding Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):100
+msgid "Any documentation that a program might have (other than man pages) is stored in <path>/usr/share/doc/gentoolkit-[version]/[program-name]/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):110
+msgid "equery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):115
+msgid "<c>equery</c> is a tool that displays a great deal of useful information about the packages on your system and much more. <c>equery --help</c> gives you the full set of options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):121
+msgid "Not all features listed by <c>equery --help</c> have been implemented yet. Those that have not been, are mentioned clearly. You will also see that every command has a short option, e.g. <c>b</c> instead of <c>belongs</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):127
+msgid "Be aware that equery currently changes the format of the output if it is sent through a pipe. The piped format is intended to be easier to parse by tools, but you can also turn it off by adding the <c>--no-pipe</c> option. If you write scripts that employ equery, you should be aware of this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):137
+msgid "Finding the Package That a File Came From"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):140
+msgid "<c>equery</c> also provides the functionality of finding the package that a file came from, using <c>belongs</c> command (or just <c>b</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):145
+msgid "Finding the ebuild that installed a given file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):145
+#, no-wrap
+msgid "\n# <i>equery belongs /usr/bin/audacious</i>\n[ Searching for file(s) /usr/bin/audacious in *... ]\nmedia-sound/audacious-1.1.2 (/usr/bin/audacious)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):151
+msgid "By using the <c>-f</c> option, you may search for packages with files matching any regular expression. The <c>-e</c> option is useful for terminating your search immediately when a match is found."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):160
+msgid "Verifying Package Integrity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):163
+msgid "Sometimes it is useful to check a package's integrity. <c>equery</c> can verify md5 sums as well as timestamps to indicate when a package might have been corrupted, replaced, or removed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):169
+msgid "OK package integrity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):169
+#, no-wrap
+msgid "\n# <i>equery check gentoolkit</i>\n[ Checking app-portage/gentoolkit-0.2.0 ]\n * 54 out of 54 files good\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):175
+msgid "Please note that if you change configuration files after installation, these may be reported as \"not good\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):183
+msgid "List of all packages depending on ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):186
+msgid "<c>equery</c> is able to list all direct dependencies matching a package. The function we should use to do this is <c>depends</c> and it's as easy as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):191
+msgid "Looking for packages depending on pygtk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):191
+#, no-wrap
+msgid "\n# <i>equery depends pygtk</i>\n[ Searching for packages depending on pygtk... ]\napp-office/dia-0.93\ndev-python/gnome-python-2.0.0-r1\ngnome-extra/gdesklets-core-0.26.2\nmedia-gfx/gimp-2.0.4\nx11-libs/vte-0.11.11-r1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):204
+msgid "Dependency Graphs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):207
+msgid "<c>equery</c> is capable of giving us a dependency graph for a specified package. The dependency graph gives a listing of all the packages that have direct and indirect dependencies on the package in question."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):213
+msgid "Dependency Graph for cdrtools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):213
+#, no-wrap
+msgid "\n# <i>equery depgraph cdrtools</i>\nDisplaying dependencies for app-cdr/cdrtools-2.01_alpha37\n`-- app-cdr/cdrtools-2.01_alpha37\n `-- sys-libs/glibc-2.3.4.20040808 (virtual/libc)\n  `-- sys-kernel/linux-headers-2.4.22 (virtual/os-headers)\n   `-- sys-apps/baselayout-1.10.4\n    `-- sys-apps/sysvinit-2.85-r1\n     `-- sys-apps/gawk-3.1.3-r1\n      `-- sys-apps/util-linux-2.12-r4\n          `-- sys-apps/sed-4.0.9\n        `-- sys-libs/ncurses-5.4-r4\n            `-- sys-apps/pam-login-3.14\n            `-- sys-libs/pam-0.77-r1\n                 `-- sys-libs/cracklib-2.7-r10\n               `-- sys-apps/miscfiles-1.3-r1\n              `-- app-arch/gzip-1.3.5-r1\n              `-- sys-apps/portage-2.0.50-r10\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):233
+msgid "For example, while glibc is a direct dependency for cdrtools,linux-headers are an indirect dependency. Note that the output also includes information about virtual packages. In the example above, <c>cdrtools</c> is actually written to require virtual/libc, not sys-libs/glibc, but on the given system in the example sys-libs/glibc provides virtual/libc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):244
+msgid "Listing Files Belonging to an Ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):247
+msgid "<c>equery</c> can list the files that belong to an installed ebuild. If I don't know the files that Gentoolkit has installed on the system, I will use <c>equery</c> to show them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):253
+msgid "Listing files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):253
+#, no-wrap
+msgid "\n# <i>equery files gentoolkit</i>\n[ Searching for packages matching gentoolkit... ]\napp-portage/gentoolkit-0.2.0\n* Contents of app-portage/gentoolkit-0.2.0:\n/usr\n/usr/bin\n/usr/bin/equery\n/usr/bin/etcat\n/usr/bin/euse\n/usr/bin/glsa-check\n/usr/bin/qpkg\n/usr/bin/revdep-rebuild\n/usr/lib\n/usr/lib/gentoolkit\n/usr/lib/gentoolkit/pym\n/usr/lib/gentoolkit/pym/gentoolkit\n/usr/lib/gentoolkit/pym/gentoolkit/__init__.py\n/usr/lib/gentoolkit/pym/gentoolkit/gentoolkit.py\n/usr/lib/gentoolkit/pym/gentoolkit/pprinter.py\n/usr/lib/gentoolkit/pym/glsa.py\n/usr/sbin\n/usr/share\n/usr/share/doc\n/usr/share/doc/gentoolkit-0.2.0_pre10\n\n[...]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):282
+msgid "The command <c>files</c> of <c>equery</c> provide some options to modify the output. You can look them all up in the <c>equery</c> man page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):290
+msgid "Looking for packages that use a specific USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):293
+msgid "If you want to find which packages on your system that make use of a specific USE flag, <c>equery</c> has the function <c>hasuse</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):298
+msgid "Searching packages which use the firefox USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):298
+#, no-wrap
+msgid "\n# <i>equery hasuse firefox</i>\n[ Searching for USE flag firefox in all categories among: ]\n * installed packages\n[I--] [  ] dev-python/gnome-python-extras-2.14.0-r1 (0)\n[I--] [  ] media-video/totem-2.16.4 (0)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):309
+msgid "Listing Packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):312
+msgid "<c>equery</c> has a power feature to list packages belonging to our system, portage or even an overlay. Let's try this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):317
+msgid "Listing packages with equery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):317
+#, no-wrap
+msgid "\n# <i>equery list gentoolkit</i>\n[ Searching for package 'gentoolkit' in all categories among: ]\n * installed packages\n[I--] [  ] app-portage/gentoolkit-0.2.0 (0)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):324
+msgid "The standard query will search our installed packages for the name given. If found, the following info will be displayed: the package location between the first square brackets (I for Installed packages, P for Portage, O for Overlay), the possible masks between the second (~ by keyword, - by arch or M hard masked), then the category and complete name and last of all, the slot in which the package is stored."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):333
+msgid "Another example, this time we are going to use the local options in order to look for packages in our portage tree and overlay."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):338
+msgid "Using local options with equery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):338
+#, no-wrap
+msgid "\n# <i>equery list -p -o vim</i>\n[ Searching for package 'vim' in all categories among: ]\n * installed packages\n[I--] [  ] app-editors/vim-6.3-r4 (0)\n * Portage tree (/usr/portage)\n[-P-] [M~] app-editors/vim-7.0_alpha20050126 (0)\n[-P-] [M~] app-editors/vim-7.0_alpha20050201 (0)\n[-P-] [  ] app-editors/vim-6.3-r2 (0)\n[-P-] [M~] app-editors/vim-7.0_alpha20050122 (0)\n[-P-] [M~] app-editors/vim-core-7.0_alpha20050126 (0)\n[-P-] [  ] app-editors/vim-core-6.3-r3 (0)\n[-P-] [M~] app-editors/vim-core-7.0_alpha20050122 (0)\n[-P-] [M~] app-editors/vim-core-7.0_alpha20050201 (0)\n[-P-] [  ] app-editors/vim-core-6.3-r4 (0)\n * overlay tree (/opt/ebuilds)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):359
+msgid "Finding Package Sizes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):362
+msgid "Ever been curious to find out how much space a specific package is occupying? Since a package could have its files over a number of directories, the usual <c>du -hc</c> might not give you the correct figure. Not to worry, here comes <c>equery</c> to the rescue!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):369
+msgid "Package Size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):369
+#, no-wrap
+msgid "\n# <i>equery size openoffice-bin</i>\n* app-office/openoffice-bin-1.1.2\n     Total Files : 2908\n     Total Size  : 223353.31 KiB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):376
+msgid "As you can see, <c>equery</c> prints the total space used in kilobytes and also lists the total number of files the package has."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):384
+msgid "Package-wise list of USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):387
+msgid "<c>equery</c> can be used to give us information about what USE flags are being used by a specific package. It also tells us what our current USE flags are for a package and also what USE flags are available for the package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):393
+msgid "Set and Unset USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):393
+#, no-wrap
+msgid "\n# <i>equery uses wireshark</i>\n[ Colour Code : set unset ]\n[ Legend    : (U) Col 1 - Current USE flags        ]\n[           : (I) Col 2 - Installed With USE flags ]\n\n U I [ Found these USE variables in : net-analyzer/wireshark-0.99.4 ]\n - - adns      : Adds support for the adns DNS client library\n + + gtk       : Adds support for x11-libs/gtk+ (The GIMP Toolkit)\n - - ipv6      : Adds support for IP version 6\n - - kerberos  : Adds kerberos support\n - - portaudio : Adds support for the crossplatform portaudio audio API\n - - selinux   : !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur\n - - snmp      : Adds support for the Simple Network Management Protocol if available\n + + ssl       : Adds support for Secure Socket Layer connections\n - - threads   : Adds threads support for various packages. Usually pthreads\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):411
+msgid "I have installed wireshark with only the gtk and ssl flags set, but there are several other USE flags for wireshark still available. For more information on USE flags, please refer to the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2\">USE Flags</uri> chapter of the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):422
+msgid "Where's the ebuild?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):425
+msgid "We can also find out which ebuild is being used for a specific package using <c>equery</c>. This is done by using the <c>equery which</c> command which displays the full path to the ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):431
+msgid "Displaying the ebuild path"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):431
+#, no-wrap
+msgid "\n# <i>equery which cdrtools</i>\n/usr/portage/app-cdr/cdrtools/cdrtools-2.01_alpha37.ebuild\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):441
+msgid "euse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):446
+msgid "<c>euse</c> is a tool to see, set and unset USE flags at various places. For more information on USE flags, please refer to the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2\">USE Flags</uri>. Please see <c>euse -h</c> for complete help and all options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):456
+msgid "Viewing, Setting and Unsetting USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):459
+msgid "The <c>euse -a</c> command reads the current active USE flags and displays them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):464
+msgid "There are 5 \"columns\" that <c>euse</c> now uses to show whether a flag is set/unset and where all the flag has been set. The columns are as follows -- +/-, set in the Environment, set in make.Conf, set in make.Defaults, and set in make.Globals. The output looks like [+ECDG]."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):471
+msgid "Viewing all active USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):471
+#, no-wrap
+msgid "\n# <i>euse -a</i>\nX                   [+ CD ]\naalib               [+    ]\nacpi                [+ C  ]\nalsa                [+ C  ]\napache2             [+ C  ]\napm                 [+  D ]\navi                 [+  D ]\nberkdb              [+  D ]\nbitmap-fonts        [+  D ]\nbonobo              [+    ]\ncdr                 [+ C  ]\ncrypt               [+ CD ]\ncscope              [+ C  ]\ncups                [+ CD ]\ncurl                [+    ]\nemboss              [+  D ]\nencode              [+  D ]\nesd                 [+    ]\nfam                 [+    ]\nfbcon               [+ C  ]\nfirefox             [+ C  ]\nfont-server         [+  D ]\nfoomaticdb          [+  D ]\nfortran             [+  D ]\ngd                  [+ C  ]\ngdbm                [+  D ]\ngif                 [+ CD ]\ngimpprint           [+ C  ]\ngnome               [+ CD ]\ngphoto2             [+    ]\ngpm                 [+ CD ]\ngstreamer           [+ C  ]\ngtk                 [+  D ]\ngtkhtml             [+ C  ]\nguile               [+    ]\nimagemagick         [+    ]\nimlib               [+ CD ]\ninnodb              [+    ]\nipv6                [+  D ]\njavascript          [+ C  ]\njpeg                [+ CD ]\nkde                 [+  D ]\nldap                [+    ]\nlibg++              [+ CD ]\nlibwww              [+ CD ]\nmad                 [+ CD ]\nmbox                [+ C  ]\nmd5sum              [+ C  ]\nmikmod              [+ CD ]\nmmx                 [+ C  ]\nmotif               [+ CD ]\nmp3                 [+    ]\nmpeg                [+ CD ]\nmpeg4               [+ C  ]\nmysql               [+ C  ]\nncurses             [+ CD ]\nnls                 [+  D ]\nnvidia              [+ C  ]\nodbc                [+    ]\noffensive           [+    ]\nogg                 [+ CD ]\nopengl              [+ CD ]\noss                 [+  D ]\npam                 [+ CD ]\npdflib              [+ CD ]\nperl                [+ CD ]\npng                 [+ CD ]\npython              [+ CD ]\nqt                  [+  D ]\nquicktime           [+ CD ]\nreadline            [+ CD ]\nruby                [+    ]\nsdl                 [+ CD ]\nslang               [+  D ]\nspell               [+ CD ]\nsse                 [+ C  ]\nssl                 [+ CD ]\nsvga                [+ CD ]\ntcltk               [+ C  ]\ntcpd                [+  D ]\ntiff                [+ C  ]\ntruetype            [+ CD ]\nusb                 [+ C  ]\nvanilla             [+ C  ]\nx86                 [+ C  ]\nxml                 [+    ]\nxosd                [+ C  ]\nxv                  [+ CD ]\nxvid                [+ C  ]\nzlib                [+ CD ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):565
+msgid "Similarly you can use the <c>euse -a -g</c> command to only view active global USE flags. The <c>euse -a -l</c> command does the same for active local USE flags.<c>-g</c> &amp; <c>-l</c> are suboptions to <c>euse</c> and need an option before them (like <c>-a</c>) to function correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):572
+msgid "Viewing active local USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):572
+#, no-wrap
+msgid "\n# <i>euse -a -l</i>\nbitmap-fonts        [+  D ]\nfont-server         [+  D ]\nfortran             [+  D ]\ngimpprint           [+ C  ]\nmd5sum              [+ C  ]\nmpeg4               [+ C  ]\nnvidia              [+ C  ]\noffensive           [+    ]\ntruetype            [+ CD ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):585
+msgid "We can also use <c>euse</c> to set or unset use flags. The commands used for this are <c>euse -E flagname</c> (enable a flag) and <c>euse -D flagname</c> (disable a flag)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(warn):591
+msgid "Do not use the <c>euse -E</c> or <c>euse -D</c> commands by themselves (without a flag). It will set/unset ALL USE flags in <c>/etc/make.conf</c>. Although a backup is kept at <path>/etc/make.conf.euse_backup</path>, please be careful while using <c>euse -E</c> or <c>euse -D</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):598
+msgid "Setting and Unsetting USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):598
+#, no-wrap
+msgid "\n<comment>(Enabling a USE Flag)</comment>\n# <i> euse -E 3dfx</i>\n/etc/make.conf was modified, a backup copy has been placed at /etc/make.conf.euse_backup\n\n<comment>(/etc/make.conf after the command)</comment>\nUSE=\"alsa acpi apache2 -arts cups cdr crypt cscope -doc fbcon \\\n     firefox gd gif gimpprint gnome gpm gstreamer gtkhtml imlib \\\n     innodb -java javascript jpeg libg++ libwww mad mbox md5sum \\\n     mikmod mmx motif mpeg mpeg4 mysql ncurses nvidia \\\n     ogg odbc offensive opengl pam pdflib perl png python \\\n     quicktime readline sdl spell sse ssl svga tcltk tiff truetype usb \\\n     vanilla X xosd xv xvid x86 zlib 3dfx\"\n\n<comment>(Disabling the USE Flag)</comment>\n# <i> euse -D 3dfx</i>\n/etc/make.conf was modified, a backup copy has been placed at /etc/make.conf.euse_backup\n\n<comment>(/etc/make.conf after the command)</comment>\nUSE=\"alsa acpi apache2 -arts cups cdr crypt cscope -doc fbcon \\\n     firefox gd gif gimpprint gnome gpm gstreamer gtkhtml imlib \\\n     innodb -java javascript jpeg libg++ libwww mad mbox md5sum \\\n     mikmod mmx motif mpeg mpeg4 mysql ncurses nvidia \\\n     ogg odbc offensive opengl pam pdflib perl png python \\\n     quicktime readline sdl spell sse ssl svga tcltk tiff truetype usb \\\n     vanilla X xosd xv xvid x86 zlib -3dfx\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):626
+msgid "<c>euse</c> does not physically remove the flag from make.conf. It just adds a - (minus) before the flag to unset it. You may have to manually clean up your make.conf to avoid unwanted variables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):637
+msgid "Other tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):639
+msgid "revdep-rebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):642
+msgid "This tool is Gentoo's Reverse Dependency rebuilder. It will scan your installed ebuilds to find packages that have become broken as a result of an upgrade of a package they depend on. It can emerge those packages for you but it can also happen that a given package does not work anymore with the currently installed dependencies, in which case you should upgrade the broken package to a more recent version. revdep-rebuild will pass flags to emerge which lets you use the <c>--pretend</c> flag to see what is going to be emerged again before you go any further."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):653
+msgid "Running revdep-rebuild in pretend mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):653
+#, no-wrap
+msgid "\n# <i>revdep-rebuild -p</i>\n\nChecking reverse dependencies...\nPackages containing binaries and libraries broken by any package update,\nwill be recompiled.\n\nCollecting system binaries and libraries... done.\n  (/root/.revdep-rebuild.1_files)\n\nCollecting complete LD_LIBRARY_PATH... done.\n  (/root/.revdep-rebuild.2_ldpath)\n\nChecking dynamic linking consistency...\n  broken /usr/lib/ao/plugins-2/libarts.so (requires libartsc.so.0)\n  broken /usr/lib/kde3/libkpresenterpart.so (requires libartskde.so.1 libqtmcop.so.1\n         libsoundserver_idl.so.1 libkmedia2_idl.so.1 libartsflow.so.1 libartsflow_idl.so.1 libmcop.so.1)\n  broken /usr/lib/ruby/site_ruby/1.8/i686-linux/fox.so (requires libFOX-1.0.so.0)\n  broken /usr/lib/xine/plugins/1.0.0/xineplug_ao_out_arts.so (requires libartsc.so.0)\n  broken /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/auto/SDL_perl/SDL_perl.so (requires libSDL_gfx.so.0)\n  broken /usr/lib/libloudmouth-1.so.0.0.0 (requires libgnutls.so.10)\n  broken /usr/bin/k3b (requires libartskde.so.1 libqtmcop.so.1 libsoundserver_idl.so.1 libkmedia2_idl.so.1\n         libartsflow.so.1 libartsflow_idl.so.1 libmcop.so.1)\n  broken /usr/bin/lua (requires libhistory.so.4)\n  broken /usr/bin/lyx (requires libAiksaurus-1.0.so.0)\n  broken /usr/bin/luac (requires libhistory.so.4)\n  broken /usr/bin/avidemux2 (requires libartsc.so.0)\n  broken /usr/bin/pptout (requires libxml++-0.1.so.11)\n  broken /usr/bin/xml2ps (requires libxml++-0.1.so.11)\n done.\n  (/root/.revdep-rebuild.3_rebuild)\n\nAssigning files to ebuilds... done.\n  (/root/.revdep-rebuild.4_ebuilds)\n\nEvaluating package order... done.\n  (/root/.revdep-rebuild.5_order)\n\nAll prepared. Starting rebuild...\nemerge --oneshot --nodeps -p =app-cdr/k3b-0.11.14 =app-office/koffice-1.3.2 =app-office/lyx-1.3.4 \\\n       =app-office/passepartout-0.2 =dev-lang/lua-5.0.2 =dev-ruby/fxruby-1.0.29 =media-libs/libao-0.8.5 \\\n       =media-libs/xine-lib-1_rc5-r3 =media-video/avidemux-2.0.26 =net-libs/loudmouth-0.16\n\nThese are the packages that I would merge, in order:\n\nCalculating dependencies ...done!\n[ebuild   R   ] app-cdr/k3b-0.11.14\n[ebuild   R   ] app-office/koffice-1.3.2\n[ebuild   R   ] app-office/lyx-1.3.4\n[ebuild   R   ] app-office/passepartout-0.2\n[ebuild   R   ] dev-lang/lua-5.0.2\n[ebuild   R   ] dev-ruby/fxruby-1.0.29\n[ebuild   R   ] media-libs/libao-0.8.5\n[ebuild   R   ] media-libs/xine-lib-1_rc5-r3\n[ebuild   R   ] media-video/avidemux-2.0.26\n[ebuild   R   ] net-libs/loudmouth-0.16\n\nNow you can remove -p (or --pretend) from arguments and re-run revdep-rebuild.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):713
+msgid "If you need to rebuild some packages, you may run <c>revdep-rebuild</c> without the <c>-p</c> flag and the listed packages will be emerged again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):721
+msgid "glsa-check"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):724
+msgid "<c>glsa-check</c> is mainly a test tool that keeps track of the various GLSAs (Gentoo Linux Security Advisory) and will eventually be integrated into <c>emerge</c> and <c>equery</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):733
+msgid "eread"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):736
+msgid "<c>eread</c> is a simple utility to display elog files produced by &gt;=<c>portage-2.1</c>. You can set the saving of elog files by setting a couple of variables in <path>/etc/make.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):742
+msgid "Enabling elog in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):742
+#, no-wrap
+msgid "\nPORTAGE_ELOG_CLASSES=\"log\"\nPORTAGE_ELOG_SYSTEM=\"save\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):747
+msgid "This is just one way of saving elog messages. For more information on how Portage's elog system works, please refer to the appropriate page in the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=3&amp;chap=1#doc_chap4\">Portage Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):754
+msgid "Once you've set up elog to your satisfaction, just run <c>eread</c> to view your log files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):759
+msgid "Using eread"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):759
+#, no-wrap
+msgid "\n$ <i>eread</i>\n\nThis is a list of portage log items. Choose a number to view that file or type\nq to quit.\n\n1) app-portage:gentoolkit-0.2.4_pre2:20070320-000256.log\n2) app-portage:gentoolkit-0.2.4_pre2:20070320-000258.log\n3) app-portage:gentoolkit-0.2.4_pre2:20070320-000319.log\n4) app-portage:gentoolkit-0.2.3:20070320-000408.log\nChoice?\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):772
+msgid "Select a number and the file will be displayed using the paging program specified in the PAGER environment variable. If PAGER is not set, it will use <c>less</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):778
+msgid "After displaying the elog item, you will be prompted if you want to delete the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):786
+msgid "eclean"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):789
+msgid "<c>eclean</c> is a tool to remove old source files and old binary packages from your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):794
+msgid "When you build and install packages, the source files are downloaded and preserved in DISTDIR, usually <path>/usr/portage/distfiles</path>. This can accumulate several gigs of material over time if you don't clean it periodically. You can run <c>eclean-dist</c> to clean only source files from DISTDIR."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):802
+msgid "You can create archives of installed packages by using <c>quickpg</c> or FEATURES=\"buildpkg\". These archived packages are kept in PKGDIR, usually <path>/usr/portage/packages</path>. When you no longer need to keep them around, or if they're too old, you can run <c>eclean-pkg</c> to remove them from PKGDIR. It's a good way to ensure that any binary packages you have are only the latest versions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):811
+msgid "For more information on <c>eclean</c> and tips on maintaining a cruft-free system, please read <c>man eclean</c>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gnome-config.xml.pot b/doc/gettext/gnome-config.xml.pot
new file mode 100644
index 0000000..fba9922
--- /dev/null
+++ b/doc/gettext/gnome-config.xml.pot
@@ -0,0 +1,263 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):6
+msgid "The GNOME Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail:link):12
+msgid "lars@strojny.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail):12
+msgid "Lars Strojny"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(abstract):18
+msgid "A frequently used environment is GNOME. This HOWTO tries to describe all aspects of GNOME, including installation, configuration, usage, ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(version):27
+msgid "1.24"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(date):28
+msgid "2010-06-07"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):31
+msgid "What is GNOME?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):33
+msgid "The Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):36
+msgid "The <uri link=\"http://www.gnome.org\">GNOME</uri> project is a free software project dedicated to the development of GNOME, a Unix/Linux desktop suite and development platform. The <uri link=\"http://foundation.gnome.org\">GNOME Foundation</uri> coordinates the development and other aspects of the GNOME Project."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):47
+msgid "The Software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):50
+msgid "GNOME is a desktop environment and a development platform. This piece of free software is the desktop of choice for several industry leaders. It is interesting both for business users, home users as well as developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):59
+msgid "The Community"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):62
+msgid "Like with any big free software project, GNOME has an extensive user- and development base. <uri link=\"http://www.gnomedesktop.org\">Footnotes</uri> contains GNOME Desktop news for users; <uri link=\"http://planet.gnome.org\">GnomePlanet</uri> is for hackers/contributors and <uri link=\"http://developer.gnome.org\">Developer.Gnome.Org</uri> is for the GNOME developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):75 ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):113
+msgid "Installing GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):77
+msgid "What do you need?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(impo):80
+msgid "First read and follow the instructions in the <uri link=\"/doc/en/xorg-config.xml\">X Server Configuration Howto</uri> to setup your X environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):86
+msgid "Before you start installing GNOME, you might want to edit your USE variables. Make sure that <c>X</c>, <c>gtk</c>, and <c>gnome</c> are in your USE variable listed in <path>/etc/make.conf</path>. If you want support for <c>hald</c>, the hardware abstraction layer daemon add <c>hal</c> to your USE flags. The same goes for <c>dbus</c>, a system message bus Gnome uses extensively. If you don't want KDE support (the other big desktop environment), remove <c>qt4</c> and <c>kde</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):96
+msgid "Example USE in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):96
+#, no-wrap
+msgid "\nUSE=\"-qt4 -kde X dbus gtk gnome hal\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):100
+msgid "You can add the <c>branding</c> USE flag to get a lovely Gentoo-branded splashscreen instead of the default Gnome splashscreen:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):105
+msgid "Enabling Gentoo branding"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):105
+#, no-wrap
+msgid "\n# <i>echo \"gnome-base/gnome-session branding\" &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):109
+msgid "Once done, start installing GNOME by emerging <c>gnome</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):113
+#, no-wrap
+msgid "\n# <i>emerge gnome</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):117
+msgid "You can also opt for a minimal Gnome installation using <c>gnome-light</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):121
+msgid "Installing a minimal GNOME environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):121
+#, no-wrap
+msgid "\n# <i>emerge gnome-light</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):125
+msgid "This will take a while, so you might want to start reading all those books your mother bought you but you never opened. Done? Great, now update your environment variables:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):131
+msgid "Updating environment variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):131
+#, no-wrap
+msgid "\n# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):135
+msgid "Next we'll clean up the remaining services."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):139
+msgid "Adding hald and dbus to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):139
+#, no-wrap
+msgid "\n# <i>/etc/init.d/hald start</i>\n# <i>rc-update add hald default</i>\n\n# <i>/etc/init.d/dbus start</i>\n# <i>rc-update add dbus default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):150
+msgid "First Impressions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):153
+msgid "Let us first take a look at what we just built. Exit your root shell and log on as a regular user. We will configure our session to run GNOME when we issue the <c>startx</c> command (see also <uri link=\"/doc/en/xorg-config.xml#using_startx\">Using startx</uri> in the <uri link=\"/doc/en/xorg-config.xml\">X Server Configuration Howto</uri>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):161
+msgid "Having GNOME as default desktop environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):161
+#, no-wrap
+msgid "\n$ <i>echo \"exec gnome-session\" &gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):165
+msgid "Starting with <c>gnome-base/gnome-session-2.26.2</c>, you will need to prepend the XDG_MENU_PREFIX variable to get the Gnome menus if you're using the <path>~/.xinitrc</path> method to start your desktop. (If you're not using <path>~/.xinitrc</path>, it will be handled automatically for you; no additional configuration is needed.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):173
+msgid "Prepending XDG_MENU_PREFIX to ~/.xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):173
+#, no-wrap
+msgid "\n$ <i>sed -i '1i\\export XDG_MENU_PREFIX=gnome-' ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):177
+msgid "Now start your graphical environment by running <c>startx</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):181
+msgid "Starting GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):181
+#, no-wrap
+msgid "\n$ <i>startx</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):185
+msgid "If all goes well, you should be greeted by GNOME. Congratulations. Now let us take a look at how you can configure GNOME to suit your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):194
+msgid "Configuring GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):196
+msgid "GNOME's Graphical Login Manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):199
+msgid "If you want the GNOME Display Manager (GDM) to run automatically when you boot (so you can log on graphically), you must add the <c>xdm</c> init script to the default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):205
+msgid "Adding xdm to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):205
+#, no-wrap
+msgid "\n# <i>rc-update add xdm default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):209
+msgid "Now edit <path>/etc/conf.d/xdm</path> and alter the DISPLAYMANAGER variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):213
+msgid "Editing /etc/conf.d/xdm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):213
+#, no-wrap
+msgid "\nDISPLAYMANAGER=\"gdm\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):217
+msgid "If you reboot now, the GNOME Display Manager will prompt you for your username and password and will default to using GNOME as Desktop Environment (even though you will have the option of selecting a different one of course, choosing from those available in <path>/usr/share/xsessions/</path>). Thus, if you use GDM, you don't need to edit <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):225
+msgid "To use the functionality of <c>hald</c> you need to add your user to the <c>plugdev</c> group. If you want support for devices not handled by the <c>nautilus</c> file manager, or if you're not using <c>nautilus</c> at all, you might want to make sure that <c>gnome-volume-manager</c> is built with the <c>automount</c> USE flag, and that it's started every time you login."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gnupg-user.xml.pot b/doc/gettext/gnupg-user.xml.pot
new file mode 100644
index 0000000..a5d0ab1
--- /dev/null
+++ b/doc/gettext/gnupg-user.xml.pot
@@ -0,0 +1,667 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):6
+msgid "GnuPG Gentoo User Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail:link):9
+msgid "humpback@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail):9
+msgid "Gustavo Felisberto"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail:link):12
+msgid "zhen@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail):12
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail:link):15
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail):15
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(abstract):18
+msgid "This small guide will teach you the basics of using GnuPG, a tool for secure communication."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(version):27
+msgid "1.13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(date):28
+msgid "2010-06-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):33
+msgid "What you will get in this guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):36
+msgid "This guide assumes that you are familiar with public-key cryptography, encryption, and digital signatures. If this is not the case jump to <uri link=\"#doc_chap6\">Public Key Cryptography</uri> or take a look at the <uri link=\"http://www.gnupg.org/documentation/guides.html\">GnuPG handbook</uri>, chapter 2, and then come back."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):44
+msgid "This guide will teach you how to install GnuPG, how to create your key pair, how to add keys to your keyring, how to submit your public key to a key server and how to sign, encrypt, verify or decode messages you send or receive. You will also learn how to encrypt files on your local computer to prevent people from reading their contents."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):55
+msgid "Installation of required software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):58
+msgid "At a very basic level you need to <c>emerge gnupg</c>. Many aplications today have some sort of support for gpg, so having <e>crypt</e> in your USE variable is probably a good idea. If you wish to have an email client capable of using gnupg you can use pine (<c>emerge pinepgp</c>), mutt (<c>emerge mutt</c>), Mozilla Thunderbird (<c>emerge thunderbird</c>), evolution (evolution is a GNOME Microsoft Outlook work alike) and KDE's own KMail (KMail is part of the kdepim package)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):68
+msgid "<c>Kgpg</c> might interest you if you use KDE. This small program allows you to generate key pairs, import keys from ASCII files, sign imported keys, export keys and a few more features."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):79
+msgid "Generating your key and adding keys to your public keyring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):81
+msgid "Creating your key"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):84
+msgid "To create your key, just run <c>gpg --gen-key</c>. The first time you run it, it will create some directories; run it again to create the keys:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):89
+msgid "key generation process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):89
+#, no-wrap
+msgid "\n$ <i>gpg --gen-key</i>\ngpg (GnuPG) 1.0.7; Copyright (C) 2002 Free Software Foundation, Inc.\nThis program comes with ABSOLUTELY NO WARRANTY.\nThis is free software, and you are welcome to redistribute it\nunder certain conditions. See the file COPYING for details.\n\nPlease select what kind of key you want:\n   (1) DSA and ElGamal (default)\n   (2) DSA (sign only)\n   (4) ElGamal (sign and encrypt)\n   (5) RSA (sign only)\n   Your selection? <i>1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):104
+msgid "Here you can choose the type of key you want to use. Most users will go for the default DSA and ElGamal. Next is the key size - remember that bigger is better but don't use a size larger than 2048 with DSA/ElGamal keys. Generally 1024 is more than enough for normal email."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):111
+msgid "After size comes the expiration date. Here smaller is better, but most users can go for a key that never expires or to something like 2 or 3 years."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):116
+msgid "Choosing key size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):116
+#, no-wrap
+msgid "\nDSA keypair will have 1024 bits.\nAbout to generate a new ELG-E keypair.\n              minimum keysize is  768 bits\n              default keysize is 1024 bits\n    highest suggested keysize is 2048 bits\n    What keysize do you want? (1024) <i>2048</i>\nRequested keysize is 2048 bits       \nPlease specify how long the key should be valid.\n         0 = key does not expire\n &lt;n&gt;= key expires in n days\n &lt;n&gt;w = key expires in n weeks\n &lt;n&gt;m = key expires in n months\n &lt;n&gt;y = key expires in n years\n Key is valid for? (0) <i>0</i>\nKey does not expire at all\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):134
+msgid "Now it is time to enter some personal information about yourself. If you are going to send your public key to other people you have to use your real email address here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):140
+msgid "Entering user information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):140
+#, no-wrap
+msgid "\nIs this correct (y/n)? <i>y</i>\n                        \nYou need a User-ID to identify your key; the software constructs the user id\nfrom Real Name, Comment and Email Address in this form:\n\"Heinrich Heine (Der Dichter) &lt;heinrichh@duesseldorf.de&gt;\"\n\nReal name: <i>John Doe</i>\nEmail address: <i>john@nowhere.someplace.flick</i>\nComment: <i>The Real John Doe</i>\nYou selected this USER-ID:\n\"John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\"\n\nChange (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? <i>O</i> \nYou need a Passphrase to protect your secret key.    \n\nEnter passphrase: \n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):159
+msgid "Now enter your key passphrase twice. It is a good idea to use a strong password. If someone ever gets hold of your private key and cracks your password, they will be able to send messages signed by \"you\", making everyone believe the mails were sent by you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):166
+msgid "Next, GnuPG will generate your key. Moving the mouse or having a mp3 playing in the background will help speed up the process because it generates random data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):174
+msgid "Generating a revocation certificate"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(impo):177
+msgid "This part is very important and you must do it <e>NOW</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):181
+msgid "After creating your keys you should create a revocation certificate. Doing this allows you to revoke your key in case something nasty happens to your key (someone gets hold of your key/passphrase)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):187
+msgid "Generating revoke certificate"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):187
+#, no-wrap
+msgid "\n$ <i>gpg --list-keys</i>\n/home/humpback/.gnupg/pubring.gpg\n---------------------------------\npub  1024D/75447B14 2002-12-08 John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\nsub  2048g/96D6CDAD 2002-12-08\n\n$ <i>gpg --output revoke.asc --gen-revoke 75447B14</i>\n\nsec  1024D/75447B14 2002-12-08   John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\n\nCreate a revocation certificate for this key? <i>y</i>\nPlease select the reason for the revocation:   \n  0 = No reason specified\n  1 = Key has been compromised\n  2 = Key is superseded\n  3 = Key is no longer used\n  Q = Cancel\n(Probably you want to select 1 here)\nYour decision? <i>1</i>\nEnter an optional description; end it with an empty line:\n&gt; <i>Someone cracked me and got my key and passphrase</i>\n&gt;\nReason for revocation: Key has been compromised\nSomeone cracked me and got my key and passphrase\nIs this okay? <i>y</i>\n\nYou need a passphrase to unlock the secret key for\nuser: \"John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\"\n1024-bit DSA key, ID 75447B14, created 2002-12-08\n\nASCII armored output forced.\nRevocation certificate created.\n\nPlease move it to a medium which you can hide away; if Mallory gets\naccess to this certificate he can use it to make your key unusable.\nIt is smart to print this certificate and store it away, just in case\nyour media become unreadable.  But have some caution:  The print system of\nyour machine might store the data and make it available to others!\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):228
+msgid "The <c>gpg --list-keys</c> command lists keys in your public keyring. You may use it to see the ID of your key so that you can create the revocation certificate. Now it is a good idea to copy all the .gnupg directory and the revocation certificate (in ASCII armor - <path>revoke.asc</path>) to some secure medium (two floppy's or a CD-R you store in safe location). Remember that <path>revoke.asc</path> can be used to revoke your keys and make them unusable in the future."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(note):238
+msgid "If you have several email addresses that you would like to use with this key, you can run <c>gpg --edit-key YOUR_ID</c> and then use the <c>adduid</c> command. It will ask you for the name, email and comment of the second ID you will be using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):248
+msgid "Exporting keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):251
+msgid "To export your key, you type <c>gpg --armor --output john.asc --export john@nowhere.someplace.flick</c>. You can almost always use the key ID or something that identifies the key (here we used an email address). John now has a <path>john.asc</path> that he can send his friends, or place on his web page so that people can communicate safely with him."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):262
+msgid "Importing keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):265
+msgid "To add files to your public keyring, you must first import it, then check the key fingerprint. After you have verified the fingerprint you should validate it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(note):270
+msgid "You should be careful when verifying keys. This is one of the weak points of public key cryptography."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):275
+msgid "Now we will be adding Luis Pinto's (a friend of mine) public key to our public keyring. After giving him a call and asking him for his key fingerprint, I compare the fingerprint with the output of the <c>fpr</c> command. As the key is authentic, I add it to the public keyring. In this particular case, Luis's key will expire in 2003-12-01 so I am asked if I want my signature on his key to expire at the same time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):284
+msgid "Importing and signing keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):284
+#, no-wrap
+msgid "\n$ <i>gpg --import luis.asc</i>\ngpg: key 462405BB: public key imported\ngpg: Total number processed: 1\ngpg:               imported: 1\n$ <i>gpg --list-keys</i>\n/home/humpback/.gnupg/pubring.gpg\n---------------------------------\npub  1024D/75447B14 2002-12-08 John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\nsub  2048g/96D6CDAD 2002-12-08\n\npub  1024D/462405BB 2002-12-01 Luis Pinto &lt;lmpinto@student.dei.uc.pt&gt;\nuid                            Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\nsub  4096g/922175B3 2002-12-01 [expires: 2003-12-01]\n\n$ <i>gpg --edit-key lmpinto@dei.uc.pt</i>\ngpg (GnuPG) 1.0.7; Copyright (C) 2002 Free Software Foundation, Inc.\nThis program comes with ABSOLUTELY NO WARRANTY.\nThis is free software, and you are welcome to redistribute it\nunder certain conditions. See the file COPYING for details.\n\n\ngpg: checking the trustdb\ngpg: checking at depth 0 signed=0 ot(-/q/n/m/f/u)=0/0/0/0/0/1\npub  1024D/462405BB  created: 2002-12-01 expires: 2003-12-01 trust: -/-\nsub  4096g/922175B3  created: 2002-12-01 expires: 2003-12-01\n(1)  Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\n(2). Luis Pinto &lt;lmpinto@student.dei.uc.pt&gt;\n\nCommand&gt; <i>fpr</i>\npub  1024D/462405BB 2002-12-01 Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\n             Fingerprint: F056 3697 ADE3 CF98 B80B  8494 0AD3 E57B 4624 05BB\n     \nCommand&gt; <i>sign</i>\nReally sign all user IDs? <i>y</i>\n                           \npub  1024D/462405BB  created: 2002-12-01 expires: 2003-12-01 trust: -/-\n             Fingerprint: F056 3697 ADE3 CF98 B80B  8494 0AD3 E57B 4624 05BB\n\n     Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\n     Luis Pinto &lt;lmpinto@student.dei.uc.pt&gt;\n\nThis key is due to expire on 2003-12-01.\nDo you want your signature to expire at the same time? (Y/n) <i>Y</i>\nHow carefully have you verified the key you are about to sign actually belongs\nto the person named above?  If you don't know what to answer, enter \"0\".\n\n   (0) I will not answer. (default)\n   (1) I have not checked at all.\n   (2) I have done casual checking.\n   (3) I have done very careful checking.\n\n   Your selection? <i>3</i>\nAre you really sure that you want to sign this key\nwith your key: \"John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\"\n\nI have checked this key very carefully.\n\nReally sign? <i>y</i>\n              \nYou need a passphrase to unlock the secret key for\nuser: \"John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\"\n1024-bit DSA key, ID 75447B14, created 2002-12-08\n\nCommand&gt; <i>check</i>\nuid  Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\nsig!3       462405BB 2002-12-01   [self-signature]\nsig!3       75447B14 2002-12-08   John Doe (The Real John Doe) &lt;john@nowhe\nuid  Luis Pinto &lt;lmpinto@student.dei.uc.pt&gt;\nsig!3       462405BB 2002-12-01   [self-signature]\nsig!3       75447B14 2002-12-08   John Doe (The Real John Doe) &lt;john@nowhe\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):362
+msgid "Exchanging keys with keyservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):364
+msgid "Sending keys to keyservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):367
+msgid "Now that you have your key, it is probably a good idea to send it to the world key server. There are a lot of keyservers in the world and most of them exchange keys between them. Here we are going to send John Doe's key to the subkeys.pgp.net server. This uses HTTP, so if you need to use a proxy for HTTP traffic don't forget to set it (<c>export http_proxy=http://proxy_host:port/</c>). The command for sending the key is: <c>gpg --keyserver subkeys.pgp.net --keyserver-options honor-http-proxy --send-key 75447B14</c> where <c>75447B14</c> is the key ID. If you don't need a HTTP proxy you can remove the <e>--keyserver-options honor-http-proxy</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):379
+msgid "You can also send other people's keys that you have signed to the keyserver. We could send Luis Pinto's key to the keyserver. This way someone who trusts your key can use the signature that you have placed there to trust Luis's key."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):388
+msgid "Getting Keys from keyservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):391
+msgid "Now we are going to search for Gustavo Felisberto's key and add it to the keyring of John Doe (just in case you did not notice Gustavo Felisberto is the author this guide :))."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):397
+msgid "Searching keys from keyservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):397
+#, no-wrap
+msgid "\n$ <i>gpg --keyserver subkeys.pgp.net --keyserver-options honor-http-proxy --search-keys humpback@felisberto.net</i>\ngpg: searching for \"humpback@felisberto.net\" from HKP server subkeys.pgp.net\nKeys 1-5 of 5 for \"humpback@felisberto.net\"\n(1)Gustavo Felisberto (apt-get install anarchy) &lt;humpback@felisberto.net&gt; 1024\n  created 2002-12-06, key B9F2D52A\n(2)Gustavo Felisberto &lt;humpback@altavista.net&gt; 1024\n  created 1999-08-03, key E97E0B46\n(3)Gustavo A.S.R. Felisberto &lt;humpback@altavista.net&gt; 1024\n  created 1998-12-10, key B59AB043\n(4)Gustavo Adolfo Silva Ribeiro Felisberto &lt;humpback@altavista.net&gt; 1024\n  created 1998-08-26, key 39EB133D\n(5)Gustavo Adolfo Silva Ribeiro Felisberto &lt;humpback@altavista.net&gt; 1024\n  created 1998-06-14, key AE02AF87\n  Enter number(s), N)ext, or Q)uit &gt;<i>1</i>\ngpg: requesting key B9F2D52A from HKP keyserver subkeys.pgp.net\ngpg: key B9F2D52A: public key imported\ngpg: Total number processed: 1\ngpg:               imported: 1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):418
+msgid "As you can see from the server response I have a few keys submitted to the key server, but I currently only use <e>B9F2D52A</e>. Now John Doe can get it and sign it if he trusts it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):429
+msgid "Using a GPG Agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):431
+msgid "What is a GPG Agent?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):434
+msgid "Sometimes working with certain applications requires you to use your GPG key very frequently, which means that you have to type your passphrase a lot of times. Several applications used to support a passphrase caching mechanism to make life easier for users. However, this disallowed sharing this cache across programs (how secure would that be?) and forced applications to reinvent the wheel over and over again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):443
+msgid "A GPG agent is a separate application that GPG uses to cache the passphrase in a standard and secure way. It allows applications to use GPG concurrently: if you enter your passphrase while working in one application, the other application can work with GPG without reiterating the request for the passphrase to unlock the key - if the GPG agent is configured to allow so, of course."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):452
+msgid "Gentoo provides a few GPG agent applications. The <c>app-crypt/gnupg-1.9.*</c> package contains what could be considered the reference one, and will be the one we'll use in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):461
+msgid "Installing and Configuring gpg-agent and pinentry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):464
+msgid "You should install <c>gnupg-1.9.*</c>, which includes <c>gpg-agent</c>, and <c>pinentry</c>. <c>pinentry</c> is the helper application that gpg-agent uses to request the passphrase in a graphical window. It comes in three flavors: it can popup a window using the gtk+, Qt, or curses library (depending on the USE flag you set when emerging it)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):472
+msgid "Installing gpg-agent and pinentry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):472
+#, no-wrap
+msgid "\n# <i>emerge \\&gt;=gnupg-1.9.20 pinentry</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):476
+msgid "Next, create a file called <path>~/.gnupg/gpg-agent.conf</path> and enter the following lines which define the default timeout of the passphrase (e.g. 30 minutes) and the application to be called for when the passphrase should be retrieved the first time (e.g. the Qt version of pinentry)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):483
+msgid "Editing ~/.gnupg/gpg-agent.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):483
+#, no-wrap
+msgid "\npinentry-program /usr/bin/pinentry-qt\nno-grab\ndefault-cache-ttl 1800\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):489
+msgid "Now configure GnuPG to use an agent when appropriate. Edit <path>~/.gnupg/gpg.conf</path> and add the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):494
+msgid "Configuring GnuPG to use a GPG Agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):494
+#, no-wrap
+msgid "\nuse-agent\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):498
+msgid "Now your system is (almost) set to use the GPG agent."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):505
+msgid "Automatically Starting the GPG Agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):508
+msgid "If you use KDE as graphical environment, edit <path>/usr/kde/3.x/env/agent-startup.sh</path> (system-wide) or <path>~/.kde/env/gpgagent.sh</path> (local user) and add the following command to it to have KDE automatically starting the GPG agent:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):515
+msgid "Make KDE automatically start the GPG agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):515
+#, no-wrap
+msgid "\neval \"$(gpg-agent --daemon)\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):519
+msgid "If you use a different graphical environment, put that line (the same one as mentioned above) in <path>~/.xinitrc</path> (if you use <c>startx</c>) or <path>~/.xsession</path> (if you use XDM/GDM/KDM/...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):530
+msgid "Working with documents"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):532
+msgid "Encrypting and signing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):535
+msgid "Let's say that you have a file that you wish to send Luis. You can encrypt it, sign it, or encrypt it and sign it. Encrypting means that only Luis will be able to open it. The signature tells Luis that it was really you who created the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):542
+msgid "The next three commands will do just that, encrypt, sign and encrypt/sign."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):546
+msgid "Encrypting and Signing files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):546
+#, no-wrap
+msgid "\n$ <i>gpg --output doc.gpg --encrypt --recipient lmpinto@dei.uc.pt doc_to_encrypt</i>\n$ <i>gpg --output doc.gpg --sign --recipient lmpinto@dei.uc.pt doc_to_sign</i>\n$ <i>gpg --output doc.gpg --encrypt --sign --recipient lmpinto@dei.uc.pt doc_to_encrypt_and_sign</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):552
+msgid "This will create binary files. If you wish to create ASCII files, just add a <c>--clearsign</c> to the beginning of the command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):560
+msgid "Decrypting and verifying signatures"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):563
+msgid "Suppose that you have received a file which is encrypted to you. The command to decrypt it is <c>gpg --output document --decrypt encrypted_doc.gpg</c>. This will decrypt the document and verify the signature (if there is one)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):572
+msgid "Encrypting and decrypting without keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):575
+msgid "It is also possible to encrypt files using passwords instead of keys. Well, the password itself will function as the key - it will be used as a <e>symmetric cypher</e>. You can encrypt the file using <c>gpg</c>'s <c>--symmetric</c> argument; decrypting uses the same command as we talked about before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):582
+msgid "Encrypting files using a password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):582
+#, no-wrap
+msgid "\n$ <i>gpg --output document.gpg --symmetric document</i>\n<comment>(GnuPG will ask for a passphrase and a passphrase verification)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):590
+msgid "Advanced Features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):593
+msgid "There are some nice advanced features in GnuPG. To find them, open the <path>~/.gnupg/gpg.conf</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):598
+msgid "~/.gnupg/gpg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):598
+#, no-wrap
+msgid "\n#keyserver x-hkp://subkeys.pgp.net\n#keyserver-options auto-key-retrieve include-disabled include-revoked\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):603
+msgid "Search for the above two lines and uncomment them. With this any time GnuPG needs to check a signature and it does not find the public key on the local keyring it will contact the key server at <uri link=\"http://subkeys.pgp.net:11371/\">subkeys.pgp.net</uri> and will try to fetch it from there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):611
+msgid "Another nice command is <c>gpg --refresh-keys</c>. This will contact the keyserver defined in the options file and refresh public keys in your local key ring from there, searching for revoked keys, new IDs, and new signatures on keys. You should probably run this once or twice a month so that if someone revokes his key you will be notified."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):624
+msgid "GnuPG interfaces"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):626
+msgid "About email signatures"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):629
+msgid "95% of the time you will use GnuPG with email, signing/encrypting your outgoing messages and reading signed/encrypted messages. So it is only fair that I talk about that first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):635
+msgid "There are two ways two sign/encrypt a email with GnuPG, the old way and the new way :). In the old way messages would appear in plain text, with no possible formatting and attached files would be unsigned/unencrypted. Here is an example of a message signed the old way:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):642
+msgid "A plain text signature"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):642
+#, no-wrap
+msgid "\n-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nTest message\n\n-----BEGIN PGP SIGNATURE-----\nVersion: PGPfreeware 6.5.8 for non-commercial use\n\niQA/AwUBP8461jMX0745gR7AEQIEOwCg011GbufXO3ED3FkLWXmfzg7xm1cAoJD0\n0EU3Kd2EKNCqataEqM5qjpPs\n=LchZ\n-----END PGP SIGNATURE-----\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):657
+msgid "Messages this way are no good in today's world, where we have nice GUIs and email readers that understand html."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):662
+msgid "To solve this an addition to the MIME (Multipurpose Internet Mail Extensions) was created. This adds a field to the email that tells the mail reader that the full content of the message is signed and/or encrypted. The problem with this is that not all mail readers support this. And some even mess up the content; Microsoft's Outlook is famous for not working with this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):673
+msgid "Kgpg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):676
+msgid "Kgpg is a nice GUI for GnuPG. In the main screen you can paste the text that you wish to sign or encrypt, and you can also paste the ASCII armored text that you which to decrypt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(figure:link):682
+msgid "/images/kgpg1.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(figure:short):682
+msgid "kgpg main window"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):684
+msgid "In this image you can see the Kgpg main window with ASCII armored and encrypted text pasted into it. From here you can decrypt it (you will have to provide your password), encrypt other files, paste new text to sign...."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(figure:link):690
+msgid "/images/kgpg2.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(figure:short):690
+msgid "kgpg key manage window"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):692
+msgid "Now you can see the key managing window. From here we see our good key for John Doe. The two trusted keys for Gustavo and Luis, and the untrusted key for Daniel Robbins (I still have not given him a call to check his fingerprint :))."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):701
+msgid "Seahorse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):704
+msgid "Seahorse aims to be a GnuPG GUI interface for the Gnome desktop. The software has been evolving fast, but it still lacks many important features that can be found in Kgpg or the command line version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):713
+msgid "Enigmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):716
+msgid "Enigmail is a plug-in for Mozilla-based email clients (such as Thunderbird and Seamonkey) that is pretty simple to configure. In Seamonkey, you just go to Preferences -&gt; Privacy &amp; Security -&gt; Enigmail. There you enter your key email and that's it. You must first <c>emerge enigmail</c> to use it with Thunderbird. Then you can configure it by going to Edit -&gt; Account Settings -&gt; OpenPGP Security."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):725
+msgid "Mails that come with an untrusted pgp or gpg signature will be marked with a broken pen. Others that have good signatures will appear with a nice straight pen. Enigmail even comes with the ability to get keys from keyservers, but if it has problems it will print some very weird messages (but you still remember how to use the command line, right?)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):736
+msgid "KMail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):739
+msgid "If you have the <c>crypt</c> USE flag set, KMail will be compiled with gpg support, and will be able to encrypt and decrypt inline PGP mails automatically as well as encrypting OpenPGP/MIME mails. If you want to decrypt OpenPGP/MIME mails as well (which you probably want) you need to have a running GPG agent (see <uri link=\"#gpg-agent\">Using a GPG Agent</uri>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):747
+msgid "You can verify if KMail is properly configured by going to <c>Settings</c>, <c>Configure KMail</c>, <c>Security</c>, <c>Crypto Backends</c>. You should see a GpgME-based backend listed and you should be able to fill the OpenPGP checkbox. If it is listed but grayed out, click on <c>Rescan</c>. If the GpgME-based backend remains grayed out, KMail is not working properly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):755
+msgid "If you still are unable to get KMail to behave, please see the <uri link=\"http://kmail.kde.org/kmail-pgpmime-howto.html\">KMail PGP HowTo</uri> page for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):764
+msgid "Claws-Mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):767
+msgid "This mail reader is <e>very</e> fast with big mailboxes, has all the nice features one wants in mail readers and works pretty well with gpg. The only problem is that it does not work with the old PGP signatures, so when you receive those kind of mails you have to hand check the signatures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):774
+msgid "To use your gpg key with Claws-Mail just go to the account configuration and select the privacy tab. Once there just choose which key to use, probably most users will go with the default key."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):785
+msgid "Public Key Cryptography"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):787
+msgid "Basic Public Key Cryptography"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):790
+msgid "The concept of public key cryptography was originally devised by Whitfield Diffie and Martin Hellman in 1976. When I first heard the words \"public key\" and \"cryptography\" in the same sentence back in '93 I thought to myself that it would be impossible to do such a thing. In those days there was no Internet (well there was, but not for me) so I went to the public library and asked for books on Cryptography. I must say that I was 16 at the time so the clerk there looked to me in astonishment and brought me a book for children on substitution cyphers (those where you change a letter for another like the famous Caesar Cypher or ROT-13 (Tragbb Ebpxf, naq lbh xabj vg vf tbbq orpnhfr lbh ner ernqvat guvf qbp.), (<c>emerge rotix</c> if you cannot read the preceding text)). I was very upset with this and started to search for more info. It is good to have mathematicians in the family, because as soon as I talked to one of them I was introduced to a new world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):806
+msgid "And now a bit of mathematics:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):810
+msgid "Mathematical Concepts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):810
+#, no-wrap
+msgid "\nDefinitions:\n\n1- A prime number is a positive integer number greater than one that is only\ndivisible by 1 and itself (the remainder of the division is 0).\nThe first 8 prime numbers are 2,3,5,7,11,13,17,19\n\nTheorem (No proof here)\n1- For any non prime positive integer it is possible to break it as the product\nof prime numbers, and that product is unique.\n4=2*2\n6=2*3\n8=2*4=2*2*2\n10=2*5\n12=2*6=2*2*3\n\n\"Facts\":\n1- It is mathematically easy to multiply two large integers\n2- It is hard to find the prime factors of a given positive integer.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):831
+msgid "If I give you the number 35 and I tell you that this number is the product of two prime numbers it is easy to find that it was 5 and 7. But if I tell you the same for 1588522601 you will spend alot of time (or CPU cycles) to find it was 49811*31891. And if this number is really really big this task becomes \"impossible\". So now if I give the world my large number that is the product of two primes I know something about that number that no one else knows."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):840
+msgid "This is the basis for Public Key Cryptography (PKC) implementations today. As an (unrealistic) example, I give anyone my number and that someone will use if for cyphering a message to me. Anyone can see the cyphered message, because I am the only one who knows a shortcut to read it, anyone else will first have to \"split\" that big number to be able to read the message, and it is a \"fact\" that it is impossible to do that in a short amount of time (todays methods and the fastest computers in the world would take thousands of years to do that). In this setup the two large prime numbers would be called the PRIVATE KEY, and the large non prime number is the PUBLIC KEY."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):852
+msgid "In practice this is not 100% accurate with reality, but will give a good idea to the newcomer. For more information, check Wikipedia on the <uri link=\"http://en.wikipedia.org/wiki/Diffie-Hellman\">Diffie-Hellman</uri> protocol. For even more info go to the public library and grab a copy of the <uri link=\"http://www.cacr.math.uwaterloo.ca/hac/\">\"Handbook of Applied Cryptography\"</uri> by Alfred J. Menezes, Paul C. van Oorschot and Scott A. Vanstone. This book is also available online for free at the above site."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):862
+msgid "One consequence of the above is that if you cypher a message to me, and you loose the original uncyphered message you will no longer be able to retrieve it from the cyphered version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):871
+msgid "Signatures"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):874
+msgid "We already saw how someone can send us a cyphered message if they have our public key. But how do we know that the author of the message is really who he claims to be? Or in other words: If I receive an email from you how do I really know it was you and not someone else claiming to be you?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):881
+msgid "Remember me saying that PKC was not as simple as I had said? The idea is that when you cypher a message to me you sign it with your private key so that, when I receive it, I can first use your public key to check your signature and then use my private key to decypher the message. As you can see we could not do that in the setup I described before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):889
+msgid "It's also very important to sign messages so that you don't have to cypher them beforehand. Now you can create messages that can be read by anyone, but that come with your \"branding\". And if any single character is changed in the message it can (and will) be detected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):899
+msgid "Key Servers and Signed Keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):902
+msgid "But let's say that I have no previous contact with you until you send me a message: how do I get your public key, and how do I really know it is yours?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):907
+msgid "To solve this problem public Key Servers were created. When you create your key pair (Public and Private key), you send your public key to the key server. After this everyone can retrieve your key from there. This solves the problem of finding the key. But how do I really know that that key is the author's key? For this another concept must be introduced, and that is key signing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):915
+msgid "Key signing means that if I have the public key of another person, and I know <e>for sure</e> that it is really that persons key (it is my personal friend, someone I know in real life, etc.) I can sign that public key and send it to keyservers, that way I am telling the world: \"This key really belongs to the person it claims to belong.\". That way persons that have my public key and trust me can use that trust to trust other keys."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):924
+msgid "This can sometimes be confusing so let's see a real world situation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):928
+msgid "Let's imagine a 3 person situation: John, Mary, and Lisa. John is a good friend of Mary but does not know Lisa; Lisa is a good friend of Mary but does not know John. One day Lisa sends John a signed email. John will fetch Lisa's Public Key from the keyserver and test the message, if all went ok he will see that whoever wrote that message also created that key. But how do I know it was really the person it claims to be?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):937
+msgid "He then sees that it is signed by Mary, which he can check because he already has Mary's key and he trusts that key. With this ring of trust he continues to conclude that the email he received was really written by Lisa."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):943
+msgid "You are now ready to use this guide, you can go back to chapter 1 and learn how to use gpg."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):953
+msgid "Final thoughts and Credits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):955
+msgid "Some problems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):958
+msgid "I had some problems with photos in keys. Check the version you are using. If you have GnuPG 1.2.1-r1 and up you are probably OK, older versions may have problems. Also most keyservers don't like keys with photos, so you are better if you don't add photos."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):965
+msgid "The latest versions of gnupg don't seem to work with the <c>gpg --send-keys</c> that was used so send all keys in your keyring to the public server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):974
+msgid "What is not here"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):977
+msgid "<c>gpg</c> is a very complex tool, it lets you do much more than what I have covered here. This document is for the user who is new to GnuPG. For more information, you should check the <uri link=\"http://www.gnupg.org\">GnuPG Website</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):984
+msgid "I did not write about other tools like <c>pgp4pine</c>, <c>gpgpine</c>, <c>evolution</c> and maybe Windows tools, but I will probably extend this document in the future."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):993
+msgid "Credits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):996
+msgid "John Michael Ashley's <uri link=\"http://www.gnupg.org\">GnuPG Handbook</uri> it is a very good book for beginners."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):1001
+msgid "Swift (Sven Vermeulen) for pushing me to re-write this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):1005
+msgid "Everyone in the #gentoo-doc team you guys rock."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):1009
+msgid "Tiago Serra for getting me back to the privacy track."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/gpm.xml.pot b/doc/gettext/gpm.xml.pot
new file mode 100644
index 0000000..bbda33e
--- /dev/null
+++ b/doc/gettext/gpm.xml.pot
@@ -0,0 +1,191 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(guide:link):5
+msgid "/doc/en/gpm.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):6
+msgid "Using a Mouse within the Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(mail:link):9
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(mail):9
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(abstract):12
+msgid "This guide shows you how to set up and use GPM (the General Purpose Mouse server) from within a command line interface. This is especially useful for new Gentoo installations or for systems that cannot or do not use an X server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(version):22
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(date):23
+msgid "2006-02-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):26
+msgid "Getting GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):30
+msgid "If you've just installed Gentoo, you almost certainly don't have your mouse set up to work within a command line interface (CLI) yet. Or perhaps you can't use or don't need an X server, yet you still need to use a mouse. The solution is simple: <c>gpm</c>, the General Purpose Mouse server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):37
+msgid "First, you will need to get GPM:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):41
+msgid "Obtaining GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):41
+#, no-wrap
+msgid "\n# <i>emerge gpm</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):45
+msgid "You might have noticed a few messages during the compilation that warned about configuring the server. You must do this before starting GPM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):55
+msgid "Configuring GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):59
+msgid "Before you can use GPM, you will need to uncomment the lines corresponding to the location and protocol of your mouse. You do this by editing the GPM configuration file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):65
+msgid "Setting up GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):65
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/gpm</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):69
+msgid "In my case, I have a USB mouse on <path>/dev/input/mouse0</path>. So, I have uncommented <path>/dev/input/mice</path>, as this is the cumulative device for all mice on the system, and the appropriate protocol. Try using <path>/dev/input/mice</path> before <path>/dev/psaux</path>, as the latter is deprecated and can be disabled in the latest 2.6 kernels. If <path>/dev/input/mice</path> fails, then fall back to other devices. Here is my example <path>/etc/conf.d/gpm</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):79
+msgid "Example GPM config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):79
+#, no-wrap
+msgid "\n<comment>(Please uncomment the type of mouse you have and the appropriate MOUSEDEV entry)</comment>\n\n#MOUSE=ps2\nMOUSE=imps2\n#MOUSEDEV=/dev/psaux\nMOUSEDEV=/dev/input/mice\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):88
+msgid "If you have a wheelmouse, you will want to use the imps2 protocol, so uncomment that line. If imps2 and ps2 both fail to work for you, please refer to the GPM info page (<c>info gpm</c>) for other protocols to try. Also, if you want to be able to click on hyperlinks in terminals to navigate to a website, it is a good idea to follow the suggestion in the <c>/etc/conf.d/gpm</c> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):96
+msgid "Other options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):96
+#, no-wrap
+msgid "\n<comment>(Please uncomment this line if you want GPM to understand charsets\nused in URLs and names with ~ or : in them, etc.\nThis is a good idea to turn on!)</comment>\n\nAPPEND=\"-l \\\"a-zA-Z0-9_.:~/\\300-\\326\\330-\\366\\370-\\377\\\"\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):104
+msgid "The rest of the conf.d file contains other suggestions for your mouse server; uncomment the various options according to your needs. See <c>man gpm</c> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):115
+msgid "Running GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):119
+msgid "Now that your mouse server is installed and configured, it's time to start using it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):124
+msgid "The GPM init script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):124
+#, no-wrap
+msgid "\n# <i>/etc/init.d/gpm start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):128
+msgid "You should see a block cursor appear. Remember that only root can run the GPM init script. However, to avoid having to <c>su</c> and run the script every single time you begin a new session, why not set GPM to begin every time you turn on your computer?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):135
+msgid "Adding GPM to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):135
+#, no-wrap
+msgid "\n# <i>rc-update add gpm default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):139
+msgid "Now, whenever you start your computer, you'll be greeted by the console cursor by the time you get to the login prompt. The mouse server will continue to run even if you're not logged in as root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):150
+msgid "Working with GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):152
+msgid "Copying and pasting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):155
+msgid "Copying and pasting large blocks of text with a working mouse server is very easy. Simply highlight the text with the left mouse button (it will stay highlighted when you release the button), switch to a different terminal if you wish, position the cursor, and press the middle mouse button to paste the text where you placed the cursor. Note that you can copy and paste without ever leaving the terminal you started. This makes posting the output of error messages to the <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri> extremely simple."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):169
+msgid "Text-mode browsing and GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):172
+msgid "If you have a message on one screen and a text-mode web browser on the other, you can copy the error message by highlighting it, then change to the other terminal, left-click the appropriate text entry box to select it, and then press the middle mouse button. Voilà! Your error message can now be posted to the forums."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):180
+msgid "Though discussion of text-only browsers is somewhat beyond the scope of this guide, inevitably users will need to find a compatible console browser. Though <c>lynx</c> is most likely the oldest and well established browser, its interface has poor mouse support and recognition. Instead, try using <c>links</c> which has excellent mouse integration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):188
+msgid "Obtaining links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):188
+#, no-wrap
+msgid "\n# <i>emerge links</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):192
+msgid "This concludes the guide to using a mouse within the console. Happy mousing!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/grub-error-guide.xml.pot b/doc/gettext/grub-error-guide.xml.pot
new file mode 100644
index 0000000..510e9ea
--- /dev/null
+++ b/doc/gettext/grub-error-guide.xml.pot
@@ -0,0 +1,579 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(guide:link):5
+msgid "/doc/en/grub-error-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):6
+msgid "Gentoo Grub Error Collection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(author:title):8
+msgid "Thread Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(author):8
+msgid "Hartwig Brandl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(author:title):9 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(author:title):12
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(mail:link):10
+msgid "deathwing00@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(mail):10
+msgid "Ioannis Aslanidis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(mail:link):13
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(mail):13
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(abstract):16
+msgid "The objective of this error collection is to list the GRUB problems and errors people can be facing. All these solutions have been acquired through the cooperation of many users of the Gentoo Forums."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(version):26
+msgid "1.9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(date):27
+msgid "2008-01-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):30
+msgid "Starting notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):33
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):36
+msgid "Many thanks to <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=18420\">Earthwings</uri>, <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=39305\">penetrode</uri>, <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=41638\">loyaltonone</uri>, <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=4980\">pilla</uri>, <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=3139\">airhead</uri>, <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=13816\">nephros</uri>, <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=25859\">yamakawa</uri> and all the others for the suggestions on the original <uri link=\"http://forums.gentoo.org/viewtopic.php?t=122656\">thread</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):53
+msgid "Disclaimer warning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):56
+msgid "The examples provided are just examples. Be sure to change partition numbers and the like according to your systems specs. Follow the solutions provided by this document at your own risk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):67
+msgid "Grub loading, please wait..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):69 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):116 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):157 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):301 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):339 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):373 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):408 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):439 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):472 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):502 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):560 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):594 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):620 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):647 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):674 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):709
+msgid "Situation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):72
+msgid "Grub output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):72
+#, no-wrap
+msgid "\nGRUB loading stage 1.5\nGRUB loading, please wait...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):77
+msgid "After this message, the system stops. If you attempt to boot the system using a grub floppy, the problem disappears."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):85 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):131 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):314 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):351 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):385 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):424 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):454 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):486 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):513 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):576 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):605 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):631 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):657 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):685 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):728
+msgid "Solution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):88
+msgid "According to <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=3134\">The_Bell</uri> you could change the boot order in your BIOS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):94
+msgid "Tell your BIOS to not boot from your floppy first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):98
+msgid "<uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=39305\">penetrode</uri> wrote that this may also be due to bad CFLAGS settings. Although the current grub ebuild filters out <c>-fstack-protector</c>, it can't hurt to recompile grub with clean CFLAGS if nothing else helps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):105
+msgid "Using a clean CFLAG to rebuild GRUB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):105
+#, no-wrap
+msgid "\n# <i>CFLAGS=\"-O2 -march=i686 -fomit-frame-pointer -pipe\" emerge grub</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):114
+msgid "Grub Error 12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):119 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):304 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):342 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):376 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):415 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):446 ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):568
+msgid "Grub Output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):119
+#, no-wrap
+msgid "\n12 : Invalid device requested.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):123
+msgid "This error is returned if the device strings syntax is correct but other than that, an error occurred that isn't defined by any other error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):134
+msgid "When you installed grub in your boot record using the interactive commands, did you execute the two lines below in the grub prompt?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):139
+msgid "Interactive installation commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):139
+#, no-wrap
+msgid "\ngrub&gt; <i>root (hd0,0)</i>\ngrub&gt; <i>setup (hd0)</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):144
+msgid "(hd0,0) must be replaced with your boot partition and (hd0) with the HDD you have chosen. Remember that (hd0) will install the bootloader in the Master Boot Record of the first hard disk, the primary master."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):155
+msgid "Grub Error 15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):160
+msgid "This error can occur in two different stages of the GRUB configuration, either during the initial configuration (installing GRUB in the master boot record) or after booting the system and attempting to launch Linux (or any other entry)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):166
+msgid "Grub Output - Initial Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):166
+#, no-wrap
+msgid "\ngrub&gt; <i>root (hd0,0)</i>\n Filesystem type is xfs, partition type 0x83\n\ngrub&gt; <i>setup (hd0)</i>\n Checking if \"/boot/grub/stage1\" exists... no\n Checking if \"/grub/stage1\" exists... no\n\nError 15: File not found\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):177
+msgid "Grub Output - Booting an Entry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):177
+#, no-wrap
+msgid "\nBooting 'gentoo Linux'\n\nroot (hd0,0)\nFilesystem type is ext2fs, partition type 0x83\nkernel (hd0,0)/boot/kernel-2.4.20 root=/dev/hda3 vga=792\n\nError 15: File not found\nPress any key to continue...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):191
+msgid "Solution - Initial Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):194
+msgid "This error is returned if the specified file name cannot be found, but everything else (like the disk/partition info) is OK."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):199
+msgid "Frequently, the error notes a missing kernel image file. Make sure that the file it is referring to exists on your boot partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):204
+msgid "To find out the exact name of your kernel, boot from the installation cd, mount your root and (if applicable) boot partition. Next, chroot into your Gentoo system and do a listing of the available files to see what kernel images you have available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):211
+msgid "Verifying kernel image existence"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):211
+#, no-wrap
+msgid "\n# <i>cd /boot</i>\n# <i>ls</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):216
+msgid "This will list all the kernels that you've got on your boot partition. If your kernel is missing make sure that you compiled a kernel (using <c>genkernel</c> or manually):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):222
+msgid "Recompile the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):222
+#, no-wrap
+msgid "\n# <i>cd /usr/src/linux/</i>\n# <i>make menuconfig</i>\n# <i>make</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):228
+msgid "And that you copied it to your boot partition:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):232
+msgid "Copying the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):232
+#, no-wrap
+msgid "\n# <i>cp /usr/src/linux/arch/i386/boot/bzImage /boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):236
+msgid "Verify that the name of the kernel is exactly the same as the one mentioned in your <path>grub.conf</path> file. Also make sure that the <c>kernel</c> line in your <path>grub.conf</path> file is referring to that partition (either explicitly or implicitly)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):243
+msgid "Another reported mistake is to have the BIOS ignore the disk on which the kernel or grub stages reside. Also, the partition on which grub stores its stages should not use a software RAID-5 (or other striping technology) configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):252
+msgid "Solution - Booting an Entry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):255
+msgid "First, verify that the <c>root</c> and <c>setup</c> lines you have used are correct."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):260
+msgid "If you are certain they are valid, then you <e>might</e> be using a flawed GRUB version (0.93.20031222). Upgrade your Portage tree or mask this version of grub:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):266
+msgid "Masking Grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):266
+#, no-wrap
+msgid "\n<comment>(Execute this from within the chrooted environment)</comment>\n# <i>echo \"=sys-boot/grub-0.93.20031222\" &gt;&gt; /etc/portage/package.mask</i>\n# <i>emerge grub -p</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):272
+msgid "You could also try to use the <c>grub-install</c> script as is recommended by the GRUB authors:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):277
+msgid "Using grub-install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):277
+#, no-wrap
+msgid "\n<comment>(The --root-directory is needed if you are using a separate boot\npartition,\n otherwise you should leave it out)</comment>\n# <i>grub-install --root-directory=/boot /dev/hda</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):284
+msgid "When all this fails, your boot partition may be corrupt. Check the partition for errors:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):289
+msgid "Checking a partition for errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):289
+#, no-wrap
+msgid "\n<comment>(Make sure the boot partition, /dev/hda1 in this case, is unmounted)</comment>\n# <i>fsck -y /dev/hda1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):299
+msgid "Grub Error 17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):304
+#, no-wrap
+msgid "\nroot (hd0,0)\nfilesystem type unknown partition type 0x7\n\nError 17 : Cannot mount selected partition\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):317
+msgid "This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):322
+msgid "Be sure to check your root(x,y) settings in your grub.conf."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):326
+msgid "Also, if you are trying to boot Windows, make sure that your <path>grub.conf</path> file has the <c>root (hdX,Y)</c> (or <c>rootnoverify (hdX,Y)</c>) and <c>chainloader (hdX,Y)+1</c> in it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):337
+msgid "Grub Error 18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):342
+#, no-wrap
+msgid "\nkernel (hd1,4)/bzImage root=/dev/hdb7\n\nError 18: Selected cylinder exceeds max supported by BIOS\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):354
+msgid "This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):361
+msgid "Try an update for your BIOS and/or move your boot partition to the front (or at least into the appropriate range)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):371
+msgid "GRUB GRUB GRUB GRUB GRUB ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):376
+#, no-wrap
+msgid "\nGRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB\n  GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB\n...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):388
+msgid "According to <uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=3139\">airhead</uri> this can be caused by having your bios detect your disks automatically. Try to set your bios entry to User Type HDD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):395
+msgid "Another possibility is that you had Grub installed on your MBR and tried reinstalling it (for instance due to hard disk changes) but used the wrong <c>setup</c> and <c>root</c> commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):406
+msgid "Probing Devices to Guess BIOS Drives. This May Take a Long Time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):411
+msgid "While trying to install grub, it hangs after displaying the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):415
+#, no-wrap
+msgid "\n# <i>grub</i>\n\nProbing devices to guess BIOS drives. This may take a long time.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):427
+msgid "One reported cause was an exotic configuration of disk devices, like ultra/non-ultra DMA disks on one cable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):437
+msgid "When Installing Grub, It Just Hangs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):442
+msgid "When installing grub, it hangs:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):446
+#, no-wrap
+msgid "\n# <i>grub</i>\n<comment>(At this stage, the installation stops)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):457
+msgid "If you haven't got a floppy drive, have you used the --no-floppy switch?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):461
+msgid "Installing grub using the --no-floppy switch"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):461
+#, no-wrap
+msgid "\n# <i>grub --no-floppy</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):470
+msgid "Uncompressing Linux... Ok, booting the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):475
+msgid "The system hangs after displaying the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):479
+msgid "Linux Output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):479
+#, no-wrap
+msgid "\nUncompressing Linux... Ok, booting the kernel.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):489
+msgid "Strictly speaking, this is no grub error. One possible cause is that ACPI is not working correctly but is enabled in the kernel. Try to disable it in your bios or in your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):500
+msgid "Grub Just Shows a Grub Prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):505
+msgid "When booting the system, you receive a grub prompt instead of a list of entries you have defined in your <path>grub.conf</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):516
+msgid "Mount your boot partition and verify if the <path>grub/grub.conf</path> file exists."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):521
+msgid "Mounting and verifying"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):521
+#, no-wrap
+msgid "\n# <i>mount /dev/hda1 /mnt/gentoo/boot</i>\n# <i>cat /mnt/gentoo/boot/grub/grub.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):526
+msgid "Also make sure that the <path>menu.lst</path> symbolic link exists:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):530
+msgid "Verifying the symbolic link"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):530
+#, no-wrap
+msgid "\n# <i>ls -l /mnt/gentoo/boot/grub/menu.lst</i>\nlrwxrwxrwx  1 root root 9 Mar  7 14:00 /mnt/gentoo/boot/grub/menu.lst -&gt; grub.conf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):535
+msgid "If not, recreate the symbolic link:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):539
+msgid "Recreating the menu.lst symbolic link"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):539
+#, no-wrap
+msgid "\n# <i>cd /mnt/gentoo/boot/grub</i>\n# <i>ln -snf grub.conf menu.lst</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):544
+msgid "If this is the case, reinstall grub:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):548
+msgid "Reinstalling Grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):548
+#, no-wrap
+msgid "\n<comment>(Run from within the chrooted environment)</comment>\n# <i>grub-install --root-directory=/boot /dev/hda</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):558
+msgid "Could Not Find Device For /boot/boot: Not Found Or Not a Block Device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):563
+msgid "When running <c>grub-install</c> during the GRUB installation, you receive the following error:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):568
+#, no-wrap
+msgid "\n# <i>grub-install --root-directory=/boot /dev/hda</i>\nCould not find device for /boot/boot: not found or not a block device\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):579
+msgid "Check that you didn't forget the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):583
+msgid "Updating the mtab file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):583
+#, no-wrap
+msgid "\n# <i>grep -v rootfs /proc/mounts &gt; /etc/mtab</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):592
+msgid "The System Reboots After Hitting Return At The Grub Menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):597
+msgid "After hitting Return at the Grub menu during the system boot, the system reboots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):608
+msgid "Try disabling framebuffer support in your kernel. If this does not help, disable APM and ACPI."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):618
+msgid "After Hitting Return At The Grub Menu, The Screen Blanks Out"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):623
+msgid "After hitting Return at the Grub menu during system boot, the screen blanks out, but the system is responsive (for instance, your numlock led is switcheable)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):634
+msgid "Turn off framebuffer (typically remove <c>vga=XYZ</c> from your <path>grub.conf</path>) and check the processor architecture in your kernel config."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):645
+msgid "Missing Grub Image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):650
+msgid "When booting the system, you do not see that spify Gentoo splashscreen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):660
+msgid "First of all check if the splashscreen file you are referring to in your <path>grub.conf</path> really exists. If that is the case, go and check the grub ebuild. Maybe the patch for the splash image is commented out in the version that you are using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):672
+msgid "Failing To Boot Windows From a Second Harddrive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):677
+msgid "After selecting the Windows entry, the system refuses to boot without any clear reason as to why."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):688
+msgid "<uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=14595\">cyrillic</uri> informed us that you can \"map\" your disks in a different order by changing your <path>grub.conf</path>'s Windows entry like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):695
+msgid "Mapping disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):695
+#, no-wrap
+msgid "\ntitle Windows XP\n  map (hd0) (hd1)\n  map (hd1) (hd0)\n  chainloader (hd1,0)+1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):707
+msgid "Grub segfaults when trying to install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):712
+msgid "The situation described below is only relevant for grub-0.95.x at the moment of installing grub at the boot sector."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):717
+msgid "Installing Grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):717
+#, no-wrap
+msgid "\ngrub&gt; root (hd0,0)\n\ngrub&gt; setup (hd0)\n\nSegmentation fault\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):731
+msgid "This is a known bug related to this problem and has been fixed in grub 0.96. It is also known that grub 0.94 r1 and grub 0.94 r2 should work correctly. If that fails too, you can try to emerge grub-static which is currently stable on amd64 and unstable on x86 (~x86). Check out bug <uri link=\"http://bugs.gentoo.org/show_bug.cgi?id=79378\">#79378</uri> for additional information."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/guide-localization.xml.pot b/doc/gettext/guide-localization.xml.pot
new file mode 100644
index 0000000..2d98e32
--- /dev/null
+++ b/doc/gettext/guide-localization.xml.pot
@@ -0,0 +1,555 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(guide:link):5
+msgid "/doc/en/guide-localization.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):6
+msgid "Gentoo Linux Localization Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author):7
+msgid "Alexander Holler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):10
+msgid "Translator/Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):11
+msgid "slucy@uchicago.edu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):11
+msgid "Steven Lucy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):13 ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):16 ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):19 ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):22 ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):25
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):14
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):14
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):17
+msgid "pylon@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):17
+msgid "Lars Weiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):20
+msgid "dertobi123@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):20
+msgid "Tobias Scherbaum"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):23
+msgid "flammie@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):23
+msgid "Flammie Pirinen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):26
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(abstract):29
+msgid "This guide should help users localize their Gentoo Linux distribution to any European locale. It uses Germany as a case-study, since it is translated from the German doc. Includes configuration for use of the euro currency symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(version):35
+msgid "1.46"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(date):36
+msgid "2010-02-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):39
+msgid "Time zone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):43
+msgid "In order to keep time properly, you need to select your timezone so that your system knows where it is located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then set your timezone in <path>/etc/conf.d/clock</path>. Please avoid the <path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):52
+msgid "Setting the timezone information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):52
+#, no-wrap
+msgid "\n# <i>ls /usr/share/zoneinfo</i>\n<comment>(Suppose you want to use Brussels)</comment>\n<comment>(First copy the proper zone to localtime)</comment>\n# <i>cp /usr/share/zoneinfo/Europe/Brussels /etc/localtime</i>\n<comment>(Now specify your timezone)</comment>\n# <i>nano -w /etc/conf.d/clock</i>\nTIMEZONE=\"Europe/Brussels\"\n\n# <i>date</i>\nWed Mar  8 00:46:05 CET 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):65
+msgid "Make sure that the timezone indicator (in this case \"CET\") is correct for your area."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):70
+msgid "You can set the value of <c>TZ</c> to be everything after the <path>/usr/share/zoneinfo</path> in your shell rc file (<path>.bash_profile</path> for bash) for a user-level setting. In this case <c>TZ=\"Europe/Berlin\"</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):82
+msgid "Hardware Clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):86
+msgid "In most Gentoo Linux installations, your hardware clock is set to UTC (or GMT, Greenwich Mean Time) and then your timezone is taken into account to determine the actual, local time. If, for some reason, you need your hardware clock not to be in UTC, you will need to edit <path>/etc/conf.d/clock</path> and change the value of <c>CLOCK</c> from <c>UTC</c> to <c>local</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):95
+msgid "local vs. GMT clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):95
+#, no-wrap
+msgid "\n<comment>(recommended:)</comment>\nCLOCK=\"UTC\"\n<comment>(or:)</comment>\nCLOCK=\"local\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):107
+msgid "Locale system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):109
+msgid "What are locales?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):112
+msgid "A Locale is a set of information that most programs use for determining country and language specific settings. The locales and their data are part of the system library and can be found at <path>/usr/share/locale</path> on most systems. A locale name is generally named <c>ab_CD</c> where <c>ab</c> is your two (or three) letter language code (as specified in ISO-639) and <c>CD</c> is your two letter country code (as specified in ISO-3166). Variants are often appended to locale names, e.g. <c>en_GB.UTF-8</c> or <c>de_DE@euro</c>. Please explore <uri link=\"http://en.wikipedia.org/wiki/Locale\">Wikipedia</uri> to read more about locales and related articles."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):127
+msgid "Environment variables for locales"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):130
+msgid "Locale settings are stored in environment variables. These are typically set in the <path>/etc/env.d/02locale</path> (for system-wide settings) and <path>~/.bashrc</path> (for user-specific settings) file. The variables controlling different aspects of locale settings are given in the table below. All of them take one name of a locale in <c>ab_CD</c> format given above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(th):141
+msgid "Variable name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(th):142
+msgid "Explanation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):145
+msgid "LANG"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):146
+msgid "Defines all locale settings at once, while allowing further individual customization via the LC_* settings below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):152
+msgid "LC_COLLATE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):153
+msgid "Define alphabetical ordering of strings. This affects e.g. output of sorted directory listing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):159
+msgid "LC_CTYPE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):160
+msgid "Define the character handling properties for the system. This determines which characters are seen as part of alphabet, numeric and so on. This also determines the character set used, if applicable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):167
+msgid "LC_MESSAGES"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):168
+msgid "Programs' localizations for applications that use message based localization scheme (majority of Gnu programs, see next chapters for closer information which do, and how to get the programs, that don't, to work)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):175
+msgid "LC_MONETARY"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):176
+msgid "Defines currency units and formatting of currency type numeric values."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):179
+msgid "LC_NUMERIC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):180
+msgid "Defines formatting of numeric values which aren't monetary. Affects things such as thousand separator and decimal separator."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):186
+msgid "LC_TIME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):187
+msgid "Defines formatting of dates and times."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):190
+msgid "LC_PAPER"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):191
+msgid "Defines default paper size."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):194
+msgid "LC_ALL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):195
+msgid "A special variable for overriding all other settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):201
+msgid "Some programs are written in such a way that they expect traditional English ordering of the alphabet, while some locales, most notably the Estonian one, use a different ordering. Therefore it's recommended to explicitly set LC_COLLATE to C when dealing with system-wide settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(warn):208
+msgid "Using LC_ALL is strongly discouraged as it can't be overridden later on. Please use it only when testing and <e>never</e> set it in a startup file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):213
+msgid "Most typically users only set the LANG variable on the global basis. This example is for a unicode German locale:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):218
+msgid "Setting the default system locale in /etc/env.d/02locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):218
+#, no-wrap
+msgid "\nLANG=\"de_DE.UTF-8\"\nLC_COLLATE=\"C\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):223
+msgid "Use <c>de_DE@euro</c> as your LANG if you want to use the Euro currency symbol (€)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):228
+msgid "It's also possible, and pretty common especially in a more traditional UNIX environment, to leave the global settings unchanged, i.e. in the \"<c>C</c>\" locale. Users can still specify their preferred locale in their own shell RC file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):235
+msgid "Setting the user locale in ~/.bashrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):235
+#, no-wrap
+msgid "\nexport LANG=\"de_DE.UTF-8\"\nexport LC_COLLATE=\"C\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):240
+msgid "Another way of configuring system is to leave it in the default C locale, but enable UTF-8 character representation at the same time. This option is achieved using the following settings in <path>/etc/env.d/02locale</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):246
+msgid "Using traditional C locale while specifying UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):246
+#, no-wrap
+msgid "\nLC_CTYPE=de_DE.UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):250
+msgid "Using the above snippet, users will be able to see localized file names properly, while not being forced to your preferred language."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):255
+msgid "For message based localization to work in programs that support it, you will probably need to have programs compiled with the <c>nls</c> (Native language support) USE flag set. Most of the programs using nls also need the gettext library to extract and use localized messages. Of course, Portage will automatically install it when needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):263
+msgid "Once you have set the right locale, be sure to update your environment variables to make your system aware of the change:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):268
+msgid "Update the environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):268
+#, no-wrap
+msgid "\n<comment>(For system-wide default locale:)</comment>\n# <i>env-update &amp;&amp; source /etc/profile</i>\n\n<comment>(For user-specific locale:)</comment>\n$ <i>source ~/.bashrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):276
+msgid "After this, you will need to kill your X server by pressing <c>Ctrl-Alt-Backspace</c>, log out, then log in as user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):281
+msgid "Now, verify that the changes have taken effect:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):285
+msgid "Verify env changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):285
+#, no-wrap
+msgid "\n$ <i>locale</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):289
+msgid "There is also additional localisation variable called LINGUAS, which affects to localisation files that get installed in gettext-based programs, and decides used localisation for some specific software packages, such as <c>kde-base/kde-l10n</c> and <c>app-office/openoffice</c>. The variable takes in <e>space</e>-separated list of language codes, and suggested place to set it is <path>/etc/make.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):298
+msgid "Setting LINGUAS in make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):298
+#, no-wrap
+msgid "\n# <i>nano -w /etc/make.conf</i>\n<comment>(Add in the LINGUAS variable. For instance, \nfor German, Finnish and English:)</comment>\nLINGUAS=\"de fi en\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):309
+msgid "Generating Specific Locales"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):312
+msgid "You will probably only use one or maybe two locales on your system. You can specify locales you will need in <path>/etc/locale.gen</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):317
+msgid "Adding locales to /etc/locale.gen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):317
+#, no-wrap
+msgid "\nen_GB ISO-8859-1\nen_GB.UTF-8 UTF-8\nde_DE ISO-8859-1\nde_DE@euro ISO-8859-15\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):324
+msgid "The next step is to run <c>locale-gen</c>. It will generate all the locales you have specified in the <path>/etc/locale.gen</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):329
+msgid "<c>locale-gen</c> is available in <c>glibc-2.3.6-r4</c> and newer. If you have an older version of glibc, you should update it now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):334
+msgid "You can verify that your selected locales are available by running <c>locale -a</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):344
+msgid "Keyboard layout for the console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):348
+msgid "The keyboard layout used by the console is set in <path>/etc/conf.d/keymaps</path> by the <c>KEYMAP</c> variable. Valid values can be found in <path>/usr/share/keymaps/<c>{arch}</c>/</path>. <path>i386</path> has further subdivisions into layout (<path>qwerty/</path>, <path>azerty/</path>, etc.). Some languages have multiple options, so you may wish to experiment to decide which one fits your needs best."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):359
+msgid "Setting the console keymap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):359
+#, no-wrap
+msgid "\nKEYMAP=\"de\"\nKEYMAP=\"de-latin1\"\nKEYMAP=\"de-latin1-nodeadkeys\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):370
+msgid "Keyboard layout for the X server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):374
+msgid "The keyboard layout to be used by the X server is specified in <path>/etc/X11/xorg.conf</path> by the <c>XkbLayout</c> option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):380
+msgid "Setting the X keymap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):380
+#, no-wrap
+msgid "\n Section \"InputDevice\"\n     Identifier  \"Keyboard1\"\n     ...\n     Option \"XkbLayout\"    \"de\"\n     #Option \"XkbModel\"     \"pc105\"    <comment>## this is for international keyboards.</comment>\n     # Option \"XkbVariant\"  \"nodeadkeys\" <comment>## this would be used for xterm input</comment>\n     ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):390
+msgid "If you have an international keyboard layout, you should set the option <c>XkbModel</c> to <c>pc102</c> or <c>pc105</c>, as this will allow mapping of the additional keys specific to your keyboard."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):396
+msgid "Deadkeys allow you to press keys that will not show immediately but will be combined with another letter to produce a single character such as é,è,á,à, etc. Setting <c>XkbVariant</c> to <c>nodeadkeys</c> allows input these special characters into X terminals."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):403
+msgid "If you would like to switch between more than one keyboard layout (for example English and Russian), all you have to do is add a few lines to <path>xorg.conf</path> that specify the desired layouts and the shortcut command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):410
+msgid "Switching between two keyboard layouts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):410
+#, no-wrap
+msgid "\n Section \"InputDevice\"\n     Identifier  \"Keyboard1\"\n     ...\n     Option \"XkbLayout\"    \"us,ru\"\n     Option \"XkbOptions\"   \"grp:alt_shift_toggle,grp_led:scroll\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):418
+msgid "Here, <c>XkbOptions</c> allows you to toggle between keyboard layouts by simply pressing <c>Alt-Shift</c>. This will also toggle the Scroll Lock light on or off, thanks to the <c>grp_led:scroll</c> option. This is a handy visual indicator of which keyboard layout you are using at the moment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):430
+msgid "KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):434
+msgid "For KDE you have to install the <c>kde-base/kde-l10n</c> and <c>app-office/koffice-l10n</c> packages. These respect the <uri link=\"#variables\">LINGUAS variable</uri> described earlier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):445
+msgid "The Euro Symbol for the Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):449
+msgid "In order to get your console to display the Euro symbol, you will need to set <c>CONSOLEFONT</c> in <path>/etc/conf.d/consolefont</path> to a file found in <path>/usr/share/consolefonts/</path> (without the <c>.psfu.gz</c>). <c>lat9w-16</c> has the Euro symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):456
+msgid "Setting the console font"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):456
+#, no-wrap
+msgid "\nCONSOLEFONT=\"lat9w-16\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):460
+msgid "You should verify that <c>CONSOLEFONT</c> is in the boot runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):464
+msgid "Verify the proper runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):464
+#, no-wrap
+msgid "\n# <i>rc-update -v show | grep -i consolefont</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):468
+msgid "If no runlevel is displayed for <c>CONSOLEFONT</c>, then add it to the proper level:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):472
+msgid "Add consolefont to boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):472
+#, no-wrap
+msgid "\n# <i>rc-update add consolefont boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):481
+msgid "The Euro Symbol in X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):483
+msgid "Most Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):486
+msgid "Getting the Euro symbol to work properly in X is a little bit tougher. The first thing you should do is change the <c>fixed</c> and <c>variable</c> definitions in <path>/usr/share/fonts/misc/fonts.alias</path> to end in <c>iso8859-15</c> instead of <c>iso8859-1</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):493
+msgid "Setting default X fonts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):493
+#, no-wrap
+msgid "\nfixed        -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-15\nvariable     -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):498
+msgid "Some applications use their own font, and you will have to tell them separately to use a font with the Euro symbol. You can do this at a user-specific level in <path>.Xdefaults</path> (you can copy this file to <path>/etc/skel/</path> for use by new users), or at a global level for any application with a resource file in <path>/usr/share/X11/app-defaults/</path> (like xterm). In these files you generally have to change an existing line, rather than adding a new one. To change our xterm font, for instance:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):508
+msgid "Setting fonts for xterm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):508
+#, no-wrap
+msgid "\n<comment>(in your home directory)</comment>\n$ <i>echo 'XTerm*font: fixed' &gt;&gt; .Xresources </i>\n$ <i>xrdb -merge .Xresources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):517
+msgid "The Euro symbol in (X)Emacs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):520
+msgid "To use the Euro symbol in (X)Emacs, add the following to <path>.Xdefaults</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):525
+msgid "setting the font for emacs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):525
+#, no-wrap
+msgid "\nEmacs.default.attributeFont: -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-15\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):529
+msgid "For XEmacs (not plain Emacs), you have to do a little more. In <path>/home/user/.xemacs/init.el</path>, add:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):534
+msgid "setting the font for xemacs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):534
+#, no-wrap
+msgid "\n(define-key global-map '(EuroSign) '[€])\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):538
+msgid "The symbol in the []s is the Euro symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):545
+msgid "OpenOffice.Org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):548
+msgid "The current stable <c>app-office/openoffice</c> and <c>app-office/openoffice-bin</c> ebuilds support the <uri link=\"#variables\">LINGUAS variable</uri> for selecting installed GUI language packs. To see the status of GUI translation, hyphenation, spell checking and other localisations on your language, please refer to <uri link=\"http://l10n.openoffice.org/languages.html\">OpenOffice.Org localisation web site</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/guide-to-mutt.xml.pot b/doc/gettext/guide-to-mutt.xml.pot
new file mode 100644
index 0000000..e67aaf5
--- /dev/null
+++ b/doc/gettext/guide-to-mutt.xml.pot
@@ -0,0 +1,414 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(guide:link):6
+msgid "/doc/en/guide-to-mutt.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):8
+msgid "QuickStart Guide to Mutt E-Mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail:link):11
+msgid "mikpolniak@adelphia.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail):11
+msgid "Mike Polniak"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(author:title):13
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail:link):14
+msgid "antifa@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail):14
+msgid "Ken Nowack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(author:title):16
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail:link):17
+msgid "hitch17@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail):17
+msgid "John Hitchings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(abstract):20
+msgid "This guide shows you how to begin using the powerful command line tools for e-mail: fetchmail, procmail, mutt, nbsmtp, msmtp."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(version):29
+msgid "1.7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(date):30
+msgid "2006-09-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):33
+msgid "Introduction to E-Mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):37
+msgid "If you're not a fan of e-mail clients with fancy graphical user interfaces, or if you would just like to experiment with other mail clients before deciding which is best for you, here is the easy way to begin using these powerful command line tools:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):48
+msgid "These programs are not only powerful and highly customizable but also small and efficient. Once you are up and running with this e-mail system you will be amazed at what you can do with it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):54
+msgid "Because this is a quick start guide, we will eliminate the Mail Transfer Agent (MTA) such as sendmail, postfix or exim. This means no complex MTA configuration. It also eliminates using port 25 for mail service."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):60
+msgid "We can do this because fetchmail can force the mail it retrieves directly to a Mail Delivery Agent (MDA) rather than forwarding to port 25. And we don't need to use a complex MTA for plain old outgoing mail delivery."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):66
+msgid "These are the programs you will need to get your e-mail running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):70
+msgid "Getting needed programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):70
+#, no-wrap
+msgid "\n# <i>emerge fetchmail nbsmtp procmail mutt</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):74
+msgid "Then just four quick steps to configure files and you will be up and running a brand new e-mail system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(impo):79
+msgid "After each step you can run a test to make sure the setup is correct. This means you will have a complete working e-mail system when you are done."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):89
+msgid "Fetchmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):93
+msgid "Fetchmail fetches mail from remote servers and forwards it to your local machines delivery system. To use it you need to set up a <path>.fetchmailrc</path> file in your home directory like this example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):99
+msgid "Sample .fetchmailrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):103
+msgid "Once you have created a <path>.fetchmailrc</path> file, you have to change the permissions on the file using the chmod command. The file must be readable only by the file owner. Set the permissions with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):109
+msgid "Changing Permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):109
+#, no-wrap
+msgid "\n$ <i>chmod 600 .fetchmailrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):113
+msgid "To see fetchmail in action, use the verbose mode (-v). To fetch all messages use -a. And you must use the option -m to tell fetchmail to send the mail to procmail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(warn):119
+msgid "While testing, it's a good idea to tell fetchmail to keep (-k) the mail on the remote server in case something goes wrong and you need to fetch it again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):124
+msgid "Run it now to see fetchmail in action!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):128
+msgid "Fetchmail test #1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):128 ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):250
+#, no-wrap
+msgid "\n$ <i>fetchmail -akv -m \"/usr/bin/procmail -d %T\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):132
+msgid "Once you have a working mail system you can set this as a cron job or put it in a monitor like gkrellm. Fetchmail can also run in a daemon mode for which you specify a polling interval in seconds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):143
+msgid "Procmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):147
+msgid "Procmail is the processor that filters the mail that is forwarded to it by fetchmail. It also acts as the MDA to deliver mail to your mailboxes where mutt (your e-mail client) can read it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):153
+msgid "To use procmail you need to create a <path>.procmailrc</path> file in your home directory. For our quickstart purposes we will use a very simple <path>.procmailrc</path> that will filter mail from three gentoo mailing lists into these mailboxes:<e>gentoo-dev, gentoo-user</e> and <e>gentoo-announce</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(note):160
+msgid "The procmail filter rules are called recipes, and I have also included recipes to filter out some spam."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):165
+msgid "Sample .procmailrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):165
+#, no-wrap
+msgid "\nMAILDIR=$HOME/MuttMail                ##you better make sure it exists\nLOGFILE=$HOME/.procmaillog\nLOGABSTRACT=no\n#VERBOSE=on...is only used for debugging\nVERBOSE=off\nFORMAIL=/usr/bin/formail\nNL=\"\n\"\n##recipe lines begin with :0\n##dont put comments on recipe lines\n##disable a recipe with the false condition !\n##condition lines begin with * and regex is your friend\n##conditions are anded and everything after * is fed straight into egrep\n##one action line follows the conditions, in this case it is a mailbox name\n\n#catch duplicates using formail\n:0 Whc: .msgid.lock\n| $FORMAIL -D 16384 .msgid.cache\n\n:0 a\n$MAILDIR/duplicates\n\n#people we always allow mail from\n:0\n* ^From:.*(craig\\@hotmail|renee\\@local.com)\n$MAILDIR/friends\n\n#now flush some spam out\n:0\n* ^Subject:.*(credit|cash|money|debt|sex|sale|loan)\n$MAILDIR/spam\n\n#no more html messages\n:0\n* ^Content-Type:.*html\n$MAILDIR/junk\n\n#now put my mail lists into mailboxes\n:0\n* ^List-Id:.*gentoo-user\ngentoo-user\n\n:0\n* ^List-Id:.*gentoo-dev\ngentoo-dev\n\n:0\n* ^List-Id:.*gentoo-announce\ngentoo-announce\n\n#catch any other gentoo mail\n:0\n* ^From:.*gentoo.org\ngentoo\n\n:0\n* ^From:.*@freshmeat\\.net\nfreshmeat\n\n################################\n# Last rule: mail that gets    #\n# this far goes in default box #\n################################\n:0\n* .*\ndefault\n\n# End of file\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(note):236
+msgid "It is only required to make the MAILDIR <path>$HOME/MuttMail</path> as Procmail will create all the mailbox files as needed in this directory using the names on the action lines. For some useful links visit <uri>http://www.procmail.org/</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):243
+msgid "You can now test <path>.procmailrc</path> by re-running the fetchmail command we tested in the first step. Remember the -k option to keep all mail on the remote server so we have it if we need to rerun it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):250
+msgid "Procmail test #1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):254
+msgid "Now that fetchmail and procmail have run, go to <path>$HOME/MuttMail</path> and read your messages with <c>less</c> or your file manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):264
+msgid "Mutt e-mail client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):268
+msgid "Mutt is used to read and compose e-mail. It is powerful and highly customizable but also small and efficient."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):273
+msgid "Mutt supports reading and writing of four different mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected. In our case we are using the mbox format, where all messages of a mailbox are stored in a single file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):280
+msgid "Mutt also has the ability to work with folders located on a remote IMAP server. See IMAP Support in section 4.11 of the Mutt manual and the Mutt web site <uri>http://www.mutt.org/</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):286
+msgid "When you emerged mutt in the first step it installed a configuration file in <path>/etc/mutt/Muttrc</path>. You also need to create a <path>.muttrc</path> file in your home directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):292
+msgid "Sample .muttrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):292
+#, no-wrap
+msgid "\n<comment>(Be sure to read the fine Mutt manual in /usr/share/doc/mutt*)\n(Any settings here override the system settings in /etc/mutt/Muttrc)</comment>\n\n# <i>cp /etc/mutt/Muttrc ~/.muttrc</i>\n# <i>nano -w .muttrc</i>\nset pager_context=1\nset pager_index_lines=6                 #show a mini-index in pager\nset menu_scroll\nset pgp_verify_sig=no                   #dont show pgp in pager\nset status_on_top                       #put status line at top\nset sort=threads                        #sort by message threads in index\n\nset status_format=\" %r %b %f %n      Del %d      Msgs %m %l %&gt; (%P)\"\nset pager_format=\"%-10.10i %[!%a %b %d %R]\"\nset date_format=\"!%H:%M %a %d %b     \"\nset index_format=\"%4C %Z %[%b%d] %-15.15F %s\"\nset folder_format=\"%2C %t %8s %d %N %f\"\n\n#set sendmail=\"/usr/bin/nbsmtp -d isp.net -h smtp.isp.net -f yourname@isp.net\"\n\n#set from=\"default-mailaddress\"         #set to your from address\n#set realname=\"myname\"\n\nset record=\"$HOME/MuttMail/sent\"        #sent mail is saved here\nset delete=yes                          #delete without prompting\nset include=yes                         #quote msg in reply\nset fast_reply=yes                      #no prompting on reply\nset beep=no                             #no noise\nset markers=no                          #no + on wrapped lines\nset confirmappend=no                    #no prompt for save to =keep\nset to_chars=\" +TCF\"                    #no L for mail_list\n\nset folder = $HOME/MuttMail\nmailboxes =gentoo-user\nmailboxes =gentoo-dev\nmailboxes =gentoo-announce\nmailboxes =gentoo\nmailboxes =freshmeat\nmailboxes =duplicates\nmailboxes =default\nmailboxes =friends\nmailboxes =junk\nmailboxes =spam\nmailboxes =keep\n\nsave-hook .* =keep                      #default mbox to (s)ave mail is =keep\nsubscribe gentoo-user gentoo-dev        #subscribed to these lists\n\nbind pager h display-toggle-weed        #toggle headers with h key\n\n# simulate the old url menu\nmacro index \\cb |urlview\\n 'call urlview to extract URLs out of a message'\nmacro pager \\cb |urlview\\n 'call urlview to extract URLs out of a message'\n\n#run fetchmail by hitting key of G\nmacro index G \"!fetchmail -a -m 'procmail -d %T'\\r\"\nmacro pager G \"!fetchmail -a -m 'procmail -d %T'\\r\"\n\n#use to edit .muttrc and then source it...no restart necessary\nmacro generic ,sm \":source $HOME/.muttrc\\r\"\nmacro generic \\cj \"!rxvt -bg wheat -e joe $HOME/.muttrc\\r\"\n\n# default list of header fields to weed out when displaying mail\n#ignore them all and then unignore what you want to see\nignore *\nunignore  Date To From: Subject X-Mailer Organization User-Agent\nhdr_order Date From To Subject X-Mailer User-Agent Organization\n\n##your Mutt has to have some colors\n##these are for four levels of quoted text\n##they override the system settings in /etc/mutt/Muttrc\n\n#color quoted green  default\ncolor quoted1 magenta blue\n#color quoted2 yellow default\n#color quoted3 red default\n#color signature cyan cyan\n\n\n#this color setup is copied from /etc/mutt/Muttrc.color\n#comment it out if you want the default colors in /etc/mutt/Muttrc\n# Je vois la vie en rose :-)\ncolor   hdrdefault      brightcyan      blue\ncolor   header          brightwhite     blue \"^from:\"\ncolor   header          brightwhite     blue   \"^subject:\"\n\ncolor   quoted          brightgreen     blue\ncolor   signature       brightwhite     blue\n\ncolor   indicator       blue            green\n\ncolor   error           red             black\nmono    error           bold\ncolor   status          black cyan\nmono    status          bold\ncolor   tree            yellow          blue\n\ncolor   tilde           brightmagenta   blue\ncolor   body            brightwhite     blue    \"[-a-z_0-9.]+@[-a-z_0-9.]+\"\nmono    body            bold                    \"[-a-z_0-9.]+@[-a-z_0-9.]+\"\ncolor   body            brightyellow    black   \"^Good signature\"\nmono    body            bold                    \"^Good signature\"\ncolor   body            brightwhite     red     \"^Bad signature from.*\"\nmono    body            bold                    \"^Bad signature from.*\"\ncolor   normal          white           blue\ncolor   message         green           black\ncolor   attachment      brightgreen     blue\n\n# End of file...but it can go on and on and on....:)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):404
+msgid "For the record, this is just a sample <path>.muttrc</path>. There are many more options that you can configure, such as integration with GPG. Have a look at <uri>http://www.dotfiles.com/index.php?app_id=27</uri> for more examples and help."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):411
+msgid "You are now ready to test your <path>.muttrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):415
+msgid "Testing .muttrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):415
+#, no-wrap
+msgid "\n$ <i>mutt -y</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):419
+msgid "This should open Mutt with a menu showing the Mutt mailboxes that you created in Test 2 when you ran the fetchmail command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):424
+msgid "Type the ? for help in navigating the Mutt Mailboxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):433
+msgid "SMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):437
+msgid "The final step is setting up nbsmtp the 'No-Brainer SMTP' used to send mail to your SMTP server. This setup is the easiest of all, as it only requires adding an entry in your <path>.muttrc</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):443
+msgid "domain: The domain you want nbsmtp to say it belongs to. This will almost invariably be the same as the domain in your e-mail address."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):448
+msgid "from@addr: This is the address you want nbsmtp to say the message is from. Note that this can be different than the \"From:\" line in your MUA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):453
+msgid "host: This is the smtp server you are sending to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):457
+msgid "Adding SMTP support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):457
+#, no-wrap
+msgid "\n$ <i>nano -w .muttrc</i>\nset sendmail=\"/usr/bin/nbsmtp -d isp.net -h smtp.isp.net -f urname@isp.net\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):462
+msgid "You are now ready to send a message. So in the Mutt pager or index hit the <c>m</c> key to compose a test message to send to your e-mail address. Mutt will use the value of the EDITOR or VISUAL for the composition editor unless you set <c>editor=</c> in the <path>.muttrc</path>. When you are done composing hit <c>y</c> to send your message. If there are no errors you will see 'sending mail' followed by 'Mail sent.'"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):471
+msgid "Remember in <path>.muttrc</path> we have set where to save sent mail with <c>set record=\"$HOME/MuttMail/sent\"</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):476
+msgid "Now to complete the test, run fetchmail again to get all your mail and verify you have received the message you sent to your e-mail address. When you find your test message, hit the <c>h</c> key to toggle a view of all the headers and see the complete mail transfer path."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(note):483
+msgid "There is one more program you probably want to add called urlview. This extracts the urls in message texts and sends them to your browser."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):488
+msgid "Getting urlview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):488
+#, no-wrap
+msgid "\n# <i>emerge urlview</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):492
+msgid "Then create <path>~/.urlview</path> by copying the configuration file from <path>/usr/share/doc/urlview*/</path> and setting your browser command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):497
+msgid "You now have a powerful and highly customizable mail system. To take advantage of its flexibility, read all the manuals and docs and find the many user configuration files available on the web: search for <path>procmailrc</path> and <path>muttrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):509
+msgid "Authenticated SMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):511
+msgid "Using nbSMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):514
+msgid "If you need to pass a username and password to your SMTP server, you can edit the <c>set sendmail</c> command in your <path>.muttrc</path> to include <c>-U &lt;username&gt; -P &lt;password&gt;</c>, like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):520
+msgid "Setting username and password for SMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):520
+#, no-wrap
+msgid "\nset sendmail=\"/usr/bin/nbsmtp -U <i>username</i> -P <i>password</i> -d isp.net -h smtp.isp.net -f urname@isp.net\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):524
+msgid "If you do not want this information to be present in your <path>.muttrc</path> file, you can also create a <path>.nbsmtprc</path> file in which you include all information:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):530
+msgid "~/.nbsmtprc example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):530
+#, no-wrap
+msgid "\nauth_user = <i>username</i>\nauth_pass = <i>password</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):538
+msgid "Alternative: Using msmtp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):541
+msgid "<c>msmtp</c> is a simple alternative to <c>nbsmtp</c> with similar possibilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):546
+msgid "Installing msmtp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):546
+#, no-wrap
+msgid "\n# <i>emerge msmtp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):550
+msgid "Now login as a normal user and configure msmtp by creating a <path>~/.msmtprc</path> file, filling in your SMTP server's information. Remember to set the permissions to a secure value!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):556
+msgid "Configuring msmtp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):556
+#, no-wrap
+msgid "\n$ <i>nano -w .msmtprc</i>\naccount default\nhost <i>smtp.your_provider.net</i>\nfrom <i>your_username@provider1.net</i>\n<comment>#see man page for more auth options</comment>\nauth login\nuser <i>your_username</i>\npassword <i>your_password</i>\n<comment>#If your SMTP Server supports TLS encryption, uncomment the next line\n#tls</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):569
+msgid "Now set the permissions of the file to a secure value:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):573
+msgid "Setting the permissions for the configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):573
+#, no-wrap
+msgid "\n$ <i>chmod 600 .msmtprc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):577
+msgid "Finally, edit or add the following line to <path>.muttrc</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):581
+msgid "Using msmtp with Mutt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):581
+#, no-wrap
+msgid "\n$ <i>nano -w .muttrc</i>\nset sendmail=\"/usr/bin/msmtp\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):586
+msgid "Fire up <c>mutt</c> and send yourself a test email to see if it worked! See the msmtp man page for more options and another example."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/home-router-howto.xml.pot b/doc/gettext/home-router-howto.xml.pot
new file mode 100644
index 0000000..a6d188d
--- /dev/null
+++ b/doc/gettext/home-router-howto.xml.pot
@@ -0,0 +1,614 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(guide:link):5
+msgid "/doc/en/home-router-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):6
+msgid "Home Router Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(mail:link):9
+msgid "vapier@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(mail):9
+msgid "Mike Frysinger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(abstract):12
+msgid "This document details how to turn an old Gentoo machine into a router for connecting your home network to the internet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(version):20
+msgid "1.40"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(date):21
+msgid "2009-09-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):28
+msgid "Building your own router out of old spare parts has many advantages over buying a pre-made canned router by say Linksys. The biggest one by far is control over the connection. The other advantages are left up to your imagination; just about anything can be done in this scenario, it's just a matter of needing it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):36
+msgid "This guide will show you how to setup Network Address Translation (NAT) on the router (kernel and iptables), add and configure common services (Domain Name System (DNS) via dnsmasq, dhcp via dhcpcd, ADSL via ppp), and conclude with more elaborate and fun things that can be done (port forwarding, traffic shaping, proxies/caching, etc...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):44
+msgid "Before getting started, there's a few basic requirements you must meet. First, you'll need a computer that has at least 2 Network Interface Cards (NICs) in it. Next, you'll need the configuration settings for your internet connection (may include things like IP/DNS/Gateway/username/password). Finally, you'll need a bit of spare time and some Gentoo loving."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):52
+msgid "The conventions used in this guide are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):57
+msgid "eth0 - NIC connected to the Local Area Network (LAN)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):58
+msgid "eth1 - NIC connected to the Wide Area Network (WAN)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):59
+msgid "LAN utilizes the private 192.168.0.xxx network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):60
+msgid "router is hardcoded to the standard 192.168.0.1 IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):61
+msgid "router is running Linux 2.4 or 2.6; you're on your own with 2.0/2.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(impo):64
+msgid "Due to security precautions, I would highly suggest you shut down any unneeded services on the router until we have a chance to get the firewall up and rolling. To view the currently running services, just run <c>rc-status</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):75
+msgid "Kernel setup (know thyself first)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):79
+msgid "Your kernel needs to have the drivers running for both your NICs. To see if your cards are already setup, just run <c>ifconfig</c>. Your output may differ slightly from the following, that's fine. What matters is that the interface shows up at all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):86
+msgid "Checking NICs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):86
+#, no-wrap
+msgid "\n# <i>ifconfig -a</i>\neth0      Link encap:Ethernet  HWaddr 00:60:F5:07:07:B8\n          BROADCAST MULTICAST  MTU:1500  Metric:1\n          RX packets:0 errors:0 dropped:0 overruns:0 frame:0\n          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0\n          collisions:0 txqueuelen:1000\n          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)\n          Interrupt:11 Base address:0x9800\n\neth1      Link encap:Ethernet  HWaddr 00:60:F5:07:07:B9\n          BROADCAST MULTICAST  MTU:1500  Metric:1\n          RX packets:0 errors:0 dropped:0 overruns:0 frame:0\n          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0\n          collisions:0 txqueuelen:1000\n          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)\n          Interrupt:10 Base address:0x9400\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):105
+msgid "If you do not see your two cards showing up and you're not sure what kind of cards you have, try running <c>lspci | grep Ethernet</c>. You can get that from <c>emerge pciutils</c>. Once you have this information, go into your kernel and add support for the correct drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):112
+msgid "The next thing you'll need is support for iptables and NAT (and packet shaping if you want). The following list is split up into always required (*), required only for adsl via PPPoE (a), suggested for everyone (x), and only for shaper (s) features. It does not matter whether you build the features into the kernel or as a module so long as when the feature is needed, the correct module(s) are loaded (module loading is left to the reader as a fun exercise however)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):122
+msgid "Network Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):122
+#, no-wrap
+msgid "\nNetworking options  ---&gt;\n   [*] TCP/IP networking\n      [*] IP: advanced router\n   [*] Network packet filtering (replaces ipchains)\n<comment>If you use 2.4.x, you have to enable the following for DHCP:</comment>\n   [*] Socket Filtering\n\n   IP: Netfilter Configuration  ---&gt;\n      [*] Connection tracking (required for masq/NAT)\n         [x] FTP protocol support\n         [x] IRC protocol support\n      [*] IP tables support (required for filtering/masq/NAT)\n         [*] IP range match support\n         [x] MAC address match support\n         [*] Multiple port match support\n         [*] Packet filtering\n            [*] REJECT target support\n            [x] REDIRECT target support\n         [*] Full NAT\n            [*] MASQUERADE target support\n         [s] Packet mangling\n            [s] MARK target support\n         [x] LOG target support\n\n   QoS and/or fair queueing  ---&gt;\n      [s] QoS and/or fair queueing\n         [s] HTB packet scheduler\n         [s] Ingress Qdisc\n\n   [a] PPP (point-to-point protocol) support\n      [a] PPP filtering\n      [a] PPP support for async serial ports\n      [a] PPP support for sync tty ports\n      [a] PPP Deflate compression\n      [a] PPP BSD-Compress compression\n      [a] PPP over Ethernet\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):161
+msgid "Some things may be slightly different in a 2.4 vs 2.6 kernel, but you should be able to figure it out :). Even among 2.6 kernels, these options have a tendency to move around. Good luck!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):172
+msgid "Hug the WAN (a.k.a. The Internet)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):175 ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):494
+msgid "Intro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):178
+msgid "There are many ways to connect to the internet so I'll just cover the ones I'm familiar with. That leaves us with ADSL (PPPoE) and cable modems (static/dynamic). If there are other methods out there, feel free to write up a little blurb and e-mail me. Feel free to skip any of the following sections in this chapter that don't apply to you. This chapter is just about getting the router connected to the internet via eth1."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):190
+msgid "ADSL and PPPoE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):193
+msgid "All the fancy PPPoE software that used to be provided by rp-pppoe (<uri link=\"http://www.roaringpenguin.com/\">Roaring Penguin</uri>) has been integrated into the <uri link=\"http://samba.org/ppp/\">standard PPP package</uri>. Simply <c>emerge ppp</c> and you'll be on your way. Remember how I said you'll need username/password information? Well I wasn't lying so I hope you have it now! Load up <path>/etc/conf.d/net</path> in your favorite editor and set it up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):203
+msgid "In order for the following net settings to work, you must have baselayout-1.12.9 or later installed on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):208 ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):259
+msgid "Setting up eth1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):208
+#, no-wrap
+msgid "\n<comment>(Replace 'vla9h924' with your username and 'boogie' with your password)</comment>\n\n# <i>nano /etc/conf.d/net</i>\n<comment>Tell baselayout to use adsl over eth1 for ppp0:</comment>\nconfig_ppp0=( \"ppp\" )\nlink_ppp0=\"eth1\"\nplugins_ppp0=( \"pppoe\" )\npppd_ppp0=(\n  \"defaultroute\"\n  \"usepeerdns\"\n  <comment>There may be other settings you want, see /etc/conf.d/net.example</comment>\n)\nusername_ppp0=\"vla9h924\"\npassword_ppp0=\"boogie\"\n\n# <i>ln -s net.lo /etc/init.d/net.ppp0</i>\n# <i>rc-update add net.ppp0 default</i>\n# <i>/etc/init.d/net.ppp0 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(warn):229
+msgid "When the DSL interface comes up, it will create ppp0. Although your NIC is called eth1, the IP is actually bound to ppp0. From now on, when you see examples that utilize 'eth1', substitute with 'ppp0'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(warn):235
+msgid "Make sure you change the permissions of the /etc/conf.d/net file so that only root can read/write it since you're sticking your username/password in it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(warn):240
+msgid "For people transitioning from the <c>rp-pppoe</c> package, or for people who hit weird connection resets, see the MTU section in the Troubleshooting chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):250
+msgid "Cable and/or dynamic/static IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):253
+msgid "If you have a static IP then you will need a few more details than if you have a dynamic IP. For static users, you will need your IP, gateway, and DNS servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):259
+#, no-wrap
+msgid "\n<comment>Dynamic IP Users:</comment>\n# <i>emerge dhcpcd</i>\n# <i>nano /etc/conf.d/net</i>\n<comment>You'll need an entry like so:</comment>\nconfig_eth1=( \"dhcp\" )\n\n<comment>Static IP Users:</comment>\n# <i>nano /etc/conf.d/net</i>\n<comment>You'll need entries like so:</comment>\nconfig_eth1=( \"66.92.78.102 broadcast 66.92.78.255 netmask 255.255.255.0\" )\nroutes_eth1=( \"default gw 66.92.78.1\" )\n# <i>nano /etc/resolv.conf</i>\n<comment>Add one line per DNS server:</comment>\nnameserver 123.123.123.123\n\n<comment>Dynamic and Static Setup:</comment>\n# <i>ln -s net.lo /etc/init.d/net.eth1</i>\n# <i>rc-update add net.eth1 default</i>\n# <i>/etc/init.d/net.eth1 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):281
+msgid "You should be all set to go now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):290
+msgid "Hug the LAN (bring along some friends)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):294
+msgid "This step is a breeze compared to the previous one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):298
+msgid "Setting up eth0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):298
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/net</i>\n<comment>Add a line like the following:</comment>\nconfig_eth0=( \"192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0\" )\n# <i>rc-update add net.eth0 default</i>\n# <i>/etc/init.d/net.eth0 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):311
+msgid "LAN Services (because we're nice people)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):314
+msgid "DHCP Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):317
+msgid "I bet it'd be nice if everyone else in your house could just plug their computers into the network and things would just work. No need to remember mind-numbing details or make them stare at confusing configuration screens! Life would be grand eh? Introducing the Dynamic Host Configuration Protocol (DHCP) and why you should care."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):325
+msgid "DHCP is exactly what its name implies. It's a protocol that allows you to dynamically configure other hosts automatically. You run a DHCP server on the router, give it all the information about your network (valid IPs, DNS servers, gateways, etc...), and then when the other hosts start up, they run a DHCP client to automatically configure themselves. No fuss, no muss! For more information about DHCP, you can always visit <uri link=\"http://en.wikipedia.org/wiki/DHCP\">Wikipedia</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):335
+msgid "We'll use a package called dnsmasq which provides both DHCP and DNS services. For now lets just focus on the DHCP aspect. Note that if you want to run a different DHCP server, you can find another example in the Fun Things chapter. Also, if you wish to tinker with the DHCP server settings, just read the comments in <path>/etc/dnsmasq.conf</path>. All the defaults should work fine though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):344
+msgid "Setting up a DHCP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):344
+#, no-wrap
+msgid "\n# <i>emerge dnsmasq</i>\n# <i>nano /etc/dnsmasq.conf</i>\n<comment>Add this line to enable dhcp:</comment>\ndhcp-range=192.168.0.100,192.168.0.250,72h\n<comment>Restrict dnsmasq to just the LAN interface</comment>\ninterface=eth0\n\n# <i>rc-update add dnsmasq default</i>\n# <i>/etc/init.d/dnsmasq start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):356
+msgid "Now your little router is a bona-fide DHCP server! Plugin those computers and watch them work! With Windows systems you should go into the TCP/IP Properties and select the 'Obtain an IP address automatically' and 'Obtain DNS server address automatically' options. Sometimes the changes aren't instantaneous, so you may have to open a command prompt and run <c>ipconfig /release</c> and <c>ipconfig /renew</c>. But enough about Windows, let's get back to our favorite penguin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):370
+msgid "DNS Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):373
+msgid "When people want to visit a place on the internet, they remember names, not a string of funky numbers. After all, what's easier to remember, ebay.com or 66.135.192.87? This is where the DNS steps in. DNS servers run all over the internet, and whenever someone wants to visit 'ebay.com', these servers turn 'ebay.com' (what we understand) into '66.135.192.87' (what our computers understand). For more information about DNS, you can always visit <uri link=\"http://en.wikipedia.org/wiki/DNS\">Wikipedia</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):383
+msgid "Since we're using dnsmasq for our DHCP server, and it includes a DNS server, you've got nothing left to do here! Your little router is already providing DNS to its DHCP clients. Bet you wish everything was this easy ;)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):389
+msgid "You're welcome to choose other DNS servers if you're more comfortable with them, but the reason dnsmasq is great is because it was designed to do exactly what we want and nothing more. It's a little DNS caching/forwarding server for local networks. We're not looking to provide DNS for our own domain here, just offer simple DNS services to everyone else on our LAN."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):401
+msgid "NAT (a.k.a. IP-masquerading)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):404
+msgid "At this point, people on your network can talk to each other and they can look up hostnames via DNS, but they still can't actually connect to the internet. While you may think that's great (more bandwidth for you!), I bet they're not too happy just yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):411
+msgid "This is where Network Address Translation (NAT) steps in. NAT is a way of connecting multiple computers in a private LAN to the internet when you have a smaller number of public IP addresses available to you. Typically you are given 1 IP by your ISP, but you want to let your whole house connect to the internet. NAT is the magic that makes this possible. For more information about NAT, you can always visit <uri link=\"http://en.wikipedia.org/wiki/NAT\">Wikipedia</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):420
+msgid "Before we get started, make sure you have iptables on your system. Although it is automatically installed on most systems, you may not have it. If you don't, just run <c>emerge iptables</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):426
+msgid "Setting up iptables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):426
+#, no-wrap
+msgid "\n<comment>First we flush our current rules</comment>\n# <i>iptables -F</i>\n# <i>iptables -t nat -F</i>\n\n<comment>Setup default policies to handle unmatched traffic</comment>\n# <i>iptables -P INPUT ACCEPT</i>\n# <i>iptables -P OUTPUT ACCEPT</i>\n# <i>iptables -P FORWARD DROP</i>\n\n<comment>Copy and paste these examples ...</comment>\n# <i>export LAN=eth0</i>\n# <i>export WAN=eth1</i>\n\n<comment>Then we lock our services so they only work from the LAN</comment>\n# <i>iptables -I INPUT 1 -i ${LAN} -j ACCEPT</i>\n# <i>iptables -I INPUT 1 -i lo -j ACCEPT</i>\n# <i>iptables -A INPUT -p UDP --dport bootps ! -i ${LAN} -j REJECT</i>\n# <i>iptables -A INPUT -p UDP --dport domain ! -i ${LAN} -j REJECT</i>\n\n<comment>(Optional) Allow access to our ssh server from the WAN</comment>\n# <i>iptables -A INPUT -p TCP --dport ssh -i ${WAN} -j ACCEPT</i>\n\n<comment>Drop TCP / UDP packets to privileged ports</comment>\n# <i>iptables -A INPUT -p TCP ! -i ${LAN} -d 0/0 --dport 0:1023 -j DROP</i>\n# <i>iptables -A INPUT -p UDP ! -i ${LAN} -d 0/0 --dport 0:1023 -j DROP</i>\n\n<comment>Finally we add the rules for NAT</comment>\n# <i>iptables -I FORWARD -i ${LAN} -d 192.168.0.0/255.255.0.0 -j DROP</i>\n# <i>iptables -A FORWARD -i ${LAN} -s 192.168.0.0/255.255.0.0 -j ACCEPT</i>\n# <i>iptables -A FORWARD -i ${WAN} -d 192.168.0.0/255.255.0.0 -j ACCEPT</i>\n# <i>iptables -t nat -A POSTROUTING -o ${WAN} -j MASQUERADE</i>\n<comment>Tell the kernel that ip forwarding is OK</comment>\n# <i>echo 1 &gt; /proc/sys/net/ipv4/ip_forward</i>\n# <i>for f in /proc/sys/net/ipv4/conf/*/rp_filter ; do echo 1 &gt; $f ; done</i>\n\n<comment>This is so when we boot we don't have to run the rules by hand</comment>\n# <i>/etc/init.d/iptables save</i>\n# <i>rc-update add iptables default</i>\n# <i>nano /etc/sysctl.conf</i>\n<comment>Add/Uncomment the following lines:</comment>\nnet.ipv4.ip_forward = 1\nnet.ipv4.conf.default.rp_filter = 1\n\n<comment>If you have a dynamic internet address you probably want to enable this:</comment>\nnet.ipv4.ip_dynaddr = 1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):474
+msgid "Once you've typed out all of that, the rest of your network should now be able to use the internet as if they were directly connected themselves."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):479
+msgid "The ip_dynaddr option is useful for dial on demand systems or when your ISP gives out dynamic addresses. This works around the problem where a connection is attempted before the internet interface is fully setup. Really this just provides for a smoother network experience for users behind your router."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):491
+msgid "Fun Things (for a rainy day)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):497
+msgid "Believe it or not, you're done :). From here on out, I'll cover a bunch of common topics that may interest you. Everything in this chapter is completely optional."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):507
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):510
+msgid "Sometimes you would like to be able to host services on a computer behind the router, or just to make your life easier when connecting remotely. Perhaps you want to run a FTP, HTTP, SSH, or VNC server on one or more machines behind your router and be able to connect to them all. The only caveat is that you can only have one service/machine combo per port. For example, there is no practical way to setup three FTP servers behind your router and then try to connect to them all through port 21; only one can be on port 21 while the others would have to be on say port 123 and port 567."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):521
+msgid "All the port forwarding rules are of the form <c>iptables -t nat -A PREROUTING [-p protocol] --dport [external port on router] -i ${WAN} -j DNAT --to [ip/port to forward to]</c>. Unfortunately, iptables does not accept hostnames when port forwarding. If you are forwarding an external port to the same port on the internal machine, you can omit the destination port. See the iptables(8) man page for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):530
+msgid "Running the iptables commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):530
+#, no-wrap
+msgid "\n<comment>Copy and paste these examples ...</comment>\n# <i>export LAN=eth0</i>\n# <i>export WAN=eth1</i>\n\n<comment>Forward port 2 to ssh on an internal host</comment>\n# <i>iptables -t nat -A PREROUTING -p tcp --dport 2 -i ${WAN} -j DNAT --to 192.168.0.2:22</i>\n\n<comment>FTP forwarding to an internal host</comment>\n# <i>iptables -t nat -A PREROUTING -p tcp --dport 21 -i ${WAN} -j DNAT --to 192.168.0.56</i>\n\n<comment>HTTP forwarding to an internal host</comment>\n# <i>iptables -t nat -A PREROUTING -p tcp --dport 80 -i ${WAN} -j DNAT --to 192.168.0.56</i>\n\n<comment>VNC forwarding for internal hosts</comment>\n# <i>iptables -t nat -I PREROUTING -p tcp --dport 5900 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n# <i>iptables -t nat -I PREROUTING -p tcp --dport 5901 -i ${WAN} -j DNAT --to 192.168.0.3:5900</i>\n<comment>If you want to VNC in to 192.168.0.3, then just add ':1' to the router's hostname</comment>\n\n<comment>SAMBA forwarding to an internal host (excess ports to cover Windows)</comment>\n# <i>iptables -t nat -I PREROUTING -p tcp --dport 135 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n# <i>iptables -t nat -I PREROUTING -p tcp --dport 139 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n# <i>iptables -t nat -I PREROUTING -p tcp --dport 445 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n# <i>iptables -t nat -I PREROUTING -p udp --dport 137:138 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n# <i>iptables -t nat -I PREROUTING -p udp --dport 445 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n\n<comment>Bittorrent forwarding</comment>\n# <i>iptables -t nat -A PREROUTING -p tcp --dport 6881:6889 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n\n<comment>eDonkey/eMule forwarding</comment>\n# <i>iptables -t nat -A PREROUTING -p tcp --dport 4662 -i ${WAN} -j DNAT --to 192.168.0.55</i>\n\n<comment>Game Cube Warp Pipe support</comment>\n# <i>iptables -t nat -A PREROUTING -p udp --dport 4000 -i ${WAN} -j DNAT --to 192.168.0.56</i>\n\n<comment>Playstation 2 Online support</comment>\n# <i>iptables -t nat -A PREROUTING -p tcp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>\n# <i>iptables -t nat -A PREROUTING -p udp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>\n\n<comment>Xbox Live</comment>\n# <i>iptables -t nat -A PREROUTING -p tcp --dport 3074 -i ${WAN} -j DNAT --to 192.168.0.69</i>\n# <i>iptables -t nat -A PREROUTING -p udp --dport 3074 -i ${WAN} -j DNAT --to 192.168.0.69</i>\n# <i>iptables -t nat -A PREROUTING -p udp --dport 88 -i ${WAN} -j DNAT --to 192.168.0.69</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):575
+msgid "If you have other common / cool examples, please <mail link=\"vapier@gentoo.org\">e-mail me</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):584
+msgid "Identd (for IRC)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):587
+msgid "Internet Relay Chat utilizes the ident service pretty heavily. Now that the IRC clients are behind the router, we need a way to host ident for both the router and the clients. One such server has been created called <c>midentd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):594
+msgid "Setting up ident"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):594
+#, no-wrap
+msgid "\n# <i>emerge midentd</i>\n# <i>rc-update add midentd default</i>\n# <i>/etc/init.d/midentd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):600
+msgid "There are a few other ident servers in portage. Depending on your needs, I would recommend checking out <c>oidentd</c> and <c>fakeidentd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):682
+msgid "Time Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):685
+msgid "Keeping your system time correct is essential in maintaining a healthy system. One of the most common ways of accomplishing this is with the Network Time Protocol (NTP) and the ntp package (which provides implementations for both server and client)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):692
+msgid "Many people run ntp clients on their computers. Obviously, the more clients in the world, the larger the load the ntp servers need to shoulder. In environments like home networks though, we can help keep the load down on public servers while still providing the proper time to all our computers. As an added bonus, our private updates will be a lot faster for the clients too! All we have to do is run a ntp server on our router that synchronizes itself with the public internet servers while providing the time to the rest of the computers in the network. To get started, simply <c>emerge ntp</c> on the router."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):704
+msgid "Setting up the NTP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):704
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/ntp-client</i>\n<comment>Customize if you wish but the defaults should be fine</comment>\n# <i>rc-update add ntp-client default</i>\n\n# <i>nano /etc/ntp.conf</i>\n<comment>Add the follwing lines:</comment>\nrestrict default ignore\nrestrict 192.168.0.0 mask 255.255.255.0 notrust nomodify notrap\n<comment>These will allow only ntp clients with an IP\naddress in the 192.168.0.xxx range to use your ntp server</comment>\n# <i>nano /etc/conf.d/ntpd</i>\n<comment>Customize if you wish but the defaults should be fine</comment>\n# <i>rc-update add ntpd default</i>\n\n# <i>/etc/init.d/ntp-client start</i>\n# <i>/etc/init.d/ntpd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):723
+msgid "You should make sure that you allow inbound and outbound communication on the ntp port (123/udp) when setting up the server. The client just needs outbound access on port 123 over udp."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):729
+msgid "Now, on your clients, have them <c>emerge ntp</c> also. However, we will just run the ntp client so setup is a lot simpler."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):734
+msgid "Setting up a NTP client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):734
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/ntp-client</i>\n<comment>Change the 'pool.ntp.org' server in the NTPCLIENT_OPTS variable to '192.168.0.1'</comment>\n# <i>rc-update add ntp-client default</i>\n# <i>/etc/init.d/ntp-client start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):745
+msgid "Rsync Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):748
+msgid "For those who run multiple Gentoo boxes on the same lan, you often want to keep from having every machine running <c>emerge sync</c> with remote servers. By setting up a local rsync, you save on both your bandwidth and the Gentoo rsync servers' bandwidth. It's pretty simple to do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):755
+msgid "For a much more in-depth rsync guide, please see the official <uri link=\"/doc/en/rsync.xml#local\">rsync guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):760
+msgid "Since every Gentoo machine requires rsync, theres no need to emerge it. Edit the default <path>/etc/rsyncd.conf</path> config file, uncomment the <c>[gentoo-portage]</c> section, and make sure you add an <c>address</c> option. All the other defaults should be fine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):767
+msgid "Rsync server config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):767
+#, no-wrap
+msgid "\npid file = /var/run/rsyncd.pid\nuse chroot = yes\nread only = yes\naddress = 192.168.0.1\n\n[gentoo-portage]\n  path = /mnt/space/portage\n  comment = Gentoo Linux Portage tree\n  exclude = /distfiles /packages\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):779
+msgid "Then you need to start the service (again, the defaults are OK)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):783
+msgid "Starting the rsync server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):783
+#, no-wrap
+msgid "\n# <i>/etc/init.d/rsyncd start</i>\n# <i>rc-update add rsyncd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):788
+msgid "Only thing left is to set tell your clients to sync against the router."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):792
+msgid "Client SYNC settings in make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):792
+#, no-wrap
+msgid "\nSYNC=\"rsync://192.168.0.1/gentoo-portage\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):800
+msgid "Mail Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):803
+msgid "Sometimes it's nice to run your own Simple Mail Transfer Protocol (SMTP) server on the router. You may have your own reason for wanting to do so, but I run it so that the users see mail as being sent instantly and the work of retrying/routing is left up to the mail server. Some ISPs also don't allow for mail relaying for accounts that aren't part of their network (like Verizon). Also, you can easily throttle the delivery of mail so that large attachments won't seriously lag your connection for half an hour."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):813
+msgid "Setting up SMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):813
+#, no-wrap
+msgid "\n# <i>emerge netqmail</i>\n<comment>make sure the output of `hostname` is correct</comment>\n# <i>emerge --config netqmail</i>\n# <i>iptables -I INPUT -p tcp --dport smtp ! -i ${LAN} -j REJECT</i>\n# <i>ln -s /var/qmail/supervise/qmail-send /service/qmail-send</i>\n# <i>ln -s /var/qmail/supervise/qmail-smtpd /service/qmail-smtpd</i>\n# <i>cd /etc/tcprules.d</i>\n# <i>nano tcp.qmail-smtp</i>\n\n<comment>Add an entry like so to the allow section:</comment>\n192.168.0.:allow,RELAYCLIENT=\"\"\n\n# <i>make</i>\n# <i>rc-update add svscan default</i>\n# <i>/etc/init.d/svscan start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):837
+msgid "I'm a huge fan of qmail, but you're free to use a different mta :). When you setup e-mail on the hosts in your network, tell them that their SMTP server is 192.168.0.1 and everything should be peachy. You might want to visit the <uri link=\"http://netqmail.org/\">netqmail homepage</uri> for more documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):867
+msgid "Full DHCP Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):870
+msgid "Earlier we used dnsmasq to provide DHCP service to all our clients. For most people with a simple small LAN, this is perfect. But you may need something with more features. Thus we turn to a full-featured DHCP server as provided by the <uri link=\"http://www.isc.org/products/DHCP\">ISC</uri> folks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):877
+msgid "Setting up dhcpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):877
+#, no-wrap
+msgid "\n# <i>emerge dhcp</i>\n# <i>nano /etc/dhcp/dhcpd.conf</i>\n<comment>(Here is a sample configuration file:)</comment>\nauthoritative;\nddns-update-style interim;\nsubnet 192.168.0.0 netmask 255.255.255.0 {\n    range 192.168.0.100 192.168.0.250;\n    default-lease-time 259200;\n    max-lease-time 518400;\n    option subnet-mask 255.255.255.0;\n    option broadcast-address 192.168.0.255;\n    option routers 192.168.0.1;\n    option domain-name-servers 192.168.0.1;\n}\n# <i>nano /etc/conf.d/dhcpd</i>\n<comment>(Set IFACE=\"eth0\")</comment>\n# <i>rc-update add dhcpd default</i>\n# <i>/etc/init.d/dhcpd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):898
+msgid "This is the minimal setup required to replace the dnsmasq DHCP functionality that we used earlier. Speaking of which, you did remember to disable the DHCP features in dnsmasq didn't you? If not, you should do so now (just comment out the <c>dhcp-range</c> setting in <path>/etc/dnsmasq.conf</path> and restart the service)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):910
+msgid "Connect Another LAN (or two or three or ...)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):913
+msgid "Sometimes you have need of connecting the router to another LAN. Maybe you want to hook up a group of friends temporarily, or you're a neat freak and want to section off different groups of computers, or you're just really really bored. Whatever the reasons, extending the router to other LAN networks should be pretty straightforward. In the following examples, I will assume that this new network is connected via a third ethernet card, namely <c>eth2</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):923
+msgid "First you need to configure the interface. Just take the instructions in the <uri link=\"#doc_chap4_pre1\">4.1 code listing</uri> and replace <c>eth0</c> with <c>eth2</c> and <c>192.168.0</c> with <c>192.168.1</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):929
+msgid "Then you need to tweak dnsmasq to service the new interface. Just edit the <path>/etc/conf.d/dnsmasq</path> file again and append <c>-i eth2</c> to DNSMASQ_OPTS; using -i multiple times is OK. Then edit <path>/etc/dnsmasq.conf</path> and add another line like the dhcp-range line in the <uri link=\"#doc_chap5_pre1\">5.1 code listing</uri>, replacing <c>192.168.0</c> with <c>192.168.1</c>. Having multiple dhcp-range lines is OK too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):939
+msgid "Finally, see the rules in the <uri link=\"#doc_chap5_pre2\">5.2 code listing</uri> and duplicate the rules that have <c>-i ${LAN}</c> in them. You may want to create another variable, say <c>LAN2</c>, to make things easier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):951
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):954
+msgid "Useful Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):957
+msgid "If you're having trouble getting your computers to communicate, you may way to try out the following tools (they can all be found in the <c>net-analyzer</c> portage category):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(th):965
+msgid "Utility"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(th):966
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):969
+msgid "wireshark"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):970
+msgid "GUI tool to view all raw network data according to filters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):973
+msgid "tcpdump"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):974
+msgid "Console tool to dump all raw network data according to filters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):977
+msgid "iptraf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):978
+msgid "ncurses based IP LAN monitor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):981
+msgid "ettercap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):982
+msgid "ncurses based network monitor/control"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):990
+msgid "DHCP Fails To Start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):993
+msgid "When starting the dhcp init.d script for the first time, it may fail to load but neglect to give you any useful info."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):998
+msgid "DHCP Failing Example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):998
+#, no-wrap
+msgid "\n# <i>/etc/init.d/dhcp start</i>\n * Setting ownership on dhcp.leases ...          [ ok ]\n * Starting dhcpd ...                            [ !! ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1004
+msgid "The trick is to know where dhcpd is sending its output. Simply browse to <path>/var/log</path> and read the log files. Since the exact log file depends on the package you are using as a syslog, try running <c>grep -Rl dhcpd /var/log</c> to narrow down the possibilities. Chances are you made a typo in your config file. You could also try running <c>dhcpd -d -f</c> (short for debug / foreground) and debug the error based upon the output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):1017
+msgid "Incorrect MTU Value"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1020
+msgid "If you experience odd errors (such as not being able to access some webpages while others load fine), you may be having Path MTU Discovery trouble. The quick way to test is to run this iptables command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):1026
+msgid "Circumvent MTU issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):1026
+#, no-wrap
+msgid "\n# <i>iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1030
+msgid "This will affect all new connections, so just refresh the website you're having problems with in order to test. In case it helps, the standard MTU value for 100mbit ethernet connections is <c>1500</c>; this value also applies to PPPoA. For PPPoE connections it is <c>1492</c>. For more info, you should read Chapter 15 of the <uri link=\"http://lartc.org/howto/\">Linux Advanced Routing &amp; Traffic Control HOWTO</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1039
+msgid "If that command does not work for you, you may want to try putting the rule into the mangle table. Simply add <c>-t mangle</c> to the command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):1048
+msgid "Unable to connect two machines directly"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1051
+msgid "If (for whatever reason) you want to connect two machines directly together without a hub or switch, a regular ethernet cable will likely not work, unless you have an Auto MDI/MDI-X (also known as \"autosensing\") capable network adapter. You will need a different cable called a crossover cable. This <uri link=\"http://en.wikipedia.org/wiki/Ethernet_crossover_cable\">Wikipedia</uri> page explains the low level details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):1066
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1070
+msgid "I have no final notes other than if you experience any troubles with the guide, please contact <mail link=\"vapier@gentoo.org\">me</mail> or file a bug with <uri link=\"http://bugs.gentoo.org/\">Gentoo's Bugtracking Website</uri>. If you have some interesting bits you think would enhance this guide, by all means send it my way for inclusion."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/hpc-howto.xml.pot b/doc/gettext/hpc-howto.xml.pot
new file mode 100644
index 0000000..b8bdd0d
--- /dev/null
+++ b/doc/gettext/hpc-howto.xml.pot
@@ -0,0 +1,886 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):6
+msgid "High Performance Computing on Gentoo Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):9
+msgid "marc@adelielinux.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):9
+msgid "Marc St-Pierre"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):12
+msgid "benoit@adelielinux.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):12
+msgid "Benoit Morin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):17
+msgid "Assistant/Research"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):15
+msgid "jean-francois@adelielinux.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):15
+msgid "Jean-Francois Richard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):18
+msgid "olivier@adelielinux.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):18
+msgid "Olivier Crete"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):20
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):21
+msgid "dberkholz@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):21
+msgid "Donnie Berkholz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#. No licensing information; this document has been written by a third-party
+#.      organisation without additional licensing information.
+#. 
+#.      In other words, this is copyright adelielinux R&D; Gentoo only has
+#.      permission to distribute this document as-is and update it when appropriate
+#.      as long as the adelie linux R&D notice stays
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(abstract):35
+msgid "This document was written by people at the Adelie Linux R&amp;D Center &lt;http://www.adelielinux.com&gt; as a step-by-step guide to turn a Gentoo System into a High Performance Computing (HPC) system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(version):41
+msgid "1.7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(date):42
+msgid "2010-06-07"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):45
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):49
+msgid "Gentoo Linux, a special flavor of Linux that can be automatically optimized and customized for just about any application or need. Extreme performance, configurability and a top-notch user and developer community are all hallmarks of the Gentoo experience."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):56
+msgid "Thanks to a technology called Portage, Gentoo Linux can become an ideal secure server, development workstation, professional desktop, gaming system, embedded solution or... a High Performance Computing system. Because of its near-unlimited adaptability, we call Gentoo Linux a metadistribution."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):63
+msgid "This document explains how to turn a Gentoo system into a High Performance Computing system. Step by step, it explains what packages one may want to install and helps configure them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):69
+msgid "Obtain Gentoo Linux from the website <uri>http://www.gentoo.org</uri>, and refer to the <uri link=\"/doc/en/\">documentation</uri> at the same location to install it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):80
+msgid "Configuring Gentoo Linux for Clustering"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):82
+msgid "Recommended Optimizations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):85
+msgid "We refer to the <uri link=\"/doc/en/handbook/\">Gentoo Linux Handbooks</uri> in this section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):90
+msgid "During the installation process, you will have to set your USE variables in <path>/etc/make.conf</path>. We recommended that you deactivate all the defaults (see <path>/etc/make.profile/make.defaults</path>) by negating them in make.conf. However, you may want to keep such use variables as 3dnow, gpm, mmx, nptl, nptlonly, sse, ncurses, pam and tcpd. Refer to the USE documentation for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):99
+msgid "USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):99
+#, no-wrap
+msgid "\nUSE=\"-oss 3dnow -apm -avi -berkdb -crypt -cups -encode -gdbm -gif gpm -gtk\n-imlib -java -jpeg -kde -gnome -libg++ -libwww -mikmod mmx -motif -mpeg ncurses\n-nls nptl nptlonly -ogg -opengl pam -pdflib -png -python -qt4 -qtmt\n-quicktime -readline -sdl -slang -spell -ssl -svga tcpd -truetype -vorbis -X\n-xml2 -xv -zlib\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):107
+msgid "Or simply:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):111
+msgid "USE Flags - simplified version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):111
+#, no-wrap
+msgid "\nUSE=\"-* 3dnow gpm mmx ncurses pam sse tcpd\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):115
+msgid "The <e>tcpd</e> USE flag increases security for packages such as xinetd."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):119
+msgid "In step 15 (\"Installing the kernel and a System Logger\") for stability reasons, we recommend the vanilla-sources, the official kernel sources released on <uri>http://www.kernel.org/</uri>, unless you require special support such as xfs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):126
+msgid "Installing vanilla-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):126
+#, no-wrap
+msgid "\n# <i>emerge -a syslog-ng vanilla-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):130
+msgid "When you install miscellaneous packages, we recommend installing the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):135
+msgid "Installing necessary packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):135
+#, no-wrap
+msgid "\n# <i>emerge -a nfs-utils portmap tcpdump ssmtp iptables xinetd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):142
+msgid "Communication Layer (TCP/IP Network)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):145
+msgid "A cluster requires a communication layer to interconnect the slave nodes to the master node. Typically, a FastEthernet or GigaEthernet LAN can be used since they have a good price/performance ratio. Other possibilities include use of products like <uri link=\"http://www.myricom.com/\">Myrinet</uri>, <uri link=\"http://quadrics.com/\">QsNet</uri> or others."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):153
+msgid "A cluster is composed of two node types: master and slave. Typically, your cluster will have one master node and several slave nodes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):158
+msgid "The master node is the cluster's server. It is responsible for telling the slave nodes what to do. This server will typically run such daemons as dhcpd, nfs, pbs-server, and pbs-sched. Your master node will allow interactive sessions for users, and accept job executions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):165
+msgid "The slave nodes listen for instructions (via ssh/rsh perhaps) from the master node. They should be dedicated to crunching results and therefore should not run any unnecessary services."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):171
+msgid "The rest of this documentation will assume a cluster configuration as per the hosts file below. You should maintain on every node such a hosts file (<path>/etc/hosts</path>) with entries for each node participating node in the cluster."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):178
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):178
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /etc/hosts\n\n127.0.0.1       localhost\n\n192.168.1.100   master.adelie master\n\n192.168.1.1     node01.adelie node01\n192.168.1.2     node02.adelie node02\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):190
+msgid "To setup your cluster dedicated LAN, edit your <path>/etc/conf.d/net</path> file on the master node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):195
+msgid "/etc/conf.d/net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):195
+#, no-wrap
+msgid "\n# Global config file for net.* rc-scripts\n\n# This is basically the ifconfig argument without the ifconfig $iface\n#\n\niface_eth0=\"192.168.1.100 broadcast 192.168.1.255 netmask 255.255.255.0\"\n# Network Connection to the outside world using dhcp -- configure as required for you network\niface_eth1=\"dhcp\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):207
+msgid "Finally, setup a DHCP daemon on the master node to avoid having to maintain a network configuration on each slave node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):212
+msgid "/etc/dhcp/dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):212
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /etc/dhcp/dhcpd.conf\n\nlog-facility local7;\nddns-update-style none;\nuse-host-decl-names on;\n\nsubnet 192.168.1.0 netmask 255.255.255.0 {\n        option domain-name \"adelie\";\n        range 192.168.1.10 192.168.1.99;\n        option routers 192.168.1.100;\n\n        host node01.adelie {\n                # MAC address of network card on node 01\n                hardware ethernet 00:07:e9:0f:e2:d4;\n                fixed-address 192.168.1.1;\n        }\n        host node02.adelie {\n                # MAC address of network card on node 02\n                hardware ethernet 00:07:e9:0f:e2:6b;\n                fixed-address 192.168.1.2;\n        }\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):241
+msgid "NFS/NIS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):244
+msgid "The Network File System (NFS) was developed to allow machines to mount a disk partition on a remote machine as if it were on a local hard drive. This allows for fast, seamless sharing of files across a network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):250
+msgid "There are other systems that provide similar functionality to NFS which could be used in a cluster environment. The <uri link=\"http://www.openafs.org\">Andrew File System from IBM</uri>, recently open-sourced, provides a file sharing mechanism with some additional security and performance features. The <uri link=\"http://www.coda.cs.cmu.edu/\">Coda File System</uri> is still in development, but is designed to work well with disconnected clients. Many of the features of the Andrew and Coda file systems are slated for inclusion in the next version of <uri link=\"http://www.nfsv4.org\">NFS (Version 4)</uri>. The advantage of NFS today is that it is mature, standard, well understood, and supported robustly across a variety of platforms."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):264
+msgid "Ebuilds for NFS-support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):264
+#, no-wrap
+msgid "\n# <i>emerge -a nfs-utils portmap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):268
+msgid "Configure and install a kernel to support NFS v3 on all nodes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):272
+msgid "Required Kernel Configurations for NFS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):272
+#, no-wrap
+msgid "\nCONFIG_NFS_FS=y\nCONFIG_NFSD=y\nCONFIG_SUNRPC=y\nCONFIG_LOCKD=y\nCONFIG_NFSD_V3=y\nCONFIG_LOCKD_V4=y\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):281
+msgid "On the master node, edit your <path>/etc/hosts.allow</path> file to allow connections from slave nodes. If your cluster LAN is on 192.168.1.0/24, your <path>hosts.allow</path> will look like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):287 ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):446 ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):457
+msgid "hosts.allow"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):287
+#, no-wrap
+msgid "\nportmap:192.168.1.0/255.255.255.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):291
+msgid "Edit the <path>/etc/exports</path> file of the master node to export a work directory structure (/home is good for this)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):296 ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):826
+msgid "/etc/exports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):296
+#, no-wrap
+msgid "\n/home/  *(rw)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):300
+msgid "Add nfs to your master node's default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):304
+msgid "Adding NFS to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):304
+#, no-wrap
+msgid "\n# <i>rc-update add nfs default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):308
+msgid "To mount the nfs exported filesystem from the master, you also have to configure your salve nodes' <path>/etc/fstab</path>. Add a line like this one:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):314
+msgid "/etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):314
+#, no-wrap
+msgid "\nmaster:/home/  /home  nfs  rw,exec,noauto,nouser,async  0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):318
+msgid "You'll also need to set up your nodes so that they mount the nfs filesystem by issuing this command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):323
+msgid "Adding nfsmount to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):323
+#, no-wrap
+msgid "\n# <i>rc-update add nfsmount default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):330
+msgid "RSH/SSH"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):333
+msgid "SSH is a protocol for secure remote login and other secure network services over an insecure network. OpenSSH uses public key cryptography to provide secure authorization. Generating the public key, which is shared with remote systems, and the private key which is kept on the local system, is done first to configure OpenSSH on the cluster."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):341
+msgid "For transparent cluster usage, private/public keys may be used. This process has two steps:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):347
+msgid "Generate public and private keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):348
+msgid "Copy public key to slave nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):351
+msgid "For user based authentication, generate and copy as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):355
+msgid "SSH key authentication"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):355
+#, no-wrap
+msgid "\n# <i>ssh-keygen -t dsa</i>\nGenerating public/private dsa key pair.\nEnter file in which to save the key (/root/.ssh/id_dsa): /root/.ssh/id_dsa\nEnter passphrase (empty for no passphrase):\nEnter same passphrase again:\nYour identification has been saved in /root/.ssh/id_dsa.\nYour public key has been saved in /root/.ssh/id_dsa.pub.\nThe key fingerprint is:\nf1:45:15:40:fd:3c:2d:f7:9f:ea:55:df:76:2f:a4:1f root@master\n\n<comment>WARNING! If you already have an \"authorized_keys\" file,\nplease append to it, do not use the following command.</comment>\n\n# <i>scp /root/.ssh/id_dsa.pub node01:/root/.ssh/authorized_keys</i>\nroot@master's password:\nid_dsa.pub   100%  234     2.0MB/s   00:00\n\n# <i>scp /root/.ssh/id_dsa.pub node02:/root/.ssh/authorized_keys</i>\nroot@master's password:\nid_dsa.pub   100%  234     2.0MB/s   00:00\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):378
+msgid "Host keys must have an empty passphrase. RSA is required for host-based authentication."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):383
+msgid "For host based authentication, you will also need to edit your <path>/etc/ssh/shosts.equiv</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):388
+msgid "/etc/ssh/shosts.equiv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):388
+#, no-wrap
+msgid "\nnode01.adelie\nnode02.adelie\nmaster.adelie\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):394
+msgid "And a few modifications to the <path>/etc/ssh/sshd_config</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):398
+msgid "sshd configurations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):398
+#, no-wrap
+msgid "\n# $OpenBSD: sshd_config,v 1.42 2001/09/20 20:57:51 mouring Exp $\n# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin\n\n# This is the sshd server system-wide configuration file. See sshd(8)\n# for more information.\n\n# HostKeys for protocol version 2\nHostKey /etc/ssh/ssh_host_rsa_key\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):409
+msgid "If your application require RSH communications, you will need to emerge <c>net-misc/netkit-rsh</c> and <c>sys-apps/xinetd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):414
+msgid "Installing necessary applicaitons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):414
+#, no-wrap
+msgid "\n# <i>emerge -a xinetd</i>\n# <i>emerge -a netkit-rsh</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):419
+msgid "Then configure the rsh deamon. Edit your <path>/etc/xinet.d/rsh</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):423
+msgid "rsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):423
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /etc/xinetd.d/rsh\n\nservice shell\n{\n        socket_type     = stream\n        protocol        = tcp\n        wait            = no\n        user            = root\n        group           = tty\n        server          = /usr/sbin/in.rshd\n        log_type        = FILE /var/log/rsh\n        log_on_success  = PID HOST USERID EXIT DURATION\n        log_on_failure  = USERID ATTEMPT\n        disable         = no\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):442
+msgid "Edit your <path>/etc/hosts.allow</path> to permit rsh connections:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):446
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /etc/hosts.allow\n\nin.rshd:192.168.1.0/255.255.255.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):453
+msgid "Or you can simply trust your cluster LAN:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):457
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /etc/hosts.allow\n\nALL:192.168.1.0/255.255.255.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):464
+msgid "Finally, configure host authentication from <path>/etc/hosts.equiv</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):468
+msgid "hosts.equiv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):468
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /etc/hosts.equiv\n\nmaster\nnode01\nnode02\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):477
+msgid "And, add xinetd to your default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):481
+msgid "Adding xinetd to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):481
+#, no-wrap
+msgid "\n# <i>rc-update add xinetd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):488
+msgid "NTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):491
+msgid "The Network Time Protocol (NTP) is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio or satellite receiver or modem. It provides accuracies typically within a millisecond on LANs and up to a few tens of milliseconds on WANs relative to Coordinated Universal Time (UTC) via a Global Positioning Service (GPS) receiver, for example. Typical NTP configurations utilize multiple redundant servers and diverse network paths in order to achieve high accuracy and reliability."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):502
+msgid "Select a NTP server geographically close to you from <uri link=\"http://www.eecis.udel.edu/~mills/ntp/servers.html\">Public NTP Time Servers</uri>, and configure your <path>/etc/conf.d/ntp</path> and <path>/etc/ntp.conf</path> files on the master node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):509
+msgid "Master /etc/conf.d/ntp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):509
+#, no-wrap
+msgid "\n# /etc/conf.d/ntpd\n\n# NOTES:\n#  - NTPDATE variables below are used if you wish to set your\n#    clock when you start the ntp init.d script\n#  - make sure that the NTPDATE_CMD will close by itself ...\n#    the init.d script will not attempt to kill/stop it\n#  - ntpd will be used to maintain synchronization with a time\n#    server regardless of what NTPDATE is set to\n#  - read each of the comments above each of the variable\n\n# Comment this out if you dont want the init script to warn\n# about not having ntpdate setup\nNTPDATE_WARN=\"n\"\n\n# Command to run to set the clock initially\n# Most people should just uncomment this line ...\n# however, if you know what you're doing, and you\n# want to use ntpd to set the clock, change this to 'ntpd'\nNTPDATE_CMD=\"ntpdate\"\n\n# Options to pass to the above command\n# Most people should just uncomment this variable and\n# change 'someserver' to a valid hostname which you\n# can acquire from the URL's below\nNTPDATE_OPTS=\"-b ntp1.cmc.ec.gc.ca\"\n\n##\n# A list of available servers is available here:\n# http://www.eecis.udel.edu/~mills/ntp/servers.html\n# Please follow the rules of engagement and use a\n# Stratum 2 server (unless you qualify for Stratum 1)\n##\n\n# Options to pass to the ntpd process that will *always* be run\n# Most people should not uncomment this line ...\n# however, if you know what you're doing, feel free to tweak\n#NTPD_OPTS=\"\"\n\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):551
+msgid "Edit your <path>/etc/ntp.conf</path> file on the master to setup an external synchronization source:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):556
+msgid "Master ntp.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):556
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /etc/ntp.conf\n\n# Synchronization source #1\nserver ntp1.cmc.ec.gc.ca\nrestrict ntp1.cmc.ec.gc.ca\n# Synchronization source #2\nserver ntp2.cmc.ec.gc.ca\nrestrict ntp2.cmc.ec.gc.ca\nstratum 10\ndriftfile /etc/ntp.drift.server\nlogfile /var/log/ntp\nbroadcast 192.168.1.255\nrestrict default kod\nrestrict 127.0.0.1\nrestrict 192.168.1.0 mask 255.255.255.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):575
+msgid "And on all your slave nodes, setup your synchronization source as your master node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):580
+msgid "Node /etc/conf.d/ntp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):580
+#, no-wrap
+msgid "\n# /etc/conf.d/ntpd\n\nNTPDATE_WARN=\"n\"\nNTPDATE_CMD=\"ntpdate\"\nNTPDATE_OPTS=\"-b master\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):588
+msgid "Node ntp.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):588
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /etc/ntp.conf\n\n# Synchronization source #1\nserver master\nrestrict master\nstratum 11\ndriftfile /etc/ntp.drift.server\nlogfile /var/log/ntp\nrestrict default kod\nrestrict 127.0.0.1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):602
+msgid "Then add ntpd to the default runlevel of all your nodes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):606
+msgid "Adding ntpd to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):606
+#, no-wrap
+msgid "\n# <i>rc-update add ntpd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):610
+msgid "NTP will not update the local clock if the time difference between your synchronization source and the local clock is too great."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):618
+msgid "IPTABLES"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):621
+msgid "To setup a firewall on your cluster, you will need iptables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):625
+msgid "Installing iptables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):625
+#, no-wrap
+msgid "\n# <i>emerge -a iptables</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):629
+msgid "Required kernel configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):633
+msgid "IPtables kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):633
+#, no-wrap
+msgid "\nCONFIG_NETFILTER=y\nCONFIG_IP_NF_CONNTRACK=y\nCONFIG_IP_NF_IPTABLES=y\nCONFIG_IP_NF_MATCH_STATE=y\nCONFIG_IP_NF_FILTER=y\nCONFIG_IP_NF_TARGET_REJECT=y\nCONFIG_IP_NF_NAT=y\nCONFIG_IP_NF_NAT_NEEDED=y\nCONFIG_IP_NF_TARGET_MASQUERADE=y\nCONFIG_IP_NF_TARGET_LOG=y\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):646
+msgid "And the rules required for this firewall:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):650
+msgid "rule-save"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):650
+#, no-wrap
+msgid "\n# Adelie Linux Research &amp; Development Center\n# /var/lib/iptables/rule-save\n\n*filter\n:INPUT ACCEPT [0:0]\n:FORWARD ACCEPT [0:0]\n:OUTPUT ACCEPT [0:0]\n-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT\n-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT\n-A INPUT -s 192.168.1.0/255.255.255.0 -i eth1 -j ACCEPT\n-A INPUT -s 127.0.0.1 -i lo -j ACCEPT\n-A INPUT -p icmp -j ACCEPT\n-A INPUT -j LOG\n-A INPUT -j REJECT --reject-with icmp-port-unreachable\nCOMMIT\n*nat\n:PREROUTING ACCEPT [0:0]\n:POSTROUTING ACCEPT [0:0]\n:OUTPUT ACCEPT [0:0]\n-A POSTROUTING -s 192.168.1.0/255.255.255.0 -j MASQUERADE\nCOMMIT\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):674
+msgid "Then add iptables to the default runlevel of all your nodes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):678
+msgid "Adding iptables to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):678
+#, no-wrap
+msgid "\n# <i>rc-update add iptables default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):687
+msgid "HPC Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):689
+msgid "OpenPBS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):692
+msgid "The Portable Batch System (PBS) is a flexible batch queueing and workload management system originally developed for NASA. It operates on networked, multi-platform UNIX environments, including heterogeneous clusters of workstations, supercomputers, and massively parallel systems. Development of PBS is provided by Altair Grid Technologies."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):700
+msgid "Installing openpbs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):700
+#, no-wrap
+msgid "\n# <i>emerge -a openpbs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):704
+msgid "OpenPBS ebuild does not currently set proper permissions on var-directories used by OpenPBS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):709
+msgid "Before starting using OpenPBS, some configurations are required. The files you will need to personalize for your system are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):715
+msgid "/etc/pbs_environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):716
+msgid "/var/spool/PBS/server_name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):717
+msgid "/var/spool/PBS/server_priv/nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):718
+msgid "/var/spool/PBS/mom_priv/config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):719 ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):726
+msgid "/var/spool/PBS/sched_priv/sched_config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):722
+msgid "Here is a sample sched_config:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):726
+#, no-wrap
+msgid "\n#\n# Create queues and set their attributes.\n#\n#\n# Create and define queue upto4nodes\n#\ncreate queue upto4nodes\nset queue upto4nodes queue_type = Execution\nset queue upto4nodes Priority = 100\nset queue upto4nodes resources_max.nodect = 4\nset queue upto4nodes resources_min.nodect = 1\nset queue upto4nodes enabled = True\nset queue upto4nodes started = True\n#\n# Create and define queue default\n#\ncreate queue default\nset queue default queue_type = Route\nset queue default route_destinations = upto4nodes\nset queue default enabled = True\nset queue default started = True\n#\n# Set server attributes.\n#\nset server scheduling = True\nset server acl_host_enable = True\nset server default_queue = default\nset server log_events = 511\nset server mail_from = adm\nset server query_other_jobs = True\nset server resources_default.neednodes = 1\nset server resources_default.nodect = 1\nset server resources_default.nodes = 1\nset server scheduler_iteration = 60\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):763
+msgid "To submit a task to OpenPBS, the command <c>qsub</c> is used with some optional parameters. In the example below, \"-l\" allows you to specify the resources required, \"-j\" provides for redirection of standard out and standard error, and the \"-m\" will e-mail the user at beginning (b), end (e) and on abort (a) of the job."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):771
+msgid "Submitting a task"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):771
+#, no-wrap
+msgid "\n<comment>(submit and request from OpenPBS that myscript be executed on 2 nodes)</comment>\n# <i>qsub -l nodes=2 -j oe -m abe myscript</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):776
+msgid "Normally jobs submitted to OpenPBS are in the form of scripts. Sometimes, you may want to try a task manually. To request an interactive shell from OpenPBS, use the \"-I\" parameter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):782
+msgid "Requesting an interactive shell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):782
+#, no-wrap
+msgid "\n# <i>qsub -I</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):786
+msgid "To check the status of your jobs, use the qstat command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):790
+msgid "Checking the status of the jobs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):790
+#, no-wrap
+msgid "\n# <i>qstat</i>\nJob id  Name  User   Time Use S Queue\n------  ----  ----   -------- - -----\n2.geist STDIN adelie 0        R upto1nodes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):800
+msgid "MPICH"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):803
+msgid "Message passing is a paradigm used widely on certain classes of parallel machines, especially those with distributed memory. MPICH is a freely available, portable implementation of MPI, the Standard for message-passing libraries."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):810
+msgid "The mpich ebuild provided by Adelie Linux allows for two USE flags: <e>doc</e> and <e>crypt</e>. <e>doc</e> will cause documentation to be installed, while <e>crypt</e> will configure MPICH to use <c>ssh</c> instead of <c>rsh</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):817
+msgid "Installing the mpich application"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):817
+#, no-wrap
+msgid "\n# <i>emerge -a mpich</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):821
+msgid "You may need to export a mpich work directory to all your slave nodes in <path>/etc/exports</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):826
+#, no-wrap
+msgid "\n/home  *(rw)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):830
+msgid "Most massively parallel processors (MPPs) provide a way to start a program on a requested number of processors; <c>mpirun</c> makes use of the appropriate command whenever possible. In contrast, workstation clusters require that each process in a parallel job be started individually, though programs to help start these processes exist. Because workstation clusters are not already organized as an MPP, additional information is required to make use of them. Mpich should be installed with a list of participating workstations in the file <path>machines.LINUX</path> in the directory <path>/usr/share/mpich/</path>. This file is used by <c>mpirun</c> to choose processors to run on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):843
+msgid "Edit this file to reflect your cluster-lan configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):847
+msgid "/usr/share/mpich/machines.LINUX"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):847
+#, no-wrap
+msgid "\n# Change this file to contain the machines that you want to use\n# to run MPI jobs on. The format is one host name per line, with either\n#    hostname\n# or\n#    hostname:n\n# where n is the number of processors in an SMP. The hostname should\n# be the same as the result from the command \"hostname\"\nmaster\nnode01\nnode02\n# node03\n# node04\n# ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):863
+msgid "Use the script <c>tstmachines</c> in <path>/usr/sbin/</path> to ensure that you can use all of the machines that you have listed. This script performs an <c>rsh</c> and a short directory listing; this tests that you both have access to the node and that a program in the current directory is visible on the remote node. If there are any problems, they will be listed. These problems must be fixed before proceeding."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):872
+msgid "The only argument to <c>tstmachines</c> is the name of the architecture; this is the same name as the extension on the machines file. For example, the following tests that a program in the current directory can be executed by all of the machines in the LINUX machines list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):879
+msgid "Running a test"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):879
+#, no-wrap
+msgid "\n# <i>/usr/local/mpich/sbin/tstmachines LINUX</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):883
+msgid "This program is silent if all is well; if you want to see what it is doing, use the -v (for verbose) argument:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):888
+msgid "Running a test verbosively"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):888
+#, no-wrap
+msgid "\n# <i>/usr/local/mpich/sbin/tstmachines -v LINUX</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):892
+msgid "The output from this command might look like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):896
+msgid "Output of the above command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):896
+#, no-wrap
+msgid "\nTrying true on host1.uoffoo.edu ...\nTrying true on host2.uoffoo.edu ...\nTrying ls on host1.uoffoo.edu ...\nTrying ls on host2.uoffoo.edu ...\nTrying user program on host1.uoffoo.edu ...\nTrying user program on host2.uoffoo.edu ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):905
+msgid "If <c>tstmachines</c> finds a problem, it will suggest possible reasons and solutions. In brief, there are three tests:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):911
+msgid "<e>Can processes be started on remote machines?</e> tstmachines attempts to run the shell command true on each machine in the machines files by using the remote shell command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):916
+msgid "<e>Is current working directory available to all machines?</e> This attempts to ls a file that tstmachines creates by running ls using the remote shell command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):921
+msgid "<e>Can user programs be run on remote systems?</e> This checks that shared libraries and other components have been properly installed on all machines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):928
+msgid "And the required test for every development tool:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):932
+msgid "Testing a development tool"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):932
+#, no-wrap
+msgid "\n# <i>cd ~</i>\n# <i>cp /usr/share/mpich/examples1/hello++.c ~</i>\n# <i>make hello++</i>\n# <i>mpirun -machinefile /usr/share/mpich/machines.LINUX -np 1 hello++</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):939
+msgid "For further information on MPICH, consult the documentation at <uri link=\"http://www-unix.mcs.anl.gov/mpi/mpich/docs/mpichman-chp4/mpichman-chp4.htm\">http://www-unix.mcs.anl.gov/mpi/mpich/docs/mpichman-chp4/mpichman-chp4.htm</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):947
+msgid "LAM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):950 ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):960
+msgid "(Coming Soon!)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):957
+msgid "OMNI"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):969
+msgid "Bibliography"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):973
+msgid "The original document is published at the <uri link=\"http://www.adelielinux.com\">Adelie Linux R&amp;D Centre</uri> web site, and is reproduced here with the permission of the authors and <uri link=\"http://www.cyberlogic.ca\">Cyberlogic</uri>'s Adelie Linux R&amp;D Centre."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):982
+msgid "<uri>http://www.gentoo.org</uri>, Gentoo Foundation, Inc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):983
+msgid "<uri link=\"http://www.adelielinux.com\">http://www.adelielinux.com</uri>, Adelie Linux Research and Development Centre"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):987
+msgid "<uri link=\"http://nfs.sourceforge.net/\">http://nfs.sourceforge.net</uri>, Linux NFS Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):991
+msgid "<uri link=\"http://www-unix.mcs.anl.gov/mpi/mpich/\">http://www-unix.mcs.anl.gov/mpi/mpich/</uri>, Mathematics and Computer Science Division, Argonne National Laboratory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(uri:link):996
+msgid "http://www.ntp.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(uri):996
+msgid "http://ntp.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):998
+msgid "<uri link=\"http://www.eecis.udel.edu/~mills/\">http://www.eecis.udel.edu/~mills/</uri>, David L. Mills, University of Delaware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):1002
+msgid "<uri link=\"http://www.ietf.org/html.charters/secsh-charter.html\">http://www.ietf.org/html.charters/secsh-charter.html</uri>, Secure Shell Working Group, IETF, Internet Society"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):1006
+msgid "<uri link=\"http://www.linuxsecurity.com/\">http://www.linuxsecurity.com/</uri>, Guardian Digital"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):1010
+msgid "<uri link=\"http://www.openpbs.org/\">http://www.openpbs.org/</uri>, Altair Grid Technologies, LLC."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/index.xml.pot b/doc/gettext/index.xml.pot
new file mode 100644
index 0000000..8011df2
--- /dev/null
+++ b/doc/gettext/index.xml.pot
@@ -0,0 +1,80 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(version):10
+msgid "11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(title):12
+msgid "Gentoo Documentation Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(title):19
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(p):22
+msgid "Welcome to the Gentoo Documentation Resources. This page will give you a quick overview on the documentation we provide. Most documentation is released under the <uri link=\"http://creativecommons.org/licenses/by-sa/2.5\">Creative Commons - Attribution / Share Alike</uri> license, an open documentation license. All documentation should also be available in a printer-friendly format. To view this document, append <path>?style=printable</path> to the URL. You'll also find a \"Print\" link on the top-right corner of each document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(p):32
+msgid "If you find bugs in our documentation or have proposals, please use our <uri link=\"http://bugs.gentoo.org\">Bugtracking System</uri> and fill in a bug report for \"Documentation\" or \"Doc Other\". These bug reports will then be handled by the <uri link=\"/proj/en/gdp/\">Gentoo Documentation Project</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(title):42
+msgid "Documentation Repository"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(p):45
+msgid "Our documentation is <uri link=\"index.xml#doc_chap2\">categorized</uri> and hierarchically navigable. If you want a quick overview of all available documentation without the additional information, please use our <uri link=\"list.xml\">Documentation Listing</uri> page. We also have a <uri link=\"list.xml?desc=1\">full listing</uri> of all our documents with their descriptions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):59
+msgid "faq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):60
+msgid "install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):61
+msgid "desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):62
+msgid "upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):63
+msgid "gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):64
+msgid "sysadmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):65
+msgid "gentoodev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):66
+msgid "project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):67
+msgid "other"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/info-guide.xml.pot b/doc/gettext/info-guide.xml.pot
new file mode 100644
index 0000000..75b4dd2
--- /dev/null
+++ b/doc/gettext/info-guide.xml.pot
@@ -0,0 +1,316 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(guide:link):5
+msgid "/doc/en/info-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):6
+msgid "Gentoo Info Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//info-guide.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(abstract):12
+msgid "This guide is meant to show how to navigate info pages using the info command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(version):20
+msgid "1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(date):21
+msgid "2006-03-28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):26
+msgid "What is info?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):29
+msgid "Most of you may be familiar with the <c>man</c> documentation system. While man is good with quickly looking up items, it lacks structure in linking man pages together. This is where <c>info</c> comes in. Info pages are made using the <c>texinfo</c> tools, and can link with other pages, create menus and ease navigation in general. The next section will look at how info pages are laid out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):41
+msgid "Info pages layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):44
+msgid "The main info pages are held in <path>/usr/share/info</path>. Unlike the man style directory layout, <path>/usr/share/info</path> contains what is largely a rather extensive collection of files. These files have the following format:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):50
+msgid "info file format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):50
+#, no-wrap
+msgid "\npagename.info[-node].gz\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):54
+msgid "<c>pagename</c> is the actual name of the page (example: <c>wget</c>). <c>[-node]</c> is an optional construct that designates another node level (generally these are referenced to by the toplevel of the info document in question). In order to save space these info pages are compressed using the <c>gzip</c> compression scheme. Additional info pages can be listed with the <c>INFOPATH</c> environment variable (usually set through the various <path>/etc/env.d/</path> files). To get started, it's important to note the <path>/usr/share/info/dir</path> file. This special file is used when info is ran with no parameters. It contains a listing of all info pages available for users to browse. To begin looking at navigating around in info, we'll go ahead and bring it up with no arguments:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):68
+msgid "Starting up info"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):68
+#, no-wrap
+msgid "\n$ <i>info</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):72
+msgid "Now in the next chapter we'll look at dealing with basic info navigation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):80
+msgid "Working with info pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):82
+msgid "Browsing with menus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):85
+msgid "Now that info is started, we're given a screen similar to this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):89
+msgid "Sample info screen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):89
+#, no-wrap
+msgid "\nFile: dir,      Node: Top       This is the top of the INFO tree\n\n  This (the Directory node) gives a menu of major topics.\n  Typing \"q\" exits, \"?\" lists all Info commands, \"d\" returns here,\n  \"h\" gives a primer for first-timers,\n  \"mEmacs&lt;Return&gt;\" visits the Emacs manual, etc.\n\n  In Emacs, you can click mouse button 2 on a menu item or cross reference\n  to select it.\n\n* Menu:\n\nUser Interface Toolkit\n* GDK: (gdk).           The General Drawing Kit\n* GTK: (gtk).           The GIMP Toolkit\n\nGNU programming tools\n* Autoconf v2.1: (autoconf).         Create source code configuration scripts.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):110
+msgid "Right now there are a bunch of entries with an asterisk before them. These are menu items for navigating through different node levels. There are two ways of selecting menus. We'll look at the first now and the other way later. First off, we'll go ahead and look at the <c>wget</c> info page. To do so, use the down arrow key until you reach the area indicated by the blue highlighting:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):118
+msgid "Navigating to the wget info menu entry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):118
+#, no-wrap
+msgid "\nNetwork Applications\n* GnuTLS: (gnutls).                     Package for Transport Layer Security.\n* <i>Wget: (wget).</i>         The non-interactive network downloader.\n* certtool: (gnutls)Invoking certtool.  Manipulate certificates and keys.\n* gnutls-cli: (gnutls)Invoking gnutls-cli.      GNU TLS test client.\n* gnutls-cli-debug: (gnutls)Invoking gnutls-cli-debug.  GNU TLS debug client.\n* gnutls-serv: (gnutls)Invoking gnutls-serv.    GNU TLS test server.\n* srptool: (gnutls)Invoking srptool.    Simple SRP password tool.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):129
+msgid "Once you get to this area, hit the <c>ENTER</c> key to select the menu item. This will bring up the info page for <c>wget</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):134
+msgid "The wget info page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):134
+#, no-wrap
+msgid "\nFile: wget.info,  Node: Top,  Next: Overview,  Up: (dir)\n\nWget 1.10.2\n***********\n\nThis manual documents version 1.10.2 of GNU Wget, the freely available\nutility for network downloads.\n\n   Copyright (C) 1996-2005 Free Software Foundation, Inc.\n\n* Menu:\n\n* Overview::            Features of Wget.\n* Invoking::            Wget command-line arguments.\n* Recursive Download::  Downloading interlinked pages.\n* Following Links::     The available methods of chasing links.\n* Time-Stamping::       Mirroring according to time-stamps.\n* Startup File::        Wget's initialization file.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):155
+msgid "Now that we have an info page up, the next section will look at basic navigation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):163
+msgid "Basic navigation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):166
+msgid "In terms of nodes, this is considered the <c>Top</c> node for the wget page. Consider the <c>Top</c> node to be the same as the table of contents for that particular info page. Now to navigate the actual page itself, you have a couple of different methods. First off is the standard info method. This is using the <c>SPACE</c> key to move forward a page and the <c>BACKSPACE/DELETE</c> keys to move back a page. This is the recommended method as it automatically advances/retreats to the appropriate node in the document. This allows for a somewhat linear browsing for those used to man pages. Another way is through the <c>PAGE UP/PAGE DOWN</c> keys. These work, but they will not advance/retreat like <c>SPACE/BACKSPACE/DELETE</c> will. If you want to skip entire nodes without using <c>SPACE/BACKSPACE/DELETE</c>, you can also use the <c>[</c> (advance backwards) and <c>]</c> (advance forwards) keys."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):181
+msgid "As mentioned earlier, there are 2 ways of navigating menus. The other way will now be described here. The numbers <c>1-9</c> can be used to reference to the first-ninth menu entries in a document. This can be used to quickly peruse through documents. For example, we'll use <c>3</c> to reach the <c>Recursive Download</c> menu entry. So press <c>3</c> and it will bring up the <c>Recursive Download</c> screen:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):190
+msgid "Resulting Recursive Download screen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):190
+#, no-wrap
+msgid "\nFile: wget.info,  Node: Recursive Download,  Next: Following Links,  Prev: Invoking,  Up: Top\n\n3 Recursive Download\n********************\n\nGNU Wget is capable of traversing parts of the Web (or a single HTTP or\nFTP server), following links and directory structure.  We refer to this\nas to \"recursive retrieval\", or \"recursion\".\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):201
+msgid "Now we're at the <c>Recursive Download</c> screen. Here is a good time to note a few things. First off the top header section. This header shows the navigation capable from this particular screen. The page indicated by <c>Next: </c> can be accessed by pressing the <c>n</c> key, and the page indicated by <c>Prev: </c> can be accessed by pressing the <c>p</c> key. Please note that this will only work for the same level. If overused you could round up in totally unrelated content. It's better to use <c>SPACE/BACKSPACE/DELETE/[/]</c> to navigate in a linear fashion."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):212
+msgid "If for some reason you get lost, there are a few ways to get out. First is the <c>t</c> key. This will take you straight to the toplevel (table of contents) for the particular info page you're browsing. If you want to return to the last page you looked out, you can do so with the <c>l</c> key. If you want to go to the above level, you can do so with the <c>u</c> key. Now that you have some idea of navigating a page, the next chapter will look at searching for content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):226
+msgid "Searching through info"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):228
+msgid "Navigating to other info pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):231
+msgid "Now that you can navigate an individual info page, it's important to look at accessing other info pages. The first obvious way is to go to the info page through the <c>dir</c> index listing of info pages. To get to the <c>dir</c> index from deep within a document, simply press the <c>d</c> key. From there you can search for the appropriate page you want. However, if you know the actual page, there is an easier way through the <c>Goto node (g key)</c> command. To go to an info page by name, type <c>g</c> to bring up the prompt and enter the name of the page in parentheses:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):242
+msgid "Going to an info page by name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):242
+#, no-wrap
+msgid "\n* Startup File::        Wget's initialization file.\n* Examples::            Examples of usage.\n* Various::             The stuff that doesn't fit anywhere else.\n* Appendices::          Some useful references.\n* Copying::             You may give out copies of Wget and of this manual.\n--zz-Info: (wget.info.gz)Top, 24 lines --Top-------------------------------\nGoto node: <i>(libc)</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):252
+msgid "This will bring up the libc page as shown here:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):256
+msgid "Result of the Goto node command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):256
+#, no-wrap
+msgid "\nFile: libc.info,  Node: Top,  Next: Introduction,  Prev: (dir),  Up: (dir)\n\nMain Menu\n*********\n\nThis is Edition 0.10, last updated 2001-07-06, of `The GNU C Library\nReference Manual', for Version 2.3.x of the GNU C Library.\n\n* Menu:\n\n* Introduction::                 Purpose of the GNU C Library.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):270
+msgid "Now that we know how to go to info pages by name, the next section will look at searching for pieces of information using the info page's index."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):278
+msgid "Searching using an index"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):281
+msgid "In this example we'll see how to lookup the <c>printf</c> function of the c library using the <c>libc</c> info page's index. You should still be at the libc info page from the last section, and if not, use the Goto node command to do so. To utilize the index search, hit the <c>i</c> key to bring up the prompt, then enter your search term. We'll do so for <c>printf</c> below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):289
+msgid "Entering an index search query"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):289
+#, no-wrap
+msgid "\n* Character Set Handling::       Support for extended character sets.\n* Locales::                      The country and language can affect the\n                                   behavior of library functions.\n* Message Translation::          How to make the program speak the user's\n                                   language.\n--zz-Info: (libc.info.gz)Top, 1291 lines --Top-- Subfile: libc.info-1.gz-----\nIndex entry: <i>printf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):299
+msgid "After pressing enter upon completion of our query, we're brought to the <c>libc</c> definition for <c>printf</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):304
+msgid "Result of the index search query"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):304
+#, no-wrap
+msgid "\nFile: libc.info,  Node: Formatted Output Functions,  Next: Dynamic Output,  Prev: Other Output Conversions,  Up: Formatted Output\n\n12.12.7 Formatted Output Functions\n----------------------------------\n\nThis section describes how to call <i>`printf'</i> and related functions.\nPrototypes for these functions are in the header file `stdio.h'.\nBecause these functions take a variable number of arguments, you _must_\ndeclare prototypes for them before using them.  Of course, the easiest\nway to make sure you have all the right prototypes is to just include\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):317
+msgid "We've now successfully performed a search using the <c>libc</c> info page index. However, sometimes what we want is in the page itself. The next section will look at performing searches within the page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):326
+msgid "Searching using the search command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):329
+msgid "Starting from the previous location at the <c>Formatted Output Functions</c> node, we'll look at searching for the <c>sprintf</c> variation of the <c>printf</c> function. To perform a search, press the <c>s</c> key to bring up the search prompt, and then enter the query (sprintf in this case):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):336
+msgid "Entering a search query"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):336
+#, no-wrap
+msgid "\n -- Function: int wprintf (const wchar_t *TEMPLATE, ...)\n     The `wprintf' function prints the optional arguments under the\n     control of the wide template string TEMPLATE to the stream\n     `stdout'.  It returns the number of wide characters printed, or a\n--zz-Info: (libc.info.gz)Formatted Output Functions, 127 lines --Top-- Subfile: libc.info-3.gz--\nSearch for string []: <i>sprintf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):345
+msgid "Hit <c>ENTER</c> and it will show the result of the query:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):349
+msgid "Result of the search query"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):349
+#, no-wrap
+msgid "\n-- Function: int <i>sprintf</i> (char *S, const char *TEMPLATE, ...)\n     This is like `printf', except that the output is stored in the\n     character array S instead of written to a stream.  A null\n     character is written to mark the end of the string.\n\n     The `sprintf' function returns the number of characters stored in\n     the array S, not including the terminating null character.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):359
+msgid "And we have the function we need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):368 ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):370
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):373
+msgid "This concludes the overview of using info to view info pages. As always comments are both welcome and appreciated. Clicking on the my name (Chris White) on the right side will send me an email."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):382
+msgid "Additional Program Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):385
+msgid "In order to make things easier for those that wish to browse info pages through a more friendly graphical interface, the following are available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(li):391
+msgid "app-text/info2html - Convert info pages to a browse-able HTML format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(li):392
+msgid "app-text/pinfo - <c>ncurses</c> based info viewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(li):393
+msgid "app-text/tkinfo - a <c>tcl/tk</c> based info browser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(li):394
+msgid "app-vim/info - a <c>vim</c> based info browser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):397
+msgid "The <c>KDE</c> browser <c>Konqueror</c> also allows you to browse info pages through the <c>info: </c> URI."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/inserts.xml.pot b/doc/gettext/inserts.xml.pot
new file mode 100644
index 0000000..b5ca34a
--- /dev/null
+++ b/doc/gettext/inserts.xml.pot
@@ -0,0 +1,220 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(inserts:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(version):6
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):7
+msgid "Content"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):8
+msgid "Credits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):9
+msgid "Updated <docdate/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):10
+msgid "The <uri link=\"$originalversion\">original version</uri> of this document was last updated <docdate/>"
+msgstr ""
+
+#. Doc not in /doc/LL/metadoc.xml
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):12
+msgid "This translation is not maintained anymore"
+msgstr ""
+
+#. Doc in /doc/LL/metadoc.xml but not in /doc/en/metadoc.xml
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):14
+msgid "The original version of this translation is not maintained anymore"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):15
+msgid "Summary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):16
+msgid "Figure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):17
+msgid "Note"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):18
+msgid "Warning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):19
+msgid "Important"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):20
+msgid "Code Listing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):21
+msgid "Gentoo Linux Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):22
+msgid "Printable Linux Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):23
+msgid "Printable Linux Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):25
+msgid "Print"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):26
+msgid "View a printer-friendly version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):27
+msgid "View all"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):28
+msgid "View all handbook in one page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):29
+msgid "Home"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):30
+msgid "The contents of this document are licensed under the <uri link=\"http://creativecommons.org/licenses/by-sa/2.5\">Creative Commons - Attribution / Share Alike</uri> license."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):35
+msgid "Link to other book part not available"
+msgstr ""
+
+#. Metadoc stuff
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):37
+msgid "Gentoo Linux Documentation Categories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):38
+msgid "Members"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):39
+msgid "Member"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):40
+msgid "Lead"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):41
+msgid "Name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):42
+msgid "Nickname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):43
+msgid "E-mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):44
+msgid "Position"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):45
+msgid "Files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):46
+msgid "Filename"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):47
+msgid "Version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):48
+msgid "Original Version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):49
+msgid "Editing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):50
+msgid "N/A"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):51
+msgid "Bugs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):52
+msgid "Showstoppers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):53
+msgid "Normal Bugs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):54
+msgid "Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):55
+msgid "Bug ID"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):56
+msgid "Untranslated files"
+msgstr ""
+
+#. Disclaimer and redirect stuff
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):59
+msgid "Disclaimer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):60
+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.<br/> This document is not actively maintained."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):67
+msgid "This handbook has been replaced by a newer version and is not maintained anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):70
+msgid "This document is a work in progress and should not be considered official yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):73
+msgid "This document is not valid and is not maintained anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):76
+msgid "You should be redirected to <uri link=\"$redirect\">the new version</uri> within a few seconds."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/ipv6.xml.pot b/doc/gettext/ipv6.xml.pot
new file mode 100644
index 0000000..75a36df
--- /dev/null
+++ b/doc/gettext/ipv6.xml.pot
@@ -0,0 +1,935 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):6
+msgid "Gentoo IPv6 Router Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):8
+msgid "Developer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):9
+msgid "latexer@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):9
+msgid "Peter Johanson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):20 ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):12
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):12
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):14
+msgid "Editor, Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):15
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):15
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):18
+msgid "cam@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):18
+msgid "Camille Huot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):21
+msgid "okun@hack.fi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):21
+msgid "Pasi Valminen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(abstract):27
+msgid "This guide shows how to setup IPv6 on a Gentoo system. This includes establishing a tunnel with a tunnel broker, some basic DNS configuration and configuring clients to use the system to connect to IPv6 addresses."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(version):37
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(date):38
+msgid "2010-08-11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):41
+msgid "Preliminaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):43
+msgid "Basic Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):46
+msgid "Any of the 2.6 kernel trees availables in Gentoo will easily support IPv6 connections. The new USAGI IPv6 stack is integrated to the kernel since Linux 2.6.0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):52
+msgid "Emerging a kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):52
+#, no-wrap
+msgid "\n# <i>emerge gentoo-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):56
+msgid "Now we are ready to enter the kernel source directory and begin our actual kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):61
+msgid "Configuring the Linux Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):61
+#, no-wrap
+msgid "\n# <i>cd /usr/src/linux</i>\n# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):66
+msgid "This assumes the symlink <path>/usr/src/linux</path> points to the sources you will be using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):71
+msgid "'make menuconfig' options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):71
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\nNetworking support ---&gt;\nNetworking options ---&gt;\n   &lt;*&gt; The IPv6 protocol (EXPERIMENTAL)\n<comment>(The IPv6 options beneath this one can be useful for many other applications,</comment>\n<comment>but should not be needed for a basic setup)</comment>\n\n<comment>(This option is only required if you are using ptrtd for 6to4 conversion)</comment>\n[*] Network device support\n   &lt;*&gt; Universal TUN/TAP device driver support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):87
+msgid "Testing IPv6 Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):90
+msgid "After enabling the recommended options, recompile your kernel and reboot into your new IPv6-enabled kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):95
+msgid "If you don't already have <b>iproute2</b> installed, we urge you to do it now. iproute2 is a network configuration suite that contains <c>ip</c>, the famous replacement for <c>ifconfig</c>, <c>route</c>, <c>iptunnel</c> and others..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):101
+msgid "Installing iproute2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):101
+#, no-wrap
+msgid "\n# <i>emerge sys-apps/iproute2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(warn):105
+msgid "Use of ifconfig can cause serious headaches if you have multiple tunnel devices. You have to remove the tunnels in backorder, which means that the latest created must be removed first. You have been warned!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):111
+msgid "If IPv6 is working, the loopback device should show an IPv6 address:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):115
+msgid "Checking the loopback device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):115
+#, no-wrap
+msgid "\n# <i>ip -6 addr show lo</i>\n1: lo: &lt;LOOPBACK,UP&gt; mtu 16436\n    inet6 ::1/128 scope host \n       valid_lft forever preferred_lft forever\n    <comment>(The above lines show things are working)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):123
+msgid "Before going any further, make sure that you add <e>ipv6</e> to your list of USE variables in <path>make.conf</path>, so that future emerges of packages will include IPv6 support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):134
+msgid "Tunnel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):136
+msgid "Basic Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):139
+msgid "Most ISPs still do not offer any native IPv6 connections. To get around this limitation, there are several \"tunnel brokers\" around the globe that offer free IPv6 tunnels. This will allow you to tunnel all your IPv6 connections through an IPv4 connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):147
+msgid "Broker"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):147
+msgid "Location"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):149
+msgid "http://tunnelbroker.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):149 ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):179
+msgid "Hurricane Electric"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):150
+msgid "North America, Europe, Asia"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):153
+msgid "http://gogonet.gogo6.com/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):153 ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):238
+msgid "Freenet6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):154
+msgid "US"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):157
+msgid "http://www.sixxs.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):157
+msgid "Sixxs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):158
+msgid "Europe"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):161
+msgid "http://tunnel-broker.singnet.com.sg/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):161
+msgid "Singnet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):162
+msgid "Singapore"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):165
+msgid "http://broker.aarnet.net.au/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):165
+msgid "Aarnet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):166
+msgid "Australia/South Pacific"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):170
+msgid "Below are two examples for setting up a tunnel with two popular North American tunnels, Hurricane Electric (applies for non-heartbeat tunnels from sixxs.net as well) and Freenet6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):182
+msgid "Hurricane Electric (HE for short) offers free IPv6 tunnels and allocates a /64 block of addresses for you. It also allows configuration of reverse DNS. Getting a tunnel from HE is as easy as going to <uri>http://www.tunnelbroker.net/</uri> and filling out a one page form."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):189
+msgid "Registration includes listing information like your address and phone number."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):194
+msgid "After you have a tunnel approved and have a /64 block allocated, you can configure your Gentoo box. HE provides sample configurations based on ifconfig and the iproute utilities. The following two examples assume you have the following configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):203
+msgid "Local IPv4 Address (eth0)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):203
+msgid "68.36.91.195"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):206
+msgid "HE IPv4 Address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):206
+msgid "64.71.128.82"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):209
+msgid "Local IPv6 tunnel Address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):209
+msgid "2001:470:1F00:FFFF::189"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):212
+msgid "IPv6 Block"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):212
+msgid "2001:470:1F00:296::/64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):216
+msgid "Using the iproute2 package and the <c>ip</c> command, you would do the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):221
+msgid "Configuration of an IPv6 tunnel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):221
+#, no-wrap
+msgid "\n<comment>(Create a tunnel between the local (eth0) IPv4 and HE's remote IPv4 address)</comment>\n# <i>ip tunnel add sixbone mode sit remote 64.71.128.82 local 68.36.91.195 ttl 64 dev eth0</i>\n<comment>(Extract the tunneling overhead from the MTU)</comment>\n# <i>ip link set sixbone mtu 1280</i>\n<comment>(Bring the tunnel up)</comment>\n# <i>ip link set sixbone up</i>\n<comment>(Assign the IPv6 address to it)</comment>\n# <i>ip addr add 2001:470:1F00:FFFF::189 dev sixbone</i>\n<comment>(Route all global unicast IPv6 addresses through our 'sixbone' tunnel device)</comment>\n# <i>ip route add 2000::/3 dev sixbone</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):241
+msgid "<uri link=\"http://gogonet.gogo6.com/\">Freenet6</uri> is another free tunnel broker. Optional registration only requires a username and a valid email address. They have chosen to turn the tunnel management into a client/server setup and have created the <c>gateway6</c> client. The client is available in Portage. To install it do:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):249
+msgid "Installing the Freenet6 client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):249
+#, no-wrap
+msgid "\n# <i>emerge gateway6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):253
+msgid "Now if you chose to connect with authentification, you need to configure <c>gateway6</c> by editing <path>/etc/gateway6/gw6c.conf</path>. You should only have to change the <e>userid</e> and <e>passwd</e> fields to match those assigned from Freenet6 and change the gateway server. Below is a sample config file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):261
+msgid "gw6c.conf example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):261
+#, no-wrap
+msgid "\nauth_method=any\n<i>userid=anonymous</i>\n<i>passwd=foobar</i>\ntemplate=linux\nserver=broker.freenet6.net\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):273
+msgid "Testing your connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):276
+msgid "Now that your tunnel is configured, you can test your connection. The easiest way to do this is to use the <c>ping6</c> utility and try to ping an IPv6 host."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):282
+msgid "Testing the connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):282
+#, no-wrap
+msgid "\n# <i>emerge iputils</i>\n# <i>ping6 www.kame.net</i>\nPING www.kame.net(orange.kame.net) 56 data bytes\n64 bytes from orange.kame.net: icmp_seq=1 ttl=52 time=290 ms\n64 bytes from orange.kame.net: icmp_seq=2 ttl=52 time=277 ms\n64 bytes from orange.kame.net: icmp_seq=3 ttl=52 time=280 ms\n64 bytes from orange.kame.net: icmp_seq=4 ttl=52 time=279 ms\n64 bytes from orange.kame.net: icmp_seq=5 ttl=52 time=277 ms\n\n--- www.kame.net ping statistics ---\n5 packets transmitted, 5 received, 0% packet loss, time 4038ms\nrtt min/avg/max/mdev = 277.040/281.041/290.046/4.699 ms\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):297
+msgid "Further work is currently in progress to add better IPv6 support to the network init scripts. If you'd like to know the status of this and/or help out, email <mail link=\"latexer@gentoo.org\">latexer@gentoo.org</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):309
+msgid "IPv6 Support in Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):312
+msgid "Re-emerging packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):315
+msgid "Unless you had <e>USE=\"ipv6\"</e> in your <path>/etc/make.conf</path> previously, you probably need to re-emerge a bunch of packages to compile in IPv6 support for them. To get a list of all the installed packages which are affected by USE flag changes, use Portage's <c>--newuse</c> (<c>-N</c>) option:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):322
+msgid "Candidates for re-emerging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):322
+#, no-wrap
+msgid "\n# <i>emerge -uDNav world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):326
+msgid "If you have changed a lot of USE flags, the list could be quite long. It's suggested to keep your system up-to-date, so it won't hurt if you recompile all affected packages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):332
+msgid "Some packages detect IPv6 support automagically and hence have no ipv6 USE flag. Thus not all packages, which should support IPv6, will support it if you have not compiled it with an IPv6 enabled kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):342
+msgid "IPv6 Specific Packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):345
+msgid "There are a few packages which specifically deal with IPv6 items. Most of these are located in <path>/usr/portage/net-misc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):351
+msgid "Package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):351
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):353
+msgid "net-misc/ipv6calc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):354
+msgid "Converts an IPv6 address to a compressed format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):357
+msgid "net-misc/netcat6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):358
+msgid "netcat version that supports IPv6 and IPv4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):361
+msgid "dev-perl/Socket6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):362
+msgid "IPv6 related part of the C socket.h defines and structure manipulators"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):373
+msgid "DNS setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):375
+msgid "IPv6 and DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):378
+msgid "Just as DNS for IPv4 uses A records, DNS for IPv6 uses AAAA records. (This is because IPv4 is an address space of 2^32 while IPv6 is an address space of 2^128). For reverse DNS, the INT standard is deprecated but still widely supported. ARPA is the latest standard. Support for the ARPA format will be described here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):390
+msgid "BIND configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):393
+msgid "Recent versions of BIND include excellent IPv6 support. This section will assume you have at least minimal knowledge about the configuration and use of BIND. We will assume you are not running bind in a chroot. If you are, simply append the chroot prefix to most of the paths in the following section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):401
+msgid "First you need to add entries for both forward and reverse DNS zone files in <path>/etc/bind/named.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):406
+msgid "named.conf entries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):406
+#, no-wrap
+msgid "\n<comment>(We allow bind to listen to IPv6 addresses.</comment>\n<comment>Using 'any' is the only way to do it prior to bind-9.3)</comment>\noptions {\n    [...]\n    listen-on-v6 { any; }\n    [...]\n};\n<comment>(This will provide the forward DNS for the domain 'ipv6-rules.com':)</comment>\nzone \"ipv6-rules.com\" IN {\n    type master;\n    file \"pri/ipv6-rules.com\";\n};\n<comment>(This format for reverse DNS is \"bitwise.\" It's done by taking the IPv6 prefix,</comment>\n<comment>reversing the order of the numbers and putting a period between each number)</comment>\nzone \"6.9.2.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa\" {\n        type master;\n        file \"pri/rev-ipv6-rules.com.arpa\";\n};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):427
+msgid "Now we must create those zone files and add entries for all of our hosts:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):432
+msgid "pri/ipv6-rules.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):432
+#, no-wrap
+msgid "\n$TTL    2h\n@       IN      SOA     ipv6-rules.com. webmaster.ipv6-rules.com.  (\n                                2003052501 ; Serial\n                                28800      ; Refresh\n                                14400      ; Retry\n                                3600000    ; Expire\n                                86400 )    ; Minimum\n                NS      ns1.ipv6-rules.com\n\n        IN      AAAA    2001:470:1f00:296::1 ; address for ipv6-rules.com\nhost1   IN      AAAA    2001:470:1f00:296::2 ; address for host1.ipv6-rules.com\nhost2   IN      AAAA    2001:470:1f00:296::3:3 ; address for host2.ipv6-rules.com\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):447
+msgid "pri/rev-ipv6-rules.com.arpa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):447
+#, no-wrap
+msgid "\n$TTL 3d ; Default TTL (bind 8 needs this, bind 9 ignores it)\n@       IN SOA ipv6-rules.com. webmaster.ipv6-rules.com. (\n                        2003052501      ; Serial number (YYYYMMdd)\n                        24h             ; Refresh time\n                        30m             ; Retry time\n                        2d              ; Expire time\n                        3d )            ; Default TTL\n        IN      NS     ns1.ipv6-rules.com.\n; IPv6 PTR entries\n$ORIGIN 6.9.2.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.\n\n1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN      PTR     ipv6-rules.com.\n2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN      PTR     host1.ipv6-rules.com.\n3.0.0.0.3.0.0.0.0.0.0.0.0.0.0.0 IN      PTR     host2.ipv6-rules.com.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):468
+msgid "DJBDNS configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):471
+msgid "There are currently some third-party patches to DJBDNS available at <uri>http://www.fefe.de/dns/</uri> that allow it to do IPv6 nameserving. DJBDNS can be installed with these patches by emerging it with <e>ipv6</e> in your USE variables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(warn):478
+msgid "Not all record types are support yet with these patches. In particular, NS and MX records are not supported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):483
+msgid "Installing djbdns"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):483
+#, no-wrap
+msgid "\n# <i>emerge djbdns</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):487
+msgid "After djbdns is installed, it can be setup by running <c>tinydns-setup</c> and answering a few questions about which IP addresses to bind to, where to install tinydns, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):493
+msgid "Setting up tinydns"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):493
+#, no-wrap
+msgid "\n# <i>tinydns-setup</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):497
+msgid "Assuming we've installed <c>tinydns</c> into <path>/var/tinydns</path>, we can now edit <path>/var/tinydns/root/data</path>. This file will contain all the data needed to get tinydns handling DNS for your IPv6 delegation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):503
+msgid "sample data file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):503
+#, no-wrap
+msgid "\n<comment>(*.ipv6-rules.com is authoritatively handled by 192.168.0.1)</comment>\n.ipv6-rules.com:192.168.0.1:a:259200\n<comment>(Authoritative reverse DNS for 2001:470:1f00:296::/64)</comment>\n.6.9.2.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa:192.168.0.1:a\n<comment>(Specify the IPs for host1 and host2)</comment>\n6host1.ipv6-rules.com:200104701f0002960000000000000001:86400\n6host2.ipv6-rules.com:200104701f0002960000000000000002:86400\n<comment>(Point www to host1)</comment>\n3www.ipv6-rules.com:200104701f0002960000000000000002:86400\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):515
+msgid "Lines prefixed with a <c>6</c> will have both an AAAA and a PTR record created. Those prefixed with a <c>3</c> will only have an AAAA record created. Besides manually editing the <path>data</path> file, you can use the scripts <c>add-host6</c> and <c>add-alias6</c> to add new entries. After changes are made to the <path>data</path> file, you simply need to run <c>make</c> from <path>/var/tinydns/root</path>. This will create <path>/var/tinydns/root/data.cfb</path>, which tinydns will use as its source of information for DNS requests."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):531
+msgid "IPv6 Router"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):533
+msgid "Configure routing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):536
+msgid "Further configuration is required if we want to use our system as a router for other clients wishing to connect to the outside world with IPv6. We need to enable forwarding of IPv6 packets. We can do this in one of two ways."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):543
+msgid "Enabling forwarding"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):543
+#, no-wrap
+msgid "\n# <i>echo 1 &gt; /proc/sys/net/ipv6/conf/all/forwarding</i>\nor\n# <i>sysctl -w net.ipv6.conf.all.forwarding=1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(warn):549
+msgid "The <c>radvd</c> init script explained in the next chapter enables (and disables) forwarding, making the next step unnecessary."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):554
+msgid "To enable forwarding at boot, you'll need to edit <path>/etc/sysctl.conf</path> and add the following line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):559
+msgid "sysctl.conf addition"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):559
+#, no-wrap
+msgid "\n<comment>(If you will be using radvd, this step is unnecessary)</comment>\nnet.ipv6.conf.default.forwarding=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):564
+msgid "Traffic should now be forwarded from this box through the tunnel we've established with our broker."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):569
+msgid "To assign IPv6 addresses to clients, the IPv6 specification allows for both stateless and stateful IP assignment. Stateless assignment uses a process called Router Advertisement and allows clients to obtain an IP and a default route by simply bringing an interface up. It is called \"stateless\" because there is no record of IPs assigned and the host they are assigned to. Stateful assignment is handled by DHCPv6. It is \"stateful\" because the server keeps a state of the clients who've requested IPs and received them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):584
+msgid "Stateless Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):587
+msgid "Stateless configuration is easily accomplished using the Router Advertisement Daemon, or <c>radvd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):592
+msgid "Configuring radvd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):592
+#, no-wrap
+msgid "\n# <i>emerge radvd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):596
+msgid "After having emerged <c>radvd</c>, we need to create <path>/etc/radvd/radvd.conf</path> that contains information about what IP block to assign IPs from. Here is a sample <path>radvd.conf</path> file using the prefix we've been assigned from our tunnel broker."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):603
+msgid "Sample radvd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):603
+#, no-wrap
+msgid "\ninterface eth1\n{\n        <comment>(Send advertisement messages to other hosts)</comment>\n        AdvSendAdvert on;\n        <comment>(Fragmentation is bad(tm))</comment>\n        AdvLinkMTU 1280;\n        MaxRtrAdvInterval 300;\n        <comment>(IPv6 subnet prefix we've been assigned by our PoP)</comment>\n        prefix 2001:470:1F00:296::/64\n        {\n                AdvOnLink on;\n                AdvAutonomous on;\n        };\n};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(warn):620
+msgid "Make sure the interface on the first line is correct so you broadcast router advertisement to your intranet and not to your ISP!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):625
+msgid "Further information is available in <c>man radvd.conf</c>. We can now start <c>radvd</c> and set it to start at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):630
+msgid "Starting up radvd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):630
+#, no-wrap
+msgid "\n# <i>/etc/init.d/radvd start</i>\n# <i>rc-update add radvd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):639
+msgid "Stateful Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):642
+msgid "If you'd like to use stateful configuration, you'll need to install and configure dhcpv6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):647
+msgid "Installing dhcpv6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):647
+#, no-wrap
+msgid "\n# <i>emerge dhcpv6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):651
+msgid "Next we must configure the DHCPv6 server by editing <path>/etc/dhcp6s.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):656
+msgid "Sample dhcp6s.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):656
+#, no-wrap
+msgid "\nprefer-life-time 10000;\nvalid-life-time 20000;\nrenew-time 5000;\nrebind-time 8000;\ninterface eth1 {\n    link AAA {\n        allow unicast;\n        send unicast;\n        allow rapid-commit;\n        send server-preference 5;\n        renew-time 1000;\n        rebind-time 2400;\n        prefer-life-time 2000;\n        valid-life-time 3000;\n        pool{\n            range 2001:470:1f00:296::10 to 2001:470:1f00:296::110/64;\n            prefix 2001:470:1f00:296::/64;\n        };\n    };\n};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):679
+msgid "We can now start dhcp6s, and configure it to start at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):683
+msgid "Starting dhcp6s"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):683
+#, no-wrap
+msgid "\n# <i>/etc/init.d/dhcp6s start</i>\n# <i>rc-update add dhcp6s default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):693
+msgid "IPv6 Clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):695
+msgid "Using radvd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):698
+msgid "Clients behind this router should now be able to connect to the rest of the net via IPv6. If using radvd, configuring hosts should be as easy as bringing the interface up. (This is probably already done by your net.ethX init scripts)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):705
+msgid "Connecting through IPv6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):705
+#, no-wrap
+msgid "\n# <i>ip link set eth0 up</i>\n# <i>ip addr show eth0</i>\n1: eth0: &lt;BROADCAST,MULTICAST,UP&gt; mtu 1400 qdisc pfifo_fast qlen 1000\n    link/ether 00:01:03:2f:27:89 brd ff:ff:ff:ff:ff:ff\n    inet6 2001:470:1f00:296:209:6bff:fe06:b7b4/128 scope global\n       valid_lft forever preferred_lft forever\n    inet6 fe80::209:6bff:fe06:b7b4/64 scope link\n       valid_lft forever preferred_lft forever\n    inet6 ff02::1/128 scope global\n       valid_lft forever preferred_lft forever\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):722
+msgid "Using DHCPv6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):725
+msgid "If your router is set up to use DHCPv6, your clients will also need to have the <c>net-misc/dhcpv6</c> package installed. After having done this, you need to configure your client by editing <path>/etc/dhcp6c.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):731
+msgid "Sample dhcp6c.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):731
+#, no-wrap
+msgid "\ninterface eth0 {\n        send rapid-commit;\n        request domain-name-servers;\n        iaid 11111;\n        renew-time 11000;\n};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):745
+msgid "Using 6to4 Conversion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):747
+msgid "Basic principles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):750
+msgid "6to4 conversion can be used if you want to have hosts that talk to IPv4 hosts over a purely IPv6 connection. Thus you can have an entirely IPv6 internal network, with one host dealing with connecting to the outside IPv4/IPv6 world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):761
+msgid "DNS configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):764
+msgid "To get 6to4 conversion working, a DNS proxy, <c>totd</c>, needs to be configured that will send you AAAA records for sites that really only have A records. These AAAA records will point to IPv6 addresses which don't actually exist, but which will get routed through a 6to4 proxy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):771
+msgid "First, install <c>totd</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):775
+msgid "Installing totd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):775
+#, no-wrap
+msgid "\n# <i>emerge totd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):779
+msgid "Next, we need to setup <path>/etc/totd.conf</path> with some basic configuration information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):784
+msgid "Sample /etc/totd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):784
+#, no-wrap
+msgid "\n<comment>(Points to a real DNS nameserver)</comment>\nforwarder 192.168.0.2 port 53\n<comment>(What prefix to put before faked AAAA records)</comment>\nprefix 3ffe:abcd:1234:9876::\n<comment>(What port to run totd on)</comment>\nport 5005\n<comment>(What PID file to use)</comment>\npidfile /var/run/totd.pid\n<comment>(Actually do 6to4 stuff)</comment>\nstf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):797
+msgid "<c>totd</c> must be set to use a port different than port 53 if another nameserver is running on the same machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):806
+msgid "6to4 proxy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):809
+msgid "<c>ptrtd</c> will be used as a 6to4 proxy, enabling connections between the internal IPv6 host and the outside IPv4 host."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):814
+msgid "Installing ptrtd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):814
+#, no-wrap
+msgid "\n# <i>emerge ptrtd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):818
+msgid "We now need to configure <c>ptrtd</c>, telling it what fake prefix (the one we setup <c>totd</c> to use) to create proxy connections for. Edit <path>/etc/conf.d/ptrtd</path> and set <c>IPV6_PREFIX</c>. This should be the same prefix as was configured with <c>totd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):825
+msgid "Sample /etc/ptrtd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):825
+#, no-wrap
+msgid "\nIPV6_PREFIX=\"3ffe:abcd:1234:9876::\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):829
+msgid "You can now start totd, and enable it to start at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):833
+msgid "Starting totd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):833
+#, no-wrap
+msgid "\n# <i>/etc/init.d/totd start</i>\n# <i>rc-update add totd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):842
+msgid "Client configuration and testing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):845
+msgid "Clients may now be configured to connect to both IPv4 and IPv6 hosts through an IPv6 only connection. Assuming that the clients are already receiving an IP address from radvd, we simply need to add a new DNS resolver entry, and add a default route for those \"fake addresses\". First, add an entry at the top of your <path>/etc/resolv.conf</path> pointing to the machine running <c>totd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):854
+msgid "/etc/resolv.conf sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):854
+#, no-wrap
+msgid "\nnameserver 2001:470:1f00:296::1 <comment>(The server running totd)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):858
+msgid "To test name resolution, request an AAAA record for a known IPv4 only site."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):863
+msgid "Testing name resolution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):863
+#, no-wrap
+msgid "\n# <i>dig aaaa google.com</i>\n;; ANSWER SECTION:\ngoogle.com.             300     IN      AAAA     3ffe:abcd:1234:9876::d8ef:3364\ngoogle.com.             300     IN      AAAA     3ffe:abcd:1234:9876::d8ef:3564\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):870
+msgid "We will now add a default route for all addresses prefixed with our chosen fake prefix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):875
+msgid "Adding the default route"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):875
+#, no-wrap
+msgid "\n<comment>(Assuming your IPv6 interface is eth0)</comment>\n# <i>ip route add 3ffe:abcd:1234:9876::/64 via 2001:470:1f00:296::1 dev eth0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):880
+msgid "Finally, use <c>ping6</c> to ping google.com at it's fake IPv6 location."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):884
+msgid "Testing 6to4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):884
+#, no-wrap
+msgid "\n# <i>ping6 -c 2 google.com</i>\nPING 3ffe:abcd:1234:9876::d8ef:3364(3ffe:abcd:1234:9876::d8ef:3364) 56 data bytes\n64 bytes from 3ffe:abcd:1234:9876::d8ef:3364: icmp_seq=1 ttl=54 time=0.106 ms\n64 bytes from 3ffe:abcd:1234:9876::d8ef:3364: icmp_seq=2 ttl=54 time=0.090 ms\n\n--- 3ffe:abcd:1234:9876::d8ef:3364 ping statistics ---\n2 packets transmitted, 2 received, 0% packet loss, time 1000ms\nrtt min/avg/max/mdev = 0.090/0.098/0.106/0.008 ms\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):895
+msgid "The router running <c>ptrtd</c> is actually replying, but this at least tells us things are working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):905
+msgid "Other Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):909
+msgid "There are many excellent resources online pertaining to IPv6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):914
+msgid "Websites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):914
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):916
+msgid "http://www.ipv6.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):916
+msgid "www.ipv6.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):917
+msgid "General IPv6 Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):920
+msgid "http://www.linux-ipv6.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):920
+msgid "www.linux-ipv6.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):921
+msgid "USAGI Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):924
+msgid "http://www.deepspace6.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):924
+msgid "www.deepspace6.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):925
+msgid "Linux/IPv6 site"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):936
+msgid "http://www.kame.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):936
+msgid "www.kame.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):937
+msgid "*BSD implementation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):941
+msgid "On IRC, you can try <c>#ipv6</c> on <uri link=\"http://www.freenode.net/\">Freenode</uri>. You can connect to the Freenode servers using an IPv6 enabled client by connecting to <b>irc.ipv6.freenode.net</b>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/java.xml.pot b/doc/gettext/java.xml.pot
new file mode 100644
index 0000000..f0f8576
--- /dev/null
+++ b/doc/gettext/java.xml.pot
@@ -0,0 +1,641 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):6
+msgid "Gentoo Java Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//java.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail:link):9
+msgid "nichoj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail):9
+msgid "Joshua Nichols"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail:link):12
+msgid "karltk@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail):12
+msgid "Karl Trygve Kalleberg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail:link):15
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail):15
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(abstract):18
+msgid "This guide will introduce you to Java and explain how to use Java with Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(version):27
+msgid "0.23"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(date):28
+msgid "2010-07-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):31
+msgid "What is Java?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):33 ../../gentoo/xml/htdocs/doc/en//java.xml(title):170
+msgid "Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):36
+msgid "Java is a programming language developed by engineers of Sun Microsystems. The language is object-oriented and designed to run on multiple platforms without the need of recompiling code for each platform. Although Java can be compiled as a native program, much of Java's popularity can be attributed to its portability, along with other features such as garbage collection. To make platform independence possible the Java compiler compiles the Java code to an intermediate representation called \"Java bytecode\" that runs on a JRE (Java Runtime Environment) and not directly on the operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):47
+msgid "In order to run Java bytecode, one needs to have a JRE (Java Runtime Environment) installed. A JRE provides core libraries, a platform dependent Java Virtual Machine, plugins for browsers, among other things. A JDK (Java Development Kit) adds programming tools, such as a bytecode compiler and a debugger."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):60
+msgid "Before You Begin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):62
+msgid "Existing installs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):65
+msgid "For existing installs, regardless of if you have installed anything Java before, make sure you have followed the <uri link=\"/proj/en/java/java-upgrade.xml\">Java Upgrade Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):74
+msgid "New installs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):77
+msgid "New installs should require no further preparation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):86
+msgid "Installing a Virtual Machine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):88
+msgid "The choices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):91
+msgid "Gentoo provides numerous Runtime Environments (JREs) and Development Kits (JDKs). Among the current choices, we have:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):98
+msgid "Vendor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):99
+msgid "JDK"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):100
+msgid "JRE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):103
+msgid "Sun's Java Kit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):104
+msgid "dev-java/sun-jdk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):105
+msgid "dev-java/sun-jre-bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):108
+msgid "The IBM Java Kit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):109
+msgid "dev-java/ibm-jdk-bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):110
+msgid "dev-java/ibm-jre-bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):113
+msgid "BEA WebLogic's J2SE Development Kit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):114
+msgid "dev-java/jrockit-jdk-bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):126
+msgid "Installing a JRE/JDKs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):129
+msgid "To install your profile's default JDK, you can run <c>emerge virtual/jdk</c>. Or to install your profile's default JRE, you can <c>emerge virtual/jre</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):134
+msgid "In recent events, Sun has relicensed their JDK and JRE under a more Linux distro friendly license. As a result, Sun Java 1.5 and onwards are freely downloadable, without any further hassle."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):140
+msgid "A JDK also includes a JRE, so if you install a JDK you shouldn't have to also have to install a JRE."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):148
+msgid "Installing fetch-restricted virtual machines"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):151
+msgid "Some of the JDKs and JREs require you to jump through a few hoops before installing. Simply emerge the packages as you normally would. The ebuilds will then instruct you where to go and what to download."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):157
+msgid "You should download the indicated file(s) into <path>/usr/portage/distfiles</path>. Once there, you can rerun the emerge command, at which point the JRE/JDK will be begin to install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):168
+msgid "Configuring your virtual machine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):173
+msgid "Gentoo has the ability to have multiple JDKs and JREs installed without causing conflicts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):178
+msgid "Using the <c>java-config</c> tool, you can set the system-wide default (provided you have root access). Users can also use <c>java-config</c> to set up their own personal default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):184
+msgid "You can also use <e>eselect</e> to change the system and user vm. See <c>eselect java-vm help</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):192
+msgid "Setting a default virtual machine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):195
+msgid "Running the command <c>java-config --list-available-vms</c> will give you a list of all JREs and JDKs installed on your system. Here is an example of output:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):201
+msgid "Listing available VMs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):201
+#, no-wrap
+msgid "\n# <i>java-config --list-available-vms</i>\nThe following VMs are available for generation-2:\n1)      IcedTea6-bin 1.4.1 [icedtea6-bin]\n2)      Sun JDK 1.5.0.20 [sun-jdk-1.5] <comment>(Build Only)</comment>\n*)      Sun JDK 1.6.0.16 [sun-jdk-1.6]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):209
+msgid "VMs marked as Build Only may contain security vulnerabilities and/or be EOL. Gentoo recommends not setting these VMs as either your system or user VM. Please see <uri link=\"java.xml#build-only\">Build Only VM</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):216
+msgid "The <e>*</e> indicates this is the current active vm (system-vm or user-vm when set). The name in the brackets (<e>[]</e>) is the handle or ID for that particular VM. You use the handle or the number to <c>java-config --set-system-vm</c>. Here is an example of how to set the system VM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):223
+msgid "Setting the System VM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):223
+#, no-wrap
+msgid "\n<comment>(By handle (preferred))</comment>\n# <i>java-config --set-system-vm sun-jdk-1.6</i>\nNow using sun-jdk-1.6 as your generation-2 system JVM\n<comment>(By number)</comment>\n# <i>java-config --set-system-vm 3</i>\nNow using sun-jdk-1.6 as your generation-2 system JVM\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):232
+msgid "As a regular user, you can use <c>java-config --set-user-vm</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):236
+msgid "You no longer have to <c>source</c> the profile for updates to the user/system VM take place."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):244
+msgid "Build Only VM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):247
+msgid "Some virtual machines are flagged as build-only due to being EOL and/or containing security vulnerabilities. These virtual machines will not automatically be used by Gentoo for the running of applications using Gentoo launchers but will still be available for use by Gentoo's build environment as some packages may require them for building. The setting of these virtual machines as either your system or user VM is strongly discouraged as these VMs will then be used when running the <path>/usr/bin/{java,javac,..}</path> executables and will also be used by any packages not using Gentoo's launcher scripts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):262
+msgid "Preferred Build VM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):265
+msgid "While merging Java packages, the VM used for building can sometimes be different from the one currently set as the system VM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):270
+msgid "This merge time VM switching is needed when, for example, your system-vm is set to a 1.6 VM and the package you are merging requires a 1.5 VM. While merging it will select and use a 1.5 VM, leaving your system-vm choice intact."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):276
+msgid "To define which VM is selected when a switch is needed, we have created a list of <e>default/supported VMs</e> per arch. You can find them in <path>/usr/share/java-config-2/config/jdk-defaults.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):282
+msgid "Of course, Gentoo is all about choice, so you can override these defaults (and even your selected system VM) in <path>/etc/java-config-2/build/jdk.conf</path> and have complete control over which VM will get used for merging. Some examples:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):289 ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):294 ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):299
+msgid "Example /etc/java-config-2/build/jdk.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):289
+#, no-wrap
+msgid "\n<comment>(I always want it to use a sun-jdk, ie sun-jdk-1.4 for 1.4, sun-jdk-1.5 for 1.5, etc)</comment>\n*=sun-jdk\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):294
+#, no-wrap
+msgid "\n<comment>(Always use sun-jdk-1.5 wherever possible, except for when a 1.4 or 1.3 VM is explicitly required)</comment>\n*=sun-jdk-1.5\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):299
+#, no-wrap
+msgid "\n<comment># For 1.3 I prefer sun-jdk 1.4 but when it is not available, use ibm-jdk-bin,\n# For 1.5, use sun-jdk </comment>\n1.3=sun-jdk-1.4 ibm-jdk-bin\n1.5=sun-jdk\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(warn):306
+msgid "You do not <e>have</e> to edit this file. If you change these options to use a unsupported VM, things could possibly break. Because of the wide variety of available VMs, we do not have the resources to test and verify every package works on all of them. Bugs reported with a unsupported VM won't be prioritized as much as bugs present within supported VMs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):319
+msgid "Compilers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):323
+msgid "The standard Java compiler used for building is javac, which comes with each JDK. In addition to configuring the VM used at build time, it is also possible configure which compiler is used. Essentially, you define a list your preference for which compiler to use in <path>/etc/java-config-2/build/compilers.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):331
+msgid "/etc/java-config-2/build/compilers.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):331
+#, no-wrap
+msgid "\n# If the ebuild supports it\n# it will check the COMPILERS var front to back and\n# use the first compiler that is installed\n\nCOMPILERS=\"ecj-X.Y jikes javac\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):339
+msgid "Some compilers don't support all possible -target and -source arguments. Therefore, each compiler in the list is checked to see if it can support the desired -source/-target. javac will work in all cases, so if no other suitable compiler is found, it will be used instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):346
+msgid "More details about each compiler are provided below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):352
+msgid "Name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):353
+msgid "Handle"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):354
+msgid "Package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):355
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):358 ../../gentoo/xml/htdocs/doc/en//java.xml(ti):359
+msgid "javac"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):360
+msgid "N/A"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):361
+msgid "This is the default compiler that will be used, and comes with each JDK."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):366 ../../gentoo/xml/htdocs/doc/en//java.xml(ti):367
+msgid "jikes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):368
+msgid "dev-java/jikes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):369
+msgid "Jikes was originally developed by IBM. Anecdotally, it is generally quicker than javac. Note however, that it is more pedantic, and will fail under a few circumstances where javac has no issue. It also does not support Java 1.5 syntax yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):377
+msgid "Eclipse Compiler for Java"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):378
+msgid "ecj"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):379
+msgid "dev-java/eclipse-ecj"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):380
+msgid "ECJ is the compiler used by the Eclipse software development kit. It is very full featured, and is pretty fast. It does support Java 1.5 syntax."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):392
+msgid "Setting a default CLASSPATH"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(warn):396
+msgid "The options explained in this section should be considered deprecated and will most likely be removed in the future. We strongly recommend against using these, because your Java projects or application should ideally manage their own classpaths. If you choose to specify a default CLASSPATH, some applications may behave unexpectedly, because classes they weren't expecting would be on the classpath."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):405
+msgid "<c>java-config</c> can also be used to set a system-wide default CLASSPATH, as well a user-specific default CLASSPATH."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):410
+msgid "First, you will want to list available Java libraries installed on your system that might want to be put in your CLASSPATH. Here is an example of output:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):415
+msgid "Listing classes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):415
+#, no-wrap
+msgid "\n# <i>java-config --list-available-packages</i>\n[xerces-2] The next generation of high performance, fully compliant XML parsers in the Apache Xerces family (/usr/share/xerces-2/package.env)\n[junit] Simple framework to write repeatable tests (/usr/share/junit/package.env)\n[bsh] BeanShell: A small embeddable Java source interpreter (/usr/share/bsh/package.env)\n[bcel] The Byte Code Engineering Library: analyze, create, manipulate Java class files (/usr/share/bcel/package.env)\n[log4j] A low-overhead robust logging package for Java (/usr/share/log4j/package.env)\n...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):425
+msgid "Again, the names in brackets (<e>[]</e>) are the IDs that you have to pass to <c>java-config --set-system-classpath</c>. Here is an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):430
+msgid "Setting classpaths"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):430
+#, no-wrap
+msgid "\n# <i>java-config --set-system-classpath log4j,xerces-2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):434
+msgid "The current directory (<path>.</path>) will not be part of the system classpath, as that should be added in your system's login profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):439
+msgid "You will have to update your environment by logging out, then in again or sourcing <path>/etc/profile</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):444
+msgid "For users, <c>java-config --set-user-classpath</c> will create <path>~/.gentoo/java-env-classpath</path>, which you should then source from your shell's profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):450
+msgid "Sourcing user specific classpath"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):456
+msgid "If you really want a system wide or user default classpath you can add something like the following to your shell's profile. But we would advise against it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):462
+msgid "Setting classpath"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):462
+#, no-wrap
+msgid "\n# <i>export CLASSPATH=\"${CLASSPATH}:$(java-config --classpath log4j,xerces-2)\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):471
+msgid "Java Browser Plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):473
+msgid "Installing a plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):476
+msgid "You can install a Java plugin for your web browser by emerging a Java VM with the <c>nsplugin</c> USE flag set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):481
+msgid "<c>nsplugin</c> is not available for all architectures. Check for available plugins on your arch before trying to install a VM by running <c>emerge -pv &lt;java-vm&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):487
+msgid "Portage will allow you to install multiple versions of Java plugins, though only one will be used by your browser. You can check the list of available plugins by running:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):493 ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):562
+msgid "Viewing available plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):493
+#, no-wrap
+msgid "\n# <i>eselect java-nsplugin list</i>\n   [1]   sun-jre-bin-1.6\n   [2]   icedtea6-bin\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):499
+msgid "In this example, <c>sun-jre-bin</c> is selected for the browser plugin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):503
+msgid "Selecting a plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):503
+#, no-wrap
+msgid "\n# <i>eselect java-nsplugin set sun-jre-bin-1.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):507
+msgid "Verify that the correct plugin was selected:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):511 ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):586
+msgid "Verifying the correct plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):511
+#, no-wrap
+msgid "\n# <i>eselect java-nsplugin list</i>\n   [1]   sun-jre-bin-1.6  current\n   [2]   icedtea6-bin\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):517
+msgid "Java.com also provides a link to <uri link=\"http://java.com/en/download/installed.jsp\">verify your installed plugin</uri>. Additionally, if you are using a Mozilla-based browser, you can verify your Java plugin by typing <c>about:plugins</c> into the address bar."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):527
+msgid "Plugins on multilib systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):530
+msgid "If you are running a mixed 64-bit and 32-bit multilib system (for example, on AMD64), you can use 64-bit and 32-bit Java plugins. Unless you have a pressing need to run 32-bit Java applications, we recommend using native 64-bit plugins on 64-bit web browsers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):537
+msgid "There are several native 64-bit browser plugins available. The default JDK/JRE pair, <c>sun-jdk</c> and <c>sun-jre-bin</c>, both include browser plugins. Just emerge one of them with the <c>nsplugin</c> USE flag enabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):543
+msgid "Installing a 64-bit plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):543
+#, no-wrap
+msgid "\n# <i>echo \"dev-java/sun-jre-bin nsplugin\" &gt;&gt; /etc/portage/package.use</i>\n# <i>emerge sun-jre-bin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):548
+msgid "To use a 32-bit plugin on a 32-bit browser, you will need to emerge <c>emul-linux-x86-java</c> with the <c>nsplugin</c> USE flag enabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):553
+msgid "Installing a 32-bit plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):553
+#, no-wrap
+msgid "\n# <i>echo \"app-emulation/emul-linux-x86-java nsplugin\" &gt;&gt; /etc/portage/package.use</i>\n# <i>emerge emul-linux-x86-java</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):558
+msgid "Next, check which plugins are available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):562
+#, no-wrap
+msgid "\n# <i>eselect java-nsplugin list</i>\nAvailable 32-bit Java browser plugins\n  [1]   emul-linux-x86-java-1.5\n  [2]   emul-linux-x86-java-1.6\nAvailable 64-bit Java browser plugins\n  [1]   icedtea6-bin\n  [2]   sun-jre-bin-1.6\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):572
+msgid "Now select the right plugin for your browsers:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):576
+msgid "Selecting plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):576
+#, no-wrap
+msgid "\n<comment>(Choose the plugins for 32-bit and 64-bit browsers)</comment>\n# <i>eselect java-nsplugin set 32bit emul-linux-x86-java-1.6</i>\n# <i>eselect java-nsplugin set 64bit sun-jre-bin-1.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):582
+msgid "Verify the correct plugin was selected:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):586
+#, no-wrap
+msgid "\n# <i>eselect java-nsplugin list</i>\nAvailable 32-bit Java browser plugins\n  [1]   emul-linux-x86-java-1.5\n  [2]   emul-linux-x86-java-1.6  current\nAvailable 64-bit Java browser plugins\n  [1]   icedtea6-bin\n  [2]   sun-jre-bin-1.6  current\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):601
+msgid "USE flags for use with Java"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):603
+msgid "Setting USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):606
+msgid "For more information regarding USE flags, refer to the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2\">USE flags</uri> chapter from the Gentoo Handbook."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):615
+msgid "The flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):619
+msgid "The <b>java</b> flag adds support for Java in a variety of programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):620
+msgid "The <b>nsplugin</b> flag adds support for Mozilla-like browsers (including Firefox). You will need this for viewing Java applets in your Mozilla-like browser."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):625
+msgid "The <b>source</b> flag installs a zip of the source code of a package. This is traditionally used for IDEs to 'attach' source to the libraries you are using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):630
+msgid "The <b>jce</b> flag adds support for the Java Cryptography Engine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):631
+msgid "For Java packages, the <b>doc</b> flag will build API documentation using javadoc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):642
+msgid "Additional resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):644
+msgid "Off-line resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):648
+msgid "java-config man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):655
+msgid "Online resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):659
+msgid "The <uri link=\"http://www.gentoo.org/proj/en/java/\">Java Project Page</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):663
+msgid "The <uri link=\"http://news.gmane.org/gmane.linux.gentoo.java\">gentoo-java</uri>, <uri link=\"http://news.gmane.org/gmane.linux.gentoo.user\">gentoo-user</uri>, and <uri link=\"http://news.gmane.org/gmane.linux.gentoo.devel\">gentoo-dev</uri> mailing list archives"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):672
+msgid "<uri link=\"irc://irc.gentoo.org/gentoo\">#gentoo</uri> and <uri link=\"irc://irc.gentoo.org/gentoo-java\">#gentoo-java</uri> on IRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(uri:link):678
+msgid "http://en.wikipedia.org/wiki/Java_programming_language"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(uri):678
+msgid "Wikipedia's entry for Java"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):681
+msgid "If you have suggestions or questions regarding this document, please email the Gentoo Java team: <mail>java@gentoo.org</mail>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/jffnms.xml.pot b/doc/gettext/jffnms.xml.pot
new file mode 100644
index 0000000..6dfe031
--- /dev/null
+++ b/doc/gettext/jffnms.xml.pot
@@ -0,0 +1,438 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(guide:link):5
+msgid "/doc/en/jffnms.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):6
+msgid "Jffnms Installation and Setup Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(mail:link):9
+msgid "angusyoung@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(mail):9
+msgid "Otavio R. Piske"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(abstract):12
+msgid "This guide shows you how to proceed with the post installation setup of Jffnms, a network management and monitoring system, and how to monitor your systems with it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(version):22
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(date):23
+msgid "2008-03-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):26
+msgid "Jffnms Basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):31
+msgid "<uri link=\"http://www.jffnms.org\">Jffnms</uri> is a network management and monitoring system. It allows you to grab information from many different kinds of hosts and protocols. With this guide, we aim to show you how to get Jffnms properly installed and have your systems monitored by this amazing tool."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):43
+msgid "Initial Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):45
+msgid "Choosing your USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):48
+msgid "The Jffnms ebuild has the following USE flags available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(th):54
+msgid "USE Flags for Jffnms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(th):55 ../../gentoo/xml/htdocs/doc/en//jffnms.xml(th):88
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):59
+msgid "Uses Mysql to store Jffnms data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):63
+msgid "Uses PostgreSQL to store Jffnms data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):67
+msgid "Adds support for snmp, which enables jffnms to gather data from other hosts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):76
+msgid "USE flags for PHP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):79
+msgid "Being written in PHP, Jffnms is heavily dependent on PHP USE flags. In order to install Jffnms successfully, you are required to have your PHP package installed with (at least) the following USE flags:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(th):87
+msgid "USE Flags for PHP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):92
+msgid "Adds support for media-libs/gd (to generate graphics on the fly)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):96
+msgid "Adds support for Web Distributed Data eXchange"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):100
+msgid "Adds support for tcp/ip sockets"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):104
+msgid "Adds persistent session support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):108
+msgid "Adds support for the Standard PHP Library"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):112
+msgid "Enable CLI SAPI"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):119
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):122
+msgid "Just like any package in Portage, jffnms can be installed with <c>emerge</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):126
+msgid "Installing Jffnms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):126
+#, no-wrap
+msgid "\n# <i>emerge jffnms</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):130
+msgid "Jffnms should be installed in <path>/opt/jffnms/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):137
+msgid "Configuring Apache 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(warn):140
+msgid "This very basic configuration procedure for Apache does not cover all aspects of setting up a web server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):145
+msgid "Sometimes you will want to run Jffnms on your local computer instead of a remote server. If this is your case, it is very likely that you don't have an apache setup running. Don't worry about installing apache though, Portage has already done that for you. Nevertheless, you still have to configure and test apache, which (luckily) is pretty straightforward. Start by adding Apache to your default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):154
+msgid "Adding apache2 to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):154
+#, no-wrap
+msgid "\n# <i>rc-update add apache2 default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):158
+msgid "If you haven't done it yet, it's time to start apache2:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):162
+msgid "Starting apache2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):162
+#, no-wrap
+msgid "\n# <i>/etc/init.d/apache2 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):166
+msgid "Finally, point your browser at <uri>http://localhost/</uri> and you should be presented with a home page about your newly installed Apache 2. Now that we know that Apache is up and running, we can proceed to the mod_php configuration. Fire up your favorite text editor, open <path>/etc/conf.d/apache2</path> and add <c>-D PHP5</c> the APACHE2_OPTS variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):175
+msgid "Apache 2 Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):175
+#, no-wrap
+msgid "\n# <i>nano -w /etc/conf.d/apache2</i>\nAPACHE2_OPTS=\"-D DEFAULT_VHOST -D PHP5\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):180
+msgid "After that, you should create a symlink to the Jffnms install directory in your Apache document root dir. In Gentoo, by default, Apache uses <path>/var/www/localhost/htdocs</path> as document root. So, you should do the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):187
+msgid "Creating Jffnms symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):187
+#, no-wrap
+msgid "\n# <i>cd /var/www/localhost/htdocs &amp;&amp; ln -s /opt/jffnms/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):194 ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):204
+msgid "Configuring PHP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):197
+msgid "Now that Apache is running, it is time to configure PHP. Jffnms requires that you set some variables in php.ini in order to run. The <path>php.ini</path> file is usually located in <path>/etc/php/apache2-php5/php.ini</path>. You have to set these variables to the following values:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):204
+#, no-wrap
+msgid "\n# <i>nano -w /etc/php/apache2-php5/php.ini</i>\nregister_globals = On\nregister_argc_argv = On \nerror_reporting  =  E_ALL &amp; ~E_NOTICE\nallow_url_fopen = On\ninclude_path = \".:/usr/share/php5:/usr/share/php:/usr/share/php/PEAR\"\nshort_open_tag = On\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):217
+msgid "Database setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(warn):220
+msgid "Please note again that this a very basic configuration procedure for any database system and does not cover all aspects of setting up such systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):225
+msgid "Jffnms allows you to use either PostgreSQL or MySQL as its database. Here we'll show you how to create the database and necessary tables where Jffnms will store its data. It's important to note that it isn't necessary to have a database running locally to run Jffnms and except for the fact that you need to run this commands on the remote host, the procedure is the same."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):236
+msgid "Setting up PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(note):239
+msgid "If you already have a PostgreSQL database up and running, you can proceed to the <uri link=\"#use-pg\">next section</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):244
+msgid "You should add PostgreSQL to your default runlevel so it's started each time you boot your computer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):249
+msgid "Adding PostgreSQL to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):249
+#, no-wrap
+msgid "\n# <i>rc-update add postgresql default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):253
+msgid "Now you must setup the PostgreSQL database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):257
+msgid "Preparing PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):257
+#, no-wrap
+msgid "\n# <i>emerge --config postgresql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):261
+msgid "Now start PostgreSQL:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):265
+msgid "Starting PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):265
+#, no-wrap
+msgid "\n# <i>/etc/init.d/postgresql start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):272
+msgid "Using PostgreSQL as database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):275
+msgid "Once you have your PostgreSQL set up and running, you have to create a Jffnms user and a database to store host data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):280
+msgid "Creating the Jffnms user and database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):280
+#, no-wrap
+msgid "\n# <i>psql template1 postgres</i>\ntemplate1=# <i>create user jffnms password 'jfnms' createdb;</i>\ntemplate1=# <i>\\connect template1 jffnms</i>\ntemplate1=# <i>create database jffnms;</i>\ntemplate1=# <i>\\q</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):288
+msgid "Finally, you need to create all the tables where data will be stored:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):292
+msgid "Creating Jffnms tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):292
+#, no-wrap
+msgid "\n# <i>psql jffnms jffnms &lt; /opt/jffnms/docs/jffnms-0.8.3.pgsql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):296
+msgid "Once you have run those steps, the PostgreSQL database configuration for Jffnms should be ok."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):304
+msgid "Using MySQL as database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(warn):307
+msgid "Installing and configuring a MySQL database is not covered in this guide. Please see our <uri link=\"/doc/en/mysql-howto.xml\">MySQL Startup Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):312
+msgid "In case you want to run Jffnms with MySQL, you'll first need to create a database and a MySQL user. After that, create your MySQL table:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):317
+msgid "Create a mysql table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):317
+#, no-wrap
+msgid "\n# <i>mysql -u jffnms -pjffnms jffnms &lt; /opt/jffnms/docs/jffnms-0.8.3.mysql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):324
+msgid "UDP Port Monitoring and discovery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(warn):327
+msgid "This section covers setting up and running suid programs, so it may not be adequate for systems where security is too much an issue."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):332
+msgid "If you want UDP port monitoring and discovery, you need to set <c>nmap</c> and <c>fping</c> as a SUID programs. This may give you security hole in case there's a bug in one of them. To set them as a SUID you can run the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):339
+msgid "Setting up udp port monitoring and discovery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):339
+#, no-wrap
+msgid "\n# <i>chmod +s /usr/bin/nmap ; chmod a+x /usr/bin/nmap</i>\n# <i>chmod +s /usr/sbin/fping ; chmod a+x /usr/sbin/fping</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):349
+msgid "Configuring Jffnms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):351
+msgid "Configuring the poller process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):354
+msgid "The poller process is responsible for gathering data from hosts. In order to collect this data at regular intervals, it must be added to crontab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):359
+msgid "Collecting data at regular intervals"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):359
+#, no-wrap
+msgid "\n# <i>crontab -u jffnms /opt/jffnms/docs/unix/crontab</i>\n# <i>crontab -e -u jffnms</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):367
+msgid "Final setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):370
+msgid "By now, Jffnms should be correctly installed on your system. You still need, however, to configure Jffnms. Luckily, Jffnms provides us with an easy to use web page where it's possible to configure access to database, user access as well as check if the current host configuration suffices Jffnms needs. You can access this web interface through the following URL: <uri>http://localhost/jffnms/admin/setup.php</uri>. You can login to your new installation by using the username and password <c>admin</c>. You should visit <uri link=\"http://www.jffnms.org/\">Jffnms's home page</uri> for details on how to properly configure it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):387
+msgid "Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):391
+msgid "Though Jffnms is a wonderful application, it is a bit hard to get it up and running. So if you run into problems with Jffnms, there are some places where you can look for help:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):399
+msgid "http://www.jffnms.org/docs/installing.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):399
+msgid "Jffnms Installation Manual"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):403
+msgid "http://www.jffnms.org/docs/jffnms.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):403
+msgid "Jffnms Manual"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):405
+msgid "http://forums.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):405
+msgid "Gentoo Forums"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):407
+msgid "http://www.postgresql.org/docs/8.0/static/index.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):407
+msgid "PostgreSQL 8 Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):410
+msgid "http://dev.mysql.com/doc/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):410
+msgid "MySQL Documentation"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/kde-config.xml.pot b/doc/gettext/kde-config.xml.pot
new file mode 100644
index 0000000..570010a
--- /dev/null
+++ b/doc/gettext/kde-config.xml.pot
@@ -0,0 +1,56 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(guide:redirect):7
+msgid "/proj/en/desktop/kde/kde4-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(title):9
+msgid "The KDE Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(mail:link):12
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(mail):12
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(abstract):15
+msgid "One of the most used desktop environments is KDE. This guide tries to describe all aspects of KDE, including installation, configuration and usage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(version):24
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(date):25
+msgid "2008-04-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(title):28
+msgid "Moved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(p):32
+msgid "This document was moved to <uri>/proj/en/desktop/kde/kde4-guide.xml</uri>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/kde-split-ebuilds.xml.pot b/doc/gettext/kde-split-ebuilds.xml.pot
new file mode 100644
index 0000000..3b208f8
--- /dev/null
+++ b/doc/gettext/kde-split-ebuilds.xml.pot
@@ -0,0 +1,68 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(guide:redirect):7
+msgid "/proj/en/desktop/kde/kde-split-ebuilds.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(title):9
+msgid "The KDE Split Ebuilds HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(mail:link):12
+msgid "danarmak@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(mail):12
+msgid "Dan Armak"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(mail:link):15
+msgid "greg_g@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(mail):15
+msgid "Gregorio Guidi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(abstract):18
+msgid "With KDE 3.4, the 'split ebuilds' were introduced into Portage. This page documents the reasons behind the transition, the new features it brings and the way to upgrade from the old-style 'monolithic' ebuilds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(version):28
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(date):29
+msgid "2008-04-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(title):32
+msgid "Moved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(p):36
+msgid "This document was moved to <uri>/proj/en/desktop/kde/kde-split-ebuilds.xml</uri>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/kernel-config.xml.pot b/doc/gettext/kernel-config.xml.pot
new file mode 100644
index 0000000..db2a896
--- /dev/null
+++ b/doc/gettext/kernel-config.xml.pot
@@ -0,0 +1,496 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(guide:link):5
+msgid "/doc/en/kernel-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):6
+msgid "Gentoo Linux Kernel Configuration Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):9
+msgid "dsd@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):9
+msgid "Daniel Drake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):17
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):12
+msgid "curtis119@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):12
+msgid "Curtis Napier"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):15
+msgid "jdr@xemoka.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):15
+msgid "Justin Robinson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):18
+msgid "rane@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):18
+msgid "Łukasz Damentko"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):20 ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):21
+msgid "smithj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):21
+msgid "Jonathan Smith"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(abstract):27
+msgid "This document aims to introduce the concepts of manual kernel configuration, and to detail some of the most common configuration pitfalls."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(version):36
+msgid "1.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(date):37
+msgid "2010-03-21"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):40
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):44
+msgid "Gentoo provides two ways for you to handle kernel installation and upgrade: <e>automatic</e> (genkernel), and <e>manual</e>. Although the automatic method can be regarded as <e>easier</e> for the user, there are a number of reasons why a large proportion of Gentoo users choose to configure their kernel manually: greater flexibility, smaller kernel, shorter compilation time, learning experience, severe boredom, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):53
+msgid "This guide does not cover the automatic method (genkernel). If you'd prefer to use genkernel to compile and install your kernel, head over to the <uri link=\"/doc/en/genkernel.xml\">Genkernel documentation</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):59
+msgid "This guide does not attempt to document the manual configuration process from start to finish -- the configuration process relies upon a large degree of common sense, and a relatively high level of technical knowledge about your system. Instead, this document will introduce the concepts of manual configuration and detail the most common pitfalls which users face."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):67
+msgid "This document is written with recent kernels in mind, for the most common computer architectures. Some details may differ for older kernels or more exotic architectures, but much of the content will still be relevant."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):73
+msgid "At this point, you are assumed to have Linux kernel sources unpacked on your hard disk (usually somewhere under <c>/usr/src</c>), and you are expected to know how to enter the <c>menuconfig</c> configuration utility and move through the menu system. If you are not already at this stage, we do have other documentation available to help you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):82
+msgid "The <uri link=\"/doc/en/gentoo-kernel.xml\">Kernel Guide</uri> lists the various kernel source packages we have available"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):86
+msgid "The <uri link=\"/doc/en/kernel-upgrade.xml\">Kernel Upgrade Guide</uri> explains how to upgrade your kernel or switch from one to another."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):90
+msgid "The <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> covers some aspects of kernel installation too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):101
+msgid "Configuration Concepts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):103
+msgid "The basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):106
+msgid "The general process is actually rather simple: you are presented with a series of options, categorised into individual menus and sub-menus, and you select the hardware support and kernel features relevant for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):112
+msgid "The kernel includes a <e>default configuration</e>, which is presented to you the first time you run menuconfig on a particular set of sources. The defaults are generally broad and sensible, which means that the majority of users will only have to make a small number of changes to the base config. If you decide to disable an option that was enabled by default, make sure you have a relatively good understanding of exactly what that option does, and the consequences of disabling it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):122
+msgid "If this is your first time configuring a Linux kernel, you should probably aim to be conservative: don't be too adventurous, and aim to make as few modifications to the default settings as possible. At the same time, keep in mind that there are certain parts of the configuration which you absolutely must customise to your system setup to actually allow it to boot!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):133
+msgid "Built-in vs modular"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):136
+msgid "Most configuration options are <e>tristate</e>: they can be either not built at all, built directly into your kernel (Y), or built as a module (M). Modules are stored externally on the filesystem, whereas built-in items are built directly into the kernel image itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):143
+msgid "There is an important difference between built-in and modular: with a few exceptions, the kernel makes no attempt whatsoever to load any external modules when you might need them (it is left up to the user). While certain other parts of the system may have load-on-demand facilities, and there are some automatic module loading utilities available, it is recommended that you build hardware support and kernel features directly into the kernel. The kernel can then ensure the functionality and hardware support is available whenever it needs it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):154
+msgid "Of course, for some parts of the configuration, built-in is an absolute requirement. For example, if your root partition was an <c>ext2</c> filesystem, your system would not boot if ext2 was built as a module (the system would have to look on the root partition to find the ext2 module, but it cannot look on the root partition unless it already has ext2 support loaded!)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):165
+msgid "Hardware support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):168
+msgid "Beyond detecting the <e>architecture type</e> of your system, the configuration utility makes no attempt to identify which hardware is actually present in your system. While there are default settings for some hardware support, you almost certainly need to find and select the configuration options relevant to your system's hardware configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):176
+msgid "This simply requires knowledge of the components inside and connected to your computer, or for you to identify these components. For most internal components, you need to identify the <e>chipset</e> used on each one, rather than the retail product name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):183
+msgid "There are some utilities available that will help you. <c>lspci</c> (part of the <c>sys-apps/pciutils</c> package) will identify your PCI-based and AGP-based hardware, and this includes components built onto the motherboard itself. <c>lsusb</c> (from the <c>sys-apps/usbutils</c> package) will identify devices connected to USB ports."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):191
+msgid "The situation is somewhat confused by varying degrees of standardisation in the hardware world. Unless you really deviate from the defaults, your IDE hard disks will \"just work\", as will your PS/2 or USB keyboard and mouse. You'll get basic VGA display support. However, some devices such as ethernet adapters are barely standardised at all, so you'll have to identify the ethernet chipset and select the appropriate hardware support for your specific card to get any network access at all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):201
+msgid "In addition, while some things just-about-work with the default settings, you may need to select more specialised options to get the full potential from your system. For example, if you do not enable the support for the appropriate IDE chipset, your IDE hard disks will run <e>very</e> slowly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):211
+msgid "Kernel features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):214
+msgid "As well as hardware support, you also need to think in terms of the software features you require in your kernel. One important example of such a feature is filesystem support: you need to select support for the filesystems in use on your hard disk, as well as any filesystems you might be using on external storage (e.g. VFAT on USB flash disks)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):222
+msgid "Another common example is advanced network functionality. If you want to do some kind of routing or firewalling, you need to ensure the relevant configuration items are included in your kernel config."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):231
+msgid "Ready?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):234
+msgid "Now that we've introduced the concepts, you should be able to start identifying your hardware and browsing through the configuration menus, selecting the required kernel options for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):240
+msgid "The rest of this page aims to clear up common areas of confusion, and provide advice for how to avoid common problems which users often run into. Good luck!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):250
+msgid "Common problems and areas of confusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):253
+msgid "SATA disks are SCSI"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):256
+msgid "Most modern desktop systems ship with storage devices (hard disk and CD/DVD drives) on a <uri link=\"http://en.wikipedia.org/wiki/SATA\">Serial ATA</uri> bus, rather than the older <uri link=\"http://en.wikipedia.org/wiki/Parallel_ATA\">IDE</uri> (ribbon cable) bus type."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):264
+msgid "SATA support in Linux is implemented in a layer referred to as <e>libata</e>, which sits below the SCSI subsystem. For this reason, SATA drivers are found in the SCSI driver section of the configuration. Additionally, your storage devices will be treated as SCSI devices, which means SCSI disk/cdrom support is required too. Your SATA hard disk will be named as (e.g.) <c>/dev/sda</c> and your SATA CD/DVD drive will be named as (e.g.) <c>/dev/sr0</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):273
+msgid "Although the majority of these drivers are for SATA controllers, libata was not designed to be SATA-specific. All common IDE drivers will also be ported to libata in the near future, and at this point, the above considerations will also apply for IDE users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):280
+msgid "Configuration options for libata"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):280
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n SCSI device support  ---&gt;\n  &lt;*&gt; SCSI device support\n  &lt;*&gt;   SCSI disk support\n  &lt;*&gt;   SCSI CDROM support\n\n  SCSI low-level drivers  ---&gt;\n   &lt;*&gt; Serial ATA (SATA) support\n    <comment>Select your chipset from the choices listed below the above option</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):295
+msgid "IDE chipsets and DMA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):298
+msgid "Despite the introduction of SATA, IDE devices are still very common and depended upon by many. IDE is a fairly generic technology, and as such, Linux supports almost all IDE controllers out-of-the-box without any controller-specific options selected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):305
+msgid "However, IDE is an old technology, and in it's original <e>Programmed Input/Output</e> incarnation, it is unable to provide the transfer rates required for speedy access to modern storage devices. The generic IDE driver is limited to these PIO transfer modes, which result in slow data transfer rates, and significantly high CPU usage while data is being transferred to/from disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):313
+msgid "Unless you're dealing with a pre-1995 system, your IDE controller will also support an alternative transfer mode, known as <e>Direct Memory Access</e> (DMA). DMA is much much faster, and CPU utilisation is barely affected while data transfers are taking place. If you are suffering from really poor general system performance and you are using an IDE disk, chances are that DMA is not being used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(note):322
+msgid "As mentioned earlier, libata is available even for IDE drives. If you're using libata, then all your drives, including your IDE drives, will be using DMA. There's no need to do any further checking or configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):328
+msgid "If you're not using libata for your IDE disks, then you'll need to check for DMA usage and enable it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):333
+msgid "Checking if DMA is enabled on your IDE disk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):333
+#, no-wrap
+msgid "\n# <i>hdparm -d /dev/hda</i>\n\n/dev/hda:\n using_dma    =  0 (off)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):340
+msgid "To enable DMA on your IDE devices, you simply need to enable the configuration option for your IDE controller."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):345
+msgid "Configuration options for IDE controllers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):345
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n ATA/ATAPI/MFM/RLL support  ---&gt;\n  &lt;*&gt; ATA/ATAPI/MFM/RLL support\n  &lt;*&gt;   Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support\n  [*]     PCI IDE chipset support\n  <comment>Select your chipset from the choices listed below the above option</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):357
+msgid "USB Host Controllers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):360
+msgid "<uri link=\"http://en.wikipedia.org/wiki/USB\">USB</uri> is a widely adopted bus for connecting external peripherals to your computer. One of the reasons behind the success of USB is that it is a standardised protocol, however the USB <e>host controller devices</e> (HCDs) implemented on the host computer do vary a little. There are 3 main types:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):369
+msgid "<c>UHCI</c> is the Universal Host Controller Interface. It supports USB 1.1, and is usually found on motherboards based on a VIA or Intel chipset."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):373
+msgid "<c>OHCI</c> is the Open Host Controller Interface. It supports USB 1.1 and is usually found on motherboards based on an Nvidia or SiS chipset."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):377
+msgid "<c>EHCI</c> is the Extended Host Controller Interface. It is the only common host controller to support USB 2.0, and can typically be found on any computer that supports USB 2.0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):384
+msgid "Most systems will come with two of the above interface types: EHCI (USB 2.0), plus either UHCI or OHCI (USB 1.1). It is important that you select both types present on your system. While all USB 2.0 devices are backwards compatible with USB 1.1, a large proportion of USB devices (even the ones being manufactured today) are based on the USB 1.1 interface - why would a USB mouse need more than 1.5mbit/sec?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):393
+msgid "If you do not select the relevant options corresponding to the USB HCD types present on your system, you may experience 'dead' USB ports: you plug a device in, but it does not get power or respond in any way."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):399
+msgid "A neat <c>lspci</c> trick (from the <c>sys-apps/pciutils</c> package) makes it relatively easy to detect which HCDs are present in your system. Ignoring the FireWire controller which was also matched, it is easy to spot that my system requires OHCI and EHCI support:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):406
+msgid "Using lspci to detect HCD type"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):406
+#, no-wrap
+msgid "\n# <i>lspci -v | grep HCI</i>\n00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) (prog-if 10 <i>[OHCI]</i>)\n00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) (prog-if 20 <i>[EHCI]</i>)\n01:0b.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 61) (prog-if 10 [OHCI])\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):413
+msgid "Configuration for USB HCDs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):413
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n USB support  ---&gt;\n  &lt;*&gt; Support for Host-side USB\n  ---   USB Host Controller Drivers\n  &lt;*&gt;   EHCI HCD (USB 2.0) support\n  &lt;*&gt;   OHCI HCD support\n  &lt;*&gt;   UHCI HCD (most Intel and VIA) support\n  <comment>Select the HCDs present on your system, or all 3 if you are unsure.</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):427
+msgid "Multiprocessor, Hyper-Threading and Dual Core systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):430
+msgid "Many computer systems are based on multiple processors, but not always in immediately obvious ways."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):436
+msgid "Many of Intel's CPUs support a technology which they call <uri link=\"http://en.wikipedia.org/wiki/Hyperthreading\">hyper-threading</uri>, which is where the CPU is actually viewed by the system as two <e>logical</e> processors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):442
+msgid "Some of the most recent Intel/AMD CPUs actually consist of multiple physical processors inside a single package, these are known as <uri link=\"http://en.wikipedia.org/wiki/Dual_core\">dual core</uri> processors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):447
+msgid "Some high-end computer systems actually have multiple physical processors installed on specialised motherboards to provide a significant performance increase over a <e>uniprocessor</e> system. You'll probably know if you have such a system, since they aren't cheap."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):455
+msgid "In all of these cases, you need to select the appropriate kernel options to obtain optimum performance from these setups."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):460
+msgid "Configuration for multi-processing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):460
+#, no-wrap
+msgid "\nProcessor type and features  ---&gt;\n [*] Symmetric multi-processing support\n <comment>Select the above option if you are on a multi-processor system (of any type)</comment>\n [*]   SMT (Hyperthreading) scheduler support\n <comment>Select the above option if you are on an Intel Hyper-Threading CPU</comment>\n [*]   Multi-core scheduler support (NEW)\n <comment>Select the above option if your CPU is dual core</comment>\nPower management and ACPI options  ---&gt;\n [*] ACPI (Advanced Configuration and Power Interface) Support\n <comment>The above option not only enables power management features, but might\n also be a requirement for making all CPUs available to your system</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):477
+msgid "x86 High Memory support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):480
+msgid "Due to limitations in the 32-bit address space of the x86 architecture, a kernel with default configuration can only support up to 896mb RAM. If your system has more memory, only the first 896mb will be visible, unless you enable high memory support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(note):487
+msgid "This limitation is specific to the x86 (IA32) architecture. Other architectures naturally support large amounts of memory, with no configuration tweaks required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):493
+msgid "High memory support is not enabled by default, because it introduces a small system overhead. Do not be distracted by this, the overhead is insignificant when compared to the performance increase of having more memory available!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):499
+msgid "Enabling high memory support on x86"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):499
+#, no-wrap
+msgid "\nProcessor type and features  ---&gt;\n High Memory Support  ---&gt;\n  (X) 4GB\n  ( ) 64GB\n  <comment>Choose the 4GB option, unless your system has more than 4GB of RAM.</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):512
+msgid "Other kernel configuration documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):516
+msgid "So far, we have only discussed general concepts and specific problems related to kernel configuration, without going into any precise details (such details are for you to discover!). However, other parts of the Gentoo documentation collection provide specialised details for the topics at hand."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):523
+msgid "You may find these documents helpful while configuring those specific areas, but if you are new to kernel configuration, don't be too adventurous. Start by getting a basic system up and running, you can always come back later to add support for your audio, printing, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):531
+msgid "The <uri link=\"/doc/en/alsa-guide.xml\">ALSA Guide</uri> details the configuration options required for sound card support. Note that ALSA is one exception to the suggested scheme of not building things as modules: ALSA is actually much easier to configure when the components are modular."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):537
+msgid "The <uri link=\"/doc/en/bluetooth-guide.xml\">Bluetooth Guide</uri> details the options you need in order to use bluetooth devices on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):541
+msgid "The <uri link=\"/doc/en/ipv6.xml\">IPv6 Router Guide</uri> describes how to configure your kernel for routing using the next generation network addressing scheme."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):546
+msgid "If you will be using the closed-source nVidia graphics drivers for improved 3D graphics performance, the <uri link=\"/doc/en/nvidia-guide.xml\">nVidia Guide</uri> lists the options that should and should not be selected on such a system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):552
+msgid "Amongst other things, the <uri link=\"/doc/en/power-management-guide.xml\">Power Management Guide</uri> explains how to configure your kernel for CPU frequency scaling, and for suspend and hibernate functionality."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):558
+msgid "If you are running a PowerPC system, the <uri link=\"/doc/en/gentoo-ppc-faq.xml\">PPC FAQ</uri> has a few sections about kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):563
+msgid "The <uri link=\"/doc/en/printing-howto.xml\">Printing HOWTO</uri> lists the kernel options needed to support printing in Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):567
+msgid "The <uri link=\"/doc/en/usb-guide.xml\">USB Guide</uri> details the configuration required to use common USB devices such as keyboards/mice, storage devices, and printers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):579
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):581
+msgid "Configuration changes do not take effect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):584
+msgid "It is very common for users to make a configuration change, but then make a small mistake in the process following on from that point. They reboot into a kernel image that is not the one they just reconfigured, observe that whatever problem they were trying to solve is still present, and conclude that the configuration change does not solve the problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):592
+msgid "The process of compiling and installing kernels is outside the scope of this document, you should refer to the <uri link=\"/doc/en/kernel-upgrade.xml\">Kernel Upgrade Guide</uri> for general guidance. In short, the process is: configure, compile, mount /boot (if not already mounted), copy new kernel image over, reboot. If you miss out any of those final stages, your changes will not take effect!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):601
+msgid "It is possible to verify if the kernel you are booted from matches the kernel compiled on your hard disk by examining the date and time of compilation. Assuming your architecture is x86 and your kernel sources are installed at <path>/usr/src/linux</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):608
+msgid "Verifying you are booted from your modified kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):608
+#, no-wrap
+msgid "\n# <i>uname -v</i>\n#4 SMP PREEMPT Sat Jul 15 08:49:26 BST 2006\n<comment>The above command displays the date and time that the kernel you are currently booted from was compiled.</comment>\n\n# <i>ls -l /usr/src/linux/arch/i386/boot/bzImage</i>\n-rw-r--r-- 1 dsd users 1504118 Jul 15 08:49 /usr/src/linux/arch/i386/boot/bzImage\n<comment>The above command displays the date and time that the kernel image on your hard disk was last compiled.</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):618
+msgid "If the two times from the above commands differ by more than 2 minutes, it indicates that you have made a mistake during kernel reinstallation and you are not booted from the kernel image that you thought you were!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):627
+msgid "Modules do not get loaded automatically"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):630
+msgid "As mentioned earlier in this document, the kernel configuration system hides a large behavioural change when selecting a kernel component as a module (M) rather than built-in (Y). It is worth repeating this again because so many users fall into this trap."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):637
+msgid "When you select a component as built-in, the code is built into the kernel image (bzImage). When the kernel needs to use that component, it can initialise and load it automatically, without any user intervention."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):643
+msgid "When you select a component as a module, the code is built into a kernel module file and installed on your filesystem. In general, when the kernel needs to use that component, it can't! With some exceptions, the kernel makes no effort to actually load these modules - this task is left up to the user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):650
+msgid "So, if you build support for your network card as a module, and you then find that you cannot access your network, it is probably because the module is not loaded - you must either do this manually or configure your system to autoload it at boot time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):657
+msgid "Unless you have reasons to do otherwise, save yourself some time by building these components directly into the kernel image, so that the kernel can automatically set these things up for you."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/kernel-upgrade.xml.pot b/doc/gettext/kernel-upgrade.xml.pot
new file mode 100644
index 0000000..0819530
--- /dev/null
+++ b/doc/gettext/kernel-upgrade.xml.pot
@@ -0,0 +1,368 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(guide:link):5
+msgid "/doc/en/kernel-upgrade.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):6
+msgid "Gentoo Linux Kernel Upgrade Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(mail:link):8
+msgid "dsd@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(mail):8
+msgid "Daniel Drake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(abstract):11
+msgid "This document describes the process of upgrading your kernel from one release to another."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(version):20
+msgid "0.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(date):21
+msgid "2007-06-22"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):28
+msgid "The kernel is one of the few package classes in portage that requires some manual intervention to complete the upgrade. Portage will download and install the kernel source for you, but then it is up to you to step in and compile the new kernel before any changes will take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):35
+msgid "Although this guide is targeted at users upgrading from one kernel release to another, it will also be useful for users migrating from one kernel package to another."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):41
+msgid "<c>gentoo-sources</c> is used as an example in this document, however, the instructions here also apply to the other packages present in our tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):51
+msgid "Why upgrade the kernel?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):55
+msgid "Generally, upgrading from one minor kernel release to the next won't bring any major differences. There are several reasons to upgrade the kernel. One is to take advantage of a specific new feature or driver; another is to be protected against a security vulnerability, or just to maintain an up-to-date and healthy system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):63
+msgid "Even if you choose not to update to every new kernel revision, it is recommended that you at least upgrade from time to time. It is strongly recommended that you immediately upgrade to a new kernel if that new release solves a security problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):75
+msgid "Obtaining the newer sources through Portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):79
+msgid "You upgrade the kernel sources like you would upgrade any other package - using the <c>emerge</c> utility. It will probably be the case that you want to upgrade your kernel when you see the upgrade appearing on your world updates list. For example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):86
+msgid "New kernel sources appearing on update list"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):86
+#, no-wrap
+msgid "\n# <i>emerge -Dup world</i>\nCalculating dependencies ...done!\n[ebuild    NS ] sys-kernel/gentoo-sources-2.6.9-r2 [2.6.8-r5]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(note):92
+msgid "The \"NS\" label in the above output means that the new kernel will be installed in a New Slot, i.e. the sources of your old kernel will be kept around, until you manually remove them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):98
+msgid "You can then go ahead and install the update, e.g.:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):102
+msgid "Upgrading your kernel sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):102
+#, no-wrap
+msgid "\n# <i>emerge -u gentoo-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):106
+msgid "The kernel sources will then be installed into a subdirectory of <path>/usr/src</path>. In the above example, the new kernel sources will be installed at <path>/usr/src/linux-2.6.9-gentoo-r2</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):117
+msgid "Updating the /usr/src/linux symbolic link"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):121
+msgid "Gentoo requires that the <path>/usr/src/linux</path> symbolic link points to the sources of the kernel you are running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):126
+msgid "Portage can update the symlink automatically when you emerge new kernel sources. All you have to do is add the <c>symlink</c> flag to the USE variable in <path>/etc/make.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):132
+msgid "Example of USE variable in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):132
+#, no-wrap
+msgid "\n<comment>(Add the symlink keyword)</comment>\nUSE=\"<i>symlink</i> x86 3dnow 3dnowex X aac aalib adns alsa apache2\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):137
+msgid "Alternatively, you could use <c>app-admin/eselect</c> to modify the symlink."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):141
+msgid "Using eselect to symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):141
+#, no-wrap
+msgid "\n<comment>(Install eselect if you don't have it)</comment>\n# <i>emerge eselect</i>\n<comment>(See the list of available kernels)</comment>\n# <i>eselect kernel list</i>\nAvailable kernel symlink targets:\n  [1]   linux-2.6.9-gentoo-r1\n  [2]   linux-2.6.9-gentoo-r2\n<comment>(Select the correct kernel)</comment>\n# <i>eselect kernel set 1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):153
+msgid "If you really want to do it yourself, the following example shows you how to make the link point to <path>linux-2.6.9-gentoo-r2</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):158
+msgid "Updating the /usr/src/linux softlink manually"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):158
+#, no-wrap
+msgid "\n# <i>cd /usr/src</i>\n# <i>ln -sfn linux-2.6.9-gentoo-r2 linux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):168
+msgid "Configuring, compiling and installing the new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):172
+msgid "For either of these options, you should refer to the instructions given in the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri> relating to <e>Configuring the Kernel</e> and <e>Configuring the Bootloader</e>. Below is an outline of the required actions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):182
+msgid "Option 1: Automatic kernel setup with Genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):185
+msgid "If you are a genkernel user, you just need to repeat the stages you went through when installing your kernel for the first time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):190
+msgid "Simply run genkernel in the normal way:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):194
+msgid "Invoking genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):194
+#, no-wrap
+msgid "\n# <i>genkernel all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):198
+msgid "You can also use extra parameters for other genkernel functionality. For example, if you wish to configure some extra kernel options using <c>menuconfig</c> and you wish genkernel to automatically update your grub boot loader configuration, then invoke genkernel as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):205
+msgid "Invoking genkernel with some common arguments"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):205
+#, no-wrap
+msgid "\n# <i>genkernel --menuconfig --bootloader=grub all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):209
+msgid "For more info, follow the <uri link=\"/doc/en/genkernel.xml\">Gentoo Linux Genkernel Guide</uri>, or refer to the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri>. Many of the options can be set in the configuration file for <c>genkernel</c>, <path>/etc/genkernel.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):219
+msgid "Option 2: Manual configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):222
+msgid "To begin, open the <c>menuconfig</c> utility in the kernel source tree:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):226
+msgid "Invoking menuconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):226
+#, no-wrap
+msgid "\n# <i>cd /usr/src/linux</i>\n# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):231
+msgid "Select the options required for your hardware and operating environment. For additional information on kernel configuration, refer to the chapter entitled <e>Configuring the Kernel</e> of the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):238
+msgid "Next, compile your kernel and copy it over to your boot partition. Again, follow the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> instructions outlined in the chapter on <e>Configuring the Bootloader</e>. If <path>/boot</path> is a separate partition, ensure it is mounted before copying the compiled kernel to this directory! Failing to do so would keep you from booting the system with your new kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):247
+msgid "Compiling and installing the new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):247
+#, no-wrap
+msgid "\n# <i>make &amp;&amp; make modules_install</i>\n# <i>mount /boot</i>\n# <i>cp arch/i386/boot/bzImage /boot/bzImage-2.6.9-gentoo-r2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):253
+msgid "Finally, you should update your boot loader configuration, adding an entry for the new kernel (don't delete the old one just yet!) and unmount the <path>/boot</path> partition. Again, refer to the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> for detailed instructions on this procedure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):266
+msgid "Reinstalling external modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):270
+msgid "If you use any kernel modules that are not included in the kernel source tree but are provided elsewhere in Portage (e.g. ALSA drivers and NVIDIA or ATI graphics drivers), then you must reinstall these after upgrading the kernel. This is as simple as re-merging the packages involved. For more information, refer to the chapter on <e>Configuring the Kernel</e> in the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):279
+msgid "We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which rebuilds all the kernel modules you have installed using separate ebuilds for the kernel at <path>/usr/src/linux</path>. Its use is straightforward. After emerging it, simply run <c>module-rebuild populate</c> to populate the database with a list of packages that will need to be rebuilt after upgrading the kernel. Once you have finished upgrading or recompiling your kernel, run <c>module-rebuild rebuild</c> to rebuild the drivers for your new kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):289
+msgid "For more information, run <c>module-rebuild</c> without any options to see a list of commands that can be passed to the utility."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):299
+msgid "Rebooting into the new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):303
+msgid "Next, close all applications and reboot your system. If you followed the above instructions correctly, the boot loader menu should include an entry for the new kernel. Select the new kernel and let the system boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):309
+msgid "Hopefully, your system successfully boots with the new kernel, and you can log in to resume whatever you were doing. If this is the case, then the upgrade is complete."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):315
+msgid "If you made a mistake and the system fails to boot with the new kernel, reboot the system and select the entry from the boot loader that corresponds to the last known working kernel. You can then restart from the <uri link=\"#install\"> Configuring, compiling, and installing the new kernel</uri> stage -- making the appropriate changes to correct your mistake. In some cases, you might not even need to reboot to do this (e.g. you missed a driver for an audio device, Ethernet adapter, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):330
+msgid "Running multiple kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):334
+msgid "You may have noticed, that when installing the sources for your newer kernel, the sources for your existing kernel were not removed. This is by design -- it allows you to easily switch between running different kernels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):340
+msgid "Switching between multiple kernels is as simple as leaving the kernel sources under <path>/usr/src/</path> and leaving the <path>bzImage</path> binaries on your <path>/boot</path> partition (referenced by entries in your boot loader configuration). Every time you boot up, you will be presented with a choice of which kernel to boot into."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):353
+msgid "Removing older kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):357
+msgid "Continuing on from the last section, you may be happy with your new kernel and not have any need to keep older kernel versions around. To easily remove all sources for a particular kernel except for the newest one, you can take advantage of the <e>prune</e> option available through <c>emerge</c>. Continuing the example using <c>gentoo-sources</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):365
+msgid "Pruning old versions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):365
+#, no-wrap
+msgid "\n# <i>emerge -P gentoo-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):369
+msgid "In most cases, temporary files used during compilation will still remain under the appropriate source directory under <path>/usr/src</path>. It is safe to remove these using <c>rm</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):375
+msgid "You can also safely delete any modules that were used by this kernel. This can be done by removing the appropriate directories under <path>/lib/modules/</path> that relate to the kernel versions you are removing. Be careful not to delete modules belonging to kernels that you still use!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):382
+msgid "Finally, you can mount your <path>/boot</path> partition and remove the <path>bzImage</path> file(s) for the kernel(s) you are pruning. You should also edit your boot loader configuration so that it no longer references such kernel(s)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):394
+msgid "Advanced: Using your old kernel .config to configure a new one"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):398
+msgid "It is sometimes possible to save time by re-using the configuration file from your old kernel when configuring the new one. Note that this is generally unsafe -- too many changes between every kernel release for this to be a reliable upgrade path."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):405
+msgid "The only situation where this is appropriate is when upgrading from one Gentoo kernel revision to another. For example, the changes made between <c>gentoo-sources-2.6.9-r1</c> and <c>gentoo-sources-2.6.9-r2</c> will be very small, so it is usually OK to use the following method. However, it is not appropriate to use it in the example used throughout this document: upgrading from 2.6.8 to 2.6.9. Too many changes between the official releases, and the method described below does not display enough context to the user, often resulting in the user running into problems because they disabled options that they really didn't want to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):417
+msgid "To reuse your old <path>.config</path>, you simply need to copy it over and then run <c>make oldconfig</c>. In the following example, we take the configuration from <c>gentoo-sources-2.6.9-r1</c> and import it into <c>gentoo-sources-2.6.9-r2</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):424
+msgid "Reusing your old config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):424
+#, no-wrap
+msgid "\n# <i>cd /usr/src/linux-2.6.9-gentoo-r2</i>\n# <i>cp ../linux-2.6.9-gentoo-r1/.config .</i>\n# <i>make oldconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):430
+msgid "Reusing your old config with genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):430
+#, no-wrap
+msgid "\n# <i>cd /etc/kernels</i>\n# <i>cp kernel-config-x86-2.6.9-gentoo-r1 kernel-config-x86-2.6.9-gentoo-r2</i>\n# <i>genkernel all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):436
+msgid "At this point, you may be asked to produce answers for configuration options which have changed between the two versions. Once you have done that, you can compile and install your kernel as normal, without having to go through the <c>menuconfig</c> configuration process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):443
+msgid "A much safer upgrading method is to copy your config as previously shown, and then simply run <c>make menuconfig</c>. This avoids the problems of <c>make oldconfig</c> mentioned previously, as <c>make menuconfig</c> will load up your previous configuration as much as possible into the menu. Now all you have to do is go through each option and look for new sections, removals, and so on. By using <c>menuconfig</c>, you gain context for all the new changes, and can easily view the new choices and review help screens much easier. You can even use this for upgrades such as 2.6.8 to 2.6.9; just make sure you read through the options carefully. Once you've finished, compile and install your kernel as normal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):461
+msgid "Problems after a kernel upgrade?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):465
+msgid "With the rapid development of the Linux kernel, it is inevitable that some changes made from one kernel release to another may cause some problems. If you have any issues with the latest versions of <uri link=\"/doc/en/gentoo-kernel.xml#doc_chap2\"> Gentoo-supported kernels</uri> then please do report the issues to us."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/keychain-guide.xml.pot b/doc/gettext/keychain-guide.xml.pot
new file mode 100644
index 0000000..e0ae904
--- /dev/null
+++ b/doc/gettext/keychain-guide.xml.pot
@@ -0,0 +1,344 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):6
+msgid "Gentoo Linux Keychain Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail:link):9
+msgid "eric.brown@dnbrown.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail):9
+msgid "Eric Brown"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail:link):12
+msgid "vanquirius@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail):12
+msgid "Marcelo Góes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(abstract):18
+msgid "This document describes how to use ssh shared keys along with the keychain program. It assumes basic knowledge of public key cryptography."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(version):27
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(date):28
+msgid "2010-04-21"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):31
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):33
+msgid "The problem at hand"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):36
+msgid "So you have all of these lovely Gentoo machines running <c>sshd</c>, but it's a little inconvenient for you to keep typing in all of those login passwords, right? Or maybe you have a script or cron-job that needs a convenient way to use an ssh connection. Either way, there is a solution to this problem, and it begins with public key authentication."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):47
+msgid "How does public key authentication work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):50
+msgid "Assume we have a client that wants to connect to sshd on a server. The client first generates a key pair and gives the public key to the server. Afterwards, whenever the client attempts to connect, the server sends a challenge that is encrypted with that public key. Only the holder of the corresponding private key (the client) is able to decrypt it, so as you might have guessed, the correct response leads to successful authentication."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):63
+msgid "How to use public key authentication"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):65
+msgid "Generating your key pair"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):68
+msgid "The first step is to create your key pair. To do this, we will use the <c>ssh-keygen</c> command as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):73
+msgid "Generating the key pair"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):73
+#, no-wrap
+msgid "\n$ <i>ssh-keygen -t dsa</i>\n<comment>(Just accept the default values, and make sure to enter a strong passphrase)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(warn):78
+msgid "Be sure to choose a strong passphrase, especially if this key is used for root logons!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):83
+msgid "You should now have a private key in <path>~/.ssh/id_dsa</path> and a public key in <path>~/.ssh/id_dsa.pub</path>. We are ready to copy the public key over to the remote host."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):92
+msgid "Preparing the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):95
+msgid "We will be copying the <path>~/.ssh/id_dsa.pub</path> file over to the server that runs sshd. We will also be adding it to the <path>~/.ssh/authorized_keys</path> file that belongs the connecting user on that server. Here's an example of how to do that if you already have ssh access to the server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):103
+msgid "Copying the public key to the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):103
+#, no-wrap
+msgid "\n$ <i>scp ~/.ssh/id_dsa.pub server_user@server:~/myhost.pub</i>\n$ <i>ssh server_user@server \"cat ~/myhost.pub &gt;&gt; ~/.ssh/authorized_keys\"</i>\n$ <i>ssh server_user@server \"cat ~/.ssh/authorized_keys\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):109
+msgid "The output from that last line should show you the contents of the <path>~/.ssh/authorized_keys</path> file. Make sure it looks correct."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):117
+msgid "Testing the setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):120
+msgid "Theoretically, if all went well, and the ssh daemon on the server allows it, we should be able to get ssh access without a password on the server now. We will still need to decrypt the private key on the client with the passphrase we used before, but this should not be confused with the passphrase of the user account on the server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):128
+msgid "Testing the keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):128
+#, no-wrap
+msgid "\n$ <i>ssh server_user@server</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):132
+msgid "Hopefully, it asked you for your passphrase for id_dsa, and you were able to gain ssh access as server_user on the server. If not, login as server_user, and verify the contents of <path>~/.ssh/authorized_keys</path> to make sure each entry is on a single line. You might also want to check the sshd configuration to make sure that it prefers to use public key authorization when available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):140
+msgid "At this point, you're probably thinking, \"What's the point, I just replaced one password with another?!\" Relax, the next section will show you exactly how we can use this to save your precious time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):150
+msgid "Making public key authentication convenient"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):152
+msgid "Typical key management with ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):155
+msgid "If you've been following along, you're probably thinking that it would be great if we could somehow decrypt our private key(s) once, and gain the ability to ssh freely, without any passwords. You are in luck, that is exactly what the program <c>ssh-agent</c> is for."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):162
+msgid "The program <c>ssh-agent</c> is usually started at the beginning of your X session, or from a shell startup script like <path>~/.bash_profile</path>. It works by creating a unix-socket, and registering the appropriate environment variables so that all subsequent applications can take advantage of it's services by connecting to that socket. Clearly, it only makes sense to start it in the parent process of your X session if you want to use the set of decrypted private keys in all subsequent X applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):172
+msgid "Preparing ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):172
+#, no-wrap
+msgid "\n$ <i>ssh-agent</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(note):176
+msgid "This ssh-agent will keep keys decrypted until you kill ssh-agent. If you want to set a lifetime for the keys, use the -t argument as described in <c>man ssh-agent</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):182
+msgid "When you run ssh-agent, it should tell you the PID of the running ssh-agent, and also set a few environment variables, namely <c>SSH_AUTH_SOCK</c> and <c>SSH_AGENT_PID</c>. It should also automatically add <path>~/.ssh/id_dsa</path> to it's collection and ask you for the corresponding passphrase. If you have other private keys you want to add to the running ssh-agent, you can use the <c>ssh-add</c> command as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):191
+msgid "Adding more keys to ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):191
+#, no-wrap
+msgid "\n$ <i>ssh-add somekeyfile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):195
+msgid "Now for the magic. Since you should now have your decrypted private key ready, you should be able to ssh into the server without entering any passwords."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):200
+msgid "Ssh without passwords"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):200
+#, no-wrap
+msgid "\n$ <i>ssh server</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):204
+msgid "It would be nice to know how to shut down ssh-agent in case you need to, right?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):208
+msgid "Shutting down ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):208
+#, no-wrap
+msgid "\n$ <i>ssh-agent -k</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(note):212
+msgid "If you had problems getting ssh-agent to work, it might still be running. You can kill it like any other process by running <c>killall ssh-agent</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):217
+msgid "If you want even more convenience from ssh-agent, proceed to the next section on using keychain. Be sure to kill the running ssh-agent as in the example above if you decide to do so."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):226
+msgid "Squeezing the last drop of convenience out of ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):229
+msgid "Keychain will allow you to reuse an ssh-agent between logins, and optionally prompt for passphrases each time the user logs in. Before we get ahead of ourselves though, let's emerge it first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):235
+msgid "Installing keychain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):235
+#, no-wrap
+msgid "\n# <i>emerge keychain</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):239
+msgid "Assuming that was successful, we can now use keychain freely. Add the following to your <path>~/.bash_profile</path> to enable it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):244
+msgid "Enabling keychain in .bash_profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):244
+#, no-wrap
+msgid "\nkeychain ~/.ssh/id_dsa\n. ~/.keychain/$HOSTNAME-sh\n. ~/.keychain/$HOSTNAME-sh-gpg\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(note):250
+msgid "You can add more private keys to the command line as you desire. Also, if you want it to ask for passphrases each time you spawn a shell, add the --clear option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(note):256
+msgid "If you are not using bash, check the <b>EXAMPLES</b> section of <c>man keychain</c> for examples of use in other shells. The idea is to get those commands to run each time you use a shell."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):262
+msgid "Let's test it. First make sure we killed the ssh-agent from the previous section, then start up a new shell, usually by just logging in, or spawning a new terminal. It should prompt you for the password for each key you specified on the command line. All shells opened after that point should reuse the ssh-agent, allowing you to make passwordless ssh connections over and over."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):273
+msgid "Using keychain with KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):276
+msgid "If you are a KDE user, instead of using <path>~/.bash_profile</path>, you can let KDE manage ssh-agent for you. In order to do so, you will have to edit <path>/etc/kde/agent-startup.sh</path>, which is read during KDE's startup, and <path>/etc/kde/shutdown/agent-shutdown.sh</path>, which is executed during KDE's shutdown. Here is how you could edit those files:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):284
+msgid "Editing /etc/kde/agent-startup.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):284
+#, no-wrap
+msgid "\nif [ -x /usr/bin/ssh-agent ]; then\n  eval \"$(/usr/bin/ssh-agent -s)\"\nfi\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):290
+msgid "Editing /etc/kde/shutdown/agent-shutdown.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):290
+#, no-wrap
+msgid "\nif [ -n \"${SSH_AGENT_PID}\" ]; then\n  eval \"$(ssh-agent -k)\"\nfi\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):296
+msgid "Now, all you have to do is launch a term of your choice, like Konsole, and load the keys you would like to use. For example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):301
+msgid "Loading ssh key"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):301
+#, no-wrap
+msgid "\n$ <i>keychain ~/.ssh/id_dsa</i>\n<comment>(Enter your key password)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):306
+msgid "Your keys will be remembered until you end your KDE session or kill the ssh-agent manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):316
+msgid "Concluding remarks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):318
+msgid "Security considerations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):321
+msgid "Of course, the use of ssh-agent may add a bit of insecurity to your system. If another user were to use your shell while you were in the bathroom, he could login to all of your servers without passwords. As a result, it is a risk to the servers you are connecting to, and you should be sure to consult the local security policy. If you do use it, be sure to take the appropriate measures to ensure the security of your sessions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):333
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):336
+msgid "Most of this should work pretty well, but if you encounter problems, you'll certainly want to know a few useful things."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(li):342
+msgid "If you are unable to connect without ssh-agent, consider using ssh with the arguments -vvv to find out what's happening. Sometimes the server is not configured to use public key authentication, sometimes it is configured to ask for local passwords anyway! If that is the case, you may want to also use the -o option with ssh, or change the server sshd_config."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(li):349
+msgid "If you are having problems with ssh-agent or keychain, it may be that you are not using a shell that understands the commands they use. Consult the man pages for ssh-agent and keychain for details on working with other shells."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/ldap-howto.xml.pot b/doc/gettext/ldap-howto.xml.pot
new file mode 100644
index 0000000..7f2be77
--- /dev/null
+++ b/doc/gettext/ldap-howto.xml.pot
@@ -0,0 +1,420 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):6
+msgid "Gentoo Guide to OpenLDAP Authentication"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):9
+msgid "sj7trunks@pendulus.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail):9
+msgid "Benjamin Coles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):20 ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):12
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail):12
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):15
+msgid "tseng@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail):15
+msgid "Brandon Hale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):18
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail):18
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):21
+msgid "jokey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(abstract):27
+msgid "This guide introduces the basics of LDAP and shows you how to setup OpenLDAP for authentication purposes between a group of Gentoo boxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(version):36
+msgid "4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(date):37
+msgid "2010-07-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):40
+msgid "Getting Started with OpenLDAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):42
+msgid "What is LDAP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):45
+msgid "LDAP stands for <e>Lightweight Directory Access Protocol</e>. Based on X.500 it encompasses most of its primary functions, but lacks the more esoteric functions that X.500 has. Now what is this X.500 and why is there an LDAP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):52
+msgid "X.500 is a model for Directory Services in the OSI concept. It contains namespace definitions and the protocols for querying and updating the directory. However, X.500 has been found to be overkill in many situations. Enter LDAP. Like X.500 it provides a data/namespace model for the directory and a protocol too. However, LDAP is designed to run directly over the TCP/IP stack. See LDAP as a slim-down version of X.500."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):65
+msgid "I don't get it. What is a directory?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):68
+msgid "A directory is a specialized database designed for frequent queries but infrequent updates. Unlike general databases they don't contain transaction support or roll-back functionality. Directories are easily replicated to increase availability and reliability. When directories are replicated, temporary inconsistencies are allowed as long as they get synchronised eventually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):81
+msgid "How is information structured?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):84
+msgid "All information inside a directory is structured hierarchically. Even more, if you want to enter data inside a directory, the directory must know how to store this data inside a tree. Lets take a look at a fictional company and an Internet-like tree:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):91
+msgid "Organisational structure for GenFic, a Fictional Gentoo company"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):91
+#, no-wrap
+msgid "\ndc:         com\n             |\ndc:        genfic         <comment>(Organisation)</comment>\n          /      \\\nou:   People   servers    <comment>(Organisational Units)</comment>\n      /    \\     ..\nuid: ..   John            <comment>(OU-specific data)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):101
+msgid "Since you don't feed data to the database in this ascii-art like manner, every node of such a tree must be defined. To name such nodes, LDAP uses a naming scheme. Most LDAP distributions (including OpenLDAP) already contain quite a number of predefined (and general approved) schemes, such as the inetorgperson, a frequently used scheme to define users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):109
+msgid "Interested users are encouraged to read the <uri link=\"http://www.openldap.org/doc/admin24/\">OpenLDAP Admin Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):117
+msgid "So... What's the Use?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):120
+msgid "LDAP can be used for various things. This document focuses on centralised user management, keeping all user accounts in a single LDAP location (which doesn't mean that it's housed on a single server, LDAP supports high availability and redundancy), yet other goals can be achieved using LDAP as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):128
+msgid "Public Key Infrastructure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):129
+msgid "Shared Calendar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):130
+msgid "Shared Addressbook"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):131
+msgid "Storage for DHCP, DNS, ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):132
+msgid "System Class Configuration Directives (keeping track of several server configurations)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):136
+msgid "..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):144
+msgid "Configuring OpenLDAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):146
+msgid "Initial Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(note):149
+msgid "In this document we use the genfic.com address as an example. You will ofcourse have to change this. However, make sure that the top node is an official top level domain (net, com, cc, be, ...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):155
+msgid "Let's first emerge OpenLDAP:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):159
+msgid "Install OpenLDAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):159
+#, no-wrap
+msgid "\n# <i>emerge openldap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):163
+msgid "Now generate an encrypted password we'll use later on:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):167
+msgid "Generate password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):167
+#, no-wrap
+msgid "\n# <i>slappasswd</i>\nNew password: my-password\nRe-enter new password: my-password\n{SSHA}EzP6I82DZRnW+ou6lyiXHGxSpSOw2XO4\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):174
+msgid "Now edit the LDAP Server config at <path>/etc/openldap/slapd.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):178 ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):417 ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):440
+msgid "/etc/openldap/slapd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):178
+#, no-wrap
+msgid "\n<comment># Include the needed data schemes below core.schema</comment>\ninclude         /etc/openldap/schema/cosine.schema\ninclude         /etc/openldap/schema/inetorgperson.schema\ninclude         /etc/openldap/schema/nis.schema\n\n<comment>Uncomment modulepath and hdb module</comment>\n# Load dynamic backend modules:\nmodulepath    /usr/lib/openldap/openldap\n# moduleload    back_shell.so\n# moduleload    back_relay.so\n# moduleload    back_perl.so\n# moduleload    back_passwd.so\n# moduleload    back_null.so\n# moduleload    back_monitor.so\n# moduleload    back_meta.so\nmoduleload    back_hdb.so\n# moduleload    back_dnssrv.so\n\n<comment># Uncomment sample access restrictions (Note: maintain indentation!)</comment>\naccess to dn.base=\"\" by * read\naccess to dn.base=\"cn=Subschema\" by * read\naccess to *\n   by self write\n   by users read\n   by anonymous auth\n\n\n<comment># BDB Database definition</comment>\n\ndatabase        hdb\nsuffix          \"dc=genfic,dc=com\"\ncheckpoint      32      30 # &lt;kbyte&gt; &lt;min&gt;\nrootdn          \"cn=Manager,dc=genfic,dc=com\"\nrootpw          <i>{SSHA}EzP6I82DZRnW+ou6lyiXHGxSpSOw2XO4</i>\ndirectory       /var/lib/openldap-ldbm\nindex           objectClass     eq\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):217
+msgid "Next we edit the LDAP Client configuration file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):221
+msgid "/etc/openldap/ldap.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):221
+#, no-wrap
+msgid "\n# <i>nano -w /etc/openldap/ldap.conf</i>\n<comment>(Add the following...)</comment>\n\nBASE         dc=genfic, dc=com\nURI          ldap://auth.genfic.com:389/\nTLS_REQCERT  allow\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):230
+msgid "Now edit <path>/etc/conf.d/slapd</path> and uncomment the following OPTS line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):234
+msgid "/etc/conf.d/slapd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):234
+#, no-wrap
+msgid "\n<comment># Note: we don't use cn=config here, so stay with this line:</comment>\nOPTS=\"-F /etc/openldap/slapd.d -h 'ldaps:// ldap:// ldapi://%2fvar%2frun%2fopenldap%2fslapd.sock'\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):239
+msgid "Start slapd:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):243
+msgid "Starting SLAPd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):243
+#, no-wrap
+msgid "\n# <i>/etc/init.d/slapd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):247
+msgid "You can test with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):251
+msgid "Test the SLAPd daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):251
+#, no-wrap
+msgid "\n# <i>ldapsearch -x -D \"cn=Manager,dc=genfic,dc=com\" -W</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):255
+msgid "If you receive an error, try adding <c>-d 255</c> to increase the verbosity and solve the issue you have."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):265
+msgid "Client Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):267
+msgid "Migrate existing data to ldap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):270
+msgid "Go to <uri link=\"http://www.padl.com/OSS/MigrationTools.html\">http://www.padl.com/OSS/MigrationTools.html</uri> and fetch the scripts there. Configuration is stated on the page. We don't ship this anymore because the scripts are a potential security hole if you leave them on the system after porting. When you've finished migrating your data, continue to the next section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):282
+msgid "Configuring PAM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):285
+msgid "First, we will configure PAM to allow LDAP authorization. Install <c>sys-auth/pam_ldap</c> so that PAM supports LDAP authorization, and <c>sys-auth/nss_ldap</c> so that your system can cope with LDAP servers for additional information (used by <path>nsswitch.conf</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):292
+msgid "Installing pam_ldap and nss_ldap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):292
+#, no-wrap
+msgid "\n# <i>emerge pam_ldap nss_ldap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):296
+msgid "Now add the following lines in the right places to <path>/etc/pam.d/system-auth</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):301
+msgid "/etc/pam.d/system-auth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):301
+#, no-wrap
+msgid "\n<comment># Note: only add them. Don't kill stuff already in there or your box won't let you login again!</comment>\n\nauth       sufficient   pam_ldap.so use_first_pass\naccount    sufficient   pam_ldap.so\npassword   sufficient   pam_ldap.so use_authtok use_first_pass\nsession    optional     pam_ldap.so\n\n<comment># Example file:</comment>\n#%PAM-1.0\n\nauth       required     pam_env.so\nauth       sufficient   pam_unix.so try_first_pass likeauth nullok\n<i>auth       sufficient   pam_ldap.so use_first_pass</i>\nauth       required     pam_deny.so\n\n<i>account    sufficient   pam_ldap.so</i>\naccount    required     pam_unix.so\n\npassword   required     pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 try_first_pass retry=3\npassword   sufficient   pam_unix.so try_first_pass use_authtok nullok md5 shadow\n<i>password   sufficient   pam_ldap.so use_authtok use_first_pass</i>\npassword   required     pam_deny.so\n\nsession    required     pam_limits.so\nsession    required     pam_unix.so\n<i>session    optional     pam_ldap.so</i>\n\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):331
+msgid "Now change <path>/etc/ldap.conf</path> to read:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):335
+msgid "/etc/ldap.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):335
+#, no-wrap
+msgid "\n<comment>#host 127.0.0.1</comment>\n<comment>#base dc=padl,dc=com</comment>\n\nsuffix          \"dc=genfic,dc=com\"\n<comment>#rootbinddn uid=root,ou=People,dc=genfic,dc=com</comment>\n\nuri ldap://auth.genfic.com/\npam_password exop\n\nldap_version 3\npam_filter objectclass=posixAccount\npam_login_attribute uid\npam_member_attribute memberuid\nnss_base_passwd ou=People,dc=genfic,dc=com\nnss_base_shadow ou=People,dc=genfic,dc=com\nnss_base_group  ou=Group,dc=genfic,dc=com\nnss_base_hosts  ou=Hosts,dc=genfic,dc=com\n\nscope one\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):357
+msgid "Next, copy over the (OpenLDAP) <path>ldap.conf</path> file from the server to the client so the clients are aware of the LDAP environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):362
+msgid "Copying over the OpenLDAP ldap.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):362
+#, no-wrap
+msgid "\n<comment>(Substitute ldap-server with your LDAP server name)</comment>\n# <i>scp ldap-server:/etc/openldap/ldap.conf /etc/openldap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):367
+msgid "Finally, configure your clients so that they check the LDAP for system accounts:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):372
+msgid "/etc/nsswitch.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):372
+#, no-wrap
+msgid "\npasswd:         files ldap\ngroup:          files ldap\nshadow:         files ldap\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):378
+msgid "To test the changes, type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):382
+msgid "Testing LDAP Auth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):382
+#, no-wrap
+msgid "\n# <i>getent passwd|grep 0:0</i>\n\n<comment>(You should get two entries back:)</comment>\nroot:x:0:0:root:/root:/bin/bash\nroot:x:0:0:root:/root:/bin/bash\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):390
+msgid "If you noticed one of the lines you pasted into your <path>/etc/ldap.conf</path> was commented out (the <c>rootbinddn</c> line): you don't need it unless you want to change a user's password as superuser. In this case you need to echo the root password to <path>/etc/ldap.secret</path> in plaintext. This is <brite>DANGEROUS</brite> and should be chmoded to 600. What I do is keep that file blank and when I need to change someones password thats both in the ldap and <path>/etc/passwd</path> I put the pass in there for 10 seconds while I change it and remove it when I'm done."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):406
+msgid "LDAP Server Security Settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):408
+msgid "OpenLDAP permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):411
+msgid "If we take a look at <path>/etc/openldap/slapd.conf</path> you'll see that you can specify the ACLs (permissions if you like) of what data users can read and/or write:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):417
+#, no-wrap
+msgid "\naccess to *\n  by dn=\"uid=root,ou=People,dc=genfic,dc=com\" write\n  by users read\n  by anonymous auth\n\naccess to attrs=userPassword,gecos,description,loginShell\n  by self write\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):427
+msgid "This gives you access to everything a user should be able to change. If it's your information, then you got write access to it; if it's another user their information then you can read it; anonymous people can send a login/pass to get logged in. There are four levels, ranking them from lowest to greatest: <c>auth search read write</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):435
+msgid "The next ACL is a bit more secure as it blocks normal users to read other people their shadowed password:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):440
+#, no-wrap
+msgid "\naccess to attrs=\"userPassword\"\n  by dn=\"uid=root,ou=People,dc=genfic,dc=com\" write\n  by dn=\"uid=John,ou=People,dc=genfic,dc=com\" write\n  by anonymous auth\n  by self write\n  by * none\n\naccess to *\n  by dn=\"uid=root,ou=People,dc=genfic,dc=com\" write\n  by dn=\"uid=John,ou=People,dc=genfic,dc=com\" write\n  by * search\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):454
+msgid "This example gives root and John access to read/write/search for everything in the the tree below <path>dc=genfic,dc=com</path>. This also lets users change their own <path>userPassword</path>'s. As for the ending statement everyone else just has a search ability meaning they can fill in a search filter, but can't read the search results. Now you can have multiple acls but the rule of the thumb is it processes from bottom up, so your toplevel should be the most restrictive ones."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):469
+msgid "Working with OpenLDAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):471
+msgid "Maintaining the directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):474
+msgid "You can start using the directory to authenticate users in apache/proftpd/qmail/samba. You can manage it with Webmin, which provides an easy management interface. You can also use phpldapadmin, diradm, jxplorer, or lat."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):486
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):490
+msgid "We would like to thank Matt Heler for lending us his box for the purpose of this guide. Thanks also go to the cool guys in #ldap @ irc.freenode.net"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/list.xml.pot b/doc/gettext/list.xml.pot
new file mode 100644
index 0000000..4a12488
--- /dev/null
+++ b/doc/gettext/list.xml.pot
@@ -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: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(version):9
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(title):11
+msgid "Gentoo Documentation Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):19
+msgid "faq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):20
+msgid "install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):21
+msgid "desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):22
+msgid "upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):23
+msgid "gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):24
+msgid "sysadmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):25
+msgid "gentoodev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):26
+msgid "project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):27
+msgid "articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):28
+msgid "other"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/liveusb.xml.pot b/doc/gettext/liveusb.xml.pot
new file mode 100644
index 0000000..aa71c88
--- /dev/null
+++ b/doc/gettext/liveusb.xml.pot
@@ -0,0 +1,310 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):6
+msgid "Gentoo Linux LiveUSB HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(mail:link):9
+msgid "brix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(mail:link):12
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(abstract):15
+msgid "This HOWTO explains how to create a Gentoo Linux LiveUSB or, in other words, how to emulate an x86 or AMD64 Gentoo Linux LiveCD using a USB flash drive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(version):24
+msgid "7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(date):25
+msgid "2009-11-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):30
+msgid "The LiveUSB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):33
+msgid "This HOWTO explains how to create a <e>Gentoo Linux LiveUSB</e> or, in other words, how to emulate an x86 or AMD64 Gentoo Linux LiveCD using a USB flash drive. This is particularly useful for installing Gentoo Linux on a modern laptop with no CD-ROM drive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):40
+msgid "The <c>sys-boot/unetbootin</c> package provides a much easier alternative to create a bootable USB stick from any bootable CD image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):45
+msgid "Although the instructions found in this document aim at emulating a Gentoo Linux LiveCD using a USB flash drive, they should work for any arbitrary block device as long as you adjust the device names accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):54
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):57
+msgid "In order to use a Gentoo Linux LiveUSB you need the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(li):62
+msgid "Bootable USB flash drive with at least 1GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(li):63
+msgid "i686 or x86_64 computer with support for booting from USB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):66
+msgid "You will also need access to the following for creating the LiveUSB:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(li):71
+msgid "A computer running Gentoo Linux (or alternatively another Linux distribution)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):81
+msgid "Preparing the USB flash drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):83
+msgid "Partitioning the drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(warn):86
+msgid "These instructions will erase all data from the USB flash drive. Make sure to backup your data first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(impo):91
+msgid "This HOWTO assumes that the <path>/dev/sdc</path> device node corresponds to your USB flash drive. If you have other SCSI-like devices make sure to use the correct device node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):97
+msgid "Create a FAT16 partition on your USB flash drive and mark it bootable using <c>fdisk</c>. An example partitioning scheme can be seen below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):102
+msgid "If your key is 4GB or larger, use partition type <c>b</c> (W95 FAT32)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):106
+msgid "Example partitioning scheme"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):106
+#, no-wrap
+msgid "\n# <i>fdisk -l /dev/sdc</i>\n\nDisk /dev/sdc: 2063 MB, 2063597056 bytes\n255 heads, 63 sectors/track, 250 cylinders\nUnits = cylinders of 16065 * 512 = 8225280 bytes\n\n   Device Boot      Start         End      Blocks   Id  System\n/dev/sdc1   *           1         250     2008124+   6  FAT16\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):120
+msgid "Creating the filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):123
+msgid "Create a FAT16 filesystem on the USB flash drive using <c>mkdosfs</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):127
+msgid "If your key is 4GB or larger, use <c>-F 32</c> to create a FAT32 filesystem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):131
+msgid "Running mkdosfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):131
+#, no-wrap
+msgid "\n<comment>(Make sure you have sys-fs/dosfstools installed)</comment>\n# <i>emerge -av sys-fs/dosfstools</i>\n# <i>mkdosfs -F 16 /dev/sdc1</i>\nmkdosfs 2.11 (12 Mar 2005)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):141
+msgid "Installing a Master Boot Record"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):144
+msgid "Install the precompiled Master Boot Record (MBR) from <c>syslinux</c> on the USB flash drive:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):149
+msgid "Installing a master boot record"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):149
+#, no-wrap
+msgid "\n<comment>(Make sure you have sys-boot/syslinux-3.00 or later installed)</comment>\n# <i>emerge -av '&gt;sys-boot/syslinux-3'</i>\n# <i>dd if=/usr/share/syslinux/mbr.bin of=/dev/sdc</i>\n0+1 records in\n0+1 records out\n304 bytes (304 B) copied, 0.0162317 s, 18.7 kB/s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):163
+msgid "Copying the files to your key"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):165
+msgid "Mounting the Gentoo Linux Installation CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):168
+msgid "Download the Gentoo Weekly Minimal Install CD for your architecture from your local Gentoo Linux <uri link=\"/main/en/where.xml\">mirror</uri> site and mount the ISO image on <path>/mnt/cdrom</path> as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):174
+msgid "Mounting the Gentoo Linux Installation CD ISO image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):174
+#, no-wrap
+msgid "\n<comment>(Create the /mnt/cdrom mount point if needed)</comment>\n# <i>mkdir -p /mnt/cdrom</i>\n# <i>mount -o loop,ro -t iso9660 /path/to/iso.iso /mnt/cdrom</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):180
+msgid "If you receive a <e>Could not find any loop device</e> error message when mounting the iso, you need to enable the <c>Loopback device support</c> option in your kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):189
+msgid "Mounting the LiveUSB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):192
+msgid "Mount the newly formatted USB flash drive on <path>/mnt/usb</path> as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):197
+msgid "Mounting the USB flash drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):197
+#, no-wrap
+msgid "\n<comment>(Create the /mnt/usb mount point if needed)</comment>\n# <i>mkdir -p /mnt/usb</i>\n# <i>mount -t vfat /dev/sdc1 /mnt/usb</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):206 ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):215
+msgid "Copying the files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):209
+msgid "Copy the files from the Gentoo Linux Installation CD to the LiveUSB. The files need to be reordered a bit as we will be using the <c>syslinux</c> bootloader instead of <c>isolinux</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):215
+#, no-wrap
+msgid "\n# <i>cp -r /mnt/cdrom/* /mnt/usb</i>\n# <i>mv /mnt/usb/isolinux/* /mnt/usb</i>\n# <i>mv /mnt/usb/isolinux.cfg /mnt/usb/syslinux.cfg</i>\n# <i>rm -rf /mnt/usb/isolinux*</i>\n\n<comment>(The memtest86 kernel needs to be renamed for loading it via syslinux)</comment>\n# <i>mv /mnt/usb/memtest86 /mnt/usb/memtest</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):225
+msgid "You can now unmount the ISO image:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):229
+msgid "Unmounting the ISO image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):229
+#, no-wrap
+msgid "\n# <i>umount /mnt/cdrom</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):236
+msgid "Adjusting the bootloader configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):239
+msgid "Adjust the syslinux configuration file using <c>sed</c> as shown below. The <c>slowusb</c> parameter will introduce some extra delays before attempting to mount the filesystem. This is needed to allow the USB flash drive to settle upon detection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):246
+msgid "Adjusting the boot parameters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):246
+#, no-wrap
+msgid "\n# <i>sed -i \\\n    -e \"s:cdroot:cdroot slowusb:\" \\\n    -e \"s:kernel memtest86:kernel memtest:\" \\\n    /mnt/usb/syslinux.cfg</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):258
+msgid "Installing a bootloader"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):260
+msgid "Unmounting the drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):263
+msgid "Make sure you unmount the USB flash drive before installing the bootloader:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):267
+msgid "Unmounting the USB flash drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):267
+#, no-wrap
+msgid "\n# <i>umount /mnt/usb</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):274
+msgid "Installing syslinux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):277
+msgid "Finally install the <c>syslinux</c> bootloader on the USB flash drive:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):281
+msgid "Running syslinux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):281
+#, no-wrap
+msgid "\n# <i>syslinux /dev/sdc1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(impo):285
+msgid "You will need to rerun <c>syslinux /dev/sdc1</c> each time you modify the <path>syslinux.cfg</path> file for the configuration changes to take affect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):289
+msgid "If this is the first time you have used syslinux, you will need to edit <path>/etc/mtools/mtools.conf</path> on your host. Simply commenting out <c>SAMPLE FILE</c> will suffice for the purpose of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):299
+msgid "Using the LiveUSB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):301
+msgid "Booting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):304
+msgid "Insert the USB flash drive and turn on the computer, making sure the BIOS is set to boot from USB. If all goes well you should be presented with a standard syslinux prompt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):310
+msgid "You should be able to follow the generic installation instructions found in the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri> from here on."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/logcheck.xml.pot b/doc/gettext/logcheck.xml.pot
new file mode 100644
index 0000000..9cd18ca
--- /dev/null
+++ b/doc/gettext/logcheck.xml.pot
@@ -0,0 +1,193 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):6
+msgid "Logcheck Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(mail:link):9
+msgid "phajdan.jr"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(abstract):15
+msgid "This guide shows you how to analyze system logs with logcheck."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(version):23
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(date):24
+msgid "2010-10-12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):27
+msgid "Getting Started With logcheck"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):29
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):32
+msgid "<c>logcheck</c> is an updated version of <c>logsentry</c> (from the <c>sentrytools</c> package), which is a tool to analyze the system logs. Additionally, <c>logcheck</c> comes with a built-in database of common, not-interesting log messages to filter out the noise. The general idea of the tool is that all messages are interesting, except the ones explicitly marked as noise. <c>logcheck</c> periodically sends you an e-mail with a summary of interesting messages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):45 ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):65
+msgid "Installing logcheck"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(impo):48
+msgid "It is strongly recommended to remove logsentry if you have it installed on your system. Additionally, you should remove /etc/logcheck to avoid permission and file collision problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):54
+msgid "Removing logsentry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):54
+#, no-wrap
+msgid "\n<comment>(Uninstall the logsentry package)</comment>\n# <i>emerge -C logsentry</i>\n<comment>(Remove leftover files)</comment>\n# <i>rm -rf /etc/logcheck</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):61
+msgid "Now you can proceed with the installation of logcheck."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):65
+#, no-wrap
+msgid "\n# <i>emerge -av app-admin/logcheck</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):72
+msgid "Basic configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):75
+msgid "<c>logcheck</c> creates a separate user \"logcheck\" to avoid running as root. Actually, it will refuse to run as root. To allow it to analyze the logs, you need to make sure they are readable by logcheck. Here is an example for <c>syslog-ng</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):82
+msgid "/etc/syslog-ng/syslog-ng.conf snippet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):82
+#, no-wrap
+msgid "\noptions {\n        owner(root);\n\n        <comment>(Make log files group-readable by logcheck)</comment>\n        group(logcheck);\n        perm(0640);\n};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):92
+msgid "Now reload the configuration and make sure the changes work as expected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):96
+msgid "Reload syslog-ng configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):96
+#, no-wrap
+msgid "\n# <i>/etc/init.d/syslog-ng reload</i>\n<comment>(Make sure /var/log/messages has correct permissions)</comment>\n# <i>ls -l /var/log/messages</i>\n-rw-r----- 1 root logcheck 1694438 Feb 12 12:18 /var/log/messages\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):103
+msgid "You should now adjust some basic <c>logcheck</c> settings in <path>/etc/logcheck/logcheck.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):108
+msgid "Basic /etc/logcheck/logcheck.conf setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):108
+#, no-wrap
+msgid "\n# Controls the level of filtering:\n# Can be Set to \"workstation\", \"server\" or \"paranoid\" for different\n# levels of filtering. Defaults to server if not set.\n<comment>(The workstation level includes server, and server includes paranoid.\nThe paranoid level filters almost no messages)</comment>\nREPORTLEVEL=\"server\"\n\n# Controls the address mail goes to:\n# *NOTE* the script does not set a default value for this variable!\n# Should be set to an offsite \"emailaddress@some.domain.tld\"\n<comment>(Make sure you can receive the logcheck e-mails. Testing is strongly\nrecommended)</comment>\nSENDMAILTO=\"root\"\n\n# Controls if syslog-summary is run over each section.\n# Alternatively, set to \"1\" to enable extra summary.\n# HINT: syslog-summary needs to be installed.\n<comment>(If you get a lot of similar messages in the logs, you\nmay want to install app-admin/syslog-summary and enable\nthis setting)</comment>\nSYSLOGSUMMARY=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):132
+msgid "You also have to tell <c>logcheck</c> which log files to scan (<path>/etc/logcheck/logcheck.logfiles</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):137
+msgid "Basic /etc/logcheck/logcheck.logfiles setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):137
+#, no-wrap
+msgid "\n<comment>(This is an example for syslog-ng)</comment>\n/var/log/messages\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):142
+msgid "Finally, enable the logcheck cron job."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):146
+msgid "Enable logcheck cron job"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):146
+#, no-wrap
+msgid "\n<comment>(Edit the cron file and follow the instructions inside)</comment>\n# <i>nano -w /etc/cron.hourly/logcheck.cron</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(note):151
+msgid "For more information about cron read the <uri link=\"/doc/en/cron-guide.xml\">Cron Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):156
+msgid "Congratulations! Now you will be regularly getting important log messages by email. An example message looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):161
+msgid "Example logcheck message"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):161
+#, no-wrap
+msgid "\nSystem Events\n=-=-=-=-=-=-=\nFeb 10 17:13:53 localhost kernel: [30233.238342] conftest[25838]: segfault at 40 ip 40061403 sp bfc443c4 error 4\nin libc-2.10.1.so[4003e000+142000]\nFeb 11 12:31:21 localhost postfix/pickup[18704]: fatal: could not find any active network interfaces\nFeb 11 12:31:22 localhost postfix/master[3776]: warning: process //usr/lib/postfix/pickup pid 18704 exit status 1\nFeb 11 12:31:22 localhost postfix/master[3776]: warning: //usr/lib/postfix/pickup: bad command startup -- throttling\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):176
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):178
+msgid "General tips"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):181
+msgid "You can use the logcheck's <c>-d</c> switch to display more debugging information. Example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):186
+msgid "Debugging logcheck"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):186
+#, no-wrap
+msgid "\n# <i>su -s /bin/bash -c '/usr/sbin/logcheck -d' logcheck</i>\nD: [1281318818] Turning debug mode on\nD: [1281318818] Sourcing - /etc/logcheck/logcheck.conf\nD: [1281318818] Finished getopts c:dhH:l:L:m:opr:RsS:tTuvw\nD: [1281318818] Trying to get lockfile: /var/lock/logcheck/logcheck.lock\nD: [1281318818] Running lockfile-touch /var/lock/logcheck/logcheck.lock\nD: [1281318818] cleanrules: /etc/logcheck/cracking.d/kernel\n...\nD: [1281318818] cleanrules: /etc/logcheck/violations.d/su\nD: [1281318818] cleanrules: /etc/logcheck/violations.d/sudo\n...\nD: [1281318825] logoutput called with file: /var/log/messages\nD: [1281318825] Running /usr/sbin/logtail2 on /var/log/messages\nD: [1281318825] Sorting logs\nD: [1281318825] Setting the Intro\nD: [1281318825] Checking for security alerts\nD: [1281318825] greplogoutput: kernel\n...\nD: [1281318825] greplogoutput: returning 1\nD: [1281318825] Checking for security events\n...\nD: [1281318825] greplogoutput: su\nD: [1281318825] greplogoutput: Entries in checked\nD: [1281318825] cleanchecked - file: /tmp/logcheck.uIFLqU/violations-ignore/logcheck-su\nD: [1281318825] report: cat'ing - Security Events for su\n...\nD: [1281318835] report: cat'ing - System Events\nD: [1281318835] Setting the footer text\nD: [1281318835] Sending report: 'localhost 2010-08-09 03:53 Security Events' to root\nD: [1281318835] cleanup: Killing lockfile-touch - 17979\nD: [1281318835] cleanup: Removing lockfile: /var/lock/logcheck/logcheck.lock\nD: [1281318835] cleanup: Removing - /tmp/logcheck.uIFLqU\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/ltsp.xml.pot b/doc/gettext/ltsp.xml.pot
new file mode 100644
index 0000000..df5cafe
--- /dev/null
+++ b/doc/gettext/ltsp.xml.pot
@@ -0,0 +1,490 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(guide:link):5
+msgid "/doc/en/ltsp.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):6
+msgid "Gentoo - LTSP Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(author:title):7 ../../gentoo/xml/htdocs/doc/en//ltsp.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail:link):8
+msgid "lanius@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail):8
+msgid "Heinrich Wendel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail:link):11
+msgid "josiah@ritchietribe.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail):11
+msgid "Josiah Ritchie"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(author:title):13
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail:link):14
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail):14
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(abstract):17
+msgid "This guide shows you how to setup a LTSP Server with Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(version):23
+msgid "1.14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(date):24
+msgid "2008-09-28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):27
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):29
+msgid "What is LTSP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):32
+msgid "LTSP is an abbreviation for \"Linux Terminal Server Project\". Installed on a server it can supply many workstations (so called thin-clients) with identical environments. All applications run on the server and therefore you can use old PCs and convert them into XTerminals. This reduces costs and maintenance especially in an environment where you need to have an uniform workspace on each computer you login, e.g. in schools or firms."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):47 ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):61
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):49
+msgid "Preliminaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):52
+msgid "All of the examples in this document presume that your server's IP is 192.168.0.254, your domain is named yourdomain.com and your network is 192.168.0.0/24."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):64
+msgid "First of all, you must have a working Gentoo system. Please read the Gentoo Installation Manual for your architecture on <uri link=\"http://www.gentoo.org/doc\">Gentoo's Documentation Website</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):70
+msgid "Then lets begin with the easiest step, installing the ltsp package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):74
+msgid "Emerge LTSP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):74
+#, no-wrap
+msgid "\n# <i>emerge ltsp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):78
+msgid "This will install the following packages as dependencies:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):83
+msgid "<b>XFree</b>: They are called XTerminals, guess why :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):84
+msgid "<b>DHCP</b>: DHCP is a protocol for automating the configuration of computers that use TCP/IP, used by ltsp to distribute IPs to the workstations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):89
+msgid "<b>NFS</b>: NFS is a protocol to allow access to harddisks through the network, used by ltsp to mount a base system for the workstations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):94
+msgid "<b>TFTP</b>: TFTP is a simple file transfer protocol, used by ltsp to transfer the kernel to the workstations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):98
+msgid "<b>XINETD</b>: Xinetd is a powerful replacement for inetd, with advanced features, used by ltsp to start tftp."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(note):104
+msgid "If you have the kde/gnome useflag set, it will also install a complete kde/gnome system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):114
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):118
+msgid "After the emerge process has finished all services must be configured:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):125
+msgid "System Logger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):128
+msgid "To analyze problems easier, the system logger must be configured to accept remote connections. Please read the documentation of your system logger on how to achieve this. If, for example, you are using sysklogd, all you need to do is edit <path>/etc/conf.d/sysklogd</path> and add \"-r\" to the SYSLOGD line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):136
+msgid "/etc/conf.d/sysklogd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):136
+#, no-wrap
+msgid "\nSYSLOGD=\"-m 0 -r\"\nKLOGD=\"-c 3 -2\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):144
+msgid "NFS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):147
+msgid "Next step is to edit your <path>/etc/exports</path> file, in order to allow the workstations to mount the root filesystem. There should be at least two lines in it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):153
+msgid "/etc/exports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):153
+#, no-wrap
+msgid "\n/opt/ltsp-4.1/i386         192.168.0.0/255.255.255.0(ro,no_root_squash,async)\n/var/opt/ltsp/swapfiles    192.168.0.0/255.255.255.0(rw,no_root_squash,async)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(note):158
+msgid "You have to alter the network/netmask to match your network/netmask settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):163
+msgid "Now start NFS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):167
+msgid "Starting nfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):167
+#, no-wrap
+msgid "\n# <i>rc-update add nfs default</i>\n# <i>/etc/init.d/nfs start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):175
+msgid "xinetd/tftp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):177
+msgid "TFTP requires a bit of configuring to get it to work properly. First, edit <path>/etc/conf.d/in.tftpd</path> to set tftpd's options and path correctly:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):182
+msgid "/etc/conf.d/in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):182
+#, no-wrap
+msgid "\nINTFTPD_PATH=\"/tftpboot\"\nINTFTPD_OPTS=\"-s ${INTFTPD_PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):187
+msgid "The -s flag specifies that TFTP is to run in secure chrooted mode (recommended). This means that you don't need to include the <path>/tftpboot</path> path for example in the DHCP configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):193
+msgid "Next, configure xinetd to run TFTP and allow remote connections. By default TFTP won't be started by xinetd, so edit <path>/etc/xinetd.d/tftp</path> and replace <c>disable=yes</c> with <c>disable=no</c>. If the file is missing just go ahead and create <path>/etc/xinetd.d/tftp</path> with the contents below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):200
+msgid "/etc/xinetd.d/tftp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):200
+#, no-wrap
+msgid "\nservice tftp\n{\n        disable = no\n        socket_type = dgram\n        protocol = udp\n        wait = yes\n        user = root\n        server = /usr/sbin/in.tftpd\n        server_args = -s /tftpboot\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):213
+msgid "Now edit <path>/etc/xinetd.conf</path> and comment out the line <c>only_from = localhost</c> by prefacing it with a <c>#</c>. Finally, start xinetd."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):218
+msgid "Starting xinetd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):218
+#, no-wrap
+msgid "\n# <i>rc-update add xinetd default</i>\n# <i>/etc/init.d/xinetd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):226
+msgid "Name resolving"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):229
+msgid "In order for the workstation to reach all resources, a correct name resolving must be available. There are several ways to achieve this. One is to configure a DNS server for the local network, the other (and more simple) is to have almost identical <path>/etc/hosts</path> files on all systems. We are going to use the latter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):237
+msgid "All workstations must be listed in <path>/etc/hosts</path>. Take a look at the example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):242
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):242
+#, no-wrap
+msgid "\n127.0.0.1        localhost\n192.168.0.254    server      server.yourdomain.com\n192.168.0.1      ws001       ws001.yourdomain.com\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):251
+msgid "DHCP Config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):254
+msgid "This is the most complicated step in my opinion, you have to create a valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):260
+msgid "dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):260
+#, no-wrap
+msgid "\n<comment>(Some general options)</comment>\ndefault-lease-time            21600;\nmax-lease-time                21600;\nuse-host-decl-names           on;\nddns-update-style             ad-hoc;\n\n<comment>(Bootp options)</comment>\nallow booting;\nallow bootp;\n\n<comment>(Network Options)</comment>\noption subnet-mask            255.255.255.0;\noption broadcast-address      192.168.0.255;\noption routers                192.168.0.254;\noption domain-name-servers    192.168.0.254;\noption log-servers            192.168.0.254;\noption domain-name            \"yourdomain.com\";\n\n<comment>(LTSP Path Options)</comment>\noption root-path              \"192.168.0.254:/opt/ltsp-4.1/i386\";\nfilename                      \"/lts/vmlinuz-2.4.26-ltsp-2\";\n<comment>(Address of the tftp server to download the ltsp file from)</comment>\nnext-server                   192.168.0.254;\n\n<comment>(If your workstations have ISA NICs uncomment the following)</comment>\n<comment>(lines and alter the driver and IO)</comment>\n#option option-128 code 128 = string;\n#option option-129 code 129 = text;\n#option option-128 e4:45:74:68:00:00;\n#option option-129 \"NIC=ne IO=0x300\";\n\nshared-network WORKSTATIONS {\n  subnet 192.168.0.0 netmask 255.255.255.0 {\n    <comment>(Distribute dynamic IPs to the workstations)</comment>\n    range dynamic-bootp 192.168.0.1 192.168.0.16;\n    <comment>(Workstation specific configuration for PXE booting)</comment>\n    #host ws001 {\n    #  hardware ethernet     00:E0:06:E8:00:84;\n    #  fixed-address         192.168.0.1;\n    #}\n  }\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):305
+msgid "If your workstations support PXE, you should list each one of them as we have done with <e>host ws001</e> (don't forget to uncomment it). Don't give them an adress in the dynamic range, otherwise it would be possible that more workstations have the same IP (which is troublesome). Remember, if you cut-n-paste the above example, replace any \"//\" comments with \"##\", or else dhcp will fail to start."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):314
+msgid "For more documentation on this item read the official dhcp handbook: <uri>http://www.dhcp-handbook.com/</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):319
+msgid "Now start DHCP as you did with NFS and xinetd:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):323
+msgid "start dhcp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):323
+#, no-wrap
+msgid "\n# <i>rc-update add dhcp default</i>\n# <i>/etc/init.d/dhcp start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(note):328
+msgid "DHCPD needs CONFIG_PACKET and CONFIG_FILTER activated in the kernel to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):335
+msgid "LTSP Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):338
+msgid "There are many options to configure your workstations, visit <uri>http://ltsp.mirrors.tds.net/pub/ltsp/docs/ltsp-4.1-en.html#AEN1190</uri> for a full description of <path>/opt/ltsp/i386/etc/lts.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):344
+msgid "As a few suggestions to get started, you will want to first copy <path>/opt/ltsp/i386/etc/lts.conf.example</path> to <path>/opt/ltsp/i386/etc/lts.conf</path> and edit it from there. You may want to try changing the <c>SCREEN_01</c> option to read <c>SCREEN_01 = startx</c>. To use a USB mouse on the remote client, add the following MODULE lines, and change the X_MOUSE_* lines as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):353
+msgid "/opt/ltsp/i386/etc/lts.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):353
+#, no-wrap
+msgid "\nMODULE_01          = usb-uhci\nMODULE_02          = mousedev\nMODULE_03          = usbmouse\nX_MOUSE_PROTOCOL   = \"IMPS/2\"\nX_MOUSE_DEVICE     = \"/dev/input/mice\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):364
+msgid "Displaymanager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):367
+msgid "Now you have to change your displaymanager's configuration to also accept remote connections."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):372
+msgid "First change your <path>/etc/X11/xdm/Xaccess</path> file, uncomment the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):377
+msgid "/etc/X11/xdm/Xaccess"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):377
+#, no-wrap
+msgid "\n#*                   #any host can get a login window\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):381
+msgid "Now change the configuration of the displaymanager you use:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):385
+msgid "<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out <c>DisplayManager.requestPort: 0</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):390
+msgid "<b>KDM</b>: In <path>/usr/kde/3.1/share/config/kdm/kdmrc</path> look for the <c>[Xdmcp]</c> section and change <c>Enable = false</c> to <c>Enable = true</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):396
+msgid "<b>GDM</b>: In <path>/etc/X11/gdm/gdm.conf</path> look for the <c>[xdmcp]</c> section and change <c>Enable = false</c> to <c>Enable = True</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):402
+msgid "Then start the displaymanager:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):406
+msgid "Starting xdm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):406
+#, no-wrap
+msgid "\n# <i>rc-update add xdm default</i>\n# <i>/etc/init.d/xdm start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(warn):411
+msgid "There seem to be problems currently with XDM and GDM. The author used KDM to resolve these issues."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):416
+msgid "Remember, if your display manager is already running, restarting the X server via CTRL-ALT-BACKSPACE doesn't restart the display manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):424
+msgid "Creating a bootfloppy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):427
+msgid "If your workstations don't support PXE booting, you can create a boot-floppy which is used to start your workstations and connect to the terminal server. Go to <uri>http://www.rom-o-matic.net</uri>, select the latest version, select your NIC, press <e>Get ROM</e> and write the image to a floppy:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):434
+msgid "Write floppy image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):434
+#, no-wrap
+msgid "\n# <i>cat nicfile.zdsk &gt; /dev/fd0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):443
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):447
+msgid "There are a lot of things that can be the source of trouble, but there are also several resources around which help you solve your problems:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):453
+msgid "The official documentation: <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/Documentation</uri>, especially the <uri link=\"http://wiki.ltsp.org/twiki/bin/view/Ltsp/TroubleShooting\"> Troubleshooting section</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):460
+msgid "The gentoo IRC channel: <uri link=\"irc://irc.gentoo.org/gentoo\">#gentoo</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):464
+msgid "The ltsp irc channel: irc.freenode.org #ltsp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):465
+msgid "The ltsp mailinglists <uri>http://marc.info/?l=ltsp-discuss</uri> are full of some real good knowledge."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):476
+msgid "FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):480
+msgid "<b>Q:</b> My workstations have Pentium II CPUs, but my server is compiled with <c>march=athlon-xp</c>, does this work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):485
+msgid "<b>A:</b> This is no problem, because all applications run on the server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):489
+msgid "<b>Q:</b> Which CPU and how much RAM should the server have?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):493
+msgid "<b>A:</b> There is a good document with suggestions at <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):498
+msgid "<b>Q:</b> Do you have more information about this PXE stuff?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):502
+msgid "<b>A:</b> Yes, take a look at <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):507
+msgid "<b>Q:</b> Is it possibly to use 3D-Accelerated software on the workstations?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):511
+msgid "<b>A:</b> If you are using NVidia cards take a look at <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/NvidiaLtsp411</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):516
+msgid "<b>Q:</b> In some applications the fonts look crappy, what to do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):520
+msgid "<b>A:</b> You have to setup the XFontServer, add <c>USE_XFS=Y</c> to your <path>lts.conf</path>, edit <path>/etc/X11/fs/config</path> and comment <c>no-listen: tcp</c> out, replace <c>XFS_PORT=\"-1\"</c> with <c>XFS_PORT=\"7100\"</c> in <path>/etc/conf.d/xfs</path> and start xfs: <c>/etc/init.d/xfs start</c>. Also doublecheck that <path>/etc/X11/XF86Config</path> (or <path>/etc/X11/xorg.conf</path>) contains <c>FontPath \"unix/:7100\"</c> in the Files-section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):530
+msgid "<b>Q: </b> How can I use the soundcard of my workstation?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):534
+msgid "<b>A: </b> There is a ltsp-sound package in gentoo, for more instructions read the included <path>README</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):544
+msgid "Glossary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):548
+msgid "<b><uri link=\"http://www.ltsp.org\">LTSP</uri></b> \"The LTSP provides a simple way to utilize low cost workstations as either graphical or character based terminals on a GNU/Linux server.\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):554
+msgid "<b><uri link=\"http://www.webopedia.com/TERM/P/PXE.html\">PXE</uri></b> \"Short for Pre-Boot Execution Environment. Pronounced pixie, PXE is one of the components of Intel's WfM specification. It allows a workstation to boot from a server on a network prior to booting the operating system on the local hard drive. A PXE-enabled workstation connects its NIC to the LAN via a jumper, which keeps the workstation connected to the network even when the power is off.\""
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/lvm2.xml.pot b/doc/gettext/lvm2.xml.pot
new file mode 100644
index 0000000..ab40982
--- /dev/null
+++ b/doc/gettext/lvm2.xml.pot
@@ -0,0 +1,471 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(guide:link):5
+msgid "/doc/en/lvm2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):6
+msgid "Gentoo LVM2 installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail:link):9
+msgid "avi@CFFtechnologies.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail):9
+msgid "Avi Schwartz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(author:title):11
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail:link):12
+msgid "rajiv@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail):12
+msgid "Rajiv Manglani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail:link):15
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail):15
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(abstract):18
+msgid "This guide describes how to setup your Gentoo machine using the Logical Volume Manager version 2 (LVM2)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(version):27
+msgid "2.7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(date):28
+msgid "2009-02-10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):35
+msgid "This guide is based on an example with two IDE hard disks. It means that you will more than likely need to change the drive, partition names and partition sizes to match your own setup and needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(warn):41
+msgid "This document is not intended to be an LVM2 tutorial. It serves as a supplement to the Gentoo installation procedure as described in the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1\">Handbook, Part 1</uri>. Make sure you <e>read</e> the Gentoo Installation Manual <e>before</e> you start your installation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):49
+msgid "For a complete LVM HOWTO point your browser to <uri>http://tldp.org/HOWTO/LVM-HOWTO</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):57
+msgid "Initial requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):60
+msgid "If you do a fresh install of Gentoo, you will need to use a bootable CD with LVM2 support such as a Gentoo Installation CD. You can find the Installation CDs for an x86 architecture on our <uri link=\"/main/en/mirrors.xml\">mirrors</uri> under <path>/releases/x86/current/installcd</path>. Other architectures might be supported as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):68
+msgid "If you install LVM2 on a currently running system with some spare hard disk space, you will need to enable the LVM2 module (<path>dm-mod</path>). This module is available in <path>gentoo-sources</path>. Compiling your kernel and getting LVM2 to work is covered later in this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):75
+msgid "Not all 2.4 kernels provided by Gentoo support LVM2!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):82
+msgid "Partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):85
+msgid "Our example system has two IDE hard disks and will be partitioned as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):90
+msgid "/dev/hda1 -- /boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):91
+msgid "/dev/hda2 -- (swap)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):92
+msgid "/dev/hda3 -- /"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):93
+msgid "/dev/hda4 -- Will be used by LVM2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):94
+msgid "/dev/hdb1 -- Will be used by LVM2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(impo):97
+msgid "Pay attention to the partition names as it is easy to confuse the a's and b's, and the partition numbers. One false move could wipe out the wrong partition. You have been warned!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):103
+msgid "OK, time to start..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):112
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):116
+msgid "Follow the handbook, but with the following amendments to chapter <e>4. Preparing the Disks</e>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):121
+msgid "Use <c>fdisk</c> as described in the handbook, but use the partition scheme mentioned above as an example. It is only <e>an example</e>, adapt it to your own needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):127
+msgid "Create a small physical <path>/boot</path> partition (hda1). In this example, <path>/boot</path> will be not managed by LVM2. This partition will contain your bootloader and your kernel(s). A 64MB partition should be well enough for quite a few kernel generations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):134
+msgid "Create a swap partition (hda2)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):138
+msgid "Create a / (root) partition (hda3). If you are interested in trying to put your root partition under LVM management (which we do not recommend), see the resources section at the end of this guide for a link to a mini-howto on how to do this. The size of the root partition need not be large if you will keep <path>/opt /usr /home /var</path> and <path>/tmp</path> in an LVM2 Volume Group (vg). In this case, 1GB should be sufficient."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):147
+msgid "It is <b>not</b> recommended to put the following directories in an LVM2 partition: <path>/etc</path>, <path>/lib</path>, <path>/mnt</path>, <path>/proc</path>, <path>/sbin</path>, <path>/dev</path>, and <path>/root</path>. This way, you would still be able to log into your system (crippled, but still somewhat usable, as root) if something goes terribly wrong."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):155
+msgid "Assuming the <path>/boot</path>, swap and root partitions do not use the whole physical disk, create a fourth partition on this disk and set it to type 8e (Linux LVM). If you have more physical drives you would like to use with LVM, create one partition on each and give them the same type (8e)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):162
+msgid "Considering the huge size of current disks, you might consider splitting your hard disks into smaller partitions instead of creating a big partition that will be added to an LVM2 volume group in one block. LVM2 makes it easy to extend your volumes after all. This leaves you some unallocated partitions you might need to use outside of an LVM2 group. In short, don't use your disk space until you know you need it. As an example, one contributor had split his 160&nbsp;Gb hard disk into 8 partitions of 20&nbsp;Gb each."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):172
+msgid "Create the filesystems on <path>/dev/hda1</path> and <path>/dev/hda3</path>, and create and activate the swap on <path>/dev/hda2</path> as described in the handbook."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):178
+msgid "Load the LVM2 <path>dm-mod</path> module."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):182
+msgid "Loading the LVM2 module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):182
+#, no-wrap
+msgid "\n# <i>modprobe dm-mod</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):186
+msgid "Before scanning and activating LVM, you might want to edit <path>/etc/lvm/lvm.conf</path> to exclude some devices. By default, LVM2 will scan all devices, even your CDROM which can generate error messages. In the following example, the line that allows scanning of all devices is replaced by one that rejects every device but our two IDE disks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):194
+msgid "Activating LVM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):194
+#, no-wrap
+msgid "\n<comment>(Avoid scanning all devices but our disks)</comment>\n# <i>nano -w /etc/lvm/lvm.conf</i>\n<comment>(Look for the following line)</comment>\n    filter = [ \"a/.*/\" ]\n<comment>(Replace it with the following one to scan\n/dev/hda and /dev/hdb and reject anything else)</comment>\n    filter = [ \"a|/dev/hd[ab]|\", \"r/.*/\" ]\n<comment>(Save the file and quit nano)</comment>\n# <i>vgscan</i>\n  Reading all physical volumes.  This may take a while...\n  No volume groups found\n<comment>(Make any previously set up volume groups available)</comment>\n# <i>vgchange -a y</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):210
+msgid "Prepare the partitions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):214
+msgid "Preparing the partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):214
+#, no-wrap
+msgid "\n# <i>pvcreate /dev/hda4 /dev/hdb1</i>\n  No physical volume label read from /dev/hda4\n  Physical volume \"/dev/hda4\" successfully created\n  No physical volume label read from /dev/hdb1\n  Physical volume \"/dev/hdb1\" successfully created\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):222
+msgid "Setup a volume group. A volume group is the result of combining several physical units into a single logical device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):227
+msgid "In our example, <path>/dev/hda1</path>, <path>/dev/hda2</path> and <path>/dev/hda3</path> are the <path>/boot</path>, swap and root partitions so we need to combine <path>/dev/hda4</path> and <path>/dev/hdb1</path>. It can be done with a single command, but, as an example, we will create our volume group and extend it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):235
+msgid "Creating and extending a volume group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):235
+#, no-wrap
+msgid "\n<comment>(Create a volume group named vg)</comment>\n# <i>vgcreate vg /dev/hda4</i>\n  /etc/lvm/backup: fsync failed: Invalid argument <comment>(Ignore this warning)</comment>\n  Volume group \"vg\" successfully created\n<comment>(Extending an existing volume group)</comment>\n# <i>vgextend vg /dev/hdb1</i>\n  /etc/lvm/backup: fsync failed: Invalid argument <comment>(Ignore this warning, again and later as well)</comment>\n  Volume group \"vg\" successfully extended\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):246
+msgid "Create the logical volumes. Logical volumes are the equivalent of partitions you would create using fdisk in a non LVM2 environment. In our example, we create the following partitions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(th):254
+msgid "Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(th):255
+msgid "Size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):258
+msgid "/usr"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):259 ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):271
+msgid "10 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):262
+msgid "/home"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):263 ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):267
+msgid "5 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):266
+msgid "/opt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):270
+msgid "/var"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):274
+msgid "/tmp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):275
+msgid "2 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):279
+msgid "Since we are going to use LVM2, we should not worry too much about partition sizes because they can always be expanded as needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):284
+msgid "As Terje Kvernes commented, it is easier to increase the size of a partition then to shrink it. You might therefore want to start with smaller partitions and increase their size as needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):290
+msgid "Creating and extending logical volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):290
+#, no-wrap
+msgid "\n# <i>lvcreate -L10G -nusr  vg</i>\n  Logical volume \"usr\" created <comment>(Further similar messages not displayed)</comment>\n# <i>lvcreate -L5G  -nhome vg</i>\n# <i>lvcreate -L5G  -nopt  vg</i>\n# <i>lvcreate -L10G -nvar  vg</i>\n# <i>lvcreate -L2G  -ntmp  vg</i>\n<comment>(As an example, let's extend a logical volume with 5 extra Gbytes)</comment>\n# <i>lvextend -L+5G /dev/vg/home</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):301
+msgid "Create filesystems on the logical volumes the same way you would on a regular partition. We use ext3 on the logical volumes but any filesystem of your choice will work:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):307
+msgid "Creating the filesystems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):307
+#, no-wrap
+msgid "\n# <i>mke2fs -j /dev/vg/usr</i>\n# <i>mke2fs -j /dev/vg/home</i>\n# <i>mke2fs -j /dev/vg/opt</i>\n# <i>mke2fs -j /dev/vg/var</i>\n# <i>mke2fs -j /dev/vg/tmp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):315
+msgid "Mount your partitions as described in the handbook and mount your LVM2 logical volumes as if they were partitions. Replace the usual <path>/dev/hdxx</path> with <path>/dev/vg/logical_volumename</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):321
+msgid "Mounting your logical volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):321
+#, no-wrap
+msgid "\n<comment>(Make sure you have mounted your root partition as described in the handbook first)</comment>\n# <i>mkdir /mnt/gentoo/usr</i>\n# <i>mount /dev/vg/usr /mnt/gentoo/usr</i>\n# <i>mkdir /mnt/gentoo/home</i>\n# <i>mount /dev/vg/home /mnt/gentoo/home</i>\n# <i>mkdir /mnt/gentoo/opt</i>\n# <i>mount /dev/vg/opt /mnt/gentoo/opt</i>\n# <i>mkdir /mnt/gentoo/var</i>\n# <i>mount /dev/vg/var /mnt/gentoo/var</i>\n# <i>mkdir /mnt/gentoo/tmp</i>\n# <i>mount /dev/vg/tmp /mnt/gentoo/tmp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):335
+msgid "The rest of the installation handbook is mostly unchanged so we shall not walk you through it again except to point out differences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):340
+msgid "When configuring your kernel, make sure to configure your kernel to support LVM2 (not all 2.4 kernels do). Select the LVM2 module as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):345
+msgid "Selecting the LVM2 module in a 2.4.x kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):345
+#, no-wrap
+msgid "\nMulti-device support (RAID and LVM)  ---&gt;\n  [*] Multiple devices driver support (RAID and LVM)\n  &lt; &gt;  RAID support\n<comment>(Note that LVM is not selected on purpose, this was for LVM1)</comment>\n  &lt; &gt;  Logical volume manager (LVM) support\n  &lt;M&gt;  Device-mapper support\n  &lt; &gt;   Mirror (RAID-1) support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):355
+msgid "Selecting the LVM2 module in a 2.6.x kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):355
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n Multi-device support (RAID and LVM)  ---&gt;\n   [*] Multiple devices driver support (RAID and LVM)\n   &lt; &gt;   RAID support\n   &lt;M&gt;   Device mapper support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):363
+msgid "The compiled module is called <path>dm-mod.ko</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):367
+msgid "After you have built your kernel and installed its modules, add the following line to your <path>/etc/modules.autoload.d/kernel-{KV}</path> where {KV} represents your kernel version (2.4 or 2.6) so that the LVM2 module gets loaded when your machine is booted:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):374
+msgid "Adding the LVM2 module into /etc/modules.autoload.d/kernel-2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):374
+#, no-wrap
+msgid "\n# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>\n<comment>(Add the following line)</comment>\ndm-mod\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):380
+msgid "Now, install the lvm2 package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(impo):384
+msgid "Make sure your <path>/usr/src/linux</path> link points to the kernel sources you are using because the lvm2 ebuild depends on the device-mapper ebuild which will check the presence of a required source file under <path>/usr/src/linux/include/linux</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):391
+msgid "Emerging the LVM2 package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):391
+#, no-wrap
+msgid "\n# <i>emerge lvm2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):395
+msgid "Edit <path>/etc/lvm/lvm.conf</path> as described <uri link=\"#doc_chap2_pre2\">earlier</uri>. The file you previously edited is part of your installation environment and will disappear after the next reboot. This time, you edit the real one inside your new Gentoo install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):402
+msgid "When editing your <path>/etc/fstab</path> file, follow the handbook and add your LVM2 logical volumes as needed. Again, here are a few lines needed for our example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):408
+msgid "Extract of /etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):408
+#, no-wrap
+msgid "\n/dev/hda1     /boot   ext3    noauto,noatime 1 2\n/dev/hda2     none    swap    sw             0 0\n/dev/hda3     /       ext3    noatime        0 1\n# Logical volumes\n/dev/vg/usr   /usr    ext3    noatime        0 2\n/dev/vg/home  /home   ext3    noatime        0 2\n/dev/vg/opt   /opt    ext3    noatime        0 2\n/dev/vg/var   /var    ext3    noatime        0 2\n/dev/vg/tmp   /tmp    ext3    noatime        0 2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):420
+msgid "When you reach the end of the installation part of the handbook, don't forget to umount all your LVM2 logical volumes as well and for a good measure run the following command before you reboot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):426
+msgid "Shutting down LVM2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):426
+#, no-wrap
+msgid "\n# <i>vgchange -a n</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):430
+msgid "Restart your machine and all partitions should be visible and mounted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):439
+msgid "Continuing After a Reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):443
+msgid "If you have interrupted the Gentoo installation at one point and want to continue, you need to create the volume device nodes first:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):448 ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):457
+msgid "Reactivating the volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):448
+#, no-wrap
+msgid "\n# <i>vgscan --mknodes</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):452
+msgid "Installation CDs with less recent tools might need to reactivate the volumes instead:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):457
+#, no-wrap
+msgid "\n<comment>(Deactivate all volumes first)</comment>\n# <i>vgchange -a n</i>\n<comment>(Export all the volumes)</comment>\n# <i>vgexport -a</i>\n<comment>(Import all volumes)</comment>\n# <i>vgimport -a</i>\n<comment>(Reactivate all volumes)</comment>\n# <i>vgchange -a y</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):473
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):478
+msgid "The official <uri link=\"http://sources.redhat.com/lvm2\">LVM2 home page</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):481
+msgid "The <uri link=\"http://tldp.org/HOWTO/LVM-HOWTO\">LVM Howto</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):484
+msgid "Daniel Robbins's articles on LVM for IBM's DeveloperWorks: <uri link=\"/doc/en/articles/lvm-p1.xml\">Part 1</uri> and <uri link=\"/doc/en/articles/lvm-p2.xml\">Part 2</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):489
+msgid "How to boot your root FS off of LVM1: <uri>http://www.the-infinite.org/archive/docs/lvm/howto-boot-off-root-lv.txt</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):500
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):504
+msgid "Thanks <mail link=\"bangert@gentoo.org\">Thilo Bangert</mail> and <mail link=\"terjekv@math.uio.no\">Terje Kvernes</mail> for their help and comments on this document."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/lxde-howto.xml.pot b/doc/gettext/lxde-howto.xml.pot
new file mode 100644
index 0000000..2973988
--- /dev/null
+++ b/doc/gettext/lxde-howto.xml.pot
@@ -0,0 +1,234 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):6
+msgid "The LXDE Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(mail:link):9
+msgid "nathanzachary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(mail:link):12
+msgid "yngwin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(abstract):18
+msgid "This guide introduces the user to LXDE, explains its components, and leads the user through the installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(version):27
+msgid "1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(date):28
+msgid "2009-11-30"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):33
+msgid "What is LXDE?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):36
+msgid "After installing your base Gentoo system, and <uri link=\"/doc/en/xorg-config.xml\">the X Server</uri>, you have to make many choices regarding your graphical environment, if you want one at all. There are many options available to you, ranging from minimalistic window managers like <uri link=\"/doc/en/openbox.xml\">Openbox</uri>, to full-featured desktop environments like <uri link=\"/proj/en/desktop/kde/kde-config.xml\"> KDE</uri>, and <uri link=\"/doc/en/gnome-config.xml\">GNOME</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):46
+msgid "You may find yourself saying \"well, I like the idea of having a lightweight graphical environment, but I don't want to install and configure every component individually like with Openbox.\" For quite some time, such users installed <uri link=\"/doc/en/xfce-config.xml\">Xfce</uri>. While it provides a nice full-featured environment without the extensive resource usage of KDE or GNOME, it could still become a bit on the heavy side. Now, you have another choice: the <uri link=\"http://www.lxde.org\">Lightweight X11 Desktop Environment</uri>, or <uri link=\"http://www.lxde.org\">LXDE</uri> for short."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):60
+msgid "Components of LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):63
+msgid "LXDE, being a desktop environment, is comprised of several components. Each program offers a certain functionality, and together they form the complete desktop environment. Currently, there are eleven core components, and several other programs necessary to make a complete LXDE installation. These programs are the ones pulled in by the <uri link=\"http://packages.gentoo.org/package/lxde-base/lxde-meta\">LXDE meta</uri> package, discussed in the installation section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):76
+msgid "Core Components"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):80
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxappearance\">LXappearance</uri> is a GTK theme and icon configurator that allows you to customise the look of LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):86
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxde-common\">LXDE-common</uri> is a collection of default configuration files and the main set of icons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):91
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxmenu-data\">LXmenu-data</uri> is the application menu manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):96
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxinput\">LXinput</uri> is a keyboard and mouse configurator"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):101
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxpanel\">LXpanel</uri> is the panel that includes the application menu, system tray, and clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):106
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxrandr\">LXrandr</uri> is a graphical interface to X Resize and Rotate, allowing for display manipulation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):112
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxsession\">LXsession</uri> is a session manager, providing options to shutdown, reboot, and suspend the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):118
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxsession-edit\"> LXsession-edit</uri> allows you to enable/disable applications at startup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):122
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxshortcut\">LXshortcut</uri> is an easy way to edit application shortcuts, especially for desktop icons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):127
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxtask\">LXtask</uri> is the task manager used to view/edit running services and programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):131
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxterminal\">LXterminal</uri> is the vte-based tabbed terminal emulator"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):141
+msgid "Other Applications used by LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):145
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-wm/openbox\">OpenBox</uri> is the window manager, responsible for drawing the containers for programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):150
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/pcmanfm\">PCManFM</uri> is the incredibly fast, tabbed file manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):155
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/obconf\">ObConf</uri> is the configurator for OpenBox, allowing you to change window decorations and more"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):161
+msgid "<uri link=\"http://packages.gentoo.org/package/media-gfx/gpicview\">GPicView </uri> is the default image viewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):172
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):174
+msgid "Initial installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):177
+msgid "After you have emerged and configured <uri link=\"/doc/en/xorg-config\">xorg-server</uri>, you are ready to install LXDE. While you may install each component individually, the more efficient and preferred method is to emerge the meta package set:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(pre:caption):184
+msgid "Installing LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(pre):184
+#, no-wrap
+msgid "\n# <i>emerge -av lxde-meta</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):188
+msgid "If everything looks to your liking (meaning the current set of USE flags, etc.), then say \"yes\" when asked if you want to emerge the packages. Just like with other desktop environments, you will need to tell the X Server to load LXDE automatically, by adding it to your <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(pre:caption):196
+msgid "Adding LXDE to your .xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(pre):196
+#, no-wrap
+msgid "\n$ <i>echo \"exec startlxde\" &gt;&gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):200
+msgid "This will automatically start your LXDE session when you type <c>startx</c> at the console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(note):205
+msgid "If you use a login manager like SLiM, XDM, GDM, or KDM, you do not need to edit your <path>~/.xinitrc</path>. LXDE will simply show up as a choice in your login manager's screen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(impo):211
+msgid "As each user has his or her own <path>.xinitrc</path>, you need to make sure to issue that command as <e>your user</e>, not as root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):221
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):223
+msgid "GTK icon warning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):226
+msgid "Now that the X server knows to start LXDE on command, type in <c>startx</c> to fire up LXDE. The first thing you may notice is that you get a warning about an improper GTK icon set. To fix this minor hangup, you simply need to change the icon theme. To do so, click on the LXDE application menu (in the lower left-hand corner of the panel), and go to Preferences --&gt; Appearance. In the LXappearance menu, click on the \"Icon\" tab, and choose nuoveXT.2.2. Hit \"Apply,\" and then \"Close.\" The next time you login to LXDE, the error message will not appear. However, you are not limited to using the nuoveXT.2.2 icon theme. You may install any other icon theme through LXappearance, and when it is selected, the GTK icon warning will no longer appear when starting PCManFM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):242
+msgid "Right-click menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):245
+msgid "In LXDE, every appearance option is not handled through LXappearance as one might believe. Rather, there are some common options that are handled through a right-click menu on the desktop. At the bottom of that menu is the \"Desktop Settings\" menu. In here, you can find icon sizes, single-click and double-click behavior, maximum thumbnail size, and desktop wallpaper settings. It may behoove you to look through the these tabs for additional appearance settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(note):255
+msgid "These \"Desktop Settings\" can also be found by opening up the file manager (PCManFM), and going to Edit --&gt; Preferences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):265
+msgid "Further documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):267
+msgid "External resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):270
+msgid "Though this guide will help you get LXDE installed, the documentation does not stop here. There are many resources available to you regarding the various facets of the Lightweight X11 Desktop Environment. Some such resources are listed below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):278
+msgid "On the <uri link=\"http://www.lxde.org\">Official LXDE website</uri> you will find information regarding developmental progress, a community of support, and recommend system specifications for running LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):283
+msgid "The <uri link=\"http://wiki.lxde.org/en/Main_Page\">LXDE wiki</uri> contains instructions for customising your LXDE installation, including keyboard layouts, autostarting applications, changing the default window manager, and much more"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/macos-guide.xml.pot b/doc/gettext/macos-guide.xml.pot
new file mode 100644
index 0000000..a9d87af
--- /dev/null
+++ b/doc/gettext/macos-guide.xml.pot
@@ -0,0 +1,60 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(guide:link):6
+msgid "/doc/en/macos-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(guide:redirect):6
+msgid "/proj/en/gentoo-alt/macos/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(title):8
+msgid "Gentoo For Mac OS X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(mail:link):11
+msgid "ppc-macos@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(mail):11
+msgid "PPC MacOS Team"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(abstract):14
+msgid "This guide has been removed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(version):22
+msgid "2.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(date):23
+msgid "2005-11-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(title):26
+msgid "Notice"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(p):30
+msgid "This guide has been removed. Please check the <uri link=\"/proj/en/gentoo-alt/macos/\">Portage for Darwin/Mac OS X</uri> project page for more information."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/mailfilter-guide.xml.pot b/doc/gettext/mailfilter-guide.xml.pot
new file mode 100644
index 0000000..1280b00
--- /dev/null
+++ b/doc/gettext/mailfilter-guide.xml.pot
@@ -0,0 +1,1620 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(guide:link):6
+msgid "/doc/en/mailfilter-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):7
+msgid "Gentoo mailfiltering gateway guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail:link):10
+msgid "jaervosz@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail):10
+msgid "Sune Kloppenborg Jeppesen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(author:title):12
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail:link):13
+msgid "gentoo@hilli.dk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail):13
+msgid "Jens Hilligsøe"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(author:title):15
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail:link):16
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail):16
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(abstract):19
+msgid "This guide is step-by-step guide for installing spam fighting technologies for Postfix. Among them Amavisd-new using Spamassassin and ClamAV, greylisting and SPF."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(version):29
+msgid "0.14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(date):30
+msgid "2007-08-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):33 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1296 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1521
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):37
+msgid "This guide describe step by step how to install a spam and virus filtering mail gateway. It is quite simple to adopt this to a single server solution."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):45
+msgid "The big picture"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):48
+msgid "This document describe how to setup a spam filtering mail gateway with multiple domains. This server is meant to run in front of the mail servers actually keeping the mail accounts i.e. Microsoft Exchange or Lotus Notes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):55
+msgid "In this setup applications with good security records and readable configuration files have been chosen. The email MTA is postfix which has a good security record and is fairly easy to setup right. Postfix will listen normally on port 25 for incoming mail. Upon reception it will forward it to Amavisd-new on port 10024. Amavisd-new will then filter the mail through different filters before passing the mail back to Postfix on port 10025 which in turn will forward the mail to the next mail server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):65
+msgid "Amavisd-new is a content filtering framework utilizing helper applications for virus filtering and spam filtering. In this setup we will be using two helper applications one ClamAV for filtering virus mails and Spamassassin for filtering spam. Spamassassin itself can function as yet another layer of content filtering framework and utilize the helper applications Vipul's Razor2 and DCC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):73
+msgid "Unlike many other spam fighting technologies like RBLs and others Spamassassin does not simply accept or reject a given email based on one single test. It uses a lot of internal tests and external helper applications to calculate a spam score for every mail passed through. This score is based on the following tests:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):81
+msgid "Bayesian filtering"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):82
+msgid "Static rules based on regular expressions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):85
+msgid "RBLs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):86
+msgid "Razor2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):87 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2106
+msgid "Pyzor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):88 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):236
+msgid "DCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):83
+msgid "Distributed and collaborative networks: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):93
+msgid "The first part (chapters 1 to 4) of the guide will describe the basic setup of a mailfiltering gateway. The next chapters can be implemented individually with no dependence between each chapter. These chapters describe how to:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):100
+msgid "setup special IMAP folders for learning of the Bayesian filter and for delivery of false positives"
+msgstr ""
+
+#. <li>setup log analyzers to create daily reports</li>
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):107
+msgid "setup greylisting with Postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):108
+msgid "setup Amavisd-new to use a MySQL backend for user preferences"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):109
+msgid "setup Spamassassin to use a MySQL backend for AWL and Bayes data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):112
+msgid "The IMAP folders will be using the maildir format. Having each mail in a separate file makes handling much simpler. If you're using mbox I propose to give maildir a try. If you're not already using maildir emerge the necessary tools with <c>emerge courier-imap</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):119
+msgid "A planned fifth part will contain various tips regarding performance and things you may want to know (running chrooted, postfix restrictions, etc.)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):124
+msgid "Delegating responsibility to third parties is not without risks. You have to know and trust these third parties. In this setup only the decision to quarantine virus mails are based on a single third party. Using Spamassassin's scoring system the decision to stop spam mails are not made by a single authority except perhaps Spamassassins own static rules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):132
+msgid "When rejecting spam mails at the MTA level you have to be very careful when selecting the RBL's you want to use, i.e. SpamCop is a bad RBL to use at the MTA level because you will experience false positives because sometimes their listing is just too aggressive. Further info at <uri link=\"http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?UNIX03/Realtime_Blackhole_Lists_Are_Bad\">Realtime Blackhole Lists Are Bad</uri> and <uri link=\"http://theory.whirlycott.com/~phil/antispam/rbl-bad/rbl-bad.html\">The Spam Problem: Moving Beyond RBLs</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):146 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1572
+msgid "Preparations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):149
+msgid "Before you start make sure that you have a working Postfix installation where you can send and receive mails also you need a backend mailserver. If you're not experienced with setting up Postfix it might quickly become too complicated if all should be set up at once. If you need help you can find it in the excellent <uri link=\"http://www.gentoo.org/doc/en/virt-mail-howto.xml\">Virtual Mailhosting System with Postfix Guide</uri> in the Gentoo Documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):163
+msgid "Installing the programs needed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):167
+msgid "We start out by installing the most important programs: Amavisd-new, Spamassassin and ClamAV."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):172
+msgid "Installing Amavis, Spamassassin and Clamav"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):172
+#, no-wrap
+msgid "\n# <i>emerge amavisd-new spamassassin clamav </i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):176
+msgid "As previously mentioned you should already have a working <c>postfix</c> instance running on the box. Basically this shouldn't be much more than <c>emerge postfix</c><e>and</e> have a basic understanding of how Postfix is working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):186 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):204
+msgid "Setting up DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):189
+msgid "If you're not setting up a gateway server but have the mailboxes on the same server you only have to create the MX-Record."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):194
+msgid "While the programs are emerging fire up another shell and create the needed DNS records."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):199
+msgid "Start out by creating a <c>MX</c> record for the mail gateway and an <c>A</c> record for the next destination."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):204
+#, no-wrap
+msgid "\n<comment>(Create a MX record for the gateway server)</comment>\n                MX      10      mailgateway.mydomain.tld.\n<comment>(Create an A record for the gateway server)</comment>\nmailgateway     A       mgw.ip.add.here\n<comment>(Create an A record for the next hop mail server)</comment>\nmail            A       ms.ip.add.here\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):213
+msgid "Some ADSL providers might block port 25 and force you to relay mail through one of their servers. Typically you have to create a secondary MX-Record like <c>MX 20 backup-mx.some-isp.tld</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):222
+msgid "Opening the firewall"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):225
+msgid "In addition to allowing normal mail traffic you have to allow a few services through your firewall to allow the network checks to communicate with the servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(th):233
+msgid "Application"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(th):233
+msgid "Protocol"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(th):233
+msgid "Port"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):236
+msgid "UDP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):236
+msgid "6277"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):239
+msgid "Razor(outgoing ping)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):239 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):242
+msgid "TCP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):239
+msgid "7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):242
+msgid "Razor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):242
+msgid "2703"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):246
+msgid "Razor uses pings to discover what servers are closest to it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):253
+msgid "Configuring Postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):256
+msgid "First we have to tell <c>postfix</c> to listen on port 10025 and we remove most of the restrictions as they have already been applied by the <c>postfix</c> instance listening on port 25. Also we ensure that it will only listen for local connections on port 10025. To accomplish this we have to add the following at the end of <path>/etc/postfix/master.cf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):264
+msgid "Changing the master.cf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):264
+#, no-wrap
+msgid "\nsmtp-amavis     unix -        -       n     -       2  smtp\n  -o smtp_data_done_timeout=1200\n  -o smtp_send_xforward_command=yes\n<comment>#Equivalently when using lmtp:\n#lmtp-amavis    unix -        -       n     -       2  lmtp\n#   -o lmtp_data_done_timeout=1200\n#   -o lmtp_send_xforward_command=yes</comment>\n\n127.0.0.1:10025 inet n        -       n     -       -  smtpd\n  -o content_filter=\n  -o local_recipient_maps=\n  -o relay_recipient_maps=\n  -o smtpd_restriction_classes=\n  -o smtpd_client_restrictions=\n  -o smtpd_helo_restrictions=\n  -o smtpd_sender_restrictions=\n  -o smtpd_recipient_restrictions=permit_mynetworks,reject\n  -o mynetworks=127.0.0.0/8\n  -o strict_rfc821_envelopes=yes\n  -o smtpd_error_sleep_time=0\n  -o smtpd_soft_error_limit=1001\n  -o smtpd_hard_error_limit=1000\n\n<comment>#If you want to use proxy filtering instead\n#smtp            inet n         -       n      -       8 smtpd\n# -o smtpd_proxy_filter=127.0.0.1:10024\n# -o smtpd_client_connection_count_limit=4\n#If you don't want to scan outgoing mail use this\n#10.0.0.2:smtp   inet n         -       n       -      - smtpd\n#-o content_filter=</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):297
+msgid "The <c>smtp-amavis</c> line specifies that a maximum of two of these processes may run at any time. If you need a greater degree of concurrency tune this number to fit your needs. Remember that to match the number with <c>$max_servers</c> in <path>amavisd.conf</path>. Keep in mind that <c>amavisd-new</c> is quite memory-intensive and raising the amount of <c>amavisd-new</c> processes too high can easily lead to memory starvation and heavy swapping, which leads to drastically reduced performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):307
+msgid "If you want to reject spam early on in the process you can use the Before-Queue (proxy) method instead of the filter method. If you uncomment the three lines you will have to set <c>content_filter=</c> in <path>main.cf</path>. This is not recommended for high traffic servers as the number of concurrent connections are limited to the number of amavisd instances."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):316
+msgid "The Before-Queue(proxy) method is still not properly tested."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):320
+msgid "If you, for any reason whatsoever, want to send mail from this box and don't want it scanned, add another postfix instance by uncommenting the last two lines and substitute with a proper IP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):326
+msgid "The file <path>master.cf</path> tells the postfix master program how to run each individual postfix process. More info with <c>man 8 master</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):332
+msgid "Next we need the main <c>postfix</c> instance listening on port 25 to filter the mail through <c>amavisd-new</c> listening on port 10024."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):337
+msgid "We also need to set the next hop destination for mail. Tell Postfix to filter all mail through an external content filter and enable explicit routing to let Postfix know where to forward the mail to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):343 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):985
+msgid "Modifying /etc/postfix/main.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):343
+#, no-wrap
+msgid "\nbiff = no\nempty_address_recipient = MAILER-DAEMON\nqueue_minfree = 120000000\n\ncontent_filter = smtp-amavis:[127.0.0.1]:10024\n<comment>#Equivalently when using lmtp:\n#content_filter = lmtp-amavis:[127.0.0.1]:10024\n\n# TRANSPORT MAP\n#\n# Insert text from sample-transport.cf if you need explicit routing.</comment>\ntransport_maps = hash:/etc/postfix/transport\n\nrelay_domains = $transport_maps\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):360
+msgid "Postfix has a lot of options set in <path>main.cf</path>. For further explanation of the file please consult <c>man 5 postconf</c> or the same online <uri link=\"http://www.postfix.org/postconf.5.html\">Postfix Configuration Parameters</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):367
+msgid "The format of the <path>transport</path> file is the normal Postfix hash file. Mail to the domain on the left hand side is forwarded to the destination on the right hand side."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):373
+msgid "/etc/postfix/transport"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):373
+#, no-wrap
+msgid "\nmydomain.tld                          smtp:mail.mydomain.tld\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):377
+msgid "After we have edited the file we need to run the <c>postmap</c> command. Postfix does not actually read this file so we have to convert it to the proper format with <c>postmap /etc/postfix/transport</c>. This creates the file <path>/etc/postfix/transport.db</path>. There is no need to reload Postfix as it will automatically pick up the changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):385
+msgid "If the next hop mail server is not listening on the standard SMTP port 25 you can tell postfix to use a given port number, like <c>smtp:mail.mydomain.tld:25000</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):391
+msgid "If your first attempts to send mail result in messages bouncing, you've likely made a configuration error somewhere. Try temporarily enabling <c>soft_bounce</c> while you work out your configuration issues. This prevents postfix from bouncing mails on delivery errors by treating them as temporary errors. It keeps mails in the mail queue until <c>soft_bounce</c> is disabled or removed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):400
+msgid "Enabling soft_bounce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):400
+#, no-wrap
+msgid "\n# <i>postconf -e \"soft_bounce = yes\"</i>\n# <i>/etc/init.d/postfix reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):405
+msgid "Once you've finished creating a working configuration, be sure to disable or remove <c>soft_bounce</c> and reload postfix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):413
+msgid "Configuring Amavisd-new"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):416
+msgid "Amavisd-new is used to handle all the filtering and allows you to easily glue together severel different technologies. Upon reception of a mail message it will extract the mail, filter it through some custom filters, handle white and black listing, filter the mail through various virus scanners and finally it will filter the mail using SpamAssassin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):424
+msgid "Amavisd-new itself has a number of extra features:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):429
+msgid "it identifies dangerous file attachments and has policies to handle them"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):435
+msgid "whitelists"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):436
+msgid "blacklists"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):437
+msgid "spam score thresholds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):438
+msgid "virus and spam policies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):432
+msgid "per-user, per-domain and system-wide policies for: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):443
+msgid "Apart from <c>postfix</c> and <c>freshclam</c> we will run all applications as the user <c>amavis</c>."
+msgstr ""
+
+#. <p>
+#. Create the new home directory and set the proper permissions.
+#. </p>
+#. 
+#. <pre caption="Create the new home directory and set the proper permissions">
+#. # <i>mkdir /var/amavis</i>
+#. # <i>chown amavis:amavis /var/amavis</i>
+#. # <i>chmod 750 /var/amavis</i>
+#. </pre>
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):466
+msgid "Edit the following lines in <path>/etc/amavisd.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):470
+msgid "Editing /etc/amavisd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):470
+#, no-wrap
+msgid "\n<comment>(Insert the domains to be scanned)</comment>\n$mydomain = 'example.com';\n<comment>(Bind only to loopback interface)</comment>\n$inet_socket_bind = '127.0.0.1';\n<comment>(Forward to Postfix on port 10025)</comment>\n$forward_method = 'smtp:127.0.0.1:10025';\n$notify_method = $forward_method;\n<comment>(Define the account to send virus alert emails)</comment>\n$virus_admin = \"virusalert\\@$mydomain\";\n<comment>(Always add spam headers)</comment>\n$sa_tag_level_deflt  = -100;\n<comment>(Add spam detected header aka X-Spam-Status: Yes)</comment>\n$sa_tag2_level_deflt = 5;\n<comment>(Trigger evasive action at this spam level)</comment>\n$sa_kill_level_deflt = $sa_tag2_level_deflt;\n<comment>(Do not send delivery status notification to sender.  It does not affect\ndelivery of spam to recipient. To do that, use the kill_level)</comment>\n$sa_dsn_cutoff_level = 10;\n<comment>Don't bounce messages left and right, quarantine\ninstead</comment>\n$final_virus_destiny      = D_DISCARD;  # (defaults to D_DISCARD)\n$final_banned_destiny     = D_DISCARD;  # (defaults to D_BOUNCE)\n$final_spam_destiny       = D_DISCARD;  # (defaults to D_BOUNCE)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):496
+msgid "With this line <c>$sa_tag2_level_deflt = 5;</c> you set the Spamassassin spam score to 5. This might be a bit low. As you might have noticed the Amavisd-new default is <c>6.3</c>. If you don't want to see a single spam mail in your mail folder choose <c>5</c>, but if you don't want to deal with false positives choose <c>6.3</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):504
+msgid "Create a quarantine directory for the virus mails as we don't want these delivered to our users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):509
+msgid "Create a quarantine directory for the virus mails"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):509
+#, no-wrap
+msgid "\n# <i>mkdir /var/amavis/virusmails</i>\n# <i>chown amavis:amavis /var/amavis/virusmails</i>\n# <i>chmod 750 /var/amavis/virusmails</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):515
+msgid "Amavisd-new offers finer policy tuning by using policy banks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):522
+msgid "Configuring ClamAV"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):525
+msgid "As virus scanner we use ClamAV as it has a fine detection rate comparable with commercial offerings, it is very fast and it is Open Source Software. We love log files, so make <c>clamd</c> log using <c>syslog</c> and turn on verbose logging. Also do not run <c>clamd</c> as <c>root</c>. Now edit <path>/etc/clamd.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):533
+msgid "Edit /etc/clamd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):533
+#, no-wrap
+msgid "\n<comment>(Verbose logging with syslog)</comment>\nLogSyslog\nLogVerbose\nLogFacility LOG_MAIL\n<comment>(Change pid file location)</comment>\nPidFile /var/run/amavis/clamd.pid\n<comment>(Set the clamav socket)</comment>\nLocalSocket /var/amavis/clamd\n<comment>(Close the connection when this limit is exceeded)</comment>\nStreamMaxLength 10M\n<comment>(Don't run clamd as root)</comment>\nUser amavis\n<comment>(Newer versions require you to uncomment this)</comment>\nScanMail\nScanArchive\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):551
+msgid "Also remember to remove the Example directive to make ClamAV work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):555
+msgid "ClamAV comes with the <c>freshclam</c> deamon dedicated to periodical checks of virus signature updates. Instead of updating virus signatures twice a day we will make <c>freshclam</c> update virus signatures every two hours."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):561
+msgid "Edit /etc/freshclam.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):561
+#, no-wrap
+msgid "\n<comment>(Syslog logging)</comment>\nLogSyslog\n<comment>(Verbose logging)</comment>\nLogVerbose\n<comment>(Explicitly drop root privileges)</comment>\nDatabaseOwner clamav\n<comment>(Check for updates every two hours. That is the official recommendation)</comment>\nChecks 12\n<comment>(Use the mirror closest to you. Replace XY with your country code</comment>\nDatabaseMirror db.XY.clamav.net\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):574
+msgid "Start <c>clamd</c> with <c>freshclam</c> using the init scripts by modifying <path>/etc/conf.d/clamd</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):579
+msgid "Modifying /etc/conf.d/clamd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):579
+#, no-wrap
+msgid "\nSTART_CLAMD=yes\nFRESHCLAM_OPTS=\"-d\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):584
+msgid "At last modify <path>amavisd.conf</path> with the new location of the socket."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):589 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1087
+msgid "Modifying /etc/amavisd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):589
+#, no-wrap
+msgid "\n<comment>(Uncomment the clamav scanner and modify socket location)</comment>\n['ClamAV-clamd',\n\\&amp;ask_daemon, [\"CONTSCAN {}\\n\", \"/var/amavis/clamd\"],\n  qr/\\bOK$/, qr/\\bFOUND$/,\n  qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ],\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):597
+msgid "Do NOT modify the <c>$unix_socketname</c> unless you know what you're doing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):604
+msgid "Configuring Vipul's Razor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):607
+msgid "Razor2 is a collaborative and distributed spam checksum network. Install it with <c>emerge razor</c> and create the needed configuration files. Do this as user <c>amavis</c> by running <c>su - amavis</c> followed <c>razor-admin -create</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):614
+msgid "Creating the required configuration files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):614
+#, no-wrap
+msgid "\n# <i>emerge razor</i>\n\n<comment>(Temporarily set amavis' shell to bash)</comment>\n# <i>usermod -s /bin/bash amavis</i>\n# <i>su - amavis</i>\n$ <i>razor-admin -create</i>\n$ <i>exit</i>\n\n<comment>(Reset the shell to /bin/false)</comment>\n# <i>usermod -s /bin/false amavis</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):630
+msgid "Configuring Distributed Checksum Clearinghouse (dcc)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):633
+msgid "Like Razor2, dcc is a collaborative and distributed spam checksum network. Its philosopy is to count the number of recipients of a given mail identifying each mail with a fuzzy checksum."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):639
+msgid "Installing DCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):639
+#, no-wrap
+msgid "\n# <i>emerge dcc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):646
+msgid "Configuring Spamassassin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):649
+msgid "Amavis is using the Spamassassin Perl libraries directly so there is no need to start the service. Also this creates some confusion about the configuration as some Spamassassin settings are configured in <path>/etc/mail/spamassassin/local.cf</path> and overridden by options in <path>/etc/amavisd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):657
+msgid "Create /etc/mail/spamassassin/local.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):657
+#, no-wrap
+msgid "\n<comment># Enable the Bayes system</comment>\nuse_bayes               1\n\n<comment># Enable all network checks</comment>\nskip_rbl_checks         0\n\n<comment># Mail using languages used in these country codes will not be marked\n# as being possibly spam in a foreign language.\n# - danish english norwegian swedish</comment>\nok_languages            da en no sv\n\n<comment># Mail using locales used in these country codes will not be marked\n# as being possibly spam in a foreign language.</comment>\nok_locales              en\n\n<comment># Use a sensible bayes path</comment>\nbayes_path              /var/amavis/.spamassassin/bayes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):677
+msgid "With Spamassassin version 3.1 you have to enable DCC, Razor2 by uncommenting the corresponding lines in <path>v310.pre</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):682
+msgid "You can find inspiration for your <path>local.cf</path> file by trying the <uri link=\"http://www.yrex.com/spam/spamconfig.php\">SpamAssassin Configuration Generator</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):688
+msgid "You might also want to switch the <c>ok_languages</c> and <c>ok_locales</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):697
+msgid "Every good rule has good exceptions as well"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):701
+msgid "Once mail really starts passing through this mail gateway you will probably discover that the above setup is not perfect. Maybe some of your customers like to receive mails that others wouldn't. You can whitelist/blacklist envelope senders quite easily. Uncomment the following line in <path>amavisd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):709
+msgid "Modifying amavisd.conf to do sitewide scoring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):709
+#, no-wrap
+msgid "\nread_hash(\"/var/amavis/sender_scores_sitewide\"),\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):713
+msgid "In the <path>sender_scores_sitewide</path> file you put complete email addresses or just the domian parts and then note a positive/negative score to add to the spam score."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):719
+msgid "whitelist_sender example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):719
+#, no-wrap
+msgid "\n<comment>(Whitelist all emails from the specific email address)</comment>\npostmaster@example.net                -3.0\n<comment>(Whitelist all emails from the example.net excluding subdomains)</comment>\n.example.net                          1.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):726
+msgid "See <path>/etc/amavisd.conf</path> for more examples."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):730
+msgid "Placing these addresses outside <path>amavisd.conf</path> is a cleaner and safer solution."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):735
+msgid "Alternatively it can be done in Spamassassin's configuration file <path>/etc/mail/spamassassin/local.cf</path> but I think it is cleaner to do it in <path>/etc/amavisd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):741
+msgid "In a later chapter I will show how to implement per-user policies using MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):746
+msgid "While waiting for a better method you can add the following to <path>amavisd.conf</path> to bypass spam checks for <c>postmaster</c> and <c>abuse</c> mailboxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):752
+msgid "By pass spam filters for all postmaster and abuse mails"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):752
+#, no-wrap
+msgid "\nmap { $bypass_spam_checks{lc($_)}=1 } (qw(\n        postmaster@\n        abuse@\n));\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(impo):759
+msgid "While we are at it we should <e>never</e> automatically discard mails to the <c>postmaster</c> or the <c>abuse</c> accounts. See <uri link=\"http://www.ietf.org/rfc/rfc2142.txt\">RFC 2142 MAILBOX NAMES FOR COMMON SERVICES, ROLES AND FUNCTIONS</uri>. Otherwise your domains might end up listed in some of the evil lists over at <uri link=\"http://www.rfc-ignorant.org/\">rfc-ignorant.org</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):773
+msgid "Adding more rules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):777
+msgid "If you want to use more rules provided by the SARE Ninjas over at the <uri link=\"http://www.rulesemporium.com/\">SpamAssassin Rules Emporium</uri> you can easily add and update them using the <c>sa-update</c> mechanism included in Spamassassin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):784
+msgid "A brief guide to using SARE rulesets with <c>sa-update</c> can be found <uri link=\"http://daryl.dostech.ca/sa-update/sare/sare-sa-update-howto.txt\">here</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):794
+msgid "Testing and finishing up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):796
+msgid "Testing the setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):799
+msgid "Now before you start <c>freshclam</c> you can manually verify that it works."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):803
+msgid "Testing freshclam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):803
+#, no-wrap
+msgid "\n# <i>freshclam</i>\nClamAV update process started at Sun May  2 09:13:41 2004\nReading CVD header (main.cvd): OK\nDownloading main.cvd [*]\nmain.cvd updated (version: 22, sigs: 20229, f-level: 1, builder: tkojm)\nReading CVD header (daily.cvd): OK\nDownloading daily.cvd [*]\ndaily.cvd updated (version: 298, sigs: 1141, f-level: 2, builder: diego)\nDatabase updated (21370 signatures) from database.clamav.net (193.1.219.100).\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):815
+msgid "Now you have updated virus definitions and you know that <path>freshclam.conf</path> is working properly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):820
+msgid "Test freshclam and amavisd from the cli and amavisd testmails. Start <c>clamd</c> and <c>amavis</c> with the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):825
+msgid "Start amavisd and clamd and reload postfix configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):825
+#, no-wrap
+msgid "\n# <i>/etc/init.d/clamd start</i>\n# <i>/etc/init.d/amavisd start</i>\n# <i>/etc/init.d/postfix reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):831
+msgid "If everything went well <c>postfix</c> should now be listening for mails on port 25 and for reinjected mails on port 10024. To verify this check your log file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):836
+msgid "Checking log files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):836
+#, no-wrap
+msgid "\n# <i>tail -f /var/log/mail.log</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):840
+msgid "Depending on your log settings the correct path might be <path>/var/log/messages</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):845
+msgid "Now if no strange messages appear in the log file it is time for a new test."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):850
+msgid "Use <c>netcat</c> to manually connect to <c>amavisd</c> on port 10024 and <c>postfix</c> on port 10025."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):855
+msgid "Netcat can be used as an advanced replacement for <c>telnet</c>. Install it with <c>emerge netcat</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):860
+msgid "For some unknown reason you can not complete a manual mail injection to <c>amavisd</c> with netcat. Use <c>telnet</c> instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):865
+msgid "Manually checking that amavisd and postfix are listning to the new ports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):865
+#, no-wrap
+msgid "\n# <i>nc localhost 10024</i>\n<comment>(Amavis working)</comment>\n220 [127.0.0.1] ESMTP amavisd-new service ready\n<i>nc localhost 10025</i>\n<comment>(Postfix reinject working)</comment>\n220 example.com ESMTP Postfix\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):874
+msgid "If you want to see the complete output from amavisd-new start <c>amavisd debug-sa</c> as the <c>amavis</c> user and send a mail. For this to work you might have to change the default shell in <path>/etc/passwd</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):881
+msgid "Add <c>amavisd</c> and <c>clamd</c> to the <c>default</c> runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):885
+msgid "Add amavisd and clamd to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):885
+#, no-wrap
+msgid "\n# <i>rc-update add clamd default</i>\n# <i>rc-update add amavisd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):890
+msgid "We do not add <c>spamd</c> to the default runlevel as <c>amavisd</c> uses the Spamassassin Perl libraries directly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):895
+msgid "You might notice <c>Net::Server: Couldn't POSIX::setuid to ... []</c> lines in your log. According to <uri link=\"http://www.ijs.si/software/amavisd/README.chroot\">amavis chroot README</uri>, if the process UID remains 0 (<c>root</c>), the program will terminate, otherwise you can consider the message just as informative. This is because <c>POSIX::setuid()</c> returns a string <c>0 but true</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(impo):905
+msgid "If you enabled login for amavis remember to set back the login shell in <path>/etc/passwd</path> to <c>/bin/false</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):915
+msgid "Autolearning and sidelining emails"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):917
+msgid "Creating the spamtrap user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):920
+msgid "Create the spamtrap account and directories."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):924
+msgid "Create spamtrap account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):924
+#, no-wrap
+msgid "\n# <i>useradd -m spamtrap</i>\n# <i>maildirmake /home/spamtrap/.maildir</i>\n# <i>chown -R spamtrap:mailusers /home/spamtrap/.maildir</i>\n<comment>(Give the spamtrap user a sensible password)</comment>\n# <i>passwd spamtrap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):932
+msgid "If you manually want to check some of the mails to ensure that you have no false positives you can use the following <c>procmail</c> recipe to sideline spam found into different mail folders."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):941
+msgid "Creating .procmailrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):944
+msgid "Creating /home/spamtrap/.procmailrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):944
+#, no-wrap
+msgid "\n<comment>#Set some default variables</comment>\nMAILDIR=$HOME/.maildir\n\nSPAM_FOLDER=$MAILDIR/.spam-found/\n\nLIKELY_SPAM_FOLDER=$MAILDIR/.likely-spam-found/\n\n<comment>#Sort mails with a spamscore of 7+ to the spamfolder</comment>\n:0:\n* ^X-Spam-Status: Yes\n* ^X-Spam-Level: \\*\\*\\*\\*\\*\\*\\*\n$SPAM_FOLDER\n\n<comment>#Sort mail with a spamscore between 5-7 to the likely spam folder</comment>\n:0:\n* ^X-Spam-Status: Yes\n$LIKELY_SPAM_FOLDER\n\n<comment>#Sort all other mails to the inbox</comment>\n:0\n*\n./\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):969
+msgid "If your mail server is going to receive a lot of mail you should NOT use the likely-spam recipe. Instead set <c>$sa_tag2_level_deflt</c> high enough to avoid false positives and filter it directly to <c>$SPAM_FOLDER</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):976
+msgid "If you haven't already installed <c>procmail</c> do it with <c>emerge procmail</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):981
+msgid "Now make sure that Postfix uses <c>procmail</c> to deliver mail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):985
+#, no-wrap
+msgid "\nmailbox_command = /usr/bin/procmail -a \"DOMAIN\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):992
+msgid "Create mailfolders"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):995
+msgid "Now we will create shared folders for ham and spam."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):999
+msgid "Create the necessary mailfolders"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):999
+#, no-wrap
+msgid "\n# <i>maildirmake /var/amavis/.maildir</i>\n# <i>maildirmake -S /var/amavis/.maildir/Bayes</i>\n# <i>maildirmake -s write -f spam /var/amavis/.maildir/Bayes</i>\n# <i>maildirmake -s write -f ham /var/amavis/.maildir/Bayes</i>\n# <i>maildirmake -s write -f redeliver /var/amavis/.maildir/Bayes</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1007
+msgid "Amavisd-new needs to be able to read these files as well as all mailusers. Therefore we add all the relevant users to the mailuser group along with amavis."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1012
+msgid "Setting the proper permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1012
+#, no-wrap
+msgid "\n# <i>groupadd mailusers</i>\n# <i>usermod -G mailusers spamtrap</i>\n# <i>chown -R amavis:mailusers /var/amavis/.maildir/</i>\n# <i>chown amavis:mailusers /var/amavis/</i>\n# <i>chmod -R 1733 /var/amavis/.maildir/Bayes/</i>\n# <i>chmod g+rx /var/amavis/.maildir/</i>\n# <i>chmod g+rx /var/amavis/.maildir/Bayes/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):1022
+msgid "This grants members of the <c>mailusers</c> groups access to <c>amavis</c> mail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1027
+msgid "This makes the spam and ham folders writable but not readable. This way users can safely submit their ham without anyone else being able to read it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1032
+msgid "Then run the following command as the <c>spamtrap</c> user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1036
+msgid "Adding the shared folders to the users mailfolder"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1036
+#, no-wrap
+msgid "\n$ <i>maildirmake --add Bayes=/var/amavis/.maildir/Bayes $HOME/.maildir</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1040
+msgid "We have to give the group read permissions on the <path>Bayes</path> folder in order for the mail client to be able to see the subdirectories used by IMAP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1049
+msgid "Adding cron jobs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1052
+msgid "Now run <c>crontab -u amavis -e</c> to edit the amavis crontab to enable automatic learning of the Bayes filter every hour."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1057 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1128
+msgid "amavis crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1057
+#, no-wrap
+msgid "\n<comment>#Auto learn</comment>\n0 * * * *          /usr/bin/sa-learn --spam /var/amavis/.maildir/Bayes/.spam/{cur,new} \\\n                    &gt; /dev/null 2&gt;&amp;1\n0 * * * *          /usr/bin/sa-learn --ham /var/amavis/.maildir/Bayes/.ham/{cur,new} &gt; \\\n                   /dev/null 2&gt;&amp;1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1065
+msgid "<c>amavis</c> has to be a member of the <c>cron</c> group to run crons."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1070
+msgid "It seems like the shared maildir folders will make <c>sa-learn</c> examine all messages twice. This should not be a problem. The output will also show that the maximum of messages learned from is half or less than the messages examined."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1079 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1805
+msgid "Modifying amavisd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1082
+msgid "Now modify amavis to redirect spam emails to the <c>spamtrap</c> account and keep spamheaders."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1087
+#, no-wrap
+msgid "\n<comment>(Define the account to send virus spam emails)</comment>\n$spam_quarantine_to = \"spamtrap\\@$myhostname\";\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1095
+msgid "Redelivering false positives"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1098
+msgid "If you set the spam score very low like we do you will probably have some false positives. These are filtered into the folder <path>likely-spam</path>. These are manually reviewed and any false positive is moved to the <path>redeliver</path> mailfolder. From there it is first fed through <c>sa-learn --ham</c> and then redelivered with all headers intact using a patched version of <uri link=\"http://www.engelschall.com/sw/smtpclient/\">smtpclient</uri> by Ralf S. Engelschall."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1109
+msgid "The original version 1.0.0 of <c>smtpclient</c> is already in Portage however to keep all headers intact we use a modified version. Here is how you install the revised version:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1115
+msgid "Installing revised smtpclient"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1115
+#, no-wrap
+msgid "\n<comment>(Switch to your portage OVERLAY)</comment>\n# <i>wget http://home.coming.dk/files/smtpclient.tar.gz</i>\n# <i>tar xzf smtpclient.tar.gz</i>\n# <i>echo \"mail-client/smtpclient    ~x86\" &gt;&gt; /etc/portage/package.keywords</i>\n# <i>echo \"mail-client/smtpclient    fullheaders\" &gt;&gt; /etc/portage/package.use</i>\n# <i>emerge smtpclient</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1124
+msgid "Check for mails in the <path>redeliver</path> folder every minute using cron."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1128
+#, no-wrap
+msgid "\n<comment>#Redeliver false positives</comment>\n* * * * *          find /var/amavis/.maildir/Bayes/.redeliver/cur/ -type f -name \\\n                   \"[0-9]*\" -exec cp {} /var/amavis/.maildir/Bayes/.ham/cur/ \\; \\\n                   &amp;&amp; find /var/amavis/.maildir/Bayes/.redeliver/cur/ -type f \\\n                   -name \"[0-9]*\" -exec /usr/local/bin/redeliver.pl {} \\;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1136
+msgid "Now we only have to copy the <c>redeliver.pl</c> file to <path>/usr/local/bin/</path>. <uri link=\"http://home.coming.dk/files/redeliver.pl\">Download it</uri> or use the version below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1143
+msgid "redeliver.pl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1143
+#, no-wrap
+msgid "\n<comment>#!/usr/bin/perl -w\n\n# Redelivers mail using a modified version of smtpclient\n# By: Jens Hilligsoe &lt;gentoo@hilli.dk&gt;</comment>\n\nuse strict;\n\nif(!($#ARGV == 0)) {\n        die \"Usage:\\n$0 maildir_mail\\n\";\n}\n\nmy $mail = $ARGV[0];\nmy $to = \"\";\nmy $from = \"\";\n\nsub prunefile ( $ );\n\n<comment># Retrieve To and From envelope adresses</comment>\nopen (MAIL, $mail) or die \"Could not open $mail: $?\\n\";\nwhile(&lt;MAIL&gt;) {\n    if(($to eq \"\") || ($from eq \"\")) {\n        chop;\n        (my $key, my $value) = split (/:/);\n        if($key eq \"X-Envelope-To\") {\n            $to = $value;\n            $to =~ s/[\\&lt;\\&gt;,]//g; # Remove \"&lt;\", \"&gt;\" and \",\"\n            $to =~ s/^\\s+|\\s+$//g; #Remove whitespace before and after\n        }\n        if($key eq \"X-Envelope-From\") {\n            $from = $value;\n            $from =~ s/[\\&lt;\\&gt;,]//g;\n            $from =~ s/^\\s+|\\s+$//g;\n            if($from eq \"\") {\n                $from = \"postmaster\";\n            }\n        }\n    }\n}\n\nif($to eq \"\") {\n    prunefile($ARGV[0]); # Just nuke it if to is empty\n} else {\n    my $redelivercmd = \"cat $ARGV[0] | smtpclient -F -S 127.0.0.1 -P 10025 -f $from $to\";\n    unless (system($redelivercmd) == 0 ) {\n        die \"Unable to redeliver: $?\";\n    }\n    prunefile($ARGV[0]); # Clean up\n}\n\nsub prunefile ( $ ) {\n    my ($file) = @_;\n    unless (unlink $file) {\n        die \"Unable to remove mail: $?\";\n    }\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1204
+msgid "Cleaning up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1207
+msgid "We don't want to keep mail forever so we use <c>tmpwatch</c> to clean up regularily. Emerge it with <c>emerge tmpwatch</c>. Only <c>root</c> is able to run <c>tmpwatch</c> so we have to edit the <c>root</c> crontab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1213
+msgid "Modifying root crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1213
+#, no-wrap
+msgid "\n<comment># Clean up\n# Keep virusmails for a week (24*7 hours)</comment>\n15 0 * * *      /usr/sbin/tmpwatch -c -f -d --quiet 168 /var/amavis/virusmails/\n<comment># Delete spam and ham learned after a week</comment>\n15 0 * * *      /usr/sbin/tmpwatch -c -f -d --quiet 168 /var/amavis/.maildir/Bayes/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1294 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2072
+msgid "Greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1299
+msgid "Greylisting is one of the newer weapons in the spam fighting arsenal. As the name implies it is much like whitelisting and blacklisting. Each time an unknown mailserver tries to deliver mail the mail is rejected with a <e>try again later</e> message. This means that mail gets delayed but also that stupid spam bots that do not implement the RFC protocol will drop the attempt to deliver the spam and never retry. With time spam bots will probably adjust, however it will give other technologies more time to identify the spam."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1311
+msgid "If your ISP blocks incoming traffic on port 25 and relays all mail to you through their own mail server greylisting will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1316
+msgid "Postfix 2.1 come with a simple Perl greylisting policy server that implements such a scheme. However it suffers from unpredictable results when the partition holding the greylisting database run out of space. There exists an improved version that do not suffer this problem. First I will show how to install the builtin greylisting support that come with Postfix and then I will show how to configure the more robust replacement."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1326
+msgid "There are other greylisting policy servers for Postfix around (such as <uri link=\"http://www.gasmi.net/gld.html\">Gld</uri>, which is in Portage, and <uri link=\"http://sqlgrey.sourceforge.net/\">SQLgrey</uri>). Some of them support database backends, auto whitelisting and other neat features."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1336
+msgid "Simple greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1339
+msgid "If you prefer to use the improved greylisting with postgrey you can safely skip this section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1344
+msgid "We need the file <path>greylist.pl</path> but unfortunately the ebuild does not install it as default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1349
+msgid "Getting greylist.pl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1349
+#, no-wrap
+msgid "\n# <i>cp /usr/portage/distfiles/postfix-your-version-here.tar.gz /root/</i>\n# <i>tar xzf postfix-your-version-here.tar.gz</i>\n# <i>cp postfix-2.1.0/examples/smtpd-policy/greylist.pl /usr/bin/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1355
+msgid "Now we have the file in place we need to create the directory to hold the greylisting database:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1360
+msgid "Creating directory for the greylisting database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1360
+#, no-wrap
+msgid "\n# <i>mkdir /var/mta</i>\n# <i>chown nobody /var/mta</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):1365
+msgid "Do not create the greylisting database directory on a partition that might run out of space. While postfix can recover from no-space-left situations for the mail queue and mail box situations, this is not the case with the greylisting database. If the file becomes corrupted you may not be able to receive mail at all until you delete the file by hand."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1377
+msgid "Configuring greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1380
+msgid "Now that we have all this ready all that is left is to add it to the postfix configuration. First we add the necessary information to the <path>master.cf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1386
+msgid "Modifying master.cf to use greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1386
+#, no-wrap
+msgid "\npolicy-greylist  unix  -       n       n       -       -       spawn\n   user=nobody argv=/usr/bin/perl /usr/bin/greylist.pl\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1391
+msgid "The postfix spawn daemon normally kills its child processes after 1000 seconds but this is too short for the greylisting process so we have to increase the timelimit in <path>main.cf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1397 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1481
+msgid "Modifying main.cf to use greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1397
+#, no-wrap
+msgid "\npolicy-greylist_time_limit = 3600\n<comment>(Under smtpd_recipient_restrictions add:)</comment>\ncheck_sender_access hash:/etc/postfix/sender_access\n<comment>(Later on add:)</comment>\nrestriction_classes = greylist\ngreylist = check_policy_service unix:private/policy-greylist\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):1406
+msgid "Be sure to specify <c>check_sender_access</c> AFTER <c>reject_unauth_destination</c> or else your system could become an open mail relay."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1412
+msgid "The greylist database gets polluted quickly with bogus addresses. It helps if you protect greylist lookups with other restrictions that reject unknown senders and/or recipients."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1418
+msgid "We don't want to use greylisting for all domains but only for those frequently abused by spammers. After all it will delay mail delivery. A list of frequently forged MAIL FROM domains can be found <uri link=\"http://www.monkeys.com/anti-spam/filtering/sender-domain-validate.in\">online</uri>. Add the domains you receive a lot of spam from to <path>/etc/postfix/sender_access</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1427
+msgid "Format of sender_access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1427
+#, no-wrap
+msgid "\naol.com     greylist\nhotmail.com greylist\nbigfoot.com greylist\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1433
+msgid "If you want a more extensive list:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1437
+msgid "Adding all domains to sender_access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1437
+#, no-wrap
+msgid "\n# <i>wget http://www.monkeys.com/anti-spam/filtering/sender-domain-validate.in</i>\n# <i>cat sender-domain-validate.in | sort | awk {'print $1 \"\\t\\t greylist\"'} &gt; /etc/postfix/sender_access</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1442
+msgid "Now we only have to initialize the <path>sender_access</path> database:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1447
+msgid "Initialize sender_access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1447
+#, no-wrap
+msgid "\n# <i>postmap /etc/postfix/sender_access</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1451
+msgid "Now the setup of simple greylisting is complete."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):1455
+msgid "I tried this on one box handling thousands of mails daily and the results were almost a complete disaster. After four days the box was bogged down with hundreds of old <c>greylist.pl</c> processes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1464
+msgid "Configuring improved greylisting with postgrey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1467
+msgid "You can install the enhanced greylisting policy server with a simple <c>emerge</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1472
+msgid "Installing postgrey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1472
+#, no-wrap
+msgid "\n# <i>emerge postgrey</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1476
+msgid "After installing <c>postgrey</c> we have to edit <path>main.cf</path>. Changes are almost exactly like the built in greylisting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1481
+#, no-wrap
+msgid "\n<comment>(Under smtpd_recipient_restrictions add:)</comment>\ncheck_sender_access hash:/etc/postfix/sender_access\n<comment>(Later on add:)</comment>\nsmtpd_restriction_classes = greylist\ngreylist = check_policy_service inet:127.0.0.1:10030\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1489
+msgid "The Postfix SMTPD_POLICY_README only uses <c>restriction_classes</c> but that does not appear to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1494
+msgid "If you want to greylist everything instead add <c>check_policy_service inet:127.0.0.1:10030</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1499
+msgid "Finally, start the server and add it to the proper runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1503
+msgid "Starting postgrey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1503
+#, no-wrap
+msgid "\n# <i>/etc/init.d/postgrey start</i>\n# <i>rc-update add postgrey default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1508
+msgid "Some people like to get their mail fast and thus greylisting is worthless. However if you employ a backup mail server you can safely setup greylisting on that server. My limited experiences tell me that it can stop up to a third of the spam received."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1519
+msgid "SPF (Sender Policy Framework)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1524
+msgid "SPF allows domain owners to state in their DNS records which IP addressess should be allowed to send mails from their domain. This will prevent spammers from spoofing the <c>Return-Path</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1530
+msgid "If your ISP blocks incoming traffic on port 25 and relays all mail to you through their own mail server SPF will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1535
+msgid "First domain owners have to create a special <c>TXT</c> DNS record. Then an SPF-enabled MTA can read this and if the mail originates from a server that is not described in the SPF record the mail can be rejected. An example entry could look like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1542
+msgid "Example SPF record"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1542
+#, no-wrap
+msgid "\nexample.com.  IN TXT  \"v=spf1 a mx ptr -all\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1546
+msgid "The <c>-all</c> means to reject all mail by default but allow mail from the <c>A</c>(<c>a</c>), <c>MX</c>(<c>mx</c>) and <c>PTR</c>(<c>ptr</c>) DNS records. For more info consult further resources below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1553
+msgid "If you relay outgoing mail through your ISP you will have to add: <c>include:yourisp.com</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1558
+msgid "Spamassassin 3.0 has support for SPF, however it is not enabled by default and the new policy daemon in Postfix supports SPF so let's install SPF support for Postfix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1564
+msgid "If you want to use SPF with Spamassassin instead simply <c>emerge&nbsp;dev-perl/Mail-SPF-Query</c> and restart Amavisd-new."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1575
+msgid "First you have to install Postfix 2.1 as described above. When you have fetched the source grab the <path>spf.pl</path> with:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1581
+msgid "Installing spf.pl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1581
+#, no-wrap
+msgid "\n# <i>cp postfix-&lt;version&gt;/examples/smtpd-policy/spf.pl /usr/local/bin/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1585
+msgid "The <path>spf.pl</path> coming with Postfix is slightly buggy so find and uncomment the following line: <c>push @HANDLERS, \"sender_permitted_from\"; use Mail::SPF::Query;</c>. Furthermore in about line 199 substitute <c>comemnt</c> with <c>comment</c>. Alternatively you can download a <uri link=\"http://spf.pobox.com/postfix-policyd.txt\">development version</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1594
+msgid "This Perl script also needs some Perl libraries that are not in portage but it is still quite simple to install them:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1599
+msgid "Installing the needed Perl libraries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1599
+#, no-wrap
+msgid "\n# <i>emerge Mail-SPF-Query Net-CIDR-Lite Sys-Hostname-Long</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1603
+msgid "Now that we have everything in place all we need is to configure Postfix to use this new policy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1608
+msgid "Modifying master.cf to use SPF"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1608
+#, no-wrap
+msgid "\npolicy-spf  unix  -       n       n       -       -       spawn\n   user=nobody argv=/usr/bin/perl /usr/local/bin/spf.pl\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1613
+msgid "Now add the SPF check in <path>main.cf</path>. Properly configured SPF should do no harm so we could check SPF for all domains:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1618
+msgid "Modifying main.cf to use SPF"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1618
+#, no-wrap
+msgid "\n<comment>(Under smtpd_recipient_restrictions add:)</comment>\ncheck_policy_service unix:private/policy-spf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1623
+msgid "If you're experiencing problems with SPF, e.g. when using <c>fetchmail</c>, you might want to enable SPF for certain domains only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1633
+msgid "Configuring amavisd-new to use MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1635
+msgid "Configuring MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1638
+msgid "This has not been tested on versions higher than 2.2. Feedback is welcome :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1642
+msgid "For large domains the default values you can set in <path>amavisd.conf</path> might not suit all users. If you configure amavisd-new with MySQL support you can have individual settings for users or groups of users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1649
+msgid "Creating the MySQL database and user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1649
+#, no-wrap
+msgid "\n# <i>mysql -u root -p mysql</i>\nEnter password:\nWelcome to the MySQL monitor.  Commands end with ; or \\g.\nYour MySQL connection id is 78 to server version: 4.0.18-log\n\nType 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\nmysql&gt; <i>create database maildb;</i>\nmysql&gt; <i>GRANT INSERT,UPDATE,DELETE,SELECT ON maildb.* TO 'mail'@'localhost' IDENTIFIED BY 'very_secret_password';</i>\nmysql&gt; <i>use maildb;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1661
+msgid "Now that the database is created we'll need to create the necessary tables. You can cut and paste the following into the mysql prompt:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1666 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1859
+msgid "MySQL table layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1666
+#, no-wrap
+msgid "\nCREATE TABLE users (\n    id         int unsigned NOT NULL auto_increment,\n    priority   int          NOT NULL DEFAULT '7',  -- 0 is low priority\n    policy_id  int unsigned NOT NULL DEFAULT '1',\n    email      varchar(255) NOT NULL,\n    fullname   varchar(255) DEFAULT NULL,    -- not used by amavisd-new\n    local      char(1),     -- Y/N  (optional field, see note further down)\n    PRIMARY KEY (id),\n    KEY email (email)\n    );\nCREATE UNIQUE INDEX users_idx_email ON users(email);\n\n<comment>(any e-mail address, external or local, used as senders in wblist)</comment>\nCREATE TABLE mailaddr (\n   id         int unsigned NOT NULL auto_increment,\n   priority   int          NOT NULL DEFAULT '7',  -- 0 is low priority\n   email      varchar(255) NOT NULL,\n   PRIMARY KEY (id),\n   KEY email (email)\n   );\nCREATE UNIQUE INDEX mailaddr_idx_email ON mailaddr(email);\n\n<comment>(-- per-recipient whitelist and/or blacklist,</comment>\n<comment>-- puts sender and recipient in relation wb)</comment>\n(white or blacklisted sender)\nCREATE TABLE wblist (\n   rid        int unsigned NOT NULL,     -- recipient: users.id\n   sid        int unsigned NOT NULL,     -- sender:    mailaddr.id\n   wb         char(1) NOT NULL, -- W or Y / B or N / space=neutral\n   PRIMARY KEY (rid,sid)\n   );\n\nCREATE TABLE policy (\n   id               int unsigned NOT NULL auto_increment,\n   policy_name      varchar(32),     -- not used by amavisd-new\n   virus_lover          char(1),     -- Y/N\n   spam_lover           char(1),     -- Y/N  (optional field)\n   banned_files_lover   char(1),     -- Y/N  (optional field)\n   bad_header_lover     char(1),     -- Y/N  (optional field)\n   bypass_virus_checks  char(1),     -- Y/N\n   bypass_spam_checks   char(1),     -- Y/N\n   bypass_banned_checks char(1),     -- Y/N  (optional field)\n   bypass_header_checks char(1),     -- Y/N (optional field)\n   spam_modifies_subj   char(1),     -- Y/N (optional field)\n   spam_quarantine_to   varchar(64) DEFAULT NULL, -- (optional field)\n   spam_tag_level  float,  -- higher score inserts spam info headers\n   spam_tag2_level float DEFAULT NULL,  -- higher score inserts\n               -- 'declared spam' info header fields\n   spam_kill_level float,  -- higher score activates evasive actions, e.g.\n               -- reject/drop, quarantine, ...\n               -- (subject to final_spam_destiny setting)\n   PRIMARY KEY (id)\n  );\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1722
+msgid "If you have problems using copy/paste you might have to copy this somewhere else and clean out the unneeded characters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1727
+msgid "Lookups trying to match email are done with raw (rfc2821-unquoted and unbracketed) addresses as a key, i.e.: <c>John \"Funny\" Smith@example.com</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1733
+msgid "Lookups are performed in the following order: <c>SQL</c>, <c>LDAP</c>, <c>hash</c>, <c>ACL</c>, <c>regexp</c>, <c>constant</c>. The first that returns a definitive answer (not <c>undef/NULL</c>) stops the search."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1739
+msgid "If you wish to use whitelisting and blacklisting you must add the sender and receiver to <c>mailadr</c> after which you create the relation between the two e-mail addresses in <c>wblist</c> and state if it is whitelisting (<c>W</c>) or blacklisting (<c>B</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1746
+msgid "Now that we have created the tables let's insert a test user and a test policy:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1751
+msgid "Create test user and test policy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1751
+#, no-wrap
+msgid "\nINSERT INTO users\n   SET\n      id         =1,\n      priority   =9,\n      policy_id  =1,\n      email      =\"johndoe@example.com\",\n      fullname   =\"John Doe\",\n      local      =\"Y\";\n\nINSERT INTO policy\n   SET\n      id                     =1,\n      policy_name            =\"Test policy 1\",\n      virus_lover            =\"N\",\n      spam_lover             =\"N\",\n      banned_files_lover     =\"N\",\n      bad_header_lover       =\"N\",\n      bypass_virus_checks    =\"N\",\n      bypass_spam_checks     =\"N\",\n      bypass_banned_checks   =\"N\",\n      bypass_header_checks   =\"N\",\n      spam_modifies_subj     =\"N\",\n      spam_quarantine_to     =NULL,\n      spam_tag_level         =-50.0,\n      spam_tag2_level        =7.0,\n      spam_kill_level        =10.0;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1780
+msgid "Copy this to somewhere else and adjust to suit your own environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1784
+msgid "<c>local</c> should be set to <c>Y</c> otherwise the mail will not be scanned for spam."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1789
+msgid "This inserts a test user and a Test policy. Adjust these examples to fit your needs. Further explanation of the configuration names can be found in <path>amavisd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1798
+msgid "Configuring amavisd to use MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1801
+msgid "Now that MySQL is ready we need to tell amavis to use it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1805
+#, no-wrap
+msgid "\n@lookup_sql_dsn =\n   ( ['DBI:mysql:maildb:host1', 'mail', 'very_secret_password']  );\n\n<comment>(For clarity uncomment the default)</comment>\n$sql_select_policy = 'SELECT *,users.id FROM users,policy'.\n   ' WHERE (users.policy_id=policy.id) AND (users.email IN (%k))'.\n   ' ORDER BY users.priority DESC';\n\n<comment>(If you want sender white/blacklisting)</comment>\n   $sql_select_white_black_list = 'SELECT wb FROM wblist,mailaddr'.\n     ' WHERE (wblist.rid=?) AND (wblist.sid=mailaddr.id)'.\n     '   AND (mailaddr.email IN (%k))'.\n     ' ORDER BY mailaddr.priority DESC';\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1826
+msgid "Configuring Spamassassin to use MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1830
+msgid "As of Spamassassin 3.0 it is possible to store the Bayes and AWL data in a MySQL database. We will use MySQL as the backend as it can generally outperform other databases. Also, using MySQL for both sets of data makes system management much easier. Here I will show how to easily accomplish this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1837
+msgid "First start out by creating the new MySQL user and then create the needed tables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1842
+msgid "Creating the new MySQL database and user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1842
+#, no-wrap
+msgid "\n# <i>mysql -u root -p mysql</i>\nEnter password:\nWelcome to the MySQL monitor.  Commands end with ; or \\g.\nYour MySQL connection id is 78 to server version: 4.0.18-log\n\nType 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\nmysql&gt; <i>create database dbname;</i>\nmysql&gt; <i>GRANT INSERT,UPDATE,DELETE,SELECT ON dbname.* TO 'dbuser'@'localhost' IDENTIFIED BY 'another_very_secret_password';</i>\nmysql&gt; <i>use dbname;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1854
+msgid "Now that the database is created we'll create the necessary tables. You can cut and paste the following into the mysql prompt:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1859
+#, no-wrap
+msgid "\n      CREATE TABLE bayes_expire (\n          id                    int(11)         NOT NULL default '0',\n          runtime               int(11)         NOT NULL default '0',\n          KEY bayes_expire_idx1 (id)\n          ) TYPE=MyISAM;\n\n      CREATE TABLE bayes_global_vars (\n          variable              varchar(30)     NOT NULL default '',\n          value                 varchar(200)    NOT NULL default '',\n          PRIMARY KEY           (variable)\n          ) TYPE=MyISAM;\n\n      INSERT INTO bayes_global_vars VALUES ('VERSION','3');\n\n      CREATE TABLE bayes_seen (\n          id                    int(11)         NOT NULL default '0',\n          msgid                 varchar(200) binary NOT NULL default '',\n          flag                  char(1)         NOT NULL default '',\n          PRIMARY KEY           (id,msgid)\n          ) TYPE=MyISAM;\n\n      CREATE TABLE bayes_token (\n          id                    int(11)         NOT NULL default '0',\n          token                 char(5)         NOT NULL default '',\n          spam_count            int(11)         NOT NULL default '0',\n          ham_count             int(11)         NOT NULL default '0',\n          atime                 int(11)         NOT NULL default '0',\n          PRIMARY KEY           (id, token),\n          INDEX (id, atime)\n          ) TYPE=MyISAM;\n\n      CREATE TABLE bayes_vars (\n          id                    int(11)         NOT NULL AUTO_INCREMENT,\n          username              varchar(200)    NOT NULL default '',\n          spam_count            int(11)         NOT NULL default '0',\n          ham_count             int(11)         NOT NULL default '0',\n          token_count           int(11)         NOT NULL default '0',\n          last_expire           int(11)         NOT NULL default '0',\n          last_atime_delta      int(11)         NOT NULL default '0',\n          last_expire_reduce    int(11)         NOT NULL default '0',\n          oldest_token_age      int(11)         NOT NULL default '2147483647',\n          newest_token_age      int(11)         NOT NULL default '0',\n          PRIMARY KEY           (id),\n          UNIQUE bayes_vars_idx1 (username)\n          ) TYPE=MyISAM;\n\n      CREATE TABLE awl (\n          username              varchar(100)    NOT NULL default '',\n          email                 varchar(200)    NOT NULL default '',\n          ip                    varchar(10)     NOT NULL default '',\n          count                 int(11)         default '0',\n          totscore              float           default '0',\n          PRIMARY KEY           (username,email,ip)\n          ) TYPE=MyISAM;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(impo):1916
+msgid "The <c>INSERT</c> line is needed otherwise Spamassassin will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1921
+msgid "This is also available in the source tarball in the files <path>awl_mysql.sql</path> and <path>bayes_mysql.sql</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1929
+msgid "Configuring Spamassassin to use the MySQL backend"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1932
+msgid "If you have an old Bayes database in the DBM database and want to keep it follow these instructions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1937
+msgid "Converting Bayes data from a DBM Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1944
+msgid "Note that the last step should only be performed after the MySQL database and <path>secrets.cf</path> have been updated."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1949
+msgid "Now give Spamassassin the required info:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1953
+msgid "Modifying /etc/mail/spamassassin/secrets.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1953
+#, no-wrap
+msgid "\n<comment>(Tell Spamassassin to use MySQL for bayes data</comment>\nbayes_store_module              Mail::SpamAssassin::BayesStore::SQL\nbayes_sql_dsn                   DBI:mysql:sa_bayes:localhost:3306\nbayes_sql_username              db_name\nbayes_sql_password              another_very_secret_password\n\n<comment>(Tell Spamassassin to use MySQL for AWL data</comment>\nauto_whitelist_factory          Mail::SpamAssassin::SQLBasedAddrList\nuser_awl_dsn                    DBI:mysql:sa_bayes:localhost:3306\nuser_awl_sql_username           db_name\nuser_awl_sql_password           another_very_secret_password\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1967
+msgid "Next, change its permissions for proper security:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1971
+msgid "Changing permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1971
+#, no-wrap
+msgid "\n# <i>chmod 400 /etc/mail/spamassassin/secrets.cf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1975
+msgid "To create a very secret password use <c>emerge app-admin/makepasswd</c> and <c>makepasswd -chars=8</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1980
+msgid "Now all you have to do is <c>/etc/init.d/amavisd restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1989
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1991 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2100
+msgid "Amavisd-new"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1994
+msgid "To troubleshoot Amavisd-new start out by stopping it with <c>/etc/init.d/amavisd stop</c> and then start it manually in the foreground with <c>amavisd debug</c> and watch it for anomalies in the output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2003 ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2099
+msgid "Spamassassin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):2006
+msgid "To troubleshoot Spamassassin you can filter an email through it with <c>spamassassin -D &lt; mail</c>. To ensure that the headers are intact you can move it from another machine with IMAP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):2012
+msgid "If you need to troubleshoot you have to enable login for the user <c>amavis</c> by changing the login shell in <path>/etc/passwd</path> to <path>/bin/bash</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):2018
+msgid "If you want you can make get the same information and more with Amavisd-new using <c>amavisd debug-sa</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2026
+msgid "Getting help"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):2029
+msgid "If you need help a good place to go is the amavis-user mailing list. Before postting a question try searching the <uri link=\"http://marc.theaimsgroup.com/?l=amavis-user\">Amavis User mailing list archives</uri>. If you find no answer here you can subscribe to the <uri link=\"https://lists.sourceforge.net/lists/listinfo/amavis-user\">Amavis User mailing list</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):2039
+msgid "If your question is specific to SpamAssassin, DCC, Razor, or Postfix, please refer to their respective home pages listed below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2049
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2051
+msgid "For further information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2056
+msgid "http://www.ijs.si/software/amavisd/INSTALL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2056
+msgid "Amavisd-new INSTALL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2060
+msgid "http://www.ijs.si/software/amavisd/README.postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2060
+msgid "Amavisd-new Postfix README"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2064
+msgid "http://www.ijs.si/software/amavisd/amavisd-new-docs.html#pbanks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2064
+msgid "Amavisd-new Policy bank documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2068
+msgid "http://spamassassin.apache.org/full/3.0.x/dist/sql/README"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2068
+msgid "Spamassassin SQL README"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2072
+msgid "http://www.greylisting.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2075
+msgid "http://www.postfix.org/FILTER_README.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2075
+msgid "Postfix SMTPD_POLICY_README"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2079
+msgid "http://www.unixwiz.net/techtips/postfix-HELO.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2079
+msgid "Blocking spammers with Postfix HELO controls"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2083
+msgid "http://www.linuxjournal.com/article.php?sid=7327"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2083
+msgid "SPF Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2087
+msgid "http://jimsun.linxnet.com/misc/postfix-anti-UCE.txt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2087
+msgid "Jim Seymour's Postfix Anti-UCE Cheat Sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2095
+msgid "General resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2099
+msgid "http://www.spamassassin.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2100
+msgid "http://www.ijs.si/software/amavisd/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2102
+msgid "http://www.ijs.si/software/amavisd/amavisd-new-docs.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2102
+msgid "Amavisd-new documentation bits and pieces"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2105
+msgid "http://razor.sourceforge.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2105
+msgid "Vipuls's Razor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2106
+msgid "http://pyzor.sourceforge.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2108
+msgid "http://www.rhyolite.com/anti-spam/dcc/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2108
+msgid "Distributed Checksum Clearinghouse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2112
+msgid "http://www.renaissoft.com/projects/maia/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2112
+msgid "Maia Mailguard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2120
+msgid "Other howtos"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2125
+msgid "http://www.flakshack.com/anti-spam/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2125
+msgid "Fairly-Secure Anti-SPAM Gateway Using OpenBSD, Postfix, Amavisd-new, SpamAssassin, Razor and DCC"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/man-guide.xml.pot b/doc/gettext/man-guide.xml.pot
new file mode 100644
index 0000000..2844587
--- /dev/null
+++ b/doc/gettext/man-guide.xml.pot
@@ -0,0 +1,401 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(guide:link):5
+msgid "/doc/en/man-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):6
+msgid "Gentoo Man Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(abstract):12
+msgid "This guide shows how to navigate man pages using man."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(version):20
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(date):21
+msgid "2006-06-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):26
+msgid "The man program"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):29
+msgid "Everyone at some point in their linux life has used it. \"It\" is the <c>man</c> command. However, while the man program itself appears to be rather simplistic in its construct, it has a few extra abilities than just simply scrolling through the page. This document hopes to help shed some light on these capabilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):40
+msgid "Man layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):43
+msgid "Man pages are mainly stored in the <path>/usr/share/man</path> directory. However, as long as a man page is located in the <c>MANPATH</c> environment variable, man will be able to pick it up. Gentoo will generally store <c>MANPATH</c> variables in <path>/etc/env.d</path>. Within these directories are some folders with the structure manX where X is the section number. For example, a standard man layout might look like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):52
+msgid "Standard man structure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):52
+#, no-wrap
+msgid "\n$ <i>ls /usr/share/man | grep man</i>\nman0p\nman1\nman1p\nman2\nman3\nman3p\nman4\nman5\nman6\nman7\nman8\nman9\nmann\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):69
+msgid "The actual section numbering appears fairly standard. However, notice that there is a <path>mann</path> and some <path>man#p</path> folders. The following table lists the above man page directories and what is contained within them:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(th):77
+msgid "Man Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(th):78
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):81
+msgid "man0p"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):82
+msgid "The <c>p</c> here stands for POSIX, as with the other directories with p in their names. Man pages in this directory describe the functionality of various POSIX header files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):89
+msgid "man1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):90
+msgid "This section is for standard commands. Most programs will put their man pages here, so this section tends to be the largest."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):96
+msgid "man1p"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):97
+msgid "This section describes the POSIX versions of the commands described in 1p. Since it only describes basic commands, it is much smaller than man1."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):103
+msgid "man2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):104
+msgid "This section describes Linux kernel system calls."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):107
+msgid "man3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):108
+msgid "This section describes standard c library functions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):111
+msgid "man4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):112
+msgid "This section describes special devices. These devices are generally kernel oriented, but <c>Xorg-X11</c> has entries in here as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):118
+msgid "man5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):119
+msgid "This section describes both the makeup of certain files and what files a program uses. Those of you reading this document may be familiar with references to <c>man 5 portage</c> for a description of the <c>portage</c> file structure, and <c>man 5 make.conf</c> for <path>make.conf</path> makeup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):128
+msgid "man6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):129
+msgid "This section introduces games and other special toys."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):132
+msgid "man7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):133
+msgid "This section describes standards and other miscellaneous items. These standards can include things such as charsets, SQL statements, ISO standards and regular expressions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):140
+msgid "man8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):141
+msgid "This section describes administrative commands (those usually run by the root user)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):147
+msgid "man9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):148
+msgid "This section is somewhat sparse, but is meant to contain documentation for various parts of the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):154
+msgid "mann"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):155
+msgid "This section is mainly used by <c>Tcl/Tk</c>. The <c>n</c> stands for new."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):161
+msgid "While this is not an extensive and detailed list, it does cover the man pages that most people will be interested in. However, sometimes you can find out what a section does as easily as looking at this table. The next chapter will look at using man to traverse this layout."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):173
+msgid "Working with the man layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):175
+msgid "Browsing the man layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):178
+msgid "Now that we understand the man layout, we can begin to look it over for commands. Sometimes we may need to narrow down what man page we want. The first way would be addressing by section. To found out a description of a section, once can use <c>man section intro</c> like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):185
+msgid "Using man intro to describe a section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):185
+#, no-wrap
+msgid "\n$ <i>man 3 intro</i>\n<comment>(Output slightly modified to fit the document properly)</comment>\nINTRO(3)               Linux Programmer's Manual                INTRO(3)\n\n\n\nNAME\n       intro - Introduction to library functions\n\nDESCRIPTION\n       This chapter describes all library functions excluding the library\n       functions described in chapter 2, which implement system calls.\n       There are various function groups which can be identified by a\n       letter which is appended to the chapter number:\n....\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):203
+msgid "Unfortunately, this doesn't always work! However, luckily for us there is another way to search for commands that may return multiple results (such as a library call and system command having the same name). To do so, we use the <c>-K</c> parameter to man like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):210
+msgid "Using man -K to search by string"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):210
+#, no-wrap
+msgid "\n$ <i>man -K sleep</i>\n/usr/share/man/man0p/time.h.0p.gz? [ynq] <i>n</i>\n/usr/share/man/man0p/unistd.h.0p.gz? [ynq] <i>n</i>\n/usr/share/man/man2/alarm.2.gz? [ynq] <i>n</i>\n/usr/share/man/man2/pause.2.gz? [ynq] <i>n</i>\n/usr/share/man/man2/futex.2.gz? [ynq] <i>n</i>\n/usr/share/man/man2/nanosleep.2.gz? [ynq] <i>y</i>\n/usr/share/man/man2/semop.2.gz? [ynq] <i>q</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):221
+msgid "Sometimes the output may be a lot larger. In this case it might be better to specify more specific keywords. Now that we know where to find the man page, the next section will look at viewing the man page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):230
+msgid "Viewing man pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):233
+msgid "Viewing man pages can be done in 2 ways, first is with <c>man [man page name]</c>. The second way is <c>man [section] [man page name]</c>. Let's take <c>bc</c> for example. I can view either the first man page that comes up on <c>bc</c> (which would be section 1, because it is the lowest section containing a man page on <c>bc</c>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):241
+msgid "Viewing the default man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):241
+#, no-wrap
+msgid "\n$ <i>man bc</i>\nbc(1)                                            bc(1)\n\n\nNAME\n       bc - An arbitrary precision calculator language\n...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):251
+msgid "However, what if I want the POSIX version? Then I can use the second form:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):255
+msgid "Viewing a specific man page by section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):255
+#, no-wrap
+msgid "\n$ <i>man 1p bc</i>\nBC(P)        POSIX Programmer's Manual           BC(P)\n\n\nNAME\n       bc - arbitrary-precision arithmetic language\n...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):265
+msgid "And the man page is displayed. Now that we have the man page up, it's time to work with it. The next section will look at navigation and searching."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):273
+msgid "Navigating and searching man pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):276
+msgid "Navigating a man page is fairly simple. To move up and down line by line, use the up and down arrow keys. To move up page by page, you can use the page up and page down keys. Do however note that these navigation instructions assume the environmental <c>PAGER</c> variable is set to use the default pager, <c>less</c>. Less also has a few other commands for navigation, but the arrow keys usually suffice:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):285
+msgid "Additional less navigation keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):285
+#, no-wrap
+msgid "\n  e  ^E  j  ^N  CR  *  Forward  one line   (or N lines).\n  y  ^Y  k  ^K  ^P  *  Backward one line   (or N lines).\n  f  ^F  ^V  SPACE  *  Forward  one window (or N lines).\n  b  ^B  ESC-v      *  Backward one window (or N lines).\n  z                 *  Forward  one window (and set window to N).\n  w                 *  Backward one window (and set window to N).\n  ESC-SPACE         *  Forward  one window, but don't stop at end-of-file.\n  d  ^D             *  Forward  one half-window (and set half-window to N).\n  u  ^U             *  Backward one half-window (and set half-window to N).\n  ESC-)  RightArrow *  Left  one half screen width (or N positions).\n  ESC-(  LeftArrow  *  Right one half screen width (or N positions).\n  F                    Forward forever; like \"tail -f\".\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):300
+msgid "Searching, however, is more interesting. The two most basic searches are <c>/pattern</c> and <c>?pattern</c>. The first version searches forwards, and the second searches backwards. <c>pattern</c> is a regular expression pattern that is described in <c>man 7 regex</c>. Let's take for example searching for the <c>-D</c> option to <c>emerge</c>. First, bring up the emerge man page:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):308
+msgid "Bringing up the emerge man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):308
+#, no-wrap
+msgid "\n$ <i>man emerge</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):312
+msgid "Then, at the screen, press the <c>/</c> key to bring up the entry prompt to search forwards and enter in our search pattern:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):317
+msgid "Bringing up the forward search prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):317
+#, no-wrap
+msgid "\n     gracefully handles updating installed packages to newer releases as well.\n     It handles both source and binary packages, and it can be used to create\n     binary packages for distribution.\n\nEBUILDS, TBZ2S, CLASSES AND DEPENDENCIES\n/<i>\\-D</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(note):326
+msgid "The <c>\\</c> is done to escape the <c>-</c> sign, which would normally be used as part of a regular expression."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):331
+msgid "This will search the man page, and bring the searched item into focus:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):335
+msgid "Forward search results"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):335
+#, no-wrap
+msgid "\n  --deep (-D)\n        When used in conjunction with --update, this flag forces emerge to consider the entire\n        dependency tree of packages, instead of checking only the immediate dependencies of\n        the packages.  As an example, this catches updates in libraries that are not directly\n        listed in the  dependencies of a package.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):343
+msgid "If you hit a search result by accident and want to continue searching for the same results, simply press the <c>/</c> key again, and press enter (i.e. don't put a pattern it). This will cause the search to default to the last pattern used. Now with some man pages, options are listed, then explained later on. Take the <c>man 5 portage</c> man page. It lists the files used, then explains their usage. Searching forward a few times would return the results, but there's an easier way to handle this, with the second search form, backwards searching. Let's use this to find the description on <path>package.unmask</path>. First, bring up <c>man 5 portage</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):355
+msgid "Bringing up the man 5 portage man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):355
+#, no-wrap
+msgid "\n$ <i>man 5 portage</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):359
+msgid "Now press <c>SHIFT+g</c>. This will bring you to the end of the page:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):363
+msgid "End of the man page after SHIFT+g"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):363
+#, no-wrap
+msgid "\nSEE ALSO\n       emerge(1), ebuild(1), ebuild(5), make.conf(5)\n\nPortage 2.0.51        Jan 2004            PORTAGE(5)\nlines 418-442/442 (END)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):371
+msgid "Now we'll go ahead and enter the pattern to search for with the <c>?pattern</c> backwards search option. First press the <c>?</c> key to bring up the prompt, and then enter in <c>package.unmask</c>, our query:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):377
+msgid "Specifying our search"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):377
+#, no-wrap
+msgid "\nSEE ALSO\n       emerge(1), ebuild(1), ebuild(5), make.conf(5)\n\nPortage 2.0.51        Jan 2004           PORTAGE(5)\n?<i>package.unmask</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):385
+msgid "Then hit enter to bring up the result:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):389
+msgid "Our search result"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):389
+#, no-wrap
+msgid "\n  package.unmask\n       Just like package.mask above, except here you list packages you want to unmask.\n       Useful for overriding the global  package.mask  file (see below).  Note that\n       this does not override packages that are masked via KEYWORDS.\n...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):397
+msgid "And the search is complete! Note that just as with <c>/</c>, using <c>?</c> search with no pattern will use the last pattern to search."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):405
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):408
+msgid "This concludes the man guide. This will hopefully shed some light on navigating man pages, and maybe even give a few new tips to the more experienced users. For those who prefer alternate means of navigating man pages, the following are also available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(li):416
+msgid "app-text/man2html - a program for converting man pages to html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(li):417
+msgid "app-text/tkman - a tk based man page browser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):420
+msgid "Also the <c>KDE</c> web browser <c>Konqueror</c> can browse man pages using the <c>man:</c> syntax in the address bar."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/management-structure.xml.pot b/doc/gettext/management-structure.xml.pot
new file mode 100644
index 0000000..7b0aa1b
--- /dev/null
+++ b/doc/gettext/management-structure.xml.pot
@@ -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: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(guide:link):5
+msgid "/doc/en/management-structure.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):6
+msgid "Gentoo Top-Level Management Structure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(mail:link):9
+msgid "drobbins@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(mail):9
+msgid "Daniel Robbins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(mail:link):12
+msgid "pauldv@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(mail):12
+msgid "Paul de Vrieze"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(abstract):16
+msgid "Gentoo top-level management structure (work in progress)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(version):22
+msgid "1.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(date):23
+msgid "2003-07-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):27
+msgid "Gentoo top-level management structure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(brite):33
+msgid "As of May 2005, this document is no longer valid but kept for historical purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):40
+msgid "What was the purpose of the new management structure?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):43
+msgid "The purpose of the new management structure was to solve chronic management, coordination and communication issues in the Gentoo project. In particular, we had no clearly defined top-level management structure, and no official, regular meetings to communicate status updates between developers serving in critical roles. In general, most communication took place on irc and irregularly via email. There was also little to no accountability, even at a high level, to complete projects on time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):53
+msgid "Because of this prior state of affairs, it was difficult to set goals and track the status of projects. This lack of communication and coordination also made it difficult for top-level developers to manage their own projects. In addition, we had other chronic problem of not having clearly-defined roles and scopes of executive decision-making authority for top-level developers, which resulted in many top-level developers doubting that they even have the authority to manage their own projects and sub-projects. While this had *never* been the intention of top-level developers, it is the unfortunate result of an unstructured development process: no one knew what was going on, and everyone deferred to the Chief Architect for all executive decisions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):67
+msgid "Clearly, a plan was needed to swiftly and permanently address these issues by increasing communication, coordination, and accountability. Roles and scopes of executive decision-making authority needed to be defined for top developers so that they have a clear mandate as well as accountability to manage their projects and thus ensure their projects completed their appointed work efficiently and on-schedule."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):79
+msgid "Initial implementation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):82
+msgid "Initial implementation of the new management structure began by creating official top-level management structure. This management structure consists of the Chief Architect and a group of developers that will be given the title of Top-level Managers. Top-level Managers will be accountable for the projects they manage, and be responsible for communicating the status of their projects to the rest of the Top-level Managers and Chief Architect, as well as other responsibilities detailed later in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):92
+msgid "All the top-level projects in the Gentoo project are in the process of being clearly defined, including goals, sub-projects, members, roadmap and schedules. The \"Hardened Gentoo\" page at <uri>http://www.gentoo.org/proj/en/hardened/</uri> is an excellent example of such a top-level project definition, and many other top-level projects currently exist today."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):101
+msgid "Certain executive decision-making authority will be granted to these projects, as agreed upon by the Chief Architect, Top-level Managers and project members. Then, as part of the initial implementation of the new management structure, a Top-level Manager or managers will be officially adopt projects and ebuild herds. These managers will be responsible for tracking the status of the project, ensuring that the project meets targets and is generally managed properly. Manager responsibilities are described in detail later in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):115
+msgid "Management team"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):118
+msgid "The current top-level management team is as follows (in no particular order):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):123
+msgid "Seemant Kulleen (seemant)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):124
+msgid "Jay Pfeifer (pfeifer)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):125
+msgid "Joshua Brindle (method)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):126
+msgid "Kurt Lieber (klieber)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):127
+msgid "Pieter Van den Abeele (pvdabeel)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):128
+msgid "Jon Portnoy (avenj)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):129
+msgid "Paul de Vrieze (pauldv)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):130
+msgid "Sven Vermeulen (swift)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):136
+msgid "Management charter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):139
+msgid "1) Constructive, professional communication: All communication should be focused on improving the management of Gentoo projects, should be constructive in nature and should be shared in a friendly, professional manner."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):146
+msgid "2) Accountability to peers: Allow fellow members of this list to hold us accountable to follow-through on projects and meet deadlines. Keep fellow members accountable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):152
+msgid "3) Management of projects: empower managers to have the authority and strategic direction necessary to properly manage thier projects and efforts to ensure projects complete their appointed work on time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):158
+msgid "4) Results: our expectation is that our efforts, when properly executed, will result in the Gentoo project's ability to meet deadlines, have much better communication and coordination throughout the entire project, higher overall quality and a more positive experience for all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):168
+msgid "Manager responsibilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):171
+msgid "Every top-level Gentoo project will have a clearly defined scope, and clearly defined and explicit executive decision-making authority that will be granted to managers of the project to exercise and/or delegate as they see fit. Both the scope and any necessary decision-making authority must be agreed upon by both the Chief Architect and project members. The scope and executive authority of a project can be expanded over time as required as approved by the Top-level Managers and Chief Architect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):181
+msgid "In addition to decision-making authority, managers have the following responsibilities:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):187
+msgid "Keep a complete list of all projects and efforts you are managing, and associated gentoo.org project page up-to-date"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):192
+msgid "Manage and track the status of these efforts. This includes active direction as well as passive tracking of progress."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):197
+msgid "Define clear goals, roadmaps and timelines (preliminary if necessary) for every effort."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):202
+msgid "Proactively identify efforts that have problems and need help."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):204
+msgid "Ensure that your efforts are completed on-time, or that any efforts that are behind-schedule are reported in a timely manner."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):209
+msgid "Remain focused. Make sure that you are not managing more than you can handle."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):214
+msgid "Fulfill formal communication and coordination responsibilities required by top-level managers (weekly meetings, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):219
+msgid "Fulfill formal communication and coordination responsibilities required by individual efforts (project meetings, communication with project members, etc.) This is important as our management of projects means that we have the responsibility not only to communicate with our peers but also those who we are managing. This communication should be frequent, have a formal component (planned meetings, official status updates, etc.) and model good management practices to members of our teams."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):229
+msgid "<b>RECURSIVE FUNCTIONALITY</b>: At an appropriate time, implement these management practices for *sub*-projects (define managers, clear sub-project goals, grant executive authority) with you serving as primary authority."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):239
+msgid "Meetings, logs and status updates"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):242
+msgid "Currently, weekly manager meetings are held on irc, and all Gentoo developers are welcome to join the meeting channel and view the meeting in progress. In addition, after the meeting completes, the floor is opened for questions and comments by developers. The weekly meetings generally take place on Monday. After the meeting and open-floor session is concluded, a log of the meeting is posted to the gentoo-core mailing list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):251
+msgid "Status updates are very important to the proper functioning of our management structure. Currently, managers make an effort to email each other weekly status updates. Soon, we hope to post weekly status updates to our respective project pages so that the public can be apprised on the status of every top-level project."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(note):259
+msgid "Inability to attend due to time zone can be addressed by posting the full IRC log to gentoo-managers and allowing non-attending members to post ideas, comments and follow-ups."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):268
+msgid "Decision-making"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):271
+msgid "Currently, GLEPs (Gentoo Linux Enhancement Proposals) can be approved or rejected by the appropriate top-level manager under which the GLEP falls. If there is no clearly-defined manager under which the GLEP falls, the GLEP will be voted upon by the Managers and Chief Architect, and must be approved unanimously. In all cases, a public, written explanation must be provided detailing why the GLEP was approved or rejected, either by the manager who approved/rejected it, or the head of the GLEP sub-project (Grant Goodyear) if the GLEP was voted upon by the management team. This summary is meant to reflect the decision that was made by some of the managers at an early manager meeting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):283
+msgid "Currently, there is no formal general voting procedure in place. In the interim, any item to be voted upon must be approved by \"votable\" by the Chief Architect. Before voting takes place, all managers must have an opportunity to present their ideas before the other managers, with the general originator(s) of the idea having the opportunity to present first. After that, the Chief Architect and Managers can present their ideas, with the Chief Architect having the opportunity to present last. After this has happened, voting can take place, and the item will be approved on an unanimous vote. Managers or the Chief Architect can choose to abstain from voting, and the vote can still pass with abstainers as long as at least 50% of the members have voted. The voting must take place at an official managers meeting. Non-attending managers are allowed to vote via email. The vote must be officially tallied and posted to the managers list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):298
+msgid "The reason for the \"Chief Architect approval\" clause it to prevent the voting process from being abused by allowing voting items that make no sense, such as those that begin with a \"Should we continue to,\" where a \"nay\" result would result in a change in existing policy, as well as preventing managers for requesting that every small decision be voted upon. We currently have no clear policy to determine what is a \"votable\" item, and without this policy there needs to be some method to determine what is \"votable\" and what affects some immutable part of Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):309
+msgid "This section is subject to additional clarification and refinement in the future, as is the rest of this document. The purpose of this section is to document our currently-existing procedures rather than define ideal or \"final\" procedures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):319
+msgid "Top-level projects"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):323
+msgid "It is the responsibility of the <uri link=\"/proj/en/metastructure/\">metastructure</uri> top-level project to officially document and get changes approved to our management structure. The <uri link=\"/proj/en/metastructure/projects.xml\">official top-level project list</uri> can be viewed, and can be expected to change/expand slightly at the new management structure is implemented."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/metadoc.xml.pot b/doc/gettext/metadoc.xml.pot
new file mode 100644
index 0000000..5e08e04
--- /dev/null
+++ b/doc/gettext/metadoc.xml.pot
@@ -0,0 +1,1648 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(metadoc:lang):4
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(version):5
+msgid "1.155"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(lead):7
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):8
+msgid "cam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):9
+msgid "flammie"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):10
+msgid "fox2mike"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):11
+msgid "jkt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):13
+msgid "rane"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):14
+msgid "vanquirius"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):17
+msgid "Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):18
+msgid "Installation Related Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):19
+msgid "Installation Guides"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):20
+msgid "Other Installation Related Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):21
+msgid "Upgrade Guides"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):22
+msgid "Gentoo System Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):23
+msgid "Published Articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):24
+msgid "Portage and Related Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):25
+msgid "Configuring Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):26
+msgid "Gentoo Choices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):27
+msgid "Gentoo Articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):28
+msgid "Learning Linux Articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):29
+msgid "DeveloperWorks Common Threads"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):30
+msgid "Miscellaneous Articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):31
+msgid "System Administration Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):32
+msgid "General System Administration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):33
+msgid "Specific Administration Guides"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):34
+msgid "Gentoo Development Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):35
+msgid "Gentoo Development Policies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):36
+msgid "Development Related Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):37
+msgid "Gentoo Desktop Documentation Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):38
+msgid "Installing your Desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):39
+msgid "Configuring your Desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):40
+msgid "Application Specific Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):41
+msgid "Other Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):42
+msgid "Project Specific Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):43
+msgid "Base Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):44
+msgid "Developer Relations Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):45
+msgid "Documentation Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):46
+msgid "Hardened Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):47
+msgid "Infrastructure Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):48
+msgid "Metastructure Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):49
+msgid "Public Relations Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):50
+msgid "Release Engineering Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):51
+msgid "Security Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):52
+msgid "Gentoo Forums Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):53
+msgid "Gentoo Overlays Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):56
+msgid "/doc/en/metadoc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):57
+msgid "/doc/en/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):58
+msgid "/doc/en/list.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):59
+msgid "/doc/en/overview.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):60
+msgid "/doc/en/doc-languages.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):61
+msgid "/doc/en/inserts.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):62
+msgid "/main/en/name-logo.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):63
+msgid "/doc/en/articles/prompt-magic.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):64
+msgid "/doc/en/articles/bash-by-example-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):65
+msgid "/doc/en/articles/bash-by-example-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):66
+msgid "/doc/en/articles/bash-by-example-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):67
+msgid "/doc/en/articles/making-the-distro-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):68
+msgid "/doc/en/articles/making-the-distro-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):69
+msgid "/doc/en/articles/making-the-distro-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):70
+msgid "/doc/en/articles/lpi-101-fundamentals-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):71
+msgid "/doc/en/articles/lpi-101-administration-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):72
+msgid "/doc/en/articles/lpi-101-intermediate-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):73
+msgid "/doc/en/articles/lpi-101-advanced-p4.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):74
+msgid "/doc/en/articles/dynamic-iptables-firewalls.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):75
+msgid "/doc/en/articles/l-sed1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):76
+msgid "/doc/en/articles/l-sed2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):77
+msgid "/doc/en/articles/l-sed3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):78
+msgid "/doc/en/articles/l-awk1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):79
+msgid "/doc/en/articles/l-awk2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):80
+msgid "/doc/en/articles/l-awk3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):81
+msgid "/doc/en/articles/l-posix1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):82
+msgid "/doc/en/articles/l-posix2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):83
+msgid "/doc/en/articles/l-posix3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):84
+msgid "/doc/en/articles/linux-24-stateful-fw-design.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):85
+msgid "/doc/en/articles/afig-ct-ext3-intro.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):86
+msgid "/doc/en/articles/hardware-stability-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):87
+msgid "/doc/en/articles/hardware-stability-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):88
+msgid "/doc/en/articles/partitioning-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):89
+msgid "/doc/en/articles/partitioning-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):90
+msgid "/doc/en/articles/partition-planning-tips.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):91
+msgid "/doc/en/articles/maximum-swappage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):92
+msgid "/doc/en/articles/lvm-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):93
+msgid "/doc/en/articles/lvm-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):94
+msgid "/doc/en/articles/software-raid-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):95
+msgid "/doc/en/articles/software-raid-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):96
+msgid "/doc/en/articles/linux-kernel-compiling.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):97
+msgid "/doc/en/articles/openssh-key-management-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):98
+msgid "/doc/en/articles/openssh-key-management-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):99
+msgid "/doc/en/articles/openssh-key-management-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):100
+msgid "/doc/en/articles/l-afig-p8.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):101
+msgid "/doc/en/articles/samba-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):102
+msgid "/doc/en/articles/samba-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):103
+msgid "/doc/en/articles/samba-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):104
+msgid "/doc/en/articles/l-redesign-1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):105
+msgid "/doc/en/articles/l-redesign-2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):106
+msgid "/doc/en/articles/l-redesign-3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):107
+msgid "/doc/en/articles/l-redesign-4.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):108
+msgid "/doc/en/articles/autotools-practices.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):109
+msgid "/doc/en/bugzilla-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):110
+msgid "/doc/en/mysql-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):111
+msgid "/doc/en/postgres-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):112
+msgid "/doc/en/bluetooth-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):113
+msgid "/doc/en/utf-8.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):114
+msgid "/doc/en/cron-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):115
+msgid "/doc/en/ldap-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):116
+msgid "/doc/en/nvidia-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):117
+msgid "/doc/en/ati-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):118
+msgid "/doc/en/cvs-tutorial.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):119
+msgid "/doc/en/devfs-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):120
+msgid "/doc/en/distcc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):121
+msgid "/doc/en/cross-compiling-distcc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):122
+msgid "/doc/en/dri-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):123
+msgid "/doc/en/ebuild-submit.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):124
+msgid "/doc/en/gentoo-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):125
+msgid "/doc/en/migration-to-2.6.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):126
+msgid "/doc/en/altinstall.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):127
+msgid "/doc/en/faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):128
+msgid "/doc/en/gentoo-alpha-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):129
+msgid "/doc/en/gentoo-amd64-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):130
+msgid "/doc/en/handbook/handbook-alpha.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):131
+msgid "/doc/en/handbook/handbook-amd64.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):132
+msgid "/doc/en/handbook/handbook-arm.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):133
+msgid "/doc/en/handbook/handbook-hppa.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):134
+msgid "/doc/en/handbook/handbook-ia64.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):135
+msgid "/doc/en/handbook/handbook-mips.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):136
+msgid "/doc/en/handbook/handbook-ppc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):137
+msgid "/doc/en/handbook/handbook-ppc64.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):138
+msgid "/doc/en/handbook/handbook-sparc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):139
+msgid "/doc/en/handbook/handbook-x86.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):140
+msgid "/doc/en/handbook/hb-portage-branches.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):141
+msgid "/doc/en/handbook/hb-install-about.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):142
+msgid "/doc/en/handbook/hb-install-alpha-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):143
+msgid "/doc/en/handbook/hb-install-alpha-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):144
+msgid "/doc/en/handbook/hb-install-alpha-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):145
+msgid "/doc/en/handbook/hb-install-alpha-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):146
+msgid "/doc/en/handbook/hb-install-arm-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):147
+msgid "/doc/en/handbook/hb-install-arm-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):148
+msgid "/doc/en/handbook/hb-install-arm-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):149
+msgid "/doc/en/handbook/hb-install-arm-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):150
+msgid "/doc/en/handbook/hb-install-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):151
+msgid "/doc/en/handbook/hb-install-finalise.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):152
+msgid "/doc/en/handbook/hb-install-hppa-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):153
+msgid "/doc/en/handbook/hb-install-hppa-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):154
+msgid "/doc/en/handbook/hb-install-hppa-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):155
+msgid "/doc/en/handbook/hb-install-hppa-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):156
+msgid "/doc/en/handbook/hb-install-ia64-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):157
+msgid "/doc/en/handbook/hb-install-ia64-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):158
+msgid "/doc/en/handbook/hb-install-ia64-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):159
+msgid "/doc/en/handbook/hb-install-mips-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):160
+msgid "/doc/en/handbook/hb-install-mips-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):161
+msgid "/doc/en/handbook/hb-install-mips-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):162
+msgid "/doc/en/handbook/hb-install-mips-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):163
+msgid "/doc/en/handbook/hb-install-mips-stage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):164
+msgid "/doc/en/handbook/hb-install-mips-system.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):165
+msgid "/doc/en/handbook/hb-install-network.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):166
+msgid "/doc/en/handbook/hb-install-next.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):167
+msgid "/doc/en/handbook/hb-install-ppc-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):168
+msgid "/doc/en/handbook/hb-install-ppc-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):169
+msgid "/doc/en/handbook/hb-install-ppc-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):170
+msgid "/doc/en/handbook/hb-install-ppc-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):171
+msgid "/doc/en/handbook/hb-install-ppc64-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):172
+msgid "/doc/en/handbook/hb-install-ppc64-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):173
+msgid "/doc/en/handbook/hb-install-ppc64-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):174
+msgid "/doc/en/handbook/hb-install-ppc64-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):175
+msgid "/doc/en/handbook/hb-install-sparc-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):176
+msgid "/doc/en/handbook/hb-install-sparc-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):177
+msgid "/doc/en/handbook/hb-install-sparc-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):178
+msgid "/doc/en/handbook/hb-install-sparc-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):179
+msgid "/doc/en/handbook/hb-install-stage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):180
+msgid "/doc/en/handbook/hb-install-tools.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):181
+msgid "/doc/en/handbook/hb-install-x86+amd64-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):182
+msgid "/doc/en/handbook/hb-install-x86+amd64-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):183
+msgid "/doc/en/handbook/hb-install-x86+amd64-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):184
+msgid "/doc/en/handbook/hb-install-x86+amd64-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):185
+msgid "/doc/en/handbook/hb-install-blockdevices.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):186
+msgid "/doc/en/handbook/hb-install-bootconfig.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):187
+msgid "/doc/en/handbook/hb-install-filesystems.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):188
+msgid "/doc/en/handbook/hb-install-kernelmodules.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):189
+msgid "/doc/en/handbook/hb-install-kernelparams.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):190
+msgid "/doc/en/handbook/hb-working-features.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):191
+msgid "/doc/en/handbook/hb-working-portage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):192
+msgid "/doc/en/handbook/hb-working-rcscripts.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):193
+msgid "/doc/en/handbook/hb-working-use.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):194
+msgid "/doc/en/handbook/hb-working-variables.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):195
+msgid "/doc/en/handbook/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):196
+msgid "/doc/en/handbook/hb-install-system.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):197
+msgid "/doc/en/handbook/hb-portage-configuration.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):198
+msgid "/doc/en/handbook/hb-portage-diverttree.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):199
+msgid "/doc/en/handbook/hb-portage-files.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):200
+msgid "/doc/en/handbook/hb-portage-tools.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):201
+msgid "/doc/en/handbook/hb-net-advanced.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):202
+msgid "/doc/en/handbook/hb-net-functions.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):203
+msgid "/doc/en/handbook/hb-net-management.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):204
+msgid "/doc/en/handbook/hb-net-modules.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):205
+msgid "/doc/en/handbook/hb-net-start.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):206
+msgid "/doc/en/handbook/hb-net-wireless.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):207
+msgid "/doc/en/lvm2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):208
+msgid "/doc/en/gentoo-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):209
+msgid "/doc/en/gentoo-ppc-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):210
+msgid "/doc/en/alsa-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):211
+msgid "/doc/en/xorg-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):212
+msgid "/doc/en/quick-samba-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):213
+msgid "/doc/en/ltsp.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):214
+msgid "/doc/en/gentoolkit.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):215
+msgid "/doc/en/gnupg-user.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):216
+msgid "/doc/en/ipv6.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):217
+msgid "/doc/en/guide-localization.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):218
+msgid "/doc/en/guide-to-mutt.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):219
+msgid "/doc/en/uml.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):220
+msgid "/doc/en/java.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):221
+msgid "/doc/en/openafs.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):222
+msgid "/proj/en/desktop/kde/kde4-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):223
+msgid "/doc/en/nano-basics-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):224
+msgid "/doc/en/shoutcast-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):225
+msgid "/doc/en/vdr-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):226
+msgid "/doc/en/xml-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):227
+msgid "/doc/en/diskless-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):228
+msgid "/doc/en/prelink-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):229
+msgid "/doc/en/printing-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):230
+msgid "/doc/en/rsync.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):231
+msgid "/doc/en/qmail-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):232
+msgid "/doc/en/source_mirrors.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):233
+msgid "/doc/en/gentoo-x86-quickinstall.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):234
+msgid "/doc/en/gentoo-x86-quickinstall-after-reboot.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):235
+msgid "/doc/en/gentoo-x86-quickinstall-media.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):236
+msgid "/doc/en/gentoo-x86-quickinstall-stage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):237
+msgid "/doc/en/gentoo-x86-quickinstall-system.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):238
+msgid "/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):239
+msgid "/doc/en/vi-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):240
+msgid "/doc/en/virt-mail-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):241
+msgid "/doc/en/mailfilter-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):242
+msgid "/doc/en/genkernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):243
+msgid "/doc/en/gentoo-sparc-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):244
+msgid "/doc/en/mips-requirements.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):245
+msgid "/doc/en/udev-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):246
+msgid "/doc/en/gentoo-x86-tipsntricks.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):247
+msgid "/doc/en/gentoo-sparc-netboot-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):248
+msgid "/doc/en/gentoo-sparc-obpreference.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):249
+msgid "/doc/en/gnome-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):250
+msgid "/proj/en/desktop/gnome/howtos/gnome-2.26-upgrade.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):251
+msgid "/doc/en/gpm.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):252
+msgid "/doc/en/home-router-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):253
+msgid "/doc/en/arm-requirements.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):254
+msgid "/doc/en/power-management-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):255
+msgid "/doc/en/new-upgrade-to-gentoo-1.4.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):256
+msgid "/doc/en/portage-utils.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):257
+msgid "/proj/en/base/amd64/howtos/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):258
+msgid "/proj/en/base/amd64/howtos/bugs.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):259
+msgid "/proj/en/base/amd64/howtos/chroot-old.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):260
+msgid "/proj/en/base/amd64/howtos/fpic-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):261
+msgid "/proj/en/devrel/handbook/handbook.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):262
+msgid "/proj/en/gdp/doc/doc-policy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):263
+msgid "/proj/en/gdp/doc/doc-tipsntricks.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):264
+msgid "/proj/en/gdp/doc/handbook-release.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):265
+msgid "/proj/en/gdp/doc/gorg.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):266
+msgid "/main/en/about.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):267
+msgid "/main/en/philosophy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):268
+msgid "/main/en/contract.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):269
+msgid "/main/en/contact.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):270
+msgid "/main/en/graphics.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):271
+msgid "/main/en/irc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):272
+msgid "/main/en/lists.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):273
+msgid "/main/en/shots.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):274
+msgid "/main/en/sponsors.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):275
+msgid "/main/en/support.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):276
+msgid "/main/en/where.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):277
+msgid "/proj/en/site.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):278
+msgid "/doc/en/kernel-upgrade.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):279
+msgid "/proj/en/desktop/x/x11/modular-x-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):280
+msgid "/proj/en/desktop/x/x11/porting-modular-x-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):281
+msgid "/proj/en/desktop/x/x11/xorg-server-1.6-upgrade-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):282
+msgid "/proj/en/devrel/policy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):283
+msgid "/proj/en/gdp/doc/translators-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):284
+msgid "/proj/en/hardened/primer.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):285
+msgid "/proj/en/hardened/hardenedfaq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):286
+msgid "/proj/en/hardened/hardenedxorg.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):287
+msgid "/proj/en/hardened/pax-quickstart.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):288
+msgid "/proj/en/hardened/grsecurity.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):289
+msgid "/proj/en/hardened/capabilities.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):290
+msgid "/proj/en/hardened/selinux/selinux-handbook.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):291
+msgid "/proj/en/hardened/rsbac/overview.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):292
+msgid "/proj/en/hardened/rsbac/quickstart.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):293
+msgid "/proj/en/infrastructure/dev-email.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):294
+msgid "/proj/en/infrastructure/cvs-sshkeys.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):295
+msgid "/proj/en/infrastructure/dev-machines.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):296
+msgid "/proj/en/infrastructure/server-specs.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):297
+msgid "/proj/en/infrastructure/tenshi/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):298
+msgid "/proj/en/infrastructure/config-ntp.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):299
+msgid "/proj/en/infrastructure/config-ssh.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):300
+msgid "/proj/en/infrastructure/config-syslog.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):301
+msgid "/proj/en/infrastructure/dev-webspace.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):302
+msgid "/proj/en/infrastructure/faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):303
+msgid "/proj/en/infrastructure/mirrors-rsync.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):304
+msgid "/proj/en/metastructure/projectxml.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):305
+msgid "/proj/en/pr/docs/howto-presentation.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):306
+msgid "/proj/en/releng/catalyst/faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):307
+msgid "/proj/en/releng/installer/design.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):308
+msgid "/proj/en/releng/docs/release_guidelines.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):309
+msgid "/proj/en/releng/release/2004.0/releng/profile-update.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):310
+msgid "/proj/en/forums/forum-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):311
+msgid "/security/en/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):312
+msgid "/security/en/vulnerability-policy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):313
+msgid "/security/en/coordinator_guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):314
+msgid "/security/en/padawans.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):315
+msgid "/security/en/bug-searching.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):316
+msgid "/doc/en/keychain-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):317
+msgid "/proj/en/gdp/doc/metadoc-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):318
+msgid "/doc/en/hpc-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):319
+msgid "/proj/en/base/embedded/gnap-userguide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):320
+msgid "/doc/en/grub-error-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):321
+msgid "/doc/en/usb-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):322
+msgid "/doc/en/liveusb.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):323
+msgid "/doc/en/fluxbox-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):324
+msgid "/proj/en/vps/vserver-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):325
+msgid "/doc/en/security/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):326
+msgid "/doc/en/security/security-handbook.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):327
+msgid "/doc/en/security/shb-chroot.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):328
+msgid "/doc/en/security/shb-firewalls.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):329
+msgid "/doc/en/security/shb-intrusion.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):330
+msgid "/doc/en/security/shb-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):331
+msgid "/doc/en/security/shb-limits.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):332
+msgid "/doc/en/security/shb-logging.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):333
+msgid "/doc/en/security/shb-mounting.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):334
+msgid "/doc/en/security/shb-pam.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):335
+msgid "/doc/en/security/shb-perms.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):336
+msgid "/doc/en/security/shb-pre.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):337
+msgid "/doc/en/security/shb-tcp.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):338
+msgid "/doc/en/security/shb-services.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):339
+msgid "/doc/en/security/shb-tight.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):340
+msgid "/doc/en/security/shb-uptodate.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):341
+msgid "/proj/en/apache/doc/troubleshooting.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):342
+msgid "/proj/en/apache/doc/upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):343
+msgid "/proj/en/apache/doc/developer.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):344
+msgid "/doc/en/sudo-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):345
+msgid "/doc/en/gentoo-freebsd.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):346
+msgid "/doc/en/gentoo-mips-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):347
+msgid "/doc/en/mysql-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):348
+msgid "/doc/en/mysql-upgrade-slotted.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):349
+msgid "/doc/en/gcc-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):350
+msgid "/proj/en/base/x86/arch-testers-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):351
+msgid "/doc/en/jffnms.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):352
+msgid "/doc/en/conky-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):353
+msgid "/doc/en/man-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):354
+msgid "/doc/en/info-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):355
+msgid "/proj/en/java/java-upgrade.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):356
+msgid "/doc/en/kernel-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):357
+msgid "/doc/en/zsh.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):358
+msgid "/doc/en/change-chost.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):359
+msgid "/doc/en/xfce-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):360
+msgid "/doc/en/openbox.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):361
+msgid "/doc/en/lxde-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):362
+msgid "/doc/en/gcc-optimization.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):363
+msgid "/doc/en/vpnc-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):364
+msgid "/proj/en/qa/autofailure.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):365
+msgid "/proj/en/qa/automagic.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):366
+msgid "/proj/en/qa/backtraces.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):367
+msgid "/proj/en/portage/doc/manually-fixing-portage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):368
+msgid "/doc/en/xen-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):369
+msgid "/proj/en/overlays/userguide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):370
+msgid "/proj/en/overlays/devguide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):371
+msgid "/proj/en/overlays/policy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):372
+msgid "/proj/en/base/pam/upgrade-0.99.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):373
+msgid "/proj/en/base/embedded/handbook/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):374
+msgid "/proj/en/tex/texlive-migration-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):375
+msgid "/doc/en/openrc-migration.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):376
+msgid "/doc/en/multipath.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):377
+msgid "/doc/en/bind-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):378
+msgid "/doc/en/logcheck.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):379
+msgid "/proj/en/qa/devmanual.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):383 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):697 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):705 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):708 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):711 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):715 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):719 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):723 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1006 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1046 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1077 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1080
+msgid "gentoodev_docs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):386 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):527 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):726 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):729 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):732 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):735 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):738 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):741 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):744 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):747 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):750 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):753 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):756 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):759 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):762 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):765
+msgid "other"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):389 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):392 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):395 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):407 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):410 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):413 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):416 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):485 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):488 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):491 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):494 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):497 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):500 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):503 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):506 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):509 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):512 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):515 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):518 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):521 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):524
+msgid "articles_linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):398 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):401 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):404
+msgid "articles_gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):419 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):422 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):425 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):428 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):431 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):434 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):437 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):440 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):443 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):446 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):449 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):452 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):455 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):458 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):461 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):464 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):467 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):470 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):473
+msgid "articles_commth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):476 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):479 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):482
+msgid "articles_others"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):530 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):533 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):645 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):648 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):651 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):654 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):657 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):660 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):664 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):667 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):673 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):676 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):679 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):682 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):685 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):688 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):691 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):694 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):798 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):808 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):849 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):856 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):860 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):863 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):972 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):978 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):999 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1002 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1019 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1023 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1027 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1031 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1053 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1056 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1083 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1089 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1111
+msgid "sysadmin_specific"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):536 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):540 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):663 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):801 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):807 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):811 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):815 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):818 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):821 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1059
+msgid "desktop_config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):539 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):633 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):636 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):639 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):642 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):812 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):842 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):845 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1009 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1062 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1065 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1071 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1074
+msgid "sysadmin_general"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):543 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):546 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):549 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1012
+msgid "install_guides"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):552 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):981 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):984 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1013 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1035
+msgid "project_base"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):555 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):558 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):561 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):564 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):567 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1016
+msgid "faq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):570 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):573 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):576 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):579 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):583 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):587 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):591 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):987 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):990 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):993 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):996
+msgid "install_other"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):580 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):584 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):588 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):846 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):857 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1003 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1020 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1024 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1028 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1032 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1039 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1043 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1050 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1068 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1105 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1108
+msgid "upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):594 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):599 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):604 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):609 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):614 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):617 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1086 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1093
+msgid "gentoo_portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):620 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):625
+msgid "gentoo_configuring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):630
+msgid "gentoo_choices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):669
+msgid "68740"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):698 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):867
+msgid "project_devrel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):701 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):866 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):946 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):956
+msgid "gentoodev_policies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):702 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):712 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):716 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):720 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):870 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):975
+msgid "project_gdp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):768 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):771 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):774 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):780 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):783 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):786 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):789 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):792 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):795 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1038 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1042 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1049
+msgid "desktop_install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):776
+msgid "83806"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):803
+msgid "48733"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):824 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):827 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):830 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):833 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):836 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):839 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):971
+msgid "desktop_apps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):851
+msgid "102481"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):852
+msgid "115130"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):873 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):876 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):879 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):882 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):885 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):888 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):891 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):894 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):897
+msgid "project_hardened"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):900 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):903 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):906 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):909 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):912 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):915 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):918 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):921 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):924 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):927 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):930
+msgid "project_infra"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):933
+msgid "project_metastructure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):936
+msgid "project_pr"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):939 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):942 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):945 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):949
+msgid "project_releng"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):952 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):955 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):959 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):962 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):965
+msgid "project_security"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):968
+msgid "project_forums"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1092 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1096 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1100
+msgid "project_overlays"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1097 ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1101
+msgid "gentdev_docs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1102
+msgid "gentdev_policies"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/migration-to-2.6.xml.pot b/doc/gettext/migration-to-2.6.xml.pot
new file mode 100644
index 0000000..eb80d10
--- /dev/null
+++ b/doc/gettext/migration-to-2.6.xml.pot
@@ -0,0 +1,1059 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(guide:link):5
+msgid "/doc/en/migration-to-2.6.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):6
+msgid "The complete Gentoo Linux 2.6 migration guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):9
+msgid "dsd@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):9
+msgid "Daniel Drake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):14
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):12
+msgid "sergey_zlodey@mail.ru"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):12
+msgid "Sergey Galkin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):15
+msgid "svyatogor@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):15
+msgid "Sergey Kuleshov"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):18
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):18
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):21
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):21
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(abstract):24
+msgid "This document will aid you in the process of migrating from Linux 2.4 to Linux 2.6, devfs to udev, OSS to ALSA, and LVM to LVM2."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(version):29
+msgid "0.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(date):30
+msgid "2008-03-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):33
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):35
+msgid "What is new in Linux 2.6?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):38
+msgid "That is not an easy question to answer. Linux 2.6 is the result of over 2 years of rapid development and stabilisation of new features, and is architecturally quite different from its 2.4 counterpart. Some of the major changes are listed below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):46
+msgid "Scheduler/Interactivity improvements: Linux feels very smooth on desktop systems and copes much better than 2.4 while under load"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):50
+msgid "Scalability: Linux now scales much better at both ends - on small embedded devices and also systems with many processors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):54
+msgid "Performance: Throughput from common applications is much improved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):55
+msgid "Hardware support: Linux now supports many more architectures and hardware devices out-of-the-box than any other operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):61
+msgid "Joseph Pranevich has written a very detailed document, <uri link=\"http://www.kniggit.net/wwol26.html\">The Wonderful World Of Linux 2.6</uri> which you may be interested to glance over. If you are interested in the more technical details, you can refer to <uri link=\"http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt\">The post-halloween document</uri> - but do bear in mind that this is somewhat outdated now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):74
+msgid "Gentoo and 2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):77
+msgid "From the 2005.0 release of Gentoo Linux, the default kernel is the latest 2.6 series kernel. The default profile of the system is picked up from <path>/etc/make.profile</path> which on 2005.0 or above would be a symlink to <path>/usr/portage/profiles/default-linux/x86/2005.0</path> under which various important settings are taken care of."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):85
+msgid "If you are using a 2.4 profile, please change it to one that supports a 2.6 kernel by doing the following."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):90
+msgid "Changing your profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):90
+#, no-wrap
+msgid "\n# <i>rm -f /etc/make.profile</i>\n# <i>ln -snf /usr/portage/profiles/default-linux/x86/2005.1 /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):98
+msgid "What is udev?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):101
+msgid "In the past, Gentoo has instructed users to use <e>devfs</e> for managing the <path>/dev</path> directory, which contains a series of device interfaces to allow system applications to communicate with hardware (through the kernel)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):107
+msgid "<e>devfs</e>, whilst a good concept, has some internal problems, and has been completely removed from the main stable tree as of 2.6.13."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):112
+msgid "<e>udev</e> is the new way of managing device nodes. It addresses issues with previous device managers, and also attempts to solve some other problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):117
+msgid "The above may not mean much to you, but fear not, the hard working Gentoo developers have put effort into making the migration from devfs very easy. Please read the <uri link=\"/doc/en/udev-guide.xml\">Gentoo udev Guide</uri> for more information regarding the same."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):127
+msgid "What is ALSA?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):130
+msgid "With Linux 2.4, chances are that you used OSS (open sound system) drivers to power your sound card. OSS has been replaced by a newer and better set of sound drivers: ALSA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):136
+msgid "ALSA, the Advanced Linux Sound Architecture, is a new set of sound drivers with a new and improved API, present in the Linux 2.6 kernel. It is backwards compatible with OSS applications, provided that you select the right kernel configuration options!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):143
+msgid "If you do not have any sound/audio hardware, you can safely skip over any ALSA-related instructions in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):151
+msgid "What is LVM?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):154
+msgid "<e>Logical Volume Management</e> (LVM) exists as set of tools allowing you to manage your disk storage in a very flexible manner. Amongst other things, it allows powerful control over partitions (e.g. resizing without reboot), and makes operations like device changes relatively simple. LVM acts as an alternative to standard partition-based disk management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):162
+msgid "LVM support has historically been implemented in Linux 2.4. Linux 2.6 features a new version of LVM, named <e>LVM2</e>. The migration process requires you to install new versions of the user-level tools (covered later in this document) but will leave your data intact!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):169
+msgid "<e>If you do not currently use LVM for data-storage management, then LVM2 migration does not apply to you.</e> If this is the case, you can safely ignore any parts of this document referencing LVM/LVM2. Upgrading to Linux 2.6 does <e>not</e> require you to store your data on LVM partitions - you can keep your data in the standard partition-format as it always has been."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):177
+msgid "If you are not a LVM user, but you think LVM2 sounds useful for you, you can convert your disks to this format at a later date, by following the <uri link=\"/doc/en/lvm2.xml\">Gentoo LVM2 Installation Guide</uri>. For now, let us just concentrate on getting a smooth 2.6 migration underway."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):189
+msgid "Preparation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):191
+msgid "Get your system up-to-date"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):194
+msgid "Some of the changes brought in with Linux 2.6 also required some changes in the base system applications. Before continuing, you should ensure that your system is relatively up-to-date, and to be perfectly sure, you should update all world and system packages where updates are available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):201
+msgid "In particular, make sure you have the latest stable versions of the following packages:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):209
+msgid "<c>sys-kernel/genkernel</c> (only if you wish to use genkernel as opposed to manual configuration)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):215
+msgid "Updating all world packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):215
+#, no-wrap
+msgid "\n# <i>emerge --sync</i>\n# <i>emerge -ua world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):223
+msgid "modutils vs module-init-tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):226
+msgid "<c>sys-apps/modutils</c> is the package that provides tools such as <c>modprobe</c>, <c>rmmod</c> and <c>insmod</c> for Linux 2.4."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):231
+msgid "Linux 2.6 introduces a new module format, and therefore requires new tools for handling modules. These are bundled up into the <c>sys-apps/module-init-tools</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):237
+msgid "You should now remove modutils and install module-init-tools:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):241
+msgid "Switching from modutils to module-init-tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):241
+#, no-wrap
+msgid "\n# <i>emerge --unmerge sys-apps/modutils</i>\n# <i>emerge module-init-tools</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):246
+msgid "Don't worry - even though you have just unmerged modutils, module-init-tools provides backwards compatibility for Linux 2.4, so you will still be able to boot into Linux 2.4 and handle modules for that kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):252
+msgid "For the above reason, module-init-tools might already be installed and working with your existing Linux 2.4 kernel. In this case, you don't need to worry about this stage - your system is already ready to deal with Linux 2.6 modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):261 ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):269
+msgid "Installing udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):264
+msgid "There is no configuration involved here. Simply use <c>emerge</c> to install udev:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):269
+#, no-wrap
+msgid "\n# <i>emerge -a udev</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):273
+msgid "You should now read the <uri link=\"/doc/en/udev-guide.xml\">Gentoo udev Guide</uri> to get a more complete idea about the differences between udev and devfs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):282
+msgid "Checking for essential device nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):285
+msgid "When the system boots up, the system requires some essential device nodes. As udev is not included in the kernel, it is not activated immediately. To work around this, you must ensure that you have some essential device nodes on your disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):292
+msgid "Our installation stage files will have created the required devices during the initial installation. However, some users have reported that this is not the case. We will use this opportunity to check that the device files exist, and create them if they do not."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):299
+msgid "As your existing device manager will be mounted at <path>/dev</path>, we cannot access it directly. So we will bind-mount your root partition to another location and access the <path>/dev</path> directory from there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):305
+msgid "Bind-mounting your root partition and listing static devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):305
+#, no-wrap
+msgid "\n# <i>mkdir -p /mnt/temp</i>\n# <i>mount -o bind / /mnt/temp</i>\n# <i>cd /mnt/temp/dev</i>\n# <i>ls -l console null</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):312
+msgid "If the above <e>ls</e> command reported that either <c>console</c> or <c>null</c> do not exist, then you must create them yourself, as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):317
+msgid "Creating the missing console and null nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):317
+#, no-wrap
+msgid "\n# <i>mknod -m 660 console c 5 1</i>\n# <i>mknod -m 660 null c 1 3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):322
+msgid "You should now unmount your bind-mounted root partition, even if you did not have to create those devices:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):327
+msgid "Unmounting the bind-mounted root"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):327
+#, no-wrap
+msgid "\n# <i>cd</i>\n# <i>umount /mnt/temp</i>\n# <i>rmdir /mnt/temp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):336
+msgid "Installing ALSA utilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):339
+msgid "ALSA requires you to have some packages installed, so that applications can use the ALSA API. These packages will also allow you to control the mixer and volume levels. Install the required utilities as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):345
+msgid "Installing ALSA utilities and libraries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):345
+#, no-wrap
+msgid "\n# <i>emerge -a alsa-lib alsa-utils alsa-tools alsa-headers alsa-oss</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):354
+msgid "Installing the Linux 2.6 sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):357
+msgid "Choosing and installing a kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):360
+msgid "The first thing you need to do is install sources of a 2.6 kernel of your choice. The two Gentoo-supported 2.6 kernels are currently <e>gentoo-sources</e> (for desktops) and <e>hardened-sources</e> (for servers). There are others available, see the <uri link=\"/doc/en/gentoo-kernel.xml\">Gentoo Linux Kernel Guide</uri> for more choices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):369
+msgid "In this guide, we'll use <c>gentoo-sources</c> as an example. Install your chosen set of kernel sources using the <c>emerge</c> utility:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):374
+msgid "Installing gentoo-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):374
+#, no-wrap
+msgid "\n# <i>emerge -a gentoo-sources</i>\nThese are the packages that I would merge, in order:\nCalculating dependencies ...done!\n[ebuild  NS   ] sys-kernel/gentoo-sources-2.6.10-r4\n\nDo you want me to merge these packages? [Yes/No] <i>y</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):383
+msgid "When performing the above <c>emerge</c> command, if you find that it wants to install a 2.4 version of gentoo-sources (e.g. <c>gentoo-sources-2.4.26</c>), then it means that the profile you are using is not designed for Linux 2.6 users. Please follow the <uri link=\"/doc/en/gentoo-upgrading.xml\">Gentoo Upgrading Document</uri> to switch to a 2.6-based profile, and retry installing 2.6 kernel sources."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):395
+msgid "Updating the /usr/src/linux symbolic link"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):398
+msgid "Various components of the Gentoo utilities rely on <path>/usr/src/linux</path> being a symbolic link to the kernel sources that you are running (or wish to compile against)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):404
+msgid "We will now update our <path>/usr/src/linux</path> link to point at the kernel sources we just installed. Continuing our example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):409
+msgid "Updating the /usr/src/linux softlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):409
+#, no-wrap
+msgid "\n# <i>cd /usr/src</i>\n# <i>ln -sfn linux-2.6.10-gentoo-r4 linux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):419
+msgid "Known pitfalls with Linux 2.6 migration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):423
+msgid "Before we get stuck into configuring the kernel, I'll attempt to detail the most common errors that people make when migrating to Linux 2.6, as some of these points will influence the way you configure the new kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):429
+msgid "Not all of these points are relevant at this stage, but I will detail them all here in one place, and you can refer back at your leisure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):437
+msgid "Don't use \"make oldconfig\" with a 2.4 .config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):440
+msgid "If you don't understand what this means, don't worry, you won't make this mistake if you follow the rest of this guide correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):445
+msgid "You'll be asked many many questions, since there have been a large amount of changes. Many people who do try a <c>make oldconfig</c> from a 2.4 config end up creating an unworkable kernel (e.g. no output on-screen, no input from keyboard, etc). Please save yourself the trouble, and use the traditional <c>menuconfig</c> configuration method just this once."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):456
+msgid "Don't use ide-scsi for CD/DVD writing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):459
+msgid "In Linux 2.4, the only way to achieve good CD/DVD writing results was to enable the (rather ugly) <c>ide-scsi</c> emulation. Thankfully, the IDE layer in Linux 2.6 has been extended to support CD/DVD writers much better."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):465
+msgid "You don't need to enable any extra options to support CD writing. Just be sure <e>not</e> to enable <c>ide-scsi</c> as you used to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):473
+msgid "PC Speaker is now a configurable option"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):476
+msgid "You won't get your normal console beeps (or any response from the PC speaker at all) unless you specifically enable the new PC speaker option (<c>CONFIG_INPUT_PCSPKR</c>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):482
+msgid "Location of PC speaker option"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):482
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n Input device support  ---&gt;\n  [*] Misc\n   &lt;*&gt;   PC Speaker support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):489
+msgid "By \"PC speaker\", I am referring to the analogue speaker that beeps once when your system is powering up, I am not referring to normal sound hardware used for playing music, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):498
+msgid "New USB Storage block device driver sometimes problematic"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):501
+msgid "Very recently, a new USB storage device driver has been added to the kernel. At the time of writing, this driver (\"ub\") is still in its early stages and some users find it to be unreliable. If you have problems accessing your USB hard disk, USB flash disk, USB card reader, or USB digital camera, then you could try reverting to the older SCSI-style driver:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):509
+msgid "Disabling ub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):509
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n Block devices  ---&gt;\n  &lt; &gt; Low Performance USB Block driver\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):515
+msgid "The older SCSI-style driver (USB Mass Storage support) is enabled by default. It can be found under \"Device Drivers --&gt; USB support\", but will generally not come into effect while ub is also present."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):524
+msgid "usbdevfs renamed to usbfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):527
+msgid "If you have edited your <path>/etc/fstab</path> file to customise the way that the USB device filesystem gets mounted, you may have to modify the filesystem type from <e>usbdevfs</e> to <e>usbfs</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):533
+msgid "Recent 2.4 kernels will also allow you to use \"usbfs\" as well as \"usbdevfs\", so you are not breaking any backwards compatibility by doing this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):541
+msgid "Don't renice X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):544
+msgid "If you are a desktop 2.4 user, you may have hacked your system into running X at a higher priority, as in some cases it seems to provide better desktop performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):550
+msgid "There have been many scheduler changes in 2.6 which change this behaviour. If you continue to run X at a higher priority, it will do exactly what it is supposed to (run the <e>display server</e> at a very high priority) and you will notice consequences such as sound stuttering and slow application load times because your CPU is spending too long serving X and only X."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):558
+msgid "In Linux 2.6, you no longer need to renice desktop applications to get good interactivity. Please remove your \"niceness\" hacks!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):566
+msgid "X11 config file should now use /dev/input/mice for PS/2 and USB mice"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):569
+msgid "One of the changes that a default udev configuration introduces is different organisation of the mouse device nodes. Previously, you would have had nodes such as <path>/dev/psaux</path> and <path>/dev/mouse</path>. You will now have nodes such as <path>/dev/input/mouse0</path>, <path>/dev/input/mouse1</path>, and a collective <path>/dev/input/mice</path> node which combines movements from all mice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):578
+msgid "Since the old X configurations typically reference <path>/dev/mouse</path> or <path>/dev/psaux</path> then you may get an error similar to the one shown below when you attempt to start X11:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):584
+msgid "Common error when starting X on a udev system for the first time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):584
+#, no-wrap
+msgid "\n(EE) xf86OpenSerial: Cannot open device /dev/mouse\n  No such file or directory.\n(EE) Mouse0: cannot open input device\n(EE) PreInit failed for input device \"Mouse0\"\nNo core pointer\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):592
+msgid "To correct this, open your X11 config in a text editor, and update the mouse <e>InputDevice</e> section to use the <path>/dev/input/mice</path> device. An example is shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):598
+msgid "Opening your X11 config file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):598
+#, no-wrap
+msgid "\n# <i>nano -w /etc/X11/xorg.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):602
+msgid "If you are still using XFree86, your config file will be <path>/etc/X11/XF86Config</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):607
+msgid "Sample mouse InputDevice section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):607
+#, no-wrap
+msgid "\nSection \"InputDevice\"\n  Identifier  \"Mouse0\"\n  Driver      \"mouse\"\n  Option      \"Protocol\" \"auto\"\n  Option      \"Device\" \"/dev/input/mice\"\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):616
+msgid "If you are using a serial mouse, the new device path will be <path>/dev/tts/0</path> instead of <path>/dev/ttyS0</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):624
+msgid "New Serial-ATA (SATA) drivers name the devices differently"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):627
+msgid "If you used the original Serial ATA drivers under Linux 2.4, you probably observed your SATA devices having names such as <path>/dev/hde</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):632
+msgid "Linux 2.6 introduces some new SATA drivers (libata) which are based on the SCSI subsystem. As these drivers are based on SCSI, your SATA disks will now show up as SCSI devices. Your first SATA disk will be named <path>/dev/sda</path>. You will need to update your <path>/etc/fstab</path> file to reflect this, and you will need to bear this in mind when choosing the root/real_root kernel boot parameter later on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):641
+msgid "libata has been backported into recent versions of Linux 2.4, so you may already be familiar with the new device naming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):649
+msgid "bootsplash no longer maintained"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):652
+msgid "If you used the <c>gentoo-sources-2.4</c> kernel, you may have used the <e>bootsplash</e> functionality in order to provide yourself with a colourful framebuffer console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):658
+msgid "The developer of bootsplash appears to have lost interest in his project, given some design problems. However, Gentoo developer <e>Michał Januszewski</e> is developing a successor, <c>gensplash</c>, which in included in the gentoo-sources-2.6 kernel. You can follow Michał's <uri link=\"http://dev.gentoo.org/~spock/projects/gensplash/archive/gensplash-in-5-easy-steps.txt\"> Gensplash in 5 easy steps</uri> document in order to familiarize yourself with how gensplash is operated."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):671
+msgid "I2C drivers now included in the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):674
+msgid "If you use <c>lm-sensors</c> to monitor system temperatures and power levels, you previously needed to install the <c>i2c</c> package in order to provide hardware support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):680
+msgid "The I2C hardware drivers are now included in the Linux 2.6 kernel, no external i2c package is required. Remember to compile support for your specific I2C devices into the kernel configuration. You will then be able to use <c>lm-sensors</c> as usual."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):694
+msgid "Configuring, building, and installing the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):698
+msgid "As with Linux 2.4, you have two options for managing your new kernel build."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):703
+msgid "The default method is to configure your kernel manually. This may seem daunting but is the preferred way as long as you know your system. If you wish to configure your new kernel manually, please continue on to the <uri link=\"#manual\">next chapter</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):709
+msgid "The alternative option is to use our <c>genkernel</c> utility to automatically configure, compile, and install a kernel for you. If you wish to use <c>genkernel</c> then skip over the next chapter and proceed with <uri link=\"#genkernel\">using genkernel</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):722
+msgid "Default: Manual configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):724
+msgid "Configuring the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):727
+msgid "We'll now get on with configuring the kernel. Open menuconfig in the usual way:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):731
+msgid "Invoking menuconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):731
+#, no-wrap
+msgid "\n# <i>cd /usr/src/linux</i>\n# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):736
+msgid "You will probably be familiar with using menuconfig from configuring 2.4 kernels. Fortunately, the front end has barely changed at all, but you will observe much better organisation of kernel options, plus <e>many</e> new options that weren't present in 2.4."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):743
+msgid "Be sure to enable the following important kernel options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):747
+msgid "Required kernel options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):747
+#, no-wrap
+msgid "\nFile systems ---&gt;\n  Pseudo Filesystems ---&gt;\n    [*] /proc file system support\n    [*] Virtual memory file system support (former shm fs)\n\n<comment>(the following are required for udev):</comment>\nGeneral setup  ---&gt;\n [*] Support for hot-pluggable devices\n\n<comment>(the following are required for ALSA):</comment>\nDevice Drivers  ---&gt;\n Sound  ---&gt;\n  &lt;*&gt; Sound card support\n  Advanced Linux Sound Architecture  ---&gt;\n   &lt;M&gt; Advanced Linux Sound Architecture\n   &lt;M&gt; Sequencer support\n   &lt;M&gt; OSS Mixer API\n   [*] OSS Sequencer API\n<comment>   (and do not forget to select your soundcard from the submenus!)</comment>\n\n<comment>(the following are required if you use LVM for disk management):</comment>\nDevice Drivers  ---&gt;\n Multi-device support (RAID and LVM)  ---&gt;\n  [*] Multiple devices driver support (RAID and LVM)\n   &lt;*&gt;   Device mapper support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(warn):775
+msgid "Previously you may have included support for the <path>/dev</path> file system (now marked OBSOLETE). Do not enable devfs support. We have installed udev, which we will be using instead of devfs from now on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):781
+msgid "Also, remember to enable support for the filesystems that you use, and the hardware present in your system. Be sure to enable support for the IDE controller on your motherboard if you wish to benefit from fast DMA disk access. Refer to the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=7\">Configuring the Kernel</uri> section of the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> for additional guidance here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):794
+msgid "Building the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):797
+msgid "Now that we have configured the kernel, we can start the compilation process:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):801
+msgid "Compiling the kernel source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):801
+#, no-wrap
+msgid "\n# <i>make &amp;&amp; make modules_install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):805
+msgid "You may recall having to run <c>make dep</c> with Linux 2.4 sources. This is no longer required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):810
+msgid "Wait for the kernel compilation to complete (and observe the much more readable compilation output)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):818 ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):826
+msgid "Installing the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):821
+msgid "The next step is mounting your <path>/boot</path> partition and copying the kernel image over. You must then update your bootloader config manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):826
+#, no-wrap
+msgid "\n# <i>mount /boot</i>\n# <i>cp arch/i386/boot/bzImage /boot/bzImage-2.6.10-gentoo-r4</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):831
+msgid "Note that the above instructions are examples only, you should follow your usual procedure of updating kernels by following the instructions in the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> (see the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=7\">Configuring the Kernel</uri> chapter)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):839
+msgid "When updating your bootloader config, do not remove the old entry pointing at your 2.4 kernel. This way, you will easily be able to switch between the two if something is not working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):845
+msgid "Now continue onto the <uri link=\"#modules\">Module Configuration</uri> section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):854
+msgid "Alternative: Using genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):858
+msgid "If you prefer to use genkernel instead of manually configuring your kernel, you will be happy to hear that using genkernel to produce 2.6 kernels is very similar to the process you performed when producing your previous 2.4 kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):864
+msgid "You should invoke genkernel as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):868
+msgid "Invoking genkernel with some common arguments"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):868
+#, no-wrap
+msgid "\n# <i>genkernel --udev --menuconfig --bootloader=grub all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):872
+msgid "In the above example, we also take advantage of genkernel features to open menuconfig to allow you to customise the kernel configuration (if you wish), and to update the grub bootloader configuration after compilation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):878
+msgid "You should choose genkernel arguments that suit you, but do not forget to include the <c>--udev</c> argument! Refer to the <uri link=\"/doc/en/genkernel.xml\">Gentoo Linux Genkernel Guide</uri> and the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=7\">Configuring the Kernel</uri> chapter of the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> for additional information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):887
+msgid "If you choose to update your bootloader config yourself, then you must remember to include the <c>udev</c> kernel parameter. A sample <e>grub</e> config section is shown below, but remember to adjust the <e>real_root</e> parameter for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):894
+msgid "Sample GRUB config for genkernel + udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):894
+#, no-wrap
+msgid "\ntitle Gentoo Linux (2.6 kernel)\nroot (hd0,0)\nkernel /kernel-2.6.10-gentoo-r4 <i>udev</i> root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3\ninitrd /initrd-2.6.10-gentoo-r4\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):906
+msgid "Module Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):909
+msgid "Installing external modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):912
+msgid "Many users will additionally rely on kernel modules that are built outside of the kernel tree. Common examples are the binary ATI and Nvidia graphics drivers. You now need to install those modules, which will compile against the 2.6 sources found at <path>/usr/src/linux</path>. This is the usual case of <c>emerge packagename</c> for all the external modules you are used to using with 2.4."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):921
+msgid "Refer again to the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=7\">Configuring the Kernel</uri> chapter of the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> for more info."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):931
+msgid "Autoloading modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):934
+msgid "You may have decided to compile some kernel components as modules (as opposed to compiled directly into the kernel) and would like to have them autoloaded on bootup like you did with 2.4. Also, if you installed any external modules from the portage tree (as described above) you will probably want to autoload them too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):942
+msgid "You can achieve this similarly as to how you did with 2.4. Simply open up the file <path>/etc/modules.autoload.d/kernel-2.6</path> in a text editor and list the names of the modules you would like autoloaded."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):948
+msgid "Opening the module autoload list in nano"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):948
+#, no-wrap
+msgid "\n# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):952
+msgid "Sample autoload list to load the 3c59x and nvidia modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):952
+#, no-wrap
+msgid "\n# /etc/modules.autoload.d/kernel-2.6:  kernel modules to load when system boots.\n#\n# Note that this file is for 2.6 kernels.\n#\n# Add the names of modules that you'd like to load when the system\n# starts into this file, one per line. Comments begin with # and\n# are ignored. Read man modules.autoload for additional details.\n\n3c59x\nnvidia\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):970
+msgid "LVM to LVM2 migration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):972
+msgid "Upgrading to LVM2 tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):975
+msgid "If you do not use LVM to manage your disk storage, you can safely skip this chapter and skip onto the next."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):980
+msgid "Fortunately, upgrading from the LVM1 user tools to the LVM2 versions is very simple:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):985
+msgid "Upgrading user-tools from LVM1 to LVM2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):985
+#, no-wrap
+msgid "\n# <i>emerge --unmerge lvm-user</i>\n# <i>emerge lvm2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):990
+msgid "You will need to re-emerge <c>lvm-user</c> if you plan to go back to booting a 2.4 kernel, as <c>lvm2</c> by itself isn't enough for 2.4 kernels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1000
+msgid "Booting into Linux 2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1004
+msgid "It's now time to boot into Linux 2.6. Close all applications and reboot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1008
+msgid "Rebooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1008
+#, no-wrap
+msgid "\n# <i>umount /boot</i>\n# <i>reboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1013
+msgid "When you reboot, if you followed this document correctly so far, you will have the option of either loading Linux 2.4 or Linux 2.6 from your bootloader. Choose Linux 2.6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1019
+msgid "Once the system has booted, check that things are working. If you made a mistake in the kernel configuration, don't worry, you can skip back to the <uri link=\"#conf\">Configuring, building, and installing the kernel</uri> section, make your change, recompile and install new kernel image, reboot, and try again!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1030
+msgid "Configuring and unmuting ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1033
+msgid "We will now complete the ALSA configuration and unmute the audio channels. The ALSA packages provide a useful utility to make this process relatively simple:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1038
+msgid "Invoking the automatic ALSA configuration utility"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1038
+#, no-wrap
+msgid "\n# <i>alsaconf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1042
+msgid "The process is straightforward: allow the <e>/etc/modules.d/alsa</e> file to be automatically updated, and then allow ALSA to be reloaded. alsaconf will then terminate, however you will need to run it multiple times if you have multiple sound devices installed in your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1049
+msgid "You should now add <c>alsasound</c> to your boot runlevel, so that volumes will be saved on shutdown and restored on bootup:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1054
+msgid "Adding alsasound to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1054
+#, no-wrap
+msgid "\n# <i>rc-update add alsasound boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):1058
+msgid "The <c>alsaconf</c> utility chooses initial volume levels for your sound devices. If these are inappropriate, you can modify them at any time with the <c>alsamixer</c> utility."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1067
+msgid "Any immediate problems?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1070
+msgid "At this stage you should refer back to the <uri link=\"#pitfalls\">Known pitfalls with Linux 2.6 migration</uri> section which may be helpful with any issues you encounter immediately."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1081
+msgid "Header files and NPTL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1085
+msgid "By now you are running Linux 2.6 and hopefully have all issues ironed out. You should now update your Linux kernel header files and re-merge glibc so that userspace applications can take advantage of new Linux 2.6 features."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1091
+msgid "Updating to linux-headers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1091
+#, no-wrap
+msgid "\n# <i>emerge -u linux-headers</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1095
+msgid "After updating your headers package, you should generally re-merge glibc. There is a new feature here that you may be interested in - NPTL. NPTL is a new threading model present in Linux 2.6, which features much quicker thread create and destroy times. This won't make much of a difference to most systems, but you may wish to enable it during this migration process! To enable NPTL, edit <path>/etc/make.conf</path>, adding <e>nptl</e> to your USE variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(warn):1104
+msgid "If you choose to also enable the \"nptlonly\" flag, be aware that you will no longer be able to boot a 2.4 kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1109
+msgid "Now re-merge glibc (you should do this even if you did not choose to enable NPTL)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1114
+msgid "Reinstalling glibc against the new kernel headers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1114
+#, no-wrap
+msgid "\n# <i>emerge -a glibc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1118
+msgid "If you enabled NPTL, existing binaries will not use it until they are recompiled. However, any binaries compiled from this point onwards <e>will</e> use NPTL. You may wish to recompile all binaries now, e.g.:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1124
+msgid "Recompiling all packages on the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1124
+#, no-wrap
+msgid "\n# <i>emerge -e world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1128
+msgid "Alternatively, you can just let your system \"naturally\" convert itself to NPTL as you update to newer versions of packages when they are released."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1138
+msgid "Closing remarks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1140
+msgid "Problems?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1143
+msgid "With the incredible amount of work that went into Linux 2.6, it is sometimes inevitable that things which used to work fine, no longer function as expected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1148
+msgid "If you have any problems with your 2.6 kernel, and you can confirm that this problem does not exist with Linux 2.4, then please open a bug with us on our <uri link=\"http://bugs.gentoo.org\">Bugzilla</uri>. We will investigate the issue, and if we find that it is a problem in the mainline kernel, we may then ask you to file a report at the central kernel bugzilla."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1159
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1162
+msgid "Hopefully you have just completed a smooth migration and you are enjoying the benefits which Linux 2.6 brings over 2.4."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1167
+msgid "I would like to say a word of thanks to the many users who effectively 'tested' this document while it was in its early stages, and provided feedback about how the migration process went. Sorry that I did not reply to all the emails (there were a lot!), but I did read every one, and refined this document where appropriate. Enjoy your 2.6-enhanced systems :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1178
+msgid "Removing Linux 2.4 from your system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1181
+msgid "After you have been running 2.6 for a while, you may decide that you no longer have any requirement to be able to use Linux 2.4. The steps you can take to clean up your system are detailed below. <e>Only follow the procedure in this section if you are sure that you don't want/need to use 2.4 again!</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1188
+msgid "The 2.4 kernel source code can be removed, using the emerge utility as usual. For example, assuming you have 2.4 versions of vanilla-sources and gentoo-sources installed, you could use the following command to remove them while keeping the 2.6 versions intact:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1195
+msgid "Example: Removing Linux 2.4 sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1195
+#, no-wrap
+msgid "\n# <i>emerge --unmerge =vanilla-sources-2.4.* =gentoo-sources-2.4.*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1199
+msgid "Portage will not completely clean out your 2.4 kernel source installations, because some temporary files are created during compilation. It is safe to remove these remnants with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1205
+msgid "Removing remaining temporary files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1205
+#, no-wrap
+msgid "\n# <i>rm -rf /usr/src/linux-2.4.*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1209
+msgid "You can additionally remove modules and information files relating to your old 2.4 kernel installations, as these are no longer needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1214
+msgid "Removing previously-installed 2.4 modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1214
+#, no-wrap
+msgid "\n# <i>rm -rf /lib/modules/2.4.*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1218
+msgid "The 2.4 kernel binaries you used to boot from can also be safely removed. You should mount your <c>/boot</c> partition, and remove those images. You should also update your bootloader configuration so that it no longer references these deleted kernel images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1225
+msgid "Some Linux 2.4 users will have previously installed the <c>alsa-driver</c> package to benefit from the new audio capabilities included in Linux 2.6. If you were one of these users, and you followed the advice given earlier in this document about building ALSA with the 2.6 kernel sources (as opposed to using the <c>alsa-driver</c> package), then you can safely remove this to prevent future conflicts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1234
+msgid "Additionally, <c>lm-sensors</c> users will have previously used the <c>i2c</c> package to provide the hardware drivers. As already mentioned, I2C drivers are now included in the kernel, so this package can also be removed in order to prevent future conflicts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1241
+msgid "The devfs management daemon, <c>devfsd</c>, can also safely be removed, now that we are using <c>udev</c> for device management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1246
+msgid "Removing alsa-driver, i2c, and devfsd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1246
+#, no-wrap
+msgid "\n# <i>emerge --unmerge alsa-driver i2c devfsd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1250
+msgid "If you are LVM2 user, you may wish to convert your data into the LVM2 data format in order to benefit from the advantages which LVM2 provides. However, this operation will prevent you from ever accessing your LVM data from a 2.4 kernel. If you want to continue with the conversion (this is totally optional!), then you should examine the <c>vgconvert</c> man page for instructions on how to carry this out. An example is shown below, where <c>main</c> is the volume group name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1260
+msgid "Converting a LVM1 volume to LVM2 format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1260
+#, no-wrap
+msgid "\n# <i>vgconvert -M2 main</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/mips-requirements.xml.pot b/doc/gettext/mips-requirements.xml.pot
new file mode 100644
index 0000000..a7a63d8
--- /dev/null
+++ b/doc/gettext/mips-requirements.xml.pot
@@ -0,0 +1,444 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):6
+msgid "Gentoo/MIPS Linux Hardware Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(mail:link):9
+msgid "kumba@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(mail):9
+msgid "Joshua Kinard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(mail:link):12
+msgid "redhatter@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(mail):12
+msgid "Stuart Longland"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(abstract):15
+msgid "This document provides an overview of the status of various MIPS-based systems for installing Gentoo Linux. If you find errors or omissions please email the maintainer or an editor."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(version):25
+msgid "1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(date):26
+msgid "2010-09-01"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):29
+msgid "General Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):32
+msgid "System Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):35
+msgid "The exact requirements will largely depend on what you intend to use the machine for and how you wish to go about installing Gentoo. The following table should give you a rough idea."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):44
+msgid "Minimum"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):45
+msgid "Recommended"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):46
+msgid "Ideal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):49
+msgid "RAM:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):50
+msgid "48~64MB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):51
+msgid "&gt;128MB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):52
+msgid "~256MB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):55
+msgid "HDD:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):56
+msgid "4GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):57
+msgid "&gt;8GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):58
+msgid "18GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):66
+msgid "A Note about serial consoles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):69
+msgid "If you lack an appropriate Framebuffer, you will be required to use serial console. Serial console programs for linux include <c>minicom</c> and <c>xc</c>, and for Windows, <c>HyperTerminal</c> and <c>Tera Term Pro</c>. If you are running Windows, and intend to use HyperTerminal, it is advised that you seek out an updated client from the program's website instead of the one installed by default. An upgraded client provides much better serial support than the default one installed by Windows."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):82
+msgid "User Testimonies &amp; Kernel Configurations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):85
+msgid "As an aid to the project, a <uri link=\"http://stuartl.longlandclan.hopto.org/gentoo/mips/\">hardware support database</uri> has been set up. This support database is intended to provide a quick and easy way to determine how well certain configurations are supported. The system also allows people to contribute their comments and kernel configs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):98
+msgid "Silicon Graphics Systems -- Stable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):102
+msgid "The following systems are known to be very stable overall. Just about all the core hardware is supported in these systems, and there are very few outstanding stability issues at this time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):111
+msgid "IP22: Indy, Indigo 2 and Challenge S"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):118
+msgid "<e>(on Indy and Challenge S)</e> R4000, R4400, R4600, R5000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):121
+msgid "<e>(on Indigo 2)</e> R4000, R4400"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):129 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):530
+msgid "Linux 2.4: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):130 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):264 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):298 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):358
+msgid "Linux 2.6: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):136 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):537
+msgid "32-bit: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):137 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):271 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):305 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):365
+msgid "64-bit: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):143 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):208 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):277 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):311 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):371 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):544
+msgid "o32: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):144
+msgid "n32: <e>Experimental</e> (Only on Linux 2.6 R5000/RM5200)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):145 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):210 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):279 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):313 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):373 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):546 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):582 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):628
+msgid "n64: <e>Not Available In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):151
+msgid "At present, only the Newport (XL) graphics framebuffer is supported in Linux. Therefore on systems with other framebuffers, you will need to use serial console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):156
+msgid "The Challenge S has its RJ-45 connector on a daughter board (Mezz) linked with an unsupported SCSI adapter, a WD33C95A. In order for this network connector to function, this SCSI bus needs to be activated, however it is not yet supported by Linux. As a result of this, the Challenge S can only get network connectivity via its AUI connector."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):163
+msgid "Indigo2 EISA Support is <e>highly</e> experimental. It isn't very well tested and may not work with all hardware. Hardware that it is known to function with is listed, and as more compatible hardware is discovered, it will be added. Please note that hardware requiring DMA support is currently not functional. This includes EISA/ISA-based soundcards. EISA Video cards requiring an x86-compatible BIOS are also not functional."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):179
+msgid "IP32: O2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):186
+msgid "<b>Stable:</b> R5000, RM5200"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):187
+msgid "<b>Experimental:</b> RM7000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):188
+msgid "<b>Unsupported:</b> R10000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):194 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):263 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):357
+msgid "Linux 2.4: <e>Unsupported in Kernel</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):195 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):531
+msgid "Linux 2.6: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):201 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):270 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):304 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):364
+msgid "32-bit: <e>Unsupported in Kernel</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):202
+msgid "64-bit: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):209 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):312
+msgid "n32: <e>Experimental</e> (Only on Linux 2.6)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):216
+msgid "The O2 RM7000 Processor support is limited in Linux currently, as it requires a fairly recent kernel version (&gt;2.6.7), and has several notable issues. The first issue is a problem with SCSI at the moment, making the internal disks unusable at the current time. The Level 3 (Tertiary) Cache is also disabled due to there being no support for this cache in the linux kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):224
+msgid "Please be aware that this note only applies to the official SGI RM7000 running at 350MHz, not the 600MHz RM7000 that can be assembled using an RM5200 board. These \"modded\" CPU modules for O2 systems are not supported/tested, although, in theory, they should be functional, but may suffer from the same problems listed above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):240
+msgid "Silicon Graphics Systems -- Experimental/Unstable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):244
+msgid "The systems listed here are known to run Linux... <e>HOWEVER</e>, in many cases, there are known stability issues, and major gaps in the hardware support. In short, it will be a rough and bumpy ride."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):253
+msgid "IP27: Origin 200 and 2000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):257
+msgid "<b>Processor Options <e>(Experimental)</e>:</b> R10000, R12000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):278 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):372
+msgid "n32: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):287
+msgid "IP28: Indigo 2 Impact (a.k.a Indigo 2 R10k)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):291
+msgid "<b>Processor Options <e>(Experimental)</e>:</b> R10000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):297 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):566
+msgid "Linux 2.4: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):331
+msgid "MIPS R10000 Microprocessor User's Manual (See <e>PDF Pages 51-55</e>) <uri>http://techpubs.sgi.com/library/manuals/2000/007-2490-001/pdf/007-2490-001.pdf</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):336
+msgid "Post to NetBSD sgimips Mailing List on 29 Jun 2000 <uri>http://mail-index.netbsd.org/port-sgimips/2000/06/29/0006.html</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):319
+msgid "IP28 Indigo2 Impact support (classified as an Indigo2 system w/ an R10000 Processor) is <e>very experimental</e>. Most of the work is currently being done by Peter Fuerst, who maintains patches on his <uri link=\"http://www.pfrst.de/download.html\">website</uri>. This kernel is <e>NOT</e> intended for stable, day-to-day use. The Indigo2 IP28 system suffers from an issue known as <e>Speculative Execution</e>, a feature of the R10000 Processor that is problematic on machines that are <e>Non Cache Coherent</e>, such as the IP28 Indigo2 and on R10000/R12000-based IP32 O2 systems. Details on the nature of Speculative Execution, and the issues it poses to the Indigo2 can be found at the following URLs: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):349
+msgid "IP30: Octane"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):353
+msgid "<b>Processor Options (Experimental):</b> R10000, R12000, R14000A"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):379
+msgid "Octane support in Linux should be regarded as experimental. Support for this particular machine from SGI has been progressing quite well and the Linux kernel functions reasonably well. The current status for this system may be found on <uri link=\"http://www.linux-mips.org/~skylark/\">Stanislaw Skowronek's page</uri>. Wider support in Gentoo for this system will be available in the future, so watch this space closely for more details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):388
+msgid "The serial ports on the Octane currently only support 9600 baud rate, 8-bits, no parity, 1 stop bit. Other baud rates do not currently work at present."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):402
+msgid "Silicon Graphics Systems -- Unsupported"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):406
+msgid "Just about all of these systems are totally unsupported at the kernel level -- making a full Linux system totally impossible. Little is known about a lot of the systems listed here -- therefore any support in the near future is highly unlikely. You may wish to keep an eye on the <uri link=\"http://www.linux-mips.org\">Linux/MIPS website</uri> for any news of ports -- either that, or start your own. :-)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):416
+msgid "IP12: Iris Indigo (R3000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):417
+msgid "IP20: Iris Indigo (R4000 or R4400 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):418
+msgid "IP26: Indigo 2 Power (R8000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):419
+msgid "IP34: Fuel (R14000A or R16000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):420
+msgid "IP35: Origin 3000 (R14000 or R14000A CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):421
+msgid "IP45: Origin 300 (R14000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):422
+msgid "IP53: Origin 350 &amp; Tezro (R16000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):430
+msgid "Silicon Graphics Accessories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):434
+msgid "As with most systems, there is quite wide array of peripherals that one can obtain for Silicon Graphics systems. While a lot of these work in IRIX, Linux support is a bit touch-and-go on some of these items. The following table lists the support for each device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):443
+msgid "Stable Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):444
+msgid "Experimental Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):445
+msgid "Unsupported/Untested"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):448
+msgid "Indy/Indigo2: XL Graphics Card (Newport)<br/> Indy/Indigo2: SGI Seeq Ethernet 10Mbps<br/> Indy/Indigo2: WD33C93 SCSI<br/> Indy/Indigo2: HAL2 Sound/Audio<br/> Indy/Indigo2: Parallel Port<br/> Indy/Indigo2: Serial Port<br/> O2: SGI MACE Ethernet 10/100Mbps<br/> O2: Adaptec AIC7880 SCSI<br/> O2: Serial Port<br/> Indigo2 ISA: Parallel Port Card (PC-Style)<br/> Indigo2 ISA: NE2000 Compatible 10Mbps NIC (RTL8019)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):461
+msgid "Indy: I2C/VINO subsystem &amp; IndyCam<br/> Indigo2 EISA: 3COM 3c597 10/100Mbps<br/> O2: GBE Framebuffer<br/> O2: PCI Slot<br/> Octane: Keyboard<br/> Octane: Mardi Gras (MGRAS) Graphics<br/> Octane: QLogic ISP1040B SCSI<br/> Octane: RAD1 Audio<br/> Octane: SMP Support<br/> Octane: V6/V8/V10/V12 Graphics (Odyssey)<br/> Origin: IOC3 Ethernet 10/100Mbps<br/> Origin: QLogic ISP1020 SCSI<br/> O2 PCI: ALi 5273 USB 2.0 (Req. Kernel &gt;=2.6.8.1)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):476
+msgid "(1)Indy/Indigo2: Impact &amp; Extreme/XZ graphics chipsets<br/> Indy: Phobos G130 10/100Mbps NIC<br/> Indigo2: GIO64 Slots<br/> Indigo2: Phobos G160 10/100Mbps NIC<br/> Challenge S: WD33C95A SCSI Adapter/RJ-45 Daughter Card<br/> O2: VICE Subsystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(note):487
+msgid "(1) Work has begun on porting the ImpactSR to the Indigo2 Impact (IP28) workstation. At the moment, it's early days, and the driver is not functional yet, but this may change in the coming months.<br/> Likewise with Extreme graphics... a few people were starting to look into writing drivers for this chipset. Nothing has been released yet, but we may see something in the not too distant future.<br/> We will update this page if such a driver is released."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):502
+msgid "Cobalt Servers -- Stable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):506
+msgid "The Cobalt servers are a set of machines all based around the QED RM523[01] CPU. They came in two varieties, the RaQ -- a rackmounted model, and the Qube, a small desktop model (1ft. cube). The big difference between these systems and the SGI systems above, is that these systems are <e>little endian</e> (<c>mipsel</c>) as opposed to <e>big endian</e> (<c>mips</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):514
+msgid "These were also sold under an OEM arragement to other companies, examples of this are the Gateway Microserver (Qube 2) and the Seagate NasRaQ (RaQ 2)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):522
+msgid "Qube/Raq 2800 (a.k.a Qube/Raq 2)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):526
+msgid "<b>Processor:</b> QED RM5231 @ 250MHz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):538
+msgid "64-bit: <e>Highly Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):545 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):581 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):627
+msgid "n32: <e>Not Available In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):556
+msgid "Cobalt Servers -- Experimental"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):558
+msgid "Raq 2700 (a.k.a Raq 1)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):562 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):608
+msgid "<b>Processor:</b> QED RM5230 @ 150MHz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):567 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):613
+msgid "Linux 2.6: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):573
+msgid "32-bit: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):574 ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):620
+msgid "64-bit: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):580
+msgid "o32: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):592
+msgid "Cobalt Servers -- Unsupported"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):594
+msgid "Qube 2700 (a.k.a Qube 1)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):597
+msgid "The Qube 2700 was the first of this whole subarchitecture. Unfortunately, it lacks a serial port, making installation at present, damn near impossible. We're looking into ways we can support this system, but as none of the developers have access to one of these machines, we have no way to test our efforts. You may wish to have a look at <uri link=\"http://www.metzner.org/projects/qube/\">Jan Metzner's page</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):612
+msgid "Linux 2.4: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):619
+msgid "32-bit: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):626
+msgid "o32: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/multipath.xml.pot b/doc/gettext/multipath.xml.pot
new file mode 100644
index 0000000..679e8c0
--- /dev/null
+++ b/doc/gettext/multipath.xml.pot
@@ -0,0 +1,289 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):6
+msgid "Multipathing for Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):17
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):9
+msgid "tsunam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):12
+msgid "matthew.summers@liquidustech.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail):12
+msgid "Matthew Summers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):15
+msgid "richard.anderson@liquidustech.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail):15
+msgid "Richard Anderson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):18
+msgid "steve.rucker@liquidustech.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail):18
+msgid "Steve Rucker"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):21
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(abstract):24
+msgid "This document teaches you how to set up multipathing services for data storage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(version):32
+msgid "1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(date):33
+msgid "2008-09-10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):36
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):40
+msgid "Multipathing services, generally deployed in enterprise environments, provide a means for high performance, load-balanced, and fault-tolerant data storage either locally or via a storage area network (SAN). Multipathing facilitates a single storage device to be transparently accessed across one or more paths. For example, if there are two connections from a server Host Bus Adapter (HBA) to two Fibre Channel switches and then to a SAN, when the HBA module loads and scans the bus, it will read four paths to the SAN: the paths from the server HBA to and from each Fibre Channel switch and at the storage device. Taking advantage of this situation, Multipath allows you to make use of each path simultaneously or independently to ensure a constant and reliable connection to the data in storage. Multipath serves as a failover for all connections points in the event of losing one path making critical data always available due to redundancy in the design and implementation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):56
+msgid "In the most basic sense, multipathing is made of two distinct parts: <c>device-mapper</c> and <c>multipath-tools</c>. <b>Device Mapper</b> is the first key element of this application. Administrators are probably familiar with Device Mapper from LVM, EVMS, dm-crypt, or in this case, Multipath. In short, working within the kernel space Device Mapper takes one block device such as <path>/dev/sda</path> (as all SAN based targets will be some type of SCSI device) and maps it to another device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):66
+msgid "On a lower level, Device Mapper creates a virtual block device accepting all of the commands of a regular block device, but passes on the actual data to the real block device. As previously stated, the mapping process is all handled in the kernel space and not in user space."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):73
+msgid "<b>Multipath Tools</b> is a set of userspace tools that interacts with the Device Mapper tools and creates structures for device handling, implementing I/O multipathing at the OS level. In a typical SAN environment, you will have multiple paths to the same storage device: a fiber card (or two) on your server that connects to a switch which then connects to the actual storage itself (as in the scenario discussed above). So administrators could possibly see the same device one to four times in such a situation (each card will see the LUN twice, once for each path it has available to it). Thus, a single drive could be recognized as <path>sda</path>, <path>sdb</path>, <path>sdc</path>, and <path>sdd</path>. If you were to mount <path>/dev/sda</path> to <path>/san1</path>, for instance, you would be going over the singular path from one fiber card to a switch and then to a port on the same storage device. If any of those points were to fail, you would lose your storage device suddenly and have to unmount and remount with another device (<path>sdb</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):90
+msgid "Consequently, this scenario is not ideal as you are only using one out of the four possible paths. This is where the combination of Multipath tools and Device Mapper are beneficial. As already explained, Device Mapper creates virtual block devices and then passes information to the real block devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):102
+msgid "Installation and Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):104
+msgid "Installation and Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):107
+msgid "You need to emerge <c>multipath-tools</c> and <c>sg3_utils</c>. On the disk, you want to find the <c>wwid</c>. You can use <c>sq_vpd</c> (provided by <c>sg3_utils</c>) to do this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):113
+msgid "Installing multipath-tools and initial configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):113
+#, no-wrap
+msgid "\n# <i>emerge multipath-tools sg3_utils</i>\n<comment>(Replace /dev/DEVICE with your disk to find its wwid)</comment>\n# <i>/usr/bin/sq_vpd ?page=di /dev/DEVICE</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):119
+msgid "Where DEVICE is the sd device, the ID will come back with a <c>0x6</c>. Replace <c>0x</c> with <c>3</c>, and you will have the proper ID that you'll put into the multipath <c>wwid</c> in <path>/etc/multipath.conf</path>. More on this in the next chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):129
+msgid "Configuring Gentoo for multipathing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):132
+msgid "To configure Gentoo for multipath, your kernel needs the following settings:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):136
+msgid "Adding multipath support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):136
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n  SCSI device support  ---&gt;\n    &lt;*&gt; SCSI target support\n    &lt;*&gt; SCSI disk support\n    [*] Probe all LUNs on each SCSI device\n  [*] Multiple devices driver support (RAID and LVM)  ---&gt;\n    &lt;*&gt;  Multipath I/O support\n    &lt;*&gt;  Device mapper support\n    &lt;*&gt;    Multipath target\n        <comment>(Select your device from the list)</comment>)\n    &lt;*&gt;      EMC CX/AX multipath support  \n    &lt;*&gt;      LSI/Engenio RDAC multipath support  \n    &lt;*&gt;      HP MSA multipath support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(note):152
+msgid "<c>scsi_id</c> is done by targets. IDE drives have two spots to which you can connect. An administrator has the ability to set a drive as a master and another drive as a slave or set to autoselect by changing the dip switches. scsi_id is similar. Each drive or Logical Unit Number (LUN) has a unique ID, which ranges from 0 to 254. A device that has ID 0 will be discovered before a device that has, for example, ID 120, because it performs a LIP (a scan of the SCSI bus for devices that respond) that starts from 0 and works its way upwards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):162
+msgid "In the kernel menu config, make sure CONFIG_SCSI_MULTI_LUN=y is set to ensure the SCSI subsystem is able to probe all Logical Unit Numbers (LUNs) (This is recommended as you'll stop scanning after ID 0 if you have a device on an ID of <c>0</c> but not <c>1</c> and then on an ID of <c>2</c>. Simply, you'll get your device for ID <c>0</c> but not <c>2</c>.) or whichever device you need for SCSI, such as a QLogic 2400 card, which is in the SCSI low-level drivers area."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):171
+msgid "For a better understanding, consider the following scenarios:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):175
+msgid "There are three drives with IDs of 0,1,2. Without the \"probe all LUNs\" setting, you will see IDs 0,1,2 as sda,sdb,sdc - all devices are seen. If you delete the ID 1 drive. IDs 0,2 will still be seen. It might seem to make sense that you would see sda and sdb now (sdc would move to sdb as there is no device to fill it up). However, if you don't probe all LUNs, it will perform in the following manner:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):184
+msgid "Scenario 1: Without \"probe all LUNs\", the scan will start and ID 0 will be seen. ID 0 will be set to sda and then move to find ID 1. If ID 1 is not detected, scanning will stop and be considered complete having perceived to have scanned all devices even if there is a device on ID 2 or any other subsequent ID. Reboot for scenario two."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):192
+msgid "Scenario 2: If you have \"probe all LUNs\", the scan will start and detect ID 0. This ID will be assigned sda and will continue to detect the next device. If ID 1 is not detected, scanning will continue to find more devices. ID 2 will be located and assigned to be sdb. If no devices (IDs) are detected beyond that, scanning will be considered complete."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(note):200
+msgid "Although it seems that it is unfeasible or even unnecessary to have devices spaced many LUNs apart, to account for all options it is necessary to still probe all LUNs. An administrator will encounter many reasons (business or personal) for such a setup. Therefore, the second scenario would be optimal to ensure that all devices are recognized and assigned an ID in the multipath setup process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):209
+msgid "So, once you probe all LUNs, all devices will be recognized and assigned an ID in Multipath."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):219
+msgid "Architectural Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):223
+msgid "As part of Multipath Tools, there are priority groups filled with the devices mentioned earlier. After you have configured <c>multipath-tools</c> and started it with <c>/etc/init.d/multipath start</c>, you can list the groups via <c>multipath -l</c>. The output will look like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):230
+msgid "multipath -l output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):230
+#, no-wrap
+msgid "\nEVA_SAN (3600508b4001044ee00013000031e0000)\n[size=300 GB][features=\"1 queue_if_no_path\"][hwhandler=\"0\"]\n\\_ round-robin 0 [active]\n\\_ 0:0:0:1 sda 8:0  [active]\n\\_ round-robin 0 [enabled]\n\\_ 0:0:1:1 sdb 8:16 [active]\n\nEVA_SAN2 (3600508b4001044ee0001300003880000)\n[size=300 GB][features=\"1 queue_if_no_path\"][hwhandler=\"0\"]\n\\_ round-robin 0 [active]\n\\_ 0:0:0:2 sdc 8:32 [active]\n\\_ round-robin 0 [enabled]\n\\_ 0:0:1:2 sdd 8:48 [active]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):246
+msgid "By default, it will pick the first priority group (the first top round-robin for the EVA_SAN2, for instance, being <path>sdc</path>). In this instance, due to round robin it will bounce back and forth. But if one path was to fail, it would push all information to the other path and continue. Only if all the devices in a path fail will it actually fail and go to the secondary priority group."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):257
+msgid "Typical Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):260
+msgid "A typical Multipath configuration looks like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):264
+msgid "A typical /etc/multipath.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):264
+#, no-wrap
+msgid "\ndefaults {\nudev_dir                /dev\npolling_interval        15\nselector                \"round-robin 0\"\npath_grouping_policy    group_by_prio\nfailback                5\npath_checker            tur\nprio_callout            \"/sbin/mpath_prio_tpc /dev/%n\"\nrr_min_io               100\nrr_weight               uniform\nno_path_retry           queue\nuser_friendly_names     yes\n}\nblacklist {\ndevnode cciss\ndevnode fd\ndevnode hd\ndevnode md\ndevnode sr\ndevnode scd\ndevnode st\ndevnode ram\ndevnode raw\ndevnode loop\ndevnode sda\n}\n\nmultipaths {\nmultipath {\nwwid\n<comment>(To find your wwid, please use /usr/bin/sq_vpd ?page=di /dev/DEVICE.\nThe address will be a 0x6. Remove the 0x and replace it with 3.)</comment>\nalias DB_SAN\n}\ndevices {\ndevice {\n<comment>(White spacing is important on these two items to match the vendor specifications.)</comment>\n\"IBM     \"\n\"1815      FAStT \"\n}\n}\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(impo):309
+msgid "On your devices, it is best to <c>cat</c><path>/sys/block/sd(device)/device/model</path> and <c>cat</c><path>/sys/block/device/sd(device)/device/vendor</path>, placing both directly into your devices section in <path>/etc/multipath.conf</path>. You might not always see the white spacing, and it's part of the name in this case. One reason for the device section is that not every vendor's string is in the kernel convention and naming, and the string, as such, is not always detected as required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):320
+msgid "A typical multipath configuration utilizing an EVA_SAN where the device information is in the kernel information regarding SAN hardware detection would look like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):326
+msgid "EVA_SAN configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):326
+#, no-wrap
+msgid "\nmultipaths {\nmultipath {\nwwid  3600508b4001044ee00013000031e0000\nalias EVA_SAN\n}\nmultipath {\nwwid    3600508b4001044ee0001300003880000\nalias   EVA_SAN2\n}\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):344
+msgid "Setting Up Your Own Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):348
+msgid "The multipath configuration is fairly simple to accomplish because the only file that needs modification is <path>/etc/multipath.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):353
+msgid "To begin, set the <b>polling interview</b> to how often (in seconds) path checks will be performed to ensure that the path is alive and healthy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):358
+msgid "<b>selector</b> will be set at <c>\"round-robin 0\"</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(note):362
+msgid "This round-robin value is the only selector value that will be used in this configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):367
+msgid "<b>prio_callout</b>: This one can be quite important, and there are a number of different priorities for different devices, such as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):373
+msgid "mpath_prio_alua"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):374
+msgid "mpath_prio_emc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):375
+msgid "mpath_prio_hds_modular"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):376
+msgid "mpath_prio_netapp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):377
+msgid "mpath_prio_tpc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(note):380
+msgid "For most people, <c>mpath_prio_tpc</c> will suffice as it's a conservative checker. Other devices like <c>mpath_prio_netapp</c> have special functionality for priority grouping, such as netapps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):386
+msgid "<b>path_grouping_policy</b> has a few different options: failover, multibus, group_by_prio. <c>Failover</c> will only have one disk per priority group. <c>Multibus</c> will put all devices into one priority group. <c>Group_by_prio</c> is done by a \"priority value.\" So routes that have the same priority value will be grouped together, the priority values being determined by the callout."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):395
+msgid "<b>no_path_retry</b> is set to <c>queue</c> as most people don't want data to fail to send at all. So, if all paths fail, for instance, the I/Os will queue up until the device returns and then sends everything again. Depending on your transfer, this can cause load issues."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):402
+msgid "<b>rr_min_io</b> are the number of I/Os to do per path before switching to the next I/Os in the same group. If <path>sda</path> and <path>sdb</path> were in the same group, rr_min_io would do 100 I/Os to <path>sda</path> then do 100 to <path>sdb</path>, bouncing back and forth. This is a setting to tweak for each instance to maximize performance because the data load and size of transfers/request vary by company. The default in the case is <c>1000</c>, but some may prefer a smaller number in order to switch ports more often, when possible."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):413
+msgid "<b>user_friendly_names</b> make it easier to see which device you are working with. For example, if you set user_friendly_names to <c>no</c>, then you'll see WWID instead of EVA_SAN for your device."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/mysql-howto.xml.pot b/doc/gettext/mysql-howto.xml.pot
new file mode 100644
index 0000000..59a37a3
--- /dev/null
+++ b/doc/gettext/mysql-howto.xml.pot
@@ -0,0 +1,832 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(guide:link):5
+msgid "/doc/en/mysql-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):6
+msgid "MySQL Startup Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail:link):12
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail):12
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail:link):15
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail):15
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(abstract):18
+msgid "This document helps a user set up and use MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(version):26
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(date):27
+msgid "2006-08-08"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):30
+msgid "Getting Started With MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):32
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):35
+msgid "MySQL is a popular database server that is used in various applications. SQL stands for (S)tructured (Q)uery (L)anguage, which is what MySQL uses to communicate with other programs. On top of that, MySQL has its own expanded SQL functions to provide additional functionality to users. In this document, we'll look at how to do the initial MySQL installation, set up databases and tables, and create new users. Let's start out with the installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):47
+msgid "MySQL Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):50
+msgid "First make sure you have MySQL installed on your system. In case you need specific functionality from MySQL, please make sure you have the required USE flags enabled as they will help fine tune your installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):56
+msgid "Installing MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):56
+#, no-wrap
+msgid "\n<comment>(View available USE flags)</comment>\n# <i>emerge --pretend --verbose mysql</i>\n<comment>(Install MySQL)</comment>\n# <i>emerge mysql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):63
+msgid "Upon completion of the installation, you will see the following notice:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):67
+msgid "MySQL einfo message"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):67
+#, no-wrap
+msgid "\nYou might want to run:\n\"emerge --config =dev-db/mysql-[version]\"\nif this is a new install.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):73
+msgid "Since this is a new installation, we run the command. You need to press <c>ENTER</c> when prompted while configuring the MySQL database. The configuration sets up the main MySQL database which contains administrative information such as databases, tables, users, permissions and more. The configuration recommends that you change your root password as soon as possible. We will definitely do this, otherwise someone could come along by chance and hack our default setup MySQL server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):83
+msgid "MySQL configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):83
+#, no-wrap
+msgid "\n<comment>(Replace [version] with the version number you have just installed.)</comment>\n# <i>emerge --config =dev-db/mysql-[version]</i>\n * MySQL DATADIR is /var/lib/mysql\n * Press ENTER to create the mysql database and set proper\n * permissions on it, or Control-C to abort now...\n\n   Preparing db table\n   Preparing host table\n   Preparing user table\n   Preparing func table\n   Preparing tables_priv table\n   Preparing columns_priv table\n   Installing all prepared tables\n\n   To start mysqld at boot time you have to copy support-files/mysql.server\n   to the right place for your system\n\n   PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !\n   To do so, issue the following commands to start the server\n   and change the applicable passwords:\n<comment>(Note the next 3 lines)</comment>\n   /etc/init.d/mysql start\n   /usr/bin/mysqladmin -u root -h pegasos password 'new-password'\n   /usr/bin/mysqladmin -u root password 'new-password'\n   Depending on your configuration, a -p option may be needed\n   in the last command. See the manual for more details.\n\n<comment>(Some MySQL non-ebuild specific information has been removed from here\nso as to keep this document as consistent as possible)</comment>\n\n   * For security reasons you should set your MySQL root\n   * password as soon as possible.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(impo):118
+msgid "As of mysql-4.0.24-r2, passwords are entered during the config phase making root password entry more secure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):123
+msgid "The config script has already printed out the commands we need to run to setup our password, so we shall now run them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):128
+msgid "Setting up your MySQL root password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):128
+#, no-wrap
+msgid "\n# <i>/etc/init.d/mysql start</i>\n * Re-caching dependency info (mtimes differ)...\n * Starting mysqld (/etc/mysql/my.cnf) ...        [ ok ]\n<comment>(Replace new-password with your desired password)</comment>\n# <i>/usr/bin/mysqladmin -u root -h localhost password 'new-password'</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):136
+msgid "You can now test that your root password was successfully configured by trying to login to your MySQL server:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):141
+msgid "Logging into the MySQL server using mysql"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):141
+#, no-wrap
+msgid "\n$ <i>mysql -u root -h localhost -p</i>\nEnter password:\nWelcome to the MySQL monitor. Commands end with ; or \\g.\nYour MySQL connection id is 4 to server version: 4.0.25\n\nType 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n\nmysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):152
+msgid "The <c>-u</c> switch sets the user that will be logging in. The <c>-h</c> switch sets the host. This will usually be <c>localhost</c> unless you are setting up a remote server. Finally, <c>-p</c> tells the mysql client that you will be entering a password to access your database. Notice the <c>mysql&gt;</c> prompt. This is where you type in all your commands. Now that we're in the mysql prompt as the root user, we can begin to setup our database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):166
+msgid "Setting Up The Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):168
+msgid "Creating A Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):171
+msgid "We have logged in and a mysql prompt is displayed. First let's take a look at the databases we currently have. To do so, we use the <c>SHOW DATABASES</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):177
+msgid "Displaying MySQL databases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):177
+#, no-wrap
+msgid "\nmysql&gt; <i>SHOW DATABASES;</i>\n+----------+\n| Database |\n+----------+\n| mysql    |\n| test     |\n+----------+\n2 rows in set (0.09 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(impo):188
+msgid "Please remember that MySQL commands should end with a semicolon -- <c>;</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):192
+msgid "Despite the fact that a test database is already created, we are going to create our own. Databases are created using the <c>CREATE DATABASE</c> command. We'll create one named \"gentoo\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):198
+msgid "Creating the gentoo database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):198
+#, no-wrap
+msgid "\nmysql&gt; <i>CREATE DATABASE gentoo;</i>\nQuery OK, 1 row affected (0.08 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):203
+msgid "The response lets us know that the command was executed without any errors. In this case, 1 row was modified. This is a reference to the main mysql database, which carries a list of all the databases. You won't need to worry too much about the background details. The last number is how fast the query was executed. We can verify the database was created by running the <c>SHOW DATABASES</c> command again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):212
+msgid "Verifing the database is created"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):212
+#, no-wrap
+msgid "\nmysql&gt; <i>SHOW DATABASES;</i>\n+----------+\n| Database |\n+----------+\n| gentoo   |\n| mysql    |\n| test     |\n+----------+\n3 rows in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):224
+msgid "Indeed our database has been created. In order to work with creating tables for our new gentoo database, we need to select it as our current database. To do so, we use the <c>USE</c> command. The <c>USE</c> command takes the name of the database you wish to use as your current database. Another option is to set it on the command line after the <c>-D</c> switch. Let's go ahead and switch to the gentoo database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):233
+msgid "Switching our database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):233
+#, no-wrap
+msgid "\nmysql&gt; <i>USE gentoo;</i>\nDatabase changed\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):238
+msgid "And the current database is now our previously created gentoo database. Now that we're using it, we can start to create some tables and put information in them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):249
+msgid "Working With Tables In MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):251
+msgid "Creating a Table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):254
+msgid "In the structure of MySQL, there are databases, tables, records, and fields. Databases hold together tables, tables hold together records, records hold together fields, which contain the actual information. This structure lets users select how they want to access their information. So far we've dealt with databases, now let's work with tables. First off, tables can be listed similiarly to databases using the <c>SHOW TABLES</c> command. Right now there are no tables in our gentoo database, as running the command will show us:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):264
+msgid "Empty gentoo Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):264
+#, no-wrap
+msgid "\nmysql&gt; <i>SHOW TABLES;</i>\nEmpty set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):269
+msgid "This means we need to create some tables. In order to do so, we use the <c>CREATE TABLE</c> command. However, this command is quite different from simple <c>CREATE DATABASE</c> command. This command takes a list of arguments. The form is as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):276
+msgid "CREATE TABLE Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):276
+#, no-wrap
+msgid "\nCREATE TABLE [table_name] ([field_name] [field_data_type]([size]));\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):280
+msgid "<b>table_name</b> is the name of the table we wish to create. In this case, let's make a table named <c>developers</c>. This table will contain the developer's name, email and job. <b>field_name</b> will contain the name of the field. We have 3 required names in this case: name, email, and job. The <b>field_data_type</b> is what type of information will be stored. The different formats available can be found at the <uri link=\"http://dev.mysql.com/doc/mysql/en/column-types.html\">MySQL Column Types Page</uri>. For our purposes, we'll use the <c>VARCHAR</c> data type for all of our fields. <c>VARCHAR</c> is one of the simplest of data types when it comes to working with strings. <b>size</b> is how much of data a single field will store. In this case, we'll use 128. This means that the field can have <c>VARCHAR</c> data that is 128 bytes. You can safely think of this as 128 characters for the time being, though there is a somewhat more technical explanation that the above site will provide you with. Now that we know how we are going to create the table, let's do it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):298
+msgid "Creating our table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):298
+#, no-wrap
+msgid "\nmysql&gt; <i>CREATE TABLE developers ( name VARCHAR(128), email VARCHAR(128), job VARCHAR(128));</i>\nQuery OK, 0 rows affected (0.11 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):303
+msgid "Looks like our table was created ok. Let's check it with the <c>SHOW TABLES</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):308
+msgid "Verifying our table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):308
+#, no-wrap
+msgid "\nmysql&gt; <i>SHOW TABLES;</i>\n+------------------+\n| Tables_in_gentoo |\n+------------------+\n| developers       |\n+------------------+\n1 row in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):318
+msgid "Yes, there's our table. However, it doesn't seem to have any information on the types of fields we setup. For that, we use the <c>DESCRIBE</c> command (or <c>DESC</c> for short), which takes the name of the table as its argument. Let's see what that gives us for our developers table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):325
+msgid "Describing our developers table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):325
+#, no-wrap
+msgid "\nmysql&gt; <i>DESCRIBE developers;</i>\n+-------+--------------+------+-----+---------+-------+\n| Field | Type         | Null | Key | Default | Extra |\n+-------+--------------+------+-----+---------+-------+\n| name  | varchar(128) | YES  |     | NULL    |       |\n| email | varchar(128) | YES  |     | NULL    |       |\n| job   | varchar(128) | YES  |     | NULL    |       |\n+-------+--------------+------+-----+---------+-------+\n3 rows in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):337
+msgid "This shows the different fields and their types. It also shows a few extra attributes that are beyond the scope of this howto. Feel free to refer to the <uri link=\"http://dev.mysql.com/doc/mysql/en/\">MySQL Reference Manual</uri> for more information. We now have a table to work with. Now let's go ahead and populate it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):348
+msgid "Populating Our MySQL Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):351
+msgid "We populate a table (or add data) using the <c>INSERT</c> command. Like the <c>CREATE TABLE</c> command, it also has a specific format:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):356
+msgid "INSERT Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):356
+#, no-wrap
+msgid "\nINSERT INTO table (col1, col2, ...) VALUES('value1', 'value2', ...);\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):360
+msgid "This command is used to insert a record into table. table contains the MySQL table we wish to enter the information into. The table name may be followed by the list of columns to insert data into and <c>VALUES()</c> contains the values you wish to insert into the table. You may omit the list of columns if you insert a value into each one and if you write the values in the same order the columns have been defined. In this case, we want to insert data into the developers table. Let's insert sample records:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):370
+msgid "Inserting information into our developers table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):370
+#, no-wrap
+msgid "\nmysql&gt; <i>INSERT INTO developers VALUES('Joe Smith', 'joesmith@gentoo.org', 'toolchain');</i>\nQuery OK, 1 row affected (0.06 sec)\n<comment>(If you don't know the order of the columns in the table or want to insert an incomplete record)</comment>\nmysql&gt; <i>INSERT INTO developers (job, name) VALUES('outsourced', 'Jane Doe');</i>\nQuery OK, 1 row affected (0.01 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):378
+msgid "According to our return result, it appears that the record was inserted correctly. What if we want to input more information than just one record? That's where the <c>LOAD DATA</c> command comes into play. This loads records from a tab separated file. Let's try that by editing a file in our home directory with the records. We'll call this file <path>records.txt</path>. Here's a sample:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):387
+msgid "~/records.txt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):387
+#, no-wrap
+msgid "\nJohn Doe\tjohndoe@gentoo.org\tportage\nChris White\tchriswhite@gentoo.org\tdocumentation\nSam Smith\tsamsmith@gentoo.org\tamd64\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(impo):393
+msgid "Be sure you know what data you're dealing with. It's very unsafe to use <c>LOAD DATA</c> when you are uncertain of the file's contents!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):398
+msgid "Now the <c>LOAD DATA</c> command has a somewhat enlongated definition, but we'll use the simplest form here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):403
+msgid "LOAD DATA Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):403
+#, no-wrap
+msgid "\nLOAD DATA LOCAL INFILE '/path/to/filename' INTO TABLE table;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):407
+msgid "<path>/path/to/filename</path> is the directory and filename that will be used. table is the name of our table. In this case, our file is <path>~/records.txt</path> and the table is developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):413
+msgid "Loading in our data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):413
+#, no-wrap
+msgid "\nmysql&gt; <i>LOAD DATA LOCAL INFILE '~/records.txt' INTO TABLE developers;</i>\nQuery OK, 3 rows affected (0.00 sec)\nRecords: 3  Deleted: 0  Skipped: 0  Warnings: 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(impo):419
+msgid "If you come up with any strange behaviour, make sure your fields are separated by tabs. If you paste information into your infile from another source, it may convert your tabs to spaces."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):425
+msgid "That worked well. However, this simply inserts records, and does not give you any sort of control over MySQL. Many web applications use sql scripts in order to setup MySQL quickly and easily. If you want to use an sql script, you'll need to run mysql in batch mode, or source the file. Here's an example of running mysql in batch mode:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):433
+msgid "MySQL in batch mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):433
+#, no-wrap
+msgid "\n$ <i>mysql -u root -h localhost -p &lt; sqlfile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):437
+msgid "Like <c>LOAD DATA</c>, be sure you can tell what <path>sqlfile</path> does. <e>Failure to do so may cause your database to be compromised!</e> Another way you can accomplish this is to use the <c>source</c> command. This command will run mysql commands from an sql file while in the mysql interactive mode. Here is how to source an sql file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):445
+msgid "Sourcing an sql file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):445
+#, no-wrap
+msgid "\nmysql&gt; <i>source sqlfile;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):449
+msgid "If you see a web application wanting you to run an sql file, the two above commands can be used to accomplish that task. We have our table setup, so how do we check our fields? We do this by searching our table with queries."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):458
+msgid "Browsing MySQL Tables With Queries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):461
+msgid "Queries are one of the main features of any SQL database. They help us turn data in our tables into something useful. Most queries are done with the <c>SELECT</c> command. The <c>SELECT</c> command is fairly complex, and we're only going to look at three main forms of the command in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):468
+msgid "SELECT forms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):468
+#, no-wrap
+msgid "\n<comment>(Select all entries in a table)</comment>\nSELECT * FROM table;\n<comment>(Select specific entries in a table)</comment>\nSELECT * FROM table WHERE field=value;\n<comment>(Select specific fields)</comment>\nSELECT field1,field2,field3 FROM table [WHERE field=value];\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):477
+msgid "Let's take a quick look at the first form. It's relatively simple and gives you an overall look of your table. We'll go ahead and run it to see what data we have so far."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):483
+msgid "Contents of our table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):483 ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):679
+#, no-wrap
+msgid "\nmysql&gt; <i>SELECT * FROM developers;</i>\n+-------------+-----------------------+----------------+\n| name        | email                 | job            |\n+-------------+-----------------------+----------------+\n| Joe Smith   | joesmith@gentoo.org   | toolchain      |\n| John Doe    | johndoe@gentoo.org    | portage        |\n| Chris White | chriswhite@gentoo.org | documentation  |\n| Sam Smith   | samsmith@gentoo.org   | amd64          |\n| Jane Doe    | NULL                  | Outsourced job |\n+-------------+-----------------------+----------------+\n5 rows in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):497
+msgid "We see both the data we inserted through <c>INSERT</c> and those inserted by <c>LOAD DATA</c> present. Now, let's say that we just want to see the record for Chris White. We can do so with the second form of select as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):503
+msgid "Selecting a specific record using SELECT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):503
+#, no-wrap
+msgid "\nmysql&gt; <i>SELECT * FROM developers WHERE name = 'Chris White';</i>\n+-------------+-----------------------+---------------+\n| name        | email                 | job           |\n+-------------+-----------------------+---------------+\n| Chris White | chriswhite@gentoo.org | documentation |\n+-------------+-----------------------+---------------+\n1 row in set (0.08 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):513
+msgid "As expected, the specific entry that we were looking for has been selected. Now, let's say we only wanted to know the person's job and email address, not their name. We can do so with the third form of <c>SELECT</c> as shown here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):519
+msgid "Selecting a specific record and fields using SELECT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):519
+#, no-wrap
+msgid "\nmysql&gt; <i>SELECT email,job FROM developers WHERE name = 'Chris White';</i>\n+-----------------------+---------------+\n| email                 | job           |\n+-----------------------+---------------+\n| chriswhite@gentoo.org | documentation |\n+-----------------------+---------------+\n1 row in set (0.04 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):529
+msgid "This method of selection is a lot easier to manage, expecially with larger amounts of information, as we'll see later on. Right now, being the root mysql user, we have unlimited permissions to do what we wish with the MySQL database. In a server environment, a user with such privileges can be quite problematic. In order to control who does what with the databases, we setup privileges."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):543
+msgid "MySQL Privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):545
+msgid "Granting Privileges with GRANT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):548
+msgid "Privileges are what kind of access users have to databases, tables, pretty much anything. Right now in the gentoo database, the MySQL root account is the only account that can access it, given its permissions. Now, let's create two somewhat generic users, guest and admin, who will access the gentoo database and work with the information in it. The guest account will be a restricted one. All it will be able to do is get information from the database, and that's it. admin will have the same control as root, but only for the gentoo database (not the main mysql databases). Before we start on that, let's have a closer look at this somewhat simplified format of the <c>GRANT</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):560
+msgid "GRANT Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):560
+#, no-wrap
+msgid "\nGRANT [privileges] ON database.* TO '[user]'@'[host]' IDENTIFIED BY '[password]';\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(note):564
+msgid "<c>GRANT</c> is considered to be the way to create a user. Later versions of MySQL, however, do contain a <c>CREATE_USER</c> function, though <c>GRANT</c> is still preferred."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):570
+msgid "First we have the privileges we wish to assign. With what we've learned so far, here are some of the privileges you can set:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):576
+msgid "<c>ALL</c> - Gives the all privilege control for the database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):577
+msgid "<c>CREATE</c> - Allows users to create tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):578
+msgid "<c>SELECT</c> - Allows users to query tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):579
+msgid "<c>INSERT</c> - Allows users to insert data into a table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):580
+msgid "<c>SHOW DATABASES</c> - Allows users to see a list of databases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):581
+msgid "<c>USAGE</c> - User has no privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):582
+msgid "<c>GRANT OPTION</c> - Allows users to grant privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(note):585
+msgid "If you're running MySQL to communicate data to a web application, <c>CREATE</c>, <c>SELECT</c>, <c>INSERT</c> (discussed here), <c>DELETE</c> and <c>UPDATE</c> (for further infomation look up the <uri link=\"http://dev.mysql.com/doc/mysql/en/grant.html\"> MySQL Reference Manual - GRANT and REVOKE Syntax</uri> section) are the only permissions you will most likely need. A lot of people make the mistake of granting all permissions when it's not really necessary. Check with the application developers to see if such permissions will cause issues with general operation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):597
+msgid "For our admin user, ALL will do. For the guest user, <c>SELECT</c> will be sufficient for read only access. database is the database we wish the user to have these permissions on. In this example, gentoo is the database. The .* means all tables. If you wanted to, you could apply per table access. user is the name of the user and host is the hostname the user will be accessing from. In most cases, this will be localhost. Finally, password is the user's password. Given the information, let's go ahead and create our users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):607
+msgid "Creating the admin and guest user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):607
+#, no-wrap
+msgid "\n<comment>(admin)</comment>\nmysql&gt; <i>GRANT ALL ON gentoo.* TO 'admin'@'localhost' IDENTIFIED BY 'password';</i>\n<comment>(guest)</comment>\nmysql&gt; <i>GRANT SELECT ON gentoo.* TO 'guest'@'localhost' IDENTIFIED BY 'password';</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):614
+msgid "Now that we have the users setup, let's test them out. First we quit mysql by typing <c>quit</c> at the command prompt:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):619
+msgid "Quitting MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):619
+#, no-wrap
+msgid "\nmysql&gt; <i>quit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):623
+msgid "We're now back at the console. Now that we have our users setup, let's go ahead and see what they can do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):631
+msgid "Testing User Permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):634
+msgid "We shall now attempt to login as the guest user. Currently, the guest user has <c>SELECT</c> only privileges. This basically comes down to being able to search and nothing more. Go ahead and login with the guest account."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):640
+msgid "Logging in with the guest account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):640
+#, no-wrap
+msgid "\n$ <i>mysql -u guest -h localhost -p</i>\nEnter password:\nWelcome to the MySQL monitor. Commands end with ; or \\g.\nYour MySQL connection id is 6 to server version: 4.0.25\n\nType 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n\nmysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):651
+msgid "Now we should test the user restriction(s). Let's switch to the gentoo database:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):655
+msgid "Switching to the gentoo database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):655
+#, no-wrap
+msgid "\nmysql&gt; <i>USE gentoo;</i>\nReading table information for completion of table and column names\nYou can turn off this feature to get a quicker startup with -A\n\nDatabase changed\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):663
+msgid "Now let's try to do something we are not supposed to. We'll attempt to create a table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):668
+msgid "Attempting to create a table with the guest user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):668
+#, no-wrap
+msgid "\nmysql&gt; <i>CREATE TABLE test (test VARCHAR(20), foobar VARCHAR(2));</i>\nERROR 1044: Access denied for user: 'guest@localhost' to database 'gentoo'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):673
+msgid "As you can see, this function fails, as our user does not have the appropriate access. However, one access we did grant is the <c>SELECT</c> statement. Let's go ahead and try that:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):679
+msgid "Attempting the SELECT statement"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):693
+msgid "The command succeeds, and we're given a glimpse of what user permissions can do. We did, however, create an admin account as well. This was created to show that even all permissions granted users can still have limitations. Go ahead and quit MySQL and login as the admin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):700
+msgid "Logging in as admin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):700
+#, no-wrap
+msgid "\nmysql&gt; <i>quit</i>\nBye\n$ <i>mysql -u admin -h localhost -p</i>\nEnter password:\nWelcome to the MySQL monitor. Commands end with ; or \\g.\nYour MySQL connection id is 7 to server version: 4.0.25\n\nType 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n\nmysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):713
+msgid "To begin, we'll try creating a new database with our admin user. This admin user will have access similiar to the root MySQL account, and will be able to do any kind of modification to the gentoo database it chooses. This will test the user's access to the main MySQL database. Remember ealier that we only set permissions to a specific database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):721
+msgid "Attempting to create a new database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):721
+#, no-wrap
+msgid "\nmysql&gt; <i>CREATE DATABASE gentoo2;</i>\nERROR 1044: Access denied for user: 'admin@localhost' to database 'gentoo2'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):726
+msgid "Indeed, the admin user cannot create databases on the main MySQL database, despite all his permissions on the gentoo database. However, we're still able to use the admin account to modify the gentoo database, as shown here by this example data insertion."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):733
+msgid "Admin permissions in gentoo database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):733
+#, no-wrap
+msgid "\nmysql&gt; <i>USE gentoo;</i>\nReading table information for completion of table and column names\nYou can turn off this feature to get a quicker startup with -A\n\nDatabase changed\nmysql&gt; <i>INSERT INTO developers VALUES('Bob Simmons', 'bobsimmons@gentoo.org', 'python');</i>\nQuery OK, 1 row affected (0.08 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):743
+msgid "The admin user can access the database as they please. Now sometimes, we need to get rid of user permissions. This could be anything from a problematic user to a retired employee. Let's take a look at how to disable user permissions with the <c>REVOKE</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):753
+msgid "Removing User Access With The REVOKE Command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):756
+msgid "The <c>REVOKE</c> command lets us deny access to a user. We can either deny full access, or specific access. In fact, the format is very similiar to <c>GRANT</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):762
+msgid "REVOKE Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):762
+#, no-wrap
+msgid "\nREVOKE [privileges] ON database.* FROM '[user]'@'[host]';\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):766
+msgid "Options here are explained in the <c>GRANT</c> command section. In this section however, we're going to deny full access to a user. Let's say we find out the guest account is causing some problems security wise. We decide to revoke all privileges. We login as root and do the needful."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):773
+msgid "Revoking user permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):773
+#, no-wrap
+msgid "\nmysql&gt; <i>REVOKE ALL ON gentoo.* FROM 'guest'@'localhost';</i>\nQuery OK, 0 rows affected (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(note):778
+msgid "In this case, user access is simple, so per database revoking is not a problem. However, in larger cases, you would most likely be using *.* instead of gentoo.* to remove user access to all other databases."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):784
+msgid "Now let's quit and attempt to login as a guest user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):788
+msgid "Attempting guest user login"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):788
+#, no-wrap
+msgid "\n$ <i>mysql -u guest -h localhost -p</i>\nEnter password:\nWelcome to the MySQL monitor. Commands end with ; or \\g.\nYour MySQL connection id is 9 to server version: 4.0.25\n\nType 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n\nmysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):799
+msgid "Although we're able to login, our access to gentoo is now gone."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):803
+msgid "Denied access to guest account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):803
+#, no-wrap
+msgid "\nmysql&gt; <i>USE gentoo;</i>\nERROR 1044: Access denied for user: 'guest@localhost' to database 'gentoo'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):808
+msgid "And our problematic user is no longer able to access the gentoo database. Please note that the user was still able to login. That is because they remain in the main MySQL database. Let's take a look at how to completely remove an account with <c>DELETE</c> and the MySQL user table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):818
+msgid "Removing Accounts Using DELETE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):821
+msgid "The MySQL user table is a listing of all users and information about them. Make sure you're logged in as root. Then go ahead and use the main MySQL database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):826
+msgid "Using the main mysql database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):826
+#, no-wrap
+msgid "\nmysql&gt; <i>USE mysql;</i>\nReading table information for completion of table and column names\nYou can turn off this feature to get a quicker startup with -A\n\nDatabase changed\nmysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):835
+msgid "Now let's see what tables the mysql database has:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):839
+msgid "mysql database table listing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):839
+#, no-wrap
+msgid "\nmysql&gt; <i>SHOW TABLES;</i>\n+-----------------+\n| Tables_in_mysql |\n+-----------------+\n| columns_priv    |\n| db              |\n| func            |\n| host            |\n| tables_priv     |\n| user            |\n+-----------------+\n6 rows in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):854
+msgid "The user table is the table we're after. However, the user table contains 30 different fields, making it very hard to read. In order to make things easier to read, we'll go ahead and use the third version of the <c>SELECT</c> statement. The fields we're after are Host and User."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):861
+msgid "Finding our guest user in the user table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):861
+#, no-wrap
+msgid "\nmysql&gt; <i>SELECT Host,User FROM user WHERE User = 'guest';</i>\n+-----------+-------+\n| Host      | User  |\n+-----------+-------+\n| localhost | guest |\n+-----------+-------+\n1 row in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):871
+msgid "Now that we have our information, we can get rid of the guest user. This is done with the <c>DELETE</c> command and the syntax is shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):876
+msgid "DELETE Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):876
+#, no-wrap
+msgid "\nDELETE FROM table WHERE field='value';\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):880
+msgid "You may notice that <c>DELETE</c> is somewhat similiar to the <c>SELECT</c> statement in its format. In this case, the field will be User, and the value guest. This will delete the record in the user table where the user is guest, successfully deleting our guest user account. Let's go ahead and do that:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):887
+msgid "Deleting the guest account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):887
+#, no-wrap
+msgid "\nmysql&gt; <i>DELETE FROM user WHERE User='guest';</i>\nQuery OK, 1 row affected (0.07 sec)\n<comment>(FLUSH PRIVILEGES is needed to update user permissions)</comment>\nmysql&gt; <i>FLUSH PRIVILEGES;</i>\nQuery OK, 0 rows affected (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):895
+msgid "It seems to have worked ok. Let's test by logging out and attempting to login as our guest user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):900
+msgid "Attempting login as the guest user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):900
+#, no-wrap
+msgid "\nmysql&gt; <i>quit</i>\nBye\n$ <i>mysql -u guest -h localhost -p</i>\nEnter password:\nERROR 1045: Access denied for user: 'guest@localhost' (Using password: YES)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):908
+msgid "Our user is now successfully deleted!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):915
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):918
+msgid "While this guide focuses mainly on setting up MySQL on the command line, a few alternatives are available in GUI form:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):924
+msgid "<uri link=\"http://www.phpmyadmin.net/home_page/\">phpMyAdmin</uri> - Popular php based MySQL administration tool."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):928
+msgid "<uri link=\"http://sourceforge.net/projects/mysqlnavigator/\">mysqlnavigator</uri> - QT frontend to MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):933
+msgid "<uri link=\"http://gmyclient.sourceforge.net/\">gmyclient</uri> - A GNOME based MySQL client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):937
+msgid "<uri link=\"http://www.knoda.org/\">knoda</uri> - A KDE MySQL client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):940
+msgid "This ends the MySQL introductory tutorial. I hope this gives you a better understanding of the basics behind MySQL and getting a database set up. Please email me at <mail>chriswhite@gentoo.org</mail> if you have any comments."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/mysql-upgrade-slotted.xml.pot b/doc/gettext/mysql-upgrade-slotted.xml.pot
new file mode 100644
index 0000000..c7e7ac9
--- /dev/null
+++ b/doc/gettext/mysql-upgrade-slotted.xml.pot
@@ -0,0 +1,92 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(guide:link):5
+msgid "/doc/en/mysql-upgrade-slotted.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(title):6
+msgid "\"Unslotting\" a slotted MySQL Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(mail:link):9
+msgid "vivo@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(mail):9
+msgid "Francesco Riosa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(mail:link):12
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(mail):12
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(abstract):15
+msgid "This document describes how to go back to an unslotted MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(version):23
+msgid "6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(date):24
+msgid "2006-03-10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(title):27
+msgid "Upgrading to an unslotted MySQL version from a slotted one"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(title):29
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(p):32
+msgid "Due to the negative response from our user base, the MySQL team has decided to go back to unslotted MySQL. In other words, installing different versions of MySQL on the same system is not supported anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(p):38
+msgid "If you had upgraded to the slotted version, this guide should help you upgrade to the unslotted version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(title):46
+msgid "\"Unslotting\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(p):49
+msgid "The following script should do most of the work:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(pre:caption):53
+msgid "\"Unslotting\" script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(p):90
+msgid "It is also recommended that you move data directories listed in <path>/etc/mysql/my.cnf</path>. If you do that, don't forget to edit <path>/etc/mysql/my.cnf</path> as well."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/mysql-upgrading.xml.pot b/doc/gettext/mysql-upgrading.xml.pot
new file mode 100644
index 0000000..1da3fc2
--- /dev/null
+++ b/doc/gettext/mysql-upgrading.xml.pot
@@ -0,0 +1,366 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(guide:link):5
+msgid "/doc/en/mysql-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):6
+msgid "Upgrade guide to MySQL 4.* or 5.0.*"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(mail:link):9
+msgid "citizen428@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(mail):9
+msgid "Michael Kohl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(mail:link):12
+msgid "vivo@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(mail):12
+msgid "Francesco Riosa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(abstract):15
+msgid "The MySQL herd is proud to announce that MySQL 5.0 will soon be found in Gentoo's stable tree. This document describes how to upgrade to MySQL 4.* and to 5.0.*."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(version):25
+msgid "1.17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(date):26
+msgid "2007-06-04"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):29
+msgid "Straight upgrade, suggested for 4.1 =&gt; 5.0 migration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):33
+msgid "The myisam storage engine in version 4.1 was already mature enough to allow a direct upgrade to the next major version of MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(note):38
+msgid "This is not true for MERGE tables. You will likely run into trouble if you attempt a direct upgrade for this (rarely used) type of table. You should dump and recreate those tables and restore their contents in the process of upgrading. If unsure, you should begin with <uri link=\"#doc_chap2\">Upgrading from old versions of MySQL</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):46
+msgid "For this step two shells are required because locks belong to the mysql session."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):51
+msgid "Straight upgrade from 4.1 to 5.0.*"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):51
+#, no-wrap
+msgid "\n# <i>quickpkg dev-db/mysql</i>\n# <i>alias MYSQL=\"mysql --user=root --password=</i><comment>'your_password'</comment><i>\"</i>\n# <i>DATADIR=$(MYSQL --batch --raw --silent --skip-column-names \\</i>\n     <i>--execute='SHOW variables LIKE \"datadir\";' \\</i>\n     <i>| sed -e 's|datadir[ \\t]||')</i>\n\n<comment>(This next step should be done in the second shell)</comment>\n# <i>mysql --user=root --password=</i><comment>'your_password'</comment>\nmysql&gt; <i>FLUSH TABLES WITH READ LOCK;</i>\n\n<comment>(Return to the first shell to run this command)</comment>\n# <i>tar -cjpvf ~/mysql.$(date +%F\"T\"%H-%M).tar.bz2 \\</i>\n     <i>/etc/conf.d/mysql /etc/mysql/my.cnf \"${DATADIR}\"</i>\n\n<comment>(The following commands should be done in the second shell)</comment>\nmysql&gt; <i>UNLOCK TABLES;</i>\nmysql&gt; <i>quit</i>\n\n<comment>(Return to the first shell for the rest of the upgrade)</comment>\n# <i>tar -tjvf ~/mysql.*.tar.bz2</i>\n# <i>emerge -av \"&gt;dev-db/mysql-5.0\"</i>\n# <i>dispatch-conf</i>\n# <i>revdep-rebuild</i>\n# <i>/etc/init.d/mysql restart</i>\n# <i>mysql_upgrade_shell --user=root --password=</i><comment>'your_password'</comment><i> \\</i>\n     <i>--protocol=tcp --datadir=\"${DATADIR}\"</i>\n# <i>/etc/init.d/mysql restart</i>\n# <i>unset DATADIR</i>\n# <i>unalias MYSQL</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):88
+msgid "Upgrading from old versions of MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):92
+msgid "Users upgrading from an old version (&lt;4.0.24) of MySQL will first have to install MySQL 4.0.25. If you are already running a more recent version, you can skip this section and continue with the <uri link=\"#backup\">next one</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):98
+msgid "Simple upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):98
+#, no-wrap
+msgid "\n# <i>emerge -av --buildpkg \"&lt;mysql-4.1\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):107
+msgid "Creating a backup of your current data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):111
+msgid "Values inside primary keys are handled differently in various MySQL versions, see <uri link=\"http://bugs.gentoo.org/108502\">bug #108502</uri> for more details, it is higly recommended to scan your tables for values of \"0\" (zero) or less and update them to a value greater than or equal to \"1\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):118
+msgid "One of the most important tasks that every database administrator has to perform is backing up data. Here we go:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):123
+msgid "Dump of all databases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):123
+#, no-wrap
+msgid "\n# <i>mysqldump \\</i>\n  <i>-uroot \\</i>\n  <i>--password=</i><comment>'your_password'</comment><i> \\</i>\n  <i>-hlocalhost \\</i>\n  <i>--all-databases \\</i>\n  <i>--opt \\</i>\n  <i>--allow-keywords \\</i>\n  <i>--flush-logs \\</i>\n  <i>--hex-blob \\</i>\n  <i>--master-data \\</i>\n  <i>--max_allowed_packet=16M \\</i>\n  <i>--quote-names \\</i>\n  <i>--result-file=BACKUP_MYSQL_4.0.SQL</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):139
+msgid "Now a file named <path>BACKUP_MYSQL_4.0.SQL</path> should exist, which can be used later to recreate your data. The data is described in the MySQL dialect of SQL, the Structured Query Language."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):145
+msgid "Now would also be a good time to see if the backup you have created is working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):154
+msgid "Upgrading from recent versions of MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):158
+msgid "If you have skipped step #1, you now have to create a backup package (of the database server, not the data) of the currently installed version:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):163
+msgid "Binary package backup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):163
+#, no-wrap
+msgid "\n# <i>quickpkg dev-db/mysql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):167
+msgid "Now it's time to clean out the current version and all of its data:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):171
+msgid "Uninstall MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):171
+#, no-wrap
+msgid "\n# <i>/etc/init.d/mysql stop</i>\n# <i>emerge -C mysql</i>\n# <i>tar cjpvf ~/mysql.$(date +%F\"T\"%H-%M).tar.bz2 /etc/mysql/my.cnf /var/lib/mysql/</i>\n# <i>ls -l ~/mysql.*</i>\n# <i>rm -rf /var/lib/mysql/ /var/log/mysql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(note):179
+msgid "Now two different backups should exist: the SQL one, which is portable between various versions of MySQL, and the other one that will allow you to quickly restore your database. This is covered later in this document in more detail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):185
+msgid "After you get rid of your old MySQL installation, you can now install the new version. Note that <c>revdep-rebuild</c> is necessary for rebuilding packages linking against MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):191
+msgid "Upgrading the binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):191
+#, no-wrap
+msgid "\n# <i>emerge -av \"&gt;mysql-4.1\"</i>\n<comment>(Update your config files, you may also use dispatch-conf)</comment>\n# <i>etc-update</i>\n# <i>revdep-rebuild</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):198
+msgid "Now configure the newly installed version of MySQL and restart the daemon:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):202
+msgid "Configure MySQL 4.1 base setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):202
+#, no-wrap
+msgid "\n# <i>emerge --config =mysql-4.1.<comment>&lt;micro_version&gt;</comment></i>\n# <i>/etc/init.d/mysql start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):207
+msgid "Finally you can import the backup you have created during step #2."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):211
+msgid "The default <path>/etc/mysql/my.cnf</path> file sets binary logging on (<c>log-bin</c>) by default. This will log every single transaction that modifies data. If run on a very large database (1GB or more), this could create extremely large files that take up disk space rather quickly. If you are low on space, disabling binary logging might be a good idea."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):219
+msgid "The default character set in MySQL 4.1 and above is <c>utf8</c>. If the data contain <e>non</e>-ASCII characters, you may want to preserve the default character set of the database replacing all occurrences of <c>utf8</c> with <c>latin1</c> in the <path>/etc/mysql/my.cnf</path> config file. More information can be found <uri link=\"#On_charset_conversion\">Charset conversion</uri> chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):228
+msgid "The administrative <c>mysql</c> database that contains user names, passwords amongst other things is and <b>must</b> be encoded in utf8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):233
+msgid "Older mysqldump utilities may export tables in the wrong order when foreign keys are involved. To work around this problem, surround the SQL with the following statements:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):239
+msgid "Fixing foreign key checks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):239
+#, no-wrap
+msgid "\nSET FOREIGN_KEY_CHECKS=0\nSET FOREIGN_KEY_CHECKS=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):244
+msgid "Next, import the backup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):248
+msgid "Importing the SQL backup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):248
+#, no-wrap
+msgid "\n# <i>cat BACKUP_MYSQL_4.0.SQL \\</i>\n     <i>| mysql \\</i>\n     <i>-uroot \\</i>\n     <i>--password=</i><comment>'your_password'</comment><i> \\</i>\n     <i>-hlocalhost \\</i>\n     <i>--max_allowed_packet=16M</i>\n\n# <i>mysql_fix_privilege_tables \\</i>\n     <i>--defaults-file=/etc/mysql/my.cnf \\</i>\n     <i>--user=root \\</i>\n     <i>--password=</i><comment>'your_password'</comment><i></i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):262
+msgid "If you restart your MySQL daemon now and everything goes as expected, you have a fully working version of 4.1.x."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):267
+msgid "Restart the MySQL instance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):267
+#, no-wrap
+msgid "\n# <i>/etc/init.d/mysql restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):271
+msgid "If you encountered any problems during the upgrade process, please report them on <uri link=\"http://bugs.gentoo.org\">Bugzilla</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):281
+msgid "Recover the old installation of MySQL 4.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):285
+msgid "If you are not happy with MySQL 4.1, it's possible to go back to MySQL 4.0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):289
+msgid "Reverting to the previous version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):289
+#, no-wrap
+msgid "\n# <i>/etc/init.d/mysql stop</i>\n# <i>emerge -C mysql</i>\n# <i>rm -rf /var/lib/mysql/ /var/log/mysql</i>\n# <i>emerge --usepkgonly \"&lt;mysql-4.1\"</i>\n<comment>(Replace &lt;timestamp&gt; with the one used when creating the backup.)</comment>\n# <i>tar -xjpvf mysql.&lt;timestamp&gt;.tar.bz2 -C /</i>\n# <i>/etc/init.d/mysql start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):299
+msgid "If packages other than <c>dev-db/mysql</c> have been emerged following this guide, you need to run <c>revdep-rebuild</c> to ensure that every client is using the correct mysqlclient shared object."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):310
+msgid "On charset conversion:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):312
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):315
+msgid "This chapter is not intended to be an exhaustive guide on how to do such conversions, rather a short list of hints on which the reader can elaborate."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):320
+msgid "Converting a database may be a complex task and difficulty increases with data variancy. Things like serialized object and blobs are one example where it's difficult to keeps pieces together."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):329
+msgid "Indexes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):332
+msgid "Every utf-8 character is considered 3 bytes long within an index. Indexes in MySQL can be up to 1000 bytes long (767 bytes for InnoDB tables). Note that the limits are measured in bytes, whereas the length of a column is interpreted as number of characters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):339
+msgid "MySQL can also create indexes on parts of a column, this can be of some help. Below are some examples:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):344
+msgid "Indexing using prefixes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):344
+#, no-wrap
+msgid "\n$ <i>mysql -uroot -p'<comment>your_password</comment>' test</i>\n\nmysql&gt; <i>SHOW variables LIKE \"version\" \\G</i>\n*************************** 1. row ***************************\nVariable_name: version\n    Value: <comment>5.0.24-log</comment>\n1 row in set (0.00 sec)\n\nmysql&gt; <i>CREATE TABLE t1 (</i>\n  -&gt;   <i>c1 varchar(255) NOT NULL default '',</i>\n  -&gt;   <i>c2 varchar(255) NOT NULL default ''</i>\n  -&gt;   <i>) ENGINE=MyISAM DEFAULT CHARSET=utf8;</i>\nQuery OK, 0 rows affected (0.01 sec)\n\nmysql&gt; <i>ALTER TABLE t1</i>\n  -&gt;   <i>ADD INDEX idx1 ( c1 , c2 );</i>\n<comment>ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes</comment>\n\nmysql&gt; <i>ALTER TABLE t1</i>\n  -&gt;   <i>ADD INDEX idx1 ( c1(165) , c2(165) );</i>\nQuery OK, 0 rows affected (0.01 sec)\nRecords: 0  Duplicates: 0  Warnings: 0\n\nmysql&gt; <i>CREATE TABLE t2 (</i>\n  -&gt;   <i>c1 varchar(255) NOT NULL default '',</i>\n  -&gt;   <i>c2 varchar(255) NOT NULL default ''</i>\n  -&gt;   <i>) ENGINE=MyISAM DEFAULT CHARSET=sjis;</i>\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql&gt; <i>ALTER TABLE t2</i>\n  -&gt;   <i>ADD INDEX idx1 ( c1(250) , c2(250) );</i>\nQuery OK, 0 rows affected (0.03 sec)\nRecords: 0  Duplicates: 0  Warnings: 0\n\nmysql&gt; <i>CREATE TABLE t3 (</i>\n  -&gt;   <i>c1 varchar(255) NOT NULL default '',</i>\n  -&gt;   <i>c2 varchar(255) NOT NULL default ''</i>\n  -&gt;   <i>) ENGINE=MyISAM DEFAULT CHARSET=latin1;</i>\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql&gt; <i>ALTER TABLE t3</i>\n  -&gt;   <i>ADD INDEX idx1 ( c1 , c2 );</i>\nQuery OK, 0 rows affected (0.03 sec)\nRecords: 0  Duplicates: 0  Warnings: 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):394
+msgid "Environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):397
+msgid "The system must be configured to support the UTF-8 locale. You will find more information in our <uri link=\"/doc/en/utf-8.xml\">Using UTF-8 with Gentoo</uri> and <uri link=\"/doc/en/guide-localization.xml\">Localization Guide</uri> documents."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):404
+msgid "In this example, we set some shell environment variables to make use of the English UTF-8 locale in <path>/etc/env.d/02locale</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):409
+msgid "/etc/env.d/02locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):409
+#, no-wrap
+msgid "\nLC_ALL=en_US.UTF-8\nLANG=en_US.UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):414
+msgid "Be sure to run <c>env-update &amp;&amp; source /etc/profile</c> afterward."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):421
+msgid "iconv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):424
+msgid "<c>iconv</c>, provided by <c>sys-libs/glibc</c>, is used to convert text files from one charset to another. The <c>app-text/recode</c> package can be used as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):430
+msgid "Using iconv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):430
+#, no-wrap
+msgid "\n<comment>(From latin1 to utf8)</comment>\n$ <i>iconv -f ISO-8859-15 -t UTF-8 file1.sql &gt; file2.sql</i>\n\n<comment>(From Japanese to utf8)</comment>\n$ <i>iconv -f ISO2022JP -t UTF-8 file1.sql &gt; file2.sql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):438
+msgid "<c>iconv</c> can be used to recode a sql dump even if the environment is not set to utf8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):446
+msgid "SQL Mangling"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):449
+msgid "It's possible to use the <c>CONVERT()</c> and <c>CAST()</c> MySQL functions to convert data in your SQL scripts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):457
+msgid "Apache (webserver)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):460
+msgid "To use utf-8 with apache, you need to adjust the following variables in <path>httpd.conf</path>: AddDefaultCharset, CharsetDefault, CharsetSourceEnc. If your source html files aren't encoded in utf-8, they <b>must</b> be converted with <c>iconv</c> or <c>recode</c>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/nagios-guide.xml.pot b/doc/gettext/nagios-guide.xml.pot
new file mode 100644
index 0000000..13d0214
--- /dev/null
+++ b/doc/gettext/nagios-guide.xml.pot
@@ -0,0 +1,383 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):6
+msgid "Gentoo System Monitoring with Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(abstract):12
+msgid "For system and network monitoring, the Nagios tool is a popular choice amongst various free software users. This guide helps you discover Nagios and how you can integrate it with your existing Gentoo infrastructure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(version):20
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(date):21
+msgid "2010-03-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):24 ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):225
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):26
+msgid "System Monitoring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):29
+msgid "Single system users usually don't need a tool to help them identify the state of their system. However, when you have a couple of systems to administer, you will require an overview of your systems' health: do the partitions still have sufficient free space, is your CPU not overloaded, how many people are logged on, are your systems up to date with the latest security fixes, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):37
+msgid "System monitoring tools, such as the Nagios software we discuss here, offer an easy way of dealing with the majority of metrics you want to know about your system. In larger environments, often called \"enterprise environments\", the tools aggregate the metrics of the various systems onto a single location, allowing for centralized monitoring management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):48
+msgid "About Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):51
+msgid "The <uri link=\"http://www.nagios.org\">Nagios</uri> software is a popular software tool for host, service and network monitoring for Unix (although it can also capture metrics from the Microsoft Windows operating system family). It supports:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):59
+msgid "obtaining metrics for local system resources, such as diskspace, CPU usage, memory consumption, ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):63
+msgid "discovering service availability (such as SSH, SMTP and other protocols),"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):66
+msgid "assuming network outages (when a group of systems that are known to be available on a network are all unreachable),"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):72
+msgid "and more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):76
+msgid "Basically, the Nagios software consists of a core tool (which manages the metrics), a web server module (which manages displaying the metrics) and a set of plugins (which obtain and send the metrics to the core tool)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):85
+msgid "About this Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):88
+msgid "The primary purpose of this document is to introduce you, Gentoo users, to the Nagios software and how you can integrate it within your Gentoo environment. The guide is not meant to describe Nagios in great detail - I leave this up to the documentation editors of Nagios itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):99
+msgid "Setting Up Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):101 ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):121
+msgid "Installing Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):104
+msgid "Before you start installing Nagios, draw out and decide which system will become your master Nagios system (i.e. where the Nagios software is fully installed upon and where all metrics are stored) and what kind of metrics you want to obtain. You will not install Nagios on every system you want to monitor, but rather install Nagios on the master system and the TODO on the systems you want to receive metrics from."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):113
+msgid "Install the Nagios software on your central server:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(warn):117
+msgid "Nagios 3 is currently still ~arch masked, so you first need to unmask it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):121
+#, no-wrap
+msgid "\n# <i>emerge nagios</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):125
+msgid "Follow the instructions the ebuild displays at the end of the installation (i.e. adding <c>nagios</c> to your active runlevel, configuring web server read access and more)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):131
+msgid "Really. Read it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):140
+msgid "Restricting Access to the Nagios Web Interface"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):143
+msgid "The Nagios web interface allows for executing commands on the various systems monitored by the Nagios plugins. For this purpose (and also because the metrics can have sensitive information) it is best to restrict access to the interface."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):149
+msgid "For this purpose, we introduce two access restrictions: one on IP level (from what systems can a user connect to the interface) and a basic authentication one (using the username / password scheme)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):155
+msgid "First, edit <path>/etc/apache2/modules/99_nagios3.conf</path> and edit the <c>allow from</c> definitions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):160
+msgid "Allow from definitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):160
+#, no-wrap
+msgid "\n<comment>(Example allowing access from the local host and the local network)</comment>\nOrder allow,deny\nAllow from 127.0.0.1 192.168.1.1/24\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):166
+msgid "Next, create an Apache authorization table where you define the users who have access to the interface as well as their authorizations. The authentication definition file is called <path>.htaccess</path> and contains where the authentication information itself is stored."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):173
+msgid "Example .htaccess file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):173
+#, no-wrap
+msgid "\nAuthName \"Nagios Access\"\nAuthType Basic\nAuthUserFile /etc/nagios/auth.users\nRequire valid-user\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):180
+msgid "Place this file inside the <path>/usr/share/nagios/htdocs</path> and <path>/usr/lib/nagios/cgi-bin</path> directories."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):185
+msgid "Create the <path>/etc/nagios/auth.users</path> file with the necessary user credentials. By default, the Gentoo nagios ebuild defines a single user called <c>nagiosadmin</c>. Let's create that user first:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):191
+msgid "Creating the nagiosadmin user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):191
+#, no-wrap
+msgid "\n# <i>htpasswd2 -c /etc/nagios/auth.users nagiosadmin</i>\n<comment>(Apache needs read access to auth.users)</comment>\n# <i>chown nagios:nagios /etc/nagios/auth.users</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):200
+msgid "Accessing Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):203
+msgid "Once Nagios and its dependencies are installed, fire up Apache and Nagios:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):207
+msgid "Starting the services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):207
+#, no-wrap
+msgid "\n# <i>/etc/init.d/nagios start</i>\n# <i>/etc/init.d/apache2 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):212
+msgid "Next, fire up your browser and connect to <uri link=\"http://localhost/nagios\">http://localhost/nagios</uri>. Log on as the <c>nagiosadmin</c> user and navigate to the <e>Host Detail</e> page. You should be able to see the monitoring states for the local system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):223
+msgid "Installing Client Daemons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):228
+msgid "There are various methods available to monitor remote hosts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):233
+msgid "Use the <e>NRPE</e> daemon on the remote host and have Nagios communicate to this daemon using the <path>check_nrpe</path> plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):237
+msgid "Use a password-less SSH connection to execute the command remotely"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):240
+msgid "Trap SNMP events and create Nagios alerts from it"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):245
+msgid "We focus on using the NRPE method as it is the most popular one and leave the other methods as an interesting excercise."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):253
+msgid "Installing NRPE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):256
+msgid "With NRPE, each remote host runs a daemon (the NRPE deamon) which allows the main Nagios system to query for certain metrics. One can run the NRPE daemon by itself or use an inetd program. I'll leave the inetd method as a nice exercise to the reader and give an example for running NRPE by itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):263
+msgid "First install the NRPE plugin:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):267
+msgid "Installing the NRPE plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):267
+#, no-wrap
+msgid "\n# <i>emerge nagios-nrpe</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):271
+msgid "Next, edit <path>/etc/nagios/nrpe.cfg</path> to allow your main Nagios system to access the NRPE daemon and customize the installation to your liking. Another important change to the <path>nrpe.cfg</path> file is the list of commands that NRPE supports. For instance, to use <c>nagios-nrpe</c> version 2.12 with Nagios 3, you'll need to change the paths from <path>/usr/nagios/libexec</path> to <path>/usr/lib/nagios/plugins</path>. Finally, launch the NRPE daemon:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):280
+msgid "Launching the NRPE daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):280
+#, no-wrap
+msgid "\n# <i>/etc/init.d/nrpe start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):284
+msgid "Finally, we need to configure the main Nagios system to connect to this particular NRPE instance and request the necessary metrics. To introduce you to Nagios' object syntax, our next section will cover this a bit more throroughly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):293
+msgid "Configuring a Remote Host"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(note):296
+msgid "The following hands-on tutorial is an example, used to introduce the user to Nagios' object model. Do not see this as the \"Best Practice\" for configuring Nagios."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):302
+msgid "First, edit <path>/etc/nagios/nagios.cfg</path> and place a <c>cfg_dir</c> directive. This will tell Nagios to read in all object configuration files in the said directory - in our example, the directory will contain the definitions for remote systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):309
+msgid "Editing /etc/nagios/nagios.cfg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):309
+#, no-wrap
+msgid "\ncfg_dir=/etc/nagios/objects/remote\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):313
+msgid "Create the directory and start with the first file, <path>nrpe-command.cfg</path>. In this file, we configure a Nagios command called <c>check_nrpe</c> which will be used to trigger a plugin (identified by the placeholder <c>$ARG1$</c>) on the remote system (identified by the placeholder <c>$HOSTADDRESS$</c>). The <c>$USER1$</c> variable is a default pointer to the Nagios installation directory (for instance, <path>/usr/nagios/libexec</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):323
+msgid "Defining the check_nrpe command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):323
+#, no-wrap
+msgid "\n# <i>nano /etc/nagios/objects/remote/nrpe-command.cfg</i>\n\ndefine command {\n  command_name check_nrpe\n  command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):332
+msgid "Next, create a file <path>nrpe-hosts.cfg</path> where we define the remote host(s) to monitor. In this example, we define two remote systems:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):337
+msgid "Defining two remote hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):337
+#, no-wrap
+msgid "\n# <i>nano /etc/nagios/objects/remote/nrpe-hosts.cfg</i>\n\ndefine host {\n  use linux-server\n  host_name webber\n  alias Gentoo Linux Web Server\n  address 192.168.2.1\n}\n\ndefine host {\n  use linux-server\n  host_name isync\n  alias Gentoo Linux RSync server\n  address 192.168.2.2\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):355
+msgid "Finally, define the service(s) you want to check on these hosts. As a prime example, we run the system load test and disk usage plugins:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):360
+msgid "Define the services to check"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):360
+#, no-wrap
+msgid "\n# <i>nano /etc/nagios/objects/remote/nrpe-services.cfg</i>\n\ndefine service {\n  use generic-service\n  host_name webber,isync\n  service_description Current Load\n  check_command check_nrpe!check_load\n}\n\ndefine service {\n  use generic-service\n  host_name webber,isync\n  service_description Root Partition\n  check_command check_nrpe!check_disk\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):378
+msgid "That's it. If you now check the service details on the Nagions monitoring site you'll see that the remote hosts are connected and are transmitting their monitoring metrics to the Nagios server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):387
+msgid "Using Passwordless SSH Connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):390
+msgid "Just as we did by creating the <c>check_nrpe</c> command, we can create a command that executes a command remotely through a passwordless SSH connection. We leave this up as an interesting exercise to the reader."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):396
+msgid "A few pointers and tips:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):401
+msgid "Make sure the passwordless SSH connection is set up for a dedicated user (definitely not root) - most checks you want to execute do not need root privileges anyway"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):406
+msgid "Creating a passwordless SSH key can be accomplished with <c>ssh-keygen</c>, you install a key on the destination system by adding the public key to the <path>.ssh/authorized_keys</path> file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):417
+msgid "More Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):419
+msgid "Adding Gentoo Checks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):422
+msgid "It is quite easy to extend Nagios to include Gentoo-specific checks, such as security checks (GLSAs). Gentoo developer Wolfram Schlich has a <c>check_glsa.sh</c> script <uri link=\"http://dev.gentoo.org/~wschlich/misc/nagios/nagios-plugins-extra/nagios-plugins-extra-4/plugins/\">available</uri> amongst others."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):433
+msgid "Nagios Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):437
+msgid "<uri>http://www.nagios.org</uri>, the official Nagios website"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):440
+msgid "<uri>http://www.nagiosexchange.org</uri>, where you can find Nagios plugins and addons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):444
+msgid "<uri>http://www.nagiosforge.org</uri>, where developers host Nagios addon projects"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):448
+msgid "<uri>http://www.nagioswiki.org</uri>, for more information and tutorials on Nagios"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/nano-basics-guide.xml.pot b/doc/gettext/nano-basics-guide.xml.pot
new file mode 100644
index 0000000..6738ba2
--- /dev/null
+++ b/doc/gettext/nano-basics-guide.xml.pot
@@ -0,0 +1,158 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(guide:link):5
+msgid "/doc/en/nano-basics-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):7
+msgid "Nano Basics Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(author:title):9
+msgid "Gentoo Doc Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(author):9
+msgid "Sherman Boyd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(author:title):12
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(mail:link):13
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(mail):13
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(abstract):16
+msgid "This guide is meant to be a simple introduction to nano. It will quickly help you to become familiar with its basic operation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(version):21
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(date):22
+msgid "2006-01-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):25
+msgid "Nano Basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):27
+msgid "Purpose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):30
+msgid "This guide was written to cover basic operations in nano, and is meant to be very concise. For more information about nano check out:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(uri):36 ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(uri):153
+msgid "http://www.nano-editor.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):42
+msgid "Opening and creating files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):45
+msgid "Opening and creating files is simple in nano, simply type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(pre:caption):49
+msgid "Creating or opening a file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(pre):49
+#, no-wrap
+msgid "\n# <i>nano filename</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):53
+msgid "Nano is a modeless editor so you can start typing immediately to insert text. If you are editing a configuration file like <path>/etc/fstab</path> use the <c>-w</c> switch, for example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(pre:caption):59
+msgid "Disable the word wrapping"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(pre):59
+#, no-wrap
+msgid "\n# <i>nano -w /etc/fstab</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(warn):63
+msgid "It is very, very important that you use the <c>-w</c> switch when opening a config file. Failure to do so may keep your system from booting or cause other bad things."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):72
+msgid "Saving and exiting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):75
+msgid "If you want to save the changes you've made, press <c>Ctrl+O</c>. To exit nano, type <c>Ctrl+X</c>. If you ask nano to exit from a modified file, it will ask you if you want to save it. Just press <c>N</c> in case you don't, or <c>Y</c> in case you do. It will then ask you for a filename. Just type it in and press <c>Enter</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):83
+msgid "If you accidentally confirmed that you want to save the file but you actually don't, you can always cancel by pressing <c>Ctrl+C</c> when you're prompted for a filename."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):92
+msgid "Cutting and pasting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):95
+msgid "To cut a single line, you use <c>Ctrl+K</c> (hold down <c>Ctrl</c> and then press <c>K</c>). The line disappears. To paste it, you simply move the cursor to where you want to paste it and punch <c>Ctrl+U</c>. The line reappears. To move multiple lines, simply cut them with several <c>Ctrl+K</c>s in a row, then paste them with a single <c>Ctrl+U</c>. The whole paragraph appears wherever you want it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):104
+msgid "If you need a little more fine-grained control, then you have to mark the text. Move the cursor to the beginning of the text you want to cut. Hit <c>Ctrl+6</c> (or <c>Alt+A</c>). Now move your cursor to the end of the text you want to cut: the marked text gets highlighted. If you need to cancel your text marking, simply hit <c>Ctrl+6</c> again. Press <c>Ctrl+K</c> to cut the marked text. Use <c>Ctrl+U</c> to paste it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):116
+msgid "Searching for text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):119
+msgid "Searching for a string is easy as long as you think <e>\"WhereIs\"</e> instead of <e>\"Search\"</e>. Simply hit <c>Ctrl+W</c>, type in your search string, and press <c>Enter</c>. To search for the same string again, hit <c>Alt+W</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(note):125
+msgid "In nano's help texts the Ctrl-key is represented by a caret (<c>^</c>), so <c>Ctrl+W</c> is shown as <c>^W</c>, and so on. The Alt-key is represented by an <c>M</c> (from \"Meta\"), so <c>Alt+W</c> is shown as <c>M-W</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):134
+msgid "More options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):137
+msgid "If you're interested in tweaking nano, be sure to read <path>/etc/nanorc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):144
+msgid "Wrap up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):147
+msgid "That is all! Thanks to kiyose and quazion from #gentoo. Again, for more information about nano check out:"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/new-upgrade-to-gentoo-1.4.xml.pot b/doc/gettext/new-upgrade-to-gentoo-1.4.xml.pot
new file mode 100644
index 0000000..4657423
--- /dev/null
+++ b/doc/gettext/new-upgrade-to-gentoo-1.4.xml.pot
@@ -0,0 +1,249 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(guide:link):7
+msgid "/doc/en/new-upgrade-to-gentoo-1.4.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):9
+msgid "Gentoo 1.4 Upgrade Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(mail:link):12
+msgid "rac@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(mail):12
+msgid "Robert Coie"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(author:title):14
+msgid "Copy Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(mail:link):15
+msgid "avenj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(mail):15
+msgid "Jon Portnoy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(abstract):18
+msgid "A method for upgrading older Gentoo installations in place to Gentoo 1.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(version):26
+msgid "0.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(date):27
+msgid "2005-07-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):30
+msgid "Before you begin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):32
+msgid "Be prepared"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):35
+msgid "As with any major upgrade to the core of your Gentoo system, there is always the possibility that unforeseen problems will ensue. It is always prudent to back up all important data before beginning this process. If possible, try to allocate a large block of time for this upgrade, so that you will not feel rushed. All the software on your machine will need to be recompiled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):46
+msgid "Other options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):49
+msgid "This is not the only way to upgrade your system. You can install a new 1.4 system onto a separate partition and reuse some of your system configuration instead. This method also has the advantage that you can always go back to your old system in the meantime as a fallback. You may also decide to simply not upgrade your system. If you decide you want to upgrade in place, read on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):60
+msgid "General notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):63
+msgid "Whenever the code listings suggest running the <c>emerge</c> command, it is always a good idea to make a test run of the command using the <c>-p</c> or <c>--pretend</c> option to make sure that the command will do what you expect it to do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):74
+msgid "Upgrading in place"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):76
+msgid "Get Portage as current as possible"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):79
+msgid "Some of the syntax of current ebuilds is unreadable by older versions of Portage. If you don't have at least Portage 2.0.44, try upgrading Portage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):84
+msgid "Updating Portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):84
+#, no-wrap
+msgid "\n# <i>emerge --sync</i>\n# <i>emerge -u portage</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(note):89
+msgid "If your Portage version is very old, you may get an error message containing the phrase \"unscriptable object\". Read and follow the instructions in <path>/usr/portage/sys-apps/portage/files/README.RESCUE</path>. Your Portage install should then be current."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):99
+msgid "Preparing GCC for cohabitation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):102
+msgid "You will be installing a newer version of GCC during this upgrade. Versions of GCC older than 2.95.3-r8 are not designed to have multiple versions of GCC installed. You must therefore upgrade GCC to at least version 2.95.3-r8. This will also have the beneficial side-effect of installing the <c>gcc-config</c> package on your system, which can be used to switch back and forth between various installed versions of GCC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):111
+msgid "Updating GCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):111
+#, no-wrap
+msgid "\n# <i>emerge -u gcc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):115
+msgid "You can now check to see if gcc-config is working properly:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):119
+msgid "Verifying GCC profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):119
+#, no-wrap
+msgid "\n# <i>gcc-config --get-current-profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):123
+msgid "This should return i686-pc-linux-gnu-2.95.3 on most x86 systems. Older systems may return i586-pc-linux-gnu-2.95.3."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):131
+msgid "Installing GCC 3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):134
+msgid "Now you can install a newer version of GCC without damaging your current compiler. Look in <path>/usr/portage/sys-devel/gcc</path> for a version of the GCC ebuild that is at least 3.2.1-r6. Choose the highest version that is marked stable for your architecture. To see if an ebuild is considered stable for your architecture, look for the KEYWORDS line in the ebuild file. If it has your architecture listed without a ~ in front of it, it is considered stable. Assuming 3.2.2 is the most current stable version, we first need to remove the glibc dependency from gcc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):145
+msgid "Edit <path>/usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</path> and search for the line containing <c>DEPEND</c>. Remove the <c>glibc</c> dependency and save the ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):151
+msgid "Editing gcc-3.2.2.ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):151
+#, no-wrap
+msgid "\n# <i>vim /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):155
+msgid "Now install the latest GCC version on your system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):159
+msgid "Install the latest GCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):159
+#, no-wrap
+msgid "\n# <i>USE=\"-java\" emerge /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):166
+msgid "Changing profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):169
+msgid "Now you need to change two sets of profiles: your gcc-config profile and your Portage profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):174
+msgid "Change the Portage profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):174
+#, no-wrap
+msgid "\n# <i>cd /etc</i>\n# <i>rm make.profile</i>\n<comment>(Replace \"x86\" with your architecture)</comment>\n# <i>ln -s ../usr/portage/profiles/default-x86-1.4 make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):181
+msgid "Change the GCC profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):181
+#, no-wrap
+msgid "\n<comment>(Note the one for the version you just emerged, use it below)</comment>\n# <i>gcc-config --list-profiles</i>\n<comment>(Replace with the version you noted above)</comment>\n# <i>gcc-config i686-pc-linux-gnu-3.2.2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):191
+msgid "Recompile toolchain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):194
+msgid "Now you need to recompile your core toolchain with your new compiler. If you are continuing in the same shell, you need to run <c>source /etc/profile</c> as gcc-config instructed you to. Then emerge glibc and binutils using your new compiler:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):201
+msgid "Rebuilding the toolchain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):201
+#, no-wrap
+msgid "\n# <i>emerge glibc binutils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(warn):205
+msgid "It is quite likely that you will upgrade glibc from a 2.2 or older version to 2.3. Do not downgrade glibc afterwards. Any software you have compiled against glibc 2.3 will stop working, and this can make your system unusable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):214
+msgid "Recompiling everything with your new compiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):217
+msgid "Now you may recompile everything on your system with your new compiler:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):221
+msgid "Rebuilding the entire system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):221
+#, no-wrap
+msgid "\n# <i>emerge -e world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(note):225
+msgid "If this command fails at any point due to errors, you can use <c>emerge --resume</c> to continue the process where you left off. This requires Portage 2.0.47 or later."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/nvidia-guide.xml.pot b/doc/gettext/nvidia-guide.xml.pot
new file mode 100644
index 0000000..ba34a41
--- /dev/null
+++ b/doc/gettext/nvidia-guide.xml.pot
@@ -0,0 +1,524 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):6
+msgid "Gentoo Linux nVidia Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail:link):12
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail):12
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail:link):15
+msgid "curtis119@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail):15
+msgid "M Curtis Napier"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail:link):18
+msgid "wolf31o2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail):18
+msgid "Chris Gianelloni"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(abstract):21
+msgid "Many Gentooists have an nVidia chipset on their system. nVidia provides specific Linux drivers to boost the performance of your card. This guide informs you how to install and configure these drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(version):31
+msgid "1.41"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(date):32
+msgid "2010-07-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):35
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):39
+msgid "The nVidia drivers in the tree are released by nVidia and are built against the Linux kernel. They contain a binary blob that does the heavy lifting for talking to the card. The drivers consist of two parts, a kernel module, and an X11 driver. Both parts are included in a single package. Due to the way nVidia has been packaging their drivers, you will need to make some choices before you install the drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):48
+msgid "The <c>nvidia-drivers</c> package contains the latest drivers from nVidia with support for <e>all</e> cards, with several versions available depending on how old your card is. It uses an eclass to detect what kind of card you're running so that it installs the proper version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):60
+msgid "Driver compatibility"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):62
+msgid "Which version?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):65
+msgid "The <c>nvidia-drivers</c> package supports the full range of available nVidia cards. Multiple versions are available for installation, depending on the card(s) you have."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):71
+msgid "Newer cards such as the GeForce 400, 300, 200, 100, 9, 8, 7, and 6 series should use the latest drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):76
+msgid "Older cards such as the GeForce FX 5 series should use the 173.x drivers, such as <c>nvidia-drivers-173.14.15</c>. For these cards, you should mask <c>&gt;=x11-drivers/nvidia-drivers-174.00</c> in your <path>/etc/portage/package.mask</path> file. This will prevent newer versions of the driver which are incompatible with your card from being installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):84
+msgid "Old cards such as the GeForce 3 or GeForce 4 series require the 96.x drivers. For these cards, you should mask <c>&gt;=x11-drivers/nvidia-drivers-97.00</c> in your <path>/etc/portage/package.mask</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):90
+msgid "The oldest NV2x-based cards (such as TNT, TNT2, GeForce, and GeForce 2) are no longer supported by <c>nvidia-drivers</c>. Instead, use an open-source driver: <c>xf86-video-nouveau</c> (recommended) or <c>xf86-video-nv</c> (old, deprecated)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):97
+msgid "You can check for driver compatibility for your card at to determine which driver supports it by viewing the README at its appropriate x86 or x86-64 <uri link=\"http://www.nvidia.com/object/unix.html\">release page</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):108
+msgid "Configuring your Card"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):110
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):113
+msgid "As mentioned above, the nVidia kernel driver installs and runs against your current kernel. It builds as a module, so it makes sense that your kernel must support the loading of kernel modules. If you used <c>genkernel all</c> to configure the kernel for you, then you're all set. If not, double check your kernel configuration so that this support is enabled:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):121
+msgid "Enabling the Loading of Kernel Modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):121
+#, no-wrap
+msgid "\nLoadable module support ---&gt;\n  [*] Enable loadable module support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):126
+msgid "You also need to enable <e>Memory Type Range Register</e> in your kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):130
+msgid "Enabling MTRR"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):130
+#, no-wrap
+msgid "\nProcessor and Features ---&gt;\n  [*] MTRR (Memory Type Range Register) support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):135
+msgid "Also, if you have an AGP graphics card, you can optionally enable <c>agpgart</c> support to your kernel, either compiled in or as a module. If you do not use the in-kernel agpgart, then the drivers will use their own <c>agpgart</c> implementation, called <c>NvAGP</c>. On certain systems, this performs better than the in-kernel agpgart, and on others, it performs worse. You will need to evaluate this on your own system to get the best performance. If you are unsure what to do, use the in-kernel agpgart:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):144
+msgid "Enabling agpgart"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):144
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\nGraphics Support ---&gt;\n-*- /dev/agpgart (AGP Support) ---&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(note):150
+msgid "On amd64, the IOMMU controls the agpgart setting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):157
+msgid "Arch-specific notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(impo):160
+msgid "For x86 and AMD64 processors, the in-kernel driver conflicts with the binary driver provided by nVidia. If you will be compiling your kernel for these CPUs, you must completely remove support for the in-kernel driver as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):166
+msgid "Remove the in-kernel driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):166
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\nGraphics Support ---&gt;\n&lt;*&gt; Support for frame buffer devices ---&gt;\n&lt; &gt;   nVidia Framebuffer Support\n&lt; &gt;   nVidia Riva support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):174
+msgid "A framebuffer alternative is <c>uvesafb</c>, an <uri link=\"http://dev.gentoo.org/~spock/projects/uvesafb/\">advanced framebuffer</uri>. Note that you can choose to compile it into your kernel, or as a module. The following example compiles uvesafb into the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):181
+msgid "Enable uvesafb support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):181
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\nGraphics Support ---&gt;\n&lt;*&gt; Support for frame buffer devices ---&gt;\n&lt;*&gt;   Userspace VESA VGA graphics support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):189
+msgid "Or you can try <c>VESA</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):193
+msgid "Enable VESA support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):193
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\nGraphics Support ---&gt;\n&lt;*&gt; Support for frame buffer devices ---&gt;\n[*]   VESA VGA graphics support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):201
+msgid "For more information, you can look up the documentation for your chosen framebuffer in <path>/usr/src/linux/Documentation/fb/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):209
+msgid "Continuing with Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):212
+msgid "The <c>nvidia-drivers</c> ebuild automatically discovers your kernel version based on the <path>/usr/src/linux</path> symlink. Please ensure that you have this symlink pointing to the correct sources and that your kernel is correctly configured. Please refer to the \"Configuring the Kernel\" section of the <uri link=\"/doc/en/handbook/\">Installation Handbook</uri> for details on configuring your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):221
+msgid "First, you'll need to choose the right kernel source using <c>eselect</c>. If you are using <c>gentoo-sources-2.6.34-r1</c>, your kernel listing might look something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):227
+msgid "Check your /usr/src/linux symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):227
+#, no-wrap
+msgid "\n# <i>eselect kernel list</i>\nAvailable kernel symlink targets:\n  [1]   linux-2.6.34-gentoo-r1 *\n  [2]   linux-2.6.33-gentoo-r2\n  [3]   linux-2.6.32.9\n<comment>(Verify that the right kernel is marked with an asterisk</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):236
+msgid "In the above output, you'll notice that the <c>linux-2.6.34-gentoo-r1</c> kernel is marked with an asterisk (<b>*</b>) to show that it is the symlinked kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):241
+msgid "If the symlink is not pointing to the correct sources, you must update the link by selecting the number of your desired kernel sources, as in the example above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):247
+msgid "Create/Update /usr/src/linux symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):247
+#, no-wrap
+msgid "\n<comment>(Select the correct kernel)</comment>\n# <i>eselect kernel set 1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):255
+msgid "Installing the Appropriate Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):258
+msgid "Now it's time to install the drivers. You can do this by first following the <uri link=\"/doc/en/xorg-config.xml\">X Server Configuration HOWTO</uri> and setting <c>VIDEO_CARDS=\"nvidia\"</c> in <path>/etc/make.conf</path>. When you install the X server, it will then install the right version of <c>nvidia-drivers</c> for you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(note):266
+msgid "The drivers can be installed with the <c>gtk</c> USE flag set in <path>/etc/make.conf</path>. This will install <c>media-video/nvidia-settings</c>, a handy graphical tool for monitoring and configuring several aspects of your nVidia card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(impo):273
+msgid "Every time you <uri link=\"/doc/en/kernel-upgrade.xml\">compile a new kernel</uri> or recompile the current one, you will need to reinstall the nVidia kernel modules. An easy way to keep track of modules installed by ebuilds (such as <c>nvidia-drivers</c>) is to install <c>sys-kernel/module-rebuild</c>. Once you've installed it, simply run <c>module-rebuild populate</c> to populate its database with a list of packages to be rebuilt. Once you've finished compiling or recompiling a kernel, just run <c>module-rebuild rebuild</c> to rebuild the drivers for your new kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):284
+msgid "Once the installation has finished, run <c>modprobe nvidia</c> to load the kernel module into memory. If this is an upgrade, you should remove the previous module first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):290
+msgid "Loading the kernel module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):290
+#, no-wrap
+msgid "\n# <i>lsmod | grep nvidia &amp;&amp; rmmod nvidia</i>\n# <i>modprobe nvidia</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):295
+msgid "To prevent you having to manually load the module on every bootup, you probably want to have this done automatically each time you boot your system, so edit <path>/etc/modules.autoload.d/kernel-2.6</path> and add <c>nvidia</c> to it. Don't forget to run <c>update-modules</c> afterwards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(impo):302
+msgid "If you compiled <c>agpgart</c> as a module, you will need to add it to <path>/etc/modules.autoload.d/kernel-2.6</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):307
+msgid "Running update-modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):307
+#, no-wrap
+msgid "\n# <i>update-modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):314
+msgid "Configuring the X Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):317
+msgid "Once the appropriate drivers are installed you need to configure your X Server to use the <c>nvidia</c> driver instead of the default <c>nv</c> driver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):322
+msgid "Open <path>/etc/X11/xorg.conf</path> with your favorite editor (such as <c>nano</c> or <c>vim</c>) and go to the <c>Device</c> section. In that section, change the <c>Driver</c> line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):328
+msgid "Changing nv to nvidia in the X Server configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):328
+#, no-wrap
+msgid "\nSection \"Device\"\n  Identifier \"nVidia Inc. GeForce2\"\n  <i>Driver     \"nvidia\"</i>\n  VideoRam   65536\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):336
+msgid "Then go to the <c>Module</c> section and make sure the <c>glx</c> module gets loaded while the <c>dri</c> module doesn't:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):341
+msgid "Updating the Module section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):341
+#, no-wrap
+msgid "\nSection \"Module\"\n  <comment>(...)</comment>\n  <i># Load  \"dri\"\n  Load  \"glx\"</i>\n  <comment>(...)</comment>\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):350
+msgid "Next, in section <c>Screen</c>, make sure that either the <c>DefaultDepth</c> directive is set to 16 or 24, or that you only have <c>Display</c> subsections with <c>Depth</c> settings of 16 or 24. Without it, the nVidia GLX extensions will not start."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):357
+msgid "Updating the Screen section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):357
+#, no-wrap
+msgid "\nSection \"Screen\"\n  <comment>(...)</comment>\n  <i>DefaultDepth 16</i>\n  Subsection \"Display\"\n  <comment>(...)</comment>\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):366
+msgid "Run <c>eselect</c> so that the X Server uses the nVidia GLX libraries:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):370
+msgid "Running eselect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):370
+#, no-wrap
+msgid "\n# <i>eselect opengl set nvidia</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):377
+msgid "Adding your Users to the video Group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):380
+msgid "You have to add your user to the <c>video</c> group so he has access to the nVidia device files:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):385
+msgid "Adding your user to the video group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):385
+#, no-wrap
+msgid "\n# <i>gpasswd -a youruser video</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):389
+msgid "This might not be totally necessary if you aren't using <c>udev</c> but it doesn't hurt either and makes your system future-proof."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):397
+msgid "Testing your Card"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):400
+msgid "To test your nVidia card, fire up X and run <c>glxinfo</c>, which is part of the <c>mesa-progs</c> package. It should say that direct rendering is activated:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):405
+msgid "Checking the direct rendering status"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):405
+#, no-wrap
+msgid "\n$ <i>glxinfo | grep direct</i>\ndirect rendering: Yes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):410
+msgid "To monitor your FPS, run <c>glxgears</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):417
+msgid "Enabling nvidia Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):420
+msgid "Some tools, such as <c>mplayer</c> and <c>xine-lib</c>, use a local USE flag called <c>xvmc</c> which enables XvMCNVIDIA support, useful when watching high resolution movies. Add in <c>xvmc</c> in your USE variable in <path>/etc/make.conf</path> or add it as USE flag to <c>media-video/mplayer</c> and/or <c>media-libs/xine-lib</c> in <path>/etc/portage/package.use</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):428
+msgid "There are also some applications that use the <c>nvidia</c> USE flag, so you may want to add it to <path>/etc/make.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):433
+msgid "Then, run <c>emerge -uD --newuse world</c> to rebuild the applications that benefit from the USE flag change."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):441
+msgid "Using NVidia Settings Tool"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):444
+msgid "nVidia also provides you with a settings tool. This tool allows you to monitor and change graphical settings without restarting the X server and is available through Portage as <c>media-video/nvidia-settings</c>. As mentioned earlier, it will be pulled in automatically if you install the drivers with the <c>gtk</c> USE flag set in <path>/etc/make.conf</path> or in <path>/etc/portage/package.use</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):458
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):460
+msgid "Getting 2D to work on machines with 4Gb or more memory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):463
+msgid "If you are having troubles with the nVidia 2D acceleration it is likely that you are unable to set up a write-combining range with MTRR. To verify, check the contents of <path>/proc/mtrr</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):469
+msgid "Checking if you have write-combining enabled"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):469
+#, no-wrap
+msgid "\n# <i>cat /proc/mtrr</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):473
+msgid "Every line should contain \"write-back\" or \"write-combining\". If you see a line with \"uncachable\" in it you will need to change a BIOS setting to fix this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):478
+msgid "Reboot and enter the BIOS, then find the MTRR settings (probably under \"CPU Settings\"). Change the setting from \"continuous\" to \"discrete\" and boot back into Linux. You will now find out that there is no \"uncachable\" entry anymore and 2D acceleration now works without any glitches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):488
+msgid "When I attempt to load the kernel module I receive a \"no such device\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):493
+msgid "This usually occurs when you don't have a matching video card. Make sure that you have an nVidia-powered graphical card (you can double-check this using <c>lspci</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):499
+msgid "If you are confident that you have an nVidia card, check your BIOS and see if the directive <e>Assign IRQ to VGA</e> is set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):509
+msgid "Expert Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):511
+msgid "Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):514
+msgid "The nVidia driver package also comes with comprehensive documentation. This is installed into <c>/usr/share/doc</c> and can be viewed with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):520
+msgid "Viewing the NVIDIA documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):520
+#, no-wrap
+msgid "\n$ <i>less /usr/share/doc/nvidia-drivers-*/README.gz</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):527
+msgid "Kernel module parameters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):530
+msgid "The <c>nvidia</c> kernel module accepts a number of parameters (options) which you can use to tweak the behaviour of the driver. Most of these are mentioned in the documentation. To add or change the values of these parameters, edit the file <c>/etc/modprobe.d/nvidia.conf</c>. Remember to run <c>update-modules</c> after modifying this file, and bear in mind that you will need to reload the <c>nvidia</c> module before the new settings take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):539
+msgid "Adjusting nvidia options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):539
+#, no-wrap
+msgid "\n<comment>(Edit /etc/modprobe.d/nvidia.conf in your favourite editor)</comment>\n# <i>nano -w /etc/modprobe.d/nvidia.conf</i>\n<comment>(Update module information)</comment>\n# <i>update-modules</i>\n<comment>(Unload the nvidia module...)</comment>\n# <i>modprobe -r nvidia</i>\n<comment>(...and load it once again)</comment>\n# <i>modprobe nvidia</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):553
+msgid "Advanced X configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):556
+msgid "The GLX layer also has a plethora of options which can be configured. These control the configuration of TV out, dual displays, monitor frequency detection, etc. Again, all of the available options are detailed in the documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):562
+msgid "If you wish to use any of these options, you need to list them in the relevant Device section of your X config file (usually <c>/etc/X11/xorg.conf</c>). For example, suppose I wanted to disable the splash logo:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):568
+msgid "Advanced nvidia configuration in the X configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):568
+#, no-wrap
+msgid "\nSection \"Device\"\n  Identifier \"nVidia Inc. GeForce2\"\n  Driver     \"nvidia\"\n  <i>Option     \"NoLogo\" \"true\"</i>\n  VideoRam   65536\nEndSection\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/openafs.xml.pot b/doc/gettext/openafs.xml.pot
new file mode 100644
index 0000000..dcceec4
--- /dev/null
+++ b/doc/gettext/openafs.xml.pot
@@ -0,0 +1,1200 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(guide:link):6
+msgid "/doc/en/openafs.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):7
+msgid "Gentoo Linux OpenAFS Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):9 ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):12 ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):15 ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):18 ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):21 ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):24
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):10
+msgid "stefaan@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):10
+msgid "Stefaan De Roeck"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):13
+msgid "darks@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):13
+msgid "Holger Brueckner"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):16
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):16
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):19
+msgid "blubber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):19
+msgid "Tiemo Kieft"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):22
+msgid "fnjordy@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):22
+msgid "Steven McCoy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):25
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):25
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(abstract):28
+msgid "This guide shows you how to install an OpenAFS server and client on Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(version):37
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(date):38
+msgid "2007-06-29"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):41
+msgid "Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):43
+msgid "About this Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):46
+msgid "This document provides you with all necessary steps to install an OpenAFS server on Gentoo Linux. Parts of this document are taken from the AFS FAQ and IBM's Quick Beginnings guide on AFS. Well, never reinvent the wheel. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):55
+msgid "What is AFS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):58
+msgid "AFS is a distributed filesystem that enables co-operating hosts (clients and servers) to efficiently share filesystem resources across both local area and wide area networks. Clients hold a cache for often used objects (files), to get quicker access to them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):66
+msgid "AFS is based on a distributed file system originally developed at the Information Technology Center at Carnegie-Mellon University that was called the \"Andrew File System\". \"Andrew\" was the name of the research project at CMU - honouring the founders of the University. Once Transarc was formed and AFS became a product, the \"Andrew\" was dropped to indicate that AFS had gone beyond the Andrew research project and had become a supported, product quality filesystem. However, there were a number of existing cells that rooted their filesystem as /afs. At the time, changing the root of the filesystem was a non-trivial undertaking. So, to save the early AFS sites from having to rename their filesystem, AFS remained as the name and filesystem root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):83
+msgid "What is an AFS cell?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):86
+msgid "An AFS cell is a collection of servers grouped together administratively and presenting a single, cohesive filesystem. Typically, an AFS cell is a set of hosts that use the same Internet domain name (for example, gentoo.org) Users log into AFS client workstations which request information and files from the cell's servers on behalf of the users. Users won't know on which server a file which they are accessing, is located. They even won't notice if a server will be located to another room, since every volume can be replicated and moved to another server without any user noticing. The files are always accessible. Well, it's like NFS on steroids :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):101
+msgid "What are the benefits of using AFS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):104
+msgid "The main strengths of AFS are its: caching facility (on client side, typically 100M to 1GB), security features (Kerberos 4 based, access control lists), simplicity of addressing (you just have one filesystem), scalability (add further servers to your cell as needed), communications protocol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):116
+msgid "Where can I get more information?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):119
+msgid "Read the <uri link=\"http://www.angelfire.com/hi/plutonic/afs-faq.html\">AFS FAQ</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):124
+msgid "OpenAFS main page is at <uri link=\"http://www.openafs.org\">www.openafs.org</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):129
+msgid "AFS was originally developed by Transarc which is now owned by IBM. You can find some information about AFS on <uri link=\"http://www.transarc.ibm.com/Product/EFS/AFS/index.html\">Transarc's Webpage</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):139
+msgid "How Can I Debug Problems?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):142
+msgid "OpenAFS has great logging facilities. However, by default it logs straight into its own logs instead of through the system logging facilities you have on your system. To have the servers log through your system logger, use the <c>-syslog</c> option for all <c>bos</c> commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):154
+msgid "Upgrading from previous versions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):156
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):159
+msgid "This section aims to help you through the process of upgrading an existing OpenAFS installation to OpenAFS version 1.4.0 or higher (or 1.2.x starting from 1.2.13. The latter will not be handled specifically, as most people will want 1.4 for a.o. linux-2.6 support, large file support and bug fixes)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):166
+msgid "If you're dealing with a clean install of a 1.4 version of OpenAFS, then you can safely skip this chapter. However, if you're upgrading from a previous version, we strongly urge you to follow the guidelines in the next sections. The transition script in the ebuild is designed to assist you in quickly upgrading and restarting. Please note that it will (for safety reasons) not delete configuration files and startup scripts in old places, not automatically change your boot configuration to use the new scripts, etc. If you need further convincing, using an old OpenAFS kernel module together with the updated system binaries, may very well cause your kernel to freak out. So, let's read on for a clean and easy transition, shall we?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):179
+msgid "This chapter has been written bearing many different system configurations in mind. Still, it is possible that due to peculiar tweaks a user has made, his or her specific situation may not be described here. A user with enough self-confidence to tweak his system should be experienced enough to apply the given remarks where appropriate. Vice versa, a user that has done little to his system but install the previous ebuild, can skip most of the warnings further on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):192
+msgid "Differences to previous versions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):195
+msgid "Traditionally, OpenAFS has used the same path-conventions that IBM TransArc labs had used, before the code was forked. Understandably, old AFS setups continue using these legacy path conventions. More recent setups conform with FHS by using standard locations (as seen in many Linux distributions). The following table is a compilation of the configure-script and the README accompanying the OpenAFS distribution tarballs:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):206
+msgid "Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):207
+msgid "Purpose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):208
+msgid "Transarc Mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):209
+msgid "Default Mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):210
+msgid "translation to Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):213
+msgid "viceetcdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):214
+msgid "Client configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):215
+msgid "/usr/vice/etc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):216
+msgid "$(sysconfdir)/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):217
+msgid "/etc/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):220
+msgid "unnamed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):221
+msgid "Client binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):222
+msgid "unspecified"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):223
+msgid "$(bindir)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):224
+msgid "/usr/bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):227
+msgid "afsconfdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):228
+msgid "Server configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):229
+msgid "/usr/afs/etc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):230
+msgid "$(sysconfdir)/openafs/server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):231
+msgid "/etc/openafs/server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):234
+msgid "afssrvdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):235
+msgid "Internal server binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):236
+msgid "/usr/afs/bin (servers)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):237
+msgid "$(libexecdir)/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):238
+msgid "/usr/libexec/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):241
+msgid "afslocaldir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):242
+msgid "Server state"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):243
+msgid "/usr/afs/local"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):244
+msgid "$(localstatedir)/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):245
+msgid "/var/lib/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):248
+msgid "afsdbdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):249
+msgid "Auth/serverlist/... databases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):250
+msgid "/usr/afs/db"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):251
+msgid "$(localstatedir)/openafs/db"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):252
+msgid "/var/lib/openafs/db"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):255
+msgid "afslogdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):256
+msgid "Log files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):257
+msgid "/usr/afs/logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):258
+msgid "$(localstatedir)/openafs/logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):259
+msgid "/var/lib/openafs/logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):262
+msgid "afsbosconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):263
+msgid "Overseer config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):264
+msgid "$(afslocaldir)/BosConfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):265
+msgid "$(afsconfdir)/BosConfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):266
+msgid "/etc/openafs/BosConfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):270
+msgid "There are some other oddities, like binaries being put in <path>/usr/vice/etc</path> in Transarc mode, but this list is not intended to be comprehensive. It is rather meant to serve as a reference to those troubleshooting config file transition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):277
+msgid "Also as a result of the path changes, the default disk cache location has been changed from <path>/usr/vice/cache</path> to <path>/var/cache/openafs</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):283
+msgid "Furthermore, the init-script has been split into a client and a server part. You used to have <path>/etc/init.d/afs</path>, but now you'll end up with both <path>/etc/init.d/openafs-client</path> and <path>/etc/init.d/openafs-server</path>. Consequently, the configuration file <path>/etc/conf.d/afs</path> has been split into <path>/etc/conf.d/openafs-client</path> and <path>/etc/conf.d/openafs-server</path>. Also, options in <path>/etc/conf.d/afs</path> to turn either client or server on or off have been obsoleted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):295
+msgid "Another change to the init script is that it doesn't check your disk cache setup anymore. The old code required that a separate ext2 partition be mounted at <path>/usr/vice/cache</path>. There were some problems with that:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):302
+msgid "Though it's a very logical setup, your cache doesn't need to be on a separate partition. As long as you make sure that the amount of space specified in <path>/etc/openafs/cacheinfo</path> really is available for disk cache usage, you're safe. So there is no real problem with having the cache on your root partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):309
+msgid "Some people use soft-links to point to the real disk cache location. The init script didn't like this, because then this cache location didn't turn up in <path>/proc/mounts</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):314
+msgid "Many prefer ext3 over ext2 nowadays. Both filesystems are valid for usage as a disk cache. Any other filesystem is unsupported (like: don't try reiserfs, you'll get a huge warning, expect failure afterwards)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):325
+msgid "Transition to the new paths"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):328
+msgid "First of all, emerging a newer OpenAFS version should not overwrite any old configuration files. The script is designed to not change any files already present on the system. So even if you have a totally messed up configuration with a mix of old and new locations, the script should not cause further problems. Also, if a running OpenAFS server is detected, the installation will abort, preventing possible database corruption."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):337
+msgid "One caveat though -- there have been ebuilds floating around the internet that partially disable the protection that Gentoo puts on <path>/etc</path>. These ebuilds have never been distributed by Gentoo. You might want to check the <c>CONFIG_PROTECT_MASK</c> variable in the output of the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):344
+msgid "Checking your CONFIG_PROTECT_MASK"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):344
+#, no-wrap
+msgid "\n# <i>emerge info | grep \"CONFIG_PROTECT_MASK\"</i>\nCONFIG_PROTECT_MASK=\"/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):349
+msgid "Though nothing in this ebuild would touch the files in <path>/etc/afs</path>, upgrading will cause the removal of your older OpenAFS installation. Files in <c>CONFIG_PROTECT_MASK</c> that belong to the older installation will be removed as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):356
+msgid "It should be clear to the experienced user that in the case he has tweaked his system by manually adding soft links (e.g. <path>/usr/afs/etc</path> to <path>/etc/openafs</path>), the new installation may run fine while still using the old configuration files. In this case, there has been no real transition, and cleaning up the old installation will result in a broken OpenAFS config."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):364
+msgid "Now that you know what doesn't happen, you may want to know what does:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):369
+msgid "<path>/usr/afs/etc</path> is copied to <path>/etc/openafs/server</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):372
+msgid "<path>/usr/vice/etc</path> is copied to <path>/etc/openafs</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):375
+msgid "<path>/usr/afs/local</path> is copied to <path>/var/lib/openafs</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):378
+msgid "<path>/usr/afs/local/BosConfig</path> is copied to <path>/etc/openafs/BosConfig</path>, while replacing occurrences of <path>/usr/afs/bin/</path> with <path>/usr/libexec/openafs</path>, <path>/usr/afs/etc</path> with <path>/etc/openafs/server</path> and <path>/usr/afs/bin</path> (without the / as previously) with <path>/usr/bin</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):386
+msgid "<path>/usr/afs/db</path> is copied to <path>/var/lib/openafs/db</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):389
+msgid "The configuration file <path>/etc/conf.d/afs</path> is copied to <path>/etc/conf.d/openafs-client</path>, as all known old options were destined for client usage only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):399
+msgid "The upgrade itself"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):402
+msgid "So you haven't got an OpenAFS server setup? Or maybe you do, the previous sections have informed you about what is going to happen, and you're still ready for it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):408
+msgid "Let's go ahead with it then!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):412
+msgid "If you do have a server running, you want to shut it down now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):416
+msgid "Stopping OpenAFS (in case you have a server)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):416 ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):439
+#, no-wrap
+msgid "\n# <i>/etc/init.d/afs stop</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):420
+msgid "And then the upgrade itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):424
+msgid "Now upgrade!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):424
+#, no-wrap
+msgid "\n# <i>emerge -u openafs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):431
+msgid "Restarting OpenAFS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):434
+msgid "If you had an OpenAFS server running, you would have not have been forced to shut it down. Now is the time to do that."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):439
+msgid "Stopping OpenAFS client after upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):443
+msgid "As you may want keep the downtime to a minimum, so you can restart your OpenAFS server right away."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):448
+msgid "Restarting OpenAFS server after upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):448
+#, no-wrap
+msgid "\n# <i>/etc/init.d/openafs-server start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):452
+msgid "You can check whether it's running properly with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):456
+msgid "Checking OpenAFS server status"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):456
+#, no-wrap
+msgid "\n# <i>/usr/bin/bos status localhost -localauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):460
+msgid "Before starting the OpenAFS client again, please take time to check your cache settings. They are determined by <path>/etc/openafs/cacheinfo</path>. To restart your OpenAFS client installation, please type the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):466
+msgid "Restarting OpenAFS client after upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):466
+#, no-wrap
+msgid "\n# <i>/etc/init.d/openafs-client start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):473
+msgid "Cleaning up afterwards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):476
+msgid "Before cleaning up, please make really sure that everything runs smoothly and that you have restarted after the upgrade (otherwise, you may still be running your old installation)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(impo):482
+msgid "Please make sure you're not using <path>/usr/vice/cache</path> for disk cache if you are deleting <path>/usr/vice</path>!!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):487
+msgid "The following directories may be safely removed from the system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):498
+msgid "The following files are also unnecessary:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):507
+msgid "Removing the old files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):507
+#, no-wrap
+msgid "\n# <i>tar czf /root/oldafs-backup.tgz /etc/afs /usr/vice /usr/afs /usr/afsws</i>\n# <i>rm -R /etc/afs /usr/vice /usr/afs /usr/afsws</i>\n# <i>rm /etc/init.d/afs /etc/conf.d/afs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):513
+msgid "In case you've previously used ebuilds =openafs-1.2.13 or =openafs-1.3.85, you may also have some other unnecessary files:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):528
+msgid "Init Script changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):531
+msgid "Now most people would have their systems configured to automatically start the OpenAFS client and server on startup. Those who don't can safely skip this section. If you had your system configured to start them automatically, you will need to re-enable this, because the names of the init scripts have changed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):539
+msgid "Re-enabling OpenAFS startup at boot time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):539
+#, no-wrap
+msgid "\n# <i>rc-update del afs default</i>\n# <i>rc-update add openafs-client default</i>\n# <i>rc-update add openafs-server default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):545
+msgid "If you had <c>=openafs-1.2.13</c> or <c>=openafs-1.3.85</c>, you should remove <path>afs-client</path> and <path>afs-server</path> from the default runlevel, instead of <path>afs</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):554
+msgid "Troubleshooting: what if the automatic upgrade fails"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):557
+msgid "Don't panic. You shouldn't have lost any data or configuration files. So let's analyze the situation. Please file a bug at <uri link=\"http://bugs.gentoo.org\">bugs.gentoo.org</uri> in any case, preferably with as much information as possible."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):564
+msgid "If you're having problems starting the client, this should help you diagnosing the problem:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):570
+msgid "Run <c>dmesg</c>. The client normally sends error messages there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):573
+msgid "Check <path>/etc/openafs/cacheinfo</path>. It should be of the form: /afs:{path to disk cache}:{number of blocks for disk cache}. Normally, your disk cache will be located at <path>/var/cache/openafs</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):579
+msgid "Check the output of <c>lsmod</c>. You will want to see a line beginning with the word openafs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):583
+msgid "<c>pgrep afsd</c> will tell you whether afsd is running or not"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):584
+msgid "<c>cat /proc/mounts</c> should reveal whether <path>/afs</path> has been mounted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):590
+msgid "If you're having problems starting the server, then these hints may be useful:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):595
+msgid "<c>pgrep bosserver</c> tells you whether the overseer is running or not. If you have more than one overseer running, then something has gone wrong. In that case, you should try a graceful OpenAFS server shutdown with <c>bos shutdown localhost -localauth -wait</c>, check the result with <c>bos status localhost -localauth</c>, kill all remaining overseer processes and then finally check whether any server processes are still running (<c>ls /usr/libexec/openafs</c> to get a list of them). Afterwards, do <c>/etc/init.d/openafs-server zap</c> to reset the status of the server and <c>/etc/init.d/openafs-server start</c> to try launching it again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):606
+msgid "If you're using OpenAFS' own logging system (which is the default setting), check out <path>/var/lib/openafs/logs/*</path>. If you're using the syslog service, go check out its logs for any useful information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):618
+msgid "Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):620
+msgid "Getting AFS Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):623
+msgid "You can get the original IBM AFS Documentation. It is very well written and you really want read it if it is up to you to administer a AFS Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):628
+msgid "Installing afsdoc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):628
+#, no-wrap
+msgid "\n# <i>emerge app-doc/afsdoc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):632
+msgid "You also have the option of using the documentation delivered with OpenAFS. It is installed when you have the USE flag <c>doc</c> enabled while emerging OpenAFS. It can be found in <path>/usr/share/doc/openafs-*/</path>. At the time of writing, this documentation was a work in progress. It may however document newer features in OpenAFS that aren't described in the original IBM AFS Documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):646
+msgid "Client Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):648
+msgid "Building the Client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):651 ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):783
+msgid "Installing openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):651 ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):783
+#, no-wrap
+msgid "\n# <i>emerge net-fs/openafs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):655
+msgid "After successful compilation you're ready to go."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):662
+msgid "A simple global-browsing client installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):665
+msgid "If you're not part of a specific OpenAFS-cell you want to access, and you just want to try browsing globally available OpenAFS-shares, then you can just install OpenAFS, not touch the configuration at all, and start <path>/etc/init.d/openafs-client</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):675
+msgid "Accessing a specific OpenAFS cell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):678
+msgid "If you need to access a specific cell, say your university's or company's own cell, then some adjustments to your configuration have to be made."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):683
+msgid "Firstly, you need to update <path>/etc/openafs/CellServDB</path> with the database servers for your cell. This information is normally provided by your administrator."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):689
+msgid "Secondly, in order to be able to log onto the OpenAFS cell, you need to specify its name in <path>/etc/openafs/ThisCell</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):694
+msgid "Adjusting CellServDB and ThisCell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):694
+#, no-wrap
+msgid "\nCellServDB:\n&gt;netlabs        #Cell name\n10.0.0.1        #storage\n\nThisCell:\nnetlabs\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(warn):703
+msgid "Only use spaces inside the <path>CellServDB</path> file. The client will most likely fail if you use TABs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):708
+msgid "CellServDB tells your client which server(s) it needs to contact for a specific cell. ThisCell should be quite obvious. Normally you use a name which is unique for your organisation. Your (official) domain might be a good choice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):715
+msgid "For a quick start, you can now start <path>/etc/init.d/openafs-client</path> and use <c>klog</c> to authenticate yourself and start using your access to the cell. For automatic logons to you cell, you want to consult the appropriate section below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):725
+msgid "Adjusting the cache"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):728
+msgid "Unfortunately the AFS Client needs a ext2/3 filesystem for its cache to run correctly. There are some issues when using other filesystems (using e.g. reiserfs is not a good idea)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):734
+msgid "You can house your cache on an existing filesystem (if it's ext2/3), or you may want to have a separate partition for that. The default location of the cache is <path>/var/cache/openafs</path>, but you can change that by editing <path>/etc/openafs/cacheinfo</path>. A standard size for your cache is 200MB, but more won't hurt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):745
+msgid "Starting AFS on startup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):748
+msgid "The following command will create the appropriate links to start your afs client on system startup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(warn):753
+msgid "You should always have a running afs server in your domain when trying to start the afs client. Your system won't boot until it gets some timeout if your AFS server is down (and this is quite a long long time.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):759
+msgid "Adding AFS client to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):759
+#, no-wrap
+msgid "\n# <i>rc-update add openafs-client default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):768
+msgid "Server Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):770
+msgid "Building the Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):773
+msgid "All commands should be written in one line!! In this document they are sometimes wrapped to two lines to make them easier to read."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):778
+msgid "If you haven't already done so, the following command will install all necessary binaries for setting up an AFS Server <e>and</e> Client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):790
+msgid "Starting AFS Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):793
+msgid "You need to run the <c>bosserver</c> command to initialize the Basic OverSeer (BOS) Server, which monitors and controls other AFS server processes on its server machine. Think of it as init for the system. Include the <c>-noauth</c> flag to disable authorization checking, since you haven't added the admin user yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(warn):801
+msgid "Disabling authorization checking gravely compromises cell security. You must complete all subsequent steps in one uninterrupted pass and must not leave the machine unattended until you restart the BOS Server with authorization checking enabled. Well, this is what the AFS documentation says. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):808
+msgid "Initialize the Basic OverSeer Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):808
+#, no-wrap
+msgid "\n# <i>bosserver -noauth &amp;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):812
+msgid "Verify that the BOS Server created <path>/etc/openafs/server/CellServDB</path> and <path>/etc/openafs/server/ThisCell</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):817
+msgid "Check if CellServDB and ThisCell are created"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):817
+#, no-wrap
+msgid "\n# <i>ls -al /etc/openafs/server/</i>\n-rw-r--r--    1 root     root           41 Jun  4 22:21 CellServDB\n-rw-r--r--    1 root     root            7 Jun  4 22:21 ThisCell\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):826
+msgid "Defining Cell Name and Membership for Server Process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):829
+msgid "Now assign your cell's name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(impo):833
+msgid "There are some restrictions on the name format. Two of the most important restrictions are that the name cannot include uppercase letters or more than 64 characters. Remember that your cell name will show up under <path>/afs</path>, so you might want to choose a short one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):840
+msgid "In the following and every instruction in this guide, for the &lt;server name&gt; argument substitute the full-qualified hostname (such as <b>afs.gentoo.org</b>) of the machine you are installing. For the &lt;cell name&gt; argument substitute your cell's complete name (such as <b>gentoo</b>)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):848
+msgid "Run the <c>bos setcellname</c> command to set the cell name:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):852
+msgid "Set the cell name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):852
+#, no-wrap
+msgid "\n# <i>bos setcellname &lt;server name&gt; &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):859
+msgid "Starting the Database Server Process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):862
+msgid "Next use the <c>bos create</c> command to create entries for the four database server processes in the <path>/etc/openafs/BosConfig</path> file. The four processes run on database server machines only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):870
+msgid "kaserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):871
+msgid "The Authentication Server maintains the Authentication Database. This can be replaced by a Kerberos 5 daemon. If anybody wants to try that feel free to update this document :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):878
+msgid "buserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):879
+msgid "The Backup Server maintains the Backup Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):882
+msgid "ptserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):883
+msgid "The Protection Server maintains the Protection Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):886
+msgid "vlserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):887
+msgid "The Volume Location Server maintains the Volume Location Database (VLDB). Very important :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):894
+msgid "Create entries for the database processes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):894
+#, no-wrap
+msgid "\n# <i>bos create &lt;server name&gt; kaserver \\\nsimple /usr/libexec/openafs/kaserver \\\n-cell &lt;cell name&gt; -noauth</i>\n# <i>bos create &lt;server name&gt; buserver \\\nsimple /usr/libexec/openafs/buserver \\\n-cell &lt;cell name&gt; -noauth</i>\n# <i>bos create &lt;server name&gt; ptserver \\\nsimple /usr/libexec/openafs/ptserver \\\n-cell &lt;cell name&gt; -noauth</i>\n# <i>bos create &lt;server name&gt; \\\nvlserver simple /usr/libexec/openafs/vlserver \\\n-cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):909
+msgid "You can verify that all servers are running with the <c>bos status</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):913
+msgid "Check if all the servers are running"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):913
+#, no-wrap
+msgid "\n# <i>bos status &lt;server name&gt; -noauth</i>\nInstance kaserver, currently running normally.\nInstance buserver, currently running normally.\nInstance ptserver, currently running normally.\nInstance vlserver, currently running normally.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):924
+msgid "Initializing Cell Security"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):927
+msgid "Now we'll initialize the cell's security mechanisms. We'll begin by creating the following two initial entries in the Authentication Database: The main administrative account, called <b>admin</b> by convention and an entry for the AFS server processes, called <c>afs</c>. No user logs in under the identity <b>afs</b>, but the Authentication Server's Ticket Granting Service (TGS) module uses the account to encrypt the server tickets that it grants to AFS clients. This sounds pretty much like Kerberos :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):937
+msgid "Enter <c>kas</c> interactive mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):941
+msgid "Entering the interactive mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):941
+#, no-wrap
+msgid "\n# <i>kas -cell &lt;cell name&gt; -noauth</i>\nka&gt; <i>create afs</i>\ninitial_password:\nVerifying, please re-enter initial_password:\nka&gt; <i>create admin</i>\ninitial_password:\nVerifying, please re-enter initial_password:\nka&gt; <i>examine afs</i>\n\nUser data for afs\nkey (0) cksum is 2651715259, last cpw: Mon Jun  4 20:49:30 2001\npassword will never expire.\nAn unlimited number of unsuccessful authentications is permitted.\nentry never expires.  Max ticket lifetime 100.00 hours.\nlast mod on Mon Jun  4 20:49:30 2001 by &lt;none&gt;\npermit password reuse\nka&gt; <i>setfields admin -flags admin</i>\nka&gt; <i>examine admin</i>\n\nUser data for admin (ADMIN)\nkey (0) cksum is 2651715259, last cpw: Mon Jun  4 20:49:59 2001\npassword will never expire.\nAn unlimited number of unsuccessful authentications is permitted.\nentry never expires.  Max ticket lifetime 25.00 hours.\nlast mod on Mon Jun  4 20:51:10 2001 by &lt;none&gt;\npermit password reuse\nka&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):971
+msgid "Run the <c>bos adduser</c> command, to add the <b>admin</b> user to the <path>/etc/openafs/server/UserList</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):976
+msgid "Add the admin user to the UserList"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):976
+#, no-wrap
+msgid "\n# <i>bos adduser &lt;server name&gt; admin -cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):980
+msgid "Issue the <c>bos addkey</c> command to define the AFS Server encryption key in <path>/etc/openafs/server/KeyFile</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):985
+msgid "If asked for the input key, give the password you entered when creating the AFS entry with <c>kas</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):990
+msgid "Entering the password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):990
+#, no-wrap
+msgid "\n# <i>bos addkey  &lt;server name&gt; -kvno 0 -cell &lt;cell name&gt; -noauth</i>\ninput key:\nRetype input key:\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):996
+msgid "Issue the <c>pts createuser</c> command to create a Protection Database entry for the admin user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):1001
+msgid "By default, the Protection Server assigns AFS UID 1 to the <b>admin</b> user, because it is the first user entry you are creating. If the local password file (<path>/etc/passwd</path> or equivalent) already has an entry for <b>admin</b> that assigns a different UID use the <c>-id</c> argument to create matching UIDs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1009
+msgid "Create a Protection Database entry for the database user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1009
+#, no-wrap
+msgid "\n# <i>pts createuser -name admin -cell &lt;cell name&gt; [-id &lt;AFS UID&gt;] -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1013
+msgid "Issue the <c>pts adduser</c> command to make the <b>admin</b> user a member of the system:administrators group, and the <c>pts membership</c> command to verify the new membership"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1019
+msgid "Make admin a member of the administrators group and verify"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1019
+#, no-wrap
+msgid "\n# <i>pts adduser admin system:administrators -cell &lt;cell name&gt; -noauth</i>\n# <i>pts membership admin -cell &lt;cell name&gt; -noauth</i>\nGroups admin (id: 1) is a member of:\nsystem:administrators\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1029
+msgid "Properly (re-)starting the AFS server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1032
+msgid "At this moment, proper authentication is possible, and the OpenAFS server can be started in a normal fashion. Note that authentication also requires a running OpenAFS client (setting it up is described in the previous chapter)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1042
+msgid "Shutdown bosserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1042
+#, no-wrap
+msgid "\n# <i>bos shutdown &lt;server name&gt; -wait -noauth</i>\n# <i>killall bosserver</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1047
+msgid "Normal OpenAFS server (and client) startup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1047
+#, no-wrap
+msgid "\n# <i>/etc/init.d/openafs-server start</i>\n# <i>/etc/init.d/openafs-client start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1052
+msgid "Adding AFS server to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1052
+#, no-wrap
+msgid "\n# <i>rc-update add openafs-server default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1056
+msgid "Getting a token as the admin user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1056
+#, no-wrap
+msgid "\n# <i>klog admin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1074
+msgid "Starting the File Server, Volume Server and Salvager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1077
+msgid "Start the <c>fs</c> process, which consists of the File Server, Volume Server and Salvager (fileserver, volserver and salvager processes)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1082
+msgid "Start the fs process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1082
+#, no-wrap
+msgid "\n# <i>bos create &lt;server name&gt; fs \\\nfs /usr/libexec/openafs/fileserver /usr/libexec/openafs/volserver /usr/libexec/openafs/salvager \\\n-cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1088
+msgid "Verify that all processes are running:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1092
+msgid "Check if all processes are running"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1092
+#, no-wrap
+msgid "\n# <i>bos status &lt;server name&gt; -long -noauth</i>\nInstance kaserver, (type is simple) currently running normally.\nProcess last started at Mon Jun  4 21:07:17 2001 (2 proc starts)\nLast exit at Mon Jun  4 21:07:17 2001\nCommand 1 is '/usr/libexec/openafs/kaserver'\n\nInstance buserver, (type is simple) currently running normally.\nProcess last started at Mon Jun  4 21:07:17 2001 (2 proc starts)\nLast exit at Mon Jun  4 21:07:17 2001\nCommand 1 is '/usr/libexec/openafs/buserver'\n\nInstance ptserver, (type is simple) currently running normally.\nProcess last started at Mon Jun  4 21:07:17 2001 (2 proc starts)\nLast exit at Mon Jun  4 21:07:17 2001\nCommand 1 is '/usr/libexec/openafs/ptserver'\n\nInstance vlserver, (type is simple) currently running normally.\nProcess last started at Mon Jun  4 21:07:17 2001 (2 proc starts)\nLast exit at Mon Jun  4 21:07:17 2001\nCommand 1 is '/usr/libexec/openafs/vlserver'\n\nInstance fs, (type is fs) currently running normally.\nAuxiliary status is: file server running.\nProcess last started at Mon Jun  4 21:09:30 2001 (2 proc starts)\nCommand 1 is '/usr/libexec/openafs/fileserver'\nCommand 2 is '/usr/libexec/openafs/volserver'\nCommand 3 is '/usr/libexec/openafs/salvager'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1122
+msgid "Your next action depends on whether you have ever run AFS file server machines in the cell."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1127
+msgid "If you are installing the first AFS Server ever in the cell, create the first AFS volume, <b>root.afs</b>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):1132
+msgid "For the partition name argument, substitute the name of one of the machine's AFS Server partitions. Any filesystem mounted under a directory called <path>/vicepx</path>, where x is in the range of a-z, will be considered and used as an AFS Server partition. Any unix filesystem will do (as opposed to the client's cache, which can only be ext2/3). Tip: the server checks for each <path>/vicepx</path> mount point whether a filesystem is mounted there. If not, the server will not attempt to use it. This behaviour can be overridden by putting a file named <path>AlwaysAttach</path> in this directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1143
+msgid "Create the root.afs volume"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1143
+#, no-wrap
+msgid "\n# <i>vos create &lt;server name&gt; &lt;partition name&gt; root.afs -cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1147
+msgid "If there are existing AFS file server machines and volumes in the cell issue the <c>vos sncvldb</c> and <c>vos syncserv</c> commands to synchronize the VLDB (Volume Location Database) with the actual state of volumes on the local machine. This will copy all necessary data to your new server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1154
+msgid "If the command fails with the message \"partition /vicepa does not exist on the server\", ensure that the partition is mounted before running OpenAFS servers, or mount the directory and restart the processes using <c>bos restart &lt;server name&gt; -all -cell &lt;cell name&gt; -noauth</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1162
+msgid "Synchronise the VLDB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1162
+#, no-wrap
+msgid "\n# <i>vos syncvldb &lt;server name&gt; -cell &lt;cell name&gt; -verbose -noauth</i>\n# <i>vos syncserv &lt;server name&gt; -cell &lt;cell name&gt; -verbose -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1170
+msgid "Starting the Server Portion of the Update Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1173
+msgid "Start the update server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1173
+#, no-wrap
+msgid "\n# <i>bos create &lt;server name&gt; \\\nupserver simple \"/usr/libexec/openafs/upserver \\\n-crypt /etc/openafs/server -clear /usr/libexec/openafs\" \\\n-cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1183
+msgid "Configuring the Top Level of the AFS filespace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1186
+msgid "First you need to set some ACLs, so that any user can lookup <path>/afs</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):1191
+msgid "The default OpenAFS client configuration has <b>dynroot</b> enabled. This option turns <path>/afs</path> into a virtual directory composed of the contents of your <path>/etc/openafs/CellServDB</path> file. As such, the following command will not work, because it requires a real AFS directory. You can temporarily switch dynroot off by setting <b>ENABLE_DYNROOT</b> to <b>no</b> in <path>/etc/conf.d/openafs-client</path>. Don't forget to issue a client restart after changing parameters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1201
+msgid "Set access control lists"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1201
+#, no-wrap
+msgid "\n# <i>fs setacl /afs system:anyuser rl</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1205
+msgid "Then you need to create the root volume, mount it readonly on <path>/afs/&lt;cell name&gt;</path> and read/write on <path>/afs/.&lt;cell name&gt;</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1211
+msgid "Prepare the root volume"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1211
+#, no-wrap
+msgid "\n# <i>vos create &lt;server name&gt; &lt;partition name&gt; root.cell</i>\n# <i>fs mkmount /afs/&lt;cell name&gt; root.cell</i>\n# <i>fs setacl /afs/&lt;cell name&gt; system:anyuser rl</i>\n# <i>fs mkmount /afs/.&lt;cell name&gt; root.cell -rw</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1218
+msgid "Adding volumes underneath"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1218
+#, no-wrap
+msgid "\n# <i>vos create &lt;server name&gt; &lt;partition name&gt; &lt;myvolume&gt;</i>\n# <i>fs mkmount /afs/&lt;cell name&gt;/&lt;mymountpoint&gt; &lt;myvolume&gt;</i>\n# <i>fs mkmount /afs/&lt;cell name&gt;/.&lt;mymountpoint&gt; &lt;myvolume&gt; -rw</i>\n# <i>fs setquota /afs/&lt;cell name&gt;/.&lt;mymountpoint&gt; -max &lt;quotum&gt;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1225
+msgid "Finally you're done!!! You should now have a working AFS file server on your local network. Time to get a big cup of coffee and print out the AFS documentation!!!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):1231
+msgid "It is very important for the AFS server to function properly, that all system clocks are synchronized. This is best accomplished by installing a ntp server on one machine (e.g. the AFS server) and synchronize all client clocks with the ntp client. This can also be done by the AFS client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1243
+msgid "Basic Administration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1245
+msgid "Disclaimer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1248
+msgid "OpenAFS is an extensive technology. Please read the AFS documentation for more information. We only list a few administrative tasks in this chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1256
+msgid "Configuring PAM to Acquire an AFS Token on Login"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1259
+msgid "To use AFS you need to authenticate against the KA Server if using an implementation AFS Kerberos 4, or against a Kerberos 5 KDC if using MIT, Heimdal, or ShiShi Kerberos 5. However in order to login to a machine you will also need a user account, this can be local in <path>/etc/passwd</path>, NIS, LDAP (OpenLDAP), or a Hesiod database. PAM allows Gentoo to tie the authentication against AFS and login to the user account."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1269
+msgid "You will need to update <path>/etc/pam.d/system-auth</path> which is used by the other configurations. \"use_first_pass\" indicates it will be checked first against the user login, and \"ignore_root\" stops the local superuser being checked so as to order to allow login if AFS or the network fails."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1277
+msgid "/etc/pam.d/system-auth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1277
+#, no-wrap
+msgid "\nauth       required     pam_env.so\nauth       sufficient   pam_unix.so likeauth nullok\nauth       sufficient   pam_afs.so.1 use_first_pass ignore_root\nauth       required     pam_deny.so\n\naccount    required     pam_unix.so\n\npassword   required     pam_cracklib.so retry=3\npassword   sufficient   pam_unix.so nullok md5 shadow use_authtok\npassword   required     pam_deny.so\n\nsession    required     pam_limits.so\nsession    required     pam_unix.so\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1293
+msgid "In order for <c>sudo</c> to keep the real user's token and to prevent local users gaining AFS access change <path>/etc/pam.d/su</path> as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1298
+msgid "/etc/pam.d/su"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1298
+#, no-wrap
+msgid "\n<comment># Here, users with uid &gt; 100 are considered to belong to AFS and users with\n# uid &lt;= 100 are ignored by pam_afs.</comment>\nauth       sufficient   pam_afs.so.1 ignore_uid 100\n\nauth       sufficient   pam_rootok.so\n\n<comment># If you want to restrict users begin allowed to su even more,\n# create /etc/security/suauth.allow (or to that matter) that is only\n# writable by root, and add users that are allowed to su to that\n# file, one per line.\n#auth       required     pam_listfile.so item=ruser \\\n#       sense=allow onerr=fail file=/etc/security/suauth.allow\n\n# Uncomment this to allow users in the wheel group to su without\n# entering a passwd.\n#auth       sufficient   pam_wheel.so use_uid trust\n\n# Alternatively to above, you can implement a list of users that do\n# not need to supply a passwd with a list.\n#auth       sufficient   pam_listfile.so item=ruser \\\n#       sense=allow onerr=fail file=/etc/security/suauth.nopass\n\n# Comment this to allow any user, even those not in the 'wheel'\n# group to su</comment>\nauth       required     pam_wheel.so use_uid\n\nauth       required     pam_stack.so service=system-auth\n\naccount    required     pam_stack.so service=system-auth\n\npassword   required     pam_stack.so service=system-auth\n\nsession    required     pam_stack.so service=system-auth\nsession    optional     pam_xauth.so\n\n<comment># Here we prevent the real user id's token from being dropped</comment>\nsession    optional     pam_afs.so.1 no_unlog\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/openbox.xml.pot b/doc/gettext/openbox.xml.pot
new file mode 100644
index 0000000..a9d5a87
--- /dev/null
+++ b/doc/gettext/openbox.xml.pot
@@ -0,0 +1,656 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):6
+msgid "The Openbox Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//openbox.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(mail:link):9
+msgid "nathanzachary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(abstract):15
+msgid "This guide shows you how to install the Openbox window manager, and references many potential programs to be used in conjunction with an Openbox session."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(version):24
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(date):25
+msgid "2010-09-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):31
+msgid "What is Openbox?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):34
+msgid "So, you've installed <uri link=\"/doc/en/xorg-config.xml\">The X Server</uri> and realised that TWM just isn't going to cut it for your needs. You may have also had some experience with big desktop environments like <uri link=\"/proj/en/desktop/kde/kde4-guide.xml\">KDE</uri>, <uri link=\"/doc/en/gnome-config.xml\">GNOME</uri>, and <uri link=\"/doc/en/xfce-config.xml\">Xfce</uri>. One component of those larger desktop suites is called the window manager (or WM for short). A window manager is responsible for the appearance and placement of the containers (or \"windows\") inside which programs run. Openbox is a minimalistic, no-frills-attached window manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):50
+msgid "Why should I use it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):53
+msgid "Openbox, unlike the larger desktop environments, depends on very few libraries. For that reason, it can provide a lightweight graphic environment that runs very quickly, even on older hardware. Whether your hardware is old or new, Openbox also provides a highly customisable and unobtrusive working environment. That means that if you don't want or need a panel, taskbar, clock, or any other program, those choices are yours to make!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):67
+msgid "Installation and configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):69
+msgid "Initial installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):72
+msgid "After you have emerged and configured <c>xorg-server</c>, installing Openbox can be done in one simple command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):77
+msgid "Installing Openbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):77
+#, no-wrap
+msgid "\n# <i>emerge -av openbox</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):81
+msgid "Just like with other window managers and desktop environments, you will need to tell the X Server to load Openbox automatically, by adding it to your <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):87
+msgid "Adding Openbox to your .xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):87
+#, no-wrap
+msgid "\n$ <i>echo \"exec openbox-session\" &gt;&gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):91
+msgid "This will automatically start your Openbox session when you type <c>startx</c> at the terminal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(impo):96
+msgid "As each user has his or her own <path>.xinitrc</path>, you need to make sure to issue that command as <e>your user</e>, not as root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):101
+msgid "If you experience problems with automounting, or if you use dbus and ConsoleKit, you may want to put <c>exec ck-launch-session dbus-launch openbox-session</c> in your <path>.xinitrc</path> instead of the default mentioned above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):107
+msgid "You can also replace the KDE, GNOME, or Xfce default window manager with Openbox by following the <uri link=\"#inside-desktop-env\">Openbox inside desktop environments</uri> directions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):113
+msgid "Now that you have emerged Openbox and added it to your <path>.xinitrc</path>, go ahead and issue the <c>startx</c> command to see Openbox in action. As you can see, the desktop is simply a cluttered mess! In following with the Openbox philosophy, what you will see is a barebones environment from which you can build your desktop completely to your liking."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):121
+msgid "Since you're looking at nothing more than a black screen, you may be wondering where the menu is. If you click your right mouse button, you will notice that a menu pops up in the location of your cursor. This menu is nothing more than an example to illustrate the style of an Openbox menu. Since it <e>is</e> just an example, none of the items in the menu will work unless you have actually emerged those programs. In the next section, you will see how to create your own menu that contains links to <e>your</e> programs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(impo):131
+msgid "If you click to view the menu and notice that there is nothing legible, you need to install some fonts. Two common choices are <c>media-fonts/corefonts</c> and <c>media-fonts/ttf-bitstream-vera</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):140
+msgid "Menu configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):143
+msgid "Since the default Openbox menu is essentially useless to you for the reasons mentioned above, it's time that we create one that will work. Everything in the Openbox menu is written in the appropriately named <path>menu.xml</path> file, which can be in the user-specific location of <path>~/.config/openbox/menu.xml</path>, or in the system-wide location of <path>/etc/xdg/openbox/menu.xml</path>. By default, the only <path>menu.xml</path> file that is created is the system-wide one which applies to all users on the system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):154
+msgid "An easy way to get a basic menu file which you can modify is to use MenuMaker, which will generate a <path>menu.xml</path> file based on the programs which you currently have installed on your system. To do so, you must firstly emerge it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):161
+msgid "Installing MenuMaker"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):161
+#, no-wrap
+msgid "\n# <i>emerge menumaker</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):165
+msgid "Once it is installed, make sure to logout of root, and back into your user account. You then instruct MenuMaker to create a menu specifically using the Openbox XML syntax:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):171
+msgid "Using MenuMaker to generate a basic Openbox menu.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):171
+#, no-wrap
+msgid "\n$ <i>mmaker -v OpenBox3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):175
+msgid "The generated menu will be located at <path>~/.config/openbox/menu.xml</path>. You can then choose to leave it as your user-specific <path>menu.xml</path>, or to additionally copy it to the system-wide menu configuration as well:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):182
+msgid "Overwriting the default system-wide menu.xml files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):182
+#, no-wrap
+msgid "\n# <i>cp .config/openbox/menu.xml /etc/xdg/openbox/menu.xml</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(impo):186
+msgid "It is a good idea to use MenuMaker to generate a default menu, as it will have the Openbox root-menu items. These items include a virtual desktop switcher, and the commands to restart and exit your Openbox session."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):192
+msgid "When you open up the <path>menu.xml</path> file in your favourite editor (nano, for example), you will notice that the XML tags used are very human-readable and easily understandable. You may choose to modify the default file to fit your needs, or you may want to write it from scratch (don't worry, it's really not that difficult). The basic syntax for the menu XML is as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):200 ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):219 ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):284
+msgid "Editing the menu.xml file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):200
+#, no-wrap
+msgid "\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;openbox_menu&gt;\n&lt;separator label=\"NAME_OF_SEPARATOR\" /&gt;\n&lt;menu id=\"IDENTIFIER\" label=\"NAME_OF_MENU\"&gt;\n  &lt;item label=\"NAME_OF_PROGRAM\"&gt;\n    &lt;action name=\"execute\"&gt;&lt;execute&gt;/LOCATION/OF/BINARY&lt;/execute&gt;&lt;/action&gt;\n  &lt;/item&gt;\n&lt;/menu&gt;\n&lt;/openbox_menu&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):212
+msgid "The above example will work for any applications that launch with standard options in their own windows, but what if you need to append options to the program at launch time? That is no problem either, but the syntax of the menu item is slightly different."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):219
+#, no-wrap
+msgid "\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;openbox_menu&gt;\n&lt;separator label=\"NAME_OF_SEPARATOR\" /&gt;\n&lt;menu id=\"IDENTIFIER\" label=\"NAME_OF_MENU\"&gt;\n  &lt;item label=\"NAME_OF_PROGRAM\"&gt;\n    &lt;action name=\"execute\"&gt;&lt;command&gt;/LOCATION/OF/BINARY --OPTION1 --OPTION2&lt;/command&gt;&lt;/action&gt;\n  &lt;/item&gt;\n&lt;/menu&gt;\n&lt;/openbox_menu&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):231
+msgid "Simply replace anything in CAPS in the above two examples with your information. Alternatively, you can <c>emerge obmenu</c>, which is a graphical interface allowing you to create your menus without having to manually edit the <path>menu.xml</path> file. It is a very small application and offers a nice amount of customisation without typing any XML."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):242
+msgid "Openbox theme and behaviour configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):245
+msgid "Aside from being minimalistic and lightweight, Openbox is also surprisingly customisable and flexible. As a user, you can easily change various settings related to theme, appearance, window placement, docking, and more. There are two options for configuring these settings within Openbox. You may either manually edit <path>~/.config/openbox/rc.xml</path>, or you may want a GUI to help you quickly change settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):254
+msgid "If you want to manually edit <path>rc.xml</path>, you simply open up your favourite text editor and start making changes. You might want to make a backup of the original file just in case, and store it in a location like <path>~/.config/openbox/rc.xml.default</path>. There are plenty of comments within the document itself that should help you with editing. Alternatively, you may want to look at the <uri link=\"http://icculus.org/openbox/index.php/Help:Contents#Configuration\">Openbox configuration guides</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):265
+msgid "If manually editing <path>rc.xml</path> doesn't sound like your cup of tea, you may want to use the GTK+ application to manage your themes and behaviours in Openbox. The application that you will use is called ObConf, and can be installed on your system just as easily as was Openbox itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):272
+msgid "Installing ObConf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):272
+#, no-wrap
+msgid "\n# <i>emerge obconf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):276
+msgid "You can then open the configurator by typing <c>obconf</c> in your terminal. Next, you can go and add an entry for ObConf into your <path>menu.xml</path> so it will show up in your Openbox menu. If the \"editing the menu.xml file\" code listing above seemed too vague to be helpful, we'll use ObConf as an example of a menu entry:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):284
+#, no-wrap
+msgid "\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;openbox_menu&gt;\n&lt;menu id=\"1\" label=\"Configuration\"&gt;\n  &lt;item label=\"OpenBox Config\"&gt;\n    &lt;action name=\"execute\"&gt;&lt;execute&gt;/usr/bin/obconf&lt;/execute&gt;&lt;/action&gt;\n  &lt;/item&gt;\n&lt;/menu&gt;\n&lt;/openbox_menu&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):295
+msgid "While ObConf is a great GUI tool for editing many behaviour-related settings for Openbox, it doesn't allow one to manipulate nearly as many settings as are presented in the <path>rc.xml</path> file itself. If you are having trouble finding a particular setting which you would like to change, please consult the <uri link=\"http://openbox.org/wiki/Configuration\">Openbox Wiki</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):304
+msgid "In recent versions of Openbox (namely &gt;3.4.7.2), one may experience a delay in the submenu opening. This setting was introduced into the rc.xml file, and is listed as &lt;submenuShowDelay&gt;100&lt;/submenuShowDelay&gt;. Simply choose a lower number that suits your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):314
+msgid "Autostart configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):317
+msgid "As mentioned above, you don't see a whole lot when you issue the <c>startx</c> command for the first time after installing Openbox. In addition to customising your menus and changing the behaviour of the window manager, you will probably want to have some programs automatically start with your Openbox session. There is an easily-editable <path>autostart.sh</path> script that allows you to do just that. Just like with the <path>menu.xml</path> file, there are two different locations of the <path>autostart.sh</path> script--the system-wide (<path>/etc/xdg/openbox/autostart.sh</path>), and the user-defined (<path>~/.config/openbox/autostart.sh</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):329
+msgid "In the default <path>autostart.sh</path>, you will notice a bunch of lines calling for programs like the gnome-settings-daemon, XDG, and others. These lines will generate errors upon logout if you don't have the programs installed and configured. The easiest thing to do when getting started with Openbox is to just comment out these lines by using the # symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):336
+msgid "Commenting out lines in autostart.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):336
+#, no-wrap
+msgid "\n# Run XDG autostart things. By default don't run anything desktop-specific\n# DESKTOP_ENV=\"\"\n# if which /usr/lib/openbox/xdg-autostart &gt;/dev/null; then\n#  /usr/lib/openbox/xdg-autostart $DESKTOP_ENV\n# fi\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):344
+msgid "In the above example, the comment symbol (#) was added before each line. The commenting method is preferred to just deleting the lines because you may want to add support for some of those startup items at a later time. Thus, leaving the default lines in place could ease that process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):351
+msgid "Adding your own programs to the <path>autostart.sh</path> script is as easy as writing in the program name for many applications. For instance, if you have <uri link=\"http://packages.gentoo.org/package/app-admin/conky\">Conky</uri> (a lightweight system monitor) installed, and want it to start automatically with your Openbox session, you simply add the following line to your <path>autostart.sh</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):360
+msgid "Adding Conky to your autostart.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):360
+#, no-wrap
+msgid "\nconky &amp;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):364
+msgid "The ampersand (&amp;) after the command allows that application to load up in the background. You will most likely want to load all the applications in your <path>autostart.sh</path> script in the background because doing so will let Openbox and other programs load without the previous one finishing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):374
+msgid "Setting the background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):377
+msgid "Some things that you might take for granted in bigger desktop environments are not included by default in Openbox. One such thing is setting your desktop background. In order to place an image as your wallpaper, you will need to emerge a program like <uri link=\"http://packages.gentoo.org/package/media-gfx/feh\">feh</uri> or <uri link=\"http://packages.gentoo.org/package/x11-misc/nitrogen\">nitrogen</uri>. <c>feh</c> is a simple image viewer that can also set the background, <e>and</e> it can easily be put into the autostart script. Once you have emerged <c>feh</c>, you can issue the following command to set the background:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):389 ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):405
+msgid "Using feh to set the background image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):389
+#, no-wrap
+msgid "\n<comment>(feh has many other options instead of --bg-scale, \nwhich will scale the image to the screen dimensions.\nConsult the feh documentation.)</comment>\n$ <i>feh --bg-scale /path/to/image.jpg</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):396
+msgid "Once you have set the background manually, a file called <path>.fehbg</path> will be created in your home directory. This file simply contains the above command that you just entered in the terminal, and is automatically updated when you issue a different background command. Now, to set your background automatically upon login, you can add the following line to your <path>autostart.sh</path> script:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):405
+#, no-wrap
+msgid "\nsource $HOME/.fehbg &amp;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):409
+msgid "If you don't particularly care for the idea of having to issue a command in the terminal in order to set your background, you can alternatively use <c>nitrogen</c>. It will allow you to set a folder for your background images, view thumbnails of those images, and fit, stretch, or tile them to your desktop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):417
+msgid "Installing <c>nitrogen</c> and getting it into your Openbox menu requires a few more steps than are readily apparent. First, you need to <c>emerge nitrogen</c>. Second, you need to run <c>nitrogen</c> with your backgrounds folder appended:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):423
+msgid "Starting nitrogen with your image folder"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):423
+#, no-wrap
+msgid "\n$ <i>nitrogen /path/to/your/backgrounds/folder</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):427
+msgid "Third, you can set your background image, but it will not be there after you logout. Just as with <c>feh</c>, you need to restore your background by editing your <path>autostart.sh</path> script to have the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):433
+msgid "Restoring your background with nitrogen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):433
+#, no-wrap
+msgid "\nnitrogen --restore &amp;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):437
+msgid "This will cause nitrogen to load automatically when you start your Openbox session, and that can lead to a slightly slower load time than using feh."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):447
+msgid "Programs to use with Openbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):451
+msgid "The following is a list of some programs which you might want to use within your Openbox environment. While the list contains numerous terminal emulators, file managers, panels, and more, it should by no means be considered exhaustive. If none of the programs listed fit your needs, please check the appropriate categories in Portage for more options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):462
+msgid "Terminal emulators"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):466
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxterminal\">LXterminal</uri> is the default terminal emulator for LXDE. It is very lightweight, and based on VTE. While EvilVTE offers many more customisation options (including transparency), LXterminal has a graphical interface for some of the more common options (font, colors, et cetera)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):474
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-terms/evilvte\">EvilVTE</uri> is an extremely lightweight terminal emulator based on (you guessed it) VTE. It supports tabs, multiple encodings, as well as an easy and extensible configuration file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):481
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-terms/mrxvt\">Mrxvt</uri> is a multi-tabbed rxvt clone with XFT, transparent background and CJK support. It also features session support for each tab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):486
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-terms/aterm\">Aterm</uri> supports transparency and backwards compatibility with rxvt. It was originally designed for the AfterStep window manager, but easily integrates with other environments."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):492
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-terms/eterm\">Eterm</uri> is a terminal based on vt102 and designed to be a more feature-rich replacement for xterm."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):497
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-terms/rxvt-unicode\">Rxvt-unicode</uri> is a clone of rxvt that supports Unicode, daemons, embedded perl, and multiple fonts simultaneously."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):503
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-terms/terminal\">Terminal</uri> is the VTE-based default for the Xfce desktop environment, so it does require some Xfce libraries to run. However, it is still fairly speedy, and supports transparency and is easily customised."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):515
+msgid "File managers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):519
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/pcmanfm\">PCManFM</uri> is the lightweight filemanager from LXDE. It supports tabbed browsing, drag and drop, thumnails for images, bookmarks, volume management, searching, and more. It also provides supports for managing the desktop background and drawing desktop icons (both optionally)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):527
+msgid "<uri link=\"http://packages.gentoo.org/package/xfce-base/thunar\">Thunar</uri> is the standard file manager from Xfce. It features a bulk renamer, user-customisable actions, and an extension framework, along with many optional plugins, such as media tag editing. It depends on several Xfce libraries, but it's still slimmed down compared to other file managers like Nautilus (from GNOME), and Konqueror (from KDE)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):535
+msgid "<uri link=\"http://packages.gentoo.org/package/gnome-base/nautilus\">Nautilus</uri> is the powerful file manager from the GNOME desktop environment. It features volume management, thumbnails for images, searching, and some system configuration. As it depends on many of the GNOME libraries for proper function, it can seem a bit heavy compared to some of the other file managers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):544
+msgid "<uri link=\"http://packages.gentoo.org/package/app-misc/gentoo\">Gentoo</uri> (no relation to this glorious Linux distribution) is a two-pane style file manager. It is incredibly lightweight, but lacks a some features now prominent in modern file managers. It should definitely be considered for older hardware, or if you are wanting a barebones setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):551
+msgid "<uri link=\"http://packages.gentoo.org/package/app-misc/emelfm2\">emelFM2</uri> is another file manager in the vein of Midnight Commander. It features a two-pane window. As with the Gentoo file manager (listed above), it is barebones and does not include many features prevalent in newer file managers. However, it also offers a few features not found in other file managers, such as a built-in commandline in a separate pane."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):565
+msgid "Desktop management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):569
+msgid "Though <uri link=\"http://packages.gentoo.org/package/x11-misc/pcmanfm\">PCManFM</uri> is mainly a file manager, it also gives you the option to manage the desktop background (instead of using <c>feh</c> or <c>nitrogen</c>) and draw desktop icons."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):576
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/idesk\">iDesk</uri> is a simple program used to draw desktop icons. It supports shadowed and anti-aliased fonts, PNG images, \"snap-to-grid\" placement, and changing the desktop background."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):587
+msgid "Panels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):591
+msgid "<uri link=\"http://code.google.com/p/tint2/\">Tint2</uri> is a simple, lightweight panel and taskbar. It supports color, transparency, a clock, drag and drop between virtual desktops, a system tray, and comes with a battery monitor. You can even add a button to display the applications menu from your window manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):598
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/pypanel\">PyPanel</uri> is an easily customised panel written in Python and C. It features transparency, shading, tinting, location and layout configuration, font type, autohiding, application launcher, clock, and more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):605
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxpanel\">LXPanel</uri> is the default panel and taskbar from LXDE. It features a launcher, menu, clock, and a GUI-based configurator. It is feature-rich while depending on very few packages, making it a good choice for a lean system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):612
+msgid "<uri link=\"http://packages.gentoo.org/package/xfce-base/xfce4-panel\">Xfce4-panel</uri> is the default panel from the Xfce desktop environment. It supports application launchers, detachable menus, a pager, tasklist, clock, applets, and more. It does, however, require a few of the Xfce libraries which are not dependencies of some other panels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):620
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/fbpanel\">FBpanel</uri> is a simple, extremely lightweight panel that supports window lists, launchers, a clock, and a few other goodies. It's not the most featureful panel, and it can be cumbersome to configure, but it needs only GTK+ to run."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):632
+msgid "Pagers and systrays"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):636
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/netwmpager\">NetWMpager</uri> is an EWMH-compliant pager that integrates nicely into any of the *box environments. It is not as obtrusive, and is much more readily customisable than many of the other available pagers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):643
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/bbpager\">BBpager</uri> is a desktop pager that was originally written for BlackBox, but works nicely with Openbox as well. It does have some BlackBox dependencies though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):649
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-plugins/docker\">Docker</uri> is the system tray that is made especially for Openbox. It has no extra dependencies, and gives you the ability to view and use tray icons for supported GTK and QT-based applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):656
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/trayer\">Trayer</uri> is a system tray that was modified from the FBpanel code, and is often used with FVWM. One of its perks is that it supports transparency."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):666
+msgid "Session management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):670
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxsession\"> LXsession</uri> is the stripped down session manager from LXDE. It is designed to remember applications that the user was running at the last logout, and to automatically restart those programs. It also supports the HAL daemon."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):677
+msgid "<uri link=\"http://packages.gentoo.org/package/xfce-base/xfce4-session\"> Xfce4-session</uri> is the session manager from, you guessed it, Xfce. It is capable of saving several sessions, and provides methods for logging out, rebooting, and suspending your computer. It does, however, have many Xfce dependencies."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):689
+msgid "Configuration tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):693
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/obconf\">ObConf</uri> is a GUI application allowing you to customise the Openbox window manager without manually editing <path>~/.config/openbox/rc.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):698
+msgid "<uri link=\"http://packages.gentoo.org/package/lxde-base/lxappearance\">LXappearance</uri> is a GTK theme and icon configurator used with LXDE. It provides a nice graphical interface for setting the theme and icons, while depending on very few extra libraries."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):705
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-themes/gtk-chtheme\">GTK-ChTheme</uri> is a simple application allowing for easier switching of GTK themes and your font. Currently, it does not allow for the switching of icon themes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):711
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-themes/gtk-theme-switch\">GTK-theme-switch</uri> is another simple application that lets you change your GTK theme."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):721
+msgid "Miscellaneous"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):725
+msgid "<uri link=\"http://packages.gentoo.org/package/app-admin/conky\">Conky</uri> is a lightweight system monitor that can display over 250 objects, including date and time, CPU usage, memory usage, IMAP/POP3 email, top processes, hardware sensor data, and even info from your music player. It is highly customisable both in appearance and data display. We also have a <uri link=\"/doc/en/conky-howto.xml\">Conky configuration guide</uri> available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):733
+msgid "<uri link=\"http://packages.gentoo.org/package/app-editors/leafpad\">Leafpad</uri> is a simple text editor. It is very lightweight, but includes features like codeset options, and the ability to undo/redo without limits."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):739
+msgid "<uri link=\"http://packages.gentoo.org/package/media-gfx/feh\">feh</uri> is a simple image viewer that runs from the terminal, but it also has many other features. It can display a slideshow of images, create an index print, dynamically zoom, and set the desktop background (detailed instructions above)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):746
+msgid "<uri link=\"http://packages.gentoo.org/package/media-gfx/gpicview\">GPicView</uri> is a GUI-based image viewer. Though it has more dependencies than <c>feh</c>, it is incredibly quick to load and run."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):752
+msgid "<uri link=\"http://packages.gentoo.org/package/x11-misc/slim\">SLiM</uri> is the Simple Login Manager, which allows you to login to your Openbox session via a graphical interface instead of the terminal. It has very few dependencies, and supports many themes, but should not be used on machines that require remote logins."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):766
+msgid "Openbox inside desktop environments"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):768
+msgid "LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):771
+msgid "If installing each component of a working environment sounds like a little <e>too</e> much customisation, but you still want the flexibility of Openbox, you may want to look into a desktop environment that uses Openbox as its default window manager. That environment is <uri link=\"http://www.lxde.org/\">LXDE</uri>, the Lightweight X Desktop Environment. Designed to require even fewer system resources than Xfce, it is built around Openbox."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):783
+msgid "Openbox inside GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):786
+msgid "If you already have a GNOME environment installed, you may just want to replace the Metacity window manager with Openbox. Fortunately, this is quite a simple task! You will need to fire up your favourite editor, open your <path>~/.xinitrc</path> file, and put the following command inside it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):793
+msgid "Adding an Openbox-GNOME session to your .xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):793
+#, no-wrap
+msgid "\nexec openbox-gnome-session\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):797
+msgid "If you use GDM or another graphical login manager, you will see a new \"GNOME/Openbox\" option in your session menu. You can simply select that option instead of manually editing your <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):806
+msgid "Openbox inside KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):809
+msgid "Say you have KDE installed and like it, but you want more flexibility with your window management than KWin offers. You can use Openbox as your window manager inside of KDE by simply editing your <path>~/.xinitrc</path> file, and replacing your current exec command with the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):816
+msgid "Adding an Openbox-KDE session to your .xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):816
+#, no-wrap
+msgid "\nexec openbox-kde-session\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):820
+msgid "Now when you issue <c>startx</c> you will see KDE, but instead of KWin, you will have the customisability of the Openbox window manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):825
+msgid "If you use KDM or another graphic login manager, you will see a new \"KDE/Openbox\" option in your session menu. You can simply select that option instead of manually editing your <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):831
+msgid "This method of using Openbox with KDE has been tested with the KDE 3.x releases. While it seems highly likely that it will work with the KDE 4.x series, it has not been thoroughly tested as of yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):840
+msgid "Openbox inside Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):843
+msgid "If you use Xfce4 and would like to replace xfwm4 with Openbox, you will need to go about it a little differently than with KDE or GNOME. First, you need to start your normal Xfce session, and open up a terminal. From the terminal, issue the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):850
+msgid "Killing xfwm4 and replacing it with Openbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):850
+#, no-wrap
+msgid "\n$ <i>killall xfwm4 ; openbox &amp; exit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):854
+msgid "Second, you need to exit out of your Xfce session, and make sure to tick the checkbox that says \"Save session for future login.\" This will keep Openbox as your default window manager. Third, you will notice that you can't logout properly when using the default menu action. To fix this problem, open up your <path>menu.xml</path>, and locate this line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):862
+msgid "Finding the exit action in menu.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):862
+#, no-wrap
+msgid "\n&lt;item label=\"Exit\"&gt;\n     &lt;action name=\"Exit\"/&gt;\n&lt;/item&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):868
+msgid "Change it to this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):872
+msgid "Replacing the exit action in menu.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):872
+#, no-wrap
+msgid "\n&lt;item label=\"Exit\"&gt;\n  &lt;action name=\"Execute\"&gt;\n    &lt;command&gt;xfce4-session-logout&lt;/command&gt;\n  &lt;/action&gt;\n&lt;/item&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):880
+msgid "With Xfce4, the root-menu provided by Xfdesktop will be used instead of the Openbox root-menu."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):890
+msgid "Further documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):892
+msgid "External resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):895
+msgid "While this document will easily take you through the inital installation and customisation of Openbox, it is by no means the only reference on the topic. There are several other resources that will aid you in creating your perfect Openbox setup. Some of them are listed below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):903
+msgid "On <uri link=\"http://openbox.org/\">The Official Openbox website</uri> you will find more detailed information regarding theming, creating menus (including pipe menus), autostart scripting, and much more. This site also has information regarding new releases, upgrades, and instructions on how you can contribute to development."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):910
+msgid "The <uri link=\"http://urukrama.wordpress.com/openbox-guide/\">Urukrama's Guide to Openbox</uri> blog contains a plethora of information about switching GTK+ themes, setting up keybindings, desktop effects, and other programs to use in conjunction with Openbox. Though the tutorial was originally written for use with Ubuntu, everything is applicable to Gentoo (and other Linux distributions for that matter)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):918
+msgid "<uri link=\"http://www.box-look.org/\">Box-Look</uri> provides numerous themes, icons, wallpapers, fonts, and tools to be used with Openbox (as well as the other *box window managers like Fluxbox, Blackbox, PekWM, etc.)"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/openrc-migration.xml.pot b/doc/gettext/openrc-migration.xml.pot
new file mode 100644
index 0000000..9e2476f
--- /dev/null
+++ b/doc/gettext/openrc-migration.xml.pot
@@ -0,0 +1,378 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(guide:link):5
+msgid "/doc/en/openrc-migration.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):6
+msgid "Baselayout and OpenRC Migration Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(mail:link):9
+msgid "cardoe"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(author:title):14
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(mail:link):15
+msgid "uberlord"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(abstract):18
+msgid "This guide shows you how to migrate from baselayout-1 to baselayout-2 and OpenRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(version):27
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(date):28
+msgid "2010-07-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):31
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):33
+msgid "What's baselayout?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):36
+msgid "Baselayout provides a basic set of files that are necessary for all systems to function properly, such as <path>/etc/hosts</path>. It also provides the basic filesystem layout used by Gentoo (i.e. <path>/etc</path>, <path>/var</path>, <path>/usr</path>, <path>/home</path> directories)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):46
+msgid "What's OpenRC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):49
+msgid "OpenRC is a dependency-based rc system that works with whatever init is provided by the system, normally <path>/sbin/init</path>. However, it is <e>not</e> a replacement for <path>/sbin/init</path>. The default init used by Gentoo Linux is <c>sys-apps/sysvinit</c>, while Gentoo/FreeBSD uses the FreeBSD init provided by <c>sys-freebsd/freebsd-sbin</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):60
+msgid "So why migrate?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):63
+msgid "Originally Gentoo's rc system was built into baselayout 1 and written entirely in bash. This led to several limitations. For example, certain system calls need to be accessed during boot and this required C-based callouts to be added. These callouts were each statically linked, causing the rc system to bloat over time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):70
+msgid "Additionally, as Gentoo expanded to other platforms like Gentoo/FreeBSD and Gentoo Embedded, it became impossible to require a bash-based rc system. This led to a development of baselayout 2, which is written in C and only requires a POSIX-compliant shell. During the development of baselayout 2, it was determined that it was a better fit if baselayout merely provided the base files and filesystem layout for Gentoo and the rc system was broken off into its own package. Thus we have OpenRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):80
+msgid "OpenRC is primarily developed by <uri link=\"http://roy.marples.name/openrc\">Roy Marples</uri> and supports all current Gentoo variations (i.e. Gentoo Linux, Gentoo/FreeBSD, Gentoo Embedded, and Gentoo Vserver) and other platforms such as FreeBSD and NetBSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):92
+msgid "Migration to OpenRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):96
+msgid "Migration to OpenRC is fairly straightforward; it will be pulled in as part of your regular upgrade process by your package manager. The most important step actually comes after you install the new <c>&gt;=sys-apps/baselayout-2</c> and <c>sys-apps/openrc</c> packages. It is <e>critical</e> that you run <c>dispatch-conf</c> and ensure your <path>/etc</path> is up to date before rebooting. <brite>Failure to do so will result in an unbootable system</brite> and will require the use of the Gentoo LiveCD to perform the steps below to repair your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):107
+msgid "Once you've finished updating your config files, there are a few things to verify prior to rebooting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):116
+msgid "/etc/conf.d/rc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):119
+msgid "<path>/etc/conf.d/rc</path> has been deprecated and any settings you have in there will need to be migrated to the appropriate settings in <path>/etc/rc.conf</path>. Please read through <path>/etc/rc.conf</path> and <path>/etc/conf.d/rc</path> and migrate the settings. Once you are complete, delete <path>/etc/conf.d/rc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):130
+msgid "Kernel modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):133
+msgid "Normally, when you want certain kernel modules automatically loaded at boot, you place them into <path>/etc/modules.autoload.d/kernel-2.6</path> along with any parameters you wanted to pass to them. In baselayout-2, this file is not used anymore. Instead, autoloaded modules and module parameters are placed in one file, <path>/etc/conf.d/modules</path>, no matter the kernel version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):141
+msgid "An example old style configuration would be:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):145
+msgid "/etc/modules.autoload.d/kernel-2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):145
+#, no-wrap
+msgid "\nivtv\ncx88_dvb video_br=2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):150
+msgid "Converting the above example would result in the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):154
+msgid "/etc/conf.d/modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):154
+#, no-wrap
+msgid "\n<comment># Modules autoloaded at boot</comment>\nmodules_2_6=\"ivtv cx88_dvb\"\n<comment># Module parameters</comment>\nmodule_cx88_dvb_args_2_6=\"video_br=2\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):161
+msgid "In the above examples, the modules and their parameters would only be passed to 2.6.x series kernels. The new configuration allows for fine grained control over the modules and parameters based on kernel version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):167
+msgid "An in-depth example would be:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):171
+msgid "detailed example of /etc/conf.d/modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):171
+#, no-wrap
+msgid "\n<comment># Always load ochi1394 and ieee1394, no matter the kernel version</comment>\nmodules=\"ohci1394 ieee1394\"\n<comment># Only load tun and usbserial for 2.6.x series kernels</comment>\nmodules_2_6=\"tun usbserial\"\n<comment># Only load cx88_dvb for 2.6.23 kernels</comment>\nmodules_2_6_23=\"cx88_dvb\"\n<comment># Only load ivtv for 2.6.23-gentoo-r5</comment>\nmodules_2_6_23_gentoo_r5=\"ivtv\"\n\n<comment># For 2.6.23-gentoo-r5, pass video_br=2 to cx88_dvb</comment>\nmodule_cx88_dvb_args_2_6_23_gentoo_r5=\"video_br=2\"\n<comment># For 2.6.x series kernels, always pass vendor and product</comment>\nmodule_usbserial_args_2_6=\"vendor=0x1410 product=0x2110\"\n<comment># Always pass debug to ieee1394</comment>\nmodule_ieee1394_args=\"debug\" \n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(impo):189
+msgid "The <b>module*</b> variables are not cumulative. The more version-specific variables will override the more general variables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(note):194
+msgid "Please note the difference between <b>module_</b> and <b>modules_</b>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):201
+msgid "Boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):204
+msgid "The <c>boot</c> runlevel performs several important steps for every machine. For example, making sure your root filesystem is mounted read/write, that your filesystems are checked for errors, that your mountpoints are available, and that the <path>/proc</path> pseudo-filesystem is started at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):211
+msgid "With OpenRC, volume management services for your block storage devices are no longer run automatically at boot. This includes lvm, raid, swap, device-mapper (dm), dm-crypt, evms, and the like. You must ensure the appropriate initscript for these services is in the <c>boot</c> runlevel, otherwise it's possible that your system will not boot!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):219
+msgid "While the OpenRC ebuild will attempt to do this migration for you, you should verify that it migrated all the volume management services properly:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):224
+msgid "Display all services in boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):224
+#, no-wrap
+msgid "\n# <i>ls -l /etc/runlevels/boot/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):228
+msgid "If you don't see root, procfs, mtab, swap, and fsck in the above listing, perform the following to add them to the <c>boot</c> runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):233
+msgid "Adding critical services to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):233
+#, no-wrap
+msgid "\n# <i>rc-update add root boot</i>\n# <i>rc-update add procfs boot</i>\n# <i>rc-update add mtab boot</i>\n# <i>rc-update add fsck boot</i>\n# <i>rc-update add swap boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):241
+msgid "If you know you use mdraid and lvm but do not see them above, you would run the following to add initscripts to the <c>boot</c> runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):246
+msgid "Adding mdraid and lvm to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):246
+#, no-wrap
+msgid "\n# <i>rc-update add mdraid boot</i>\n# <i>rc-update add lvm boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):254
+msgid "Udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):257
+msgid "OpenRC no longer starts <c>udev</c> by default, but it does need to be present in the <c>sysinit</c> runlevel to be started. The OpenRC ebuild should detect if <c>udev</c> was previously enabled and add it to the <c>sysinit</c> runlevel. However, to be safe, check if <c>udev</c> is present:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):264
+msgid "Verifying udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):264
+#, no-wrap
+msgid "\n# <i>ls -l /etc/runlevels/sysinit</i>\nlrwxrwxrwx 1 root root 14 2009-01-29 08:00 /etc/runlevels/sysinit/udev -&gt; \\\n/etc/init.d/udev\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):270
+msgid "If <c>udev</c> is not listed, add it to the correct runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):274
+msgid "Adding udev to the sysinit runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):274
+#, no-wrap
+msgid "\n# <i>rc-update add udev sysinit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):281
+msgid "Network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):284
+msgid "Due to baselayout and OpenRC being broken into two different packages, your net.eth0 initscript may disappear during the upgrade process. To replace this initscript please perform the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):290
+msgid "Adding back missing net.eth0 script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):290
+#, no-wrap
+msgid "\n# <i>cd /etc/init.d</i>\n# <i>ln -s net.lo net.eth0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):295
+msgid "If you are missing any other network initscripts, follow the instructions above to re-add them. Simply replace <c>eth0</c> with the name of your network device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):301
+msgid "Also, <path>/etc/conf.d/net</path> no longer uses bash-style arrays for configuration. Please review <path>/usr/share/doc/openrc-&lt;version&gt;/net.example</path> for configuration instructions. Conversion should be relatively straight-forward, for example a static IP assignment would change as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):309
+msgid "Old /etc/conf.d/net style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):309
+#, no-wrap
+msgid "\nconfig_eth0=( \"192.168.1.37 netmask 255.255.255.0 brd 192.168.1.255\" )\nroutes_eth0=( \"default via 192.168.1.100\" )\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):314
+msgid "New /etc/conf.d/net style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):314
+#, no-wrap
+msgid "\nconfig_eth0=\"192.168.1.37 netmask 255.255.255.0 brd 192.168.1.255\"\nroutes_eth0=\"default via 192.168.1.100\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):322
+msgid "Clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):325
+msgid "Clock settings have been renamed from <path>/etc/conf.d/clock</path> to your system's native tool for adjusting the clock. This means on Linux it will be <path>/etc/conf.d/hwclock</path> and on FreeBSD it will be <path>/etc/conf.d/adjkerntz</path>. Systems without a working real time clock (RTC) chip should use <path>/etc/init.d/swclock</path>, which sets the system time based on the mtime of a file which is created at system shutdown. The initscripts in <path>/etc/init.d/</path> have also been renamed accordingly, so make sure the appropriate script for your system has been added to the boot runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):337
+msgid "Additionally, the <c>TIMEZONE</c> variable is no longer in this file. Its contents are instead found in the <path>/etc/timezone</path> file. If it doesn't exist, you will of course have to create it with your timezone. Please review both of these files to ensure their correctness."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):344
+msgid "The proper value for this file is the path relative to your timezone from <path>/usr/share/zoneinfo</path>. For example, for someone living on the east coast of the United States, the following would be a correct setting:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):350
+msgid "/etc/timezone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):350
+#, no-wrap
+msgid "\nAmerica/New_York\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):357
+msgid "XSESSION"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):360
+msgid "The XSESSION variable is no longer found in <path>/etc/rc.conf</path>. Instead, you can set the XSESSION variable per-user in <path>~/.bashrc</path> (or equivalent), or system-wide in <path>/etc/env.d/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):366
+msgid "Here's an example of setting XSESSION for the whole system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):370
+msgid "Setting XSESSION system-wide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):370
+#, no-wrap
+msgid "\n# <i>echo 'XSESSION=\"Xfce4\"' &gt; /etc/env.d/90xsession</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(impo):374 ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(impo):394
+msgid "You must run <c>env-update</c> after creating a file in <path>/etc/env.d</path>, and then logout and login for it to take effect. If you set the variable in <path>~/.bashrc</path>, you can re-source the file with <c>source ~/.bashrc</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):384
+msgid "EDITOR and PAGER"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):387
+msgid "The EDITOR variable is no longer found in <path>/etc/rc.conf</path>. Both EDITOR and PAGER are set by default in <path>/etc/profile</path>. You should change this as needed in your <path>~/.bashrc</path> (or equivalent) file or create <path>/etc/env.d/99editor</path> and set the system default there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):404
+msgid "Boot log"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):407
+msgid "Previously, you could log the boot process by using <c>app-admin/showconsole</c>. However, OpenRC now handles all logging internally, so there's no need for the hacks that <c>showconsole</c> employed. You can safely unmerge <c>showconsole</c>. To continue logging boot messages, just set the appropriate variable in <path>/etc/rc.conf</path>. Logs will appear in <path>/var/log/rc.log</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):416
+msgid "Enabling boot logging in /etc/rc.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):416
+#, no-wrap
+msgid "\nrc_logger=\"YES\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):423
+msgid "Finishing up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):426
+msgid "Once you've finished updating your config files and initscripts, the last thing to do is <b>reboot</b>. This is necessary because system state information is not preserved during the upgrade, so you'll need to provide it with a fresh boot."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/overview.xml.pot b/doc/gettext/overview.xml.pot
new file mode 100644
index 0000000..1bdaf1b
--- /dev/null
+++ b/doc/gettext/overview.xml.pot
@@ -0,0 +1,32 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(version):10
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(title):12
+msgid "Documentation Development Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(title):19
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(p):22
+msgid "On this page you'll find an overview of all available documentation files, important bugs, etc."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/pda-guide.xml.pot b/doc/gettext/pda-guide.xml.pot
new file mode 100644
index 0000000..25bc202
--- /dev/null
+++ b/doc/gettext/pda-guide.xml.pot
@@ -0,0 +1,276 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(guide:link):5
+msgid "/doc/en/pda-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):6
+msgid "Gentoo PDA Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(mail:link):12
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(mail):12
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(abstract):15
+msgid "Nowadays, personal digital assistants, or PDAs, are quite popular. Not only do they provide more features than before, they are also easy to handle, even by people who aren't that computer literate. But how can you synchronise these PDAs with your Gentoo Linux installation if they are almost all running Windows Mobile?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(version):27
+msgid "1.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(date):28
+msgid "2007-11-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):31
+msgid "Setting up PDA Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):33 ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):147
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):36
+msgid "PDAs are everywhere. They are an evolution of the paper journals and address books and have become very feature-rich: addresses and telephone numbers, pictures and movies, small spreadsheets or documents, calender entries, ... anything is possible with PDAs. And thanks to wireless technology, PDAs can manipulate or receive data from various devices (like GPS devices or other PDAs) or join the world-wide Internet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):45
+msgid "However, most PDAs run a propriatary operating system and might not be easy to synchronise with your computer if you are not running software of the same vendor. Luckily, the free software community has made serious efforts in reverse engineering access to the PDAs and some companies have even opened their specification to connect with the PDA. This guide will cover accessing and synchronizing PDAs with your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):57
+msgid "Kernel Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):60
+msgid "The first thing we need to do is get the kernel to recognize our device. Open up the kernel configuration (for instance, through <c>make menuconfig</c>) and add support for your PDA. If your device uses USB to connect to a computer you will most likely find support for it under <e>Device Drivers -&gt; USB support -&gt; USB Serial Converter support</e>. For instance, iPAQ users (and many others) can use the <e>USB PocketPC PDA Driver</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):69
+msgid "Kernel Driver Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):69
+#, no-wrap
+msgid "\n&lt;M&gt; USB Serial Converter support\n[ ]   USB Serial Console device support (EXPERIMENTAL)\n[ ]   USB Generic Serial Driver\n&lt; &gt;   USB Belkin and Peracom Single Port Serial Driver\n&lt; &gt;   USB ConnectTech WhiteHEAT Serial Driver\n&lt; &gt;   USB Digi International AccelePort USB Serial Driver\n&lt; &gt;   USB Cypress M8 USB Serial Driver\n&lt; &gt;   USB Empeg empeg-car Mark I/II Driver\n&lt; &gt;   USB FTDI Single Port Serial Driver (EXPERIMENTAL)\n&lt; &gt;   USB Handspring Visor / Palm m50x / Sony Clie Driver\n&lt;M&gt;   USB PocketPC PDA Driver\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):83
+msgid "You might wonder why it is called a <e>Serial Converter</e>. This is because you are going to use USB (technology) to talk with your device, even though the device itself is accessed using a serial protocol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):89
+msgid "You will also need asynchronous PPP support:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):93
+msgid "Kernel Driver Setup for Async PPP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):93
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\n  Network device support ---&gt;\n    &lt;M&gt; PPP (point-to-point protocol) support\n      &lt;M&gt; PPP support for async serial ports\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):100
+msgid "Rebuild the kernel and its modules. If you only had to modify a module, you can install the modules and continue. Otherwise, set up the new kernel in your boot loader and reboot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):109
+msgid "Detecting Your PDA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):112
+msgid "Ok, now that we have the kernel module setup, let's go ahead and get some information. Plug in your device and take a look at your modules list if you have build support for the device as a kernel module:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):118
+msgid "Checking if your PDA is detected"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):118
+#, no-wrap
+msgid "\n# <i>lsmod</i>\nModule                  Size  Used by\nipaq                   30736  0\nusbserial              25120  1 ipaq\n<comment>(...)</comment>\n\n# <i>dmesg | grep Pocket</i>\ndrivers/usb/serial/usb-serial.c: USB Serial support registered for PocketPC PDA\ndrivers/usb/serial/ipaq.c: USB PocketPC PDA driver v0.5\nipaq 3-2:1.0: PocketPC PDA converter detected\nusb 3-2: PocketPC PDA converter now attached to ttyUSB0\n\n# <i>ls -la /dev/ttyUSB0</i>\ncrw-rw---- 1 root uucp 188, 0 Sep 27 19:21 /dev/ttyUSB0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):135
+msgid "As we can see, the device has been detected and is now accessible through <path>/dev/ttyUSB0</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):145
+msgid "Using SynCE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):150
+msgid "<uri link=\"http://www.synce.org\">SynCE</uri> is the tool you can use to connect to and work with Windows Mobile and Windows CE powered devices. The tool connects, through the device set up earlier, to the device and allows applications to synchronise appointments, addresses and more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):157
+msgid "A list of devices supported through SynCE can be found on the <uri link=\"http://www.synce.org\">SynCE website</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):162
+msgid "SynCE is not available through a stable ebuild though, so before installing it, you will first need to mark them in <path>/etc/portage/package.keywords</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):167
+msgid "List of packages to list in package.keywords"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):167
+#, no-wrap
+msgid "\napp-pda/synce\napp-pda/synce-software-manager\napp-pda/synce-librapi2\napp-pda/synce-libsynce\napp-pda/synce-multisync_plugin\napp-pda/synce-rra\ndev-libs/libmimedir\napp-pda/synce-dccm\napp-pda/synce-trayicon\napp-pda/orange\napp-pda/dynamite\napp-pda/synce-kde\napp-pda/synce-gnomevfs\napp-pda/synce-serial\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):184
+msgid "Then, install the <c>app-pda/synce</c> and <c>net-dialup/ppp</c> packages to obtain the necessary tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):192
+msgid "Configuring the PDA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):195
+msgid "The next task is to configure the serial device we found earlier (<path>/dev/ttyUSB0</path> in our example) to be used with SynCE:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):200
+msgid "Configuring the serial device for SynCE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):200
+#, no-wrap
+msgid "\n~# <i>synce-serial-config ttyUSB0</i>\n\nYou can now run synce-serial-start to start a serial connection.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):206
+msgid "This step only has to be performed once: it stored the necessary PPP-related information inside <path>/etc/ppp/peers/synce-device</path> which is read by PPP when it is called by <c>synce-serial-start</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):215
+msgid "Accessing The Device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):218
+msgid "Now, log on as the user who will be using the PDA and run the <c>vdccm</c> command. This tool is the connection manager for SynCE through which programs connect to the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):224
+msgid "Launching the connection manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):224
+#, no-wrap
+msgid "\n~$ <i>vdccm</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):228
+msgid "As root again, run <c>synce-serial-start</c> which will connect to the device. With some PDAs, you will notice this on the PDA itself through a synchronisation symbol or any other event."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):234
+msgid "Running synce-serial-start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):234
+#, no-wrap
+msgid "\n~# <i>synce-serial-start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):238
+msgid "In some cases, the first attempts fail but this isn't shown immediately. You can rerun the command a few times until the command replies that a serial connection is already started. To verify that the connection is done, check if a ppp interface (like ppp0) is created and has an IP address attached to it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):245
+msgid "When <path>ppp0</path> is started, the configuration starts the <path>/etc/init.d/net.ppp0</path> init script which is configured through <path>/etc/conf.d/net.ppp0</path>, so you definitely want to take a look at this configuration file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):255
+msgid "File Navigation and Manipulation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):258
+msgid "The SynCE project provides a number of programs to communicate with the PDA and exchange files. The tools have similar namings as on a regular Unix system but with a <c>p</c> prepended to it: <c>pcp</c>, <c>pls</c>, <c>pmv</c>, <c>prm</c>, <c>pmkdir</c>, <c>prmdir</c>. Other tools are specific for PDAs, like <c>prun</c> to launch a program, <c>synce-install-cab</c> to install a CAB file or <c>pstatus</c> to display information about the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):267
+msgid "Beware though, the behavior of the tools is not all that intuïtive. For instance, the <c>pls</c> tool shows the contents of the <path>My Documents</path> directory whereas the <c>pcp</c> tool starts from the <path>My Device</path> location. As an example, we'll upload a file to the <path>My Documents</path> folder:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):275
+msgid "Uploading a file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):275
+#, no-wrap
+msgid "\n~$ <i>pls</i>\nDirectory               Tue 01 Jan 2002 01:00:00 PM CET  Business/\nDirectory               Tue 01 Jan 2002 01:00:00 PM CET  Personal/\nDirectory               Tue 01 Jan 2002 01:00:00 PM CET  Templates/\n~$ <i>pcp music.mp3 :\"My Documents/music.mp3\"</i>\nFile copy of 3852416 bytes took 0 minutes and 38 seconds, that's 101379 bytes/s.\n~$ <i>pls</i>\nArchive        3852416  Wed 02 Jan 2002 07:05:06 PM CET  music.mp3\nDirectory               Tue 01 Jan 2002 01:00:00 PM CET  Business/\nDirectory               Tue 01 Jan 2002 01:00:00 PM CET  Personal/\nDirectory               Tue 01 Jan 2002 01:00:00 PM CET  Templates/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):292
+msgid "SynCE for KDE Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):295
+msgid "The <uri link=\"http://synce.sourceforge.net/synce/kde/\">SynCE for KDE Project</uri> aims to support PDAs within KDE by facilitating file exchange, synchronisation and installation and even provide mirroring capabilities so you can control your PDA from within KDE."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):303
+msgid "The <c>raki</c> tool is SynCE's PocketPC management tool for KDE. The first time you launch it, it asks whether you use <c>dccm</c> or <c>vdccm</c>. Once you selected the connection manager you use (in our example it would be <c>vdccm</c>) your KDE session (or any environment which supports KDE applets) will now have a PDA applet from which you can browse and synchronise your PDA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):311
+msgid "However, KDE integration for PDAs is better maintained through KPilot..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):320
+msgid "All-In-One Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):322
+msgid "KPilot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(note):325
+msgid "The author did not get KPilot to run well on his iPAQ as it timed out before the connection was made. If anyone knows a possible solution to this, please report this at <uri link=\"https://bugs.gentoo.org/XXXXXX\">bug XXXXXX</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):331
+msgid "The <c>kde-base/kpilot</c> application provides synchronisation support from the PDA with Kontact (KDE) or Evolution (GNOME). Its setup is quite easy: install the package and launch it. The first time you run it, it will ask you to identify your PDA, either by passing on the device name or having KPilot auto-detect the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):339
+msgid "Once configured, you can quickly synchronise tasks, data, addresses and messages between your PDA and Kontact, the KDE PIM manager."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/portage-utils.xml.pot b/doc/gettext/portage-utils.xml.pot
new file mode 100644
index 0000000..80cafaa
--- /dev/null
+++ b/doc/gettext/portage-utils.xml.pot
@@ -0,0 +1,241 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(guide:link):5
+msgid "/doc/en/portage-utils.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):7
+msgid "Portage-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail:link):10
+msgid "rane@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail):10
+msgid "Łukasz Damentko"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(author:title):12 ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(author:title):15
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail:link):13
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail):13
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail:link):16
+msgid "vanquirius@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail):16
+msgid "Marcelo Góes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(abstract):19
+msgid "This guide covers some common uses of portage-utils, a set of fast Portage helper applications written in C."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(version):28
+msgid "1.3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(date):29
+msgid "2007-05-23"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):32
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):36
+msgid "<c>portage-utils</c> is a collection of very fast utilities written in C, which are meant to offer a faster but more limited alternative to their <c>gentoolkit</c> counterparts. Please note that <c>portage-utils</c> is not meant to replace <c>gentoolkit</c>. Its utilities are much more efficient than the equivalent ones from <c>gentoolkit</c> and might be better suited to be used in scripts that need to call Portage repeatedly, but <c>portage-utils</c> does not offer the same functionalities. It does not consider eclasses at all and does not provide tools like <c>revdep-rebuild</c> and <c>glsa-check</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):47
+msgid "More information about <c>gentoolkit</c> can be found in the <uri link=\"/doc/en/gentoolkit.xml\">Gentoolkit</uri> guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):52
+msgid "You can view the complete list of applications in <c>portage-utils</c> by typing <c>man q</c> or <c>q --help</c>. Please read the man page for each utility described, as this guide is only meant to be a short reference for the most useful functions and does not include all the information about each application."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):60
+msgid "The first step of using <c>portage-utils</c> is to install the package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):64
+msgid "Installing portage-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):64
+#, no-wrap
+msgid "\n# <i>emerge portage-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):73
+msgid "Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):75
+msgid "How to find a package to which a file belongs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):78
+msgid "<c>qfile</c> finds the package to which a file belongs:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):82
+msgid "Finding the package to which a file belongs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):82
+#, no-wrap
+msgid "\n$ <i>qfile /etc/fonts/fonts.conf</i>\nmedia-libs/fontconfig (/etc/fonts/fonts.conf)\n$ <i>qfile /usr/share/keymaps/atari/atari-uk-falcon.map.gz</i>\nsys-apps/kbd (/usr/share/keymaps/atari/atari-uk-falcon.map.gz)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):92
+msgid "Verifying package integrity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):95
+msgid "If you want to check MD5 sums or mtimes of the files installed by some package, you can do it using the <c>qcheck</c> application:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):100
+msgid "Checking package integrity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):100
+#, no-wrap
+msgid "\n$ <i>qcheck portage-utils</i>\nChecking app-portage/portage-utils-0.1.13 ...\n  * 36 out of 36 files are good\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):106
+msgid "Of course, all the files which were changed after installation will be reported here. If the application reports configuration files which you have manually edited after installation, there's nothing to worry about."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):115 ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):125
+msgid "Listing packages which depend on some package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):118
+msgid "Of course there's also an application which allows you to list all the packages which depend on some package. This is done using <c>qdepends</c>. Use the <c>-a</c> flag to show all the DEPEND, RDEPEND, and PDEPEND information for a package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):125
+#, no-wrap
+msgid "\n$ <i>qdepends -a pygtk</i>\n * DEPEND\ndev-python/pygtk-2.8.2: &gt;=dev-lang/python-2.3 &gt;=x11-libs/gtk+-2.8.0\n&gt;=dev-libs/glib-2.8.0 &gt;=x11-libs/pango-1.10.0 &gt;=dev-libs/atk-1.8.0\n&gt;=gnome-base/libglade-2.5.0 &gt;=dev-python/pycairo-0.9.0 dev-python/numeric\nvirtual/opengl dev-python/pyopengl &gt;=x11-libs/gtkglarea-1.99\n&gt;=dev-util/pkgconfig-0.9 sys-devel/patch\n * RDEPEND\ndev-python/pygtk-2.8.2: &gt;=dev-lang/python-2.3 &gt;=x11-libs/gtk+-2.8.0\n&gt;=dev-libs/glib-2.8.0 &gt;=x11-libs/pango-1.10.0 &gt;=dev-libs/atk-1.8.0\n&gt;=gnome-base/libglade-2.5.0 &gt;=dev-python/pycairo-0.9.0 dev-python/numeric\nvirtual/opengl dev-python/pyopengl &gt;=x11-libs/gtkglarea-1.99\n * PDEPEND\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):144
+msgid "Listing files that belong to an ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):147
+msgid "<c>qlist</c> gives you a list of all files that belong to an ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):151
+msgid "Listing files which belong to an ebuild file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):151
+#, no-wrap
+msgid "\n$ <i>qlist vim</i>\n/usr/bin/gvim\n/usr/bin/gvimdiff\n/usr/bin/evim\n/usr/bin/eview\n/usr/bin/gview\n/usr/bin/rgvim\n[...]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):165
+msgid "Looking for packages that use some USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):168
+msgid "This is done with <c>quse</c>, which must be run as root. It may take some time to first create/update the ebuild cache."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):173
+msgid "Looking for packages with the 'firefox' USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):173
+#, no-wrap
+msgid "\n# <i>quse firefox</i>\napp-office/openoffice/openoffice-2.0.2_rc1.ebuild binfilter curl eds firefox gnome gtk java kde ldap xml2\ndev-haskell/gtk2hs/gtk2hs-0.9.10.ebuild doc glade gnome firefox\ndev-java/swt/swt-3.1-r1.ebuild accessibility cairo firefox gnome\n[...]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):184
+msgid "Finding package sizes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):187
+msgid "This is done with <c>qsize</c> application and is as simple as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):191
+msgid "Finding package size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):191
+#, no-wrap
+msgid "\n$ <i>qsize vim</i>\napp-editors/gvim-6.4: 10 files, 7 non-files, 2327.516 KB\napp-editors/vim-6.4: 6 files, 2 non-files, 2058.14 KB\napp-editors/vim-core-6.4: 1024 files, 68 non-files, 10950.984 KB\n[...]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):202
+msgid "Searching the Portage tree"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):205
+msgid "One of the most powerful tools of <c>portage-utils</c> is <c>qsearch</c>. This tool allows you to search your Portage tree much faster than default <c>emerge -s</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):211
+msgid "Here are some examples of its usage:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):215
+msgid "Using qsearch to search the tree"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):215
+#, no-wrap
+msgid "\n<comment>(I forgot the name of the package with my favorite fonts)</comment>\n$ <i>qsearch terminus</i>\nmedia-fonts/terminus-font A clean fixed font for the console and X11\n\n<comment>(I want to thank the guy who made them. What's his homepage?)</comment>\n$ <i>qsearch -H terminus</i>\nmedia-fonts/terminus-font http://www.is-vn.bg/hamster/jimmy-en.html\n\n<comment>(I need a jabber client and I need it now)</comment>\n$ <i>qsearch -S \"jabber client\"</i>\napp-emacs/emacs-jabber A Jabber client for Emacs.\nnet-im/gajim Jabber client written in PyGTK\nnet-im/gnome-jabber Gnome Jabber Client\nnet-im/gossip Lightweight Jabber client for GNOME\nnet-im/imcom Python commandline Jabber Client\nnet-im/psi QT 3.x Jabber Client, with Licq-like interface\nnet-im/tkabber Featureful Jabber client for tcl/tk.\nx11-themes/psi-themes Iconsets for Psi, a QT 3.x Jabber Client\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):239
+msgid "Extracting information from emerge logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):242
+msgid "There is also a tool that allows you to extract useful information from your <path>emerge.log</path> file. It's called <c>qlop</c> and it can be useful when you want to estimate package compilation times or compare with your friends whose computer compiles faster. It also allows you to check what's compiling at the moment and how long it will take - which is handy when you're working in the console and don't have any other means to check it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):251
+msgid "Reading emerge logs with qlop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):251
+#, no-wrap
+msgid "\n<comment>(I'm starting to emerge perl and I want an estimate on how long it usually takes)</comment>\n$ <i>qlop -tH perl</i>\nperl: 7 minutes, 52 seconds for 4 merges\n<comment>(Now let's see what's emerging at the moment)</comment>\n$ <i>qlop -c</i>\n* perl-5.8.8-r23\n    started: Mon May 21 12:41:11 2007\n    elapsed: 19 seconds\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/postgres-howto.xml.pot b/doc/gettext/postgres-howto.xml.pot
new file mode 100644
index 0000000..73a37cc
--- /dev/null
+++ b/doc/gettext/postgres-howto.xml.pot
@@ -0,0 +1,654 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(guide:link):5
+msgid "/doc/en/postgres-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):6
+msgid "PostgreSQL Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(mail:link):12
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(mail):12
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(abstract):15
+msgid "This guide is meant to show the basic setup of PostgreSQL. The setup described here should be sufficient enough to use for basic web appplications, and any other program that provides PostgreSQL support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(version):25
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(date):26
+msgid "2007-04-25"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):29
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):31
+msgid "PostgreSQL introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):34
+msgid "When talking to most developers about the different database solutions to use, two major databases will usually form the answer. One would be <c>MySQL</c>, and the other is what this document will refer to, <c>PostgreSQL</c>. The advantages of one over the other is a somewhat long winded debate, however it is just to say that PostgreSQL has had a more firm grasp on true relational database structure than MySQL. Most of the standard features such as <b>FOREIGN KEY</b> was only just added in MySQL 5. However, whatever the case may be, this document assumes that you have selected PostgreSQL as the database to use. The first place to start is the <c>emerge</c> process. In the next section, the installation process through emerge will be described, as well as the basic configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):51
+msgid "PostgreSQL installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):54
+msgid "To begin, we must first <c>emerge</c> the PostgreSQL package. To do so, run the following code to first ensure that the options for it are properly set:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):59
+msgid "Checking the PostgreSQL build options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):59
+#, no-wrap
+msgid "\n# <i>emerge -pv postgresql</i>\n\nThese are the packages that I would merge, in order:\n\nCalculating dependencies ...done!\n[ebuild  N    ] dev-db/postgresql-8.0.4  -doc -kerberos +nls +pam +perl -pg-intdatetime +python +readline (-selinux) +ssl -tcl +xml +zlib 0 kB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):68
+msgid "Here's a list of what the different build options indicate:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):74
+msgid "USE Flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):75
+msgid "Meaning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):78
+msgid "doc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):79
+msgid "This USE flag enables or disables the installation of documentation outside of the standard man pages. The one good time to disable this option is if you are low on space, or you have alternate methods of getting a hold of the documentation (online, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):87
+msgid "kerberos"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):88
+msgid "When connecting to the database, with this option enabled, the admin has the option of using <c>kerberos</c> to authenticate their users/services to the database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):95
+msgid "nls"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):96
+msgid "If this option is enabled, PostgreSQL can utilize translated strings for non-English speaking users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):102
+msgid "pam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):103
+msgid "If this option is enabled, and the admin configures the PostgreSQL configuration file properly, users/services will be able to login to a PostgreSQL database using <c>PAM</c> (Pluggable Authentication Module)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):110
+msgid "perl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):111
+msgid "If this option is enabled, <c>perl</c> bindings for PostgreSQL will be built."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):117
+msgid "pg-intdatetime"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):118
+msgid "If this option is enabled, PostgreSQL will support 64 bit integer date types."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):124
+msgid "python"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):125
+msgid "If this option is enabled, PostgreSQL will be built with <c>python</c> bindings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):131
+msgid "readline"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):132
+msgid "If this option is enabled, PostgreSQL will support <c>readline</c> style command line editing. This includes command history and isearch."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):138
+msgid "selinux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):139
+msgid "If this option is enabled, an <c>selinux</c> policy for PostgreSQL will be installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):145
+msgid "ssl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):146
+msgid "If this option is enabled, PostgreSQL will utilize the <c>OpenSSL</c> library to encrypt traffic between PostgreSQL clients and servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):152
+msgid "tcl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):153
+msgid "If this option is enabled, PostgreSQL will build <c>tcl</c> bindings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):158
+msgid "xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):159
+msgid "If this option is enabled, <c>XPATH</c> style xml support will be built. More information on using xml support with PostgreSQL can be found on: <uri link=\"http://www.throwingbeans.org/postgresql_and_xml.html\"> PostgreSQL and XML</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):167
+msgid "zlib"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):168
+msgid "This isn't really used by PostgreSQL itself, but by <c>pg_dump</c> to compress the dumps it produces."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):175
+msgid "Once you've customized PostgreSQL to meet your specific needs, go ahead and start the <c>emerge</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):180
+msgid "Emerge-ing PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):180
+#, no-wrap
+msgid "\n# <i>emerge postgresql</i>\n<comment>(Output shortened)</comment>\n&gt;&gt;&gt; /usr/lib/libecpg.so.5 -&gt; libecpg.so.5.0\n&gt;&gt;&gt; /usr/bin/postmaster -&gt; postgres\n * Make sure the postgres user in /etc/passwd has an account setup with /bin/bash as the shell\n *\n * Execute the following command\n * emerge --config =postgresql-8.0.4\n * to setup the initial database environment.\n *\n&gt;&gt;&gt; Regenerating /etc/ld.so.cache...\n&gt;&gt;&gt; dev-db/postgresql-8.0.4 merged.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):195
+msgid "As shown by the einfo output, there is some post setup that must be done. The next chapter will look at the actual configuration of PostgreSQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):204
+msgid "PostgreSQL configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):206
+msgid "Setting up the initial database environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):209
+msgid "As noted in the earlier <c>emerge</c> output, the initial database environment must be setup. However, before this is done, one thing needs to be considered. Unlike, say MySQL, PostgreSQL's \"root\" password is the password of the actual user. However, only the user is created by the ebuild <e>not</e> the password. So before we can begin, the password must be set for the postgres user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):217
+msgid "Setting the password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):217
+#, no-wrap
+msgid "\n# <i>passwd postgres</i>\nNew UNIX password:\nRetype new UNIX password:\npasswd: password updated successfully\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):224
+msgid "Now that this is set up, the creation of the initial database environment can occur:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):229
+msgid "Configuring the database environment with emerge --config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):229
+#, no-wrap
+msgid "\n# <i>emerge --config =postgresql-8.0.4</i>\n\n\nConfiguring pkg...\n\n * Creating the data directory ...\n * Initializing the database ...\nThe files belonging to this database system will be owned by user \"postgres\".\nThis user must also own the server process.\n\nThe database cluster will be initialized with locale C.\n\nfixing permissions on existing directory /var/lib/postgresql/data ... ok\ncreating directory /var/lib/postgresql/data/global ... ok\ncreating directory /var/lib/postgresql/data/pg_xlog ... ok\ncreating directory /var/lib/postgresql/data/pg_xlog/archive_status ... ok\ncreating directory /var/lib/postgresql/data/pg_clog ... ok\ncreating directory /var/lib/postgresql/data/pg_subtrans ... ok\ncreating directory /var/lib/postgresql/data/base ... ok\ncreating directory /var/lib/postgresql/data/base/1 ... ok\ncreating directory /var/lib/postgresql/data/pg_tblspc ... ok\nselecting default max_connections ... 100\nselecting default shared_buffers ... 1000\ncreating configuration files ... ok\ncreating template1 database in /var/lib/postgresql/data/base/1 ... ok\ninitializing pg_shadow ... ok\nenabling unlimited row size for system tables ... ok\ninitializing pg_depend ... ok\ncreating system views ... ok\nloading pg_description ... ok\ncreating conversions ... ok\nsetting privileges on built-in objects ... ok\ncreating information schema ... ok\nvacuuming database template1 ... ok\ncopying template1 to template0 ... ok\n\nWARNING: enabling \"trust\" authentication for local connections\nYou can change this by editing pg_hba.conf or using the -A option the\nnext time you run initdb.\n\nSuccess. You can now start the database server using:\n\n    /usr/bin/postmaster -D /var/lib/postgresql/data\nor\n    /usr/bin/pg_ctl -D /var/lib/postgresql/data -l logfile start\n\n *\n * You can use /etc/init.d/postgresql script to run PostgreSQL instead of pg_ctl.\n *\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):281
+msgid "Now the initial database environment is setup. The next section will look at verifying the install and setting up users to access the database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):289
+msgid "PostgreSQL database setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):292
+msgid "Now that PostgreSQL is setup, it's a good idea at this point to verify the installation. First, make sure the service starts up ok:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):297
+msgid "Starting up the PostgreSQL service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):297
+#, no-wrap
+msgid "\n# <i>/etc/init.d/postgresql start</i>\n* Starting PostgreSQL ...                                          [ ok ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):302
+msgid "Once this is verified working, it's also a good idea to add it to the default runlevel so it starts at boot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):307
+msgid "Adding to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):307
+#, no-wrap
+msgid "\n# <i>rc-update add postgresql default</i>\n* postgresql added to runlevel default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):312
+msgid "Now that the service has started, it's time to try setting up a test database. To start out, let's create a test database by using the <c>createdb</c> command. We'll also pass along the <c>-U</c> option to set the user (it defaults to the current user name if you don't), and the <c>-W</c> option to request the password we created earlier. Finally we give it the name of the database we want to create:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):321
+msgid "Creating a database with createdb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):321
+#, no-wrap
+msgid "\n$ <i>createdb -U postgres -W test</i>\nPassword:\nCREATE DATABASE\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):327
+msgid "The database was successfully created, and we can confirm that the database can run basic tasks. We'll go ahead and drop this database (remove it) with the <c>dropdb</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):333
+msgid "Dropping a database with dropdb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):333
+#, no-wrap
+msgid "\n$ <i>dropdb -U postgres -W test</i>\nPassword:\nDROP DATABASE\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):339
+msgid "Right now, only the postgres user can run commands. Obviously this is not the sort of setup one would like in a multi-user environment. The next section will look at working with user accounts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):348
+msgid "Setting up database user accounts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):351
+msgid "As mentioned earlier, having to login as the postgres user is somewhat undesirable in a mult-user environment. In most cases there will be various users and services accessing the server, and each have different permission requirements. So, to handle this, the <c>createuser</c> command can be used. This command is an alternative to running a few SQL queries, and is a lot more flexible from an admin standpoint. We'll go ahead and create two users, a 'superuser' that can add other users and administer the db, and a standard user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):361
+msgid "Setting up the superuser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):361
+#, no-wrap
+msgid "\n<comment>(replace chris with the username you'd like to use)</comment>\n$ <i>createuser -a -d -P -E -U postgres -W chris</i>\nEnter password for new user:\nEnter it again:\nPassword:\nCREATE USER\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):370
+msgid "There, we've created the superuser. The command line option <c>-a</c> specifies that this user can add other users. <c>-d</c> means that this user can create databases. <c>-P</c> let's you enter a password for the user and <c>-E</c> will encrypt it for security purposes. Now then, we'll test this new user's permissions out by setting up our standard user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):378
+msgid "Setting up the standard user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):378
+#, no-wrap
+msgid "\n<comment>(replace chris with the username you've just created)</comment>\n$ <i>createuser -A -D -P -E -U chris -W testuser</i>\nEnter password for new user:\nEnter it again:\nPassword:\nCREATE USER\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):387
+msgid "Success! Our new user was created using the previously created superuser. The <c>-A</c> and <c>-D</c> options do the opposite of <c>-a</c> and <c>-d</c>, and instead deny the user the ability to create other users and databases. Now that there are users to work with, the next chapter will look at using the new database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):399
+msgid "Using PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):401
+msgid "Setting up permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):404
+msgid "Now there is a user that can create databases and add other users, and the main postgres user that can do anything. The user created earlier can currently login to the server, and that's about it. In general, users need to be able to insert data and retrieve data, and sometimes any other number of tasks. So, for this new user to be able to do anything, they must be setup with the proper permissions. This can easily be done by passing the <c>-O</c> parameter to <c>createdb</c>. We'll start by making a new database, <b>MyDB</b> with our superuser that will be owned by the previous testuser:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):415
+msgid "Creating the MyDB database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):415
+#, no-wrap
+msgid "\n$ <i>createdb -O testuser -U chris -W MyDB</i>\nPassword:\nCREATE DATABASE\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):421
+msgid "Alright, now we have a new MyDB database, and a testuser that can access it. To test this out, we'll login as the testuser to the new MyDB database. We'll do this with the <c>psql</c> program. This program is what's used to connect to the PostgreSQL database from command line. So connect to the new database like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):429
+msgid "Logging into the MyDB database as the testuser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):429
+#, no-wrap
+msgid "\n$ <i>psql -U testuser -W MyDB</i>\nPassword:\nWelcome to psql 8.0.4, the PostgreSQL interactive terminal.\n\nType:  \\copyright for distribution terms\n       \\h for help with SQL commands\n       \\? for help with psql commands\n       \\g or terminate with semicolon to execute query\n       \\q to quit\n\nMyDB=&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):443
+msgid "So, the testuser is now logged into the database, and can begin to initiate some commands. To get a feel for using PostgreSQL, the next section will take a look at some of the basic commands in navigating the <c>psql</c> client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):452
+msgid "Basic PostgreSQL commands and creating a table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):455
+msgid "For those who are used to MySQL, this is somewhat of a definite read. This is where PostgreSQL may get somewhat unique with regards to running commands. To start, here is a list of some commands that will be discussed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):463
+msgid "Command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):464
+msgid "Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):465
+msgid "MySQL Equivalent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):468
+msgid "\\c[onnect] [DBNAME|- [USER]]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):469
+msgid "Connects to another database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):470
+msgid "USE DATABASE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):473
+msgid "\\q"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):474
+msgid "Quit the <c>psql</c> client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):475
+msgid "quit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):478
+msgid "\\i FILE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):479
+msgid "Run commands from <c>FILE</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):480
+msgid "source FILE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):483
+msgid "\\o [FILE]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):484
+msgid "Send query results to <c>FILE</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):485
+msgid "INTO OUTFILE, but outputs everything (not just SELECTS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):488
+msgid "\\d [NAME]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):489
+msgid "Describe a database or table (as well as other items)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):490
+msgid "DESC(RIBE)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):493
+msgid "\\db [PATTERN]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):494
+msgid "List available tables that match <c>PATTERN</c> (all if no pattern is given)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):498
+msgid "SHOW TABLES"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):502
+msgid "With the exception of <c>\\c[onnect]</c>, all the commands shown will be used later on in the section. So right now the database is empty. That said, we need to insert some data. The first step to inserting data, however, is to put it in a table. Right now there are no tables in the database, so we need to create one. This is done with the <c>CREATE TABLE</c> command. We'll make a table of items. They will contain a Product ID, Description, and price:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):511
+msgid "Creating the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):511
+#, no-wrap
+msgid "\nMyDB=&gt; CREATE TABLE products (\nMyDB(&gt;   product_id SERIAL,\nMyDB(&gt;   description TEXT,\nMyDB(&gt;   price DECIMAL\nMyDB(&gt; );\nNOTICE:  CREATE TABLE will create implicit sequence \"products_product_id_seq\"\nfor serial column \"products.product_id\"\nCREATE TABLE\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):522
+msgid "You can ignore the NOTICE, it's perfectly harmless. Looking at the last line of the function, <c>CREATE TABLE</c> seems to indicate that the command has succeeded. However, let's go ahead and verify that the table was indeed successfully created with the <c>\\d</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):529
+msgid "Looking at the newly created table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):529
+#, no-wrap
+msgid "\nMyDB=&gt; <i>\\d products</i>\n                                 Table \"public.products\"\n   Column    |  Type   |                            Modifiers\n-------------+---------+------------------------------------------------------------------\n product_id  | integer | not null default nextval('public.products_product_id_seq'::text)\n description | text    |\n price       | numeric |\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):539
+msgid "Indeed the table was successfully created. Now that the table is created, it needs to be populated with data. The next section will look at populating the database with data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):548
+msgid "Inserting data into the database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):551
+msgid "This section will look at the two ways of populating the newly created table with data. First let's look at the most basic command, <c>INSERT</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):556
+msgid "INSERT syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):556
+#, no-wrap
+msgid "\nINSERT INTO [tablename] (column1,column2,column3) VALUES(value1,value2,value3)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):560
+msgid "<c>tablename</c> contains the name of the table to insert the data into. (column1,column2,column3) lets you specify the specific columns to insert the values into. VALUES(value1,value2,value3) is the listing of values. The values are inserted into the same order as the columns (column1 gets value1, column2 gets value2, column3 gets value3). These counts <e>must</e> be the same. So let's go ahead and insert an item into the table:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(impo):569
+msgid "From working with databases for a long time, I personally recommend specifying <c>INSERT</c> statements exactly as above. Developers often make the mistake of using <c>INSERT INTO</c> without specifying columns. This is unproductive, as if a new column gets added to the database, it will cause in error if the value to column count is not the same. You should <e>always</e> specify the columns unless you're 300% sure you'll never add a column."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):578
+msgid "Inserting data into the table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):578
+#, no-wrap
+msgid "\nMyDB=&gt; <i>INSERT INTO products (description,price) VALUES('A test product', 12.00);</i>\nINSERT 17273 1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):583
+msgid "The last line needs a bit of explaining. The return of an insert command is an OID (Object Identifier) and the number of rows inserted. OID's are a bit beyond the scope of this guide, and the <uri link=\"http://www.postgresql.org/docs/8.1/static/datatype-oid.html\">PostgreSQL manual</uri> has some good information on it. Now, for a situation where you have 20,000 products, these insert statements can be a little tedious. However, not all is lost. The <c>COPY</c> command can be used to insert data into a table from a file or stdin. In this example, let's assume that you have a csv (comma separated values) file, which contains the product id, description, and price. The file looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):596
+msgid "products.csv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):596
+#, no-wrap
+msgid "\n2,meat,6.79\n3,soup,0.69\n4,soda,1.79\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):602
+msgid "Now we'll use the <c>COPY</c> command to populate our data:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(impo):606
+msgid "The <c>COPY FROM STDIN</c> command is used because only the postgres user can insert data from a file (for obvious security reasons)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):611
+msgid "Using COPY to populate the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):611
+#, no-wrap
+msgid "\nMyDB=&gt; <i>COPY products FROM STDIN WITH DELIMITER AS ',';</i>\nEnter data to be copied followed by a newline.\nEnd with a backslash and a period on a line by itself.\n&gt;&gt; <i>2,meat,6.79</i>\n&gt;&gt; <i>3,soup,0.69</i>\n&gt;&gt; <i>4,soda,1.79</i>\n&gt;&gt; <i>\\.</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):621
+msgid "Unfortunately, this line doesn't return the same status information as the <c>INSERT INTO</c> statement. How do we know the data was inserted? The next section will look at running queries to check our data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):630
+msgid "Using PostgreSQL queries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):633
+msgid "This section will look at using the <c>SELECT</c> statement to view data in our tables. The basic <c>SELECT</c> format looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):638
+msgid "SELECT syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):638
+#, no-wrap
+msgid "\nSELECT (column1,column2|*) FROM (table) [WHERE (conditionals)]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):642
+msgid "There are two ways to select columns. The first is using <c>*</c> to select all columns, and the second is to specify a list of specific columns you wish to see. The second is quite handy when you want to find a specific column in a rather large list of them. Let's start out with using <c>SELECT</c> with <c>*</c> to specify all columns:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):650
+msgid "Viewing the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):650
+#, no-wrap
+msgid "\nMyDB=&gt; <i>SELECT * FROM products;</i>\n product_id |  description   | price\n------------+----------------+-------\n          1 | A test product | 12.00\n          2 | meat           |  6.79\n          3 | soup           |  0.69\n          4 | soda           |  1.79\n(4 rows)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):661
+msgid "As shown here, all the data we inserted earlier is indeed in the table. Now let's say we only want to see the description and the price, and don't care about the product id. In this case we'll use the column specific SELECT form:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):667
+msgid "Viewing specific columns from the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):667
+#, no-wrap
+msgid "\nMyDB=&gt; <i>SELECT description,price FROM products;</i>\n  description   | price\n----------------+-------\n A test product | 12.00\n meat           |  6.79\n soup           |  0.69\n soda           |  1.79\n(4 rows)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):678
+msgid "Now only the product and price is shown, letting us focus on only the important data. Now let's say that we want to see only the items that are greater than $2.00. Here's where the <c>WHERE</c> clause comes in handy:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):684
+msgid "Viewing specific rows from the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):684
+#, no-wrap
+msgid "\nMyDB=&gt; <i>SELECT description,price FROM products WHERE price &gt; 2.00;</i>\n  description   | price\n----------------+-------\n A test product | 12.00\n meat           |  6.79\n(2 rows)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):693
+msgid "Now a listing of products over $2.00 is displayed, focusing the data even more. These forms of querying for information are very powerful, and can help create extremely useful reports."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):702
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):705
+msgid "This concludes the PostgreSQL Guide. A big thanks goes to Masatomo Nakano, the previous Gentoo PostgreSQL maintainer for his help in answering my questions. Any suggestions on this guide should be sent to <mail>chriswhite@gentoo.org</mail>. For more extensive documentation, see the <uri link=\"http://www.postgresql.org\">PostgreSQL website</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/power-management-guide.xml.pot b/doc/gettext/power-management-guide.xml.pot
new file mode 100644
index 0000000..2df0f8a
--- /dev/null
+++ b/doc/gettext/power-management-guide.xml.pot
@@ -0,0 +1,1323 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):6
+msgid "Power Management Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):9
+msgid "earthwings@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):9
+msgid "Dennis Nienhüser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):12
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):12
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):18
+msgid "Power Management is the key to extend battery run time on mobile systems like laptops. This guide assists you setting it up on your laptop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):27
+msgid "1.47"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):28
+msgid "2010-07-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):35
+msgid "Capacity and lifetime of laptop batteries have improved much in the last years. Nevertheless modern processors consume much more energy than older ones and each laptop generation introduces more devices hungry for energy. That's why Power Management is more important than ever. Increasing battery run time doesn't necessarily mean buying another battery. Much can be achieved applying intelligent Power Management policies."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):47
+msgid "A Quick Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):50
+msgid "Please notice that this guide describes Power Management for <e>laptops</e>. While some sections might also suite for <e>servers</e>, others do not and may even cause harm. Please do not apply anything from this guide to a server unless you really know what you are doing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):57
+msgid "As this guide has become rather long, here's a short overview helping you to find your way through it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):62
+msgid "The <uri link=\"#doc_chap2\">Prerequisites</uri> chapter talks about some requirements that should be met before any of the following device individual sections will work. This includes BIOS settings, kernel configuration and some simplifications in user land. The following three chapters focus on devices that typically consume most energy - processor, display and hard drive. Each can be configured seperately. <uri link=\"#doc_chap3\">CPU Power Management</uri> shows how to adjust the processor's frequency to save a maximum of energy without losing too much performance. A few different tricks prevent your hard drive from working unnecessarily often in <uri link=\"#doc_chap5\">Disk Power Management</uri> (decreasing noise level as a nice side effect). Some notes on graphics cards, Wireless LAN and USB finish the device section in <uri link=\"#doc_chap6\">Power Management For Other Devices</uri> while another chapter is dedicated to the (rather experimental) <uri link=\"#doc_chap7\">sleep states</uri>. Last not least <uri link=\"#doc_chap8\">Troubleshooting</uri> lists common pitfalls."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):83
+msgid "Power Budget For Each Component"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:link):87
+msgid "/images/energy-budget.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:short):87
+msgid "Which component consumes how much energy?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:caption):87
+msgid "Power budget for each component"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):89
+msgid "Nearly every component can operate in different states - off, sleep, idle, active to name a few - consuming a different amount of energy. Major parts are consumed by the LCD display, CPU, chipset and hard drives. Often one is able to activate OS-independent Power Management in the BIOS, but an intelligent setup in the operating system adapting to different situations can achieve much more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):102
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):106
+msgid "Before discussing the details of making individual devices Power Management aware, make sure certain requirements are met. After controlling BIOS settings, some kernel options want to be enabled - these are in short ACPI, sleep states and CPU frequency scaling. As power saving most of the time comes along with performance loss or increased latency, it should only be enabled when running on batteries. That's where a new runlevel <e>battery</e> comes in handy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):118
+msgid "The BIOS Part"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):121
+msgid "First have a look into your BIOS Power Management settings. The best way is to combine BIOS and operating system policies, but for the moment it's better to disable most of the BIOS part. This makes sure it doesn't interfere with your policies. Don't forget to re-check BIOS settings after you configured everything else."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):132
+msgid "Setting USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):135
+msgid "Please check that the <c>acpi</c> USE flag is set in <path>/etc/make.conf</path>. Other USE flags that might be interesting for your system are <c>apm</c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>, <c>pmu</c>. See <path>/usr/portage/profiles/use*.desc</path> for details. If you forgot to set one of these flags, you can recompile affected packages using the <c>--newuse</c> flag in <c>emerge</c>, see <c>man emerge</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):147
+msgid "Configuring The Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):150
+msgid "ACPI (Advanced Configuration and Power Interface) support in the kernel is still work in progress. Using a recent kernel will make sure you'll get the most out of it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):156
+msgid "There are different kernel sources in Portage. I'd recommend using <c>gentoo-sources</c> or <c>tuxonice-sources</c>. The latter contains patches for TuxOnIce, see the chapter about <uri link=\"#doc_chap7\">sleep states</uri> for more details. When configuring the kernel, activate at least these options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):163
+msgid "Minimum kernel setup for Power Management (Kernel 2.6)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):163
+#, no-wrap
+msgid "\nPower management and ACPI options ---&gt;\n[*] Power Management support\n  [ ] Software Suspend\n\n  ACPI( Advanced Configuration and Power Interface ) Support ---&gt;\n    [ ]   Deprecated /proc/acpi/ files\n    [*]   AC Adapter\n    [*]   Battery\n    &lt;M&gt;   Button\n    &lt;M&gt;   Video\n    [ ]   Generic Hotkey\n    &lt;M&gt;   Fan\n    &lt;M&gt;   Processor\n    &lt;M&gt;     Thermal Zone\n    &lt; &gt;   ASUS/Medion Laptop Extras\n    &lt; &gt;   IBM ThinkPad Laptop Extras\n    &lt; &gt;   Toshiba Laptop Extras\n    (0)   Disable ACPI for systems before Jan 1st this year\n    [ ]   Debug Statements\n    [*]   Power Management Timer Support\n    &lt; &gt;   ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)\n\n  CPU Frequency Scaling ---&gt;\n    [*] CPU Frequency scaling\n    [ ]   Enable CPUfreq debugging\n    &lt; &gt;   CPU frequency translation statistics\n    [ ]     CPU frequency translation statistics details\n          Default CPUFreq governor (userspace)\n    &lt;*&gt;   'performance' governor\n    &lt;*&gt;   'powersave' governor\n    &lt;*&gt;   'ondemand' cpufreq policy governor\n    &lt;*&gt;   'conservative' cpufreq governor\n    &lt;*&gt;   CPU frequency table helpers\n    &lt;M&gt; ACPI Processor P-States driver\n    &lt;*&gt; <i>CPUFreq driver for your processor</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):201
+msgid "Decide yourself whether you want to enable Software Suspend, and Sleep States (see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba laptop, enable the appropriate section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):207
+msgid "The kernel has to know how to enable CPU frequency scaling on your processor. As each type of CPU has a different interface, you've got to choose the right driver for your processor. Be careful here - enabling <c>Intel Pentium 4 clock modulation</c> on a Pentium M system will lead to strange results for example. Consult the kernel documentation if you're unsure which one to take."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):215
+msgid "Compile your kernel, make sure the right modules get loaded at startup and boot into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</c> to get the acpi daemon. This one informs you about events like switching from AC to battery or closing the lid. Make sure the modules are loaded if you didn't compile them into the kernel and start acpid by executing <c>/etc/init.d/acpid start</c>. Run <c>rc-update add acpid default</c> to load it on startup. You'll soon see how to use it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):225
+msgid "Installing acpid"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):225
+#, no-wrap
+msgid "\n# <i>emerge sys-power/acpid</i>\n# <i>/etc/init.d/acpid start</i>\n# <i>rc-update add acpid default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):234
+msgid "Creating A \"battery\" Runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):237
+msgid "The default policy will be to enable Power Management only when needed - running on batteries. To make the switch between AC and battery convenient, create a runlevel <c>battery</c> that holds all the scripts starting and stopping Power Management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):244
+msgid "You can safely skip this section if you don't like the idea of having another runlevel. However, skipping this step will make the rest a bit trickier to set up. The next sections assume a runlevel <c>battery</c> exists."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):250
+msgid "Creating a battery runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):250
+#, no-wrap
+msgid "\n# <i>cd /etc/runlevels</i>\n# <i>cp -a default battery</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):255
+msgid "Finished. Your new runlevel <c>battery</c> contains everything like <c>default</c>, but there is no automatic switch between both yet. Time to change it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):264
+msgid "Reacting On ACPI Events"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):267
+msgid "Typical ACPI events are closing the lid, changing the power source or pressing the sleep button. An important event is changing the power source, which should cause a runlevel switch. A small script will take care of it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):273
+msgid "First you need a script which changes the runlevel to <c>default</c> respectively <c>battery</c> depending on the power source. The script uses the <c>on_ac_power</c> command from <c>sys-power/pm-utils</c> - make sure the package is installed on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):280
+msgid "Installing pm-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):280
+#, no-wrap
+msgid "\n# <i>emerge pm-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):284
+msgid "You are now able to determine the power source by executing <c>on_ac_power &amp;&amp; echo AC available || echo Running on batteries</c> in a shell. The script below is responsible for changing runlevels. Save it as <path>/etc/acpi/actions/pmg_switch_runlevel.sh</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):291
+msgid "/etc/acpi/actions/pmg_switch_runlevel.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):291
+#, no-wrap
+msgid "\n#!/bin/bash\n\n<comment># BEGIN configuration</comment>\nRUNLEVEL_AC=\"default\"\nRUNLEVEL_BATTERY=\"battery\"\n<comment># END configuration</comment>\n\n\nif [ ! -d \"/etc/runlevels/${RUNLEVEL_AC}\" ]\nthen\n    logger \"${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting.\"\n    exit 1\nfi\n\nif [ ! -d \"/etc/runlevels/${RUNLEVEL_BATTERY}\" ]\nthen\n    logger \"${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting.\"\n    exit 1\nfi\n\nif on_ac_power\nthen\n    if [[ \"$(&lt;/var/lib/init.d/softlevel)\" != \"${RUNLEVEL_AC}\" ]]\n    then\n        logger \"Switching to ${RUNLEVEL_AC} runlevel\"\n         /sbin/rc ${RUNLEVEL_AC}\n    fi\nelif [[ \"$(&lt;/var/lib/init.d/softlevel)\" != \"${RUNLEVEL_BATTERY}\" ]]\nthen\n    logger \"Switching to ${RUNLEVEL_BATTERY} runlevel\"\n    /sbin/rc ${RUNLEVEL_BATTERY}\nfi\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):326
+msgid "Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> to make the script executable. The last thing that needs to be done is calling the script whenever the power source changes. That's done by catching ACPI events with the help of <c>acpid</c>. First you need to know which events are generated when the power source changes. The events are called <c>ac_adapter</c> and <c>battery</c> on most laptops, but it might be different on yours."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):336
+msgid "Determining ACPI events for changing the power source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):336
+#, no-wrap
+msgid "\n# <i>tail -f /var/log/messages | grep \"ACPI event\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):340
+msgid "Run the command above and pull the power cable. You should see something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):345
+msgid "Sample output for power source changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):345
+#, no-wrap
+msgid "\n[Tue Sep 20 17:39:06 2005] ACPI event \"ac_adapter AC 00000080 00000000\"\n[Tue Sep 20 17:39:06 2005] ACPI event \"battery BAT0 00000080 00000001\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):350
+msgid "The interesting part is the quoted string after <c>ACPI event</c>. It will be matched by the event line in the files you are going to create below. Don't worry if your system generates multiple events or always the same. As long as any event is generated, runlevel changing will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):357
+msgid "/etc/acpi/events/pmg_ac_adapter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):357
+#, no-wrap
+msgid "\n<comment># replace \"ac_adapter\" below with the event generated on your laptop</comment>\n<comment># For example, ac_adapter.* will match ac_adapter AC 00000080 00000000</comment>\nevent=ac_adapter.*\naction=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):364
+msgid "/etc/acpi/events/pmg_battery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):364
+#, no-wrap
+msgid "\n<comment># replace \"battery\" below with the event generated on your laptop</comment>\n<comment># For example, battery.* will match battery BAT0 00000080 00000001</comment>\nevent=battery.*\naction=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):371
+msgid "Finally acpid has to be restarted to recognize the changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):375
+msgid "Finishing runlevel switching with acpid"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):375
+#, no-wrap
+msgid "\n# <i>/etc/init.d/acpid restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):379
+msgid "Give it a try: Plug AC in and out and watch syslog for the \"Switching to AC mode\" or \"Switching to battery mode\" messages. See the <uri link=\"#doc_chap8\">Troubleshooting section</uri> if the script is not able to detect the power source correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):386
+msgid "Due to the nature of the event mechanism, your laptop will boot into runlevel <c>default</c> regardless of the AC/battery state. This is fine when running from AC, but we'd like to boot into the battery runlevel otherwise. One solution would be to add another entry to the boot loader with the parameter <c>softlevel=battery</c>, but it's likely to forget choosing it. A better way is faking an ACPI event in the end of the boot process and letting <path>pmg_switch_runlevel.sh</path> script decide whether a runlevel change is necessary. Open <path>/etc/conf.d/local.start</path> in your favourite editor and add these lines:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):398
+msgid "Runlevel adjustment at boot time by editing local.start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):398
+#, no-wrap
+msgid "\n<comment># Fake acpi event to switch runlevel if running on batteries</comment>\n/etc/acpi/actions/pmg_switch_runlevel.sh \"battery/battery\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):403
+msgid "Prepared like this you can activate Power Management policies for individual devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):413
+msgid "CPU Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):417
+msgid "Mobile processors can operate at different frequencies. Some allow changing voltage as well. Most of the time your CPU doesn't need to run at full speed and scaling it down will save much energy - often without any performance decrease."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):427
+msgid "Some Technical Terms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):430
+msgid "CPU frequency scaling brings up some technical terms that might be unknown to you. Here's a quick introduction."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):435
+msgid "First of all, the kernel has to be able to change the processor's frequency. The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU. Thus it's important to choose the right one in your kernel. You should already have done it above. Once the kernel knows how to change frequencies, it has to know which frequency it should set. This is done according to the <b>policy</b> which consists of a <b>CPUfreq policy</b> and a <b>governor</b>. A CPUfreq policy are just two numbers which define a range the frequency has to stay between - minimal and maximal frequency. The governor now decides which of the available frequencies in between minimal and maximal frequency to choose. For example, the <b>powersave governor</b> always chooses the lowest frequency available, the <b>performance governor</b> the highest one. The <b>userspace governor</b> makes no decision but chooses whatever the user (or a program in userspace) wants - which means it reads the frequency from <path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):452
+msgid "This doesn't sound like dynamic frequency changes yet and in fact it isn't. Dynamics however can be accomplished with various approaches. For example, the <b>ondemand governor</b> makes its decisions depending on the current CPU load. The same is done by various userland tools like <c>cpudyn</c>, <c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to enable or disable dynamic frequency changes depending on power source."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):464
+msgid "Setting The Frequency"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):467
+msgid "Decreasing CPU speed and voltage has two advantages: On the one hand less energy is consumed, on the other hand there is thermal improvement as your system doesn't get as hot as running on full speed. The main disadvantage is obviously the loss of performance. Decreasing processor speed is a trade off between performance loss and energy saving."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):475
+msgid "Not every laptop supports frequency scaling. If unsure, have a look at the list of supported processors in the <uri link=\"#doc_chap8\">Troubleshooting</uri> section to verify yours is supported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):481
+msgid "It's time to test whether CPU frequency changing works. Let's install another tool: <c>sys-power/cpufrequtils</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):486
+msgid "Checking CPU frequency"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):486
+#, no-wrap
+msgid "\n# <i>emerge cpufrequtils</i>\n# <i>cpufreq-info</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):491
+msgid "Here is an example output:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):495
+msgid "Sample output from cpufreq-info"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):495
+#, no-wrap
+msgid "\ncpufrequtils 0.3: cpufreq-info (C) Dominik Brodowski 2004\nReport errors and bugs to linux@brodo.de, please.\nanalyzing CPU 0:\n  driver: centrino\n  CPUs which need to switch frequency at the same time: 0\n  hardware limits: 600 MHz - 1.40 GHz\n  available frequency steps: 600 MHz, 800 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz\n  available cpufreq governors: conservative, ondemand, powersave, userspace, performance\n  current policy: frequency should be within 924 MHz and 1.40 GHz.\n    The governor \"performance\" may decide which speed to use\n    within this range.\n  current CPU frequency is 1.40 GHz.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):510
+msgid "Now play around with <c>cpufreq-set</c> to make sure frequency switching works. Run <c>cpufreq-set -g ondemand</c> for example to activate the ondemand governor and verify the change with <c>cpufreq-info</c>. If it doesn't work as expected, you might find help in the <uri link=\"#doc_chap8\">Troubleshooting section</uri> in the end of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):518
+msgid "<c>cpufrequtils</c> can operate in an automatic mode (when you use the <b>ondemand</b> governor), you can also switch to the <b>userspace</b> governor if you want to manually set a specific speed. You can also statically set your CPU to its highest or lowest frequency by using the <b>performance</b> and <b>powersave</b> governors, respectively."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):526
+msgid "Changing CPU speeds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):526
+#, no-wrap
+msgid "\n<comment>(Set the highest available frequency)</comment>\n# <i>cpufreq-set -g performance</i>\n<comment>(Set the lowest available frequency)</comment>\n# <i>cpufreq-set -g powersave</i>\n<comment>(Set a specific frequency)</comment>\n# <i>cpufreq-set -g userspace</i>\n# <i>cpufreq-set -f 2.00ghz</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):539
+msgid "Other CPU Speed Utilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):542
+msgid "While <c>cpufrequtils</c> may be the best all-around program, there are some other choices available in Portage. The following table gives a quick overview of available CPU speed utilities. It's roughly separated in three categories <b>kernel</b> for approaches that only need kernel support, <b>daemon</b> for programs that run in the background and <b>graphical</b> for programs that provide a GUI for easy configuration and changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):553
+msgid "Name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):554
+msgid "Category"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):555
+msgid "Switch decision"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):556
+msgid "Kernel governors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):557
+msgid "Further governors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):558
+msgid "Comments"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):561
+msgid "'ondemand' governor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):562 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):576
+msgid "Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):563 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):577 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):592 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):618 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):642
+msgid "CPU load"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):564 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):565 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):578 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):579
+msgid "N.A."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):566
+msgid "Chooses maximal frequency on CPU load and slowly steps down when the CPU is idle. Further tuning through files in <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/</path>. Still requires userland tools (programs, scripts) if governor switching or similar is desired."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):575
+msgid "'conservative' governor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):580
+msgid "Unlike the ondemand governor, conversative doesn't jump to maximum frequency when CPU load is high, but increases the frequency step by step. Further tuning through files in <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/</path>. Still requires userland tools (programs, scripts) if governor switching or similar is desired."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):590
+msgid "http://mnm.uib.es/~gallir/cpudyn/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):590
+msgid "cpudyn"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):591 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):602 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):617 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):630 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):641
+msgid "Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):593
+msgid "Performance, powersave"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):594
+msgid "Dynamic"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):595
+msgid "Also supports disk standby - notice however that <e>laptop mode</e> in most cases will do a better job."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):601
+msgid "http://sourceforge.net/projects/cpufreqd/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):601
+msgid "cpufreqd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):603
+msgid "Battery state, CPU load, temperature, running programs and more"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):604 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):666
+msgid "All available"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):605 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):619 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):632 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):643 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):654 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):655 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):656 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):667
+msgid "None"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):606
+msgid "Sophisticated (but somewhat complicated) setup. Extendible through plugins like sensor monitoring (lm_sensors) or coordinating some NVidia based graphics card memory and core. Cpufreqd is SMP aware and can optionally be controlled manually at runtime."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):615
+msgid "http://www.deater.net/john/powernowd.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):615
+msgid "powernowd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):620
+msgid "Passive, sine, aggressive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):621
+msgid "Supports SMP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):628
+msgid "http://projects.simpledesigns.com.pl/project/ncpufreqd/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):628
+msgid "ncpufreqd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):631
+msgid "Temperature"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):633
+msgid "Powersave, performance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):634
+msgid "Toggles the used governor between performance and powersave depending on system temperature. Very useful on laptops with notorious heat problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):640
+msgid "http://www.goop.org/~jeremy/speedfreq/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):640
+msgid "speedfreq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):644
+msgid "Dynamic, powersave, performance, fixed speed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):645
+msgid "Easy to configure with a nice client/server interface. Requires a 2.6 kernel. Unmaintained, broken and thus removed from Portage. Please switch to cpufreqd if you're still using it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):652
+msgid "http://cpuspeedy.sourceforge.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):652
+msgid "gtk-cpuspeedy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):653 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):664
+msgid "Graphical"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):657
+msgid "Gnome application, a graphical tool to set CPU frequency manually. It does not offer any automation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):663
+msgid "klaptopdaemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):665
+msgid "Battery state"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):668
+msgid "KDE only, 'ondemand' governor required for dynamic frequency scaling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):674
+msgid "While adjusting the frequency to the current load looks simple at a first glance, it's not such a trivial task. A bad algorithm can cause switching between two frequencies all the time or wasting energy when setting frequency to an unnecessary high level."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):681
+msgid "Which one to choose? If you have no idea about it, try <c>cpufreqd</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):685
+msgid "Installing cpufreqd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):685
+#, no-wrap
+msgid "\n# <i>emerge cpufreqd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):689
+msgid "<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</path>. The default one that ships with cpufreqd may look a bit confusing. I recommend replacing it with the one from former Gentoo developer Henrik Brix Andersen (see below). Please notice that you need cpufreqd-2.0.0 or later. Earlier versions have a different syntax for the config file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):697
+msgid "/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):697
+#, no-wrap
+msgid "\n[General]\npidfile=/var/run/cpufreqd.pid\npoll_interval=3\nenable_plugins=acpi_ac, acpi_battery\nenable_remote=1\nremote_group=wheel\nverbosity=5\n[/General]\n\n[Profile]\nname=ondemand\nminfreq=0%\nmaxfreq=100%\npolicy=ondemand\n[/Profile]\n\n[Profile]\nname=conservative\nminfreq=0%\nmaxfreq=100%\npolicy=conservative\n[/Profile]\n\n[Profile]\nname=powersave\nminfreq=0%\nmaxfreq=100%\npolicy=powersave\n[/Profile]\n\n[Profile]\nname=performance\nminfreq=0%\nmaxfreq=100%\npolicy=performance\n[/Profile]\n\n[Rule]\nname=battery\nac=off\nprofile=conservative\n[/Rule]\n\n[Rule]\nname=battery_low\nac=off\nbattery_interval=0-10\nprofile=powersave\n[/Rule]\n\n[Rule]\nname=ac\nac=on\nprofile=ondemand\n[/Rule]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):755
+msgid "Now you can start the cpufreqd daemon. Add it to the <c>default</c> and <c>battery</c> runlevel as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):760
+msgid "Starting cpufreqd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):760
+#, no-wrap
+msgid "\n# <i>rc-update add cpufreqd default battery</i>\n# <i>/etc/init.d/cpufreqd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):765
+msgid "Sometimes it can be desirable to select another policy than the daemon chooses, for example when battery power is low, but you know that AC will be available soon. In that case you can turn on cpufreqd's manual mode with <c>cpufreqd-set manual</c> and select one of your configured policies (as listed by <c>cpufreqd-get</c>). You can leave manual mode by executing <c>cpufreqd-set dynamic</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):774
+msgid "Do not run more than one of the above programs at the same time. It may cause confusion like switching between two frequencies all the time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):782
+msgid "Verifying the result"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):785
+msgid "The last thing to check is that your new policies do a good job. An easy way to do so is monitoring CPU speed while working with your laptop:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):790
+msgid "Monitoring CPU speed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):790
+#, no-wrap
+msgid "\n# <i>watch grep \\\"cpu MHz\\\" /proc/cpuinfo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):794
+msgid "If <path>/proc/cpuinfo</path> doesn't get updated (see <uri link=\"#doc_chap8\">Troubleshooting</uri>), monitor the CPU frequency with <c>sys-apps/x86info</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):800
+msgid "Alternative CPU speed monitoring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):800
+#, no-wrap
+msgid "\n# <i>watch x86info -mhz</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):804
+msgid "Depending on your setup, CPU speed should increase on heavy load, decrease on no activity or just stay at the same level. When using <c>cpufreqd</c> and verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get additional information about what's happening reported to <c>syslog</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):816
+msgid "LCD Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):820
+msgid "As you can see in <uri link=\"#doc_chap1_fig1\">figure 1.1</uri>, the LCD display consumes the biggest part of energy (might not be the case for non-mobile CPU's). Thus it's quite important not only to shut the display off when not needed, but also to reduce it's backlight if possible. Most laptops offer the possibility to control the backlight dimming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):831
+msgid "Standby settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):834
+msgid "The first thing to check is the standby/suspend/off timings of the display. As this depends heavily on your windowmanager, I'll let you figure it out yourself. Just two common places: Blanking the terminal can be done with <c>setterm -blank &lt;number-of-minutesM&gt;</c>, <c>setterm -powersave on</c> and <c>setterm -powerdown &lt;number-of-minutesM&gt;</c>. For X.org, modify <path>/etc/X11/xorg.conf</path> similar to this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):843
+msgid "LCD suspend settings in X.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):843
+#, no-wrap
+msgid "\nSection \"ServerFlags\"\n  Option  \"blank time\"  \"5\"  <comment># Blank the screen after 5 minutes (Fake)</comment>\n  Option  \"standby time\"  \"10\"  <comment># Turn off screen after 10 minutes (DPMS)</comment>\n  Option  \"suspend time\"  \"20\"  <comment># Full suspend after 20 minutes</comment>\n  Option  \"off time\"  \"30\"  <comment># Turn off after half an hour</comment>\n  [...]\nEndSection\n\n[...]\n\nSection \"Monitor\"\n  Identifier  [...]\n  Option  \"DPMS\"\n  [...]\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):864
+msgid "Backlight dimming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):867
+msgid "Probably more important is the backlight dimming. If you have access to the dimming settings via a tool, write a small script that dims the backlight in battery mode and place it in your <c>battery</c> runlevel. The following script should work on most IBM Thinkpads and Toshiba laptops. You've got to enable the appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops, install <c>sys-power/acpitool</c> and skip configuration of <c>thinkpad_acpi</c> (formerly called <c>ibm_acpi</c>) as described below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):877
+msgid "Support for setting brightness is marked experimental in thinkpad_acpi. It accesses hardware directly and may cause severe harm to your system. Please read the <uri link=\"http://ibm-acpi.sourceforge.net/\">thinkpad_acpi website</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):884
+msgid "To be able to set the brightness level, the thinkpad_acpi module has to be loaded with the experimental parameter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):889
+msgid "automatically loading the thinkpad_acpi module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):889
+#, no-wrap
+msgid "\n<comment>(Please read the warnings above before doing this!)</comment>\n# <i>echo \"options thinkpad_acpi experimental=1\" &gt;&gt; /etc/modprobe.d/thinkpad_acpi</i>\n# <i>update-modules</i>\n# <i>echo thinkpad_acpi &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n# <i>modprobe thinkpad_acpi</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):897
+msgid "This should work without error messages and a file <path>/proc/acpi/ibm/brightness</path> should be created after loading the module. An init script will take care of choosing the brightness according to the power source."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):904
+msgid "/etc/conf.d/lcd-brightness"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):904
+#, no-wrap
+msgid "\n<comment># See /proc/acpi/ibm/brightness for available values</comment>\n<comment># Please read /usr/src/linux/Documentation/thinkpad-acpi.txt</comment>\n\n<comment># brightness level in ac mode. Default is 7.</comment>\nBRIGHTNESS_AC=7\n\n<comment># brightness level in battery mode. Default is 4.</comment>\nBRIGHTNESS_BATTERY=4\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):915
+msgid "/etc/init.d/lcd-brightness"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):915
+#, no-wrap
+msgid "\n#!/sbin/runscript\n\nset_brightness() {\n    if on_ac_power\n    then\n        LEVEL=${BRIGHTNESS_AC:-7}\n    else\n        LEVEL=${BRIGHTNESS_BATTERY:-4}\n    fi\n\n    if [ -f /proc/acpi/ibm/brightness ]\n    then\n        ebegin \"Setting LCD brightness\"\n        echo \"level ${LEVEL}\" &gt; /proc/acpi/ibm/brightness\n        eend $?\n    elif [[ -e /usr/bin/acpitool &amp;&amp; -n $(acpitool -T | grep \"LCD brightness\") ]]\n    then\n        ebegin \"Setting LCD brightness\"\n        acpitool -l $LEVEL &gt;/dev/null || ewarn \"Unable to set lcd brightness\"\n        eend $?\n    else\n        ewarn \"Setting LCD brightness is not supported.\"\n        ewarn \"For IBM Thinkpads, check that thinkpad_acpi is loaded into the kernel\"\n        ewarn \"For Toshiba laptops, you've got to install sys-power/acpitool\"\n    fi\n}\n\nstart() {\n    set_brightness\n}\n\nstop () {\n    set_brightness\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):952
+msgid "When done, make sure brightness is adjusted automatically by adding it to the battery runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):957
+msgid "Enabling automatic brightness adjustment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):957
+#, no-wrap
+msgid "\n# <i>chmod +x /etc/init.d/lcd-brightness</i>\n# <i>rc-update add lcd-brightness battery</i>\n# <i>rc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):968
+msgid "Disk Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):972
+msgid "Hard disks consume less energy in sleep mode. Therefore it makes sense to activate power saving features whenever the hard disk is not used for a certain amount of time. I'll show you two alternative possibilities to do it. First, laptop-mode will save most energy due to several measures which prevent or at least delay write accesses. The drawback is that due to the delayed write accesses a power outage or kernel crash will be more dangerous for data loss. If you don't like this, you have to make sure that there are no processes which write to your hard disk frequently. Afterwards you can enable power saving features of your hard disk with <c>hdparm</c> as the second alternative."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):987
+msgid "Increasing idle time - laptop-mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):990
+msgid "Recent 2.6 kernels include the so-called <c>laptop-mode</c>. When activated, dirty buffers are written to disk on read calls or after 10 minutes (instead of 30 seconds). This minimizes the time the hard disk needs to be spun up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):996
+msgid "Automated start of laptop-mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):996
+#, no-wrap
+msgid "\n# <i>emerge laptop-mode-tools</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1000
+msgid "<c>laptop-mode-tools</c> has its configuration file in <path>/etc/laptop-mode/laptop-mode.conf</path>. Adjust it the way you like it, it's well commented. Run <c>rc-update add laptop_mode battery</c> to start it automatically."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1007
+msgid "Recent versions (1.11 and later) of laptop-mode-tools include a new tool <c>lm-profiler</c>. It will monitor your system's disk usage and running network services and suggests to disable unneeded ones. You can either disable them through laptop-mode-tools builtin runlevel support (which will be reverted by Gentoo's <c>/sbin/rc</c>) or use your <c>default</c>/<c>battery</c> runlevels (recommended)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1016
+msgid "Sample output from running lm-profiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1016
+#, no-wrap
+msgid "\n# <i>lm-profiler</i>\nProfiling session started.\nTime remaining: 600 seconds\n[4296896.602000] amarokapp\nTime remaining: 599 seconds\n[4296897.714000] sort\n[4296897.970000] mv\nTime remaining: 598 seconds\nTime remaining: 597 seconds\n[4296900.482000] reiserfs/0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1029
+msgid "After profiling your system for ten minutes, lm-profiler will present a list of services which might have caused disk accesses during that time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1034
+msgid "lm-profiler suggests to disable some services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1034
+#, no-wrap
+msgid "\nProgram:     \"atd\"\nReason:      standard recommendation (program may not be running)\nInit script: /etc/init.d/atd (GUESSED)\n\nDo you want to disable this service in battery mode? [y/N]: <i>n</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1042
+msgid "To disable atd as suggested in the example above, you would run <c>rc-update del atd battery</c>. Be careful not to disable services that are needed for your system to run properly - <c>lm-profiler</c> is likely to generate some false positives. Do not disable a service if you are unsure whether it's needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1053
+msgid "Limiting Write Accesses"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1056
+msgid "If you don't want to use laptop-mode, you must take special care to disable services that write to your disk frequently - <c>syslogd</c> is a good candidate, for example. You probably don't want to shut it down completely, but it's possible to modify the config file so that \"unnecessary\" things don't get logged and thus don't create disk traffic. <c>Cups</c> writes to disk periodically, so consider shutting it down and only enable it manually when needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1066
+msgid "Disabling cups in battery mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1066
+#, no-wrap
+msgid "\n# <i>rc-update del cupsd battery</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1070
+msgid "You can also use <c>lm-profiler</c> from laptop-mode-tools (see above) to find services to disable. Once you eliminated all of them, go on with configuring hdparm."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1079
+msgid "hdparm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1082
+msgid "The second possibility is using <c>hdparm</c>. Skip this if you are using laptop-mode. Otherwise, edit <path>/etc/conf.d/hdparm</path> and add the following values to your drive entries. This example assumes your hard drive is called <b>hda</b>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1089
+msgid "Using /etc/conf.d/hdparm for disk standby"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1089
+#, no-wrap
+msgid "\nhda_args=\"-q -S12\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1093
+msgid "This will activate power management for your hard drive. If you ever want to deactivate power management, you can edit <path>/etc/conf.d/hdparm</path> and change the values to <c>-q -S0</c>, or just run <c>hdparm -q -S0 /dev/hda</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1099
+msgid "See <c>man hdparm</c> for the options. Though you can always start <c>hdparm</c> manually when you are on battery power by running <c>/etc/init.d/hdparm start</c>, it's much easier to automate its startup and shutdown. To do so, add <c>hdparm</c> to the battery runlevel so that it will automatically enable power management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1107
+msgid "Automate disk standby settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1107
+#, no-wrap
+msgid "\n# <i>rc-update add hdparm battery</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):1111
+msgid "Be careful with sleep/spin down settings of your hard drive. Setting it to small values might wear out your drive and lose warranty."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1119
+msgid "Other tricks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1122
+msgid "Another possibility is to deactivate swap in battery mode. Before writing a swapon/swapoff switcher, make sure there is enough RAM and swap isn't used heavily, otherwise you'll be in big problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1128
+msgid "If you don't want to use laptop-mode, it's still possible to minimize disk access by mounting certain directories as <c>tmpfs</c> - write accesses are not stored on a disk, but in main memory and get lost with unmounting. Often it's useful to mount <path>/tmp</path> like this - you don't have to pay special attention as it gets cleared on every reboot regardless whether it was mounted on disk or in RAM. Just make sure you have enough RAM and no program (like a download client or compress utility) needs extraordinary much space in <path>/tmp</path>. To activate this, enable tmpfs support in your kernel and add a line to <path>/etc/fstab</path> like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1140
+msgid "Editing /etc/fstab to make /tmp even more volatile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1140
+#, no-wrap
+msgid "\nnone  /tmp  tmpfs  size=32m  0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1144
+msgid "Pay attention to the size parameter and modify it for your system. If you're unsure, don't try this at all, it can become a performance bottleneck easily. In case you want to mount <path>/var/log</path> like this, make sure to merge the log files to disk before unmounting. They are essential. Don't attempt to mount <path>/var/tmp</path> like this. Portage uses it for compiling..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1157
+msgid "Power Management For Other Devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1159
+msgid "Graphics Cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1162
+msgid "In case you own an ATI graphics card supporting PowerPlay (dynamic clock scaling for the graphics processing unit GPU), you can activate this feature in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the <c>DynamicClocks</c> option in the Device section. Please notice that this feature will lead to crashes on some systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1170
+msgid "Enabling ATI PowerPlay support in X.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1170
+#, no-wrap
+msgid "\nSection \"Device\"\n[...]\nOption      \"DynamicClocks\" \"on\"\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1180
+msgid "Wireless Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1183
+msgid "Wireless LAN cards consume quite a bit of energy. Put them in Power Management mode just like your hard drives."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1188
+msgid "This script assumes your wireless interface is called <c>wlan0</c>; replace this with the actual name of your interface."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1193
+msgid "Add the following option to <path>/etc/conf.d/net</path> to automatically enable power management for your wireless card:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1198
+msgid "Automated WLAN Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1198
+#, no-wrap
+msgid "\niwconfig_wlan0=\"power on\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1202
+msgid "See <c>man iwconfig</c> for details and more options like the period between wakeups or timeout settings. If your driver and access point support changing the beacon time, this is a good starting point to save even more energy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1211
+msgid "USB Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1214
+msgid "There are two problems with USB devices regarding energy consumption: First, devices like USB mice, digital cameras or USB sticks consume energy while plugged in. You cannot avoid this (nevertheless remove them in case they're not needed). Second, when there are USB devices plugged in, the USB host controller periodically accesses the bus which in turn prevents the CPU from going into sleep mode. The kernel offers an experimental option to enable suspension of USB devices through driver calls or one of the <path>power/state</path> files in <path>/sys</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1225
+msgid "Enabling USB suspend support in the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1225
+#, no-wrap
+msgid "\nDevice Drivers\n  USB support\n    [*]   Support for Host-side USB\n      [*]   USB suspend/resume (EXPERIMENTAL)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1237
+msgid "Sleep States: sleep, standby, and suspend to disk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1241
+msgid "ACPI defines different sleep states. The more important ones are"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1246
+msgid "S1 aka Standby"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1247
+msgid "S3 aka Suspend to RAM aka Sleep"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1248
+msgid "S4 aka Suspend to Disk aka Hibernate"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1251
+msgid "They can be called whenever the system is not in use, but a shutdown is not wanted due to the long boot time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1259
+msgid "Sleep (S3)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1262
+msgid "The ACPI support for these sleep states is marked experimental for good reason. APM sleep states seem to be more stable, however you can't use APM and ACPI together."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1268 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1362
+msgid "Kernel configuration for the various suspend types"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1268
+#, no-wrap
+msgid "\n  Power Management Options ---&gt;\n    [*]  Power Management support\n    [*]  Suspend to RAM and standby \n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1274
+msgid "Once your kernel is properly configured, you can use the <c>hibernate-script</c> to activate suspend or sleep mode. Let's install that first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1280
+msgid "Installing the hibernate-script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1280
+#, no-wrap
+msgid "\n# <i>emerge hibernate-script</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1284
+msgid "Some configuration has to be done in <path>/etc/hibernate</path>. The default package introduces a few configuration files for each sleep state. Options that are common to all suspend methods are placed in <path>common.conf</path>; make sure this file is properly set up for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1291
+msgid "To configure sleep, edit <path>sysfs-ram.conf</path> in <path>/etc/hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup correctly, but if you need to make further changes to this particular sleep state (or any other sleep state) you should add them to <path>/etc/hibernate/hibernate.conf</path>. The comments and option names will guide you. If you use nfs or samba shares over the network, make sure to shutdown the appropriate init scripts to avoid timeouts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1301
+msgid "For more information on setting up sleep states, read <c>man hibernate.conf</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1306
+msgid "Ready? Now is the last chance to backup any data you want to keep after executing the next command. Notice that you probably have to hit a special key like <c>Fn</c> to resume from sleep."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1312
+msgid "Calling sleep"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1312
+#, no-wrap
+msgid "\n# <i>hibernate-ram</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1316
+msgid "If you're still reading, it seems to work. You can also setup standby (S1) in a similar way by editing <path>sysfs-ram.conf</path> and changing \"UseSysfsPowerState mem\" to \"UseSysfsPowerState standby\". S3 and S4 are the more interesting sleep states due to greater energy savings however."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1326
+msgid "Hibernate (S4)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1329
+msgid "This section introduces hibernation, where a snapshot of the running system is written to disk before powering off. On resume, the snapshot is loaded and you can go on working at exactly the point you called hibernate before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1335
+msgid "Don't exchange non hot-pluggable hardware when suspended. Don't attempt to load a snapshot with a different kernel image than the one it was created with. Shutdown any NFS or samba server/client before hibernating."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1341
+msgid "There are two different implementations for S4. The original one is swsusp, then there is the newer tuxonice (formerly suspend2) with a nicer interface (including fbsplash support). A <uri link=\"http://tuxonice.net/features.html#compare\">feature comparison</uri> is available at the <uri link=\"http://www.tuxonice.net\">tuxonice homepage</uri>. There used to be Suspend-to-Disk (pmdisk), a fork of swsusp, but it has been merged back."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1351
+msgid "TuxOnIce is not included in the mainline kernel yet, therefore you either have to patch your kernel sources with the patches provided by <uri link=\"http://www.tuxonice.net\">tuxonice.net</uri> or use <c>sys-kernel/tuxonice-sources</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1358
+msgid "The kernel part for both swusp and TuxOnIce is as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1362
+#, no-wrap
+msgid "\nPower Management support ---&gt;\n  <comment>(hibernate with swsusp)</comment>\n  [*] Hibernation (aka 'suspend to disk')\n      <comment>(replace /dev/SWAP with your swap partition)</comment>\n      (/dev/SWAP)      Default resume partition\n\n  <comment>(hibernate with TuxOnIce)</comment>\n  Enhanced Hibernation (TuxOnIce)\n    --- Image Storage (you need at least one allocator)\n    [*]    File Allocator\n    [*]    Swap Allocator\n    ---   General Options\n    [*]    Compression support\n    [ ]     Allow Keep Image Mode\n    [*]     Replace swsusp by default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1380
+msgid "The configuration for swsusp is rather easy. If you didn't store the location of your swap partition in the kernel config, you can also pass it as a parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not possible due to a broken image, use the <c>noresume</c> kernel parameter. The <c>hibernate-cleanup</c> init script invalidates swsusp images during the boot process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1389
+msgid "Invalidating swsusp images during the boot process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1389 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1431
+#, no-wrap
+msgid "\n# <i>rc-update add hibernate-cleanup boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1393
+msgid "To activate hibernate with swsusp, use the hibernate script and set <c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/sysfs-disk</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1398
+msgid "Backup your data before doing this. Run <c>sync</c> before executing one of the commands to have cached data written to disk. First try it outside of X, then with X running, but not logged in."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1404
+msgid "If you experience kernel panics due to uhci or similar, try to compile USB support as module and unload the modules before sending your laptop to sleep mode. There are configuration options for this in <path>common.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1410
+msgid "Hibernating with swsusp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1410
+#, no-wrap
+msgid "\n# <i>nano -w /etc/hibernate/common.conf</i>\n<comment>(Make sure you have a backup of your data)</comment>\n# <i>hibernate</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1416
+msgid "The following section discusses the setup of TuxOnIce including fbsplash support for a nice graphical progress bar during suspend and resume."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1421
+msgid "The first part of the configuration is similar to the configuration of swsusp. In case you didn't store the location of your swap partition in the kernel config, you have to pass it as a kernel parameter with the <c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a broken image, append the <c>noresume</c> parameter. Additionally, the <c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the boot process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1431
+msgid "Invalidating TuxOnIce images during the boot process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1435
+msgid "Now edit <path>/etc/hibernate/tuxonice.conf</path>, enable the <c>TuxOnIce</c> options you need. Do not enable the <c>fbsplash</c> options in <c>common.conf</c> just yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1441
+msgid "Hibernating with TuxOnIce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1441
+#, no-wrap
+msgid "\n# <i>nano -w /etc/hibernate/tuxonice.conf</i>\n<comment>(Make sure you have a backup of your data)</comment>\n# <i>hibernate</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1447
+msgid "Please configure <c>fbsplash</c> now if you didn't do already. To enable fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> package is needed. Additionally, you've got to enable the <c>fbsplash</c> USE flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1453
+msgid "Installing tuxonice-userui"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1453
+#, no-wrap
+msgid "\n# <i>echo \"sys-apps/tuxonice-userui fbsplash\" &gt;&gt; /etc/portage/package.use</i>\n<comment>(It may be marked ~arch, so first it must be keyworded)</comment>\n# <i>echo \"sys-apps/tuxonice-userui\" &gt;&gt; /etc/portage/package.keywords</i>\n# <i>emerge tuxonice-userui</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1460
+msgid "The ebuild tells you to make a symlink to the theme you want to use. For example, to use the <c>livecd-2005.1</c> theme, run the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1465
+msgid "Using the livecd-2005.1 theme during hibernation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1465
+#, no-wrap
+msgid "\n# <i>ln -sfn /etc/splash/livecd-2005.1 /etc/splash/tuxonice</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1469
+msgid "If you don't want a black screen in the first part of the resume process, you have to add the <c>tuxoniceui_fbsplash</c> tool to your initrd image. Assuming you created the initrd image with <c>splash_geninitramfs</c> and saved it as <path>/boot/fbsplash-emergence-1024x768</path>, here's how to do that."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1476
+msgid "Adding tuxoniceui_fbsplash to an initrd image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1476
+#, no-wrap
+msgid "\n# <i>mount /boot</i>\n# <i>mkdir ~/initrd.d</i>\n# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>\n# <i>cd ~/initrd.d</i>\n# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>\n# <i>rm fbsplash-emergence-1024x768</i>\n# <i>cp /usr/sbin/tuxoniceui_fbsplash sbin/</i>\n# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 &gt; /boot/fbsplash-tuxonice-emergence-1024x768</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1487
+msgid "Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that your TuxOnIce kernel uses <path>/boot/fbsplash-tuxonice-emergence-1024x768</path> as initrd image. You can now test a dry run to see if everything is setup correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1494
+msgid "Test run for fbsplash hibernation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1494
+#, no-wrap
+msgid "\n# <i>tuxoniceui_fbsplash -t</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1498
+msgid "Afterwards open <path>/etc/hibernate/common.conf</path> and activate the fbsplash options. Execute <c>hibernate</c> and enjoy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1508
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1512
+msgid "<e>Q:</e> I'm trying to change the CPU frequency, but <path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor</path> does not exist."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1518
+msgid "<e>A:</e> Make sure your processor supports CPU frequency scaling and you chose the right CPUFreq driver for your processor. Here is a list of processors that are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-SA1100, ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile K6-3+, AMD mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, Cyrix Media GXm, Intel mobile PIII and Intel mobile PIII-M on certain chipsets, Intel Pentium 4, Intel Xeon, Intel Pentium M (Centrino), National Semiconductors Geode GX, Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, SuperH SH-3, SH-4, several \"PowerBook\" and \"iBook2\" and various processors on some ACPI 2.0-compatible systems (only if \"ACPI Processor Performance States\" are available to the ACPI/BIOS interface)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1531
+msgid "<e>Q:</e> My laptop supports frequency scaling, but <path>/sys/devices/system/cpu/cpu0/cpufreq/</path> is empty."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1536
+msgid "<e>A:</e> Look for ACPI related error messages with <c>dmesg | grep ACPI</c>. Try to update the BIOS, especially if a broken DSDT is reported. You can also try to fix it yourself (which is beyond the scope of this guide)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1542
+msgid "<e>Q:</e> My laptop supports frequency scaling, but according to <path>/proc/cpuinfo</path> the speed never changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1547
+msgid "<e>A:</e> Probably you have activated symmetric multiprocessing support (CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older kernels had a bug causing this. In that case, run <c>emerge x86info</c>, update your kernel as asked and check the current frequency with <c>x86info -mhz</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1554
+msgid "<e>Q:</e> I can change the CPU frequency, but the range is not as wide as in another OS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1559
+msgid "<e>A:</e> You can combine frequency scaling with ACPI throttling to get a lower minimum frequency. Notice that throttling doesn't save much energy and is mainly used for thermal management (keeping your laptop cool and quiet). You can read the current throttling state with <c>cat /proc/acpi/processor/CPU/throttling</c> and change it with <c>echo -n \"0:x\" &gt; /proc/acpi/processor/CPU/limit</c>, where x is one of the Tx states listed in <path>/proc/acpi/processor/CPU/throttling</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1569
+msgid "<e>Q:</e> When configuring the kernel, powersave, performance and userspace governors show up, but that ondemand thing is missing. Where do I get it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1574
+msgid "<e>A:</e> The ondemand governor is only included in recent kernel sources. Try updating them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1579
+msgid "<e>Q:</e> Battery life time seems to be worse than before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1583
+msgid "<e>A:</e> Check your BIOS settings. Maybe you forgot to re-enable some of the settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1588
+msgid "<e>Q:</e> My battery is charged, but KDE reports there would be 0% left and immediately shuts down."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1593
+msgid "<e>A:</e> Check that battery support is compiled into your kernel. If you use it as a module, make sure the module is loaded."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1598
+msgid "<e>Q:</e> My system logger reports things like \"logger: ACPI group battery / action battery is not defined\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1603
+msgid "<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path> script that is shipped with acpid. You can safely ignore it. If you like to get rid of it, you can comment the appropriate line in <path>/etc/acpi/default.sh</path> as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1610
+msgid "Disabling warnings about unknown acpi events"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1610
+#, no-wrap
+msgid "\n        *)      # logger \"ACPI action $action is not defined\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1614
+msgid "<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1618
+msgid "<e>A:</e> This seems to be a kernel bug. Read on <uri link=\"http://bugme.osdl.org/show_bug.cgi?id=1752\">here</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1623
+msgid "<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</path> and now X.org crashes / the screen stays black / my laptop doesn't shutdown properly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1629
+msgid "<e>A:</e> This happens on some systems. You have to disable <c>DynamicClocks</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1634
+msgid "<e>Q:</e> I want to use TuxOnIce, but it tells me my swap partition is too small. Resizing is not an option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1639
+msgid "<e>A:</e> If there is enough free space on your system, you can use the filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it as well. More information can be found in <path>/usr/src/linux/Documentation/power/tuxonice.txt</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1646
+msgid "<e>Q:</e> I just bought a brand new battery, but it only lasts for some minutes! What am I doing wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1651
+msgid "<e>A:</e> First follow your manufacturer's advice on how to charge the battery correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1656
+msgid "<e>Q:</e> The above didn't help. What should I do then?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1660
+msgid "<e>A:</e> Some batteries sold as \"new\" are in fact old ones. Try the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1664
+msgid "Querying battery state"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1664
+#, no-wrap
+msgid "\n$ <i>grep capacity /proc/acpi/battery/BAT0/info</i>\ndesign capacity:     47520 mWh\nlast full capacity:  41830 mWh\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1670
+msgid "If the \"last full capacity\" differs significantly from the design capacity, your battery is probably broken. Try to claim your warranty."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1675
+msgid "<e>Q:</e> My problem is not listed above. Where should I go next?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1679
+msgid "<e>A:</e> Don't fear to contact me, <mail link=\"earthwings@gentoo.org\">Dennis Nienhüser</mail>, directly. The <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri> are a good place to get help as well. If you prefer IRC, try the <c>#gentoo-laptop</c><uri link=\"irc://irc.gentoo.org\">channel</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/prelink-howto.xml.pot b/doc/gettext/prelink-howto.xml.pot
new file mode 100644
index 0000000..d8445ff
--- /dev/null
+++ b/doc/gettext/prelink-howto.xml.pot
@@ -0,0 +1,399 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):6
+msgid "Gentoo Linux Prelink Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):9
+msgid "cretin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail):9
+msgid "Stefan Jones"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):20 ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author):11
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):15
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail):15
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):18
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail):18
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):21
+msgid "erwin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail):21
+msgid "Erwin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(abstract):27
+msgid "This guide tells you how to make use of prelink support in Portage 2.0.46 and later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(version):34
+msgid "1.18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(date):35
+msgid "2010-01-12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):38
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):40
+msgid "What is Prelink and how can it help me?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):43
+msgid "Most common applications make use of shared libraries. These shared libraries need to be loaded into memory at runtime and the various symbol references need to be resolved. For most small programs this dynamic linking is very quick. But for programs written in C++ and that have many library dependencies, the dynamic linking can take a fair amount of time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):51
+msgid "On most systems, libraries are not changed very often and when a program is run, the operations taken to link the program are the same every time. Prelink takes advantage of this by carrying out the linking and storing it in the executable, in effect prelinking it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):58
+msgid "Prelinking can cut the startup times of applications. For example, a typical KDE program's loading time can be cut by as much as 50%. The only maintenance required is re-running prelink every time a library is upgraded for a pre-linked executable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(warn):65
+msgid "Prelink will not work with Hardened Gentoo. This is because both projects try to change the address space mapping of shared libraries. But prelink with the -R option randomises library base addresses, providing some degree of hardened protection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):75
+msgid "Summary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):79
+msgid "Prelinking is done via a program called, surprisingly, <c>prelink</c>. It changes the binary to make it start faster."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):83
+msgid "If an application's dependent libraries change after you have prelinked it, you need to re-prelink the application, otherwise you lose the speed advantage. This is to say, everytime you update a package via portage that updates libraries, they need to be re-prelinked."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):89
+msgid "The change to the binary is fully reversible. <c>prelink</c> has an undo function."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):93
+msgid "Current versions of Portage can handle, via <c>prelink</c>, the changing MD5sums and mtimes of the binaries."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):97
+msgid "You do not need to set <c>FEATURES=\"prelink\"</c> in your <path>make.conf</path> file; Portage will automatically support prelink if it can find the prelink binary."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):109
+msgid "Setting up Prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):111
+msgid "Installing the Programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):114
+msgid "First you need to install the <c>prelink</c> tool. The emerge process automatically verifies that your system can prelink safely."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):119
+msgid "Installing Prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):119
+#, no-wrap
+msgid "\n# <i>emerge prelink</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):123
+msgid "A number of people get errors in emerging prelink because of the failed tests. The tests were put in for safety reasons, prelink's behavior is undefined if you disable them. The emerge errors are usually only dependent on the core packages; binutils, gcc, and glibc. Try re-emerging those packages in that order."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(note):131
+msgid "Tip: If you get an error try compiling and testing <c>prelink</c> yourself (<c>./configure</c> ; <c>make</c> ; <c>make check</c> ). On a failure you can view the *.log files in the testsuite directory. They may provide you with some useful clues."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):138
+msgid "If you have a set of steps that reproduces the emerge error on another system please check <uri link=\"http://bugzilla.gentoo.org\">Bugzilla</uri> and create a bug report if it has not already been reported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):147
+msgid "Preparing your System"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):150
+msgid "Also make sure that you do <e>not</e> have -fPIC set in your CFLAGS/CXXFLAGS. If you do, you will need to rebuild your entire system without."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):158
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):161
+msgid "Running <c>env-update</c> will generate the <path>/etc/prelink.conf</path> file that tells <path>prelink</path> which files to prelink."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):166
+msgid "Running env-update"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):166
+#, no-wrap
+msgid "\n# <i>env-update</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):170
+msgid "Unfortunately you cannot prelink files that were compiled by old versions of binutils. Most of these applications come from pre-compiled, binary only packages which are installed in <path>/opt</path>. Making the following file will tell prelink not to attempt to prelink them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):177
+msgid "/etc/env.d/60prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):177
+#, no-wrap
+msgid "\nPRELINK_PATH_MASK=\"/opt\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(note):181
+msgid "You can add more or less directories to the colon separated list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):190
+msgid "Prelinking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):192
+msgid "Prelink Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):195
+msgid "I use the following command to prelink all the binaries in the directories given by <path>/etc/prelink.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):200
+msgid "Prelinking listed files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):200
+#, no-wrap
+msgid "\n# <i>prelink -amR</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(warn):204
+msgid "It has been observed that if you are low on disk space and you prelink your entire system then there is a possibility that your binaries may be truncated. The result being a b0rked system. Use the <c>file</c> or <c>readelf</c> command to check the state of a binary file. Alternatively, check the amount of free space on your harddrive ahead of time with <c>df -h</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(th):214
+msgid "The options explained:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(th):217
+msgid "-a"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(ti):218
+msgid "\"All\": prelinks all the binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(th):221
+msgid "-m"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(ti):222
+msgid "Conserve the virtual memory space. This is needed if you have a lot of libraries that need to be prelinked."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(th):228
+msgid "-R"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(ti):229
+msgid "Random -- randomize the address ordering, this enhances security against buffer overflows."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(note):236
+msgid "For more options and details see <c>man prelink</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):243
+msgid "Prelink Cron Job"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):246
+msgid "<c>sys-devel/prelink-20060213</c> and later install a cron job in <path>/etc/cron.daily/prelink</path>. To enable it, edit the configuration file <path>/etc/conf.d/prelink</path>. This will run prelink daily in the background, as needed, saving you running the command manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):256
+msgid "Speeding Up KDE After Prelinking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):259
+msgid "KDE's loading time can be greatly reduced after prelinking. If you inform KDE that it has been prelinked it will disable the loading of <c>kdeinit</c> (as it isn't required anymore) which speeds up KDE even more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):265
+msgid "Set <c>KDE_IS_PRELINKED=1</c> in <path>/etc/env.d/*kdepaths*</path> to inform KDE about the prelinking."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):273
+msgid "Removing prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):276
+msgid "If you ever change your mind about prelinking, before you unmerge prelink, you'll first need to remove the prelink cronjob from <path>/etc/cron.daily</path> and <path>/etc/conf.d/prelink</path>. Next, you'll have to remove prelinking from all binaries:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):283
+msgid "Removing prelinking from all binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):283
+#, no-wrap
+msgid "\n# <i>prelink -au</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):287
+msgid "Finally, unmerge the <c>prelink</c> package itself:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):291
+msgid "Unmerging prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):291
+#, no-wrap
+msgid "\n# <i>emerge -aC prelink</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):300
+msgid "Known Problems and Fixes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):302
+msgid "\"Cannot prelink against non-PIC shared library\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):305
+msgid "The cause of this problem is from badly compiled shared libraries that were compiled without the -fPIC gcc option for all their object files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):310
+msgid "Here are the libraries that haven't been fixed or cannot be fixed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):315
+msgid "The libraries in the wine package, including winex. Prelinking wouldn't speed up MS Windows executables anyway."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):319
+msgid "The library in media-video/mjpegtools, <path>/usr/lib/liblavfile-1.6.so.0</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):323
+msgid "Nvidia OpenGl libraries, <path>/usr/lib/opengl/nvidia/lib/libGL.so.*</path>. Due to performance reasons they were compiled without PIC support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):330
+msgid "If your problem library was not listed please report it with, preferably, a patch to add <c>-fPIC</c> to the relevant CFLAGS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):338
+msgid "When I prelink my system some static binaries don't work anymore"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):341
+msgid "Where glibc is concerned, there is no such thing as a 100% static binary. If you statically compile a binary with glibc, it may still depend on other system files. Below is an explanation by Dick Howell,"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):347
+msgid "\"I suppose the idea is that everything will be in the downloaded file, so nothing depends on the local libraries on the target system. Unfortunately with Linux, and I think anything else using GLIBC, this still isn't quite true. There's this \"libnss\" (name service switch, some people seem to call it network security system) which provides functions for accessing various databases for authentication, network information, and other things. It's supposed to make application programs independent of the separately configured actual network environment of the machine. A nice idea, but changes to GLIBC can lead to problems loading it. And you can't statically link \"libnss\", since it is configured for each machine individually. The problem comes, I think, mainly from statically linking other GLIBC libraries, notably \"libpthread\", \"libm\", and \"libc\", from which come incompatible calls to \"libnss\" functions.\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):366
+msgid "Prelink aborts with \"prelink: dso.c:306: fdopen_dso: Assertion `j == k' failed.\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):370
+msgid "This a known problem, kindly diagnosed <uri link=\"http://bugs.gentoo.org/show_bug.cgi?id=13878\">here</uri>. Prelink cannot cope with UPX-compressed executables. As of prelink-20021213 there is no fix except to hide the executables while you are prelinking. See the <uri link=\"#doc_chap2_sect2\">Configuration section</uri> above for an easy way to do this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):382
+msgid "I use grsecurity and it seems that prelinking doesn't work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):385
+msgid "In order to prelink on a system with grsecurity using a randomized mmap() base, it is necessary to turn \"randomized mmap() base\" OFF for <path>/lib/ld-2.3.*.so</path>. This can be done with the <c>chpax</c> utility, but it must be done when the file is not in use (f.i. boot from a rescue CD)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):396
+msgid "Prelink fails with error \"prelink: Can't walk directory tree XXXX: Too many levels of symbolic links\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):402
+msgid "Your symlinks are nested too deeply. This happens when a symlink points to itself. For example, <path>/usr/lib/lib -&gt; lib</path> is the most common. To fix this, you can find the symlink manually or use the utility provided by the <c>symlinks</c> package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):409
+msgid "Fix symlinks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):409
+#, no-wrap
+msgid "\n# <i>emerge symlinks</i>\n# <i>symlinks -drv /</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):414
+msgid "More details can be found at <uri link=\"http://bugs.gentoo.org/show_bug.cgi?id=82117\">Bugzilla</uri> and this <uri link=\"http://forums.gentoo.org/viewtopic-t-458144-highlight-prelink.html\">forum post</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):427
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):431
+msgid "Prelinking can drastically speed up the start up times for a number of large applications. Support is built into Portage. Prelinking is also safe as you can always undo the prelinking for any binary if you come across any problems. Just remember that when you update glibc or other libraries that you prelinked with, you need to rerun <path>prelink</path>! In short good luck!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/printing-howto.xml.pot b/doc/gettext/printing-howto.xml.pot
new file mode 100644
index 0000000..2ecc350
--- /dev/null
+++ b/doc/gettext/printing-howto.xml.pot
@@ -0,0 +1,900 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):6
+msgid "Gentoo Printing Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(mail:link):9
+msgid "swift"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(abstract):15
+msgid "This document covers the installation and maintenance of printers using CUPS and Samba. It covers local installation and networked installations and you'll also find instructions on using shared printers from other operating systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(version):25
+msgid "3.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(date):26
+msgid "2010-03-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):29
+msgid "Printing and Gentoo Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):31
+msgid "Use the Right Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):34
+msgid "Linux has great support for printers; the right tool for the job is called CUPS (<uri link=\"http://www.cups.org\">Common Unix Printing System</uri>). Since the beginning of the project, back in 1999, the installation and maintenance of CUPS has improved dramatically."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):41
+msgid "In this document we will cover how to use CUPS to setup a local or networked printer. We will not go in too much detail since the project has <uri link=\"http://www.cups.org/documentation.php\">great documentation</uri> available for advanced usage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):53
+msgid "Configure your Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):55 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):544 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):768 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):1000
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):58
+msgid "When you want to install a printer on your system you need to know how your printer will be attached to your system. Is it through a local port like LPT or USB, or is it networked? And if it is, does it use the Internet Printing Protocol (IPP) or is it through the Microsoft Windows SMB-CIFS protocol (Microsoft Windows Sharing)?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):66
+msgid "The next few sections explain what minimal kernel configuration you need. Of course, this depends on how your printer is going to be attached to your system, so for your convenience we have separated the instructions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):73
+msgid "#lpt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):73 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):99
+msgid "Locally Attached Printer (LPT)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):74
+msgid "#usb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):74 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):139
+msgid "Locally Attached Printer (USB)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):75
+msgid "#ipp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):75 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):173
+msgid "Remotely Attached Printer (IPP)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):76
+msgid "#smb-cifs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):76 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):186
+msgid "Remotely Attached Printer (SMB-CIFS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):79
+msgid "So navigate to <path>/usr/src/linux</path> and run <c>make menuconfig</c> to enter the kernel configuration. If you used <c>genkernel</c> to configure your kernel, you should still perform these steps just to make sure nothing was missed out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):86
+msgid "In the next configuration examples, we will add the necessary support <e>in</e> the kernel, not as modules. This is not mandatory; if you want you can easily use modular support. Don't forget to load the appropriate modules afterwards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):92
+msgid "Now go to the appropriate section to configure (or check) your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):102
+msgid "The LPT port is generally used to identify the parallel printer port. You need to enable parallel port support first, then PC-style parallel port support (unless you are a SPARC user) after which you enable parallel printer support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):108
+msgid "Parallel Port Printer Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):108
+#, no-wrap
+msgid "\nDevice Drivers --&gt;\n  &lt;*&gt; Parallel port support\n  &lt;*&gt;   PC-style hardware\n\nDevice Drivers --&gt;\n  Character Devices --&gt;\n    &lt;*&gt; Parallel printer support\n       [*]      IEEE 1284 transfer modes)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(note):119
+msgid "Some users might need to enable other options in the <c>Parallel port support</c> section. Check the kernel configuration <c>Help</c> function for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):125 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):159 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):200
+msgid "That's it; quit the kernel configuration and rebuild your kernel. Don't forget to copy the new kernel image to the <path>/boot</path> location (and don't forget to mount <path>/boot</path> if needed) and update your boot loader configuration prior to rebooting your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):132 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):166 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):207
+msgid "Now continue with <uri link=\"#cups\">Installing and Configuring CUPS</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):142
+msgid "To enable USB printing, you just need USB support in your kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):146
+msgid "USB Port Printer Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):146
+#, no-wrap
+msgid "\nDevice Drivers --&gt;\n  USB Support --&gt;\n    &lt;*&gt; Support for Host-side USB\n    <comment>(...)</comment>\n    --- USB Host Controller Drivers\n    <comment>(Select the HCD that your system uses. If you do not know which one\n     to select, run \"lspci -v | grep HCI\" from another terminal)</comment>\n    &lt;*&gt; EHCI HCD (USB 2.0) support <comment>( or )</comment>\n    &lt;*&gt; OHCI HCD support           <comment>( or )</comment>\n    &lt;*&gt; UHCI HCD (most Intel and VIA) support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):176
+msgid "To be able to connect to a remotely attached printer through the Internet Printing Protocol your kernel just needs to have networking support. Assuming your kernel has that already, continue with <uri link=\"#cups\">Installing and Configuring CUPS</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):189
+msgid "Your kernel must support SMB CIFS:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):193
+msgid "SMB-CIFS Printer Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):193
+#, no-wrap
+msgid "\nFile systems --&gt;\n  Network File Systems --&gt;\n    &lt;*&gt; SMB file system support (to mount Windows shares etc.)\n    &lt;*&gt; CIFS support (advanced network file system for Samba, Windows and other CIFS compliant servers)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):216
+msgid "Installing and Configuring CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):218
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):221
+msgid "Installing CUPS with Gentoo is a breeze. CUPS has a few optional features that might interest you. To enable or disable those features, use the USE flags associated with them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(th):229
+msgid "USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(th):230
+msgid "Impact on CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):233
+msgid "dbus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):234
+msgid "Adds support for the <c>dbus</c> system message bus."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):237
+msgid "jpeg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):238
+msgid "Adds support for printing JPEG images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):241
+msgid "nls"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):242
+msgid "Enable National Language Support. With nls in place, CUPS is able to deliver localized feedback so you can hopefully enjoy CUPS in your native language."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):249
+msgid "pam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):250
+msgid "If you need print job authentication through the Pluggable Authentication Modules, this will activate PAM support for CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):256
+msgid "php"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):257
+msgid "Adds support for php scripting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):260
+msgid "png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):261
+msgid "Adds support for printing PNG images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):264
+msgid "ppds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):265
+msgid "Adds support for automatically generated ppd (printing driver) files. See <uri link=\"#installing_best\">Installing the Best Driver</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):271
+msgid "samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):272
+msgid "If you want to be able to share locally attached printers to Windows systems on your network using the SMB-CIFS protocol, or you want to be able to use shared printers from Windows systems, you need SAMBA support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):279
+msgid "slp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):280
+msgid "In a managed environment the printer might be made available as a service to others. With the Service Location Protocol you can easily find and configure a service on your system. Enable this USE flag if your printer is available as a service or should be made available as one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):288
+msgid "ssl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):289
+msgid "If you want remote authentication and/or privacy, you need support for the Secure Socket Layer, allowing for encrypted printing sessions. Support for SSL must be available on all participating systems in your network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):296
+msgid "tiff"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):297
+msgid "Adds support for printing TIFF images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):300
+msgid "X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):301
+msgid "Allows you to use your desktop menu to load the CUPS configuration webpage into your preferred browser."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):308
+msgid "Check the current USE settings. If you want to deviate from your current USE settings for CUPS alone, add the appropriate USE flags to <path>/etc/portage/package.use</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):314
+msgid "USE flag settings for CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):314
+#, no-wrap
+msgid "\n# <i>emerge -pv cups</i>\n[ebuild N     ] net-print/cups-1.2.6  \"X dbus jpeg nls pam png ppds ssl -php -samba -slp -tiff\" 0 kB\n\n<comment>(For instance, to enable SAMBA support for CUPS)</comment>\n# <i>nano -w /etc/portage/package.use</i>\nnet-print/cups samba\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):323
+msgid "If you are happy with the result, have Portage install CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):327
+msgid "Installing CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):327
+#, no-wrap
+msgid "\n# <i>emerge cups</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(impo):331
+msgid "Any users that need to print should be added to the <c>lp</c> group. Add them by running (as root) <c>gpasswd -a username lp</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):336
+msgid "If the printer is attached to your system locally, you need to load CUPS automatically on start-up. Make sure your printer is attached and powered on before you start CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):342
+msgid "Automatically starting CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):342
+#, no-wrap
+msgid "\n# <i>/etc/init.d/cupsd start</i>\n# <i>rc-update add cupsd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):350
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):353
+msgid "The default CUPS server configuration in <path>/etc/cups/cupsd.conf</path> is sufficient for most users. However, several users might need some changes to the CUPS configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):359
+msgid "In the next sections we cover a few changes that are often needed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):364
+msgid "In <uri link=\"#remote_usage\">Remote Printer Access</uri> we allow other systems to use the printer attached to this Linux workstation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):368
+msgid "In <uri link=\"#remote_admin\">CUPS Remote Administration</uri> we grant access to the CUPS administration from remote systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):372
+msgid "In <uri link=\"#windows_pcl\">Enable Support for Windows PCL Drivers</uri> you configure CUPS to support Windows PCL drivers. This is advised if you want Windows systems to be able to use a Samba-shared printer as most Windows drivers are PCL drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):378
+msgid "In <uri link=\"#setup_remote\">Setting Up a Remote Printer</uri> we configure this system to use a printer attached to another system (not Windows share)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):388
+msgid "Remote Printer Access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):391
+msgid "If you want other systems to use your printer through IPP you need to explicitly grant access to the printer in <path>/etc/cups/cupsd.conf</path>. If you want to share your printer using SAMBA, this change is not needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):397
+msgid "Open up <path>/etc/cups/cupsd.conf</path> in your favorite editor and add in an <c>Allow</c> line for the system(s) that should be able to reach to your printer. In the next example, we grant access to the printer from localhost and from any system whose IP address starts with <c>192.168.0</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):404
+msgid "Allowing remote access to the printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):404
+#, no-wrap
+msgid "\n&lt;Location /&gt;\n  Order allow,deny\n  <i>Allow localhost</i>\n  <i>Allow from 192.168.0.*</i>\n&lt;/Location&gt;\n\n<comment>(This broadcasts browsing information to the clients on the network)\n(This is so that they know the printer is available)</comment>\nBrowseAddress 192.168.0.*:631\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):416
+msgid "Also, you will need to specify which port CUPS listens to, so that it will respond to printing requests from other machines on your network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):421
+msgid "Port configuration in /etc/cups/cupsd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):421
+#, no-wrap
+msgid "\nListen *:631\n<comment>(Make sure that localhost is commented out)</comment>\n#Listen localhost:631\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(note):427
+msgid "If you are still using CUPS 1.1 (which is now deprecated), then you will need to use a different syntax for remote printing requests:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):432
+msgid "Deprecated CUPS 1.1 configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):432
+#, no-wrap
+msgid "\nPort 631\n<comment>(Make sure the next two lines are commented out)</comment>\n#Listen 127.0.0.1:631\n#Listen localhost:631\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):442
+msgid "CUPS Remote Administration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):445
+msgid "If you are interested in remote administration, you need to grant access from other systems than just localhost to the CUPS administration. Edit <path>/etc/cups/cupsd.conf</path> and have it explicitly grant access to the systems you want. For instance, to grant access to the system with IP address of 192.168.0.3:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):453
+msgid "Allowing remote access in /etc/cups/cupsd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):453
+#, no-wrap
+msgid "\n&lt;Location /admin&gt;\n<comment>(...)</comment>\n  Encryption Required\n  Order allow,deny\n  <i>Allow localhost</i>\n  <i>Allow 192.168.0.3</i>\n&lt;/Location&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):463
+msgid "Do not forget to restart CUPS after making changes to <path>/etc/cups/cupsd.conf</path> by running <c>/etc/init.d/cupsd restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):471
+msgid "Enable Support for Windows PCL Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):474
+msgid "PCL drivers send raw data to the print server. To enable raw printing on CUPS, you need to edit <path>/etc/cups/mime.types</path> and uncomment the line <c>application/octet-stream</c> if it is not already uncommented. Then you need to edit <path>/etc/cups/mime.convs</path> and do the same, if it is not already uncommented."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):482
+msgid "Enable support for raw printing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):482
+#, no-wrap
+msgid "\n# <i>vim /etc/cups/mime.types</i>\n<comment>(Uncomment the line so that the file contains:)</comment>\napplication/octet-stream\n\n# <i>vim /etc/cups/mime.convs</i>\n<comment>(Uncomment the line so that the file contains:)</comment>\napplication/octet-stream     application/vnd.cups-raw    0    -\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):492
+msgid "Do not forget to restart CUPS after making these changes by running <c>/etc/init.d/cupsd restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):500
+msgid "Setting Up a Remote Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):503
+msgid "If the printers are attached to a remote CUPS-powered server you can easily set up your system to use the remote printer by changing the <path>/etc/cups/client.conf</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):509
+msgid "Assuming the printer is attached to a system called <c>printserver.mydomain</c>, open up <path>/etc/cups/client.conf</path> with your favorite editor and set the <c>ServerName</c> directive:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):515
+msgid "Editing client.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):515
+#, no-wrap
+msgid "\n# <i>vim /etc/cups/client.conf</i>\n\n<comment>(Substitute printserver.mydomain with your print server name)</comment>\nServerName <i>printserver.mydomain</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):522
+msgid "The remote system will have a default printer setting which you will be using. If you want to change the default printer, use <c>lpoptions</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):527
+msgid "Changing the default printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):527
+#, no-wrap
+msgid "\n<comment>(First list the available printers)</comment>\n# <i>lpstat -a</i>\nhpljet5p accepting requests since Jan 01 00:00\nhpdjet510 accepting requests since Jan 01 00:00\n\n<comment>(Set the HP LaserJet 5P as the default printer)</comment>\n# <i>lpoptions -d hpljet5p</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):542
+msgid "Configuring a Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):547
+msgid "If the printer you want to configure is remotely available through a different print server (running CUPS) you do not need to follow these instructions. Instead, read <uri link=\"#setup_remote\">Setting Up a Remote Printer</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):556
+msgid "Detecting the Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):559
+msgid "If you have a USB printer or your parallel port printer was powered on when you booted your Linux system, you might be able to retrieve information from the kernel stating that it has successfully detected your printer. However this is merely an indication and not a requirement."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):566
+msgid "Retrieving kernel information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):566
+#, no-wrap
+msgid "\n<comment>(For a parallel port printer)</comment>\n$ <i>dmesg | grep -i print</i>\nparport0: Printer, Hewlett-Packard HP LaserJet 2100 Series\n\n<comment>(For a USB printer)</comment>\n$ <i>lsusb</i>\n<comment>(...)</comment>\nBus 001 Device 007: ID 03f0:1004 Hewlett-Packard DeskJet 970c/970cse\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):580
+msgid "Installing the Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):583
+msgid "To have the printer installed on your system, fire up your browser and have it point to <uri link=\"http://localhost:631\">http://localhost:631</uri>. You will be greeted by the CUPS web interface from which you can perform all administrative tasks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(note):590
+msgid "If you use an HTTPS connection to CUPS, the first time you access the interface it <e>may</e> take a very long time before the site comes up. This is because the first request triggers the generation of the CUPS SSL certificates which can be a very time-consuming job."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):597
+msgid "Go to <e>Administration</e> and enter your root login and password information at the box. Then, when you have reached the administrative interface, click on <e>Add Printer</e>. You will be greeted by a new screen allowing you to enter the following information:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):605
+msgid "The <e>spooler name</e>, a short but descriptive name used on your system to identify the printer. This name should not contain spaces or any special characters. For instance, for the HP LaserJet 5P you could say <c>hpljet5p</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):611
+msgid "The <e>location</e>, a description where the printer is physically located (for instance in your room, or in the kitchen right next to your dish washer, ...). This is to help maintaining several printers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):616
+msgid "The <e>description</e> in which you should place a full description of the printer. A common use is the full printer name (like \"HP LaserJet 5P\")."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):622
+msgid "The next screen asks you for the device where the printer listens to. You will have the choice of several devices. The next table covers a few possible devices, but the list is not exhaustive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(th):630
+msgid "Device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(th):631
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):634
+msgid "AppSocket/HP JetDirect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):635
+msgid "This special device allows for network printers to be accessible through a HP JetDirect socket. Only specific printers support this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):641
+msgid "Internet Printing Protocol (IPP or HTTP)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):642
+msgid "Use this to reach your remote printer through the IPP protocol either directly (IPP) or through HTTP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):648
+msgid "LPD/LPR Host or Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):649
+msgid "Select this if the printer is remote and attached to a LPD/LPR server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):654
+msgid "Parallel Port #1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):655
+msgid "Select this when the printer is locally attached to your parallel port (LPT). When the printer is automatically detected its name will be appended to the device as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):662
+msgid "USB Printer #1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):663
+msgid "Select this when the printer is locally attached to a USB port. The printer name should automatically be appended to the device name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):670
+msgid "If you are installing a remote printer, you will be asked for the URI to the printer:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):676
+msgid "An LPD printer server requires a <c>lpd://hostname/queue</c> syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):679
+msgid "An HP JetDirect printer requires a <c>socket://hostname</c> syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):682
+msgid "An IPP printer requires a <c>ipp://hostname/printers/printername</c> or <c>http://hostname:631/ipp/queue</c> syntax."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):693
+msgid "Next, select the printer manufacturer in the adjoining screen and the model type and number in the subsequent one. For many printers you will find multiple drivers. You can either select one now or search on <uri link=\"http://www.linuxprinting.org/printer_list.cgi\">LinuxPrinting.org's Printer List</uri> for a good driver. You can change drivers easily later on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):701
+msgid "Once the driver is selected, CUPS will inform you that the printer has been added successfully to the system. You can now go to the printer management page on the administration interface and select <c>Configure Printer</c> to change the printer settings (resolution, page format, ...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):711
+msgid "Testing and Reconfiguring the Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):714
+msgid "To verify if the printer is working correctly, go to the printer administration page, select your printer and click on <c>Print Test Page</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):719
+msgid "If the printer does not seem to work correctly, click on <c>Modify Printer</c> to reconfigure the printer. You will be greeted with the same screens as during the first installation but the defaults will now be your current configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):726
+msgid "If you have no idea why your printer does not function, you might get a clue by looking at <path>/var/log/cups/error_log</path>. In the next example we find out that there is a permission error, probably due to a wrong <c>Allow</c> setting in <path>/etc/cups/cupsd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):733
+msgid "Looking for CUPS errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):733
+#, no-wrap
+msgid "\n# <i>tail /var/log/cups/error_log</i>\n<comment>(...)</comment>\nE [11/Jun/2005:10:23:28 +0200] [Job 102] Unable to get printer status (client-error-forbidden)!\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):742
+msgid "Installing the Best Driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):745
+msgid "Many printer drivers exist; to find out which one has the best performance for your printer, visit the <uri link=\"http://www.linuxprinting.org/printer_list.cgi\">LinuxPrinting Printer List</uri>. Select your brand and type to find out what driver the site recommends. For instance, for the HP LaserJet 5P, the site recommends the <c>ljet4</c> driver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):754
+msgid "Download the PPD file from the site and place it in <path>/usr/share/cups/model</path>, then run <c>/etc/init.d/cupsd restart</c> as root. This will make the driver available through the CUPS web interface. Now reconfigure your printer as described above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):766
+msgid "Using Special Printer Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):771
+msgid "Some printers require specific drivers or provide additional features that are not enabled through the regular configuration process as described above. This chapter will discuss a selection of printers and how they are made to work with Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):778
+msgid "The following printers and/or drivers are covered:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):783
+msgid "#gutenprint"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):783 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):791
+msgid "Gutenprint Driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):784
+msgid "<uri link=\"#hplip\">HPLIP Driver</uri> (deprecates HPOJ and HPIJS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):785
+msgid "#pnm2ppa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):785 ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):865
+msgid "PNM2PPA Driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):794
+msgid "The <uri link=\"http://gutenprint.sourceforge.net\">gutenprint</uri> drivers are high-quality, open source printer drivers for various Canon, Epson, HP, Lexmark, Sony, Olympus and PCL printers supporting CUPS, ghostscript, The Gimp and other applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):801
+msgid "Gentoo's Portage Tree contains an ebuild for the gutenprint drivers. Just use <c>emerge</c> to install them. Note that the ebuild listens to quite a few USE flags (such as <c>cups</c> and <c>ppds</c>). You must have enabled at least these two flags!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):808
+msgid "Installing gutenprint drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):808
+#, no-wrap
+msgid "\n# <i>emerge gutenprint</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):812
+msgid "When the emerge process has finished, the gutenprint drivers will be available through the CUPS web interface."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):820
+msgid "HPLIP Driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):823
+msgid "The <uri link=\"http://hplipopensource.com/hplip-web/index.html\">HPLIP Project</uri> uses the hpcups printer driver. It also includes scanner and fax support and service tools for various multi-purpose peripherals. For printing support, it is recomended to use the new hpcups driver, which you can enable with the <c>hpcups</c> USE flag. The old hpijs driver is still included when you build <c>hplip</c> with the <c>hpijs</c> USE flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):832
+msgid "The default install enables dynamically generated ppd files at runtime. Some old printers may still require static ppd files. If you encounter problems when using <c>hp-setup</c> try enabling the <c>static-ppds</c> USE flag and rebuilding <c>hplip</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):839
+msgid "Installing the hplip drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):839
+#, no-wrap
+msgid "\n# <i>emerge -vp hplip</i>\nThese are the packages that would be merged, in order:\n\nCalculating dependencies... done!\n[ebuild  N    ] net-print/hplip-3.9.12  USE=\"gtk hpcups qt4 -doc -fax -hpijs \n-libnotify -minimal -new-hpcups -parport -policykit -scanner -snmp -static-ppds\n-udev-acl\" 20,871 kB \n\nTotal: 1 package (1 new), Size of downloads: 20,871 kB\n\n# <i>emerge hplip</i>\n<comment>(Make sure your USB printer is plugged into your computer)</comment>\n# <i>hp-setup</i>\n# <i>/etc/init.d/cupsd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):856
+msgid "When the emerge process has finished, the <c>hp-setup</c> tool will attempt to detect and install the printer drivers for your printer on the system. Once finished, your printer will be available in the CUPS configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):868
+msgid "PPA is an HP technology that focuses on sending low-level processing to the system instead of to the printer which makes the printer cheaper but more resource consuming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):874
+msgid "If the <uri link=\"http://www.linuxprinting.org/printer_list.cgi\">LinuxPrinting</uri> site informs you that the <uri link=\"http://pnm2ppa.sourceforge.net/\">pnm2ppa</uri> driver is your best option, you need to install the <c>pnm2ppa</c> filter on your system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):882
+msgid "Installing the pnm2ppa filter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):882
+#, no-wrap
+msgid "\n# <i>emerge pnm2ppa</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):886
+msgid "Once installed, download the PPD file for your printer from the <uri link=\"http://www.linuxprinting.org/printer_list.cgi\">LinuxPrinting</uri> site and put it in <path>/usr/share/cups/model</path>. Next, configure your printer using the steps explained above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):898
+msgid "Printing From and To Microsoft Windows"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(note):902
+msgid "You should read our <uri link=\"/doc/en/quick-samba-howto.xml\">Samba/CUPS Guide</uri> for more detailed information on setting up CUPS with Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):910
+msgid "Configuring a Windows Client for IPP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):913
+msgid "Microsoft Windows supports IPP (Windows 9x and ME users need to <uri link=\"http://support.microsoft.com/default.aspx?scid=kb;en-us;294439\">install</uri> it separately). To install a printer that is attached to your Linux box on Windows, fire up the <c>Add Printer</c> wizard and select <c>Network Printer</c>. When you are asked for the URI, use the <c>http://hostname:631/printers/queue</c> syntax."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):922
+msgid "Make sure that your systems <uri link=\"#remote_usage\">can reach</uri> your printer!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):930
+msgid "Configuring a Windows Client for a Samba Shared Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):933
+msgid "To share the printer on the SMB-CIFS network, you must have SAMBA installed and configured correctly. How to do this is beyond the scope of this document, but we will quickly deal with the configuration of SAMBA for shared printers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):939
+msgid "Open <path>/etc/samba/smb.conf</path> with your favorite editor and add a <c>[printers]</c> section to it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):944
+msgid "Adding a [printers] section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):944
+#, no-wrap
+msgid "\n[printers]\n  comment      = All printers\n  path         = /var/spool/samba\n  browseable   = no\n  guest ok     = no\n  writable     = no\n  printable    = yes\n  public       = yes\n  printer name = hpljet5p\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):956
+msgid "Now navigate to the top of the <path>smb.conf</path> file until you are inside the <c>[global]</c> section. Then locate the <c>printcap name</c> and <c>printing</c> settings and set each of them to <c>cups</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):962
+msgid "Changing the [global] section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):962
+#, no-wrap
+msgid "\n[global]\n  <comment>(...)</comment>\n  printcap name = <i>cups</i>\n  printing      = <i>cups</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):969
+msgid "Make sure you enabled the <uri link=\"#windows_pcl\">Windows PCL drivers</uri> support in CUPS. Then, restart the <c>smb</c> service to have the changes take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):978
+msgid "Configuring a Linux Client for a Windows Print Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):981
+msgid "First of all, make sure that the printer is shared on your Windows system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):985
+msgid "Next, in the CUPS web interface, configure your printer as described previously. You will notice that CUPS has added another driver called <c>Windows Printer via SAMBA</c>. Select it and use the <c>smb://username:password@workgroup/server/printername</c> or <c>smb://server/printername</c> syntax for the URI."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):998
+msgid "Printing-related Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1003
+msgid "Many tools exist that help you configure a printer, use additional printing filters, add features to your printing capabilities, etc. This chapter lists a few of them. The list is not exhaustive and not meant to discuss each tool in great detail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):1013
+msgid "Gtk-LP - A Gtk-powered Printer Configuration Tool"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1016
+msgid "With <uri link=\"http://gtklp.sourceforge.net/index.shtml\">Gtk-LP</uri> you can install, modify and configure your printer from a stand-alone Gtk application. It uses CUPS and provides all standard CUPS capabilities as well. Definitely worth checking out if you dislike the CUPS Web interface or want a stand-alone application for your day-to-day printing routines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1024
+msgid "To install it, emerge <c>gtklp</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):1028
+msgid "Installing Gtk-LP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):1028
+#, no-wrap
+msgid "\n# <i>emerge gtklp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):1037
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):1039
+msgid "Error: Unable to convert file 0 to printable format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1042
+msgid "If you are having printing troubles and <path>/var/log/cups/error_log</path> shows this message:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):1047
+msgid "Error log"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):1047
+#, no-wrap
+msgid "\nUnable to convert file 0 to printable format\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1051
+msgid "You need to re-emerge <c>ghostscript-gpl</c> with the <c>cups</c> USE flag. You can either add <c>cups</c> to your USE flags in <path>/etc/make.conf</path>, or you can enable it only for <c>ghostscript-gpl</c> as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):1057
+msgid "Adding cups to ghostscript-gpl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):1057
+#, no-wrap
+msgid "\n# <i>echo \"app-text/ghostscript-gpl cups\" &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1061
+msgid "Then emerge <c>ghostscript-gpl</c>. When it has finished compiling, be sure to restart <c>cupsd</c> afterward:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):1066
+msgid "Restarting cupsd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):1066
+#, no-wrap
+msgid "\n# <i>/etc/init.d/cupsd restart</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/qmail-howto.xml.pot b/doc/gettext/qmail-howto.xml.pot
new file mode 100644
index 0000000..8de5bc8
--- /dev/null
+++ b/doc/gettext/qmail-howto.xml.pot
@@ -0,0 +1,493 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(guide:link):5
+msgid "/doc/en/qmail-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):7
+msgid "netqmail/vpopmail Virtual Mail Hosting System Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(mail:link):10
+msgid "vapier@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(mail):10
+msgid "Mike Frysinger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(abstract):13
+msgid "This document details how to create a mail hosting system based upon netqmail, vpopmail, courier-imap, mysql, and horde's imp."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(version):20
+msgid "1.15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(date):21
+msgid "2007-10-11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):28
+msgid "Whether you're providing e-mail for just system daemons, a single server, a domain, or for many virtual domains, netqmail can easily be setup to handle your needs. This guide will help you setup netqmail for all of these scenarios with a focus on remote access and encrypted communications the whole way through."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):35
+msgid "Specifically, the packages this guide will help you with are netqmail, courier-imap, vpopmail, and horde/imp. These core packages will also bring in daemontools, ucspi-tcp, mysql, apache, and mod_php. netqmail provides the core mta functions, courier-imap provides remote retrieval services, vpopmail provides virtual domain management, and horde/imp provides webmail access."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):43
+msgid "Before emerging anything, you will need the following USE variables enabled. If you've already emerged any of these packages, you may have to re-emerge them. <c>USE=\"maildir ssl imap mysql\"</c>. Additionally, if you want to use horde/imp for your webmail then you will need <c>USE=\"nls\"</c> before emerging mod_php."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(note):51
+msgid "This guide is written in steps. If at anytime you feel your setup is 'complete', you do not need to continue."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):56
+msgid "The last step of course is to commit yourself to the netqmail system. There are many other packages with which you could build your e-mail system. Now is the time to research and decide that netqmail is for you. We have another <uri link=\"virt-mail-howto.xml\">lovely guide</uri> centered around <uri link=\"http://www.postfix.org/\">Postfix</uri>, or you could look into <uri link=\"http://www.exim.org/\">exim</uri>. It's up to you to choose the best solution for yourself; it is up to us to show you how to use netqmail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):71
+msgid "netqmail (talking to myself)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):75
+msgid "Emerge netqmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):75
+#, no-wrap
+msgid "\n# <i>emerge mail-mta/netqmail</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):79
+msgid "This guide is designed around netqmail-1.05-r4 or later. Will it work with earlier versions? Maybe. Should you upgrade? Yes, if you want to be sure this guide will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(warn):85
+msgid "If you get a message like <c>the virtual/mta package conflicts with another package</c> then you need to make sure to unmerge the other MTA on your system. To figure out what package that is, just run <c>emerge netqmail -p</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):91
+msgid "Emerging netqmail will also emerge ucspi-tcp and daemontools. You can read up on <uri link=\"http://cr.yp.to/ucspi-tcp.html\">ucspi-tcp</uri> and on <uri link=\"http://cr.yp.to/daemontools.html\">daemontools</uri> if you like. Basically, daemontools is responsible for managing netqmail as a service while ucspi-tcp is responsible for managing the incoming TCP connections to the netqmail service."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):100
+msgid "First we have a few post-install configuration steps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):104
+msgid "Out-of-the-box setup for netqmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):104
+#, no-wrap
+msgid "\n<comment>(Customize to fit your personal information)</comment>\n# <i>nano /var/qmail/control/servercert.cnf</i>\n# <i>emerge --config netqmail</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):110
+msgid "The design of netqmail has been completely around the focus of security. To this end, e-mail is never sent to the user 'root'. So now you have to select a user on your machine to receive mail that would normally be destined for 'root'. From now on in this guide, I will refer to that user as I have it in my setup, 'vapier'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):118
+msgid "Setting up non-root account for mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):118
+#, no-wrap
+msgid "\n# <i>cd /var/qmail/alias</i>\n# <i>echo vapier &gt; .qmail-root</i>\n# <i>echo vapier &gt; .qmail-postmaster</i>\n# <i>echo vapier &gt; .qmail-mailer-daemon</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):125
+msgid "Now we want to get the netqmail delivery service up and running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):129
+msgid "Start netqmail delivery service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):129
+#, no-wrap
+msgid "\n# <i>rc-update add svscan default</i>\n# <i>/etc/init.d/svscan start</i>\n# <i>cd /service</i>\n# <i>ln -s /var/qmail/supervise/qmail-send qmail-send</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):136
+msgid "We want to make sure netqmail is working correctly, so here's a quick test."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):140
+msgid "Test delivery service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):140
+#, no-wrap
+msgid "\n# <i>ssh vapier@localhost</i>\n# <i>maildirmake .maildir</i>\n# <i>qmail-inject root &lt;&lt; EOF\ntest root e-mail!\nEOF</i>\n# <i>qmail-inject postmaster &lt;&lt; EOF\ntest postmaster e-mail!\nEOF</i>\n# <i>qmail-inject vapier &lt;&lt; EOF\ntest vapier e-mail!\nEOF</i>\n# <i>mutt</i>\n<comment>(You should now have 3 e-mails in your inbox)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):156
+msgid "And that's all! Now you have a mail system that will handle mail for your local machine and the system daemons/users who utilize it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(warn):161
+msgid "If you don't receive any mail or you see weird errors in the log files (check <path>/var/log/qmail/</path>) involving 'localhost.localhost', then that means your domain/dns information is not setup properly. By default, netqmail utilizes the output of <c>hostname --fqdn</c>. If, on your machine, this returns 'localhost', then check your <path>/etc/conf.d/hostname</path>, <path>/etc/hosts</path>, and your dns to make sure everything is correct. Once you have, edit the configuration files in <path>/var/qmail/control/</path>. Use the example setups that follow if you need some more help."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):172
+msgid "Example /var/qmail/control/ files for a 2nd level domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):172
+#, no-wrap
+msgid "\n# <i>hostname --fqdn</i>\nwh0rd.org\n# <i>cat me</i>\nwh0rd.org\n# <i>cat defaultdomain</i>\nwh0rd.org\n# <i>cat plusdomain</i>\nwh0rd.org\n# <i>cat locals</i>\nwh0rd.org\n# <i>cat rcpthosts</i>\nwh0rd.org\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):187
+msgid "Example /var/qmail/control/ files for a 3rd level domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):187
+#, no-wrap
+msgid "\n# <i>hostname --fqdn</i>\nmail.wh0rd.org\n# <i>cat me</i>\nmail.wh0rd.org\n# <i>cat defaultdomain</i>\nwh0rd.org\n# <i>cat plusdomain</i>\nwh0rd.org\n# <i>cat locals</i>\nmail.wh0rd.org\n# <i>cat rcpthosts</i>\nmail.wh0rd.org\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):207
+msgid "vpopmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):211
+msgid "Emerge vpopmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):211
+#, no-wrap
+msgid "\n# <i>emerge vpopmail</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):215
+msgid "This guide is designed around vpopmail-5.4.6 or later. Will it work with earlier versions? Maybe. Should you upgrade? Yes, if you want to be sure this guide will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):221
+msgid "vpopmail takes a little bit more effort to setup than the previous packages. Since vpopmail runs off of mysql, we'll have to make sure that it's up and running first. Then we can setup the vpopmail database and move on. Before you do this step, you should make sure you've already emerged and setup mysql properly. Note that the password I will use for the vpopmail database is 'vpoppw', you however should pick a different one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):230
+msgid "Setting up vpopmail in mysql"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):230
+#, no-wrap
+msgid "\n# <i>rc-update add mysql default</i>\n<comment>If you just emerged mysql for the first time, make sure you run\nthe <i>ebuild &lt;mysql.ebuild&gt; config</i> command and follow the\ndirections before starting the mysql server.</comment>\n# <i>/etc/init.d/mysql start</i>\n# <i>nano /etc/vpopmail.conf</i>\n<comment>(Change the password from 'secret' to 'vpoppw')</comment>\n# <i>mysql -p &lt;&lt; EOF\ncreate database vpopmail;\nuse mysql;\ngrant select, insert, update, delete, create, drop on vpopmail.* to vpopmail@localhost identified by 'vpoppw';\nflush privileges;\nEOF</i>\n<comment>(The following steps may or may not be needed, but we run them just to be sure)</comment>\n# <i>chown root:vpopmail /etc/vpopmail.conf</i>\n# <i>chmod 640 /etc/vpopmail.conf</i>\n# <i>chown root:vpopmail /var/vpopmail/bin/vchkpw</i>\n# <i>chmod 4711 /var/vpopmail/bin/vchkpw</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(warn):251
+msgid "If you experience permission problems with mysql/vpopmail, you may want to try restarting mysql. Just run <c>/etc/init.d/mysql restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):256
+msgid "At this point in time, vpopmail is ready to roll. In this guide, we will be providing virtual hosting for the domain 'wh0rd.org'. This means we need to tell vpopmail about this domain we want it to host for us. We'll also quickly add an user account for 'vapier' while we're here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):263
+msgid "Adding a domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):263
+#, no-wrap
+msgid "\n<comment>(You only have to do this if the <i>vadddomain</i> step below results in \"command not found\")</comment>\n# <i>source /etc/profile</i>\n\n<comment>(While debugging vpopmail, you may want to consult the logs)</comment>\n# <i>mysql -u vpopmail -p</i>\nmysql&gt; <i>select * from vpopmail.vlog;</i>\n\n# <i>vadddomain wh0rd.org postpass</i>\n<comment>(Now quickly verify the domain is setup properly)</comment>\n# <i>printf \"postmaster@wh0rd.org\\0postpass\\0blah\\0\" | vchkpw `which id` 3&lt;&amp;0</i>\nuid=89(vpopmail) gid=89(vpopmail) groups=0(root)\n<comment>(If you don't see something similar to above, then permissions somewhere are incorrect)</comment>\n# <i>vadduser vapier@wh0rd.org vappw</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):279
+msgid "Every domain that vpopmail creates comes with a 'postmaster' account. Here we told vpopmail that the password for the postmaster account is 'postpass'. Before vpopmail can be truly useful, we'll need to be able to receive mail via courier and send mail via netqmail and SMTP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):291
+msgid "Courier POP/IMAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):295
+msgid "Emerge courier-imap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):295
+#, no-wrap
+msgid "\n# <i>emerge net-mail/courier-imap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):299
+msgid "You must emerge courier-imap after vpopmail. That way the authvchkpw module will be built."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):304
+msgid "This guide is designed around net-mail/courier-imap-3.0.7 or later. Will it work with earlier versions? Maybe. Should you upgrade? Yes, if you want to be sure this guide will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):310
+msgid "Now for the common post-install configuration steps. These steps are only needed if you wish to run SSL encrypted communications (which you should !). Otherwise you can skip to the last two steps in the two following code listings, removing the '-ssl' from the init script name each time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):317
+msgid "Out-of-the-box setup for POP3/SSL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):317
+#, no-wrap
+msgid "\n# <i>nano /etc/courier/authlib/authdaemonrc</i>\n<comment>(Set the authmodulelist variable to only contain \"authvchkpw\")</comment>\n# <i>cd /etc/courier-imap</i>\n# <i>nano pop3d.cnf</i>\n<comment>(Edit the [ req_dn ] section)</comment>\n# <i>mkpop3dcert</i>\n# <i>rc-update add courier-pop3d-ssl default</i>\n# <i>/etc/init.d/courier-pop3d-ssl start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):328
+msgid "Out-of-the-box setup for IMAP/SSL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):328
+#, no-wrap
+msgid "\n# <i>cd /etc/courier-imap</i>\n# <i>nano imapd.cnf</i>\n<comment>(Edit the [ req_dn ] section)</comment>\n# <i>mkimapdcert</i>\n# <i>rc-update add courier-imapd-ssl default</i>\n# <i>/etc/init.d/courier-imapd-ssl start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):337
+msgid "Your mail client should now be able to login to the host running courier and retrieve mail for the virtual host. In my case, I am now able to login with the username 'vapier@wh0rd.org' and password 'vappw'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):348
+msgid "netqmail (talking to the world)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):352
+msgid "Let's get SMTP up and running while making sure we don't create another spam hole for people to abuse."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):357
+msgid "Start netqmail SMTP service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):357
+#, no-wrap
+msgid "\n# <i>cd /var/qmail/control/</i>\n# <i>nano conf-smtpd</i>\n<comment>(Uncomment the SMTP-AUTH variables and set QMAIL_SMTP_CHECKPASSWORD to /var/vpopmail/bin/vchkpw)</comment>\n# <i>nano servercert.cnf</i>\n<comment>(Edit the [ req_dn ] section)</comment>\n# <i>mkservercert</i>\n# <i>cd /service</i>\n# <i>ln -s /var/qmail/supervise/qmail-smtpd qmail-smtpd</i>\n# <i>/etc/init.d/svscan restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):369
+msgid "Assuming you haven't tweaked the netqmail control files at all, netqmail will now accept mail for the wh0rd.org virtual domain and for users of the local machine. Furthermore, netqmail will relay mail for anyone who sends via 127.0.0.1 and for anyone who is able to authenticate with vpopmail. When you setup your mail client to send mail, make sure you select options like 'Server requires authentication'. In my case, I set the user as 'vapier@wh0rd.org' and my password as 'vappw'. The last detail is to make sure you tell your mail client to use SSL/TLS for SMTP communication. netqmail will not let you authenticate if the session is not encrypted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):386
+msgid "Horde / IMP Webmail Client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):390
+msgid "Although there are plenty of webmail clients out there (and you're free to use any of them), I prefer the <uri link=\"http://www.horde.org/imp/\">IMP Webmail Client</uri> that is part of the Horde framework. The biggest reason is that Horde can simply provide Webmail access, or you can easily add other components to handle Address Books, Calendars, Tasks, etc... If this hasn't convinced you yet, then perhaps you need to read up on <uri link=\"http://www.horde.org/\">Horde</uri> for yourself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):400
+msgid "On to the good stuff! We need to emerge IMP now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):404
+msgid "Emerge IMP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):404
+#, no-wrap
+msgid "\n# <i>emerge horde-imp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):408
+msgid "This guide is based around horde-2.2.x and horde-imp-3.2.x. The CVS versions (and thus the next major release) will probably have very different configuration settings. Also note that php-5.x will probably break horde-2.x."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):414
+msgid "Horde currently isn't the easiest to setup unless you know exactly what to do. Fortunately for you, I know exactly what to do, thus you will too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):419
+msgid "Out-of-the-box setup for Horde"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):419
+#, no-wrap
+msgid "\n# <i>cd /var/www/localhost/htdocs/horde/config/</i>\n# <i>for f in *.dist ; do mv ${f} ${f/.dist} ; done</i>\n# <i>nano horde.php</i>\n<comment>(Under 'Horde Authentication':)</comment>\n$conf['auth']['driver'] = 'imap';\n$conf['auth']['params']['dsn'] = '{localhost:993/imap/ssl/novalidate-cert}';\n\n<comment>(Under 'Horde Logging':)</comment>\n$conf['log']['name'] = '/var/log/apache2/horde.log';\n\n<comment>(Under 'Problem Reporting':)</comment>\n$conf['problems']['enabled'] = true;\n$conf['problems']['email'] = 'webmaster@wh0rd.org';\n\n# <i>nano registry.php</i>\n<comment>(Under 'Handlers':)</comment>\n$this-&gt;registry['auth']['login'] = 'imp';\n$this-&gt;registry['auth']['logout'] = 'imp';\n\n<comment>(Under 'Application registry':)\nSet the 'status' element of applications['imp'] from 'inactive' to 'active'</comment>\n\n# <i>touch /var/log/apache2/horde.log</i>\n# <i>chown apache:apache /var/log/apache2/horde.log</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(note):446
+msgid "You'll may want to change the 'webmaster' e-mail account to something else. If you wish to use that e-mail address, then remember you'll have to add that user via vpopmail (or see below about qmailadmin)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):452
+msgid "Now we setup IMP real quick."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):456
+msgid "Out-of-the-box setup for IMP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):456
+#, no-wrap
+msgid "\n# <i>cd /var/www/localhost/htdocs/horde/imp/config/</i>\n# <i>for f in *.dist ; do mv ${f} ${f/.dist} ; done</i>\n# <i>nano servers.php</i>\n\n<comment>(Edit the $servers['imap'] array:)</comment>\n$servers['imap'] = array(\n  'name' =&gt; 'wh0rd.org',\n  'server' =&gt; 'localhost',\n  'protocol' =&gt; 'imap/ssl/novalidate-cert',\n  'port' =&gt; 993,\n  'folders' =&gt; '',\n  'namespace' =&gt; 'INBOX.',\n  'maildomain' =&gt; 'wh0rd.org',\n  'smtphost' =&gt; 'localhost',\n  'realm' =&gt; '',\n  'preferred' =&gt; ''\n);\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):476
+msgid "Finally, we bring up apache so we can start using webmail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):480
+msgid "Running apache"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):480
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/apache2</i>\n<comment>(Uncomment APACHE2_OPTS=\"-D SSL -D PHP5\")</comment>\n# <i>rc-update add apache2 default</i>\n# <i>/etc/init.d/apache2 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(warn):487
+msgid "You should really look into forcing https on users of horde. This isn't a trivial issue, but you should look into it for the sake of security."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):492
+msgid "To test out the new IMP setup, launch a web browser and visit <uri>http://localhost/horde/</uri> (or change localhost with the server you're setting this up on). You should see the Horde welcome page where you can login. Again, in my setup, I simply login with 'vapier@wh0rd.org' and 'vappw' as my username and password."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):500
+msgid "At this point, Horde and IMP are all setup. You should, however, go back through the config directories and tweak each to your heart's content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):510
+msgid "Extra packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):512
+msgid "qmailadmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):515
+msgid "The first package I would suggest you look into is <uri link=\"http://www.inter7.com/qmailadmin.html\">qmailadmin</uri>. It's a web based interface for managing virtual domains. Simply <c>emerge net-mail/qmailadmin</c> and then point your webbrowser to <uri>http://localhost/cgi-bin/qmailadmin</uri> in order to use it. Makes life a lot easier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):527
+msgid "qmHandle"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):530
+msgid "If you run into problems with netqmail queues and have a hard time debugging the situation, you may want to look into <uri link=\"http://qmhandle.sourceforge.net/\">qmHandle</uri>. It's a simple perl program which allows you to view and manage the netqmail message queue. Again, all you need to do is <c>emerge net-mail/qmhandle</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):541
+msgid "horde add ons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):544
+msgid "I would highly recommend looking into the many other Horde applications. The <uri link=\"http://www.horde.org/turba/\">Turba</uri>, <uri link=\"http://www.horde.org/kronolith/\">Kronolith</uri>, and <uri link=\"http://www.horde.org/nag/\">Nag</uri> applications complement IMP very well for instance. Their configuration is similar to that of IMP, so you should have no trouble setting them up. Just remember to edit registry.php in the horde config directory so the new applications show up at the bottom of the horde website."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):558
+msgid "ucspi-tcp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):561
+msgid "netqmail utilizes ucspi-tcp to handle the incoming connections for netqmail. If you wish to customize these filtering rules, then see the configuration files in <path>/etc/tcprules.d/</path> (older versions put files in <path>/etc</path>). There you'll find two files for each service, the configuration file (i.e. tcp.qmail-smtp) and the compiled version of this file that ucspi-tcp uses (i.e. tcp.qmail-smtp.cdb). Whenever you update the configuration file, you'll have to rebuild the binary version of it. Just run <c>tcprules tcp.qmail-smtp.cdb tcp.qmail-smtp.tmp &lt; tcp.qmail-smtp</c>. Every time a connection is made to the netqmail service, the compiled rules file is re-read, so there's no need to restart the service."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):577
+msgid "qmail-scanner"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):580
+msgid "If you wish to do content filtering on your mail server (spam and virus), then you'll need to use a different queuing program than the default one. One good program for doing so is <uri link=\"http://qmail-scanner.sourceforge.net/\">qmail-scanner</uri>. Just <c>emerge qmail-scanner</c> and edit the <path>/etc/tcprules.d/tcp.qmail-smtp</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):589
+msgid "The build process of qmail-scanner is quite ugly. In order to support packages, they must already be on your system. This means you will have to emerge SpamAssassin and/or Clam AntiVirus before you emerge qmail-scanner. See the relevant following sections for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):596
+msgid "Changing the queuer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):596
+#, no-wrap
+msgid "\n# <i>cd /etc/tcprules.d/</i>\n# <i>nano tcp.qmail-smtp</i>\n<comment>(Add QMAILQUEUE=\"/var/qmail/bin/qmail-scanner-queue\" to the catchall allow rule)</comment>\n# <i>tcprules tcp.qmail-smtp.cdb tcp.qmail-smtp.tmp &lt; tcp.qmail-smtp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):603
+msgid "See the following sections for setting up spam and virus filtering. You may want to set a few custom options by editing <path>/var/qmail/bin/qmail-scanner-queue.pl</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):612
+msgid "SpamAssassin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):615
+msgid "One of the best Open Source spam filters out there is <uri link=\"http://www.spamassassin.org/\">SpamAssassin</uri>. Just <c>emerge mail-filter/spamassassin</c> to install. The package comes in two flavors, a command line version and a client/server version. For servers that will be handling a small amount of mail, running with the command line version is OK, but for anyone whose server will be handling appreciative loads should utilize the client/server version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):625
+msgid "Out-of-the-box setup for SpamAssassin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):625
+#, no-wrap
+msgid "\n# <i>nano /etc/mail/spamassassin/local.cf</i>\n<comment>(At the bare minimum, add these options:)</comment>\nrequired_hits 6\nskip_rbl_checks 1\n\n# <i>rc-update add spamd default</i>\n# <i>/etc/init.d/spamd start</i>\n# <i>nano /var/qmail/bin/qmail-scanner-queue.pl</i>\n<comment>(Make sure the $spamc_binary variable is set to '/usr/bin/spamc'.)</comment>\n<comment>(If it is set to '', then see the note below.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):638
+msgid "If you did not have SpamAssassin on your system before you emerged qmail-scanner, you will have to re-emerge qmail-scanner now. Its build process is pretty ugly and will only add in features for packages it detects on the system at build time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):645
+msgid "At this point, incoming mail should be sent through qmail-scanner which will run it through SpamAssassin for you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):653
+msgid "Clam AntiVirus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):656
+msgid "Like SpamAssassin, <uri link=\"http://www.clamav.net/\">Clam AntiVirus</uri> comes in two flavors. I'll give you a quick run down on how to quickly setup the client/server version. First, just <c>emerge app-antivirus/clamav</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):662
+msgid "Out-of-the-box setup for Clam AntiVirus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):662
+#, no-wrap
+msgid "\n# <i>nano /etc/conf.d/clamd</i>\n<comment>(Set START_CLAMD=yes)</comment>\n# <i>nano /etc/clamav.conf</i>\n<comment>(Setup stuff the way you want it)</comment>\n# <i>rc-update add clamd default</i>\n# <i>/etc/init.d/clamd start</i>\n# <i>nano /var/qmail/bin/qmail-scanner-queue.pl</i>\n<comment>(Make sure the $clamscan_binary variable is set to '/usr/bin/clamscan'.)</comment>\n<comment>(If it is set to '', then see the note below.)</comment>\n# <i>nano /var/qmail/control/conf-common</i>\n<comment>(If ClamAV reports memory problems try rasing the softlimit)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):676
+msgid "If you did not have Clam AntiVirus on your system before you emerged qmail-scanner, you will have to re-emerge qmail-scanner now. Its build process is pretty ugly and will only add in features for packages it detects on the system at build time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):683
+msgid "At this point, incoming mail should be sent through qmail-scanner which will run it through Clam AntiVirus for you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):693
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):697
+msgid "I have no final notes other than if you experience any troubles with the guide, please contact <mail link=\"vapier@gentoo.org\">me</mail> or file a bug with <uri link=\"http://bugs.gentoo.org/\">Gentoo's Bugtracking Website</uri>. If you have some interesting bits you think would enhance this guide, by all means send it my way for inclusion. I love netqmail and would gladly add stuff that could possibly enhance a user's experience with the mta."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/quick-samba-howto.xml.pot b/doc/gettext/quick-samba-howto.xml.pot
new file mode 100644
index 0000000..1be9636
--- /dev/null
+++ b/doc/gettext/quick-samba-howto.xml.pot
@@ -0,0 +1,817 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(guide:link):5
+msgid "/doc/en/quick-samba-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):7
+msgid "Gentoo Samba3/CUPS HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(author:title):9 ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(author:title):12
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(author):9
+msgid "Andreas \"daff\" Ntaflos"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(mail:link):13
+msgid "joshua@sungentoo.homeunix.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(mail):13
+msgid "Joshua Preston"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(author:title):15
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(mail:link):16
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(mail):16
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(abstract):19
+msgid "Setup, install and configure a Samba server under Gentoo that shares files and printers without the need to install drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(version):28
+msgid "1.26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(date):29
+msgid "2009-01-25"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):32
+msgid "Introduction to this HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):34
+msgid "Purpose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):37
+msgid "This HOWTO is designed to help you move a network from many different clients speaking different languages, to many different machines that speak a common language. The ultimate goal is to help differing architectures and technologies, come together in a productive, happily coexisting environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):44
+msgid "Following the directions outlined in this HOWTO should give you an excellent step towards a peaceful cohabitation between Windows, and virtually all known variations of *nix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):50
+msgid "This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to explore the functionality and power of the Gentoo system, portage and the flexibility of USE flags. Like so many other projects, it was quickly discovered what was missing in the Gentoo realm: there weren't any Samba HOWTOs catered for Gentoo users. These users are more demanding than most; they require performance, flexibility and customization. This does not however imply that this HOWTO was not intended for other distributions; rather that it was designed to work with a highly customized version of Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):61
+msgid "This HOWTO will describe how to share files and printers between Windows PCs and *nix PCs. It will also show you how to mount and manipulate shares."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):66
+msgid "There are a few topics that will be mentioned, but are out of the scope of this HOWTO. These will be noted as they are presented."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):71
+msgid "This HOWTO is based on a compilation and merge of an excellent HOWTO provided in the <uri link=\"http://forums.gentoo.org\">Gentoo forums</uri> by Andreas \"daff\" Ntaflos and the collected knowledge of Joshua Preston. The link to this discussion is provided below for your reference:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri:link):80
+msgid "http://forums.gentoo.org/viewtopic.php?t=110931"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):80
+msgid "HOWTO CUPS+Samba: printing from Windows &amp; Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):88
+msgid "Before you use this guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):91
+msgid "There are a several other guides for setting up CUPS and/or Samba, please read them as well, as they may tell you things left out of this HOWTO (intentional or otherwise). One such document is the very useful and well written <uri link=\"/doc/en/printing-howto.xml\">Gentoo Printing Guide</uri>, as configuration issues and specific printer setup is not discussed here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):102
+msgid "Brief Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):105
+msgid "After presenting the various USE flags, the following list will outline all of the topics covered as they are presented:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):113
+msgid "Install and configure Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):114 ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):121
+msgid "Install and configure CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):115
+msgid "Adding the printer to CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):116
+msgid "Adding the PS drivers for the Windows clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):111
+msgid "On the Samba server: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):122
+msgid "Configuring a default printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):123
+msgid "Mounting a Windows or Samba share"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):119
+msgid "On the Unix clients: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):128
+msgid "Configuring the printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):129
+msgid "Accessing Samba shares"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):126
+msgid "On the Windows Clients: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):137
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):140
+msgid "We will need the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):145
+msgid "net-fs/samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):146
+msgid "net-print/cups (built with the <c>ppds</c> USE flag)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):147
+msgid "net-print/hplip (if you have an HP printer)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):148
+msgid "A kernel of sorts (2.6)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):149
+msgid "A printer (PS or non-PS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):150
+msgid "A working network (home/office/etc) consisting of more than one machine)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):155
+msgid "The main package we use here is <c>net-fs/samba</c>, however, you will need a kernel with CIFS support enabled in order to mount a Samba or Windows share from another computer. CUPS will be emerged if it is not already."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):166
+msgid "Getting acquainted with Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):168
+msgid "The USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):171
+msgid "Before emerging anything, take a look at some of the various USE flags available to Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):176
+msgid "Samba uses the following USE Variables:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):176
+#, no-wrap
+msgid "\nkerberos acl cups ldap pam readline python winbind\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):180
+msgid "Depending on the network topology and the specific requirements of the server, the USE flags outlined below will define what to include or exclude from the emerging of Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(th):189
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):193
+msgid "Include support for Kerberos. The server will need this if it is intended to join an existing domain or Active Directory. See the note below for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):201
+msgid "Enables Access Control Lists. The ACL support in Samba uses a patched ext2/ext3, or SGI's XFS in order to function properly as it extends more detailed access to files or directories; much more so than typical *nix GID/UID schemas."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):210
+msgid "This enables support for the Common Unix Printing System. This provides an interface allowing local CUPS printers to be shared to other systems in the network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):218
+msgid "Enables the Lightweight Directory Access Protocol (LDAP). If Samba is expected to use Active Directory, this option must be used. This would be used in the event Samba needs to login to or provide login to a Domain/Active Directory Server. The kerberos USE flag is needed for proper functioning of this option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):228
+msgid "Include support for pluggable authentication modules (PAM). This provides the ability to authenticate users on the Samba Server, which is required if users have to login to your server. The kerberos USE flag is recommended along with this option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):237
+msgid "Link Samba against libreadline. This is highly recommended and should probably not be disabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):244
+msgid "Python bindings API. Provides an API that will allow Python to interface with Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):251
+msgid "Winbind allows for a unified logon within a Samba environment. It uses a Unix implementation of Windows RPC calls, PAM and the name service switch (supported by the c library) to enable Windows NT domain users to appear and work as Unix users on a Unix system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):260
+msgid "A couple of things worth mentioning about the USE flags and different Samba functions include:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):266
+msgid "ACLs on ext2/3 are implemented through extended attributes (EAs). EA and ACL kernel options for ext2 and/or ext3 will need to be enabled (depending on which file system is being used - both can be enabled)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):275
+msgid "http://www.bluelightning.org/linux/samba_acl_howto/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):276
+msgid "http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):271
+msgid "While Active Directory, ACL, and PDC functions are out of the intended scope of this HOWTO, you may find these links as helpful to your cause: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):286
+msgid "Server Software Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):288
+msgid "Emerging Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):291
+msgid "First of all: be sure that all your hostnames resolve correctly. Either have a working domain name system running on your network or appropriate entries in your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames don't point to the correct machines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):298
+msgid "Hopefully now you can make an assessment of what you'll actually need in order to use Samba with your particular setup. The setup used for this HOWTO is:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):304
+msgid "cups"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):305
+msgid "readline"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):306
+msgid "pam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):309
+msgid "To optimize performance, size and the time of the build, the USE flags are specifically included or excluded."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):314
+msgid "First, add <c>ppds</c> to your USE flags to make sure that when CUPS is built, it has proper foomatic support:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):319
+msgid "Adding ppds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):319
+#, no-wrap
+msgid "\n# <i>echo \"net-print/cups ppds\" &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):323
+msgid "Now, emerge Samba:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):327
+msgid "Emerge Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):327
+#, no-wrap
+msgid "\n# <i>echo \"net-fs/samba readline cups pam\" &gt;&gt; /etc/portage/package.use</i>\n# <i>emerge net-fs/samba</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):332
+msgid "This will emerge Samba and CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):339
+msgid "Emerging net-print/hplip"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):342
+msgid "You only need to emerge this if you use an HP printer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):346
+msgid "Emerge hplip"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):346
+#, no-wrap
+msgid "\n# <i>emerge net-print/hplip</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):355
+msgid "Server Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):357
+msgid "Configuring Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):360
+msgid "The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is divided in sections indicated by [sectionname]. Comments are either # or ;. A sample <path>smb.conf</path> is included below with comments and suggestions for modifications. If more details are required, see the man page for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the Samba Web site or any of the numerous Samba books available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):369
+msgid "A Sample /etc/samba/smb.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):369
+#, no-wrap
+msgid "\n[global]\n<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>\nworkgroup = <comment>MYWORKGROUPNAME</comment>\n<comment># Of course this has no REAL purpose other than letting\n# everyone knows it's not Windows!\n# %v prints the version of Samba we are using.</comment>\nserver string = Samba Server %v\n<comment># We are going to use cups, so we are going to put it in here ;-)</comment>\nprintcap name = cups\nprinting = cups\nload printers = yes\n<comment># We want a log file and we do not want it to get bigger than 50kb.</comment>\nlog file = /var/log/samba/log.%m\nmax log size = 50\n<comment># We are going to set some options for our interfaces...</comment>\nsocket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192\n<comment># This is a good idea, what we are doing is binding the\n# samba server to our local network.\n# For example, if eth0 is our local network device</comment>\ninterfaces = lo <i>eth0</i>\nbind interfaces only = yes\n<comment># Now we are going to specify who we allow, we are afterall\n# very security conscience, since this configuration does\n# not use passwords!</comment>\nhosts allow = 127.0.0.1 <i>192.168.1.0/24</i>\nhosts deny = 0.0.0.0/0\n<comment># Other options for this are USER, DOMAIN, ADS, and SERVER\n# The default is user</comment>\nsecurity = share\n<comment># No passwords, so we're going to use a guest account!</comment>\nguest ok = yes\n\n<comment># Now we setup our print drivers information!</comment>\n[print$]\ncomment = Printer Drivers\npath = /etc/samba/printer <comment># this path holds the driver structure</comment>\nguest ok = yes\nbrowseable = yes\nread only = yes\n<comment># Modify this to \"username,root\" if you don't want root to\n# be the only printer admin)</comment>\nwrite list = <i>root</i>\n\n<comment># Now we'll setup a printer to share, while the name is arbitrary\n# it should be consistent throughout Samba and CUPS!</comment>\n[HPDeskJet930C]\ncomment = HP DeskJet 930C Network Printer\nprintable = yes\npath = /var/spool/samba\npublic = yes\nguest ok = yes\n<comment># Modify this to \"username,root\" if you don't want root to\n# be the only printer admin)</comment>\nprinter admin = <i>root</i>\n\n<comment># Now we setup our printers share. This should be\n# browseable, printable, public.</comment>\n[printers]\ncomment = All Printers\nbrowseable = no\nprintable = yes\nwritable = no\npublic = yes\nguest ok = yes\npath = /var/spool/samba\n<comment># Modify this to \"username,root\" if you don't want root to\n# be the only printer admin)</comment>\nprinter admin = <i>root</i>\n\n<comment># We create a new share that we can read/write to from anywhere\n# This is kind of like a public temp share, anyone can do what\n# they want here.</comment>\n[public]\ncomment = Public Files\nbrowseable = yes\npublic = yes\ncreate mode = 0766\nguest ok = yes\npath = /home/samba/public\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(warn):451
+msgid "If you like to use Samba's guest account to do anything concerning printing from Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c> section. The guest account seems to cause problems when running <c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See below, too, when we talk about <c>cupsaddsmb</c> and the problems that can arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c> or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you from a lot of problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):462
+msgid "Now create the directories required for the minimum configuration of Samba to share the installed printer throughout the network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):467
+msgid "Create the directories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):467
+#, no-wrap
+msgid "\n# <i>mkdir /etc/samba/printer</i>\n# <i>mkdir /var/spool/samba</i>\n# <i>mkdir /home/samba/public</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):473
+msgid "At least one Samba user is required in order to install the printer drivers and to allow users to connect to the printer. Users must exist in the system's <path>/etc/passwd</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):479
+msgid "Creating the users"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):479
+#, no-wrap
+msgid "\n# <i>smbpasswd -a root</i>\n\n<comment>(If another user is to be a printer admin)</comment>\n# <i>smbpasswd -a username</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):486
+msgid "The Samba passwords need not be the same as the system passwords in <path>/etc/passwd</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):491
+msgid "You will also need to update <path>/etc/nsswitch.conf</path> so that Windows systems can be found easily using NetBIOS:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):496
+msgid "Editing /etc/nsswitch.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):496
+#, no-wrap
+msgid "\n# <i>nano -w /etc/nsswitch.conf</i>\n<comment>(Edit the hosts: line)</comment>\nhosts: files dns <i>wins</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):505
+msgid "Configuring CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):508
+msgid "This is a little more complicated. CUPS' main config file is <path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's <path>httpd.conf</path> file, so many you may find it familiar. Outlined in the example are the directives that need to be changed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):515
+msgid "/etc/cups/cupsd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):515
+#, no-wrap
+msgid "\nServerName <i>PrintServer</i>          <comment># your printserver name</comment>\nServerAdmin <i>root@PrintServer</i>    <comment># the person for printer-related hate-mail, e.g. you</comment>\n\nAccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>\nErrorLog  /var/log/cups/error_log  <comment># doesn't really need changing either</comment>\n\nLogLevel  debug <comment># only while installing and testing, should later be\n                # changed to 'info'</comment>\n\nMaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,\n               # there seemed to be a bug in CUPS' controlling of the web interface,\n               # making CUPS think a denial of service attack was in progress when\n               # I tried to configure a printer with the web interface. weird.</comment>\n\nBrowseAddress @IF(<i>eth0</i>) <comment># Change this to your internal net interface</comment>\n\n&lt;Location /&gt;\nOrder Deny,Allow\nDeny From All\nAllow From <i>192.168.1.*</i>  <comment># the addresses of your internel network\n                        # e.g. 192.168.1.* will allow connections from any host on\n                        # the 192.168.1.0 network. change to whatever suits you</comment>\n&lt;/Location&gt;\n\n&lt;Location /admin&gt;\nAuthType Basic\nAuthClass System\nAllow From <i>192.168.1.*</i>  <comment># same as above, allow any host on the\n                        # 192.168.1.0 network to connect and do\n                        # administrative tasks after authenticating</comment>\nOrder Deny,Allow\nDeny From All\n&lt;/Location&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):551
+msgid "Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. The changes to <path>mime.convs</path> and <path>mime.types</path> are needed to make CUPS print Microsoft Office document files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):557
+msgid "/etc/cups/mime.convs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):557
+#, no-wrap
+msgid "\n<comment>(The following line is found near the end of the file. Uncomment it)</comment>\napplication/octet-stream        application/vnd.cups-raw        0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):562
+msgid "Edit <path>/etc/cups/mime.types</path> to uncomment some lines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):566
+msgid "/etc/cups/mime.types"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):566
+#, no-wrap
+msgid "\n<comment>(The following line is found near the end of the file. Uncomment it)</comment>\napplication/octet-stream\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):571
+msgid "CUPS needs to be started on boot, and started immediately."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):575
+msgid "Setting up the CUPS service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):575
+#, no-wrap
+msgid "\n<comment>(To start CUPS on boot)</comment>\n# <i>rc-update add cupsd default</i>\n<comment>(To start or restart CUPS now)</comment>\n# <i>/etc/init.d/cupsd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):585
+msgid "Installing a printer for and with CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):588
+msgid "First, go to <uri link=\"http://linuxprinting.org\">LinuxPrinting.Org</uri> to find and download the correct PPD file for your printer and CUPS. To do so, click the link Printer Listings to the left. Select your printers manufacturer and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click \"Show\". On the page coming up click the \"recommended driver\" link after reading the various notes and information. Then fetch the PPD file from the next page, again after reading the notes and introductions there. You may have to select your printers manufacturer and model again. Reading the <uri link=\"http://www.linuxprinting.org/cups-doc.html\">CUPS quickstart guide</uri> is also very helpful when working with CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):601
+msgid "Now you have a PPD file for your printer to work with CUPS. Place it in <path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. This can be done via the CUPS web interface or via command line. The web interface is found at <path>http://PrintServer:631</path> once CUPS is running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):609
+msgid "Install the printer via command line"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):609
+#, no-wrap
+msgid "\n# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>\n# <i>/etc/init.d/cupsd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):614
+msgid "Remember to adjust to what you have. Be sure to have the name (<c>-p</c> argument) right (the name you set above during the Samba configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or whatever device you are using for your printer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):621
+msgid "You should now be able to access the printer from the web interface and be able to print a test page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):629
+msgid "Installing the Windows printer drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):632
+msgid "Now that the printer should be working it is time to install the drivers for the Windows clients to work. Samba 2.2 introduced this functionality. Browsing to the print server in the Network Neighbourhood, right-clicking on the printershare and selecting \"connect\" downloads the appropriate drivers automagically to the connecting client, avoiding the hassle of manually installing printer drivers locally."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):641
+msgid "There are two sets of printer drivers for this. First, the Adobe PS drivers which can be obtained from <uri link=\"http://www.adobe.com/support/downloads/main.html\">Adobe</uri> (PostScript printer drivers). Second, there are the CUPS PS drivers, to be obtained by emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch, so you may need to add it to <path>/etc/portage/package.keywords</path>. There doesn't seem to be a difference between the functionality of the two, but the Adobe PS drivers need to be extracted on a Windows System since it's a Windows binary. Also the whole procedure of finding and copying the correct files is a bit more hassle. The CUPS drivers support some options the Adobe drivers don't."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):655
+msgid "This HOWTO uses the CUPS drivers for Windows. Install them as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):659
+msgid "Install the drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):659
+#, no-wrap
+msgid "\n# <i>emerge -av cups-windows</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):663
+msgid "Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution. Be sure to read its manpage (<c>man cupsaddsmb</c>), as it will tell you which Windows drivers you'll need to copy to the proper CUPS directory. Once you've copied the drivers, restart CUPS by running <c>/etc/init.d/cupsd restart</c>. Next, run <c>cupsaddsmb</c> as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):671
+msgid "Run cupsaddsmb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):671
+#, no-wrap
+msgid "\n# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>\n<comment>(Instead of HPDeskJet930C you could also specify \"-a\", which will\n\"export all known printers\".)</comment>\n# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(warn):678
+msgid "The execution of this command often causes the most trouble. Read through the <uri link=\"http://forums.gentoo.org/viewtopic.php?t=110931\">posts in this thread</uri> for some troubleshooting tips."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):684
+msgid "Here are common errors that may happen:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):689
+msgid "The hostname given as a parameter for <c>-h</c> and <c>-H</c> (<c>PrintServer</c>) often does not resolve correctly and doesn't identify the print server for CUPS/Samba interaction. If an error like: <b>Warning: No PPD file for printer \"CUPS_PRINTER_NAME\" - skipping!</b> occurs, the first thing you should do is substitute <c>PrintServer</c> with <c>localhost</c> and try it again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):697
+msgid "The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message is quite common, but can be triggered by many problems. It's unfortunately not very helpful. One thing to try is to temporarily set <c>security = user</c> in your <path>smb.conf</path>. After/if the installation completes successfully, you should set it back to share, or whatever it was set to before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):707
+msgid "This should install the correct driver directory structure under <path>/etc/samba/printer</path>. That would be <path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3 driver files and the PPD file, renamed to <path>YourPrinterName.ppd</path> (the name which you gave the printer when installing it (see above)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):715
+msgid "Pending no errors or other complications, your drivers are now installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):722
+msgid "Finalizing our setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):725
+msgid "Lastly, setup our directories."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):729
+msgid "Final changes needed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):729
+#, no-wrap
+msgid "\n# <i>mkdir /home/samba</i>\n# <i>mkdir /home/samba/public</i>\n# <i>chmod 755 /home/samba</i>\n# <i>chmod 755 /home/samba/public</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):739
+msgid "Testing our Samba configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):742
+msgid "We will want to test our configuration file to ensure that it is formatted properly and all of our options have at least the correct syntax. To do this we run <c>testparm</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):748
+msgid "Running the testparm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):748
+#, no-wrap
+msgid "\n<comment>(By default, testparm checks /etc/samba/smb.conf)</comment>\n# <i>/usr/bin/testparm</i>\nLoad smb config files from /etc/samba/smb.conf\nProcessing section \"[printers]\"\nGlobal parameter guest account found in service section!\nProcessing section \"[public]\"\nGlobal parameter guest account found in service section!\nLoaded services file OK.\nServer role: ROLE_STANDALONE\nPress enter to see a dump of your service definitions\n ...\n ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):766
+msgid "Starting the Samba service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):769
+msgid "Now configure Samba to start at bootup; then go ahead and start it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):773
+msgid "Setting up the Samba service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):773
+#, no-wrap
+msgid "\n# <i>rc-update add samba default</i>\n# <i>/etc/init.d/samba start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):781
+msgid "Checking our services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):784
+msgid "It would probably be prudent to check our logs at this time also. We will also want to take a peak at our Samba shares using <c>smbclient</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):789
+msgid "Checking the shares with smbclient"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):789
+#, no-wrap
+msgid "\n# <i>smbclient -L localhost</i>\nPassword:\n<comment>(You should see a BIG list of services here.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):800
+msgid "Configuration of the Clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):802
+msgid "Printer configuration of *nix based clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):805
+msgid "Despite the variation or distribution, the only thing needed is CUPS. Do the equivalent on any other UNIX/Linux/BSD client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):810
+msgid "Configuring a Gentoo system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):810
+#, no-wrap
+msgid "\n# <i>emerge cups</i>\n# <i>nano -w /etc/cups/client.conf</i>\nServerName <i>PrintServer</i>      <comment># your printserver name</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):816
+msgid "That should be it. Nothing else will be needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):820
+msgid "If you use only one printer, it will be your default printer. If your print server manages several printers, your administrator will have defined a default printer on the server. If you want to define a different default printer for yourself, use the <c>lpoptions</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):827
+msgid "Setting your default printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):827
+#, no-wrap
+msgid "\n<comment>(List available printers)</comment>\n# <i>lpstat -a</i>\n<comment>(Sample output, yours will differ)</comment>\nHPDeskJet930C accepting requests since Jan 01 00:00\nlaser accepting requests since Jan 01 00:00\n<comment>(Define HPDeskJet930C as your default printer)</comment>\n# <i>lpoptions -d HPDeskJet930C</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):837
+msgid "Printing in *nix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):837
+#, no-wrap
+msgid "\n<comment>(Specify the printer to be used)</comment>\n# <i>lp -d HPDeskJet930C anything.txt</i>\n<comment>(Use your default printer)</comment>\n# <i>lp foobar.whatever.ps</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):844
+msgid "Just point your web browser to <c>http://printserver:631</c> on the client if you want to manage your printers and their jobs with a nice web interface. Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your print server, not the name you gave to the cups print server if you used different names."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):855
+msgid "Mounting a Windows or Samba share in GNU/Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(note):858
+msgid "Don't forget to install <c>net-fs/mount-cifs</c> or <c>net-fs/samba</c> on the client(s) that will be accessing the shares."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):863
+msgid "Now is time to configure our kernel to support CIFS. Since I'm assuming we've all compiled at least one kernel, we'll need to make sure we have all the right options selected in our kernel. For simplicity's sake, make it a module for ease of use. It is the author's opinion that kernel modules are a good thing and should be used whenever possible."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):871
+msgid "Kernel support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):871
+#, no-wrap
+msgid "\nCONFIG_CIFS=m\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):875
+msgid "Then make the module/install it; insert it with:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):879
+msgid "Loading the kernel module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):879
+#, no-wrap
+msgid "\n# <i>modprobe cifs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):883
+msgid "Once the module is loaded, mounting a Windows or Samba share is possible. Use <c>mount</c> to accomplish this, as detailed below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):888
+msgid "Mounting a Windows/Samba share"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):888
+#, no-wrap
+msgid "\n<comment>(The syntax for mounting a Windows/Samba share is:\n  mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point\nIf we are not using passwords or a password is not needed)</comment>\n\n# <i>mount -t cifs //PrintServer/public /mnt/public</i>\n\n<comment>(If a password is needed)</comment>\n# <i>mount -t cifs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):899
+msgid "After you mount the share, you would access it as if it were a local drive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):906
+msgid "Printer Configuration for Windows NT/2000/XP clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):909
+msgid "That's just a bit of point-and-click. Browse to <path>\\\\PrintServer</path> and right click on the printer (HPDeskJet930C) and click connect. This will download the drivers to the Windows client and now every application (such as Word or Acrobat) will offer HPDeskJet930C as an available printer to print to. :-)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):921
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):923
+msgid "A Fond Farewell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):926
+msgid "That should be it. You should now have a successful printing enviroment that is friendly to both Windows and *nix as well as a working share!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):936
+msgid "Links and Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):938
+msgid "Links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):941
+msgid "These are some links that may help you in setting up, configuration and troubleshooting your installation:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri:link):947
+msgid "http://www.cups.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):947
+msgid "CUPS Homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):948
+msgid "<uri link=\"http://www.samba.org/\">Samba Homepage</uri>, especially the <uri link=\"http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html\">chapter on Samba/CUPS configuration</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri:link):953
+msgid "http://linuxprinting.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):953
+msgid "LinuxPrinting dot Org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):954
+msgid "<uri link=\"http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/\">Kurt Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and Samba, and generally printing support on networks. A really interesting read, with lots and lots of details.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri:link):961
+msgid "http://www.freebsddiary.org/cups.php"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):961
+msgid "FreeBSD Diary's CUPS Topic"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):967
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):970
+msgid "See <uri link=\"http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37\">this page</uri> from Kurt Pfeifle's \"Printing Support in Samba 3.0\" manual. Lots of useful tips there! Be sure to look this one up first, before posting questions and problems! Maybe the solution you're looking for is right there."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/rsync.xml.pot b/doc/gettext/rsync.xml.pot
new file mode 100644
index 0000000..95569c7
--- /dev/null
+++ b/doc/gettext/rsync.xml.pot
@@ -0,0 +1,393 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(guide:link):5
+msgid "/doc/en/rsync.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):6
+msgid "Gentoo Linux rsync Mirrors Policy and Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//rsync.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail:link):9
+msgid "mirror-admin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail):9
+msgid "Gentoo Mirror Administrators"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail:link):12
+msgid "klausman-gentoo@schwarzvogel.de"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail):12
+msgid "Tobias Klausmann"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail:link):15
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail):15
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(abstract):18
+msgid "This document explains how to set up a official rsync mirror and your own local mirror."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(version):27
+msgid "3.9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(date):28
+msgid "2010-06-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):31
+msgid "Preliminaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):33
+msgid "Terms, names and all that"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):36
+msgid "This guide is intended for people who would like to set up an rsync mirror of their own. It caters not only to those who want to run an official rsync mirror but also those wanting to run private mirrors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):42
+msgid "There are three kinds of Gentoo rsync mirrors: main rotation mirrors, community mirrors and private mirrors. Main rotation mirrors are maintained by the Gentoo infrastructure team. They handle the bulk of the Gentoo rsync traffic. The community mirrors are run by volunteers from the Gentoo community. Private mirrors are mirrors run by individuals which are closed off to the public and meant to cut traffic costs and latency for an organization or individual."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):51
+msgid "At this time, we have enough community mirrors and are actively seeking additional main rotation mirrors. Hardware specifications for main rotation servers include:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):58
+msgid "Minimum of a 2GHz Pentium 4 processor (64-bit with at least 2 cores preferred)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):59
+msgid "Minimum of 2GB RAM (3GB - 4GB is ideal)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):60
+msgid "15GB of disk space (IDE/SATA is fine)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):63
+msgid "You would maintain physical possession ownership of the hardware, and keep it online in your own colocation space. Average bandwidth consumption for each main rotation mirror is currently ~10Mbit/sec (around 2.6 TiB per month). As the number of main rotation mirrors increases, this number should decrease accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):71
+msgid "If you would like to donate your machine, please email the <mail link=\"mirror-admin@gentoo.org\">Mirror Admins</mail> with the pertinent information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):82
+msgid "Setting up your own local rsync mirror"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):84 ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):240
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):87
+msgid "Many users run Gentoo on several machines and need to sync the portage trees on all of them. Using public mirrors is simply a waste of bandwidth at both ends. Syncing only one machine against a public mirror and all others against that computer would save resources on Gentoo mirrors and save users' bandwidth."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):94
+msgid "The same holds true for organizations who would like to control the rsync mirror their servers and workstations sync against. Of course, they usually also want to save on bandwidth and traffic costs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):100
+msgid "All you need to do is select which machine is going to be your own local rsync mirror and set it up. You should choose a computer that can handle the CPU and disk load that an rsync operation requires. Your local mirror also needs to be available whenever any of your other computers syncs its portage tree. Besides, it should have a static IP address or a name that always resolves to your server. Configuring a DHCP and/or a DNS server is beyond the scope of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):110
+msgid "Note that these instructions assume your private rsync mirror is a Gentoo machine. If you intend to run it on a different distribution, the guide for setting up a community mirror might be more helpful. Just don't sync the mirror every half hour but once or twice a day."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):120
+msgid "Setting up the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):123
+msgid "There is no extra package to install as the required software is already on your computer. Setting up your own local rsync mirror is just a matter of configuring the <c>rsyncd</c> daemon to make your <path>/usr/portage</path> directory available for syncing. Create the following <path>/etc/rsyncd.conf</path> configuration file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):131
+msgid "Sample /etc/rsyncd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):131
+#, no-wrap
+msgid "\npid file = /var/run/rsyncd.pid\nmax connections = 5\nuse chroot = yes\nuid = nobody\ngid = nobody\n<comment># Optional: restrict access to your Gentoo boxes</comment>\nhosts allow = 192.168.0.1 192.168.0.2 192.168.1.0/24\nhosts deny  = *\n\n[gentoo-portage]\npath=/usr/portage\ncomment=Gentoo Portage\nexclude=distfiles/ packages/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):147
+msgid "You do not need to use the <c>hosts allow</c> and <c>hosts deny</c> options. By default, all clients will be allowed to connect. The order in which you write the options is not relevant. The server will always check the <c>hosts allow</c> option first and grant the connection if the connecting host matches any of the listed patterns. The server will then check the <c>hosts deny</c> option and refuse the connection if any match is found. Any host that does not match anything will be granted a connection. Please read the man page (<c>man rsyncd.conf</c>) for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):158
+msgid "Now, start your rsync daemon with the following command as the root user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):162
+msgid "Starting the rsync daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):162
+#, no-wrap
+msgid "\n<comment>(Start the daemon now)</comment>\n# <i>/etc/init.d/rsyncd start</i>\n<comment>(Add the daemon to your default runlevel)</comment>\n# <i>rc-update add rsyncd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):169
+msgid "Let's test your rsync mirror. You do not need to try from another machine but it would be a good idea to do so. If your server is not known by name from all your computers, you can use its IP address instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):175
+msgid "Testing your mirror"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):175
+#, no-wrap
+msgid "\n<comment>(You may use the server name or its IP)</comment>\n# <i>rsync 192.168.0.1::</i>\ngentoo-portage     Gentoo Portage\n# <i>rsync your_server_name::gentoo-portage</i>\n<comment>(You should see the content of /usr/portage on your mirror)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):183
+msgid "Your rsync mirror is now set up. Keep running <c>emerge --sync</c> as you have done so far to keep your server up-to-date. If you use cron or similar facilities to sync regularly, remember to keep it down to a sensible frequency like once or twice a day."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(note):190
+msgid "Please note that most public mirror administrators consider syncing more than once or twice a day an abuse. Some if not most of them will ban your IP from their server if you start abusing their machines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):199
+msgid "Configuring your clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):202
+msgid "Now, make your other computers use your own local rsync mirror instead of a public one. Edit your <path>/etc/make.conf</path> and make the <c>SYNC</c> variable point to your server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):208
+msgid "Define SYNC in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):208
+#, no-wrap
+msgid "\n<comment>(Use your server IP address)</comment>\nSYNC=\"rsync://<i>192.168.0.1</i>/gentoo-portage\"\n<comment>(Or use your server name)</comment>\nSYNC=\"rsync://<i>your_server_name</i>/gentoo-portage\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):215
+msgid "You can check that your computer has been properly set up by syncing against your own local mirror for the first time:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):220
+msgid "Checking and syncing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):220
+#, no-wrap
+msgid "\n<comment>(Check that the SYNC variable has been setup)</comment>\n# <i>emerge --info|grep SYNC</i>\nSYNC=\"rsync://your_server_name/gentoo-portage\"\n<comment>(Sync against your local mirror)</comment>\n# <i>emerge --sync</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):228
+msgid "That's it! All your computers will now use your local rsync mirror whenever you run <c>emerge --sync</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):238
+msgid "Setting up a community rsync server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(note):243
+msgid "You can find sample configuration and script files in the gentoo-rsync-mirror package. Just do <c>emerge gentoo-rsync-mirror</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):248
+msgid "Right now, mirroring our Portage tree requires around 600Mb, so it isn't space intensive; having at least 1Gb free should allow for growing room. Setting up a Portage tree mirror is simple -- first, ensure that your mirror has rsync installed. Then, set up your <path>rsyncd.conf</path> file to look something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):256
+msgid "rsyncd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):256
+#, no-wrap
+msgid "\nuid = nobody\ngid = nobody\nuse chroot = yes\nmax connections = 15\npid file = /var/run/rsyncd.pid\nmotd file = /etc/rsync/rsyncd.motd\nlog file = /var/log/rsync.log\ntransfer logging = yes\nlog format = %t %a %m %f %b\nsyslog facility = local3\ntimeout = 300\n\n[gentoo-portage]\n#modern versions of portage use this entry\npath = /gentoo/rsync\ncomment = Gentoo Linux Portage tree mirror\nexclude = distfiles\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):276
+msgid "You can pick your own locations for most of the files, of course. What's important is the section name (<c>[gentoo-portage]</c>). This is the location that rsync clients will try to sync from."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):282
+msgid "For security reasons, the use of a chrooted environment is required! This has implications for the logged timestamps -- see the FAQ below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):287
+msgid "Now, you need to mirror the Gentoo Linux Portage tree. You can use the script below to do so. Again, you'll probably want to change some of the file locations to suit your needs -- in particular, they should match those of your <path>rsyncd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):294
+msgid "rsync-gentoo-portage.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):294
+#, no-wrap
+msgid "\n#!/bin/bash\n\nRSYNC=\"/usr/bin/rsync\"\nOPTS=\"--quiet --recursive --links --perms --times -D --delete --timeout=300\"\n#Uncomment the following line only if you have been granted access to masterportage.gentoo.org\n#SRC=\"rsync://masterportage.gentoo.org/gentoo-portage\"\n#If you are waiting for access to our master mirror, select one of our mirrors to mirror from:\nSRC=\"rsync://rsync.de.gentoo.org/gentoo-portage\"\nDST=\"/space/gentoo/rsync/\"\n\necho \"Started update at\" `date` &gt;&gt; $0.log 2&gt;&amp;1\nlogger -t rsync \"re-rsyncing the gentoo-portage tree\"\n${RSYNC} ${OPTS} ${SRC} ${DST} &gt;&gt; $0.log 2&gt;&amp;1\n\necho \"End: \"`date` &gt;&gt; $0.log 2&gt;&amp;1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):312
+msgid "Your <path>rsyncd.motd</path> should contain your IP address and other relevant information about your mirror, such as information about the host providing the Portage mirror and an administrative contact. You can now test your server as outlined in the <uri link=\"#local\">Setting up your own local rsync mirror</uri> chapter above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):320
+msgid "After you have been approved as an official rsync mirror, your host will be aliased with a name of the form: <path>rsync[num].[country code].gentoo.org</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):331
+msgid "Short FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):333
+msgid "Q: Who should I contact regarding rsync issues and maintenance?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):336
+msgid "A: Visit <uri link=\"http://bugs.gentoo.org\">Gentoo Bugzilla</uri> and fill out a bug on the product \"Mirrors\", component \"Server Problem\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):345
+msgid "Q: How can I check the freshness of an official rsync server?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):348
+msgid "The Gentoo infrastructure team monitors all community rsync servers for freshness. You can see the results on the <uri link=\"http://mirrorstats.gentoo.org/rsync\">corresponding web page</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):357
+msgid "Q: I run a private rsync mirror for my company. Can I still access masterportage.gentoo.org?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):362
+msgid "A: Because our resources are limited, we need to ensure we allocate them in such a way as to provide the maximum amount of benefit to our users. As such, we limit connections to our master rsync and distfile mirrors to public mirrors only. Users are welcome to use our regular mirror system to establish a private rsync mirror, though they are asked to follow certain basic <uri link=\"/news/en/gwn/20030505-newsletter.xml#doc_chap1_sect3\">rsync etiquette guidelines</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):375
+msgid "Q: Is it important that I sync my mirror twice an hour?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):378
+msgid "A: Yes it is important. You do not need to perform the syncs at exactly :00 and :30 but the syncs should take place in each of the following two windows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):384
+msgid ":00 to :10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):385
+msgid ":30 to :40"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):388
+msgid "Additionally, please make sure that your syncs are exactly 30 minutes apart. So, if you schedule the first sync of each hour for :08, please schedule the second sync of the hour for :38."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):397
+msgid "Q: Where should I sync my rsync mirror before I become an official Gentoo mirror?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):401
+msgid "For European-based rsync mirror: sync to rsync.de.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):402
+msgid "For US-based rsync mirror: sync to rsync.us.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):403
+msgid "For all others: sync to rsync.us.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):410
+msgid "Q: How do I find the mirror nearest to me?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):413
+msgid "A: <c>netselect</c> was designed to do this for you. If you haven't already run <c>emerge netselect</c> then do it. Then run: <c>netselect rsync.gentoo.org</c>. After a minute or so netselect will print an IP address. Take this address and use it as the only parameter for rsync with two colons appended to it. e.g.: <c>rsync 1.2.3.4::</c>. You should be able to find out which mirror that is from the banner message. Update your <path>/etc/make.conf</path> accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):426
+msgid "Q: Can I use compression when syncing against masterportage.gentoo.org?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):429
+msgid "A: No. Compression utilizes too many resources on the server, so we have forcibly disabled it on <path>masterportage.gentoo.org</path>. Please <e>do not</e> attempt to use compression when syncing against this server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):438
+msgid "Q: I'm seeing a lot of old and probably dead rsync processes, how can I get rid of them?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):442
+msgid "This command will help you to kill old rsync processes that sometimes lie around due to connection problems. It's important to kill those because they count as valid connections for the 'max connections' option. You may run this command via crontab every hour, it will search and kill rsync processes older than one hour."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):450
+msgid "Kill old rsync processes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):450
+#, no-wrap
+msgid "\n/bin/kill -9 `/bin/ps --no-headers -Crsync -o etime,user,pid,command|/bin/grep nobody | \\\n             /bin/grep \"[0-9]\\{2\\}:[0-9]\\{2\\}:\" |/bin/awk '{print $3}'`\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):458
+msgid "Q: There are many users who connect to my rsync server very frequently, sometimes even causing a DoS to my mirror, is there any way to prevent this?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):463
+msgid "In some cases, there are a few inconsiderate users who abuse the rsync mirror system by syncing more than 1-2 times per day. In the most extreme cases, users schedule cron jobs to sync every 15 minutes or so. This often leads to a Denial of Service attack by continually occupying an rsync slot that could have otherwise gone to another user. To try and prevent this, you may use the <uri link=\"/proj/en/infrastructure/mirrors/rsyncd.conf_pl.txt\">this perl script</uri> which will scan your rsync log files, pick out IP addresses that have already connected more than <c>N</c> times that day and dynamically create a <path>rsyncd.conf</path> file, including the offending IP addresses in the 'hosts deny' directive. The following line controls what <c>N</c> equals (in this case 4):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):477
+msgid "Define maximum number of connections per IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):477
+#, no-wrap
+msgid "\n@badhosts=grep {$hash{$_}&gt;4} keys %hash;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):481
+msgid "If you use this script, please remember to rotate your rsync log files daily and modify the script to match the location of your <path>rsyncd.conf</path> file. This script is tested on Gentoo Linux, but should work suitably on other arches that support both rsync and perl."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/ru/alsa-guide.xml.po b/doc/gettext/ru/alsa-guide.xml.po
new file mode 100644
index 0000000..8a47045
--- /dev/null
+++ b/doc/gettext/ru/alsa-guide.xml.po
@@ -0,0 +1,1139 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/altinstall.xml.po b/doc/gettext/ru/altinstall.xml.po
new file mode 100644
index 0000000..27e8e34
--- /dev/null
+++ b/doc/gettext/ru/altinstall.xml.po
@@ -0,0 +1,1031 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):7
+msgid "The Gentoo Linux alternative installation method HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):9
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):12
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):15
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):18
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):21
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):24
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):27
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):30
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):10
+msgid "gerrynjr@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):10
+msgid "Gerald Normandin Jr."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):13
+msgid "lordviram@rebelpacket.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):13
+msgid "Travis Tilley"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):16
+msgid "volontir@yahoo.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):16
+msgid "Oleg Raisky"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):19
+msgid "luminousit@hotmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):19
+msgid "Alex Garbutt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):22
+msgid "alex@openvs.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):22
+msgid "Alexandre Georges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):25
+msgid "vargen@b0d.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):25
+msgid "Magnus Backanda"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):28
+msgid "davoid@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):28
+msgid "Faust A. Tanasescu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):31
+msgid "aliz@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):31
+msgid "Daniel Ahlberg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):33
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):39
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):42
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):45
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):48
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):34
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):34
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):36
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author):36
+msgid "Ken Nowack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):40
+msgid "blubber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):40
+msgid "Tiemo Kieft"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):43
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):43
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):46
+msgid "smithj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):46
+msgid "Jonathan Smith"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):49
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(abstract):52
+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):62
+msgid "6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(date):63
+msgid "2010-09-27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):66
+msgid "About this document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):70
+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):85
+msgid "Booting the Install CD with Smart BootManager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):89
+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):98
+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):104
+msgid "Smart BootManager Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):104
+#, 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):134
+msgid "Using sbminst to build the boot floppy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):134
+#, no-wrap
+msgid ""
+"\n"
+"# <i>sbminst -t us  -d /dev/fd0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(note):138
+msgid ""
+"Replace <path>fd0</path> with your respective floppy device name if yours is "
+"different."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):143
+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):149
+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):155
+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):165
+msgid "Installation from non-Gentoo LiveCDs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):167
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(impo):170
+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):178
+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):185
+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):194
+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):204
+msgid "Installation instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):207
+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):214
+msgid "Creating the /mnt/gentoo mountpoint"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):214
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):218
+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):225
+msgid "Bind-mounting the proc pseudo filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):225
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount -o bind /proc /mnt/gentoo/proc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):229
+msgid ""
+"When you're ready to unpack the stage tarball in <uri link=\"/doc/en/"
+"handbook/handbook-x86.xml?part=1&amp;chap=5_sect4\">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):236
+msgid "Unpacking the stage tarball"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):236
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tar --numeric-owner -xvjpf stage3-*.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):240
+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):247
+msgid "Chrooting into the new environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):247
+#, 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):256
+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):291
+msgid "Diskless install using PXE boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):293
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):556
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):296
+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):305
+msgid "Server base setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):308
+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):315
+msgid "Directory setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):315
+#, 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):321
+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):326
+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):333
+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):340
+msgid "dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):340
+#, 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):351
+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):357
+msgid "/etc/conf.d/net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):357
+#, 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):362
+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):367
+msgid "in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):367
+#, 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):373
+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):379
+msgid "Grub setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):379
+#, 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):386
+msgid "grub.lst"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):386
+#, 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):398
+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):403
+msgid "/etc/exports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):403
+#, 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):409
+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):414
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):414
+#, 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):424
+msgid "Creating the system on the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):427
+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):439
+msgid "Mounting the filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):439
+#, no-wrap
+msgid ""
+"\n"
+"#<i> mount /dev/hdaX /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):443
+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):450
+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):455
+msgid "Extracting the stage tarball"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):455
+#, 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):465
+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):471
+msgid "menuconfig options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):471
+#, 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):490
+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):496
+msgid "/etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):496
+#, 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):503
+msgid "You also need to prevent the client to run a filesystem check:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):507
+msgid "Preventing the client to run a filesystem check"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):507
+#, 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):512
+msgid "Install <c>nfs-utils</c> since your client will heavily depend on it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):516
+msgid "Installing nfs-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):516
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge nfs-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):520
+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):526
+msgid "Starting services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):526
+#, 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):535
+msgid "Booting the new client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):538
+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):554
+msgid "Installing Gentoo from an existing Linux distribution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):559
+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):571
+msgid "Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):574
+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):585
+msgid "How should we make space for Gentoo?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):588
+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):597
+msgid "Filesystem information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):597
+#, 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):609
+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):620
+msgid "Building parted to resize partition"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):623
+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):631
+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):637
+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):650
+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):655
+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):662
+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):670
+msgid "Utility disk creation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):670
+#, 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):679
+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):686
+msgid "Building the utility floppy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):686
+#, 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):692
+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):706
+msgid "Commands to run once logged into mininux system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):706
+#, 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):729
+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):734
+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):741
+msgid "Flushing the environment during chroot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):741
+#, 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):747
+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/ru/anothertest.xml.po b/doc/gettext/ru/anothertest.xml.po
new file mode 100644
index 0000000..a560c40
--- /dev/null
+++ b/doc/gettext/ru/anothertest.xml.po
@@ -0,0 +1,72 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/apache-troubleshooting.xml.po b/doc/gettext/ru/apache-troubleshooting.xml.po
new file mode 100644
index 0000000..b111c29
--- /dev/null
+++ b/doc/gettext/ru/apache-troubleshooting.xml.po
@@ -0,0 +1,56 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/apache-upgrading.xml.po b/doc/gettext/ru/apache-upgrading.xml.po
new file mode 100644
index 0000000..8c3db5b
--- /dev/null
+++ b/doc/gettext/ru/apache-upgrading.xml.po
@@ -0,0 +1,56 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/arm-requirements.xml.po b/doc/gettext/ru/arm-requirements.xml.po
new file mode 100644
index 0000000..98412d5
--- /dev/null
+++ b/doc/gettext/ru/arm-requirements.xml.po
@@ -0,0 +1,115 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/ati-faq.xml.po b/doc/gettext/ru/ati-faq.xml.po
new file mode 100644
index 0000000..6c1d3d6
--- /dev/null
+++ b/doc/gettext/ru/ati-faq.xml.po
@@ -0,0 +1,356 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/bind-guide.xml.po b/doc/gettext/ru/bind-guide.xml.po
new file mode 100644
index 0000000..176c1f7
--- /dev/null
+++ b/doc/gettext/ru/bind-guide.xml.po
@@ -0,0 +1,536 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/bluetooth-guide.xml.po b/doc/gettext/ru/bluetooth-guide.xml.po
new file mode 100644
index 0000000..fd9f06e
--- /dev/null
+++ b/doc/gettext/ru/bluetooth-guide.xml.po
@@ -0,0 +1,870 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/bugzilla-howto.xml.po b/doc/gettext/ru/bugzilla-howto.xml.po
new file mode 100644
index 0000000..b52df67
--- /dev/null
+++ b/doc/gettext/ru/bugzilla-howto.xml.po
@@ -0,0 +1,1986 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/change-chost.xml.po b/doc/gettext/ru/change-chost.xml.po
new file mode 100644
index 0000000..03cba43
--- /dev/null
+++ b/doc/gettext/ru/change-chost.xml.po
@@ -0,0 +1,519 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/conky-howto.xml.po b/doc/gettext/ru/conky-howto.xml.po
new file mode 100644
index 0000000..2199381
--- /dev/null
+++ b/doc/gettext/ru/conky-howto.xml.po
@@ -0,0 +1,276 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/cron-guide.xml.po b/doc/gettext/ru/cron-guide.xml.po
new file mode 100644
index 0000000..715f8d0
--- /dev/null
+++ b/doc/gettext/ru/cron-guide.xml.po
@@ -0,0 +1,928 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(guide:link):5
+msgid "/doc/en/cron-guide.xml"
+msgstr ""
+
+#: ../../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 "1.9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(date):27
+msgid "2008-01-26"
+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>slocate</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/ru/cross-compiling-distcc.xml.po b/doc/gettext/ru/cross-compiling-distcc.xml.po
new file mode 100644
index 0000000..d08d8de
--- /dev/null
+++ b/doc/gettext/ru/cross-compiling-distcc.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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/cvs-tutorial.xml.po b/doc/gettext/ru/cvs-tutorial.xml.po
new file mode 100644
index 0000000..bd0d5b6
--- /dev/null
+++ b/doc/gettext/ru/cvs-tutorial.xml.po
@@ -0,0 +1,1205 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/desktop.xml.po b/doc/gettext/ru/desktop.xml.po
new file mode 100644
index 0000000..931764a
--- /dev/null
+++ b/doc/gettext/ru/desktop.xml.po
@@ -0,0 +1,65 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/devfs-guide.xml.po b/doc/gettext/ru/devfs-guide.xml.po
new file mode 100644
index 0000000..4ff6cac
--- /dev/null
+++ b/doc/gettext/ru/devfs-guide.xml.po
@@ -0,0 +1,589 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/diskless-howto.xml.po b/doc/gettext/ru/diskless-howto.xml.po
new file mode 100644
index 0000000..4174fb4
--- /dev/null
+++ b/doc/gettext/ru/diskless-howto.xml.po
@@ -0,0 +1,1687 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/distcc.xml.po b/doc/gettext/ru/distcc.xml.po
new file mode 100644
index 0000000..726a353
--- /dev/null
+++ b/doc/gettext/ru/distcc.xml.po
@@ -0,0 +1,566 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/doc-languages.xml.po b/doc/gettext/ru/doc-languages.xml.po
new file mode 100644
index 0000000..f658f6f
--- /dev/null
+++ b/doc/gettext/ru/doc-languages.xml.po
@@ -0,0 +1,44 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/dri-howto.xml.po b/doc/gettext/ru/dri-howto.xml.po
new file mode 100644
index 0000000..e53bdbd
--- /dev/null
+++ b/doc/gettext/ru/dri-howto.xml.po
@@ -0,0 +1,498 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/ebuild-submit.xml.po b/doc/gettext/ru/ebuild-submit.xml.po
new file mode 100644
index 0000000..7fedb9a
--- /dev/null
+++ b/doc/gettext/ru/ebuild-submit.xml.po
@@ -0,0 +1,253 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/faq.xml.po b/doc/gettext/ru/faq.xml.po
new file mode 100644
index 0000000..6b3180e
--- /dev/null
+++ b/doc/gettext/ru/faq.xml.po
@@ -0,0 +1,998 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/fluxbox-config.xml.po b/doc/gettext/ru/fluxbox-config.xml.po
new file mode 100644
index 0000000..33985bd
--- /dev/null
+++ b/doc/gettext/ru/fluxbox-config.xml.po
@@ -0,0 +1,880 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/gcc-optimization.xml.po b/doc/gettext/ru/gcc-optimization.xml.po
new file mode 100644
index 0000000..0daebc0
--- /dev/null
+++ b/doc/gettext/ru/gcc-optimization.xml.po
@@ -0,0 +1,725 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/gcc-upgrading.xml.po b/doc/gettext/ru/gcc-upgrading.xml.po
new file mode 100644
index 0000000..9dee752
--- /dev/null
+++ b/doc/gettext/ru/gcc-upgrading.xml.po
@@ -0,0 +1,638 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../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/ru/genkernel.xml.po b/doc/gettext/ru/genkernel.xml.po
new file mode 100644
index 0000000..054ee3a
--- /dev/null
+++ b/doc/gettext/ru/genkernel.xml.po
@@ -0,0 +1,1054 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(guide:link):5
+msgid "/doc/en/genkernel.xml"
+msgstr ""
+
+#: ../../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 ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author:title):12
+msgid "Contributor"
+msgstr ""
+
+#. folajimi@speakeasy.net
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author):12
+msgid "Jimi Ayodele"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author:title):16
+msgid "NFS Support"
+msgstr ""
+
+#. thseiler@gmail.com
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author):16
+msgid "Thomas Seiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author:title):19
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(mail:link):20
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(abstract):23
+msgid ""
+"This guide intends to provide a reference of all the functions provided by "
+"genkernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(version):30
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(date):31
+msgid "2008-06-22"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):34
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):36
+msgid "Rationale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):39
+msgid ""
+"For users who are not privy to kernel compilation, genkernel is a tool to "
+"automate this process. It can help you create a kernel image akin to those "
+"available on Gentoo Installation CDs, which are designed to auto-detect the "
+"hardware configuration of your system. Some users may also be interested in "
+"using genkernel for hardware requiring initialization and a working kernel "
+"before the system starts up. Since genkernel automatically compiles your "
+"kernel modules, you can use hardware that may require certain module "
+"parameters to be loaded for proper operation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):53
+msgid "Target Audience"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):56
+msgid ""
+"If you are either uncertain about how to compile a kernel, or are just "
+"unfamiliar with your hardware configuration, genkernel is a very handy tool. "
+"It is designed to take the pain out of the kernel compiling process, and "
+"supports most hardware by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):63
+msgid ""
+"However, if you know what drivers are required by your system, you may be "
+"able to further reduce the time taken to compile the kernel. This is "
+"possible since you can direct genkernel to only build drivers relevant to "
+"your hardware. Oftentimes, the number of drivers required by your system "
+"will be fewer (implying a shorter kernel compilation time) than the default "
+"configuration provides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):75
+msgid "Installing genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):78
+msgid ""
+"To obtain genkernel, run <c>emerge genkernel</c> from the command line. If "
+"you are using the <uri link=\"/doc/en/handbook/2005.1/hb-install-about."
+"xml#doc_chap2_sect1\">Gentoo Reference Platform</uri> (GRP), remember to "
+"install binary packages by passing the <c>-k</c> flag to emerge. Since the "
+"GRP is bundled with an older version of genkernel, the flags may be "
+"different. In any case, consult <c>genkernel --help</c> for help on how to "
+"use the version of genkernel installed on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):94
+msgid "Working with genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):96
+msgid "How to use genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):99
+msgid ""
+"Although there are several ways to run genkernel, the least-intrusive "
+"approach is provided by <c>genkernel all</c>. Here, a generic configuration "
+"which works well for most systems is used. As was mentioned earlier, this "
+"approach is not without drawbacks; most of the modules created are useless "
+"to the average user and may increase compile time. Below is an illustration "
+"of a more efficient approach, achieved by passing certain flags to genkernel "
+"as root:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):108
+msgid "Running genkernel (with flags)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):108
+#, no-wrap
+msgid ""
+"\n"
+"# <i>genkernel --splash --no-install --no-clean --menuconfig all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):112
+msgid ""
+"The above operation causes genkernel to create a framebuffer splash-enabled "
+"kernel (<c>--splash</c>) that will have to be manually installed (<c>--no-"
+"install</c>). While preparing the kernel source tree, genkernel will refrain "
+"from cleaning out any preexisting object files present in the source tree "
+"(<c>--no-clean</c>). A menu-driven kernel configuration utility will be "
+"displayed that allows the user to select which modules will be built for the "
+"system (<c>--menuconfig</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):122
+msgid ""
+"There are other flags which alter the result provided by genkernel. For "
+"instance, replacing <c>--no install</c> with the <c>--install</c> flag "
+"allows genkernel to automatically install the new kernel in the <path>/boot</"
+"path> directory. Using the <c>--mountboot</c> flag allows genkernel to mount "
+"your <path>/boot</path> partition automatically, if necessary."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):130
+msgid ""
+"Remember, genkernel is designed to make kernel compilation easy and stress-"
+"free. For this reason, genkernel features several flags to ease the kernel "
+"compilation effort. For example, there are flags to help with kernel "
+"configuration, while others affect the actual compilation. Some flags even "
+"help debug the compilation process. For those interested in further "
+"optimization, there are flags that affect kernel assembling, packaging and "
+"even kernel initialization."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):140
+msgid ""
+"The rest of this chapter examines the functionality of various flags and "
+"actions available for genkernel. Some of the flags have variants which "
+"perform a converse operation. The converse variants carry the <b><c>no-</c></"
+"b> prefix, and their effects are enclosed within the square brackets, []."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):150
+msgid "Configuration Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):153
+msgid ""
+"The configuration flags listed below exist to help you decide what features "
+"should be enabled or disabled in the kernel prior to compilation. You can "
+"even choose whether or not the configuration file created in the process "
+"should be saved. The following are the primary configuration flags:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):161
+msgid ""
+"<b>--<c>no-</c>menuconfig</b>: Activates <e>[or deactivates]</e> the <c>make "
+"menuconfig</c> command (which invokes an interactive, menu-based kernel "
+"configuration utility), before building the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):166
+msgid ""
+"<b>--gconfig</b>: Provides a kernel configuration utility which depends on "
+"the GTK+ libraries. The advantage of this option is that most users find it "
+"easier and clearer to configure the kernel using this tool, since it relies "
+"on the X-windowing system. The disadvantage of this option is that you "
+"<b>need</b> the X-windowing system to use it, so it will not work on the "
+"command line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):174
+msgid ""
+"<b>--xconfig</b>: Provides a kernel configuration utility which depends on "
+"the QT libraries. The advantage of this option is that most users find it "
+"easier and clearer to configure the kernel using this tool, since it relies "
+"on the X-windowing system. The disadvantage of this option is that you "
+"<b>need</b> the X-windowing system to use it, so it will not work on the "
+"command line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):182
+msgid ""
+"<b>--<c>no-</c>save-config</b>: Saves <e>[or does not save]</e> the kernel "
+"configuration to a file in the <path>/etc/kernels/</path> directory for "
+"later use."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):192
+msgid "Compilation Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):195
+msgid "The following flags usually take effect during the actual compilation:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):200
+msgid ""
+"<b>--kerneldir=<path>/path/to/sources/</path></b>: Specifies an alternative "
+"kernel source location, rather than the default <path>/usr/src/linux/</path> "
+"location."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):205
+msgid ""
+"<b>--kernel-config=<path>/path/to/config-file</path></b>: Specifies what "
+"alternative kernel configuration will be used, rather than the default "
+"<path>/path/to/sources/.config</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):210
+msgid ""
+"<b>--module-prefix=<path>/path/to/prefix-directory/</path></b>: Specifies a "
+"prefix to the directory where kernel modules will be installed (default path "
+"is the <path>/lib/modules/</path> directory.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):218
+msgid ""
+"<b>--<c>no-</c>clean</b>: Activates <e>[or deactivates]</e> the <c>make "
+"clean</c> command before compiling your kernel. The <c>make clean</c> "
+"command removes all object files and dependencies from the kernel's source "
+"tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):224
+msgid ""
+"<b>--<c>no-</c>mrproper</b>: Activates <e>[or deactivates]</e> the <c>make "
+"mrproper</c> command before kernel compilation. Like the <c>make clean</c> "
+"command, <c>make mrproper</c> removes all object files and dependencies from "
+"the kernel's source tree. However, any previous configuration files (in "
+"<path>/path/to/sources/.config</path> or <path>/path/to/sources/.config.old</"
+"path>) will <b>also</b> be purged from the kernel's source tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):233
+msgid ""
+"<b>--oldconfig</b>: Issues the <c>make oldconfig</c> command, which attempts "
+"to collect configuration information for the system's architecture from a "
+"generic script in <path>/usr/share/genkernel/</path>. This is a non-"
+"interactive process; no user input is entertained. Also, if <c>--oldconfig</"
+"c> is used in conjunction with <c>--clean</c>, the latter flag is negated, "
+"resulting in the activation of the <c>--no-clean</c> flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):244
+msgid ""
+"<b>--callback=\"<c>echo hello</c>\"</b>: Calls the specified arguments "
+"(<c>echo hello</c>, in this case) after the kernel and the relevant modules "
+"have been built, but before building the initrd image. This may be useful if "
+"you want to install external modules in the initrd image by emerging the "
+"relevant item(s) with the callback feature, and then redefining a genkernel "
+"module group."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):255
+msgid ""
+"<b>--<c>no-</c>install</b>: Activates <e>[or deactivates]</e> the <c>make "
+"install</c> command, which installs your new kernel image, configuration "
+"file, initrd image and system map onto your mounted boot partition. Any "
+"compiled modules will be installed as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):261
+msgid ""
+"<b>--<c>no-</c>initrdmodules</b>: Refrains from copying any modules to the "
+"genkernel-created initrd image. This flag is an exception to the rule about "
+"the <c>no-</c> prefix; omission of this prefix creates an invalid genkernel "
+"flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):267
+msgid ""
+"<b>--genzimage</b>: Creates the initrd image, prior to the kernel image. "
+"(This hack currently applies only to PPC Pegasos systems.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):276
+msgid "Compiler Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):279
+msgid ""
+"The following flags are supported by genkernel, and are passed to the "
+"relevant applications while the kernel is being assembled. These flags "
+"affect the <e>compiler</e> used for the kernel compilation process, albeit "
+"at a much lower level."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):287
+msgid ""
+"<b>--kernel-cc=<c>someCompiler</c></b>: Specifies the compiler employed "
+"during the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):291
+msgid ""
+"<b>--kernel-ld=<c>someLinker</c></b>: Specifies the linker employed during "
+"the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):295
+msgid ""
+"<b>--kernel-as=<c>someAssembler</c></b>: Specifies the assembler employed "
+"during the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):299
+msgid ""
+"<b>--kernel-make=<c>someMake</c></b>: Specifies an alternative to the <e>GNU "
+"make</e> utility employed during the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):306
+msgid ""
+"<b>--utils-cc=<c>someCompiler</c></b>: Specifies the compiler employed "
+"during the compilation of support utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):310
+msgid ""
+"<b>--utils-ld=<c>someLinker</c></b>: Specifies the linker employed during "
+"the compilation of support utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):314
+msgid ""
+"<b>--utils-as=<c>someAssembler</c></b>: Specifies the assembler employed "
+"during the compilation of support utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):318
+msgid ""
+"<b>--utils-make=<c>someMake</c></b>: Specifies an alternative to the <e>GNU "
+"make</e> utility employed during the compilation of support utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):325
+msgid ""
+"<b>--makeopts=<c>-jX</c></b>: Specifies the number of concurrent threads "
+"that the make utility can implement while the kernel (and utilities) are "
+"being compiled. The variable <b>'X'</b> is a number obtained by adding one "
+"(1) to the number of CPUs used by the system. So, for a system with one CPU, "
+"the appropriate flag is <c>-j2</c>; a system with two CPUs will use the <c>-"
+"j3</c> flag, and so on. <e>(A system with one processor that supports Hyper-"
+"Threading&trade; (HT) Technology can use the </e><c>-j3</c><e> flag, "
+"provided Symmetric Multi-Processing (SMP) support is enabled in the kernel.)"
+"</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):341
+msgid "Debugging Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):344
+msgid ""
+"The use of debugging flags during the kernel compilation process controls "
+"the amount of information reported, as well as the presentation of said data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):350
+msgid ""
+"<b>--debuglevel=<c>verblevel</c></b>: Controls the level of verbosity for "
+"information provided by genkernel. The variable <c>verblevel</c> is an "
+"integer between 0 and 5. The level '0' represents minimal output, while '5' "
+"provides as much information as possible about genkernel's activities during "
+"the kernel compilation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):357
+msgid ""
+"<b>--debugfile=<path>/path/to/outputfile</path></b>: Ignores the value set "
+"by the <c>--debuglevel</c> argument, and sends <b>all</b> debugging data "
+"produced by genkernel to the specified output file, which is located at "
+"<path>/var/log/genkernel.log</path> by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):363
+msgid ""
+"<b>--no-color</b>: Activates <e>[or deactivates]</e> colored output of "
+"debugging information (reported by genkernel) using escape sequences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):373
+msgid "Initialization Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):376
+msgid ""
+"The flags here are used to create certain effects during system startup. "
+"Some of these flags are primarily for aesthetics, while others may be "
+"essential for enabling certain features on the system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):383
+msgid ""
+"<b>--<c>no-</c>splash</b>: Activates <e>[or deactivates]</e> support for "
+"<uri link=\"http://fbsplash.berlios.de/wiki/doku.php\">framebuffer splash</"
+"uri> support in the genkernel-built initrd image. To override the default "
+"theme used by fbsplash, use <b>--splash=<c>PreferredTheme</c></b> (where "
+"<c>PreferredTheme</c> is the title of one of the directories inside the "
+"<path>/etc/splash/</path> directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):391
+msgid ""
+"<b>--splash-res=<c>PreferredResolution</c></b>: This flag allows you to "
+"select which splash screen resolutions will be supported in the initrd "
+"during the start-up of the system. This is useful for two reasons: First, "
+"you are able to select only the splash screen resolution(s) relevant to your "
+"system. Second, you avoid the unnecessary increase in the disk space "
+"required by initrd (since the initrd does not have to support resolutions "
+"that are irrelevant for your system configuration.) However, you may want to "
+"omit this flag if the kernel is being compiled for an Installation CD; this "
+"allows splash support for all possible resolutions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):402
+msgid ""
+"<b>--do-keymap-auto</b>: Force keymap selection during the boot sequence."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):405
+msgid ""
+"<b>--lvm2</b>: Includes support for storage using via <uri link=\"http://"
+"sources.redhat.com/lvm2/\">Logical Volume Management</uri> (LVM2) from "
+"<e>static</e> binaries, if available to the system. Relevant (static) LVM2 "
+"binaries are compiled if they are unavailable. Be sure to install the lvm2 "
+"package on your system with <c>emerge lvm2</c> before enabling this flag, "
+"and review the <uri link=\"/doc/en/lvm2.xml\">Gentoo LVM2 Installation</uri> "
+"guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):414
+msgid ""
+"<b>--evms2</b>: Includes support for storage using the <uri link=\"http://"
+"evms.sourceforge.net/\">Enterprise Volume Management System</uri> (EVMS2), "
+"if available. Be sure to install the evms package on your system with "
+"<c>USE=static emerge evms2</c> before using this (genkernel) flag. <e>"
+"(Omitting the </e><c>USE=static</c><e> flag during package installation will "
+"fail to include the necessary static binaries.)</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):423
+msgid ""
+"<b>--dmraid</b>: Includes support for <uri link=\"http://people.redhat.com/"
+"~heinzm/sw/dmraid/readme\">DMRAID</uri>; the utility which creates RAID "
+"mappings using the kernel device-mapper subsystem. DMRAID discovers, "
+"activates, deactivates and displays properties of software RAID sets "
+"(ATARAID, for example) and contained DOS partitions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):430
+msgid ""
+"<b>--luks</b>: Includes support for <uri link=\"http://luks.endorphin.org/"
+"\">Linux Unified Key Setup</uri> or LUKS. This will allow you to use a "
+"device encrypted by LUKS which contains the root filesystem. On the "
+"bootloader, you then set that encrypted device as the value of crypt_root "
+"(and real_root shall be the unencrypted device LUKS creates)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):438
+msgid ""
+"<b>--linuxrc=/path/to/your/linuxrc</b>: Specifies a user-created <e>linuxrc</"
+"e>&mdash; a script that is initialized during the start-up stage of the "
+"kernel, prior to the actual boot process. (A default linuxrc script should "
+"be in the <path>/usr/share/genkernel/</path> directory.) This script allows "
+"you to boot into a small, modularized kernel and load the drivers that are "
+"needed (as modules) by the system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):446
+msgid ""
+"<b>--cachedir=/path/to/alt/dir/</b>: Overrides the default cache location "
+"used while compiling the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):450
+msgid ""
+"<b>--tempdir=/path/to/new/tempdir/</b>: Specifies the location of the "
+"temporary directory used by genkernel while compiling the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):454
+msgid ""
+"<b>--unionfs</b>: Includes support for the <uri link=\"http://www.fsl.cs."
+"sunysb.edu/project-unionfs.html\">Unification File System</uri> in the "
+"initrd image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):464
+msgid "Miscellaneous Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):467
+msgid ""
+"The assortment of flags listed below are supported by genkernel, but do not "
+"fit neatly into any of the other categories:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):473
+msgid ""
+"<b>--mountboot</b>: Detects whether or not the <path>/boot/</path> directory "
+"needs to be mounted on a separate partition. It will check <path>/etc/fstab</"
+"path> script for instructions on how to mount the boot partition on a file "
+"system (if needed)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):479
+msgid ""
+"<b>--kernname=<c>NickName</c></b>: Allows you to modify the name of the "
+"kernel and initrd images in the <path>/boot/</path> directory, so that the "
+"images produced are kernel-<c>NickName</c>-version and initramfs-"
+"<c>NickName</c>-version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):490
+msgid "Possible Actions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):493
+msgid ""
+"An action tells genkernel what to build. Currently, the following actions "
+"are supported:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):499
+msgid "<c>initrd</c>: Only builds the initrd image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):500
+msgid "<c>bzImage</c>: Only builds the kernel image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):501
+msgid "<c>kernel</c>: Only builds the kernel image and modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):502
+msgid ""
+"<c>all</c>: Builds all stages &mdash; the initrd, kernel image and modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):507
+msgid ""
+"The last action, <c>all</c>, is recommended for most users since it builds "
+"the stages required for a functional kernel. Remember, an <e>action</e> "
+"simply tells genkernel what to <e>build</e>, not <e>install</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):516
+msgid "Bootloader Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):519
+msgid ""
+"To set up genkernel to work with your bootloader, three or four changes "
+"should be applied to the bootloader's configuration file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):525
+msgid ""
+"Add <c>root=/dev/ram0</c> and <c>init=/linuxrc</c> to the kernel parameters "
+"passed to the kernel image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):529
+msgid ""
+"Add <c>real_root=/dev/hda3</c>, for example, to the kernel parameters passed "
+"to the kernel image, if <path>/dev/hda3</path> contains your root partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):534
+msgid ""
+"If you are using splash, add a suitable mode line such as <c>vga=0x317</c> "
+"to the parameters passed to the kernel and also add <c>splash=verbose</c> or "
+"<c>splash=silent</c> depending on the verboseness you require from your "
+"bootloader."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):540
+msgid ""
+"Add the initrd information as required by the bootloader. Consult the <uri "
+"link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=10\">Bootloader "
+"Configuration Chapter</uri> of the Gentoo Handbook for details on how to "
+"make your bootloader initrd-aware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):553
+msgid "Configuration Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):555
+msgid "Editing /etc/genkernel.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):558
+msgid ""
+"Passing flags to genkernel from the command line can be cumbersome, "
+"especially if you have about a dozen flags:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):563
+msgid "Running genkernel (overloaded with flags)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):563
+#, no-wrap
+msgid ""
+"\n"
+"# <i>genkernel --debuglevel=5 --no-color --no-mrproper --clean --splash \\\n"
+"--kerneldir=/path/to/alternate/kernel/sources --install --menuconfig \\\n"
+"--kernel-config=/path/to/preferred/configfile --save-config --mountboot all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):569
+msgid ""
+"Fortunately, there is a configuration file where most of the basic options "
+"can be set (or changed) as necessary. What follows is a rundown of the more "
+"relevant options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):576
+msgid ""
+"<b>MENUCONFIG=<c>[yes|no]</c></b>: This option is equivalent to the <c>--"
+"menuconfig</c> flag used by genkernel, which in turn uses the <c>make "
+"menuconfig</c> command to invoke a command-line based kernel configuration "
+"utility. To invoke the utility automatically during kernel configuration via "
+"this script, set this option to 'yes' here; otherwise, choose 'no'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):583
+msgid ""
+"<b>CLEAN=<c>[yes|no]</c></b>: Setting this option to 'yes' is equivalent to "
+"the <c>--clean</c> flag used by genkernel, and invokes the <c>make clean</c> "
+"command to remove all object files and dependencies from the kernel's source "
+"tree. Setting this option to 'no' creates a cascade effect — it is "
+"equivalent to genkernel's <c>--no-clean</c> flag, which disables the <c>make "
+"clean</c> command and implies genkernel's <c>--no-mrproper</c> flag &mdash; "
+"essentially nullifying the <c>make mrproper</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):593
+msgid ""
+"<b>MRPROPER=<c>[yes|no]</c></b>: Setting this option to 'yes' is equivalent "
+"to <c>--mrproper</c> flag used by genkernel, and invokes the <c>make "
+"mrproper</c> command, which purges the kernel source tree of any "
+"configuration files. Selecting 'no' here is equivalent to genkernel's <c>--"
+"no-mrproper</c> flag, which disables the <c>make mrproper</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):600
+msgid ""
+"<b>MOUNTBOOT=<c>[yes|no]</c></b>: Setting this option to 'yes' is equivalent "
+"to the <c>--mountboot</c> flag, and automatically mounts the <path>/boot/</"
+"path> directory (if needed) at compile time. If the <path>/boot/</path> "
+"directory is on a separate partition, consider enabling this option; it will "
+"make for one less (essential) step to remember later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):607
+msgid ""
+"<b>SAVE_CONFIG=<c>[yes|no]</c></b>: After configuring the kernel, the "
+"selected options are stored as <path>.config</path> in the kernel source "
+"tree. This script may be overwritten during the next kernel compilation, or "
+"even purged from the kernel source tree. Choosing 'yes' here is equivalent "
+"to the <c>--save-config</c> flag, and stores all options selected during "
+"kernel configuration as a script in the <path>/etc/kernels/</path> "
+"directory. Choosing 'no' preserves the <e>status quo</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):616
+msgid ""
+"<b>USECOLOR=<c>[yes|no]</c></b>: Setting this option to 'yes' is equivalent "
+"to the <c>--color</c> flag, which colors genkernel's output to ease "
+"debugging (when needed.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(li):621
+msgid ""
+"<b>DEBUGLEVEL=<c>[0|1|2|3|4|5]</c></b>: This option is for adjusting the "
+"verbosity of the output produced by genkernel &mdash; setting this option to "
+"'0' with <c>--debuglevel=0</c> will suppress all output produced by "
+"genkernel; setting this option to '5' with <c>--debuglevel=5</c> provides "
+"the user with all output produced by genkernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):630
+msgid ""
+"By choosing the appropriate options in <path>/etc/genkernel.conf</path>, you "
+"can halve the number of flags passed to genkernel from the command line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):635
+msgid "Running genkernel (with flags), after employing genkernel.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):635
+#, no-wrap
+msgid ""
+"\n"
+"# <i>genkernel --splash --kerneldir=/path/to/alternate/kernel/sources \\\n"
+"--kernel-config=/path/to/preferred/configfile --install all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):640
+msgid ""
+"Identical results are obtained from both approaches, but the latter has most "
+"of the options stored in a script that can be modified at a later date."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):650
+msgid "Network-Booting with genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):652
+msgid "Network Booting from an Installation CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):655
+msgid ""
+"The genkernel utility can build kernel and initrd images that provide "
+"support for network booting, or <e>netboot</e>ing. With any luck, you should "
+"be able to netboot any recent computer into the environment provided by the "
+"Installation CD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):662
+msgid ""
+"The magic lies in genkernel's linuxrc script: it will try to <e>netmount</e> "
+"the Installation CD using NFS. From there, <e>the init scripts</e> of the "
+"Installation CD can take over, as if the CD was present locally."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):671
+msgid "Building Kernel and Initrd Images with Support for Netbooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):674
+msgid ""
+"To enable support for netbooting, include the following options while "
+"configuring the kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(warn):679
+msgid ""
+"Support for netbooting with genkernel is experimental and may contain bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):683
+msgid ""
+"First, the kernel image must include the drivers for your Network Interface "
+"Cards (NIC). Normally, drivers for such devices will be compiled as modules. "
+"However, it is essential (for netbooting) that you have such drivers "
+"compiled directly into the kernel image and <b>not</b> as modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):690
+msgid "Configuring a 2.6.x series kernel to support your NIC driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):690
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"   Networking Support ---&gt;\n"
+"      Ethernet (10 or 100Mbit)  ---&gt;\n"
+"         [*] Ethernet (10 or 100Mbit)\n"
+"         &lt;*&gt;   the driver for your network card\n"
+"<comment>(Be sure to select &lt;*&gt; and not &lt;M&gt;)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):699
+msgid ""
+"Secondly, we suggest that you enable <c>IP: kernel level autoconfiguration</"
+"c> and the <c>IP: DHCP support</c> options. This avoids an unnecessary layer "
+"of complexity since the IP address and the NFS path to the Installation CD "
+"can be configured on a DHCP server. Of course, this means the kernel command "
+"line will remain constant for any machine &mdash; which is very important "
+"for <e>etherbooting</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):708
+msgid "Configuring a 2.6.x series kernel to support DHCP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):708
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"   Networking Support ---&gt;\n"
+"      Networking options\n"
+"         [*] TCP/IP networking---&gt;\n"
+"         [*]   IP: kernel level autoconfiguration\n"
+"         [*]     IP: DHCP support\n"
+"<comment>(These options tell the kernel to send a DHCP request at bootup.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):718
+msgid ""
+"Additionally, you should enable SquashFS because most modern Gentoo "
+"Installation CDs require it. Support for SquashFS is not included with the "
+"generic kernel source tree. To enable SquashFS, apply the necessary patches "
+"to the generic kernel source or install <c>gentoo-sources</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):725
+msgid "Configuring the kernel to support SquashFS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):725
+#, no-wrap
+msgid ""
+"\n"
+"File systems---&gt;\n"
+"   Miscellaneous filesystems ---&gt;\n"
+"      [*] SquashFS 2.X - Squashed file system support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):731
+msgid ""
+"Once the compilation process is completed, create a compressed <e>tarball</"
+"e> (tar.gz) that contains the kernel's modules. This step is only necessary "
+"if your kernel version does not match the kernel image version on the "
+"Installation CD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):738
+msgid "Creating a compressed tarball containing the kernel modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):738
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Create a tar.gz containing all the modules)</comment>\n"
+"# <i>cd /</i>\n"
+"# <i>tar -cf /tmp/modules-X.Y.Z.tar.gz /lib/modules/X.Y.Z/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):744
+msgid ""
+"Depending on your network boot mechanism, you will need to do some of the "
+"following steps:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):749
+msgid "Creating a boot image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):749
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Create an etherboot image)</comment>\n"
+"# <i>emerge mknbi</i>\n"
+"# <i>cd /boot</i>\n"
+"# <i>mkelf-linux -params=\"root=/dev/ram0 init=/linuxrc ip=dhcp\" kernel... initrd... &gt; etherboot.img</i>\n"
+"\n"
+"<comment>(Create a OpenBoot / SPARC64 TFTP image)</comment>\n"
+"# <i>emerge sparc-utils</i>\n"
+"# <i>cd /boot</i>\n"
+"# <i>elftoaout kernel... -o kernel.aout</i>\n"
+"# <i>piggyback64 kernel.aout System.map-... initrd-...</i>\n"
+"# <i>mv kernel.aout openboot.img</i> <comment>(This is the boot image)</comment>\n"
+"\n"
+"<comment>(PXE does not need any more steps, the kernel and initrd can be used as is)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):765
+msgid ""
+"Finally, copy this kernel to your TFTP server. The details are architecture-"
+"dependent and are beyond the scope of this guide. Please refer to the "
+"documentation for your platform."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):774
+msgid "NFS Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):777
+msgid ""
+"To setup a NFS share that contains the Installation CD, use the loop device "
+"to mount the ISO image and then copy the contents of the CD into the NFS "
+"share. As a nice extra, genkernel's initrd scripts will extract all tar.gz "
+"files located in the <path>/nfs/livecd/add/</path> directory. All you have "
+"to do here is copy the <c>modules-X.Y.Z.tar.gz</c> archive to the <path>/nfs/"
+"livecd/add/</path> directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):786
+msgid "Preparing the NFS share"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):786
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(This assumes that /nfs/livecd is an exported NFS share)</comment>\n"
+"# <i>mount /tmp/gentoo-livecd.iso /mnt/cdrom -o loop</i>\n"
+"# <i>cp -p /mnt/cdrom /nfs/livecd</i>\n"
+"# <i>umount /mnt/cdrom</i>\n"
+"\n"
+"<comment>(Copy the modules.tar.gz into /add)</comment>\n"
+"# <i>mkdir /nfs/livecd/add</i>\n"
+"# <i>cp /tmp/modules-X.Y.Z.tar.gz /nfs/livecd/add</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):800
+msgid "DHCP Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):803
+msgid ""
+"The netboot images will ask your DHCP server for an IP as well as a root-"
+"path parameter. Both can be specified per host using a MAC address to "
+"identify machines:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):809
+msgid "Sample client dhcpd.conf setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):809
+#, no-wrap
+msgid ""
+"\n"
+"...\n"
+"\n"
+"host netbootableMachine {\n"
+"         hardware ethernet 11:22:33:44:55:66;\n"
+"         fixed-address 192.168.1.10;\n"
+"         option root-path \"192.168.1.2:/nfs/livecd\";\n"
+"}\n"
+"<comment># Here, 192.168.1.2 is the NFS server\n"
+"# While 192.168.1.10 will be the IP address of the netbooted machine</comment>\n"
+"...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):825
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre:caption):836
+msgid "Netbooting Instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):828
+msgid ""
+"Netbooting itself is again very platform-specific. The important part is to "
+"specify the <c>ip=dhcp</c> and <c>init=/linuxrc</c> parameters on the kernel "
+"command line, as this will bring up the network interface and tell the "
+"initrd scripts to mount the Installation CD via NFS. Here are some platform-"
+"specific tips:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(pre):836
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Etherboot - insert the etherboot disk into the drive and reboot\n"
+"# The kernel command line was specified when the image was constructed</comment>\n"
+"\n"
+"<comment># Sparc64 - Hit Stop-A at the boot prompt</comment>\n"
+"ok boot net ip=dhcp init=/linuxrc\n"
+"\n"
+"<comment># PXE - Setup pxelinux (part of syslinux),\n"
+"then create a pxelinux.cfg/default along the lines of:</comment>\n"
+"\n"
+"DEFAULT gentoo\n"
+"TIMEOUT 40\n"
+"PROMPT 1\n"
+"\n"
+"LABEL gentoo\n"
+"    KERNEL kernel-X.Y.Z\n"
+"    APPEND initrd=initrd-X.Y.Z root=/dev/ram0 init=/linuxrc ip=dhcp\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):860
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):862
+msgid "To Automate or not to Automate?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(p):865
+msgid ""
+"The purpose of genkernel is to provide an (easier) alternative to the time-"
+"tested approach to kernel compilation. As always, you are free to decide on "
+"whether or not you want to automate the kernel compilation process."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-alpha-faq.xml.po b/doc/gettext/ru/gentoo-alpha-faq.xml.po
new file mode 100644
index 0000000..1efa054
--- /dev/null
+++ b/doc/gettext/ru/gentoo-alpha-faq.xml.po
@@ -0,0 +1,674 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(guide:link):5
+msgid "/doc/en/gentoo-alpha-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):7
+msgid "Gentoo Linux/Alpha Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail:link):9
+msgid "tcort@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail):9
+msgid "Thomas Cort"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail:link):12
+msgid "grknight2k@bluebottle.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail):12
+msgid "Brian Evans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(abstract):18
+msgid ""
+"This FAQ is intended to answer some of the most frequently asked questions "
+"relating to Gentoo/Alpha and Linux/Alpha in general."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(version):27
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(date):28
+msgid "2008-01-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):31
+msgid "About this Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):34
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):37
+msgid ""
+"This document contains answers to the most commonly asked questions about "
+"Gentoo/Alpha and Alpha/Linux. It's aimed at both new users and experienced "
+"users alike."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):48
+msgid "About the Gentoo/Alpha Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):50
+msgid "What is Gentoo/Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):53
+msgid ""
+"The Gentoo/Alpha project is responsible for keeping the Gentoo distribution "
+"updated and current for the Alpha platform. This primarily includes "
+"keywording packages, porting software, and making new releases. The Gentoo/"
+"Alpha project aims to provide a usable environment for both desktops and "
+"servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):63
+msgid "What is the current status of the Gentoo/Alpha Project?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):66
+msgid ""
+"You can find out about the current status of the Gentoo/Alpha project via "
+"status reports. These reports inform the public about what we've been up to. "
+"New status reports will be posted about once every 6 months. Current and "
+"past status report can be found on the <uri link=\"/proj/en/base/alpha/"
+"status/index.xml\">Status Reports Project page</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):79
+msgid "The Alpha Architecture"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):81
+msgid "Isn't the Alpha architecture dead?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):84
+msgid ""
+"Not quite! HP stopped taking orders for new Alpha systems on April 27, 2007. "
+"They will take orders for Alpha options and upgrades until April 25, 2008. "
+"See their <uri link=\"http://h18002.www1.hp.com/alphaserver/evolution.html"
+"\">planning page</uri> for more details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):94
+msgid "Can I run 32-bit applications?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):97
+msgid ""
+"No, all Alpha systems use a pure 64 bit kernel and a pure 64 bit userland. "
+"You cannot even force gcc to output 32 bit code using the <c>-m32</c> "
+"compiler flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):106
+msgid "Is Alpha big endian or little endian?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):109
+msgid ""
+"All Alpha systems support both little and big endian. However, Linux only "
+"uses little endian."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):117
+msgid "Can I run Linux/x86 applications on Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):120
+msgid ""
+"No, not without a full x86 system emulator like <uri link=\"http://bochs."
+"sourceforge.net/\">bochs</uri>. In the past DEC/Compaq/HP maintained a "
+"program called <c>em86</c> which allowed Linux/x86 applications to be run on "
+"Linux/Alpha systems. However, the program is closed source and no longer "
+"maintained upstream. There are no <c>em86</c> binaries available that are "
+"compatible with gcc3's ABI."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):132
+msgid "Why install Gentoo on Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):135
+msgid ""
+"Admittedly, you can find faster 64-bit systems out there, like amd64. "
+"However, that doesn't mean that Alpha systems are useless. The following are "
+"a few good reasons why you'd want to install Linux on this sort of hardware:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):142
+msgid ""
+"You can turn an old computer into something useful. Older Alphas make great "
+"routers and servers. Their desktop performance isn't that bad either."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):146
+msgid "You will learn about unusual computer hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):147
+msgid ""
+"It's cool. How many people can say they've got Linux running on an Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):155
+msgid "Where can I buy Alpha hardware?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):158
+msgid ""
+"Alpha hardware generally isn't available at your local computer store. If "
+"you want a new Alpha you're going to have to contact <uri link=\"http://"
+"h18002.www1.hp.com/alphaserver/\">HP</uri>. If you want a used Alpha (more "
+"economical), <uri link=\"http://ebay.com\">eBay</uri> is usually a good "
+"option, assuming that the shipping doesn't cost you too much. There are "
+"several used equipment dealers that can be found via google, however most of "
+"them charge too much."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):173
+msgid "Hardware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):175
+msgid ""
+"I opened up the case on an AlphaServer and now it won't power on, what do I "
+"do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):179
+msgid ""
+"Make sure the top panel of the case is on and properly in place. The middle "
+"of the top panel of the case has a small piece of metal oriented downwards. "
+"When the top panel is put back in place properly, the small piece of metal "
+"will press down on a switch. When the switch isn't pressed down, the system "
+"will refuse to power on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):192
+msgid "Alpha Specific Compiler Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):194
+msgid "Is the use of Alpha specific compiler flags recommended?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):197
+msgid ""
+"As with all compiler optimizations, don't over do it. Use these flags with "
+"care and they will give you a stable, speedy system; use them too "
+"aggressively and you could seriously break your system. When in doubt, leave "
+"it out. If you need further clarification, check the <c>gcc</c> man page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):207
+msgid "How do I optimize for a specific instruction set and scheduling model?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):212
+msgid ""
+"You can optimize for a specific instruction set and scheduling model with "
+"<c>-mcpu=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</"
+"c>, <c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and "
+"<c>ev67</c>. If you do not use the <c>-mcpu=XXX</c> flag, then <c>gcc</c> "
+"will default to the cpu type of the machine it was compiled on. <c>-mcpu=</"
+"c> is equivalent to the <c>-march=</c> flag on x86."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(note):221
+msgid ""
+"AlphaServer 800 users should set <c>ev5</c>. There are known issues setting "
+"<c>ev56</c> particularly with Xorg causing a full system lock up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):229
+msgid ""
+"How do I specify the scheduling model without changing the instruction set?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):234
+msgid ""
+"You can specify the scheduling model without changing the instruction set "
+"with <c>-mtune=XXX</c>, where XXX is your cpu type. Valid cpu types are "
+"<c>ev4</c>, <c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> "
+"and <c>ev67</c>. <c>-mtune=</c> is implied by <c>-mcpu=</c>, so you don't "
+"need to specify this with if you set <c>-mcpu=</c>. <c>-mtune=</c> is "
+"equivalent to the <c>-mcpu=</c> flag on x86."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):246
+msgid "How do I enable software assisted floating point numbers?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):249
+msgid ""
+"You can enable software assisted floating point numbers with <c>-mieee</c>. "
+"This will enable software assistance to correctly support denormalized "
+"numbers and exceptional IEEE values such as not-a-number and plus/minus "
+"infinity."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):255
+msgid ""
+"This should be in your global <c>CFLAGS</c> unless you really know what you "
+"are doing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):263
+msgid "How do I specify the memory latency of my system?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):266
+msgid ""
+"You can specify the memory latency of your system with <c>-mmemory-"
+"latency=XXX</c>, where XXX is the number of clock cycles. This sets the "
+"latency time that the scheduler should assume for memory references. <c>gcc</"
+"c> has some predefined \"typical\" values that are also accepted by <c>-"
+"mmemory-latency=XXX</c>. Those values are <c>L1</c> for Dcache, <c>L2</c> "
+"for Scache, <c>L3</c> for Bcache, and <c>main</c> for main memory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):275
+msgid ""
+"This flag should probably not be use in your global <c>CFLAGS</c> as the "
+"value you choose is highly dependent on the memory access pattern of the "
+"application you are compiling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):284
+msgid ""
+"How do I specify that static data should be placed in the small data area?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):289
+msgid ""
+"You can specify that static data should be placed in the small data area "
+"with <c>-msmall-data</c>. This will cause <c>gcc</c> to take advantage of "
+"some features of the Alpha architecture by storing heavily used pieces of "
+"data in specific sections called the small memory sections. The sections are "
+"limited to 64kb which means accessing anything stored in them will only take "
+"one instruction."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):298
+msgid ""
+"<c>-fPIC</c> will override <c>-msmall-data</c>, so you should use the <c>-"
+"fpic</c> flag instead if you do not want <c>-msmall-data</c> to be "
+"overridden."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):304
+msgid ""
+"This flag should probably not be used in your global <c>CFLAGS</c> as some "
+"objects require more than 64kb to be stored, and this will cause a "
+"gp_overflow ld error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):313
+msgid ""
+"How do I specify that object code should be placed in the small text area?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):318
+msgid ""
+"You can specify that object code should be placed in the small text area "
+"with <c>-msmall-text</c>. This will cause <c>gcc</c> to assume that the "
+"entire program (or library) fits in 4MB, and is thus reachable with a branch "
+"instruction. This reduces the number of instructions required for a function "
+"call from 4 to 1."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):326
+msgid ""
+"This flag should probably not be used in your global <c>CFLAGS</c> as some "
+"programs (or libraries) are larger than 4MB, and this will cause an ld error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):334
+msgid ""
+"What do I do if any of these compiler flags cause a compile, linker, or "
+"runtime error?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):340
+msgid ""
+"As <uri link=\"#CFLAGS\">already mentioned</uri>, please use these "
+"<c>CFLAGS</c> cautiously. They may break your system. If you experience "
+"problems, try using less aggressive <c>CFLAGS</c> before <uri link=\"#bugs"
+"\">filing a bug report</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):352
+msgid "Alpha Booting and Bootloaders"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):354
+msgid "What is SRM?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):357
+msgid ""
+"SRM is based on the Alpha Console Subsystem specification, which provides an "
+"operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. "
+"See the <uri link=\"http://www.alphalinux.org/faq/SRM-HOWTO/\"> SRM Howto</"
+"uri> for more information about SRM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):367
+msgid "What is ARC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):370
+msgid ""
+"ARC is based on the Advanced RISC Computing (ARC) specification, which "
+"provides an operating environment for Windows NT."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):378
+msgid "How can I tell if which firmware my Alpha has, ARC or SRM?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):381
+msgid ""
+"When you power your system on you will see a screen with a blue background "
+"and white text if it is using SRM. You will see a graphical boot system if "
+"it is using ARC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):390
+msgid "Which bootloader do I use?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):393
+msgid ""
+"If your Alpha system supports SRM, then you should use aboot. If your system "
+"supports both SRM and ARCs (ARC, AlphaBIOS, ARCSBIOS), then you should "
+"follow <uri link=\"http://www.alphalinux.org/faq/x31.html\">the SRM Firmware "
+"Howto</uri> for switching to SRM and use aboot. If your system can only use "
+"ARCs (Ruffian, nautilus, xl, etc.) then you will need to choose milo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):404
+msgid "Can aboot boot kernels from xfs, reiserfs, or jfs partitions?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):407
+msgid ""
+"No, <c>aboot</c> only supports booting kernels from <c>ext2</c> and <c>ext3</"
+"c> partitions. You may still use other files systems for your root "
+"partition, you just need to create a <path>/boot</path> partition with "
+"either <c>ext2</c> or <c>ext3</c> on it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):414
+msgid ""
+"Support for reiserfs and xfs is planned. In fact, there are patches floating "
+"around that add support for those two file systems. However, the use of "
+"those patches is unsupported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):424
+msgid "Software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):427
+msgid "How is Java support in Gentoo/Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):430
+msgid ""
+"There was only one option for Java VM and Java SDK on Gentoo/Alpha. The "
+"packages were called <c>compaq-jre</c> and <c>compaq-jdk</c>. Sadly, Compaq/"
+"HP stopped all support and the packages were removed from Gentoo on October "
+"11, 2006."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):441
+msgid "Will there ever be working Java support?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):444
+msgid ""
+"We really hope so. We are following the development of the jdk from <uri "
+"link=\"http://sablevm.org\">SableVM</uri>. It isn't ready yet, but we hope "
+"with time that it will be a full drop in replacement jdk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):453
+msgid "How is .NET support in Gentoo/Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):456
+msgid ""
+"Neither of the two main open source efforts, <uri link=\"http://www.mono-"
+"project.com/Main_Page\">mono</uri> nor <uri link=\"http://www.dotgnu.org/"
+"\">DotGNU</uri>, support the alpha architecture."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):465
+msgid "What is needed for .NET support?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):468
+msgid ""
+"Bringing .NET to alpha isn't a simple task. It requires coding all of the "
+"assembly language code generation macros for the JIT (just in time) compiler "
+"and coding architecture specific functions (register allocators, etc)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):479
+msgid "Alpha Linux Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):481
+msgid "Which kernel sources should I use?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):484
+msgid ""
+"We recommend using <c>gentoo-sources</c> but <c>vanilla-sources</c> is also "
+"supported by Gentoo/Alpha. You should read the <uri link=\"/doc/en/gentoo-"
+"kernel.xml\">Gentoo Kernel Guide</uri> to determine which one is right for "
+"your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):494
+msgid "My system is broken with kernel-2.6, Can I build a 2.4 bassed system?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):497
+msgid ""
+"Gentoo/Alpha stopped supporting 2.4 kernel and profile in January 2008. "
+"Technically you can build a 2.4 Gentoo System (the kernel is in the tree) "
+"but you will have to mask all the 2.6 only packages by yourself and you "
+"won't have support from developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):504
+msgid ""
+"Gentoo/Alpha will review all bug reports about non working 2.6 systems and "
+"will try to help as much as we can."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):513
+msgid "Are hardened-sources supported?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):516
+msgid ""
+"Short answer is no. They were supported some time ago, but we lost the "
+"hardware and the maintainer so right now they are not supported. If you are "
+"interested and want to continue the initial work, please let us know."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):525
+msgid "Does the 2.6 kernel support Alpha SMP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):528
+msgid ""
+"There were some times in the past when it was broken. However, <c>2.6.15.1</"
+"c> and <c>2.6.16.19</c> are both known to work well. If you find that SMP is "
+"broken and want SMP support you will need revert to the one of the versions "
+"mentioned above or use a 2.4 kernel. If you really need to run the latest "
+"2.6 kernel on an SMP box and you don't care that only one of your processors "
+"is getting used, then you could configure the 2.6 kernel without SMP support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):542
+msgid "Helping out the Gentoo/Alpha Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):544
+msgid "How do I report bugs?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):547
+msgid ""
+"If you find a bug or you want to send us patches, then you need to file a "
+"bug report. It only takes you a little bit of your time, and your help is "
+"really appreciated. Please follow the <uri link=\"/doc/en/bugzilla-howto.xml"
+"\">Gentoo Bug Reporting Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):557
+msgid "How can I help the Gentoo/Alpha Project?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):560
+msgid "Users can help us by:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):565
+msgid "Filing clear and concise <uri link=\"#bugs\">bug reports</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):566
+msgid "Testing software that does not yet have the <c>~alpha</c> keyword."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):567
+msgid ""
+"Answering questions on the <uri link=\"/main/en/lists.xml\">mailing lists</"
+"uri>, <uri link=\"http://forums.gentoo.org/viewforum-f-32.html\"> forum</"
+"uri> and IRC channel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):572
+msgid "Sending patches"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(li):573
+msgid ""
+"Becoming an <uri link=\"http://www.gentoo.org/proj/en/base/alpha/AT/index.xml"
+"\">AT</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):581
+msgid "Is there an Alpha Arch Testers Project?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):584
+msgid ""
+"Yes, see the <uri link=\"http://www.gentoo.org/proj/en/base/alpha/AT/index."
+"xml\"> Gentoo Linux Alpha Arch Testers Project</uri> page for details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):594
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):596
+msgid "Why is my Xorg locking up my Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):599
+msgid ""
+"This is usually caused by a bad -mcpu setting. For example, the AlphaServer "
+"800 needs to be compiled with the <c>ev5</c> flag for xorg <b>and</b> glibc. "
+"Failing to do so will cause undesired results."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):610
+msgid "Other Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):612
+msgid "Why is there no Gentoo on Alpha forum?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):615
+msgid ""
+"On the <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri> there are "
+"several arch specific categories like <uri link=\"http://forums.gentoo.org/"
+"viewforum-f-24.html\">Gentoo on PPC</uri> and <uri link=\"http://forums."
+"gentoo.org/viewforum-f-24.html\">Gentoo on Sparc</uri>. There is no Gentoo "
+"on Alpha category because there simply isn't enough Gentoo/Alpha activity on "
+"the forums to warrant one. All Alpha related posts should go in the <uri "
+"link=\"http://forums.gentoo.org/viewforum-f-32.html\"> Gentoo on Alternative "
+"Architectures</uri> category."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):630
+msgid "Where can I get more help or information about Gentoo/Alpha?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):633
+msgid ""
+"If any of your questions weren't answered here, you can try other resources "
+"like the <uri link=\"/doc/en/handbook/handbook-alpha.xml\">Alpha Handbook</"
+"uri> or <uri link=\"/proj/en/base/alpha/\">our project homepage</uri>. You "
+"can also ask us at <c>#gentoo-alpha</c> on <c>irc.freenode.net</c>, <uri "
+"link=\"http://forums.gentoo.org/viewforum-f-32.html\">Gentoo on Alternative "
+"Architectures Forum</uri>, or on the <mail>gentoo-alpha@lists.gentoo.org</"
+"mail> mailing list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(title):646
+msgid "Where can I get more help or information about Alpha/Linux?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(p):649
+msgid ""
+"<uri link=\"http://alphalinux.org/\">AlphaLinux.org</uri> is a central "
+"repository for all things Alpha/Linux."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-alpha-install.xml.po b/doc/gettext/ru/gentoo-alpha-install.xml.po
new file mode 100644
index 0000000..85439f7
--- /dev/null
+++ b/doc/gettext/ru/gentoo-alpha-install.xml.po
@@ -0,0 +1,60 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(guide:redirect):3
+msgid "/doc/en/handbook/handbook-alpha.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(title):4
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(title):20
+msgid "Gentoo Alpha Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(author:title):6
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(mail:link):7
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(mail):7
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(abstract):10
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(version):16
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(date):17
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(p):24
+msgid ""
+"As of 2004.0, the individual architecture-specific installation guides have "
+"been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/"
+"handbook/handbook-alpha.xml\">Gentoo Handbook</uri>. For more information "
+"please read up on the <uri link=\"/doc/en/handbook\">Gentoo Handbook "
+"Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-alpha-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-amd64-faq.xml.po b/doc/gettext/ru/gentoo-amd64-faq.xml.po
new file mode 100644
index 0000000..340d2fa
--- /dev/null
+++ b/doc/gettext/ru/gentoo-amd64-faq.xml.po
@@ -0,0 +1,475 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):6
+msgid "Gentoo Linux/AMD64 Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):9
+msgid "blubb@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail):9
+msgid "Simon Stelling"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):12
+msgid "metalgod@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail):12
+msgid "Luis Medinas"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):15
+msgid "gerrynjr@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail):15
+msgid "Gerald J. Normandin Jr."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):18
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail):18
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(mail:link):21
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(abstract):24
+msgid "This is the Gentoo Linux/AMD64 Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(version):32
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(date):33
+msgid "2010-07-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):36
+msgid "Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):38
+msgid "Introduction to Gentoo/AMD64 FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):41
+msgid ""
+"This document contains the most commonly asked questions about Gentoo/AMD64. "
+"We intend to help and provide useful information about Gentoo/AMD64. Some of "
+"these questions can be found in forums, IRC, or mailing lists. If you have "
+"suggestions or questions about this FAQ, you are welcome to send an e-mail "
+"to <mail>amd64@gentoo.org</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):54
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):56
+msgid "What's the difference between AMD64 and EM64T?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):59
+msgid ""
+"Both refer to 64-bit processors from AMD (AMD64) and Intel (EM64T). AMD's 64-"
+"bit processors include the Athlon 64, Turion, Neo, Phenom, and Opteron "
+"families. Intel's 64-bit processors include the Core2, Core i<e>X</e>, "
+"Celeron, Xeon, and Pentium (all based on the Core2 architecture). The <uri "
+"link=\"http://en.wikipedia.org/wiki/Em64t#Intel_64\">last few versions</uri> "
+"of the old Pentium 4 and Xeon chips also support EM64T."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):68
+msgid ""
+"The AMD line of 64-bit processors were released well ahead of Intel's "
+"offering. Therefore, for historical reasons the arch keyword for all x86-64 "
+"compatible architectures is amd64. As such, <e>AMD64</e> is a generic "
+"reference to 64-bit chips, whether AMD or Intel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):78
+msgid "What CFLAGS should I use for AMD64/EM64T?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):81
+msgid ""
+"You should use simple <c>CFLAGS</c> to avoid future problems with your "
+"system. Supported <c>CFLAGS</c> are <c>-O2 -march=k8 -pipe</c> for AMD "
+"systems. Intel Core2-based systems (EM64T) should use <c>-O2 -march=core2 -"
+"pipe</c>. If you're on an old Intel Pentium 4 that supports EM64T, then use "
+"<c>-O2 -march=nocona -pipe</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):92
+msgid "What kernel should I use for AMD64?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):95
+msgid ""
+"You can use almost all kernel sources available in Portage. We recommend "
+"using <c>gentoo-sources</c> because it is a special kernel designed for "
+"Gentoo Linux. It contains lots of AMD64-specific patches and therefore is "
+"the only kernel officially supported by Gentoo/AMD64."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(warn):102
+msgid ""
+"You should watch out for some kernel features which are not well tested, "
+"such as <c>PREEMPT</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):107
+msgid ""
+"Make sure you have the <c>IA32_EMULATION</c> option activated in the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre:caption):111
+msgid "Activating IA32 Emulation in Kernel source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre):111
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+"\n"
+"Executable file formats / Emulations  ---&gt;\n"
+"  [*] IA32 Emulation\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(warn):119
+msgid ""
+"You may experience build failures on multilib-systems if you deactivate this "
+"option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):127
+msgid ""
+"Will I have a performance upgrade if I use a 64bit system instead of 32bit?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):130
+msgid ""
+"That is a difficult question to answer. In some cases, you will experience a "
+"performance improvement, in other cases you will not. For everyday use, "
+"there is nearly no difference between 64bit and 32bit. 64bit is generally "
+"faster when it comes to floating point computing which is normally the case "
+"in multimedia applications and 3D rendering. This <uri link=\"http://www."
+"linux.com/articles/114024?tid=121\">article</uri> (and a <uri link=\"http://"
+"www.linux.com/feature/43873\">related</uri> article) may interest you. "
+"There's also a nice <uri link=\"http://forums.gentoo.org/viewtopic-t-349691."
+"html\">thread</uri> in our <uri link=\"http://forums.gentoo.org\">forums</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):146
+msgid "What is multilib and how can I use it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):149
+msgid ""
+"Every AMD64 processor is able to run 32bit code as well as 64bit code. "
+"However, when you have a 32bit application, you are unable to mix it with "
+"64bit libraries or vice versa. You can, however, natively run 32bit "
+"applications if all shared libraries it needs are available as 32bit "
+"objects. You can choose whether you want multilib support or not by "
+"selecting the according profile. The default is a multilib-enabled profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(warn):158
+msgid ""
+"Currently you cannot switch from a no-multilib to a multilib-enabled "
+"profile, so think over your decision twice before you use the no-multilib "
+"profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):166
+msgid "How do I create a 32bit chroot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):169
+msgid ""
+"Please read the <uri link=\"/proj/en/base/amd64/howtos/chroot.xml\">32bit "
+"chroot guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):177
+msgid "Can I upgrade from my x86 system to amd64 by doing emerge -e world?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):180
+msgid ""
+"Due to several differences between an <c>x86</c> and an <c>amd64</c> "
+"installation, it is impossible to upgrade. Please perform a fresh install. "
+"The installation is slightly different than an x86 one, so please use the "
+"<uri link=\"/doc/en/handbook/handbook-amd64.xml\">AMD64 Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):187
+msgid ""
+"Also, binary files created on an x86 system most likely cannot be read by "
+"packages on an amd64 system. In particular, databases such as MySQL, innoDB, "
+"Berkeley DB, SQLite, OpenLDAP, etc. cannot simply be copied as-is. You will "
+"need to dump the database into an architecture-independent format, such as a "
+"text file, before attempting to restore it on an amd64 system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):198
+msgid "Can I use Reiser4?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):201
+msgid ""
+"Reiser4 is not available from any kernel offered by the Gentoo Kernel "
+"project, thus the AMD64 team doesn't support it. The answer is no."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):211
+msgid "Hardware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):213
+msgid "Will my binary NVIDIA/ATI drivers work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):216
+msgid ""
+"Yes, NVIDIA and ATI provide drivers that work on AMD64. You can install them "
+"by executing <c>emerge nvidia-drivers</c> or <c>emerge ati-drivers</c>. If "
+"you have more questions about these drivers, you should read the <uri link="
+"\"/doc/en/nvidia-guide.xml\">Nvidia guide</uri> or the <uri link=\"/doc/en/"
+"ati-faq.xml\">ATI FAQ</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):227
+msgid "How do I use Cool'n'Quiet/PowerNow/SpeedStep features?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):230
+msgid ""
+"You have to compile your kernel with support for these features. You just "
+"need to enable the features below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre:caption):235
+msgid "Kernel options for Cool'n'Quiet/PowerNow/SpeedStep"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre):235
+#, no-wrap
+msgid ""
+"\n"
+"Power management options ---&gt;\n"
+"  [*] Power Management support\n"
+"  [*] ACPI (Advanced Configuration and Power Interface) Support ---&gt;\n"
+"    &lt;*&gt;   Processor\n"
+"    &lt;*&gt;     Thermal Zone\n"
+"  CPU Frequency scaling ---&gt;\n"
+"  [*] CPU Frequency scaling\n"
+"         Default CPUFreq governor (ondemand) ---&gt;\n"
+"  -*-   'performance' governor\n"
+"  &lt;*&gt;   'userspace' governor for userspace frequency scaling\n"
+"  -*-   'ondemand' cpufreq policy governor\n"
+"  &lt;*&gt;   ACPI Processor P-States driver\n"
+"  &lt;*&gt;   AMD Opteron/Athlon64 PowerNow!\n"
+"-*- CPU idle PM support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):252
+msgid ""
+"Then <c>emerge cpufrequtils</c> and edit <path>/etc/conf.d/cpufrequtils</"
+"path> with your favorite editor."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre:caption):257
+msgid "Example of /etc/conf.d/cpufrequtils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre):257
+#, no-wrap
+msgid ""
+"\n"
+"# Options when starting cpufreq (given to the 'cpufreq-set' program)\n"
+"START_OPTS=\"--governor ondemand\"\n"
+"\n"
+"# Options when stopping cpufreq (given to the 'cpufreq-set' program)\n"
+"STOP_OPTS=\"--governor performance\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):265
+msgid ""
+"Now you only have to run <c>rc-update add cpufrequtils boot</c> to make sure "
+"it is started every time you boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(note):270
+msgid ""
+"You may want to read the <uri link=\"/doc/en/power-management-guide."
+"xml#doc_chap3\">Power Management Guide</uri> for more tips on CPU power "
+"management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):281
+msgid "Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):283
+msgid "Can I get Adobe Flash working?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):286
+msgid ""
+"Yes. Just <c>emerge adobe-flash</c>. Be sure to read any messages displayed "
+"by the ebuild once it has been emerged."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):301
+msgid "Can I get OpenOffice.org working?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):304
+msgid ""
+"Yes. Run <c>emerge openoffice</c>. It may take several hours and use most of "
+"your system resources. If you don't think your machine is up to it, you can "
+"try installing the precompiled binary, <c>openoffice-bin</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):313
+msgid ""
+"I want to install package foo, but emerge says: (masked by: ~amd64 keyword)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):316
+msgid ""
+"This means that the package is still in the 'testing' tree. Please read "
+"<c>man portage</c> or the <uri link=\"/doc/en/handbook/handbook-amd64.xml?"
+"part=3&amp;chap=3\">Mixing Software Branches</uri> chapter of the <uri link="
+"\"/doc/en/handbook/handbook-amd64.xml\">AMD64 Handbook</uri> for more "
+"information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):328
+msgid ""
+"I want to install package foo, but emerge says: (masked by: missing keyword)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):331
+msgid ""
+"This means that the package has not been tested yet. It does <e>not "
+"necessarily</e> mean that the package does not work. You can unmask it by "
+"accepting another architecture for the package. The following example shows "
+"you can tell Portage to accept any keyword for a given package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre:caption):338
+msgid "Example of adding package keywords"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(pre):338
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"category/packagename **\" &gt;&gt; /etc/portage/package.keywords</i>\n"
+"# <i>emerge packagename</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):343
+msgid ""
+"If it works fine for you, please let us know and file a bug on <uri link="
+"\"http://bugs.gentoo.org/\">Gentoo's Bugzilla</uri>, so that the AMD64 team "
+"can keyword the package and other users can benefit from your test."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(warn):349
+msgid ""
+"Do not try commands like <c>ACCEPT_KEYWORDS=\"~x86\" emerge packagename</c>. "
+"It will most certainly break your tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):359
+msgid "How can I help the Gentoo/AMD64 project?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):361
+msgid "How can I help?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):364
+msgid ""
+"With a growing popularity of the amd64 architecture, we also increasingly "
+"need more help. There's still much work to be done to improve the quality of "
+"Gentoo/AMD64. An average user can help us by:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):371
+msgid "Filing general bug reports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):372
+msgid "Testing software that does not yet have the <c>~amd64</c> keyword"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):373
+msgid ""
+"Participating in the <uri link=\"/proj/en/base/amd64/at/\">Arch Testers "
+"project</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):377
+msgid "Help answering questions on the mailing lists, forums and IRC channels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(li):380
+msgid "Sending patches"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):388
+msgid "Other Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(title):390
+msgid "Where can I get more help or information about Gentoo/AMD64?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(p):393
+msgid ""
+"If any of your questions wasn't answered here, you can try other resources "
+"listed on <uri link=\"/proj/en/base/amd64/\">our project homepage</uri>. You "
+"can also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri "
+"link=\"http://forums.gentoo.org/viewforum-f-46.html\">Gentoo/AMD64 Forums</"
+"uri>, or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-amd64-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-freebsd.xml.po b/doc/gettext/ru/gentoo-freebsd.xml.po
new file mode 100644
index 0000000..58e5f25
--- /dev/null
+++ b/doc/gettext/ru/gentoo-freebsd.xml.po
@@ -0,0 +1,1195 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):6
+msgid "A short guide to Gentoo/FreeBSD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):20
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):9
+msgid "ignacio.arquelatour@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):9
+msgid "Ignacio Arque-Latour"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):12
+msgid "citizen428@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):12
+msgid "Michael Kohl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):15
+msgid "angusyoung@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):15
+msgid "Otavio R. Piske"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):18
+msgid "ka0ttic@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):18
+msgid "Aaron Walker"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):21
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):21
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):23
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):24
+msgid "flameeyes@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):24
+msgid "Diego Pettenò"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):26
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(author:title):29
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):27
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):27
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail:link):30
+msgid "cam@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(mail):30
+msgid "Camille Huot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(abstract):33
+msgid ""
+"This document gives some general information on FreeBSD, as well as "
+"installation instructions for Gentoo/FreeBSD. It also includes some "
+"reference for people interested in helping out with development."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(version):43
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(date):44
+msgid "2010-08-08"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):47
+msgid "Introduction to FreeBSD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):49
+msgid "What is FreeBSD?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):52
+msgid ""
+"<uri link=\"http://www.freebsd.org/\">FreeBSD</uri> is a free (<uri link="
+"\"http://www.freebsd.org/copyright/freebsd-license.html\">license</uri>) "
+"Unix-like operating system. Back in 1993 when development of <uri link="
+"\"http://www.386bsd.org/\">386BSD</uri> stopped, two projects were born: "
+"<uri link=\"http://www.netbsd.org/\">NetBSD</uri>, commonly known to run on "
+"a huge number of architectures, and FreeBSD which supports the x86, amd64, "
+"ia64, sparc64 and alpha platforms. FreeBSD is renowned for its stability, "
+"performance and security, thus being used from small to huge companies all "
+"over the world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):63
+msgid ""
+"FreeBSD's current production release is version 7.1. Gentoo/FreeBSD is based "
+"on version 6.2 and older versions of Gentoo/FreeBSD are discontinued and no "
+"longer supported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):72
+msgid "What is Gentoo/FreeBSD?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):75
+msgid ""
+"<uri link=\"/proj/en/gentoo-alt/bsd/fbsd/\">Gentoo/FreeBSD</uri> is a "
+"subproject of the <uri link=\"/proj/en/gentoo-alt/\">Gentoo/Alt project</"
+"uri>, with the goal of providing a fully-capable FreeBSD operating system "
+"featuring design sensibilities taken from Gentoo Linux, such as the init "
+"system and the Portage package management system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):86
+msgid "FreeBSD and Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):89
+msgid ""
+"Users migrating from Linux to FreeBSD commonly consider the two operating "
+"systems \"almost the same\". In fact, FreeBSD really shares a lot of "
+"similarities with Linux distributions in general. Nevertheless, it has some "
+"key differences that are worth noting:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):97
+msgid ""
+"Contrary to Linux, which actually only refers to the kernel, FreeBSD is a "
+"complete operating system, consisting of a C library, userland tools and "
+"much more. This development approach makes the overall system very "
+"consistent."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):103
+msgid ""
+"Contrary to the Linux kernel, FreeBSD development is not led by one person, "
+"but instead managed by a small group of people called the <uri link=\"http://"
+"www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers."
+"html\">Core Team</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):111
+msgid ""
+"Besides, FreeBSD also has some technical differences which set it apart from "
+"Linux. Some of them are very important to know, even if you don't plan on "
+"joining the Gentoo/FreeBSD development effort:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):118
+msgid ""
+"To get run-time dynamic linking functions like <c>dlopen()</c>, programs do "
+"not need to be linked against libdl like on GNU/Linux. Instead they are "
+"linked against libc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):123
+msgid ""
+"FreeBSD doesn't have an official tool for kernel compilation, thus you'll "
+"have to resolve feature dependencies on your own."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):127
+msgid ""
+"FreeBSD uses UFS/UFS-2 as its filesystems and has no official support for e."
+"g. ReiserFS or XFS. However, there are projects for adding read-only support "
+"for these filesystems. Accessing ext2/ext3 partitions is already possible, "
+"but you cannot install your system on them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):140
+msgid "Installing Gentoo/FreeBSD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):142
+msgid "Booting the CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):145
+msgid ""
+"After this short introduction, it's about time to finally install Gentoo/"
+"FreeBSD. Unfortunately, we currently lack our own installation media, so you "
+"have to choose between two alternative installation methods. The first would "
+"be to use an existing FreeBSD installation to partition your hard drive and "
+"use it as a base for installing Gentoo/FreeBSD. This guide will describe how "
+"to use the <uri link=\"http://www.freesbie.org/\">FreeSBIE LiveCD</uri> as "
+"an installation medium for Gentoo/FreeBSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):155
+msgid ""
+"If you are intending to use FreeSBIE for installing Gentoo/FreeBSD, please "
+"make sure to use a version based on FreeBSD 6.x, such as FreeSBIE 2.0 (or "
+"one of its release candidates). You can download it from <uri link=\"http://"
+"torrent.freesbie.org/\">FreeSBIE's Bittorrent tracker</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):162
+msgid ""
+"First, boot the CD in order to begin the installation process. You'll be "
+"presented with a login screen. The username is <c>freesbie</c>, and there is "
+"no password. Next, run <c>sudo su</c> to become root, and optionally setup a "
+"password. If you want to pass time during the installation process, you can "
+"run <c>startx</c> to enter into an Xfce environment, suitable for web "
+"browsing, AIM, and other things. Unlike Linux, FreeBSD bases the name of "
+"your interface on the driver for the interface. For example, the Intel "
+"EtherExpress driver (fxp) appears as fxp0 (driver fxp, first network card). "
+"To see what your interface is, use <c>ifconfig</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):174
+msgid "Finding out the network interface name using ifconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):174
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ifconfig</i>\n"
+"fxp0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500\n"
+"        options=8&lt;VLAN_MTU&gt;\n"
+"        inet6 fe80::2d0::b7ff:febc:4fe3%fxp0 prefixlen 64 scopeid 0x1\n"
+"        inet 192.168.0.106 netmask 0xffffff00 broadcast 192.168.0.255\n"
+"        ether 00:d0:b7:bc:4f:e3\n"
+"        media: Ethernet autoselect (100baseTX &lt;full-duplex&gt;)\n"
+"        status: active\n"
+"lo0: flags=8007&lt;LOOPBACK,MULTICAST&gt; mtu 16384\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):186
+msgid ""
+"If the original DHCP request during the CD bootup failed, you can use the "
+"<c>dhclient</c> command to obtain an IP:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):191
+msgid "Obtaining a DHCP address using dhclient"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):191
+#, no-wrap
+msgid ""
+"\n"
+"# <i>dhclient fxp0</i>\n"
+"DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 9\n"
+"DHCPOFFER from 192.168.0.1\n"
+"DHCPREQUEST on fxp0 to 255.255.255.255 port 67\n"
+"DHCPACK from 192.168.0.1\n"
+"bound to 192.168.0.106 -- renewal in 302400 seconds\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):200
+msgid "The output presented here will differ based on your network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):207
+msgid "Partitioning the Drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):210
+msgid ""
+"Now that we have a mount point, it's time to partition the drive. This is "
+"done with the <c>sysinstall</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):215
+msgid "Running the sysinstall command to fdisk the drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):215
+#, no-wrap
+msgid ""
+"\n"
+"# <i>sysinstall diskPartitionEditor diskPartitionWrite</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):219
+msgid ""
+"We recommend that you use the default layout. Press enter at the dialog, "
+"then press <b>a</b> followed by <b>q</b> to accept the default layout. The "
+"next screen will present you with the option of a bootloader. For this "
+"option, choose \"None\" as we'll be installing the bootloader later on. Next "
+"comes the actual partition sizing and mount points."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):227
+msgid ""
+"This next step also uses <c>sysinstall</c>, but with different arguments:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):231
+msgid "Running sysinstall to setup partition sizing and mount points"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):231
+#, no-wrap
+msgid ""
+"\n"
+"# <i>sysinstall diskLabelEditor diskLabelCommit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):235
+msgid ""
+"Here, we'll refrain from using the automatic layout, and create one giant "
+"root partition, followed by a swap partition. Hit <b>c</b> to create a new "
+"partition. A dialog prompts you to enter a size. Go ahead and do so, using "
+"MB/GB for setting different sizes, or C for cylinders. For root, choose FS "
+"as the partition type, and set the mount point as <path>/mnt/</path>. <e>If "
+"you do not adjust the mount point, it will overwrite the FreeSBIE "
+"environment!</e> As <path>/boot</path> is not a separate partition, you'll "
+"need to disable soft-updates, or your system will not boot! To do so, use "
+"the arrow keys to navigate to your newly created partition, then hit the "
+"<b>s</b> key, until \"Newfs\" contains no <b>+S</b>. Now navigate the arrow "
+"keys until the \"Disk\" line is highlighted, and hit <b>c</b> again to "
+"create a swap partition. Generally, we recommend a swap space that is twice "
+"the size of your RAM. Choose SWAP as the partition type, and don't worry "
+"about soft-updates, as it does not apply to swap. Now we're finished, so hit "
+"<b>q</b> to finish the process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):253
+msgid ""
+"When choosing a different mountpoint than <path>/</path> for your partition, "
+"<c>sysinstall</c> will actually create a 'd' slice, which the bootloader "
+"won't boot from. To fix this, run the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):259
+msgid ""
+"Please, make sure ad0s1 is unmounted before running the following command, "
+"otherwise it will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):264
+msgid "Fixing the root partition letter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):264
+#, no-wrap
+msgid ""
+"\n"
+"# <i>disklabel ad0s1 | sed 's/^  d:/  a:/' | disklabel -R ad0s1 /dev/stdin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):268
+msgid ""
+"This will finalize the partitioning process, and format the drive in UFS for "
+"FreeBSD to utilize. This will also mount the drive for you at the mount "
+"point specified earlier (<path>/mnt/</path>). You can verify this worked by "
+"running <c>mount</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):275
+msgid "Verifying the new disk layout was mounted with mount"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):275
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount</i>\n"
+"...\n"
+"/dev/ad0s1a on /mnt (ufs, local)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):281
+msgid ""
+"Now that you have mounted the target partition, it is time to start on the "
+"Gentoo setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):289
+msgid "Gentoo Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):292
+msgid ""
+"First, we need to download a stage3 tarball and unpack it into the chroot. "
+"Point your browser to <uri>http://distfiles.gentoo.org/experimental/x86/"
+"freebsd/stages/</uri>, grab the latest snapshot, and unpack it into the "
+"mountpoint:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):299
+msgid "Obtaining and unpacking a stage3 tarball"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):299
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /mnt/</i>\n"
+"<comment>(Any other Gentoo mirror which includes the experimental/ directory will also work.)</comment>\n"
+"# <i>wget http://distfiles.gentoo.org/experimental/x86/freebsd/stages/stage3-x86-freebsd-6.2-r1.tar.bz2</i>\n"
+"# <i>tar -jxvpf stage3-x86-freebsd-6.2-r1.tar.bz2</i>\n"
+"<comment>(You can delete the tarball with the following command if you want to.)</comment>\n"
+"# <i>rm stage3-x86-freebsd-6.2-r1.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):308
+msgid ""
+"If you want you can use the transition overlay that contains semi-"
+"experimental ebuilds with patches not yet in the main Portage tree, but does "
+"allow a wider range of supported packages, please refer to the <uri link=\"/"
+"proj/en/gentoo-alt/contribute/index.xml?part=1&amp;chap=3\">Gentoo/ALT "
+"overlay documentation</uri>. Please note that the overlay is not critical "
+"and you can easily install and use Gentoo/FreeBSD without it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):317
+msgid ""
+"In order for your install to work, you need to mount the <path>/dev</path> "
+"filesystem from the currently running system into the Gentoo/FreeBSD mount "
+"point before proceeding with the chroot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):323
+msgid "Mounting the /dev filesystem and chrooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):323
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount -t devfs none /mnt/dev/</i>\n"
+"# <i>cp /etc/resolv.conf /mnt/etc/</i>\n"
+"# <i>chroot /mnt/ /bin/bash</i>\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):330
+msgid ""
+"After you obtain the Gentoo/FreeBSD overlay, it's time to link <path>/etc/"
+"make.profile</path> to the correct profile and get your <path>/etc/make."
+"conf</path> ready for Gentoo/FreeBSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):336
+msgid ""
+"Now, you have to obtain a copy of the main Gentoo Portage tree, which "
+"depending on your connection might take quite a while."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):341
+msgid "Obtaining the Portage tree"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):341
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --sync</i>\n"
+"<comment>(It's also possible to retrieve the Portage tree in another way:)</comment>\n"
+"# <i>cd /</i>\n"
+"# <i>wget http://distfiles.gentoo.org/snapshots/portage-latest.tar.bz2</i>\n"
+"# <i>tar -xjf portage-latest.tar.bz2 -C /usr/</i>\n"
+"# <i>emerge --metadata</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):350
+msgid "Setting up the profile and editing /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):350
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ln -sf /usr/portage/profiles/default-bsd/fbsd/6.2/x86/ /etc/make.profile</i>\n"
+"# <i>nano /etc/make.conf</i>\n"
+"<comment>(Please make sure you add at least the following entries:)</comment>\n"
+"CHOST=\"i686-gentoo-freebsd6.2\"\n"
+"FEATURES=\"collision-protect\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):358
+msgid ""
+"The <c>~x86-fbsd</c> keyword does not yet fully cover the same tree as "
+"<c>~x86</c>, but please <e>do not</e> put <c>~x86</c> in ACCEPT_KEYWORDS. "
+"Rather use <path>/etc/portage/package.keywords</path> to test packages, and "
+"report working packages on <uri link=\"http://bugs.gentoo.org/enter_bug.cgi?"
+"product=Gentoo%2FAlt\">Bugzilla</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):366
+msgid "If you want, you can now rebuild the system's core packages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):370
+msgid "Rebuilding the FreeBSD core packages (optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):370
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -e system</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):378
+msgid "Setting up for Booting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):380
+msgid "Set your time zone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):383
+msgid ""
+"First make sure your date and time is set correctly using <c>date "
+"yyyymmddHHMM</c>. Use UTC time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):388
+msgid "Set the date and UTC time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):388
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Check the clock)</comment>\n"
+"# <i>date</i>\n"
+"Mon Mar  6 00:14:13 UTC 2006\n"
+"\n"
+"<comment>(Set the current date and time if required)</comment>\n"
+"# <i>date 200603060016</i> <comment>(Format is yyyymmddHHMM)</comment>\n"
+"Mon Mar  6 00:16:00 UTC 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):398
+msgid ""
+"Next, set your time zone information by using the correct listing in <path>/"
+"usr/share/zoneinfo</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):403
+msgid "Setting your timezone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):403
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls /usr/share/zoneinfo</i>\n"
+"<comment>(Using Brussels as an example)</comment>\n"
+"# <i>cp /usr/share/zoneinfo/Europe/Brussels /etc/localtime</i>\n"
+"\n"
+"# <i>date</i>\n"
+"Wed Mar  8 00:46:05 CET 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):412
+msgid ""
+"Edit <path>/etc/conf.d/clock</path> to define the time zone you used "
+"previously."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):417
+msgid "Edit /etc/conf.d/clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):417
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/conf.d/clock</i>\n"
+"TIMEZONE=\"Europe/Brussels\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):425
+msgid "Kernel Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):428
+msgid ""
+"If you ran <c>emerge -e system</c>, the sources for the FreeBSD kernel were "
+"installed to <path>/usr/src/sys</path>. If you skipped this step, you can "
+"get them in the following way:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):434
+msgid "Getting the FreeBSD kernel sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):434
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge freebsd-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):438
+msgid ""
+"Configuring and compiling a custom kernel is quite different from compiling "
+"Linux, so if you are not familiar with the process we encourage you to have "
+"a look at <uri link=\"http://www.freebsd.org/doc/en_US.ISO8859-1/books/"
+"handbook/kernelconfig.html\"> chapter 8</uri> of the FreeBSD handbook. For "
+"now, you can do an installation of the GENERIC kernel, which works on most "
+"systems. To begin, enter the source directory for the kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(impo):448
+msgid ""
+"Please note that currently only the \"Traditional\" way of building the "
+"kernel is supported on Gentoo/FreeBSD!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):453
+msgid "Entering the kernel source directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):453
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/sys/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):457
+msgid ""
+"Looking over the layout, you'll see various architectures and subdirectories "
+"for various parts of the kernel. To begin the installation, we head into the "
+"<path>i386/conf/</path> directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):463
+msgid "The kernel configuration directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):463
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd i386/conf/</i>\n"
+"# <i>ls</i>\n"
+".cvsignore      GENERIC         Makefile        PAE\n"
+"DEFAULTS        GENERIC.hints   NOTES           SMP\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):470
+msgid ""
+"The main files to note are <path>GENERIC</path> and <path>GENERIC.hints</"
+"path>. As it will be needed by the installation of the kernel, go ahead and "
+"copy <path>GENERIC.hints</path> file to <path>/boot/device.hints</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):476
+msgid "Copying over the GENERIC.hints file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):476
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp GENERIC.hints /boot/device.hints</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):480
+msgid ""
+"This file is used by the kernel drivers for basic configuration information "
+"such as IRQ settings. Now it's time to configure the kernel. FreeBSD uses "
+"the <c>config</c> command to do this. <c>config</c> uses the given file (in "
+"this instance GENERIC) to copy over the required build files to a "
+"<path>compile</path> directory in the parent directory. <path>GENERIC</path> "
+"is similiar to the <path>.config</path> file for the Linux kernel. Run "
+"<c>config</c> to produce the build directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):490
+msgid "Configuring the kernel build"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):490
+#, no-wrap
+msgid ""
+"\n"
+"# <i>config GENERIC</i>\n"
+"Kernel build directory is ../compile/GENERIC\n"
+"Don't forget to ''make cleandepend; make depend''\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):496
+msgid ""
+"<c>config</c> has created a GENERIC build directory for us in the parent "
+"directory. <c>cd</c> into it, then run the following to do a complete build:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):501
+msgid "Building and installing the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):501
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd ../compile/GENERIC</i>\n"
+"# <i>make cleandepend &amp;&amp; make depend &amp;&amp; make &amp;&amp; make install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):506
+msgid ""
+"This will give us a complete kernel to work with. Now we'll need to setup "
+"the bootloader for the kernel to boot. The next chapter will discuss two "
+"methods of setting up the bootloader: <c>boot0</c> and <c>grub</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):515
+msgid "Setting up the bootloader (boot0)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(impo):518
+msgid ""
+"<c>boot0</c> is the FreeBSD bootloader. Previously, it was the only "
+"supported bootloader until <c>grub</c> was introduced into ports with UFS "
+"slice support. To install and configure <c>boot0</c>, run the following. "
+"Remember to replace <c>adXsY</c> with the actual number and slice of your "
+"disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):525
+msgid "Installing and setting up boot0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):525
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge boot0</i>\n"
+"<comment>(Leave the chroot environment)</comment>\n"
+"# <i>exit</i>\n"
+"<comment>(Issued from outside the chroot)</comment>\n"
+"# <i>fdisk -B -b /mnt/boot/boot0 /dev/adX</i>\n"
+"# <i>chroot /mnt/ /bin/bash</i>\n"
+"# <i>disklabel -B adXsY</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):535
+msgid ""
+"If you need additional information on setting up <c>boot0</c>, please "
+"consult <uri link=\"http://www.freebsd.org/doc/en_US.ISO8859-1/books/"
+"handbook/boot.html\">chapter 12</uri> of the FreeBSD handbook. Now it's time "
+"to do some basic system configuration and settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):543
+msgid ""
+"The next section will look at using the alternative bootloader, <c>grub</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):550
+msgid "Setting up the bootloader (grub)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):553
+msgid ""
+"As of grub 0.97-r1, UFS slices are readable to <c>grub</c>. This lets us use "
+"<c>grub</c> as a bootloader, the prefered method for those coming from a "
+"Linux background. To begin, emerge <c>grub</c> and setup the label as "
+"bootable. Remember to replace <c>adXsY</c> with the actual number and slice "
+"of your disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):560
+msgid "Emerge grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):560
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge grub</i>\n"
+"# <i>disklabel -B adXsY</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):565
+msgid ""
+"Now run <c>grub</c> to bring up the command prompt, and set up the partition "
+"as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):570
+msgid "Setting up grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):570
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(This is done to prevent disk error 29)</comment>\n"
+"# <i>sysctl kern.geom.debugflags=16</i>\n"
+"# <i>grub</i>\n"
+"<comment>(Example using ad0s1d)</comment>\n"
+"grub&gt; <i>root (hd0,0,d)</i>\n"
+" Filesystem type is ufs2, partition type 0xa5\n"
+"\n"
+"grub&gt; <i>setup (hd0)</i>\n"
+" Checking if \"/boot/grub/stage1\" exists... yes\n"
+" Checking if \"/boot/grub/stage2\" exists... yes\n"
+" Checking if \"/boot/grub/ufs2_stage1_5\" exists... yes\n"
+" Running \"embed /boot/grub/ufs2_stage1_5 (hd0)\"... 14 sectors are embedded.\n"
+"succeeded\n"
+" Running \"install /boot/grub/stage1 (hd0) (hd0)1+14 p (hd0,0,d)/boot/grub/stage\n"
+"2 /boot/grub/menu.lst\"... succeeded\n"
+"Done.\n"
+"\n"
+"grub&gt; quit\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):591
+msgid ""
+"To make the loader find the kernel on a specific slice (the default is 'a'), "
+"add a <c>vfs.root.mountfrom</c> line to the <path>/boot/loader.conf</path> "
+"file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):597
+msgid "Tell the loader where to look for the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):597
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo 'vfs.root.mountfrom=\"ufs:ad0s1d\"' &gt;&gt; /boot/loader.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):601
+msgid ""
+"When you first boot, you may not receive a grub menu. If so, run this at the "
+"prompt:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):606
+msgid "Booting the kernel with no menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):606
+#, no-wrap
+msgid ""
+"\n"
+"grub&gt; <i>find /boot/grub/stage1</i>\n"
+"<comment>(The output here is what you'll use in the next command)</comment>\n"
+" (hd0,0,d)\n"
+"\n"
+"grub&gt; <i>kernel (hd0,0,d)/boot/loader</i>\n"
+"  [FreeBSD-a.out, loadaddr=0x200000, text=0x1000, data=0x3a000, bss=0x0, entry=0x200000]\n"
+"\n"
+"grub&gt; <i>boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):617
+msgid ""
+"For more information on configuring grub, please refer to the <uri link=\"/"
+"doc/en/handbook/handbook-x86.xml?part=1&amp;chap=10#doc_chap2\">Gentoo Linux "
+"Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(warn):623
+msgid ""
+"Grub doesn't follow UFS symlinks so be sure to delete the <path>/boot/grub/"
+"menu.lst</path> symlink and to use <path>menu.lst</path> to setup Grub "
+"(<path>grub.conf</path> isn't used)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):632
+msgid "System configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):635
+msgid ""
+"First, we are going to setup the filesystem mounting points in <path>/etc/"
+"fstab</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):640
+msgid "Editing the filesystem in /etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):640
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/fstab</i>\n"
+"<comment>(This is an example, replace X and Y with the correct numbers for your hard disk.)</comment>\n"
+"#Device         Mountpoint      Fstype          Options         Dump    Pass\n"
+"/dev/adXsYb     none            swap            sw              0       0\n"
+"/dev/adXsYa     /               ufs             rw              1       1\n"
+"/dev/adXsYe     /usr/home       ufs             rw              2       2\n"
+"/dev/adXsYd     /tmp            ufs             rw              2       2\n"
+"/dev/acdX       /cdrom          cd9660          ro,noauto       0       0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):651
+msgid ""
+"Now would also be a good time to set up your network connection before the "
+"final reboot. You can find all the information necessary to configure your "
+"network in the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=4&amp;"
+"chap=1\">Gentoo Handbook</uri>. To have your network interface activated at "
+"boot time, you have to add it to the default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):659
+msgid "Adding your network adapter to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):659
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add net.fxp0 default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):663
+msgid ""
+"Your system's hostname can be changed in <path>/etc/conf.d/hostname</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):667
+msgid "Setting up the machine's hostname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):667
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/hostname</i>\n"
+"<comment>(Set the HOSTNAME variable to your hostname)</comment>\n"
+"HOSTNAME=\"tux\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):673
+msgid ""
+"You should also configure your domain name, which is done in the <path>/etc/"
+"conf.d/domainname</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):678
+msgid "Setting the domainname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):678
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/domainname</i>\n"
+"<comment>(Set the dns_domain variable to your domain name, and lo to your local\n"
+"network interface)</comment>\n"
+"dns_domain_lo=\"homenetwork\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):685
+msgid ""
+"If you have a NIS domain, you need to define it in the <path>/etc/conf.d/"
+"domainname</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):690
+msgid "Setting the NIS domainname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):690
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/domainname</i>\n"
+"<comment>(Set the nis_domain variable to your NIS domain name, and lo to your local network interface)</comment>\n"
+"nis_domain_lo=\"my-nisdomain\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(note):696
+msgid ""
+"For more information on domainnames and networking, please refer to the <uri "
+"link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;"
+"chap=8#doc_chap2\">Gentoo Linux Handbook</uri>, and please read the "
+"documentation in <path>/etc/conf.d/net.example</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):703
+msgid ""
+"In case you need to use another keyboard layout for your language, you have "
+"to set the correct value in <path>/etc/conf.d/syscons</path>. The following "
+"example uses the Spanish layout, so you'll have to adjust it to your need if "
+"you want to use another one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):710
+msgid "Changing your keyboard layout (Optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):710
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/syscons</i>\n"
+"KEYMAP=\"spanish.iso.acc\"\n"
+"<comment>(Possible layouts can be found in /usr/share/syscons/keymaps).</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):716
+msgid ""
+"Now would be a good time to set a password for the <c>root</c> user and to "
+"add another user account for your day-to-day work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):721
+msgid "Changing the root password and adding a new user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):721
+#, no-wrap
+msgid ""
+"\n"
+"# <i>passwd</i>\n"
+"# <i>adduser</i>\n"
+"Username: <i>fred</i>\n"
+"Full Name: <i>Fred Smith</i>\n"
+"<comment>(Accepting the default here, just hit Enter.)</comment>\n"
+"Uid (Leave empty for default):\n"
+"<comment>(OK to accept the default here as well; hit Enter.)</comment>\n"
+"Login group [fred]:\n"
+"<comment>(Enter your groups here, space separated. They must exist.)</comment>\n"
+"Login group is fred. Invite fred into other groups? []: wheel portage\n"
+"<comment>(OK to accept the default here, hit Enter)</comment>\n"
+"Login class [default]:\n"
+"<comment>(Somewhat of a personal preference.  Make sure the shell exists in /etc/shells)</comment>\n"
+"Shell (sh bash tcsh csh esh ksh zsh sash nologin) [sh] <i>bash</i>\n"
+"<comment>(OK to accept the default here, hit Enter for all these)</comment>\n"
+"User password-based authentication [yes]\n"
+"Use an empty password (yes/no) [no]:\n"
+"Use a random password? (yes/no) [no]:\n"
+"Enter password: <i>password goes here</i>\n"
+"Enter password again: <i>retype it</i>\n"
+"<comment>(OK to accept the default here, hit Enter)</comment>\n"
+"Lock out the account after creation? [no]:\n"
+"Username    : fred\n"
+"Password    : *****\n"
+"Full Name   : Fred Smith\n"
+"<comment>(This will vary)</comment>\n"
+"Uid         : 1002\n"
+"Class       :\n"
+"Groups      : fred wheel portage\n"
+"Home        : /home/fred\n"
+"Shell       : /bin/bash\n"
+"Locked      : no\n"
+"<comment>(Confirm the information is correct)</comment>\n"
+"OK? (yes/no): <i>yes</i>\n"
+"adduser: INFO: Sucessfully added (fred) to the user database\n"
+"Add another user? (yes/no): <i>no</i>\n"
+"Goodbye!\n"
+"#\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):762
+msgid ""
+"Congratulations, you have just finished your Gentoo/FreeBSD installation "
+"which you can start exploring after the final reboot. Have fun!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre:caption):767
+msgid "Rebooting the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(pre):767
+#, no-wrap
+msgid ""
+"\n"
+"# <i>exit</i>\n"
+"# <i>reboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):777
+msgid "Developing for Gentoo/FreeBSD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):779
+msgid "How to help"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):782
+msgid ""
+"There are many things you could help with, depending on your skill level and "
+"spare time:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):788
+msgid ""
+"Working on current ebuilds: this means working closely with ebuild "
+"maintainers in order to create patches or modify ebuilds in a way that can "
+"be accepted into the main tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):793
+msgid ""
+"Security: if you are into security, we need you! Although security "
+"advisories from the FreeBSD project are tracked and fixed, we can always use "
+"help in this area."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):798
+msgid ""
+"Contacts: we need people who can get in touch with FreeBSD developers to "
+"maintain contacts between us and the original project to exchange patches "
+"and discuss various problems and their solutions. Note that this should "
+"never involve any kind of spamming of mailing lists or IRC channels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):804
+msgid ""
+"Testing: the more people are actively using Gentoo/FreeBSD, the more bugs "
+"will be discovered, which helps us improving the quality of the port. If you "
+"are good at describing bugs or problems, we definitely want to hear from you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):810
+msgid ""
+"Other areas where we need help include: system ebuilds, creation of "
+"installation CDs, documentation, kernel hacking."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):820
+msgid "Known issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):823
+msgid ""
+"At the moment, there are still quite a lot of known issues. Here are the "
+"ones really worth noting:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(li):829
+msgid ""
+"Some init scripts depend on the clock service which we don't provide right "
+"now. You can just remove it from the dependencies of the script and report "
+"that on our <uri link=\"http://bugs.gentoo.org/\">Bugzilla</uri>. Please "
+"remember to use the \"Gentoo/Alt\" product for your submission."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(title):842
+msgid "Contact"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(p):846
+msgid ""
+"A list of Gentoo/FreeBSD developers can be found at the <uri link=\"/proj/en/"
+"gentoo-alt/bsd/fbsd/\">project page</uri>. Other ways to contact Gentoo/"
+"FreeBSD developers include our IRC Channel <c>#gentoo-bsd</c> on Freenode, "
+"as well as the <uri link=\"/main/en/lists.xml\">gentoo-bsd mailing list</"
+"uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-freebsd.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-hppa-install.xml.po b/doc/gettext/ru/gentoo-hppa-install.xml.po
new file mode 100644
index 0000000..b1779c2
--- /dev/null
+++ b/doc/gettext/ru/gentoo-hppa-install.xml.po
@@ -0,0 +1,60 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(guide:redirect):3
+msgid "/doc/en/handbook/handbook-hppa.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(title):4
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(title):20
+msgid "Gentoo HPPA Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(author:title):6
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(mail:link):7
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(mail):7
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(abstract):10
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(version):16
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(date):17
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(p):24
+msgid ""
+"As of 2004.0, the individual architecture-specific installation guides have "
+"been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/"
+"handbook/handbook-hppa.xml\">Gentoo Handbook</uri>. For more information "
+"please read up on the <uri link=\"/doc/en/handbook\">Gentoo Handbook "
+"Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-hppa-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-kernel.xml.po b/doc/gettext/ru/gentoo-kernel.xml.po
new file mode 100644
index 0000000..8dd4b15
--- /dev/null
+++ b/doc/gettext/ru/gentoo-kernel.xml.po
@@ -0,0 +1,571 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):6
+msgid "Gentoo Linux Kernel Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):11
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):12
+msgid "lostlogic@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):12
+msgid "Brandon Low"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):23
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):26
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):29
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(author:title):32
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):15
+msgid "dsd@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):15
+msgid "Daniel Drake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):18
+msgid "carl@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):18
+msgid "Carl Anderson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):21
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):21
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):24
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):24
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):27
+msgid "greg_g@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):27
+msgid "Gregorio Guidi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):30
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):30
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail:link):33
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(mail):33
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(abstract):36
+msgid ""
+"This document gives you an overview on all kernel sources that Gentoo "
+"provides through Portage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(version):45
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(date):46
+msgid "2010-09-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):49
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):53
+msgid ""
+"As with everything else in Gentoo Linux, the philosophy of the Gentoo Kernel "
+"team is to give you, the user, as much freedom of choice as possible. If you "
+"take a look at the output of <c>emerge -s sources</c> you see a large "
+"variety of kernels to choose from. In this document, I will attempt to give "
+"you a brief rundown of the goals of each of the patch sets, which we at "
+"Gentoo design, and also explain the other kernel sources we make available "
+"to you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):63
+msgid ""
+"Linux 2.4 is maintained by Willy Tarreau. Linus Torvalds, the original "
+"creator of Linux, handed maintainership of the Linux 2.4 branch over to "
+"Marcelo Tosatti when Linus went off to start developing the newer 2.6 kernel "
+"tree. Marcelo did a fine job of keeping 2.4 stable and secure, and has since "
+"handed over maintainership to Willy. Note that only security and bug fixes "
+"are accepted into the 2.4 kernel tree. Actual development happens in the "
+"Linux 2.6 kernel tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):72
+msgid ""
+"Linux 2.6 is maintained by Andrew Morton, who works closely with Linus "
+"Torvalds to deliver a fast, powerful, and feature-packed Linux kernel. "
+"Development is happening at incredible pace and this kernel tree is now very "
+"mature."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):79
+msgid ""
+"Some of the more uncommon system architectures are not fully compatible with "
+"Linux 2.6, and some users prefer the tried-and-tested Linux 2.4 kernel. "
+"However, please note that Linux 2.4 is currently not being developed further "
+"- only bug and security fixes are being included in the newer releases. If "
+"you are able to, we suggest that you upgrade to Linux 2.6. You may find the "
+"<uri link=\"/doc/en/migration-to-2.6.xml\">migration document</uri> useful."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):93
+msgid "Supported kernel packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):95
+msgid "genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):98
+msgid ""
+"<c>Genkernel</c> is a kernel toolset that can be used to autodetect your "
+"hardware and configure your kernel automatically. This is usually "
+"recommended for users who do not feel comfortable about compiling a kernel "
+"manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):104
+msgid ""
+"For more information, please read the <uri link=\"/doc/en/genkernel.xml"
+"\">Gentoo Linux Genkernel Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):112
+msgid "General purpose: gentoo-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):115
+msgid ""
+"For most users, we recommend the <c>gentoo-sources</c> kernel. <c>gentoo-"
+"sources</c> is a kernel based on Linux 2.6, lightly patched to fix security "
+"problems, kernel bugs, and to increase compatibility with the more uncommon "
+"system architectures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):122
+msgid ""
+"The <c>gentoo-sources</c> package absorbs most of the resources of the "
+"Gentoo kernel team. They are brought to you by a group of talented "
+"developers, which can count on the expertise of popular kernel hacker Greg "
+"Kroah-Hartman, maintainer of udev and responsible for the USB and PCI "
+"subsystems of the official Linux kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):133
+msgid "For servers: hardened-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):136
+msgid ""
+"<c>hardened-sources</c> is based on the official Linux kernel and is "
+"targeted at our users running Gentoo on server systems. It provides patches "
+"for the various subprojects of Gentoo Hardened (such as support for <uri "
+"link=\"http://www.nsa.gov/selinux/\">LSM/SELinux</uri> and <uri link="
+"\"http://grsecurity.net\">grsecurity</uri>), together with stability/"
+"security-enhancements. Check <uri>http://www.gentoo.org/proj/en/hardened/</"
+"uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(impo):146
+msgid ""
+"This kernel provides powerful patches for enhanced security. Please read the "
+"<uri link=\"/proj/en/hardened/\">documentation</uri> before you use it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):154
+msgid "ck-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):157
+msgid ""
+"<c>ck-sources</c> is Con Kolivas's kernel patch set. This patchset is "
+"primarily designed to improve system responsiveness and interactivity and is "
+"configurable for varying workloads (from servers to desktops). The patchset "
+"includes a different scheduler, BFS, designed to keep systems responsive and "
+"smooth even when under heavy load. Support and information is available at "
+"<uri>http://kernel.kolivas.org</uri> and in <c>#ck</c> on <c>irc.oftc.net</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):169
+msgid "git-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):172
+msgid ""
+"The <c>git-sources</c> package tracks daily snapshots of the upstream "
+"development kernel tree. You should run these kernels if you are interested "
+"in kernel development or testing. Bugreports should go to the <uri link="
+"\"http://bugzilla.kernel.org/\">Linux Kernel Bug Tracker</uri> or LKML "
+"(Linux Kernel Mailing List)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):183
+msgid "xen-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):186
+msgid ""
+"<c>xen-sources</c> lets you run multiple operating systems on a single "
+"physical system. You can create virtual environments in which one or more "
+"guest operating systems run on a <uri link=\"http://www.xensource.com\">Xen</"
+"uri>-powered host operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):193
+msgid ""
+"For more information on Xen and Gentoo, read the <uri link=\"/doc/en/xen-"
+"guide.xml\">Gentoo Xen Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):201
+msgid "Architecture dependent kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):204
+msgid ""
+"<c>cell-sources</c>, <c>mips-sources</c>, <c>sparc-sources</c>, and <c>xbox-"
+"sources</c> are, as their names suggest, patched to run best on specific "
+"architectures. They also contain some of the patches for hardware and "
+"features support from the other patch sets mentioned above and below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):216
+msgid "Unsupported kernel packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):220
+msgid ""
+"Now I'm going to try to briefly describe some of the other <path>sys-kernel/"
+"*-sources</path> which you saw scroll by when you ran <c>emerge -s sources</"
+"c>. Let's take them in alphabetical order. These kernels are provided as a "
+"courtesy only and the various patch sets are not supported by the Gentoo "
+"kernel team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):232
+msgid "mm-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):235
+msgid ""
+"The <c>mm-sources</c> are based on the <c>vanilla-sources</c> and contain "
+"Andrew Morton's patch set. They include the experimental and bleeding-edge "
+"features that are going to be included in the official kernel (or that are "
+"going to be rejected because they set your box on fire). They are known to "
+"be always moving at a fast pace and can change radically from one week to "
+"the other; kernel hackers use them as a testing ground for new stuff."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):244
+msgid ""
+"If you really want to live on the edge and you think <c>vanilla-sources</c> "
+"are for wussies, then try out <c>mm-sources</c>. Be warned that this kernel "
+"is highly experimental and doesn't always work as expected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):254
+msgid "pf-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):257
+msgid ""
+"The <c>pf-sources</c> kernel brings together parts of several different "
+"kernel patches. It includes the BFS patchset from <c>ck-sources</c>, the "
+"<c>tuxonice</c> patches, <uri link=\"http://www.linuximq.net\">LinuxIMQ</"
+"uri>, and the <uri link=\"http://algo.ing.unimo.it/people/paolo/disk_sched/"
+"patches/\">BFQ</uri> I/O <uri link=\"http://kerneltrap.org/Linux/"
+"Budget_Fair_Queuing_IO_Scheduler\">scheduler</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):270
+msgid "openvz-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):273
+msgid ""
+"OpenVZ is a server virtualization solution built on Linux. OpenVZ creates "
+"isolated, secure virtual private servers (VPSs) or virtual environments on a "
+"single physical server enabling better server utilization and ensuring that "
+"applications do not conflict. For more information, see <uri>http://www."
+"openvz.org</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):284
+msgid "tuxonice-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):287
+msgid ""
+"The <c>tuxonice-sources</c> (formerly <c>suspend2-sources</c>) are patched "
+"with both genpatches which includes the patches found in gentoo-sources, and "
+"<uri link=\"http://www.tuxonice.net\">TuxOnIce</uri> which is an improved "
+"implementation of suspend-to-disk for the Linux kernel, formerly known as "
+"<e>suspend2</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):295
+msgid ""
+"This kernel is recommended for laptop users who often rely on being able to "
+"suspend their laptop and resume work elsewhere."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):303
+msgid "usermode-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):306
+msgid ""
+"<c>usermode-sources</c> are the User Mode Linux kernel patches. This kernel "
+"is designed to allow Linux to run within Linux to run within Linux to ... "
+"User Mode Linux is intended for testing and virtual server support. For more "
+"information about this amazing tribute to the stability and scalability of "
+"Linux, see <uri>http://user-mode-linux.sourceforge.net</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):314
+msgid ""
+"For more information on UML and Gentoo, read the <uri link=\"/doc/en/uml.xml"
+"\">Gentoo UML Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):322
+msgid "vanilla-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):325
+msgid ""
+"The next kernel sources that many of you will probably be familiar with as "
+"Linux users are the <c>vanilla-sources</c>. These are the official kernel "
+"sources released on <uri>http://www.kernel.org/</uri>. Please note that we "
+"do not patch these kernels at all - these are purely for people who wish to "
+"run a completely unmodified Linux kernel. We recommend that you use "
+"<c>gentoo-sources</c> instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):334
+msgid ""
+"Two versions of the kernel can be found under this package: 2.4 and 2.6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):341
+msgid "zen-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):344
+msgid ""
+"<c>zen-sources</c> is designed for desktop systems. It includes code not "
+"found in the mainline kernel. The zen kernel has patches that add new "
+"features, support additional hardware, and contain various tweaks for "
+"desktops."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):355
+msgid "Previously provided kernel packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):357
+msgid "aa-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):360
+msgid ""
+"<c>aa-sources</c> was a heavily modified kernel with all kinds of patches. "
+"The upstream maintainer has stopped releasing kernel patchsets, this package "
+"was removed as it went out of date."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):369
+msgid "alpha-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):372
+msgid ""
+"<c>alpha-sources</c> was a 2.4 kernel with patches applied to improve "
+"hardware compatibility for the Alpha architecture. These patches have been "
+"developed and included in the mainline kernel. Alpha users can now run any "
+"recent kernel with no need for extra patches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):382
+msgid "development-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):385
+msgid ""
+"<c>development-sources</c>, the official 2.6 kernel from kernel.org, can now "
+"be found under the <c>vanilla-sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):393
+msgid "gentoo-dev-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):396
+msgid ""
+"<c>gentoo-dev-sources</c>, a 2.6 kernel patched with bug, security and "
+"stability fixes, can now be found under the <c>gentoo-sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):404
+msgid "grsec-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):407
+msgid ""
+"The <c>grsec-sources</c> kernel source used to be patched with the latest "
+"grsecurity updates (grsecurity version 2.0 and up) which included, amongst "
+"other security-related patches, support for PaX. As grsecurity patches are "
+"included in <c>hardened-sources</c>, this package is no longer in Portage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):417
+msgid "hardened-dev-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):420
+msgid ""
+"<c>hardened-dev-sources</c> can now be found under the <c>hardened-sources</"
+"c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):428
+msgid "hppa-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):431
+msgid ""
+"<c>hppa-sources</c> was a 2.6 kernel with patches applied to improve "
+"hardware compatibility for the HPPA architecture. These patches have been "
+"developed and included in the mainline kernel. HPPA users can now run any "
+"recent kernel with no need for extra patches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):441
+msgid "rsbac-dev-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):444
+msgid ""
+"The <c>rsbac-dev-sources</c> kernels can now be found under the <c>rsbac-"
+"sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):452
+msgid "rsbac-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):455
+msgid ""
+"<c>rsbac-sources</c> was a 2.6-based kernel. It contained patches to use "
+"Rule Set Based Access Controls (<uri link=\"http://www.rsbac.org\">RSBAC</"
+"uri>). It has been removed due to lack of maintainers. Use <c>hardened-"
+"sources</c> if you need additional security features."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):465
+msgid "selinux-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):468
+msgid ""
+"<c>selinux-sources</c>, a 2.4 kernel including lots of security "
+"enhancements, has been obsoleted by security development in the 2.6 tree. "
+"SELinux functionality can be found in the <c>hardened-sources</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):477
+msgid "sh-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):480
+msgid ""
+"<c>sh-sources</c> was a 2.6 kernel with patches applied to improve hardware "
+"compatibility for the SuperH architecture. These patches have been developed "
+"and included in the mainline kernel. SuperH users can now run any recent "
+"kernel with no need for extra patches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):490
+msgid "uclinux-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):493
+msgid ""
+"The <c>uclinux-sources</c> are meant for CPUs without MMUs as well as "
+"embedded devices. For more information, see <uri>http://www.uclinux.org</"
+"uri>. Lack of security patches as well as hardware to test on were the "
+"reasons this is no longer in the tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(title):503
+msgid "win4lin-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(p):506
+msgid ""
+"<c>win4lin-sources</c> were patched to support the userland win4lin tools "
+"that allow Linux users to run many Microsoft Windows (TM) applications at "
+"almost native speeds. This was removed due to security issues."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-kernel.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-mips-faq.xml.po b/doc/gettext/ru/gentoo-mips-faq.xml.po
new file mode 100644
index 0000000..84ceb34
--- /dev/null
+++ b/doc/gettext/ru/gentoo-mips-faq.xml.po
@@ -0,0 +1,726 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(guide:link):5
+msgid "/doc/en/gentoo-mips-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):7
+msgid "Gentoo Linux/MIPS Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(mail:link):10
+msgid "redhatter@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(mail):10
+msgid "Stuart Longland"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(abstract):13
+msgid ""
+"This FAQ is intended to answer some of the most frequently asked questions "
+"relating to Gentoo/MIPS and Linux/MIPS in general."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(version):22
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(date):23
+msgid "2005-09-08"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):26
+msgid "About this document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):31
+msgid ""
+"This FAQ is intended to answer frequently asked questions about Gentoo/MIPS "
+"and Linux/MIPS that we receive from various users. It's aimed at both new "
+"users and experienced users alike. It has been split into a number of "
+"categories to make navigation easier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):38
+msgid ""
+"If you have anything to contribute to the FAQ or, having read this guide, "
+"you still have questions that are left unanswered, feel free to <uri link="
+"\"http://mips.gentoo.org\">drop us a line</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):49
+msgid "About the Gentoo/MIPS Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):51
+msgid "What is Gentoo/MIPS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):54
+msgid ""
+"Gentoo/MIPS is a small project within the Gentoo Foundation, responsible for "
+"looking after the MIPS port of Gentoo Linux. We currently look after two "
+"main sub architectures of the MIPS family specifically: Silicon Graphics "
+"systems and MIPS-based Cobalt servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):64
+msgid "Why install Gentoo Linux on MIPS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):67
+msgid ""
+"Okay, sure, some MIPS machines aren't the fastest boxes on the block these "
+"days. However, despite the age of some of these beasts, they still can make "
+"very functional, useful machines. A Cobalt Qube 2 could make a very nice "
+"broadband Internet router, capable of hosting websites, email, IRC and "
+"numerous other tasks. There are a number of reasons why you'd want to "
+"install Linux on this sort of hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):77
+msgid ""
+"It teaches you a lot about computer hardware by giving you an alternate "
+"frame of reference"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):81
+msgid ""
+"It allows you to turn what would otherwise be useless junk into a very "
+"functional system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):85
+msgid ""
+"Status Symbol: Linux on x86 is so common these days it's not funny. However, "
+"Linux on MIPS is a lot less common and quite a talking point."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):94
+msgid "Why don't you port Gentoo to NetBSD/MIPS or IRIX?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):97
+msgid ""
+"Hey, great idea. Unfortunately, a lot of the Gentoo/MIPS team already have "
+"their hands full looking after Linux/MIPS as well as other commitments. "
+"However, you're welcome to give it a try. May I suggest raising this on the "
+"<uri link=\"http://forums.gentoo.org/viewforum-f-32.html\">Gentoo Forums</"
+"uri> and see what the interest is first. Also, have a look at some of the "
+"other threads on porting Gentoo to other architectures such as <uri link="
+"\"http://forums.gentoo.org/viewtopic-t-113387.html\">Solaris/SPARC</uri>, "
+"<uri link=\"http://forums.gentoo.org/viewtopic-t-319607.html\">IBM OS/2</"
+"uri> and <uri link=\"http://forums.gentoo.org/viewtopic-t-319691.html"
+"\">Microsoft Services For Unix</uri> for hints on how to proceed. If after "
+"some hacking you get something useful out of it... chances are a few "
+"developers will pick up on this and help you get it to the next stage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):117
+msgid "MIPS Hardware FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):119
+msgid "What is MIPS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):122
+msgid ""
+"<uri link=\"http://www.mips.com\">MIPS Technologies</uri> is a company that "
+"produce a number of RISC CPU cores which implement the MIPS Instruction Set "
+"Architecture. These processors appear in all sorts of hardware ranging from "
+"small embedded devices to large servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):129
+msgid ""
+"It also happens to be an acronym; <b>M</b>illions of <b>I</b>nstructions "
+"<b>P</b>er <b>S</b>econd."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):137
+msgid "What sort of hardware uses MIPS processors?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):140
+msgid ""
+"Good question. In short... Heaps. MIPS Processors see use inside all sorts "
+"of machines, ranging from small PDAs (such as the early Windows CE powered "
+"Casio PDAs), X Terminals (e.g. Tektronix TekXPress XP330 series), through to "
+"workstations such as the Silicon Graphics Indy and O2 and even high end "
+"servers such as the Silicon Graphics Origin 2000."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):148
+msgid ""
+"Here is a list of some of the more famous MIPS-based systems in use. A more "
+"comprehensive list can be found on the <uri link=\"http://www.linux-mips.org/"
+"wiki/index.php/Systems\">Linux/MIPS website</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):156
+msgid "Sony Game Consoles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):158
+msgid "http://www.linux-mips.org/wiki/index.php/PS1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):158
+msgid "PlayStation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):160
+msgid "http://www.linux-mips.org/wiki/index.php/PS2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):160
+msgid "PlayStation 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):162
+msgid "http://www.linux-mips.org/wiki/index.php/PSP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):162
+msgid "PlayStation Pocket"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):167
+msgid "Nintendo Game Consoles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):169
+msgid "http://www.linux-mips.org/wiki/index.php/Nintendo_64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):169
+msgid "Nintendo 64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):175
+msgid "Silicon Graphics Machines"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):177
+msgid "http://www.linux-mips.org/wiki/index.php/IP12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):177
+msgid "Iris Indigo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):179
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):181
+msgid "http://www.linux-mips.org/wiki/index.php/IP19"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):179
+msgid "Challenge"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):181
+msgid "Onyx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):183
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):185
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):187
+msgid "http://www.linux-mips.org/wiki/index.php/IP22"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):183
+msgid "Indy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):185
+msgid "Indigo 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):187
+msgid "Challenge S"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):189
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):191
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):193
+msgid "http://www.linux-mips.org/wiki/index.php/IP27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):189
+msgid "Origin 200"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):191
+msgid "Origin 2000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):193
+msgid "Onyx 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):195
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):197
+msgid "http://www.linux-mips.org/wiki/index.php/IP30"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):195
+msgid "Octane"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):197
+msgid "Octane 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):199
+msgid "http://www.linux-mips.org/wiki/index.php/IP32"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):199
+msgid "O2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):201
+msgid "http://www.linux-mips.org/wiki/index.php/IP34"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):201
+msgid "Fuel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):203
+msgid "http://www.linux-mips.org/wiki/index.php/IP35"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):203
+msgid "Origin 3000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):205
+msgid "http://www.linux-mips.org/wiki/index.php/IP45"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):205
+msgid "Origin 300"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):207
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):209
+msgid "http://www.linux-mips.org/wiki/index.php/IP53"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):207
+msgid "Origin 350"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):209
+msgid "Tezro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):214
+msgid "DECStations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):216
+msgid "http://www.linux-mips.org/wiki/index.php/Deskstation_rPC44"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):216
+msgid "rPC44"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):218
+msgid "http://www.linux-mips.org/wiki/index.php/Deskstation_Tyne"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):218
+msgid "Tyne"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):223
+msgid "Cobalt Microservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):225
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):227
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):229
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):231
+msgid "http://www.linux-mips.org/wiki/index.php/Cobalt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):225
+msgid "Qube 2700"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):227
+msgid "Qube 2800"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):229
+msgid "RaQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):231
+msgid "RaQ 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(th):236
+msgid "Broadcom-based 802.11g<br/> Broadband Internet Routers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri:link):241
+msgid "http://openwrt.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(uri):241
+msgid "Linksys WRT54G"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):246
+msgid ""
+"... and that's only just scratching the surface. These machines are wide and "
+"varied. Many of them do not currently run Linux. Of those that do, we only "
+"support a handful, although you're welcome to port Gentoo/MIPS to any MIPS "
+"machine if you so wish. Some of these machines are also the focus of the "
+"<uri link=\"http://embedded.gentoo.org\">Embedded Gentoo Project</uri> such "
+"as the Linksys WRT54G."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):258
+msgid "Is my machine supported?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):261
+msgid ""
+"This question is difficult to answer. Your machine could fall into one of "
+"three different baskets:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):267
+msgid "Your machine is supported by Gentoo/MIPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):268
+msgid "Your machine is supported by Linux/MIPS, but not by Gentoo/MIPS (yet)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):269
+msgid "Your machine is not supported by Linux/MIPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):272
+msgid ""
+"For the first one an easy way to find out is to have a look at the <uri link="
+"\"/doc/en/mips-requirements.xml\">Gentoo/MIPS requirements page</uri>. This "
+"will tell you if the system you've got can theoretically run Gentoo/MIPS. "
+"Stuart has also written a <uri link=\"http://stuartl.longlandclan.hopto.org/"
+"gentoo/mips/\">hardware support database</uri> in which users may contribute "
+"their experiences. This can help measure how well Gentoo/MIPS runs on a "
+"particular machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):282
+msgid ""
+"If you don't find your machine listed there, you may wish to have a look on "
+"the <uri link=\"http://www.linux-mips.org/wiki/index.php/Systems\">Linux/"
+"MIPS website</uri> to find it there. Installation won't be straightforward "
+"however, as the actual process of producing a kernel and suitable boot media "
+"for your hardware will have to be done largely by yourself. Naturally "
+"though, we'll try to help where we can."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):294
+msgid "Why don't you support machine X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):297
+msgid ""
+"If you've looked at the Gentoo/MIPS Hardware Requirements page, you've "
+"probably noticed there are a LOT of machines we don't support. In the case "
+"of SGI hardware, very little is known about some of them, not enough to "
+"successfully port Linux to them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):304
+msgid ""
+"If you managed to get Linux working on a box currently listed as "
+"<e>unsupported</e> however, feel free to tell us. We'd be interested to know."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):314
+msgid "MIPS Software FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):316
+msgid "Which stage tarball do I use?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):319
+msgid ""
+"This will depend on the CPU type running in your system. The stage filename "
+"is named as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(pre:caption):324
+msgid "Stage Tarball Naming Scheme"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(pre):324
+#, no-wrap
+msgid ""
+"\n"
+"  stage3-mipsel4-2005.0.tar.bz2\n"
+"  \\____/ \\_____/ \\____/\n"
+"     |      |       |\n"
+"     |      |       `--- Gentoo Release (e.g. 1.4, 2004.3, 2005.0)\n"
+"     |      |\n"
+"     |      `----------- Endianness and ISA Level\n"
+"     |                     mips   ==&gt; Big Endian\n"
+"     |                     mipsel ==&gt; Little Endian\n"
+"     |\n"
+"     |                     R3xxx and earlier: ISA Level 1\n"
+"     |                     R4xxx series:      ISA Level 3\n"
+"     |                     R5000 and above:   ISA Level 4\n"
+"     |\n"
+"     `------------------ Stage Tarball type: 1, 2 or 3.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):341
+msgid ""
+"So for those of you who are running R4000-class CPUs, try a <c>mips3</c> or "
+"<c>mipsel3</c> stage tarball."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):346
+msgid ""
+"For those running R5000-class or later CPUs, try a <c>mips4</c> or "
+"<c>mipsel4</c> stage tarball."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):351
+msgid ""
+"Sometimes the filename will have <c>n32</c> or <c>n64</c> in the filename as "
+"well. These refer to 64-bit userland images. At the moment, support for 64-"
+"bit userlands is still quite flaky and a lot of packages are broken. I'd "
+"suggest leaving these alone unless you're particularly brave and don't mind "
+"a rather bumpy ride."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):362
+msgid ""
+"I got told \"Illegal Instruction\" or \"Cannot Execute Binary File\" when "
+"chrooting. What did I do wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):366
+msgid ""
+"This is generally caused by using the wrong stage tarball. If you try to run "
+"a <c>mips4</c> userland on a <c>mips3</c> CPU, you'll get an <e>illegal "
+"instruction</e> error message. Likewise, if you have a Big Endian CPU and "
+"you try running Little Endian code on it, you'll get told <e>cannot execute "
+"binary file</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):374
+msgid ""
+"The fix is simple... clean out your partition, then unpack the correct "
+"tarball. Which one is that I hear you ask? Have a read of the previous FAQ "
+"entry."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):384
+msgid "Silicon Graphics Specific FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):386
+msgid "Why doesn't my SGI machine netboot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):389
+msgid ""
+"This could be for any number of reasons, ranging from cabling issues, "
+"through to issues on the server. The best way to troubleshoot any problem is "
+"a step-by-step approach..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):396
+msgid ""
+"<b>Have you got the SGI machine (and server) plugged into the right network "
+"ports?</b><br/> Make sure the network is cabled correctly. Also note that "
+"some machines have special needs. For instance the Challenge S cannot obtain "
+"network connectivity under Linux via its UTP port, you need to use the AUI "
+"port via a transceiver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):404
+msgid ""
+"<b>Are there any firewalls in use?</b><br/> Make sure your firewall is not "
+"blocking DHCP/BOOTP requests (ports 67 and 68 on UDP) or TFTP (port 69 on "
+"UDP).<br/><c>iptables -I INPUT 1 -p udp --dport 67:69 -j ACCEPT</c> should "
+"get things rolling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):411
+msgid ""
+"<b>Have you disabled packet MTU discovery and set the port range?</b><br/> "
+"SGI boxes require <path>/proc/sys/net/ipv4/ip_no_pmtu_disc</path> = 1 and "
+"<path>/proc/sys/net/ipv4/ip_local_port_range</path> = \"2048 32767\". See "
+"<uri link=\"/doc/en/handbook/handbook-mips.xml?part=1&amp;"
+"chap=2#doc_chap4\">the Gentoo/MIPS handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):419
+msgid ""
+"<b>Is the server giving out the correct details via BOOTP?</b><br/> Double "
+"check your <path>/etc/dhcp/dhcpd.conf</path>. ISC's dhcpd won't dish out "
+"addressing information via BOOTP unless the machine has been statically "
+"defined with a fixed address."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):425
+msgid ""
+"<b>Which TFTP server are you using?</b><br/><c>tftp-hpa</c> and <c>netkit-"
+"tftp</c> are known to work. <c>atftp</c> is a lot more advanced, this can "
+"cause problems. If in doubt, try installing <c>tftp-hpa</c> and see if the "
+"problem clears up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):431
+msgid ""
+"<b>Are the daemons running?</b><br/><c>dhcpd</c> should show up when typing "
+"<c>ps ax</c>. As for TFTP, it'll largely depend on whether its a standalone "
+"server, or if its running from <c>(x)inetd</c>. <c>tftp-hpa</c> runs as a "
+"process called <c>in.tftpd</c>. Look for that in the <c>ps ax</c> output and "
+"start any services not currently running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):439
+msgid ""
+"<b>Does the kernel exist in <path>/tftpboot</path>?</b><br/> Make sure you "
+"place the kernel image to be booted in this directory and that it is world-"
+"readable. (<c>chmod 644 /tftpboot/foo</c>) Also, in your <path>/etc/dhcp/"
+"dhcpd.conf</path>, note that the path to the kernel will be relative to the "
+"<path>/tftpboot</path> directory if you're using <c>tftp-hpa</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):447
+msgid ""
+"<b>Have you unset the <c>netaddr</c> and <c>dlserver</c> PROM variables?</"
+"b><br/> Try running <c>unsetenv netaddr</c> and <c>unsetenv dlserver</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):457
+msgid ""
+"The machine downloads the kernel, but then \"hangs\" (using a monitor and "
+"keyboard -- not serial console)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):461
+msgid ""
+"Unfortunately, not all graphics frame buffers are supported under Linux yet. "
+"This doesn't mean you can't use the machine... it just means you'll need a "
+"null-modem serial cable to interact with it. It is quite possible that the "
+"machine is in fact running, however, the system is outputting to the serial "
+"console rather than the screen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):474
+msgid "Cobalt Specific FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):476
+msgid "Why won't my Cobalt machine boot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):479
+msgid ""
+"This could be for a number of reasons. Our easiest bet however is to run "
+"through a checklist and make sure everything is correct."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):485
+msgid ""
+"<b>Have you got the Cobalt machine (and server) plugged into the right "
+"network ports?</b><br/> Make sure the network is cabled correctly. Please "
+"note, the Cobalt firmware will only boot via the Primary network port."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):491
+msgid ""
+"<b>Are there any firewalls in use?</b><br/> Make sure your firewall is not "
+"blocking DHCP/BOOTP requests (ports 67 and 68 on UDP) or RPC/Portmap (port "
+"111 on UDP and TCP).<br/><c>iptables -I INPUT 1 -p udp --dport 67:68 -j "
+"ACCEPT</c><br/><c>iptables -I INPUT 1 -p udp --dport 111 -j ACCEPT</c><br/"
+"><c>iptables -I INPUT 1 -p tcp --dport 111 -j ACCEPT</c> should get things "
+"rolling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):500
+msgid ""
+"<b>Is the server giving out the correct details via BOOTP?</b><br/> Double "
+"check your <path>/etc/dhcp/dhcpd.conf</path>. ISCs dhcpd won't dish out "
+"addressing information via BOOTP unless the machine has been statically "
+"defined with a fixed address."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):506
+msgid ""
+"<b>Are you exporting <path>/nfsroot</path> in your <path>/etc/exports</path>?"
+"</b><br/> Make sure you are exporting that to the Cobalt machine. It only "
+"needs read-only access. Also remember to run <c>exportfs -av</c> after you "
+"edit the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):513
+msgid ""
+"<b>Are the daemons running?</b><br/><c>dhcpd</c> should show up when typing "
+"<c>ps ax</c>. Likewise with <c>portmap</c> and the other RPC daemons. The "
+"following commands should look after this for you:<br/><c>/etc/init.d/dhcp "
+"start</c><br/><c>/etc/init.d/nfs start</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(li):521
+msgid ""
+"<b>Does the kernel exist in <path>/nfsroot</path>?</b><br/> Make sure you "
+"place the kernel image to be booted in this directory and that it is world-"
+"readable. (<c>chmod 644 /nfsroot/foo</c>)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(title):531
+msgid "Why don't you support the Qube 2700?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(p):534
+msgid ""
+"The Qube 2700 was the first of the Cobalt servers. While they are very nice "
+"machines, unfortunately, they lack a serial port. In other words, any "
+"interaction with the machine has to be done through a network. At present, "
+"our netboot images do not support this, although plans are in the works that "
+"may enable support for this machine."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-mips-install.xml.po b/doc/gettext/ru/gentoo-mips-install.xml.po
new file mode 100644
index 0000000..c4663dc
--- /dev/null
+++ b/doc/gettext/ru/gentoo-mips-install.xml.po
@@ -0,0 +1,60 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(guide:redirect):3
+msgid "/doc/en/handbook/handbook-mips.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(title):4
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(title):20
+msgid "Gentoo MIPS Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(author:title):6
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(mail:link):7
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(mail):7
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(abstract):10
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(version):16
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(date):17
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(p):24
+msgid ""
+"As of 2004.0, the individual architecture-specific installation guides have "
+"been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/"
+"handbook/handbook-mips.xml\">Gentoo Handbook</uri>. For more information "
+"please read up on the <uri link=\"/doc/en/handbook\">Gentoo Handbook "
+"Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-mips-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-ppc-faq.xml.po b/doc/gettext/ru/gentoo-ppc-faq.xml.po
new file mode 100644
index 0000000..ef822c7
--- /dev/null
+++ b/doc/gettext/ru/gentoo-ppc-faq.xml.po
@@ -0,0 +1,1553 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(guide:link):5
+msgid "/doc/en/gentoo-ppc-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):6
+msgid "Gentoo Linux/PowerPC Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):9
+msgid "rajiv@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail):9
+msgid "Rajiv Manglani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):12
+msgid "pylon@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail):12
+msgid "Lars Weiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):15
+msgid "sejo@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail):15
+msgid "Jochen Maes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):18
+msgid "josejx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail):18
+msgid "Joseph Jezak"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(mail:link):21
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(abstract):24
+msgid ""
+"The Gentoo/PPC FAQ is a collection of questions and answers collected from "
+"the Gentoo/PPC mailing lists and from IRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(version):33
+msgid "1.41"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(date):34
+msgid "2009-04-15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):37
+msgid "Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):39
+msgid "Introduction to the Gentoo/PPC FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):42
+msgid ""
+"This FAQ is a collection of questions and answers collected from the Gentoo/"
+"PPC mailing lists and from IRC. If you have any questions (or answers!), "
+"please contact either an author or a member of the documentation team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):54
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):56
+msgid ""
+"What kind of PowerPC computer do I have and where can I find more "
+"information about it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):62
+msgid ""
+"Welcome to Gentoo PPC! The PowerPC processor has been used in a number of "
+"popular computing devices, here are some links to help you figure out what "
+"type of hardware is in the machine on your desk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):70
+msgid "http://www.info.apple.com/support/applespec.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):70
+msgid "Apple Product Pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):75
+msgid "http://lowendmac.com/profiles.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):75
+msgid "Apple Product History and Details"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):80
+msgid "http://www.pegasosppc.com/products.php"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):80
+msgid "Genesi Model Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):85
+msgid ""
+"http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com."
+"ibm.pseries.doc/hardware_docs/selectbysystem.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):85
+msgid "IBM Documentation by Model"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):90
+msgid "http://kurobox.com/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):90
+msgid "KuroBox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri:link):93
+msgid "http://penguinppc.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(uri):93
+msgid "PenguinPPC - Linux on PowerPC Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):102
+msgid "How can I verify with OSX that the downloaded ISO is not corrupted?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):105
+msgid ""
+"First be sure you did not mount the ftp server with <e>Finder</e> and then "
+"copy the file with drag'n'drop. This will corrupt the ISO. Instead, use "
+"<c>curl</c> (with <c>curl -O http://path/to/iso</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):111
+msgid ""
+"You can check your MD5 sum using the <c>md5sum</c> tool provided with OSX. "
+"On versions of OSX without md5sum, you can use <c>openssl</c> capability to "
+"produce an md5 checksum."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):117
+msgid "Creating an md5sum with openssl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):117
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(This could take some time depending of the size of the ISO and your CPU)</comment>\n"
+"$ <i>openssl md5 /path/to/iso</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):122
+msgid ""
+"Now compare this output with the appropriate file found on the server where "
+"you downloaded the ISO (the file will end with <path>.md5</path>). If it is "
+"the same, the ISO image downloaded correctly. Be sure you have <e>not</e> "
+"mounted it (e.g. with Disk Copy) yet!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):132
+msgid "Can I dual-boot Gentoo Linux and Mac OS X?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):135
+msgid ""
+"Yes you can! In fact, <e>yabootconfig</e> will automatically detect and "
+"setup <path>/etc/yaboot.conf</path> with Linux, Mac OS X and even classic "
+"Mac OS (see the <uri link=\"/doc/en/handbook/handbook-ppc.xml?part=1&amp;"
+"chap=10\">Gentoo Handbook</uri> for details on yabootconfig). The trick is "
+"in how you partition your hard drive. Before installing Gentoo, startup with "
+"the Mac OS X Install CD. Use the <c>Disk Utility</c> to partition the drive "
+"in your machine into two or three partitions. Alternatively, use <c>parted</"
+"c> from a recent Gentoo InstallCD, since that has been patched to handle HFS "
+"and HFS+ partitions. Parted is also able to shrink a partition so you don't "
+"need to delete your existing install. The first partition should be big "
+"enough to contain all your Linux partitions (root+swap+/home etc.). The "
+"format of this partition does not matter. The second partition should be for "
+"OS X. The third (and optional) partition should be for classic Mac OS. It is "
+"only required if you intend of being able to triple boot, since OS9 must be "
+"on a separate partition from OSX for this to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):153
+msgid ""
+"After partitioning, install Mac OS X and Mac OS 9 onto their respective "
+"partitions. Once installation is complete, start following the <uri link=\"/"
+"doc/en/handbook/handbook-ppc.xml\">Gentoo Handbook</uri>. When you get to "
+"the section on partitioning, use <c>mac-fdisk</c> to <e>delete</e> the large "
+"partition you created for Gentoo. In its place, create a bootstrap "
+"partition, root, swap, and any other partitions you wish to use with Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):162
+msgid ""
+"If you have an OldWorld Macintosh (pre-iMac), follow a similar procedure as "
+"described above. However, use the Mac OS 9 install CD and the <c>Drive "
+"Setup</c> utility. OldWorld machines do not need a bootstrap partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):168
+msgid ""
+"If yabootconfig does not detect your MacOS partitions, you can manually add "
+"them to your yaboot.config. See the example yaboot.conf in the <uri link=\"/"
+"doc/en/handbook/handbook-ppc.xml?part=1&amp;chap=10#doc_chap2_pre6\"> "
+"handbook</uri> for details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):178
+msgid ""
+"I have an early NewWorld Mac such as the Blue and White G3. It should be "
+"compatible with the InstallCD, but on boot it returns an \"Unknown or "
+"corrupt filesystem\" error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):185
+msgid ""
+"As a workaround, boot into Open Firmware by holding down the Apple + Option "
+"+ O + F keys on startup. When the prompt appears, type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):190
+msgid "Early NewWorld Mac Open Firmware work around"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):194
+msgid ""
+"The CD should boot as expected now, thanks to John Plesmid for this "
+"workaround."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):201
+msgid ""
+"I have an OldWorld Macintosh and need to use BootX. However, I am having "
+"trouble opening the BootX installer archive. What can I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):207
+msgid ""
+"You will need a new version of <e>StuffIt Expander</e> to open the archive. "
+"You can <uri link=\"http://www.stuffit.com/expander/download.html\">download "
+"it</uri> for free."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):216
+msgid ""
+"I have a Beige G3 machine. Can I install Gentoo Linux/PPC on a second IDE "
+"hard drive?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):222
+msgid ""
+"Early Beige G3 machines (those with a \"Rev 1\" motherboard with an ATI "
+"RageII+ chip) do not support slave IDE drives. To use a second hard drive "
+"with this machine, you would have to attach it to the internal or external "
+"SCSI connector or install a PCI IDE card. Later G3 machines do not have this "
+"limitation. See <uri>http://www.xlr8yourmac.com/G3-ZONE/IDE/index.html</uri> "
+"for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):234
+msgid ""
+"I have a revision A or B iMac. I've replaced the hard drive with a larger "
+"one and now I can't boot into anything!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):240
+msgid ""
+"There is an 8GB limit for the root partition on these machines. Ensure that "
+"your root partition is less than 8GB and it should work as expected. This "
+"also applies to OS X and later versions of OS 9."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):249
+msgid ""
+"My /etc/fstab file has /dev/BOOT in it. Do I need to setup this line for my "
+"Apple bootstrap partition?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):255
+msgid ""
+"No. If you are not using a separate boot partition (<path>/boot</path>) then "
+"you do not need this line and can safely just delete it from <path>/etc/"
+"fstab</path>. The Apple bootstrap partition is <e>not</e><path>/boot</path> "
+"and is not related in any way. In general, Apple PowerPC machines do not "
+"need a separate <path>/boot</path> partition, and the bootstrap partition "
+"should not be mounted or referred to in your fstab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):267
+msgid ""
+"When I rebooted, yaboot didn't work! Now, I'm stuck. How can I fix this?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):272
+msgid ""
+"It's probably just a misconfigured yaboot.conf. The easiest way to fix this "
+"is to boot the InstallCD again, mount your gentoo partition and check yaboot."
+"conf for errors. You'll also need to run <c>ybin -v -C /mnt/gentoo/etc/"
+"yaboot.conf</c> to update the boot loader once you have finished. This can "
+"all be done without chrooting back into your install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):281
+msgid ""
+"If you <e>really</e> just need to get back to OSX, try holding down the "
+"Option key on startup. This should give you a graphical selection of "
+"bootable disks. Choose OSX and remember to fix your boot problems later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):290
+msgid "When I try to boot, yaboot only says \"read error\"! Why can't I boot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):295
+msgid ""
+"You're probably using XFS for your root partition. While this is an option, "
+"yaboot has some issues accessing files with holes. To ensure that your "
+"kernel will boot, instead of copying the vmlinux file to /boot, simply "
+"<c>cat</c> the kernel as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):302
+msgid "Fixing yaboot read errors on XFS with cat"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):302
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cat /usr/src/linux/vmlinux &gt; /boot/vmlinux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):309
+msgid ""
+"I installed an OSX update and now my computer only boots into OSX! How can I "
+"fix it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):315
+msgid ""
+"Hold down the option key on boot. This will bring you to a graphical boot "
+"device selector. Wait until a hard drive with a penguin shows up and click "
+"on the icon. This will boot your linux install as usual. Once you've booted, "
+"rerun <c>ybin -v</c> to fix the bootloader."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):325
+msgid ""
+"I can't boot the InstallCD! It stops while trying to set the hardware clock. "
+"What do I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):331
+msgid ""
+"Unfortunately, there was a bug in some versions of the baselayout scripts. "
+"To get the system booting, the hardware clock will need to be set. To set "
+"the clock boot into Open Firmware (using the key combination of Apple + O + "
+"F). Once you are at the Open Firmware prompt, you can set the clock using "
+"the command below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):339
+msgid "Setting the clock at the open firmware prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):339
+#, no-wrap
+msgid ""
+"\n"
+"<comment># decimal dev rtc sec min hour day month year set-time</comment>\n"
+"<comment># The example below sets the clock to 1:23:45 June, 7th, 2000</comment>\n"
+" ok\n"
+"0 &gt; decimal dev rtc 45 23 1 6 7 2000 set-time\n"
+" ok\n"
+"1 &gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):348
+msgid ""
+"Open Firmware will return with an ok after the clock is set. The system "
+"should boot normally now. Type <c>mac-boot</c> to continue booting after the "
+"clock is set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):359
+msgid "Hardware Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):361
+msgid ""
+"I'm running Gentoo on a PowerPC laptop. What packages should I install to "
+"enable laptop-specific functionality?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):367
+msgid "There are four main packages you will need to install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):372
+msgid ""
+"<e>pbbuttonsd</e> is a tool that enables the brightness and volume keys on "
+"most ppc laptops as well as other apple laptop specific functionality. The "
+"current versions also work as a power manager and replaces <e>pmud</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):377
+msgid ""
+"<e>powerprefs</e> provides a graphical configuration editing tool for "
+"configuring pbbuttonsd including settings such as power-management, trackpad "
+"options and various other preferences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):382
+msgid ""
+"<e>powernowd</e> allows cpu speed scaling for longer battery life. Other "
+"packages also provide the same functionality, such as <e>cpudyn</e>, "
+"<e>cpufreqd</e> and <e>speedfreq</e>. It doesn't really matter which you "
+"chose, just ensure that you have the <e>userspace</e> cpu frequency scaling "
+"governor enabled in your kernel. This is the only governor that will work on "
+"PPC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):392
+msgid ""
+"These packages can be installed by running the appropriate commands from the "
+"list below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):397
+msgid "Installing laptop-specific packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):397
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge pbbuttonsd</i>\n"
+"# <i>emerge powerprefs</i>\n"
+"# <i>emerge powernowd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):403
+msgid ""
+"You should edit <path>/etc/pbbuttonsd.conf</path> or use <e>powerprefs</e> "
+"to better suit your needs. The behaviour of the Fx-keys can be controlled "
+"here as well as many sleep options. To switch the Fx-keys to the OSX "
+"behaviour, set KBDMode to fkeyslast. You can turn off touchpad tapping by "
+"setting TPMode to notap. Many other options are available, see man "
+"pbbuttonsd.conf for details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):411
+msgid ""
+"It is useful to add pbbuttonsd and powernowd to your boot runlevel so that "
+"they're started when your computer starts. To do this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):416
+msgid "Adding pbbuttonsd and cpudyn to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):416
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add pbbuttonsd boot</i>\n"
+"# <i>rc-update add powernowd boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):424
+msgid ""
+"I only have one mouse-button. How can I make use of the second and third "
+"one, since ctrl-button does not work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):430
+msgid ""
+"There is no way to use ctrl-button like on Mac OS X, but you can map just "
+"about any key or combination of keys to emulate the second and third mouse-"
+"button. The values can be obtained with the command line utility <c>showkey</"
+"c> from the console. Note that this program does not work as expected from X "
+"and should only be run from the console. To use this feature, enable the "
+"following options in your kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):439
+msgid "Macintosh Device Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):439
+#, no-wrap
+msgid ""
+"\n"
+"[*] Apple Desktop Bus (ADB) support\n"
+"[*]    Use input layer for ADB devices\n"
+"[*]      Support for mouse button 2+3 emulation\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):445
+msgid ""
+"You will also need to set the keyboard to mouse button mapping values in "
+"<path>/etc/sysctl.conf</path>. Here is an example using F11 and F12:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):450
+msgid "Mouse button emulation with F11 and F12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):450
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Enable mouse button emulation</comment>\n"
+"dev.mac_hid.mouse_button_emulation = 1\n"
+"<comment># Set 2nd button to 87 - F11</comment>\n"
+"dev.mac_hid.mouse_button2_keycode = 87\n"
+"<comment># Set 3rd button to 88 - F12</comment>\n"
+"dev.mac_hid.mouse_button3_keycode = 88\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):459
+msgid ""
+"Other commonly used keycodes are 125 (The Apple key) and 96 (The Keypad "
+"Enter)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):463
+msgid "To activate these settings:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):467
+msgid "Applying the sysctl changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):467
+#, no-wrap
+msgid ""
+"\n"
+"# <i>sysctl -p /etc/sysctl.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):474
+msgid "How can I configure my Airport card?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):477
+msgid ""
+"The Airport card is an 802.11b device based on the Lucent Orinoco chipset. "
+"To use this card in Linux, enable these kernel options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):482
+msgid "Wireless LAN"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):482
+#, no-wrap
+msgid ""
+"\n"
+"[*] Wirless LAN Drivers &amp; Wireless Extensions\n"
+"&lt;*&gt; Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)\n"
+"&lt;*&gt;   Apple Airport support (build-in)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):488
+msgid ""
+"Once the kernel is configured, you'll also need some userland tools to "
+"configure the wireless settings. Emerge the <c>wireless-tools</c> for "
+"iwconfig and other wireless tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):494
+msgid "As an example of using iwconfig, to set your ESSID to home_essid:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):498
+msgid "Setting an ESSID"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):498
+#, no-wrap
+msgid ""
+"\n"
+"# <i>iwconfig eth1 essid home_essid</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):502
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):543
+msgid ""
+"For a generic guide to setting up wireless with Gentoo, please see the <uri "
+"link=\"/doc/en/handbook/handbook-ppc.xml?part=4&amp;chap=4\">Gentoo Wireless "
+"Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):511
+msgid "How can I configure my Airport Extreme card?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):514
+msgid ""
+"The Airport Extreme is an 802.11b/g card that is included with modern Apple "
+"portable computers. It is based on the Broadcom 43xx chipset which is "
+"supported by the native b43 driver project. It has been included in the "
+"2.6.24 kernel. Note that the driver should select the proper driver between "
+"b43 and b43-legacy. The firmware used for these two drivers is different, "
+"with the legacy version supporting older 4306 cards. If you have a 4306 "
+"card, build both, otherwise, it should be safe to only build b43. Also, to "
+"enable either driver, mac80211 must be selected first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):525
+msgid "Adding b43 support to the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):525
+#, no-wrap
+msgid ""
+"\n"
+"Networking --&gt; Wireless --&gt;\n"
+"     &lt;M&gt;   Generic IEEE 802.11 Networking Stack (mac80211)\n"
+"\n"
+"Device Drivers --&gt; Network device support --&gt;\n"
+"     [*] Wireless LAN (IEEE 802.11)\n"
+"     &lt;M&gt;   Broadcom 43xx wireless support (mac80211 stack)\n"
+"     [*]     Broadcom 43xx debugging\n"
+"     &lt;M&gt;   Broadcom 43xx-legacy wireless support (mac80211 stack)\n"
+"     [*]     Broadcom 43xx-legacy debugging\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):537
+msgid ""
+"After compiling your kernel, you'll need to emerge <c>b43-fwcutter</c> to "
+"install the firmware. For additional information, please see this <uri link="
+"\"http://forums.gentoo.org/viewtopic-t-409194.html\">forum post.</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):552
+msgid "Will the internal modem work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):555
+msgid ""
+"On older Macs, the internal modem is a regular serial device. In addition to "
+"ppp support and i2c support, enable this kernel option to use it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):560
+msgid "Serial Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):560
+#, no-wrap
+msgid ""
+"\n"
+"&lt;*&gt; PowerMac z85c30 ESCC support (CONFIG_SERIAL_PMACZILOG)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):564
+msgid ""
+"Newer Macs use a USB device which only has a driver from Linuxant. Unless "
+"you have purchased a key from Linuxant, this driver will only work at 14.4 "
+"and will not support FAX. To install the driver, emerge <c>net-dialin/"
+"hcfusbmodem</c> which will provide <path>/dev/ttySHCF0</path>. Then set up "
+"ppp like usual. Further information about the installation can be found at "
+"<uri>http://www.linuxant.com/drivers/hcf/install.html</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):576
+msgid "Does sleep work on my iBook/PowerBook?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):579
+msgid ""
+"Sleep (suspend to ram) works very well on all G3 iBooks and TiBooks. "
+"Recently, a kernel patch has been released that adds sleep support for G4 "
+"iBooks and Radeon based AlBooks. If you have one of these laptops, use "
+"gentoo-sources 2.6.11 (or newer) for built in support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):586
+msgid ""
+"Note that the 12\" PowerBook is not yet supported due to its nVidia chipset."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):593
+msgid "How do I get sound playback working?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):596
+msgid ""
+"There are two approaches to sound on modern kernels: OSS or ALSA. OSS is the "
+"older of the two options and has been deprecated, but still functions well "
+"for many older Macs. ALSA is the newer method and will continue to be "
+"supported in the future. We recommend that you use ALSA unless you have "
+"problems with it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):603
+msgid ""
+"If you include the OSS driver in your kernel, the ALSA driver will not load."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):607
+msgid ""
+"In addition to configuring the kernel, users who should have access to the "
+"audio devices need to be added to the appropriate group with the command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):612
+msgid "Adding users to the audio group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):612
+#, no-wrap
+msgid ""
+"\n"
+"# <i>gpasswd -a username audio</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):616
+msgid ""
+"If the kernel is set up correctly, but you can't hear any sound, ensure that "
+"the main mixer volume is turned up and that the device isn't muted!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):621
+msgid ""
+"The sound card on Macs is connected through the i2c Keywest/PowerMac bus, "
+"not the PCI bus. You will not see the card listed when viewing the PCI bus "
+"or when using alsaconf. This is less of a problem then you might imagine, "
+"because all Macs use the same driver for sound, but you will need to insure "
+"that you have i2c Keywest/PowerMac support in your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(impo):629
+msgid ""
+"If you compile in ALSA support, you need to also compile in i2c Keywest/"
+"PowerMac support. Failure to do this will result in kernel panics on boot!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):638
+msgid "Sound setup with ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):641
+msgid ""
+"For ALSA, we'll set up both the regular ALSA drivers and the OSS emulation "
+"layer so that we can still use legacy OSS only programs. In <c>make "
+"menuconfig</c> you'll need to select:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):647
+msgid "Kernel options for ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):647
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers - I2c support ---&gt;\n"
+"  I2C Hardware Bus Support ---&gt;\n"
+"    &lt;*&gt; Powermac I2C interface (Keywest on 2.6.15 and older)\n"
+"\n"
+"Device Drivers - Sound ---&gt;\n"
+"&lt;*&gt; Sound card support\n"
+"    Advanced Linux Sound Architecture ---&gt;\n"
+"    &lt; &gt;   PowerMac DMA sound support\n"
+"      &lt;*&gt; Advanced Linux Sound Architecture\n"
+"      &lt;*&gt; Sequencer support\n"
+"      &lt;*&gt; Sequencer dummy client\n"
+"      &lt;*&gt; OSS Mixer API\n"
+"      &lt;*&gt; OSS PCM (digital audio) API\n"
+"      [*] OSS Sequencer API\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):664
+msgid ""
+"Depending on the age of the machine, the correct sound driver should also be "
+"enabled. On more modern machines such as Aluminum PowerBooks, new iBooks or "
+"G5's the <c>Apple On-board Audio</c> driver should be used. For older "
+"machines, try the ALSA PowerMac driver instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):671
+msgid "ALSA Drivers - Choose only one"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):671
+#, no-wrap
+msgid ""
+"\n"
+"<comment>Older Machines</comment>\n"
+"    ALSA PowerMac devices ---&gt;\n"
+"        &lt;*&gt; PowerMac (AWACS, DACA, Burgundy, Tumbler, Keywest)\n"
+"<comment>Newer Machines</comment>\n"
+"    Apple Onboard Audio driver ---&gt;\n"
+"        &lt;*&gt; Apple Onboard Audio driver\n"
+"        &lt;*&gt;   layout-id fabric\n"
+"        &lt;*&gt;   support Onyx chip\n"
+"        &lt;*&gt;   support TAS chip\n"
+"        &lt;*&gt;   support Toonie chip\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):684
+msgid ""
+"You can also configure these as modules and ensure they're loaded on boot, "
+"but it's easier to simply compile it all in."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):689
+msgid ""
+"Please make sure that <c>PowerMac DMA sound support</c> is turned off, "
+"otherwise the ALSA module will not be able to load."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):694
+msgid ""
+"For more information on configuring ALSA, please see the <uri link=\"/doc/en/"
+"alsa-guide.xml\">Gentoo ALSA Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):699
+msgid ""
+"If you are using the alsa-driver package instead of building it into your "
+"kernel, the ALSA_CARDS variable should be set to <c>powermac</c> for older "
+"Macs or all of <c>aoa</c>, <c>aoa-fabric-layout</c>, <c>aoa-soundbus</c>, "
+"<c>aoa-soundbus-i2c</c>, <c>aoa-onyx</c>, <c>aoa-tas</c> and <c>aoa-toonie</"
+"c> for newer Macs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):710
+msgid "Sound setup with OSS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):713
+msgid "Again, only use this if you're not using ALSA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):715
+msgid "In <c>make menuconfig</c> you'll need to select:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):719
+msgid "Kernel options for OSS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):719
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers - I2c support ---&gt;\n"
+"  I2C Hardware Bus Support ---&gt;\n"
+"    &lt;*&gt; Powermac I2C interface (Keywest on 2.6.15 and older)\n"
+"\n"
+"Device Drivers - Sound ---&gt;\n"
+"&lt;*&gt; Sound card support\n"
+"  &lt;*&gt;   PowerMac DMA sound support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):729
+msgid "(or configure as modules and ensure they're loaded on boot)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):733
+msgid ""
+"If the <c>dmasound_pmac</c> module does not load, you probably need to "
+"enable <c>i2c-core</c> in the kernel or as a module."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):738
+msgid ""
+"If you are still using OSS sound, please test the ALSA drivers instead and "
+"report any regressions to the ALSA bugzila. Thanks!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):746
+msgid "How do I make my Mac power up after a power failure?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):749
+msgid ""
+"The Power Management Unit (PMU) in most Macs has the ability to turn the Mac "
+"on again after a power loss. This feature is controlled by the PMU options "
+"found in <path>/proc</path>. To enable this feature, set <c>server_mode</c> "
+"to 1, to disable it, set <c>server_mode</c> to 0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):756
+msgid "Enabling power on after power failure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):756
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"server_mode=1\" &gt; /proc/pmu/options</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):760
+msgid ""
+"Unfortunately, this setting is turned off again after the machine restarts. "
+"To ensure that your system always starts with power on after power failure "
+"enabled, add the line above to <path>/etc/conf.d/local.start</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):769
+msgid ""
+"I see lots of \"IN from bad port\" errors in my kernel dmesg, how do I fix "
+"that?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):774
+msgid ""
+"This is caused by drivers written for devices that you don't have on your "
+"system. These messages are usually harmless, but it's a good idea to disable "
+"the unused drivers anyway. See below to match up port numbers with kernel "
+"configuration options. Note that even if the numbers don't match, try "
+"disabling these kernel options anyway, most PPC machines don't use these "
+"drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):783
+msgid "IN from bad port 61 - Disable PC Speaker support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):783
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers - Input device support ---&gt;\n"
+"[*] Miscellanous devices ---&gt;\n"
+"      &lt; &gt; PC Speaker Support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):789
+msgid "IN from bad port 64 - Disable i8042 keyboard support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):789
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers - Input device support ---&gt;\n"
+"Hardware I/O Ports ---&gt;\n"
+"      &lt; &gt; Serial I/O support\n"
+"        &lt; &gt; i8042 PC Keyboard controller\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):796
+msgid "IN from bad port 2E9,2F9,3E9,3F9 - Disable 8250/16550 support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):796
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers - Character devices ---&gt;\n"
+"Serial drivers ---&gt;\n"
+"      &lt; &gt; 8250/16550 and compatible serial support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):802
+msgid ""
+"If you have another IN from bad port message that you're not sure about, "
+"please let us know!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):812
+msgid "Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):814
+msgid ""
+"I can't emerge a package, and get an error about it being masked. What "
+"should I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):820
+msgid ""
+"There are two common reasons why a package will not emerge: either it hasn't "
+"been tested on PPC or it has been tested, but hasn't yet been marked stable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):825
+msgid "The Package Hasn't Been Tested on PPC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):825
+#, no-wrap
+msgid ""
+"\n"
+"!!! All ebuilds that could satisfy \"bar\" have been masked.\n"
+"!!! One of the following masked packages is required to complete your request:\n"
+"- app-foo/bar-1.0 (masked by: missing keyword)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):831
+msgid ""
+"If your package hasn't yet been tested on PPC, you'll need to first mark the "
+"ebuild with the ppc keyword. This is done using the ekeyword tool which is "
+"part of the gentoolkit-dev package. To mark the ebuild ppc and regenerate "
+"the manifest file so that it reflects the changes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):838
+msgid "Adding the ppc keyword to app-foo/bar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):838
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ekeyword ppc /usr/portage/app-foo/bar/bar-1.0.ebuild</i>\n"
+"# <i>ebuild /usr/portage/app-foo/bar/bar-1.0.ebuild manifest</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):843
+msgid ""
+"Once the ebuild has been keyworded, you can now emerge it as usual. Test the "
+"application and if it works, <b>please</b> report it as a bug so one of the "
+"developers can add the keyword."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):849
+msgid ""
+"This change will only last until the next sync. If you need a more permanent "
+"fix, you can maintain a portage overlay. See the portage documentation for "
+"more information on maintaining an overlay."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):855
+msgid "The Package Hasn't Been Marked Stable on PPC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):855
+#, no-wrap
+msgid ""
+"\n"
+"!!! All ebuilds that could satisfy \"bar\" have been masked.\n"
+"!!! One of the following masked packages is required to complete your request:\n"
+"- app-foo/bar-1.0 (masked by: ~ppc keyword)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):861
+msgid ""
+"If your package already has the ~ppc keyword, you have two options. Either "
+"follow the above instructions and replace the ~ppc keyword with ppc, or you "
+"can use /etc/portage to unmask the specific package. The second option is "
+"preferred simply because it won't be undone by an emerge sync."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):868
+msgid "Using /etc/portage to unmask app-foo/bar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):868
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>echo \"=app-foo/bar-1.0 ~ppc\" &gt; /etc/portage/package.keywords</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):872
+msgid ""
+"If the /etc/portage directory does not exist, make sure to create it first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):876
+msgid ""
+"Now emerge the package as normal. Once you're sure the app is stable, "
+"<b>please</b> report this as a bug so the developers can add the keyword."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):884
+msgid "Does Gentoo/PPC have support for Flash?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):887
+msgid ""
+"Well, not really. Macromedia has not supplied a linux/ppc binary and open "
+"source implementations are incomplete at this time. However, there are two "
+"projects that can play many flash objects, <uri link=\"http://www.gnu.org/"
+"software/gnash/\">gnash</uri> and <uri link=\"http://swfdec.freedesktop.org/"
+"\">swfdec</uri>. Both are capable of playing back Youtube movies and lots of "
+"other popular content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):900
+msgid "Does Gentoo/PPC have a Java plugin?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):903
+msgid ""
+"Yes, a Java plugin is now available with IBM's Java 1.5 and 1.6. Note that "
+"not all Java applications work with these Java versions yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):911
+msgid "Is there an easy way to configure X?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):914
+msgid ""
+"Simply emerge <c>xac</c>. Once the package has been emerged, run <c>xac</c> "
+"to generate the config for your setup. If you would like to set a keyboard "
+"layout, you can use the --kbd-layout option. Note that although <c>xac</c> "
+"does set up DRM for most users, you may need to change your kernel "
+"configuration and emerge additional drivers to support the suggested "
+"configuration. Be sure that you've configured your kernel as shown in the "
+"question below for optimal performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):926
+msgid "What is required for DRM?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):929
+msgid ""
+"When emerging xorg-server, make sure the dri use flag is enabled. You should "
+"also set the VIDEO_CARDS variable in make.conf with your video card, "
+"VIDEO_CARDS=\"radeon\" for radeon support, VIDEO_CARDS=\"nv\" for nvidia "
+"support and so on. For a backup option, add fbdev to the list of "
+"VIDEO_CARDS, this driver should always work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):937
+msgid "Make sure in your kernel config you have the following options set:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):941
+msgid "Rage128 DRM kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):941
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers - Character devices ---&gt;\n"
+"  &lt;*&gt; /dev/agpgart (AGP Support)\n"
+"  [*] Apple UniNorth support\n"
+"  [*] Direct Rendering Manager (DRI support)\n"
+"  &lt;*&gt;   ATI Rage 128\n"
+"Device Drivers - Graphics Support ---&gt;\n"
+"  &lt;*&gt;   ATI Rage 128 display support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):951
+msgid "Radeon DRM kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):951
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers - Character devices ---&gt;\n"
+"  &lt;*&gt; /dev/agpgart (AGP Support)\n"
+"  [*] Apple UniNorth support\n"
+"  [*] Direct Rendering Manager (DRI support)\n"
+"  &lt;*&gt;   ATI Radeon\n"
+"Device Drivers - Graphics Support ---&gt;\n"
+"  &lt;*&gt;   ATI Radeon display support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):961
+msgid "nVidia kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):961
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers - Graphics Support ---&gt;\n"
+"  &lt;*&gt;   nVidia Framebuffer Support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):966
+msgid ""
+"There is currently no support for DRM on nVidia cards since nVidia has not "
+"released any drivers for PPC and there are no open drivers for 3D "
+"acceleration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):971
+msgid ""
+"Rebuild and install the kernel if necessary. After this, make sure you have "
+"booted to the native framebuffer (i.e. radeonfb or atyfb128 and <e>not</e> "
+"from offb or ofonly video), and run <c>xac</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(impo):977
+msgid ""
+"You may need to edit your <path>/etc/X11/xorg.conf</path> file depending on "
+"your card setup. Ensure that the device driver selected is either ati or "
+"your specific driver (r128 or radeon). Also check that the DRI extension is "
+"loaded and not commented out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):987
+msgid ""
+"I've installed X.org and configured it correctly, but the radeon driver is "
+"missing. What's wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):993
+msgid ""
+"Add the appropriate VIDEO_CARDS line to <path>/etc/make.conf</path> (specify "
+"r128 or radeon) and recompile <c>xorg-server</c> and <c>mesa</c> to rebuild "
+"the driver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1002
+msgid ""
+"I have a VBIOS or \"Invalid I/O allocation\" error in my xorg.log. Is this a "
+"problem?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1008
+msgid ""
+"No, this is simply X.org probing your video card. It attempts to open the "
+"x86 only video BIOS and fails, leaving one of these messages. It's harmless, "
+"don't worry about it!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1017
+msgid ""
+"When using OpenGL DRI or playing movies, the system sometimes freezes hard "
+"unexpectedly. What can I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1023
+msgid ""
+"Your system may not cope properly with AGP support. The easiest solution is "
+"to add the following line to the \"Device\" section of <path>/etc/X11/xorg."
+"conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):1029
+msgid "Forcing PCI mode for AGP-Cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):1029
+#, no-wrap
+msgid ""
+"\n"
+"Option       \"ForcePCIMode\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1033
+msgid ""
+"Also, there are some known issues with the composite extension, please "
+"disable this extension if you're having problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1038
+msgid ""
+"Finally, if you are still having trouble, please try disabling dri in your "
+"xorg.conf and see if the problems go away."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1046
+msgid ""
+"I recently emerged Xorg, but when using it, my international keyboard layout "
+"does not work correctly. The main keys work fine but I am unable to compose "
+"special characters like the \"at\" sign. The startx output says something "
+"like \"could not load keymap, falling back to default keymap\". What is "
+"wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1054
+msgid ""
+"Check that the permissions on <path>/var/tmp</path> are set to "
+"<path>drwxrwxrwx</path>. If not, change them by typing <c>chmod a+rwx /var/"
+"tmp</c>. This will allow Xorg to load keymaps properly again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1063
+msgid "How do I play Audio CDs?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1066
+msgid ""
+"NewWorld machines have no audio connection between their CD-ROM drive and "
+"their sound hardware. Therefore, audio information must be read as data and "
+"then piped to the sound hardware. This is possible using <e>Audacious</e>, "
+"which reads the audio off the CD over the ATA cable, decodes it in software "
+"and sends it to the sound card over the PCI bus as digital data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):1074
+msgid "Emerge audacious"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):1074
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge audacious</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1078
+msgid ""
+"To play a CD, just fire up <c>audacious</c>. If you're having playback "
+"trouble, you may need to open up the Preferences--&gt;Plugins--&gt;CD Audio "
+"Plugin menu and select your CD drive. Make sure that \"Digital audio "
+"extraction\" is checked."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1087
+msgid "Can I run Mac OS 9 or Mac OS X under Gentoo Linux?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1090
+msgid ""
+"Yes, as long as you are running Gentoo Linux on 32 bit PPC hardware, you can "
+"use <uri link=\"http://www.maconlinux.org/\">Mac-on-Linux</uri> which allows "
+"you to run an instance of OS 9, OS X or Linux as a process on Linux. Simply "
+"<c>emerge mol</c> to install this package. MOL supports Mac OS 7.5.2 to "
+"9.2.2, as well as any version of OS X. It can be run from a console "
+"framebuffer or run in a window on X."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):1099
+msgid ""
+"Currently, there is no support for running MOL on 64 bit PowerPC Processors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):1103
+msgid ""
+"To run MOL fullscreen, you'll need to compile MOL with the fbcon use flag "
+"enabled and run it in a console framebuffer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1108
+msgid ""
+"For networking and sound you should install the drivers in the folder "
+"<path>MOL-Install</path> on your Mac OS X-Desktop. If errors with networking "
+"occur, make sure you have the following kernel options enabled:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1114
+msgid "For OSX Networking:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1119
+msgid "Universal TUN/TAP device driver support (CONFIG_TUN)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1122
+msgid "For the DHCP server:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1127
+msgid "Socket Filtering (CONFIG_FILTER)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1128
+msgid "Packet Socket (CONFIG_PACKET)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1131
+msgid "For NAT:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1136
+msgid "Network packet filtering (CONFIG_NETFILTER)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1137
+msgid "Connection tracking (CONFIG_IP_NF_CONNTRACK)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1138
+msgid "IP tables support (CONFIG_IP_NF_IPTABLES)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1139
+msgid "Packet filtering (CONFIG_IP_NF_FILTER)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1140
+msgid "Full NAT (CONFIG_IP_NF_NAT)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(li):1141
+msgid "MASQUERADE target support (CONFIG_IP_NF_TARGET_MASQUERADE)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1147
+msgid "Can I access my ext2/ext3 partitions from OSX?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1150
+msgid ""
+"OSX can support the reading and writing of ext2/ext3 partitions by using the "
+"kernel extension provided by the <uri link=\"http://sourceforge.net/projects/"
+"ext2fsx\">ext2fsx project.</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(note):1156
+msgid ""
+"When using MOL, you cannot access a partition that is currently being used "
+"by Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1164
+msgid "Which Portage USE flags do not work on PowerPC machines?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1167
+msgid ""
+"If you're using an old flat profile, (deprecated, pre 2005.0) look at <path>/"
+"etc/make.profile/use.mask</path> for a list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1172
+msgid ""
+"If you're using a cascaded profile, (2005.0 and onwards) look at <path>/usr/"
+"portage/profiles/default-linux/ppc/use.mask</path> for a list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1180
+msgid "How can I set up distcc with my x86 box?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1183
+msgid ""
+"If you've got another faster computer, you can set up distcc to compile "
+"binaries for your slower ppc processor. It's better to do as much building "
+"as possible on the faster machine; if possible, don't even build on the "
+"slower computer. Read the <uri link=\"/doc/en/cross-compiling-distcc.xml"
+"\">DistCC Cross-compiling Guide</uri> to learn how. You may also want to "
+"read the <uri link=\"/proj/en/base/embedded/handbook/\">Gentoo Embedded "
+"Handbook</uri> to learn more about cross-compiling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1196
+msgid "Why does gcc keep segfaulting during ebuilds?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1199
+msgid ""
+"If gcc segfaults during ebuilds, this probably isn't a bug with gcc and "
+"isn't even a problem with your hardware. Most of the time this problem is "
+"due to kernel preemption being enabled. Although this option is safe on x86, "
+"it can cause cache corruption on PPC which is why it is noticed most "
+"frequently during compiles. To prevent this from happening, simply recompile "
+"the kernel with preempt turned off. To check if preempt is enabled:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre:caption):1208
+msgid "Check if preempt is enabled"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(pre):1208
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>grep PREEMPT /usr/src/linux/.config</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1212
+msgid ""
+"If returns: \"# CONFIG_PREEMPT is not set\", then you should report the "
+"segfault as a bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1217
+msgid ""
+"If it returns: \"CONFIG_PREEMPT=y\", then you'll need to disable it and "
+"rebuild your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1227
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1229
+msgid "Can I buy a CD of Gentoo Linux/PPC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1232
+msgid ""
+"Yes! We sell Gentoo on CD-ROM in our <uri link=\"http://store.gentoo.org/"
+"\">Gentoo store</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(title):1240
+msgid "This FAQ hasn't answered my question. What do I do now?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1243
+msgid ""
+"A good first step is to browse through the relevant <uri link=\"/doc/en/"
+"index.xml\">documentation on www.gentoo.org</uri>. Two PPC-specific <uri "
+"link=\"/main/en/lists.xml\">mailing lists</uri> currently exist, gentoo-ppc-"
+"dev and gentoo-ppc-user. <uri link=\"http://forums.gentoo.org/viewforum.php?"
+"f=24\">Gentoo on PPC</uri> (on forums.gentoo.org) is an open bulletin-board "
+"for discussion of all PowerPC issues. Also, there is usually a lively "
+"discussion on IRC. Join us on <c>#gentoo-ppc</c> on <c>irc.freenode.net</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(p):1254
+msgid ""
+"General information about Linux on PowerPC can be found at <uri link="
+"\"http://penguinppc.org/\">penguinppc.org</uri>. General Linux information "
+"is at <uri link=\"http://www.linuxdoc.org/\">www.linuxdoc.org</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-ppc-install.xml.po b/doc/gettext/ru/gentoo-ppc-install.xml.po
new file mode 100644
index 0000000..288a04f
--- /dev/null
+++ b/doc/gettext/ru/gentoo-ppc-install.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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(guide:link):4
+msgid "/doc/en/gentoo-ppc-install.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(guide:redirect):4
+msgid "/doc/en/handbook/handbook-ppc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(title):5
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(title):21
+msgid "Gentoo PPC Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(mail:link):8
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(mail):8
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(abstract):11
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(version):17
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(date):18
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(p):25
+msgid ""
+"As of 2004.0, the individual architecture-specific installation guides have "
+"been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/"
+"handbook/handbook-ppc.xml\">Gentoo Handbook</uri>. For more information "
+"please read up on the <uri link=\"/doc/en/handbook\">Gentoo Handbook "
+"Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-ppc-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-security.xml.po b/doc/gettext/ru/gentoo-security.xml.po
new file mode 100644
index 0000000..68c6276
--- /dev/null
+++ b/doc/gettext/ru/gentoo-security.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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(guide:link):5
+msgid "/doc/en/gentoo-security.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(guide:redirect):5
+msgid "/doc/en/security/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(title):6
+msgid "Obsolete Gentoo Linux Security Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(mail:link):8
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(mail):8
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(abstract):11
+msgid "This was a step-by-step guide for hardening Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(version):15
+msgid "1.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(date):16
+msgid "2005-06-01"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(title):19
+msgid "Obsolete"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(p):23
+msgid ""
+"This guide has been replaced by the <uri link=\"/doc/en/security/\">Gentoo "
+"Security Handbook</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-security.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-sparc-faq.xml.po b/doc/gettext/ru/gentoo-sparc-faq.xml.po
new file mode 100644
index 0000000..4b23d37
--- /dev/null
+++ b/doc/gettext/ru/gentoo-sparc-faq.xml.po
@@ -0,0 +1,778 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):6
+msgid "Gentoo Linux/SPARC Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(author:title):8
+msgid "SPARC Developer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(mail:link):9
+msgid "weeve"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(abstract):15
+msgid ""
+"This FAQ is designed to help answer the most commonly asked questions about "
+"Gentoo/SPARC and Linux on SPARC architecture. Feel free to send revisions "
+"and corrections to the Gentoo/SPARC team or the doc team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(version):25
+msgid "1.12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(date):26
+msgid "2010-03-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):29
+msgid "Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):31
+msgid "Documentation Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):34
+msgid ""
+"These are some notes to elaborate on acronyms and terms used in this "
+"document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):38
+msgid ""
+"When mentioning <c>SPARC</c>, this refers to the type of <c>sun4x</c> "
+"system. SPARC represents the <c>sun4u</c> architecture seen in the "
+"UltraSPARC series of systems (Ultras, Blades, SunFires, etc). Older 32-bit "
+"systems are no longer supported by the Gentoo/SPARC team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):45
+msgid "Acronyms: <c>OBP</c> = OpenBoot PROM, <c>SS</c> = SPARCstation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):54
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):56
+msgid "How do I install/use my SPARC over a serial console?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):59
+msgid ""
+"First, make sure you do not have a keyboard and monitor plugged in. OBP will "
+"use the monitor for output by default if either are plugged in. You will "
+"need a null modem cable or a regular serial cable with a null modem adapter "
+"to be able to view output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):66
+msgid "Standard serial port settings:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):71
+msgid "9600 baud"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):72
+msgid "8 data bits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):73
+msgid "None for parity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):74
+msgid "1 stop bits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):77
+msgid ""
+"Below is a list of commonly used programs for viewing a serial console. "
+"Check to see if your serial console application has the ability to send a "
+"break, as it can be very useful on a SPARC. The break signal on a serial "
+"console is the equivalent to issuing the Stop+A command on the keyboard."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(th):86
+msgid "Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(th):87
+msgid "Windows"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):90
+msgid "Minicom"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):91
+msgid "Hyperterm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):94
+msgid "Kermit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):95
+msgid "TeraTerm Pro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):98
+msgid "Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(ti):102
+msgid "Seyon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):111
+msgid ""
+"I have a CRT/LCD monitor attached to my SPARC that selects a resolution my "
+"monitor can't handle when the kernel boots. How do I get a visible and/or "
+"non-distorted display on my monitor?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):116
+msgid ""
+"This problem is a result of the framebuffer support the Linux kernel loads "
+"at boot time, and the modelines available on SPARC systems. Here we will "
+"assume your monitor and video card will agree on a resolution of 1024 by 768 "
+"at a refresh rate of 60 Hz. In OBP, you can set the resolution by adjusting "
+"the setting for <c>output-device</c>. To view the current setting, use the "
+"command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):124
+msgid "View current settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):124
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>printenv output-device</i>\n"
+"\n"
+"<comment>&lt;output-device&gt;        &lt;screen&gt;          &lt;screen&gt;</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):130
+msgid ""
+"Now, to set this so it will start the display using the above mentioned "
+"resolution, we will use the <c>setenv</c> command as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):135
+msgid "Setting display"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):135
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>setenv output-device screen:r1024x768x60</i>\n"
+"\n"
+"output-device =       screen:r1024x768x60\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):141
+msgid "In order for this to take effect, you will need to reset the machine:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):145
+msgid "Resetting the machine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):145
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>reset</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):149
+msgid ""
+"Additionally, for users using the onboard video card based on the ATI Mach64 "
+"chipset (Ultra 5/10 and Blade 100/150), you will want to append the "
+"following to your kernel boot options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):155
+msgid "Appending a kernel boot option"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):155
+#, no-wrap
+msgid ""
+"\n"
+"video=atyfb:1024x768@60\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):159
+msgid ""
+"If you are booting from SILO, you can append the above string onto the end "
+"of a given boot image. The following example would be if you were booting "
+"from the LiveCD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):165
+msgid "Booting a Gentoo LiveCD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):165
+#, no-wrap
+msgid ""
+"\n"
+"boot: <i>gentoo video=atyfb:1024x768@60</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):169
+msgid ""
+"If you were booting from the network, you would append the string onto the "
+"end of the boot net command in OBP as illustrated below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):174
+msgid "Booting from the net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):174
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>boot net video=atyfb:1024x768@60</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):181
+msgid "I'm new to SPARC and am not sure what kernel options to use, HELP!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):185
+msgid ""
+"Most of the time, the default kernel options will be acceptable for hardware "
+"support. You will need to make sure that <c>virtual memory</c> and <c>/proc "
+"filesystem</c> support is enabled in the kernel as instructed in the <uri "
+"link=\"/doc/en/handbook/handbook-sparc.xml\">Installation Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):195
+msgid "How do I dual boot Gentoo Linux/SPARC with Solaris?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):198
+msgid ""
+"Dual booting Gentoo/SPARC and Solaris can be done one of two ways. The two "
+"ways are: having both Gentoo/SPARC and Solaris on the same drive, or having "
+"them on separate drives. Below are example SILO configurations for each "
+"scenario. In the example configs, the following things are assumed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):205
+msgid "Single Drive Setup:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):210
+msgid "Boot drive is SCSI ID 0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):211
+msgid "Gentoo boots from partition 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):212
+msgid "Solaris boots from partition 5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):215
+msgid "Separate Drive Setup:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):220
+msgid "Second drive is SCSI ID 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):221
+msgid "Gentoo is on SCSI ID 0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):222
+msgid "Solaris is on SCSI ID 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):223
+msgid "boot-device in OBP is SCSI ID 0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):227
+msgid "Sample silo.conf for a single drive installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):227
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Generic config options</comment>\n"
+"partition = 1\n"
+"timeout = 50\n"
+"\n"
+"<comment># Gentoo/SPARC options</comment>\n"
+"image = /boot/vmlinux\n"
+"    label = linux\n"
+"    root=/dev/sda4\n"
+"\n"
+"<comment># Solaris options</comment>\n"
+"other=5\n"
+"    label = Solaris\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):242
+msgid "Sample silo.conf for separate disk installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):242
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Generic config options</comment>\n"
+"parition = 1\n"
+"timeout = 50\n"
+"\n"
+"<comment># Gentoo/SPARC options</comment>\n"
+"image = /boot/vmlinux\n"
+"    label = linux\n"
+"    root=/dev/sda4\n"
+"\n"
+"<comment># Solaris options</comment>\n"
+"other = /sbus/espdma/esp/sd@1,0;1\n"
+"    label = solaris\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):262
+msgid "Hardware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):264
+msgid "Will Gentoo run on my SPARC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):267
+msgid ""
+"It depends on the type of SPARC, but chances are yes. One exception seems to "
+"be the SPARC based laptops from Tadpole, particularly the newer models. If "
+"you have a working Tadpole on Gentoo/SPARC, please contact us and let us "
+"know the details on the model and anything special needed to get it to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):274
+msgid ""
+"The Gentoo/SPARC team maintains a <uri link=\"/proj/en/base/sparc/sunhw.xml"
+"\">hardware compatibility list</uri> for SPARC64 systems. In general, "
+"support for SPARC64 systems is good enough to allow some users to run it "
+"successfully in production environments."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):284
+msgid "What additional hardware is supported under Gentoo/SPARC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):287
+msgid ""
+"For a list of additionally supported Sun hardware, consult the following "
+"list from the <uri link=\"http://www.ultralinux.org/faq.html#q_2_2."
+"\">UltraLinux homepage</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):293
+msgid ""
+"A partial list of Sun devices which do NOT currently have support under "
+"Gentoo/SPARC or SPARC/Linux in general are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):299
+msgid "SunPCI cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):300
+msgid "SBUS or PCI PCMCIA controllers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):301
+msgid "Smart card readers on some Sun Blade workstations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):302
+msgid "Floppy drive on some Sun Blade workstations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):305
+msgid ""
+"Also, the Gentoo/SPARC team maintains a <uri link=\"/proj/en/base/sparc/"
+"hwlist.xml\">list of non-Sun PCI hardware that has been tested on Gentoo/"
+"SPARC</uri>. To submit additions to the list, email <mail>sparc@gentoo.org</"
+"mail> with the information on the hardware as displayed in the existing "
+"hardware list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):316
+msgid "How do I know which SPARC I have?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):319
+msgid ""
+"The <uri link=\"http://www.ultralinux.org/faq.html#q_2_1\">UltraLinux FAQ</"
+"uri> has the answer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):327
+msgid ""
+"My box has more than one Sun Ethernet device. Why do they all have the same "
+"MAC address and how do I fix it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):331
+msgid ""
+"First, the reason they all they all have the same setting is due to a value "
+"in OpenBoot PROM (OBP). The story goes that in times past, it was assumed "
+"that if a host had multiple interfaces, the interfaces would not reside on "
+"the same Ethernet and therefore having the MAC address unique to a machine "
+"rather than to a NIC wouldn't be a problem. As time went on and different "
+"technologies developed, the opposite was proven."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):340
+msgid ""
+"As for fixing the issue, there are two ways to it; from OBP and from Linux. "
+"The OBP variable <c>local-mac-address?</c> controls this behavior. The "
+"following commands will help you to determine what <c>local-mac-address?</c> "
+"is set to:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):346
+msgid "View local-mac-address? setting from OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):346
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>printenv local-mac-address?</i>\n"
+"local-mac-address? =  false\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):351
+msgid "View local-mac-address? setting from Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):351
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eeprom local-mac-address?</i>\n"
+"local-mac-address?=false\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):356
+msgid ""
+"As you'll notice from the samples above, <c>local-mac-address?</c> is set to "
+"<b>false</b>. This will cause all interfaces on a SPARC to use the same MAC "
+"address. To change this behavior, use either of the commands below "
+"(depending on whether you do it from OBP or Linux):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):363
+msgid "Set local-mac-address? from OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):363
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>setenv local-mac-address?=true</i>\n"
+"local-mac-address? =  true\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):368
+msgid "Set local-mac-address? from Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):368
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eeprom local-mac-address?=true</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):372
+msgid "Note that you may need to reboot to see the changes take affect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):379
+msgid "Is SPARC big-endian or little-endian?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):382
+msgid ""
+"The version supported by Gentoo/SPARC (v9) is bi-endian. It uses big-endian "
+"instructions, but can access data in little-endian byte-order, such as PCI "
+"devices, which are little-endian by nature."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):393
+msgid "Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):395
+msgid ""
+"How do I get Xorg to find a usable modeline on my Ultra 5/10 or Blade "
+"100/150?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):400
+msgid ""
+"The ATI Framebuffer normally expects a PC's BIOS to set the Reference Clock "
+"speed for the video card. However, on non-x86 architectures, this doesn't "
+"happen. So what needs to be done is to set the Reference Clock speed in the "
+"<path>/etc/X11/xorg.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):407
+msgid ""
+"In the \"Device\" section of your <path>/etc/X11/xorg.conf</path>, you will "
+"want to add a line similar to the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):412
+msgid "Add to xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):412
+#, no-wrap
+msgid ""
+"\n"
+"Option      \"reference_clock\"   \"28.636 MHz\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):416
+msgid ""
+"Other common speeds are 14.318 MHz and 29.5 MHz. If you have issues you "
+"might want to try without a similar setting first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):424
+msgid "How come package foo is masked on SPARC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):427
+msgid ""
+"Chances are this is due to the fact that none of the Gentoo/SPARC developers "
+"have gotten around to testing this yet, and/or the package is currently "
+"marked with the <c>~sparc</c> keyword (meaning it's in a testing phase)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):433
+msgid ""
+"If you still want to install the package, you can follow the instructions "
+"from the <uri link=\"/doc/en/handbook/handbook-sparc.xml?part=3&amp;"
+"chap=3\">Portage Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):442
+msgid "How can I help get package foo marked stable?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):445
+msgid ""
+"If you want to help ensure a package gets marked stable in a timely fashion, "
+"particularly if it's an application with a small userbase (i.e. net-im/"
+"bitlbee), install the package and test to make sure it works. If it appears "
+"to be working well, feel free to file a bug via the <uri link=\"http://bugs."
+"gentoo.org\">Gentoo Bugzilla</uri> and assign it to the Gentoo/SPARC team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):457
+msgid ""
+"I tried to emerge a package, but emerge failed complaining that a dependency "
+"is masked. How can I fix this?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):461
+msgid ""
+"This is a bug. Please file a bug report via the <uri link=\"http://bugs."
+"gentoo.org\">Gentoo Bugzilla</uri> for the Gentoo/SPARC team indicating what "
+"package you tried to emerge, the error message emerge gave you, and the "
+"output of <c>emerge --info</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):471
+msgid "Why am I getting an error related to 32/64-bit when compiling a kernel?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):475
+msgid ""
+"The way SPARC/Linux handles the cross-compiler has changed with 2.6.25 (<uri "
+"link=\"http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;"
+"a=commitdiff;h=54cd6ddec77b75e6926d73d263aec72255b24030\">commit</uri>), "
+"thus when building a recent kernel you'd get the following error message:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):481
+msgid "SPARC/Linux compile error message"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):481
+#, no-wrap
+msgid ""
+"\n"
+"CHK     include/linux/version.h \n"
+"CHK     include/linux/utsrelease.h \n"
+"CC      arch/sparc64/kernel/asm-offsets.s \n"
+"arch/sparc64/kernel/asm-offsets.c:1: error: -m64 is not supported by this configuration \n"
+"arch/sparc64/kernel/asm-offsets.c:1: error: -mlong-double-64 not allowed with -m64 \n"
+"arch/sparc64/kernel/asm-offsets.c:1: error: -mcmodel= is not supported on 32 bit systems \n"
+"make[1]: *** [arch/sparc64/kernel/asm-offsets.s] Error 1 \n"
+"make: *** [prepare0] Error 2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):492
+msgid ""
+"Because, for the moment (there's an <b>experimental</b><uri link=\"/proj/en/"
+"base/sparc/multilib.xml\">multilib</uri> profile), Gentoo/SPARC native "
+"compiler can't generate 64-bit code (that's what sys-devel/kgcc64 is for)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):499
+msgid ""
+"What you need to do is to tell the SPARC/Linux Makefile what is your cross-"
+"compiler's binary, by issuing the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre:caption):504
+msgid "Gentoo/SPARC kernel &gt;=2.6.25 kernel compilation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(pre):504
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make CROSS_COMPILE=sparc64-unknown-linux-gnu-</i>\n"
+"# <i>make CROSS_COMPILE=sparc64-unknown-linux-gnu- image modules_install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):515
+msgid "Miscellaneous"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):517
+msgid ""
+"I'm interested in becoming more involved with Gentoo/SPARC. How do I go "
+"about doing that?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(p):521
+msgid "There are various ways to improve the project:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):526
+msgid ""
+"The best way is to become an <uri link=\"/proj/en/base/sparc/at/index.xml"
+"\">Arch Tester</uri>, and aid the developers with package testing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):530
+msgid ""
+"File bug reports such as <uri link=\"http://dev.gentoo.org/~tcunha/reports/"
+"imlate-sparc.txt\">stable, and keyword</uri> requests."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):534
+msgid ""
+"Join the <uri link=\"irc://irc.gentoo.org/gentoo-sparc\">#gentoo-sparc</uri> "
+"IRC channel on the FreeNode IRC network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):538
+msgid ""
+"Make use of the <uri link=\"http://forums.gentoo.org/viewforum.php?"
+"f=27\">Gentoo/SPARC forum</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):541
+msgid ""
+"Propose solutions for Gentoo/SPARC related bugs via the <uri link=\"http://"
+"bugs.gentoo.org\">Gentoo Bugzilla</uri>. The bugs will be assigned, or CCed "
+"to sparc@gentoo.org."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):552
+msgid "Additional Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(title):554
+msgid "Where can I get more help or information about SPARC/Linux?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):558
+msgid ""
+"<uri link=\"http://docs.sun.com/app/docs/coll/216.2\">OBP Reference Guide</"
+"uri> - Sun's guide to the OpenBoot PROM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):562
+msgid ""
+"<uri link=\"http://www.sunstuff.org\">OSIAH</uri> - Online Sun Information "
+"Archive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):566
+msgid ""
+"<uri link=\"http://www.obsolyte.com\">Obsolyte</uri> - Information on older "
+"SPARC systems and links to a lot of other great SPARC related sites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):570
+msgid ""
+"<uri link=\"http://docs.sun.com\">Sun Microsystems Documentation</uri> - "
+"Additional hardware and software information for SPARC systems, including "
+"instructions for flashing OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):575
+msgid ""
+"<uri link=\"http://sunsolve.sun.com\">Sunsolve</uri> - Great resource for "
+"Sun hardware documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(li):579
+msgid ""
+"<uri link=\"http://www.ultralinux.org\">UltraLinux Homepage</uri> - Homepage "
+"of the SPARC/Linux port"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-sparc-install.xml.po b/doc/gettext/ru/gentoo-sparc-install.xml.po
new file mode 100644
index 0000000..b764074
--- /dev/null
+++ b/doc/gettext/ru/gentoo-sparc-install.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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(guide:link):4
+msgid "/doc/en/gentoo-sparc-install.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(guide:redirect):4
+msgid "/doc/en/handbook/handbook-sparc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(title):5
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(title):21
+msgid "Gentoo SPARC Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(mail:link):8
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(mail):8
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(abstract):11
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(version):17
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(date):18
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(p):25
+msgid ""
+"As of 2004.0, the individual architecture-specific installation guides have "
+"been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/"
+"handbook/handbook-sparc.xml\">Gentoo Handbook</uri>. For more information "
+"please read up on the <uri link=\"/doc/en/handbook/\">Gentoo Handbook "
+"Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-sparc-netboot-howto.xml.po b/doc/gettext/ru/gentoo-sparc-netboot-howto.xml.po
new file mode 100644
index 0000000..c321b04
--- /dev/null
+++ b/doc/gettext/ru/gentoo-sparc-netboot-howto.xml.po
@@ -0,0 +1,866 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):6
+msgid "Gentoo Linux based Netboot HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(author:title):8
+msgid "SPARC Developer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(mail:link):9
+msgid "weeve"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(abstract):15
+msgid ""
+"Guide for setting up a netboot server for use with the Gentoo/SPARC netboot "
+"installation images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(version):24
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(date):25
+msgid "2010-10-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):32
+msgid ""
+"This howto is currently very SPARC-centric and expecting that you will be "
+"setting up your netboot server on an existing Gentoo Linux machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):37
+msgid ""
+"This document will describe how to setup a network booting environment for a "
+"Sun Microsystems SPARC or UltraSPARC based computer. The document assumes "
+"that you have an existing Gentoo Linux computer available to act as the "
+"netboot server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):44
+msgid ""
+"Both the netboot server and netboot client will need to be on the same "
+"network subnet, as the ARP protocol is typically not forwarded across "
+"different network subnets."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):50
+msgid ""
+"A generic overview of what happens during the netboot process is as follows;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):55
+msgid ""
+"Client machine sends out a reverse ARP (RARP) request to get an IP address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):58
+msgid "A server machine returns a response to the client with the IP address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):59
+msgid ""
+"The client then attempts to download a boot image from the RARP server using "
+"the TFTP protocol"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):63
+msgid "Once the image is downloaded, the netboot client then boots the image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):66
+msgid ""
+"Based on this overview, we will need to install software for a reverse ARP "
+"daemon and a TFTP daemon."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):76
+msgid "Software Installation And Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):78
+msgid "The Reverse ARP Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):81
+msgid ""
+"A reverse ARP daemon is already installed on your system; it's part of the "
+"<c>net-misc/iputils</c> package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):86
+msgid "<b>Setting up common rarpd elements</b>: <path>/etc/ethers</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):90
+msgid ""
+"You will need to setup the <path>/etc/ethers</path> file. This file "
+"indicates which hosts <c>rarpd</c> should respond to when a request is seen, "
+"and what address to reply with."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):96
+msgid ""
+"The format of <path>/etc/ethers</path> is the MAC address of the NIC the "
+"machine will be netbooting and its hostname. Whitespace delimits the MAC "
+"address from the hostname, and each entry should have its own line. The "
+"following example is for a host named sparc-netboot.gentoo.org:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):103
+msgid "Example /etc/ethers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):103
+#, no-wrap
+msgid ""
+"\n"
+"08:00:20:77:1f:3e  sparc-netboot.gentoo.org\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):107
+msgid ""
+"If a given hexadecimal number in the MAC address starts or is 0, you can "
+"chose to omit the first 0 (i.e. 08:00:20:77:1f:3e becomes 8:0:20:77:1f:3e)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):112
+msgid ""
+"If you desire to add additional hosts to <path>/etc/ethers</path>, you do "
+"not need to restart the <c>rarpd</c> services as the file is checked each "
+"time a request is received."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):118
+msgid "<b>Resolving hostnames</b>: <path>/etc/hosts</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):122
+msgid ""
+"Since each entry in <path>/etc/ethers</path> has a hostname, the netboot "
+"server needs to be able to resolve the hostname into its IP address. This "
+"can be done two ways, <path>/etc/hosts</path> or the nameserver the netboot "
+"server uses."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):128
+msgid ""
+"An <path>/etc/hosts</path> entry for resolving a hostname will look very "
+"similar to the one that probably exists from when you installed Gentoo on "
+"the netboot server. For our example host, sparc-netboot.gentoo.org, we'll "
+"assume that it has an IP address of 10.0.1.15. So the <path>/etc/hosts</"
+"path> entry would look like;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):136
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):136
+#, no-wrap
+msgid ""
+"\n"
+"10.0.1.15  sparc-netboot.gentoo.org\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):141
+msgid ""
+"Depending on the environment, you may need to consult your network "
+"administrator to get an appropriate IP address or addresses to netboot the "
+"host with."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):147
+msgid ""
+"If you use a nameserver, then the DNS server administrator will need to add "
+"a record for the hostname, in our example sparc-netboot.gentoo.org, to point "
+"to the appropriate IP address. Please consult your DNS server administrator "
+"and/or the documentation for the DNS server's DNS software for how to add "
+"the entry."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):154
+msgid ""
+"If both <path>/etc/hosts</path> and the nameserver have an entry for the "
+"host to be netbooted, <path>/etc/hosts</path> will be used first (granted "
+"the order of <path>/etc/nsswitch.conf</path> has not been changed from the "
+"default)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):164
+msgid ""
+"First, we will need to determine the options to use for <c>rarpd</c>. While "
+"there are more options than we'll cover here, these options should get you "
+"started As there is currently no <path>init.d</path> script for <c>rarpd</"
+"c>, an entry will need to be added to <path>/etc/conf.d/local.start</path> "
+"if you want to enable <c>rarpd</c> services at boot time. A sample entry is "
+"as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):172
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):265
+msgid "/etc/conf.d/local.start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):172
+#, no-wrap
+msgid ""
+"\n"
+"/usr/sbin/rarpd -v -e eth0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):176
+msgid ""
+"An explanation of the above <c>rarpd</c> options (as taken from the man "
+"page):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):181
+msgid "<c>-v</c> Be verbose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):182
+msgid ""
+"<c>-e</c> Do not check for the presence of a boot image, reply if MAC "
+"address resolves to a valid IP address using <path>/etc/ethers</path> "
+"database and DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):187
+msgid "eth0 represents the interface <c>rarpd</c> should bind to"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):190
+msgid "For more options, consult <c>man 8 rarpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):197
+msgid "The tftpd Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):200
+msgid ""
+"Here there are three options for a TFTP daemon, <c>net-ftp/atftp</c>, <c>net-"
+"ftp/netkit-tftp</c> and <c>net-ftp/tftp-hpa</c>. You only need to install "
+"one of the TFTP daemons for proper operation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):210
+msgid ""
+"Each TFTP daemon will need a directory from which to serve files to tftp "
+"clients. The directory we will use for this howto will be <path>/tftpboot</"
+"path>. This will appear as the root (<path>/</path>) directory to the "
+"clients when requests are received. Additionally, we'll setup the system to "
+"run the TFTP daemon with the user and group <c>nobody</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):218
+msgid ""
+"If the directory you have chosen does not currently exist, it will need to "
+"be created with the <c>mkdir</c> command. The command for the example <path>/"
+"tftpboot</path> is:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):224
+msgid "Creating /tftpboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):224
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/bin/mkdir /tftpboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):228
+msgid ""
+"Then we will need to change the owner of <path>/tftpboot</path> so that it "
+"is owned by user nobody and group <c>nobody</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):233
+msgid "Changing ownership"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):233
+#, no-wrap
+msgid ""
+"\n"
+"# <i>chown nobody:nobody /tftpboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):240
+msgid "The atftp Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):243
+msgid "First, install the <c>atftp</c> package as follows;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):247
+msgid "Installing atftp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):247
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge atftp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):251
+msgid ""
+"After the <c>atftp</c> package has been installed, it will need to be "
+"configured. If tftpd services are desired at boot time, an entry to <path>/"
+"etc/conf.d/local.start</path> will need to be added as <c>atftp</c> has no "
+"<path>init.d</path>, <c>inetd</c> or <c>xinetd</c> scripts of its own. If "
+"you want to use <c>inetd</c> or <c>xinetd</c> for controlling the tftpd "
+"service, please see their respective man pages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):260
+msgid ""
+"Below is an example entry for <c>atftpd</c> in <path>/etc/conf.d/local."
+"start</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):265
+#, no-wrap
+msgid ""
+"\n"
+"/usr/sbin/in.tftpd -v --daemon /tftpboot\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):269
+msgid "An explanation of the above options (as taken from the man page);"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):274
+msgid ""
+"<c>-v</c> Increase or set the logging level. No args will increase by one "
+"the current value. Default is LOG_NOTICE, see syslog(3) for log level. "
+"Current value range from 0 (LOG_EMERG) to 7 (LOG_DEBUG)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):279
+msgid ""
+"<c>--daemon</c> Run as a daemon. Do not use this option if atftpd is started "
+"by inetd."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):285
+msgid "For more options, consult <c>man 8 atftpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):292
+msgid "The netkit-tftp Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):295
+msgid "First, install the <c>netkit-tftp</c> package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):299
+msgid "Installing netkit-tftp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):299
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge netkit-tftp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):303
+msgid ""
+"Second, install <c>sys-apps/xinetd</c> if it is not currently present. After "
+"the <c>netkit-tftp</c> and <c>sys-apps/xinetd</c> packages have been "
+"installed, <c>netkit-tftp</c> will need to be configured. <c>netkit-tftp</c> "
+"needs to be run from <c>xinetd</c>, however it does not provide example "
+"scripts of its own. A sample <c>xinetd</c> file is provided below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):311
+msgid "Sample /etc/xinetd.d/tftp file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):311
+#, no-wrap
+msgid ""
+"\n"
+"service tftp\n"
+"{\n"
+"    protocol        = udp\n"
+"    port            = 69\n"
+"    socket_type     = dgram\n"
+"    wait            = yes\n"
+"    user            = nobody\n"
+"    group           = nobody\n"
+"    server          = /usr/sbin/in.tftpd\n"
+"    server_args     = /tftpboot\n"
+"    only_from       = 10.0.1.0\n"
+"    disable         = no\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):327
+msgid ""
+"This sample <c>xinetd</c> configuration file for tftp uses the line "
+"<c>disable = no</c>, which enables the service by default. This is opposite "
+"of the default way packages in Gentoo provide their respective <c>xinetd</c> "
+"configuration files, which have <c>disable</c> set to <c>yes</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):334
+msgid "An explanation of the above options which can be changed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):339
+msgid "<b>user</b>: the user in.tftpd requests are handled as"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):340
+msgid "<b>group</b>: the group in.tftpd requests are handled as"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):341
+msgid ""
+"<b>server_args</b>: the root directory for the TFTP daemon to serve files "
+"from"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):345
+msgid ""
+"<b>only_from</b>: tells xinetd which hosts to allow TFTP connections from"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):350
+msgid ""
+"Additional information on <c>xinetd</c> configuration files can be found in "
+"<c>man 5 xinetd.conf</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):355
+msgid ""
+"If <c>xinetd</c> is running, you can send it the HUP signal to have it re-"
+"read its configuration files:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):360
+msgid "Sending HUP signal to xinetd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):360
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/bin/killall -HUP xinetd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):364
+msgid "If <c>xinetd</c> is not running, start it with the init.d command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):368
+msgid "Starting xinetd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):368
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/xinetd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):372
+msgid "For more information, consult <c>man 8 in.tftpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):379
+msgid "The tftp-hpa Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):382
+msgid "First, install the <c>tftp-hpa</c> package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):386
+msgid "Installing tftp-hpa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):386
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge tftp-hpa</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):390
+msgid ""
+"<c>tftp-hpa</c> comes with an <path>init.d</path> and the accompanying "
+"<path>conf.d</path> configuration file. Check to make sure that INTFTPD_PATH "
+"and INTFTP_OPTS in <path>/etc/conf.d/in.tftpd</path> match those below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):396
+msgid "/etc/conf.d/in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):396
+#, no-wrap
+msgid ""
+"\n"
+"INTFTPD_PATH=\"/tftpboot\"\n"
+"INTFTPD_OPTS=\"-s -v -l ${INTFTPD_PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):401
+msgid "The TFTP daemon can then be started via the <path>init.d</path> script:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):405
+msgid "Starting in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):405
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/in.tftpd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):409
+msgid "For more options, consult <c>man 8 tftpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):418
+msgid "Preparing a tftpboot image for use by a client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):422
+msgid ""
+"Make sure you have an image you want to use for netbooting. Please check "
+"your <uri link=\"/main/en/mirrors.xml\">local</uri> Gentoo <uri link="
+"\"http://distfiles.gentoo.org/experimental/sparc/tftpboot/sparc64/"
+"\">distfiles mirror</uri> for the appropriate image. We'll assume you are "
+"planning to boot using the <path>gentoo-sparc64-20100128.tftpboot</path> "
+"image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):430
+msgid "Once you have an image, copy the image into <path>/tftpboot</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):434
+msgid "Copying the image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):434
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp gentoo-sparc64-20100128.tftpboot /tftpboot</i>\n"
+"# <i>chmod 644 /tftpboot/gentoo-sparc64-20100128.tftpboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):439
+msgid ""
+"Now, when the netboot client makes a TFTP request, it looks for a file that "
+"is the hexadecimal number of its current IP address, and on some platforms "
+"an <path>.ARCH</path> suffix. The hexadecimal number should use <e>capital</"
+"e> characters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):446
+msgid ""
+"So for our example IP address, 10.0.1.15, let's look at its hexadecimal "
+"equivalent:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):451
+msgid "Convert to hexadecimal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):451
+#, no-wrap
+msgid ""
+"\n"
+"# <i>printf \"%.2X%.2X%.2X%.2X\\n\" 10 0 1 15</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):455
+msgid "Example IP address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):455
+#, no-wrap
+msgid ""
+"\n"
+"decimal       10  0   1   15\n"
+"hexadecimal   0A  00  01  0F\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):460
+msgid ""
+"So for the example netboot client, it would look for a file named "
+"<path>0A00010F</path> when it tftpboots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):465
+msgid ""
+"Iif you are really, really lazy (like me), you can netboot the host to get "
+"the filename the client is looking for from the netboot server logs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):470
+msgid ""
+"Make sure that both the <c>rarpd</c> and TFTP daemon you've chosen are "
+"currently running, then boot the host as described below in <uri link="
+"\"#netbootingclient\">Netbooting the client</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):476
+msgid ""
+"The client will appear to hang after the boot net command is issued. Then on "
+"the netboot server, check the system logs for an entry for <c>in.tftpd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):481
+msgid ""
+"An example entry from a netboot server running <c>sysklogd</c> and <c>tftp-"
+"hpa</c> looks like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):486
+msgid "Log entry for netboot server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):486
+#, no-wrap
+msgid ""
+"\n"
+"Jan  3 22:48:59 stargazer in.tftpd[8368]: RRQ from 10.0.1.15 filename 0A00010F\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):490
+msgid ""
+"The filename is shown above after \"filename\" in the log entry, which in "
+"this case is <path>0A00010F</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):495
+msgid ""
+"As a way to keep track of what netboot image you are using, and to allow "
+"multiple machines to use the same netboot image, you can use a soft link to "
+"create the file with the hexadecimal value. To create this using our sample "
+"sparc64 host and the <path>gentoo-sparc64-20100128.tftpboot</path>, use the "
+"following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):503
+msgid "Linking the image files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):503
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/bin/ln -s /tftpboot/gentoo-sparc64-20100128.tftpboot \\\n"
+"/tftpboot/0A00010F</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):508
+msgid "Now everything should be set for netbooting!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):517
+msgid "Netbooting the client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):521
+msgid "From OpenBoot PROM (OBP) on the SPARC, enter the command;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):525
+msgid "Booting OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):525
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>boot net</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):529
+msgid "Other methods for certain machines are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):533
+msgid "Booting OBP, alternative"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):533
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>boot net-tpe</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(note):537
+msgid ""
+"If your system doesn't present you with an OBP at boot time, you will either "
+"need to press the Stop and A key, or send a break signal via serial console "
+"before the system boots an OS. If your system cannot find an OS, it should "
+"either try to boot via the network interface (which is what we want), or "
+"leave you at an OBP prompt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):545
+msgid ""
+"This will initiate the networking booting process. A constantly changing "
+"string of hexadecimal digits should appear. When the image has finished "
+"loading, the kernel will take over and start the OS booting process. In the "
+"case of our sparc64 install image, you will be left at a shell prompt from "
+"which you can begin the install process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(title):558
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):566
+msgid ""
+"If the netboot server is a Gentoo Linux system and experiences problems "
+"after installing the rarpd and tftpd packages, please search the <uri link="
+"\"http://forums.gentoo.org\">Gentoo Forums</uri> and <uri link=\"http://bugs."
+"gentoo.org\">Gentoo Bugzilla</uri> to see if this problem has been "
+"encountered by anyone else. If it has not, or the solutions found do not "
+"work, then please open a new bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):579
+msgid ""
+"This is presumably because the file your system is trying to load from the "
+"tftpboot server is not available. On a SPARC system, you would probably see "
+"the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):585
+msgid "Booting appears to hang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):585
+#, no-wrap
+msgid ""
+"\n"
+"Rebooting with command: boot\n"
+"Boot device: net  File and args:\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):590
+msgid ""
+"Double check that the file the client needs does exist in <path>/tftpboot</"
+"path>. You can confirm the filename it is requesting by looking in the "
+"system logs. Also, once this file exists, the client will try to load it. "
+"Sometimes, when the file is missing originally, it will freeze downloading "
+"the file once it appears. To resolve this, just get back to an OBP prompt, "
+"and issue the \"boot net\" command again. The host should then start "
+"downloading the tftpboot image and boot the OS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):605
+msgid "This could be due to a few different problems;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):610
+msgid ""
+"Make sure the entry in <path>/etc/ethers</path> exists for the client in "
+"question. If the MAC address is incorrect and/or the netboot server cannot "
+"resolve the hostname for the client, it cannot respond with the needed "
+"information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):616
+msgid ""
+"Verify that the network hub or switch the netboot server and client are "
+"connected to allow RARP traffic to flow freely. If the client's request "
+"cannot reach the server, or vice versa, the host will be unable to continue."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):622
+msgid ""
+"No one is responding to the RARPD request because no services are listening. "
+"Verify that the rarpd service is up and running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(li):626
+msgid ""
+"The client does not think its NIC has a link to the network hub/switch it is "
+"plugged into. Check to see if the NIC and the port on the network hub or "
+"switch has a link light. If the link light is on, check to see what the "
+"setting of tpe-link-test? is in OBP with the command; <c>printenv tpe-link-"
+"test?</c>. You should receive something like <path>tpe-link-test? false "
+"true</path>. The first column represents the parameter name, the second "
+"column shows the current value for the the parameter, and the third column "
+"shows the default value for the parameter. In the example above, we can see "
+"that the current value is false, which means that the client is not checking "
+"to see if the client and network hub or switch can establish a link before "
+"issuing its RARP request. Often times this can cause the problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):642
+msgid ""
+"To change the value of tpe-link-test? from an OBP prompt, issue the "
+"following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre:caption):647
+msgid "Changing tpe-link-test value"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(pre):647
+#, no-wrap
+msgid ""
+"\n"
+"ok <i>setenv tpe-link-test? true</i>\n"
+"tpe-link-test? =      true\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(p):652
+msgid ""
+"This shows the value of tpe-link-test? is now true. Try netbooting the "
+"client again."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-netboot-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-sparc-obpreference.xml.po b/doc/gettext/ru/gentoo-sparc-obpreference.xml.po
new file mode 100644
index 0000000..389e3b1
--- /dev/null
+++ b/doc/gettext/ru/gentoo-sparc-obpreference.xml.po
@@ -0,0 +1,607 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(guide:link):6
+msgid "/doc/en/gentoo-sparc-obpreference.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):7
+msgid "OpenBoot PROM (OBP) Reference"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(mail:link):10
+msgid "ciaranm@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(mail):10
+msgid "Ciaran McCreesh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(abstract):13
+msgid ""
+"The OpenBoot PROM (OBP) Reference provides a list of useful OBP commands "
+"that can help when booting, configuring and performing diagnostics upon Sun "
+"SPARC hardware and clones."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(version):20
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(date):21
+msgid "2004-08-27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):24
+msgid "About this Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):28
+msgid ""
+"This document provides a list of useful OBP commands that can be helpful "
+"when booting, configuring and performing diagnostics upon Sun SPARC hardware "
+"and clones."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):34
+msgid ""
+"Note that not all commands are available on all PROM versions. In "
+"particular, sun4c systems have a different input mode, and some JavaStation "
+"models are missing a lot of OBP functionality."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):40
+msgid ""
+"OBP is somewhat inconsistent when it comes to command names. Sometimes "
+"hyphens are used to seperate words, sometimes they are not. Some commands "
+"which display information start with or contain a dot (this is a FORTH "
+"convention)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):46
+msgid ""
+"The terms \"OBP\", \"OpenBoot PROM\" and \"PROM\" are used interchangably in "
+"this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):56
+msgid "Entering OBP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):58
+msgid "Systems with Sun Keyboards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):61
+msgid ""
+"On regular Sun systems (and clones which use Sun keyboards), press <c>Stop"
+"+A</c> when the system boots to enter OBP. The <c>Stop</c> key is the top "
+"left key on the extra block of keys on the left hand side of the keyboards "
+"(on really old systems it might be marked <c>L1</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):68
+msgid ""
+"The <c>Stop+N</c> keyboard combination at boot will reset many systems to "
+"the default PROM settings. <c>Stop+D</c> will enable diagnostics on some "
+"boards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):76
+msgid "Over Serial Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):79
+msgid ""
+"To enter OBP over serial console, send a break. In minicom, do this by "
+"pressing <c>ctrl+A F</c>. In xc, use <c>ctrl+A B</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):87
+msgid "Systems with Non-Sun (PC Style) Keyboards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):90
+msgid ""
+"On systems with PC-style keyboards (such as JavaStations and some Ultra "
+"clones), <c>ctrl+break</c> or <c>alt+ctrl+break</c> is generally used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):95
+msgid ""
+"Note that on the JavaStation JK, <c>ctrl+break</c> will restart the box "
+"rather than enter PROM. To get at OBP, you will need to set jumper J1300 "
+"pins 7-8 on the mainboard."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):106
+msgid "Basic System Commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):108
+msgid "Halting and Restarting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):111
+msgid ""
+"The <c>power-off</c> command will halt the box and turn off power. This "
+"command is sometimes screwy on Ultra5/10 systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):116
+msgid ""
+"The <c>reset</c> command will perform a soft reset. If diagnostics are "
+"enabled, they will <e>not</e> be rerun. In some documents, this command is "
+"refered to as <c>reset-all</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):122
+msgid ""
+"The <c>boot</c> command boots the system. A parameter may be provided to "
+"override the default boot device -- this can be a full device name or a "
+"device alias such as <c>disk</c>, <c>cdrom</c> or <c>net</c>. Any additional "
+"arguments are passed to the bootloader or operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):132
+msgid "PROM and System Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):135
+msgid "The <c>.version</c> command will show the OBP version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):139
+msgid ".version output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):139
+#, no-wrap
+msgid ""
+"\n"
+"{0} ok .version\n"
+"Release 3.7 Version 0 created 1997/01/09 13:06\n"
+"OBP 3.7.0 1997/01/09 13:06\n"
+"POST 3.2.1 1996/12/20 03:01\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):146
+msgid "The <c>banner</c> command will show the system information banner."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):150
+msgid "banner output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):150
+#, no-wrap
+msgid ""
+"\n"
+"{0} ok banner\n"
+"Sun Ultra 2 UPA/SBus (2 X UltraSPARC-II 296MHz), No Keyboard\n"
+"OpenBoot 3.7, 704 MB memory installed, Serial #9705521.\n"
+"Ethernet address 8:0:20:94:18:31, Host ID: 80941831\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):157
+msgid "The <c>.speed</c> command will show bus speeds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):161
+msgid ".speed output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):161
+#, no-wrap
+msgid ""
+"\n"
+"{0} ok .speed\n"
+"CPU  Speed : 296.00 MHz\n"
+"UPA  Speed : 098.66 MHz\n"
+"SBus Speed : 025.00 MHz\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):171
+msgid "Device Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):174
+msgid ""
+"The <c>show-devs</c> command will give a list of devices available to the "
+"system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):179
+msgid ""
+"The <c>probe-scsi</c> command will show internal SCSI devices available to "
+"the system. The <c>probe-scsi-all</c> command will show both internal and "
+"external devices on every SCSI interface. After running either of these "
+"commands, you <e>must</e> issue a <c>reset-all</c> before trying to boot an "
+"operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):187
+msgid "probe-scsi-all output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):187
+#, no-wrap
+msgid ""
+"\n"
+"{0} ok probe-scsi-all\n"
+"This command may hang the system if a Stop-A or halt command\n"
+"has been executed.  Please type reset-all to reset the system\n"
+"before executing this command.\n"
+"Do you wish to continue? (y/n) y\n"
+"/sbus@1f,0/SUNW,fas@e,8800000\n"
+"Target 1\n"
+"  Unit 0   Disk     SEAGATE ST34371W SUN4.2G74629710B00491\n"
+"                    Copyright (c) 1997 Seagate\n"
+"                    All rights reserved\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):200
+msgid "The <c>probe-ide</c> command is also available on IDE-based systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):204
+msgid "probe-ide output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):204
+#, no-wrap
+msgid ""
+"\n"
+"ok probe-ide\n"
+"  Device 0  ( Primary Master )\n"
+"          ATA Model: ST320420A\n"
+"\n"
+"  Device 1  ( Primary Slave )\n"
+"          ATA Model: Maxtor 6E040L0\n"
+"\n"
+"  Device 2  ( Secondary Master )\n"
+"         Not Present\n"
+"\n"
+"  Device 3  ( Secondary Slave )\n"
+"         Not Present\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):224
+msgid "Environment Variables and Device Aliases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):226
+msgid "Getting and Setting Environment Variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):229
+msgid ""
+"Use <c>printenv</c> to get a list of environment variables. To see the value "
+"of a specific variable, use <c>printenv fnord</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):234
+msgid "To set a variable, use <c>setenv myvar the new value</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):238
+msgid ""
+"To restore a variable's default value, use <c>set-default blah</c>. To "
+"revert <e>all</e> variables to default, use <c>set-defaults</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):243
+msgid ""
+"Note that boolean variables usually end in a <c>?</c>, and that they are "
+"seperate from variables of the same name without the question mark. The "
+"values <c>true</c> and <c>false</c> are used for booleans."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):252
+msgid "Useful Environment Variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):255
+msgid "Some useful environment variables:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(th):261
+msgid "Variable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(th):262
+msgid "Meaning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):266
+msgid ""
+"Sets the baud rate and related settings used by the serial console. By "
+"default <c>9600,8,n,1,-</c> is used, meaning 9600 baud, 8 bits, no parity, "
+"one stop bit, no flow control."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):274
+msgid ""
+"By default OBP will automatically boot upon startup. Set this to <c>false</"
+"c> if you'd rather send the boot command manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):281
+msgid ""
+"When auto-booting, and when <c>boot</c> is issued with no arguments, this "
+"variable is used to determine the boot device. More than one value can be "
+"provided (space seperated), in which case each is tried in turn. Each value "
+"can be a full device path or a device alias."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):290
+msgid "As <c>boot-device</c>, but used when <c>diag-switch?</c> is enabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):296
+msgid ""
+"If set, network interfaces will use their own MAC rather than the system-"
+"wide MAC. This is consistent with how PCs behave, and in violation of the "
+"Ethernet specification."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(ti):304
+msgid ""
+"If set, additional diagnostic checks will be run at power on. Note that this "
+"can take a <e>very</e> long time on SMP and / or HyperSparc systems. In "
+"addition, the <c>diag-device</c> variable will also be used to determine the "
+"boot device rather than <c>boot-device</c>. Some systems have a mainboard "
+"jumper or a switch on the front of the machine which forces this setting on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):318
+msgid "Getting and Setting Device Aliases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):321
+msgid ""
+"Device aliases can be used to simplify the arguments to many commands. "
+"Instead of typing <c>boot /sbus/SUNW,hme@e,8c00000</c>, for example, one "
+"could use <c>boot net</c>. A number of device aliases are defined by default "
+"on every system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):328
+msgid ""
+"To view all device aliases, use the <c>devalias</c> command. To view a "
+"specific alias, use <c>devalias whatever</c>. To set a device alias, use "
+"<c>devalias whatever newvalue</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):337
+msgid "Changing Monitor Resolutions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):340
+msgid ""
+"The <c>output-device</c> variable can be used to control which framebuffer "
+"is used, and at what resolution it is run, for PROM console. For example, to "
+"use the Creator card on an Ultra 1C or 2 at a resolution of 1024x768@76Hz:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):346
+msgid "Changing Monitor Settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):346
+#, no-wrap
+msgid ""
+"\n"
+"{0} ok devalias screen /SUNW,ffb\n"
+"{0} ok setenv output-device screen:r1024x768x76\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):351
+msgid ""
+"Changes will not take effect until after a reset. Not all resolutions and "
+"refresh are available on all cards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):361
+msgid "Diagnostics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):363
+msgid "Entering Diagnostic Mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):366
+msgid ""
+"Before running any diagnostics, it is best to enable <c>diag-switch?</c> and "
+"do a full power off / on cycle (hard power off). Additional diagnostic "
+"information will be provided over the serial console when the machine boots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):375
+msgid "Basic Tests"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):378
+msgid ""
+"If the power on self test (POST) succeeds, additional tests can be performed "
+"using the <c>test</c>, <c>test-all</c>, <c>watch-net</c> and <c>watch-clock</"
+"c> commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):384
+msgid ""
+"The <c>test somedevice</c> command will perform checks upon the specified "
+"device (this can be a full device path or a device alias)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):389
+msgid "Example Tests"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):389
+#, no-wrap
+msgid ""
+"\n"
+"{0} ok test scsi\n"
+"        CE DMA fill from address fff8e000 for 80 bytes   succeeded.\n"
+"         Dma register test -- succeeded.\n"
+"         Esp register test -- succeeded.\n"
+"         Dma read test -- succeeded.\n"
+"         Dma write test -- succeeded.\n"
+"{0} ok test /sbus/SUNW,hme\n"
+"Internal loopback test -- succeeded.\n"
+"Transceiver check  -- Using Onboard Transceiver - Link Up.\n"
+"passed\n"
+"{0} ok test ttya\n"
+" !\"#$%&amp;'()*+,-./0123456789:;&lt;=&gt;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmn\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):404
+msgid ""
+"The <c>test-all</c> command will perform checks upon every device capable of "
+"self tests."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):409
+msgid ""
+"The <c>watch-net</c> command can be used to watch for broadcast packets "
+"being sent over the network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):414
+msgid ""
+"The <c>watch-clock</c> command can be used to verify that the internal clock "
+"is working. It should count from 0 to 59 in a loop with an interval of one "
+"second."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):423
+msgid "Extended Diagnostics Using obdiag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(note):426
+msgid ""
+"The <c>obdiag</c> routines are only available on the Ultra 5/10 and later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):430
+msgid "To enable extended diagnostics mode, run the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):434
+msgid "Entering obdiag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):434
+#, no-wrap
+msgid ""
+"\n"
+"ok setenv mfg-mode on\n"
+"mfg-mode =            on\n"
+"ok setenv diag-switch? true\n"
+"diag-switch? =        true\n"
+"ok setenv auto-boot? false\n"
+"auto-boot? =          false\n"
+"ok reset-all\n"
+"ok obdiag\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):445
+msgid ""
+"This should display a menu. First, select <c>16</c> to enable verbose "
+"messages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre:caption):450
+msgid "obdiag menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(pre):450
+#, no-wrap
+msgid ""
+"\n"
+"          OBDiag Menu\n"
+"\n"
+"  0 ..... PCI/Cheerio\n"
+"  1 ..... EBUS DMA/TCR Registers\n"
+"  2 ..... Ethernet\n"
+"  3 ..... Keyboard\n"
+"  4 ..... Mouse\n"
+"  5 ..... Floppy\n"
+"  6 ..... Parallel Port\n"
+"  7 ..... Serial Port A\n"
+"  8 ..... Serial Port B\n"
+"  9 ..... NVRAM\n"
+" 10 ..... Audio\n"
+" 11 ..... EIDE\n"
+" 12 ..... Video\n"
+" 13 ..... All Above\n"
+" 14 ..... Quit\n"
+" 15 ..... Display this Menu\n"
+" 16 ..... Toggle script-debug\n"
+" 17 ..... Enable External Loopback Tests\n"
+" 18 ..... Disable External Loopback Tests\n"
+"\n"
+" Enter (0-13 tests, 14 -Quit, 15 -Menu) ===&gt; 16\n"
+" Enter (0-13 tests, 14 -Quit, 15 -Menu) ===&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):477
+msgid ""
+"Individual tests can then be run by selecting the relevant number. Note that "
+"some tests (for example, serial ports) assume that an external loopback "
+"connector is attached. The Ethernet test assumes that a cable is attached "
+"and connected to a switch."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(p):484
+msgid "To exit, use <c>14</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(title):492
+msgid "References"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(li):497
+msgid ""
+"OpenBoot 3.x Quick Reference, Sun P/N 802-3240 (<uri link=\"http://sunsolve."
+"sun.com/data/802/802-3240/pdf/802-3240-10.pdf\">PDF Version)</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(li):502
+msgid ""
+"OpenBoot 3.x Command Reference, Sun P/N 802-3242 (<uri link=\"http://"
+"sunsolve.sun.com/data/802/802-3242/html/TOC.html\">HTML Version)</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(li):507
+msgid ""
+"OpenBoot 3.x Supplement for PCI, Sun P/N 802-7679 (<uri link=\"http://"
+"sunsolve.sun.com/data/802/802-7679/pdf/\">Collection of PDF files)</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(li):512
+msgid ""
+"<uri link=\"http://firmworks.com/QuickRef.html\">Open Firmware Quick "
+"Reference</uri> (Not Sun OBP specific)"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-sparc-obpreference.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-upgrading.xml.po b/doc/gettext/ru/gentoo-upgrading.xml.po
new file mode 100644
index 0000000..cfe3d14
--- /dev/null
+++ b/doc/gettext/ru/gentoo-upgrading.xml.po
@@ -0,0 +1,843 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(guide:link):5
+msgid "/doc/en/gentoo-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):6
+msgid "Gentoo Upgrading Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail:link):9
+msgid "greg_g@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail):9
+msgid "Gregorio Guidi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail:link):12
+msgid "wolf31o2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail):12
+msgid "Chris Gianelloni"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail:link):15
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(mail):15
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(abstract):18
+msgid ""
+"This document explains how new Gentoo releases affect existing installs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(version):26
+msgid "2.11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(date):27
+msgid "2008-07-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):30
+msgid "Gentoo and Upgrades"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):32
+msgid "Philosophy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):35
+msgid ""
+"Here in Gentoo land, the concept of upgrading is quite different compared to "
+"the rest of the Linux world. You probably already know that we never got in "
+"touch with the \"classic\" way of upgrading software: waiting for a new "
+"release, downloading it, burning, putting it in the cdrom drive and then "
+"following the upgrade instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):43
+msgid ""
+"You know (being a Gentoo user after all) that this process is extremely "
+"frustrating for power users that want to live on the bleeding edge. Even "
+"power users from other distributions probably share the same feelings, given "
+"the popularity and spread of tools like apt or apt-rpm which make it "
+"possible to have quick and frequent updates. However, no distribution is "
+"more suited than Gentoo to satisfy these kind of demanding users. From the "
+"beginning, Gentoo was designed around the concept of fast, incremental "
+"updates."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):54
+msgid ""
+"Ideally, you install once and never bother with releases: just follow the "
+"instructions in <uri link=\"/doc/en/handbook/handbook-x86.xml?part=2&amp;"
+"chap=1\">A Portage Introduction</uri> in the <uri link=\"/doc/en/handbook/"
+"\">Gentoo Handbook</uri> that explain how to keep your system up to date. "
+"While that's the way things usually go, sometimes changes are made to the "
+"core system which require updates to be done manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):67
+msgid "Releases and Profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):70
+msgid ""
+"A recurring question about the Gentoo release process is: \"Why roll out new "
+"releases frequently, if they are not intended to let users update software?"
+"\" There are various reasons:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(li):77
+msgid ""
+"A new release means new Installation CDs with bugfixes and more features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(li):80
+msgid ""
+"A new release provides an updated set of GRP packages, so that users that "
+"choose \"the fast way\" to install (stage3 + precompiled packages) end up "
+"with a system that is not outdated"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(li):85
+msgid ""
+"Finally, a new release may, from time to time, implement some features that "
+"are incompatible with previous releases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):91
+msgid ""
+"When a release includes new incompatible features, or provides a set of core "
+"packages and settings that deeply modify the behavior of the system, we say "
+"that it provides a new <e>profile</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):97
+msgid ""
+"A <e>profile</e> is a set of configuration files, stored in a subdirectory "
+"of <path>/usr/portage/profiles</path>, that describe things such as the "
+"ebuilds that are considered <e>system</e> packages, the default USE flags, "
+"the default mapping for virtual packages, and the architecture on which the "
+"system is running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):104
+msgid ""
+"The profile in use is determined by the symbolic link <path>/etc/make."
+"profile</path>, which points to a subdirectory of <path>/usr/portage/"
+"profiles</path> which holds the profile files. For instance, the default x86 "
+"2008.0 profile can be found at <path>/usr/portage/profiles/default/linux/"
+"x86/2008.0</path>. The files in the parent directories are part of the "
+"profile as well (and are therefore shared by different subprofiles). This is "
+"why we call these <e>cascaded profiles</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):115
+msgid ""
+"Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</"
+"path> along with the current ones, but they are marked as deprecated. When "
+"that happens a file named <path>deprecated</path> is put in the profile "
+"directory. The content of this file is the name of the profile that should "
+"be \"upgraded to\"; Portage uses this information to automatically warn you "
+"when you should update to a new profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):124
+msgid ""
+"There are various reasons that a new profile may be created: the release of "
+"new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or "
+"<c>glibc</c>) that are incompatible with previous versions, a change in the "
+"default USE flags or in the virtual mappings, or maybe a change in system-"
+"wide settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):137
+msgid "Keeping up with new releases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):139
+msgid "Releases without profile changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):142
+msgid ""
+"If a new Gentoo release does not include a new profile then you can safely "
+"pretend that it never happened. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):147
+msgid ""
+"If you update your installed packages <uri link=\"/doc/en/handbook/handbook-"
+"x86.xml?part=2&amp;chap=1\">as explained in the Gentoo Handbook</uri>, then "
+"your system will be exactly the same as one that has been installed using "
+"the new release."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):157
+msgid "Releases with profile changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):160
+msgid ""
+"If a release (such as 2008.0 for x86) introduces a new profile, you have the "
+"choice to migrate to the new profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):165
+msgid ""
+"Naturally, you are not forced to do so, and you can continue to use the old "
+"profile and just update your packages <uri link=\"/doc/en/handbook/handbook-"
+"x86.xml?part=2&amp;chap=1\">as explained in the Gentoo Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):172
+msgid ""
+"However, Gentoo strongly recommends updating your profile if it becomes "
+"deprecated. When this happens, it means that Gentoo developers no longer "
+"plan on supporting it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):178
+msgid ""
+"If you decide to migrate to the new profile, then you will have to manually "
+"perform the update. The way you update may vary significantly from release "
+"to release; it depends on how deep the modifications introduced in the new "
+"profile are."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):185
+msgid ""
+"In the simplest case you only have to change the <path>/etc/make.profile</"
+"path> symlink, in the worst case you may have to recompile your system from "
+"scratch while doing a neat voodoo dance. Migration is usually covered in the "
+"release notes. You can also find <uri link=\"#instructions\">instructions</"
+"uri> at the end of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):196
+msgid "Supported profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):199
+msgid ""
+"You can view the list of profiles on your architecture officially supported "
+"by Gentoo developers when you <c>emerge eselect</c> and then run the "
+"following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):205
+msgid "Viewing supported profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):205
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect profile list</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):214
+msgid "Profile updating instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):216
+msgid "General instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(impo):219
+msgid ""
+"Make sure your Portage is updated before performing any profile changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):223
+msgid ""
+"First, run <c>emerge eselect</c>. The <c>eselect</c> utility will let you "
+"view and select profiles easily, without needing to create or remove "
+"symlinks by hand."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):229
+msgid "Profile selection with eselect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):229
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(View available profiles)</comment>\n"
+"# <i>eselect profile list</i>\n"
+"\n"
+"<comment>(Select the number of your desired profile from the list)</comment>\n"
+"# <i>eselect profile set &lt;number&gt;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):237
+msgid ""
+"If you'd still prefer to change profiles manually, then simply do the "
+"following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):241
+msgid "Changing profiles manually"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):241
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):315
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):365
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):526
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm /etc/make.profile</i>\n"
+"# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(note):246
+msgid ""
+"There are <b>desktop</b> and <b>server</b> subprofiles for most "
+"architectures. Examine these profiles carefully, as they may serve your "
+"needs better than the extremely minimal default profiles."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(note):252
+msgid ""
+"The <c>developer</c> subprofile is specifically for Gentoo Linux development "
+"tasks. It is <e>not</e> meant to help set up general development "
+"environments."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):260
+msgid "Updating to 2008.0, 2007.0, or 2006.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):263
+msgid ""
+"If you intend to upgrade to these profiles, you should be aware that they "
+"expect the system to be set to a Unicode locale by default; specifically "
+"that UNICODE=\"yes\" is set in <path>/etc/rc.conf</path>. For this to work, "
+"you must have created a Unicode locale for your system to use. Please read "
+"our <uri link=\"/doc/en/utf-8.xml\">UTF-8 guide</uri> to learn how to create "
+"the proper locale."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):272
+msgid ""
+"Alternatively, if you do not wish to set a locale, you should specify "
+"UNICODE=\"no\" in <path>/etc/rc.conf</path>, and re-emerge <c>baselayout</c> "
+"(or wait until your next <c>baselayout</c> update) with the <c>-unicode</c> "
+"USE flag. You can set <c>-unicode</c> just for <c>baselayout</c>, or you can "
+"set it globally for all packages by adding it to your USE variable in <path>/"
+"etc/make.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):281
+msgid "Optional: removing Unicode support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):281
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(To remove Unicode support just for baselayout)</comment>\n"
+"# <i>echo \"sys-apps/baselayout -unicode\" &gt;&gt; /etc/portage/package.use</i>\n"
+"# <i>emerge -a baselayout</i>\n"
+"\n"
+"<comment>(To remove Unicode support from your whole system)</comment>\n"
+"# <i>nano -w /etc/make.conf</i>\n"
+"USE=\"-unicode\"\n"
+"# <i>emerge -a baselayout</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(note):292
+msgid ""
+"If you are updating to a 2007.0 profile on the Sparc architecture, then you "
+"will need to follow the <uri link=\"/doc/en/gcc-upgrading.xml\">GCC "
+"Upgrading Guide</uri>, as <c>gcc-4</c> is the default compiler."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):298
+msgid ""
+"Finally, follow the <uri link=\"#general\">general instructions</uri> for "
+"updating your profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):306
+msgid "Updating to 2006.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):309
+msgid ""
+"To switch to the 2006.0 profile, point the <path>/etc/make.profile</path> "
+"symlink to the new location. Make sure your Portage is updated before you "
+"change your profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):315
+msgid "Changing to a 2006.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):320
+msgid ""
+"<b>alpha</b> - Users that use a 2.4 kernel or don't want to use NPTL should "
+"use the default-linux/alpha/no-nptl profile. More information is available "
+"in <uri link=\"/proj/en/releng/release/2006.0/alpha-release-notes.xml\">the "
+"alpha release notes</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):327
+msgid ""
+"<b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The "
+"ppc32 profile has been changed in a way that offers a minimalistic generic "
+"profile for all purposes, located in default-linux/ppc/ppc32. The release-"
+"dependent profile is optimized for desktop-usage and located in default-"
+"linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and G4 "
+"processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop "
+"Workstation. Make sure you choose the correct subprofile for your system "
+"when migrating to a 2006.0 profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):338
+msgid ""
+"<b>sparc</b> - Upgrading to the <b>2.4</b>-kernel based 2006.0/2.4 profile "
+"requires manual user intervention (unmerging java stuff) and an <c>emerge -e "
+"world</c> because of the <uri link=\"/doc/en/gcc-upgrading.xml\">gcc "
+"upgrade</uri>.<br/> Upgrading to the <b>2.6</b>-kernel based 2006.0 profile "
+"which is not considered stable also requires an entry in <path>/etc/portage/"
+"package.unmask</path> to umask a 2.6 version of <c>gentoo-sources</c> and a "
+"full rebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):348
+msgid ""
+"<b>All other archs</b> - There are no fundamental changes in this profile. "
+"No specific action needs to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):356
+msgid "Updating to 2005.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):359
+msgid ""
+"To switch to the 2005.1 profile, point the <path>/etc/make.profile</path> "
+"symlink to the new location. Make sure your Portage is updated before you "
+"change your profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):365
+msgid "Changing to a 2005.1 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):370
+msgid ""
+"<b>All archs</b> - There are no fundamental changes in this profile. No "
+"specific action needs to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):375
+msgid ""
+"<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged "
+"and a number of subprofiles for specific subarchitectures were created. Make "
+"sure you choose the correct subprofile for your system when migrating to a "
+"2005.1 profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):385
+msgid "Updating to 2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):388
+msgid ""
+"With the introduction of 2005.0, several architectures have decided to "
+"define additional profiles. Make sure you read the description of said "
+"profiles before you decide to migrate to one of them. Most architectures now "
+"also default to the 2.6 kernel tree where 2.4 was chosen previously."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):395
+msgid ""
+"Some architectures require a bit more actions to be completed in order to "
+"convert from one profile to another. If that is the case, the step-by-step "
+"guides are linked from the table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(th):403
+msgid "Profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(th):404
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(th):405
+msgid "Specific Upgrade Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):408
+msgid "default-linux/alpha/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):409
+msgid "Default Alpha 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):413
+msgid "default-linux/alpha/2005.0/2.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):414
+msgid "Alpha 2005.0 profile for 2.4 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):418
+msgid "default-linux/amd64/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):419
+msgid "Default AMD64 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):423
+msgid "default-linux/amd64/2005.0/no-multilib"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):424
+msgid "AMD64 2005.0 profile for multilib-disabled system installations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):428
+msgid "default-linux/arm/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):429
+msgid "Default ARM 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):433
+msgid "default-linux/hppa/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):434
+msgid "Default HPPA 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):438
+msgid "default-linux/hppa/2005.0/2.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):439
+msgid "HPPA 2005.0 profile for 2.4 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):443
+msgid "default-linux/mips/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):444
+msgid "Default MIPS 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):448
+msgid "default-linux/mips/cobalt/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):449
+msgid "Cobalt specific MIPS 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):453
+msgid "default-linux/mips/mips64/n32/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):454
+msgid "2005.0 profile for n32-supporting MIPS platforms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):458
+msgid "default-linux/mips/mips64/ip28/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):459
+msgid "Indigo2 Impact specific 64-bit 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):463
+msgid "default-linux/mips/mips64/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):464
+msgid "64-bit MIPS 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):468
+msgid "default-linux/ppc/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):469
+msgid "Default PPC 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):473
+msgid "default-linux/ppc64/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):474
+msgid "Default PPC64 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):478
+msgid "default-linux/s390/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):479
+msgid "Default S390 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):483
+msgid "default-linux/sparc/sparc32/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):484
+msgid "Default Sparc 32-bit 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):496
+msgid "default-linux/sparc/sparc64/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):497
+msgid "Default Sparc 64-bit 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):509
+msgid "default-linux/x86/2005.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):510
+msgid "Default x86 2005.0 profile for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):514
+msgid "default-linux/x86/2005.0/2.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(ti):515
+msgid "x86 2005.0 profile for 2.4 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):520
+msgid ""
+"To switch to the selected profile, point the <path>/etc/make.profile</path> "
+"symlink to the new location. Make sure your Portage is updated before you "
+"change your profile!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):526
+msgid "Changing to a 2005.0 profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):531
+msgid ""
+"If you are running a Linux 2.4-based system but want to migrate to a 2.6-"
+"based kernel, make sure you read our <uri link=\"/doc/en/migration-to-2.6.xml"
+"\">Gentoo Linux 2.6 Migration Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):540
+msgid "Updating to 2004.3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):543
+msgid ""
+"With the introduction of the 2004.3 profiles, users are not going to see "
+"huge modifications of their systems (see below for details). However, Gentoo "
+"developers decided to push out this new profile and to deprecate quite a few "
+"of the old ones to speed up the adoption of <e>stacked profiles</e>, that "
+"is, the profiles that follow the new layout of the <path>/usr/portage/"
+"profiles</path> directory, for instance <path>/usr/portage/profiles/default-"
+"linux/x86/2004.3</path> (supported by Portage 2.0.51 or later)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):554
+msgid ""
+"To switch to the 2004.3 profile, point the <path>/etc/make.profile</path> "
+"symlink to the new location:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(warn):559
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(warn):624
+msgid ""
+"Don't forget to upgrade Portage <e>before</e> you change your profile!!!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):563
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):628
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):659
+msgid "Updating the /etc/make.profile symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):563
+#, no-wrap
+msgid ""
+"\n"
+"<comment>substitute &lt;arch&gt; with your arch</comment>\n"
+"# <i>rm /etc/make.profile</i>\n"
+"# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):569
+msgid ""
+"<b>All archs</b> - As said above, there are no big changes introduced in "
+"this profile. However, it should be noted that <c>sys-apps/slocate</c> and "
+"<c>net-misc/dhcpcd</c> are no longer considered system packages. This means "
+"that if you run <c>emerge --depclean</c>, Portage will try to remove them "
+"from your system. If you need any of those packages, add them to <path>/var/"
+"lib/portage/world</path> after the profile switch, or manually emerge them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):579
+msgid ""
+"<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/"
+"devfs</c> for newly installed machines. This has no effect on already "
+"installed machines, though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):588
+msgid "Updating Portage to Support Cascading Profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):591
+msgid ""
+"Although this section does not seem to integrate well in this upgrading "
+"guide, it is quite important. Any profile listed above this section requires "
+"a Portage version that supports cascading profiles. However, some obsoleted "
+"profiles don't allow the user to upgrade Portage or the user is using a "
+"profile that isn't available anymore - any attempt to upgrade Portage will "
+"result in a failure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):599
+msgid ""
+"To work around this problem, users can set a temporary symbolic link to the "
+"<e>obsolete</e> profile, allowing them to upgrade their Portage after which "
+"they can continue with the upgrade procedure set forth in this guide. Please "
+"substitute <c>&lt;arch&gt;</c> with your respective architecture:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre:caption):606
+msgid "Updating Portage through the obsolete profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):606
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm /etc/make.profile</i>\n"
+"# <i>cd /etc</i>\n"
+"# <i>ln -sf ../usr/portage/profiles/obsolete/&lt;arch&gt; make.profile</i>\n"
+"# <i>emerge -n '&gt;=sys-apps/portage-2.0.51'</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):616
+msgid "Updating to 2004.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):619
+msgid ""
+"To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> "
+"symlink to the new location:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):628
+#, no-wrap
+msgid ""
+"\n"
+"<comment>substitute &lt;arch&gt; with your arch</comment>\n"
+"# <i>rm /etc/make.profile</i>\n"
+"# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):634
+msgid ""
+"<b>x86</b> - This profile changes the default X11 implementation from <c>x11-"
+"base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches the "
+"<e>default</e> value, and is only relevant for those who have not installed "
+"an X server yet. If you already have one installed, then it will not affect "
+"you at all; you are free to switch from one X server to the other exactly as "
+"before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):643
+msgid ""
+"<b>amd64</b> - There are no fundamental changes from previous profiles, no "
+"specific action needs to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):651
+msgid "Updating to 2004.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):654
+msgid ""
+"To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> "
+"symlink to the new location:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(pre):659
+#, no-wrap
+msgid ""
+"\n"
+"<comment>substitute &lt;arch&gt; with your arch</comment>\n"
+"# <i>rm /etc/make.profile</i>\n"
+"# <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):665
+msgid ""
+"<b>All archs</b> - There are no fundamental changes from previous profiles, "
+"no specific action needs to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(title):673
+msgid "Updating from profiles older than 1.4 to 1.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(p):676
+msgid ""
+"The instructions for this upgrade are quite complex, you can find them <uri "
+"link=\"/doc/en/new-upgrade-to-gentoo-1.4.xml\">here</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-upgrading.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-x86+raid+lvm2-quickinstall.xml.po b/doc/gettext/ru/gentoo-x86+raid+lvm2-quickinstall.xml.po
new file mode 100644
index 0000000..31bc6ea
--- /dev/null
+++ b/doc/gettext/ru/gentoo-x86+raid+lvm2-quickinstall.xml.po
@@ -0,0 +1,562 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):6
+msgid "Gentoo Linux x86 with Software Raid and LVM2 Quick Install Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(key):9
+msgid "yes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(key):10
+msgid "/dev/md3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(author:title):13
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(author:title):16
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(author:title):19
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(mail:link):14
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(mail:link):17
+msgid "swift"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(author):19
+msgid "Steven Wagner"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(abstract):21
+msgid ""
+"The Quick Install guide covers the Gentoo install process in a non-verbose "
+"manner. Its purpose is to allow users to perform a stage3 install with "
+"software RAID and LVM2 in no time. Users should already have prior "
+"experience with installing Gentoo Linux if they want to follow this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(version):32
+msgid "16"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(date):33
+msgid "2010-06-15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):36
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):40
+msgid ""
+"This guide contains all commands you should use to complete a stage3 "
+"installation including LVM2 on top of software RAID. This guide is targeted "
+"at experienced users. You need a connection to the Internet to download the "
+"stage3 and Portage snapshots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(impo):47
+msgid ""
+"New users should read the <uri link=\"/doc/en/handbook/index.xml\">Handbook</"
+"uri> as it gives a better overview about the installation process. The Quick "
+"Install guide is designed for experienced users who just need a checklist to "
+"follow."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):53
+msgid ""
+"Timing output follows all commands that take more than a couple of seconds "
+"to finish. Commands were timed on an AMD 2000 1.66 Ghz PC with 512 Mb of RAM "
+"and two SATA disks connected to a hardware controller configured as JBOD (i."
+"e. two separate hard disks are seen by Gentoo). If you have a \"hardware\" "
+"RAID controller on your motherboard, it is most likely <b>not</b> a hardware "
+"controller."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):62
+msgid "Test box specs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):62
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(The following specs and the timing information should help you determine\n"
+"a rough estimate of the time you need to complete your install)</comment>\n"
+"\n"
+"# <i>grep bogo /proc/cpuinfo</i>\n"
+"bogomips       : 3337.81\n"
+"\n"
+"# <i>hdparm -tT /dev/sda /dev/sdb</i>\n"
+"/dev/sda:\n"
+"reads:   1048 MB in  2.00 seconds = 524.00 MB/sec\n"
+" Timing buffered disk reads:  152 MB in  3.01 seconds =  50.50 MB/sec\n"
+"\n"
+"/dev/sdb:\n"
+" Timing cached reads:   1048 MB in  2.00 seconds = 524.00 MB/sec\n"
+" Timing buffered disk reads:  152 MB in  3.01 seconds =  50.50 MB/sec\n"
+"\n"
+"# <i>grep MemTotal /proc/meminfo</i>\n"
+"MemTotal:       509248 kB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):87
+msgid "Quick Install Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):92
+msgid "Preparing the Disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):95
+msgid "Load the software RAID and LVM2 modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):99
+msgid "Load RAID and LVM2 modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):99
+#, no-wrap
+msgid ""
+"\n"
+"livecd ~ # <i>modprobe raid0</i>\n"
+"livecd ~ # <i>modprobe raid1</i>\n"
+"<comment>(raid5, raid6 and raid10 are also available)</comment>\n"
+"\n"
+"livecd ~ # <i>modprobe dm-mod</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):107
+msgid ""
+"Use <c>fdisk</c> or <c>cfdisk</c> to create your partition layout. The "
+"device names are likely to be either <path>/dev/sda</path> and <path>/dev/"
+"sdb</path> for a SATA or SCSI disks, or <path>/dev/hda</path> and <path>/dev/"
+"hdb</path> for IDE disks. The following layout will be used in this guide:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):119
+msgid "Type"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):125
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):137
+msgid "Raid-1 (mirroring)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):129
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):130
+msgid "swap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):131
+msgid "Normal partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):141
+msgid "LVM2 volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):142
+msgid "Raid-0 (striped)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(impo):146
+msgid ""
+"The partition you boot from must not be striped. It may not be raid-5 or "
+"raid-0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(note):151
+msgid ""
+"On the one hand, if you want extra stability, consider using raid-1 (or even "
+"raid-5) for your swap partition(s) so that a drive failure would not corrupt "
+"your swap space and crash applications that are using it. On the other hand, "
+"if you want extra performance, just let the kernel use distinct swap "
+"partitions as it does striping by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):159
+msgid "Create the partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):159
+#, no-wrap
+msgid ""
+"\n"
+"livecd ~ # <i>fdisk /dev/sda</i>\n"
+"<comment>(Make sure you use type fd and set the bootable flag)</comment>\n"
+"\n"
+"<comment>(The rest of this guide uses the following partitioning scheme)</comment>\n"
+"livecd ~ # <i>fdisk -l /dev/sda</i>\n"
+"\n"
+"Disk /dev/sda: 299.9 GB, 299989204992 bytes\n"
+"255 heads, 63 sectors/track, 36471 cylinders\n"
+"Units = cylinders of 16065 * 512 = 8225280 bytes\n"
+"\n"
+"   Device Boot      Start         End      Blocks   Id  System\n"
+"/dev/sda1   *           1          11       88326   fd  Linux raid autodetect\n"
+"/dev/sda2              12          61      401625   82  Linux swap / Solaris\n"
+"/dev/sda3              62         311     2008125   fd  Linux raid autodetect\n"
+"/dev/sda4             312       36471   290455200   fd  Linux raid autodetect\n"
+"\n"
+"<comment>(Partition the second disk exactly as the first)</comment>\n"
+"livecd ~ # <i>fdisk /dev/sdb</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):180
+msgid ""
+"Then create the RAID device nodes and devices. Please bear in mind that the "
+"<c>/boot</c> and <c>/</c> mount points should use an older metadata format "
+"which can be specified by the <c>--metadata=0.90</c> flag:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):186
+msgid "Create device nodes and devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):186
+#, no-wrap
+msgid ""
+"\n"
+"livecd ~ # <i>mknod /dev/md1 b 9 1</i>\n"
+"livecd ~ # <i>mknod /dev/md3 b 9 3</i>\n"
+"livecd ~ # <i>mknod /dev/md4 b 9 4</i>\n"
+"\n"
+"livecd ~ # <i>mdadm --create /dev/md1 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 /dev/sdb1</i>\n"
+"mdadm: array /dev/md1 started.\n"
+"livecd ~ # <i>mdadm --create /dev/md3 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3</i>\n"
+"mdadm: array /dev/md3 started.\n"
+"livecd ~ # <i>mdadm --create /dev/md4 --level=0 --raid-devices=2 /dev/sda4 /dev/sdb4</i>\n"
+"mdadm: array /dev/md4 started.\n"
+"\n"
+"<comment>(Wait until all units are ready)</comment>\n"
+"livecd ~ # <i>cat /proc/mdstat</i>\n"
+"Personalities : [raid0] [raid1]\n"
+"md4 : active raid0 sdb4[1] sda4[0]\n"
+"581006592 blocks 64k chunks\n"
+"\n"
+"md3 : active raid1 sdb3[1] sda3[0]\n"
+"1959808 blocks [2/2] [UU]\n"
+"\n"
+"md1 : active raid1 sdb1[1] sda1[0]\n"
+"88256 blocks [2/2] [UU]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):211
+msgid ""
+"Then create the LVM2 volumes in <path>/dev/md4</path>. The following scheme "
+"is used as an <b>example</b>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):218
+msgid "Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):219
+msgid "Size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(th):220
+msgid "File system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):223
+msgid "/usr"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):224
+msgid "8 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):225
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):240
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):245
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):250
+msgid "ext3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):228
+msgid "/usr/portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):229
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):259
+msgid "2 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):230
+msgid "ext2, small block size, many inodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):233
+msgid "/usr/portage/distfiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):234
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):244
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):249
+msgid "4 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):235
+msgid "ext2, large block size, less inodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):238
+msgid "/home"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):239
+msgid "10 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):243
+msgid "/opt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):248
+msgid "/var"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):253
+msgid "/var/tmp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):254
+msgid "6 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):255
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):260
+msgid "ext2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(ti):258
+msgid "/tmp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):264
+msgid "Create LVM2 volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):264
+#, no-wrap
+msgid ""
+"\n"
+"livecd ~ # <i>vgscan</i>\n"
+"  Reading all physical volumes.  This may take a while...\n"
+"  No volume groups found\n"
+"livecd ~ # <i>vgchange -a y</i>\n"
+"  No volume groups found\n"
+"\n"
+"<comment>(Create physical volumes, we have only one in our example)</comment>\n"
+"livecd ~ # <i>pvcreate /dev/md4</i>\n"
+"  Physical volume \"/dev/md4\" successfully created\n"
+"\n"
+"<comment>(Create volume groups, again, we have only one in our example)</comment>\n"
+"livecd ~ # <i>vgcreate vg /dev/md4</i>\n"
+"  Volume group \"vg\" successfully created\n"
+"\n"
+"<comment>(Create logical volumes)</comment>\n"
+"livecd ~ # <i>lvcreate -L8G -nusr vg</i>\n"
+"  /dev/cdrom: open failed: Read-only file system\n"
+"  Logical volume \"usr\" created <comment>(Further similar messages not displayed)</comment>\n"
+"livecd ~ # <i>lvcreate -L2G -nportage vg</i>\n"
+"livecd ~ # <i>lvcreate -L4G -ndistfiles vg</i>\n"
+"livecd ~ # <i>lvcreate -L10G -nhome vg</i>\n"
+"livecd ~ # <i>lvcreate -L4G -nopt vg</i>\n"
+"livecd ~ # <i>lvcreate -L4G -nvar vg</i>\n"
+"livecd ~ # <i>lvcreate -L6G -nvartmp vg</i>\n"
+"livecd ~ # <i>lvcreate -L2G -ntmp vg</i>\n"
+"\n"
+"<comment>(Display volume groups and logical volumes)</comment>\n"
+"livecd ~ # <i>vgs</i>\n"
+"  VG   #PV #LV #SN Attr  VSize   VFree\n"
+"  vg     1   8   0 wz--n 554.09G 514.09G\n"
+"livecd ~ # <i>lvs</i>\n"
+"  LV        VG   Attr   LSize  Origin Snap%  Move Copy%\n"
+"  distfiles vg   -wi-a-  4.00G\n"
+"  home      vg   -wi-a- 10.00G\n"
+"  opt       vg   -wi-a-  4.00G\n"
+"  portage   vg   -wi-a-  2.00G\n"
+"  tmp       vg   -wi-a-  2.00G\n"
+"  usr       vg   -wi-a-  8.00G\n"
+"  var       vg   -wi-a-  4.00G\n"
+"  vartmp    vg   -wi-a-  6.00G\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):307
+msgid ""
+"Use <c>mke2fs</c>, <c>mke2fs -j</c>, <c>mkreiserfs</c>, <c>mkfs.xfs</c> and "
+"<c>mkfs.jfs</c> to create file systems. Initialize swap using <c>mkswap</c> "
+"and <c>swapon</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):313
+msgid "Create the file systems and activate swap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):313
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(ext2 is all you need on the /boot partition)</comment>\n"
+"livecd ~ # <i>mke2fs /dev/md1</i>\n"
+"\n"
+"<comment>(Let's use ext3 on the root partition)</comment>\n"
+"livecd ~ # <i>mke2fs -j /dev/md3</i>\n"
+"\n"
+"<comment>(Create file systems on logical volumes)</comment>\n"
+"livecd ~ # <i>mke2fs -b 4096 -T largefile /dev/vg/distfiles</i>\n"
+"livecd ~ # <i>mke2fs -j /dev/vg/home</i>\n"
+"livecd ~ # <i>mke2fs -j /dev/vg/opt</i>\n"
+"livecd ~ # <i>mke2fs -b 1024 -N 200000 /dev/vg/portage</i>\n"
+"livecd ~ # <i>mke2fs /dev/vg/tmp</i>\n"
+"livecd ~ # <i>mke2fs -j /dev/vg/usr</i>\n"
+"livecd ~ # <i>mke2fs -j /dev/vg/var</i>\n"
+"livecd ~ # <i>mke2fs /dev/vg/vartmp</i>\n"
+"\n"
+"<comment>(Create and activate swap)</comment>\n"
+"livecd ~ # <i>mkswap /dev/sda2 &amp;&amp; mkswap /dev/sdb2</i>\n"
+"livecd ~ # <i>swapon -p 1 /dev/sda2 &amp;&amp; swapon -p 1 /dev/sdb2</i>\n"
+"<comment>(Check that all swap partitions use the same priority)</comment>\n"
+"livecd ~ # <i>swapon -v -s</i>\n"
+"Filename                   Type            Size    Used    Priority\n"
+"/dev/sda2                  partition       401616  0       1\n"
+"/dev/sdb2                  partition       401616  0       1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):340
+msgid ""
+"Mount the freshly created file systems on <path>/mnt/gentoo</path>. Create "
+"directories for the other mount points and mount them too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):345
+msgid "Mount the file systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):345
+#, no-wrap
+msgid ""
+"\n"
+"livecd ~ # <i>mount /dev/md3 /mnt/gentoo</i>\n"
+"livecd ~ # <i>cd /mnt/gentoo</i>\n"
+"livecd gentoo # <i>mkdir boot home usr opt var tmp</i>\n"
+"livecd gentoo # <i>mount /dev/md1 /mnt/gentoo/boot</i>\n"
+"livecd gentoo # <i>mount /dev/vg/usr /mnt/gentoo/usr</i>\n"
+"livecd gentoo # <i>mount /dev/vg/home /mnt/gentoo/home</i>\n"
+"livecd gentoo # <i>mount /dev/vg/opt /mnt/gentoo/opt</i>\n"
+"livecd gentoo # <i>mount /dev/vg/tmp /mnt/gentoo/tmp</i>\n"
+"livecd gentoo # <i>mount /dev/vg/var /mnt/gentoo/var</i>\n"
+"livecd gentoo # <i>mkdir usr/portage var/tmp</i>\n"
+"livecd gentoo # <i>mount /dev/vg/vartmp /mnt/gentoo/var/tmp</i>\n"
+"livecd gentoo # <i>mount /dev/vg/portage /mnt/gentoo/usr/portage</i>\n"
+"livecd gentoo # <i>mkdir usr/portage/distfiles</i>\n"
+"livecd gentoo # <i>mount /dev/vg/distfiles /mnt/gentoo/usr/portage/distfiles</i>\n"
+"\n"
+"<comment>(Set proper perms on tmp directories)</comment>\n"
+"livecd gentoo # <i>chmod 1777 /mnt/gentoo/tmp /mnt/gentoo/var/tmp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):373
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):376
+msgid ""
+"Install a kernel source (usually <c>gentoo-sources</c>), configure it, "
+"compile it and copy the <path>arch/i386/boot/bzImage</path> file to <path>/"
+"boot</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):381
+msgid "Install a kernel source, compile it and install the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):381
+#, no-wrap
+msgid ""
+"\n"
+"livecd etc # <i>time emerge gentoo-sources</i>\n"
+"\n"
+"real  3m3.110s\n"
+"user  1m2.320s\n"
+"sys   0m34.990s\n"
+"livecd etc # <i>cd /usr/src/linux</i>\n"
+"livecd linux # <i>make menuconfig</i>\n"
+"\n"
+"<comment>(Configure your kernel as usual and make sure the raid and lvm modules you need are\n"
+"compiled in, i.e. <b>not</b> as modules. The same applies to the disk drivers and filesystems.)</comment>\n"
+"Multi-device support (RAID and LVM)  ---&gt;\n"
+"[*] Multiple devices driver support (RAID and LVM)\n"
+"  &lt;*&gt;   RAID support\n"
+"  &lt; &gt;     Linear (append) mode (NEW)\n"
+"  &lt;*&gt;     RAID-0 (striping) mode\n"
+"  &lt;*&gt;     RAID-1 (mirroring) mode\n"
+"  &lt; &gt;     RAID-10 (mirrored striping) mode (EXPERIMENTAL) (NEW)\n"
+"  &lt; &gt;     RAID-4/RAID-5 mode (NEW)\n"
+"  &lt; &gt;     RAID-6 mode (NEW)\n"
+"  &lt; &gt;     Multipath I/O support (NEW)\n"
+"  &lt; &gt;     Faulty test module for MD (NEW)\n"
+"  &lt;*&gt;   Device mapper support\n"
+"  &lt; &gt;     Crypt target support (NEW)\n"
+"  &lt; &gt;     Snapshot target (EXPERIMENTAL) (NEW)\n"
+"  &lt; &gt;     Mirror target (EXPERIMENTAL) (NEW)\n"
+"  &lt; &gt;     Zero target (EXPERIMENTAL) (NEW)\n"
+"  &lt; &gt;     Multipath target (EXPERIMENTAL) (NEW)\n"
+"  &lt; &gt;     Bad Block Relocation Device Target (EXPERIMENTAL) (NEW)\n"
+"\n"
+"livecd linux # <i>time make -j2</i>\n"
+"\n"
+"<comment>(Elapsed time depends highly on the options you selected)</comment>\n"
+"real  5m5.869s\n"
+"user  4m32.320s\n"
+"sys   0m32.930s\n"
+"\n"
+"livecd linux # <i>make modules_install</i>\n"
+"livecd linux # <i>cp arch/i386/boot/bzImage /boot/kernel</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(title):430
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre:caption):437
+msgid "Reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(p):433
+msgid "Exit the chrooted environment, unmount all file systems and reboot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(pre):437
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>exit</i>\n"
+"livecd / # <i>umount /mnt/gentoo/usr/portage/distfiles /mnt/gentoo/usr/portage \\\n"
+"/mnt/gentoo/usr /mnt/gentoo/var/tmp /mnt/gentoo/tmp /mnt/gentoo/var \\\n"
+"/mnt/gentoo/opt /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo/home \\\n"
+"/mnt/gentoo/boot /mnt/gentoo</i>\n"
+"livecd / # <i>reboot</i>\n"
+"<comment>(Don't forget to remove the CD)</comment>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86+raid+lvm2-quickinstall.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-x86-install.xml.po b/doc/gettext/ru/gentoo-x86-install.xml.po
new file mode 100644
index 0000000..3ff2a78
--- /dev/null
+++ b/doc/gettext/ru/gentoo-x86-install.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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(guide:link):5
+msgid "/doc/en/gentoo-x86-install.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(guide:redirect):5
+msgid "/doc/en/handbook/handbook-x86.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(title):6
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(title):22
+msgid "Gentoo x86 Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(abstract):12
+msgid "Replacement document for the installation guides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(version):18
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(date):19
+msgid "2004-03-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(p):26
+msgid ""
+"As of 2004.0, the individual architecture-specific installation guides have "
+"been obsoleted in favor of the new (and extended) <uri link=\"/doc/en/"
+"handbook/handbook-x86.xml\">Gentoo Handbook</uri>. For more information "
+"please read up on the <uri link=\"/doc/en/handbook/\">Gentoo Handbook "
+"Project</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-install.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-x86-quickinstall-after-reboot.xml.po b/doc/gettext/ru/gentoo-x86-quickinstall-after-reboot.xml.po
new file mode 100644
index 0000000..3db77f8
--- /dev/null
+++ b/doc/gettext/ru/gentoo-x86-quickinstall-after-reboot.xml.po
@@ -0,0 +1,312 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(version):7
+msgid "5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(date):8
+msgid "2010-10-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(title):11
+msgid "Finalizing the Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(note):14
+msgid ""
+"The <b>total</b> elapsed time between the display of the boot prompt on the "
+"minimal CD and the display of the login prompt after the reboot was "
+"<b>00:42:31</b> on our test box. Yes, less than one hour! Note that this "
+"time also includes the stage3, Portage snapshot and several packages "
+"download time and the time spent configuring the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):22
+msgid ""
+"Log in as <c>root</c>, then add one or more users for daily use with "
+"<c>useradd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):27
+msgid "Connect to your new box from another PC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):27
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Clean up your known_hosts file because your new box\n"
+"has generated a new definitive hostkey)</comment>\n"
+"$ <i>nano -w ~/.ssh/known_hosts</i>\n"
+"<comment>(Look for the IP of your new PC and delete the line,\n"
+"then save the file and exit nano)</comment>\n"
+"\n"
+"<comment>(Use the IP address of your new box)</comment>\n"
+"$ <i>ssh root@192.168.1.10</i>\n"
+"The authenticity of host '192.168.1.10 (192.168.1.10)' can't be established.\n"
+"RSA key fingerprint is 96:e7:2d:12:ac:9c:b0:94:90:9f:40:89:b0:45:26:8f.\n"
+"Are you sure you want to continue connecting (yes/no)? <i>yes</i>\n"
+"Warning: Permanently added '192.168.1.10' (RSA) to the list of known hosts.\n"
+"Password: <comment>type_the_password</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):43
+msgid "Add a new user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):43
+#, no-wrap
+msgid ""
+"\n"
+"mybox ~ # <i>useradd -g users -G lp,wheel,audio,cdrom,portage,cron -m john</i>\n"
+"mybox ~ # <i>passwd john</i>\n"
+"New UNIX password: <comment>Set John's password</comment>\n"
+"Retype new UNIX password: <comment>Type John's password again</comment>\n"
+"passwd: password updated successfully\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(title):54
+msgid "Last configuration touches"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):57
+msgid ""
+"Start by selecting nearby mirrors either by defining the <c>SYNC</c> and "
+"<c>GENTOO_MIRRORS</c> variables in <path>/etc/make.conf</path> or by using "
+"<c>mirrorselect</c>. You can also define the number of concurrent "
+"compilation processes at this point."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):64
+msgid "Use mirrorselect and set MAKEOPTS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):64
+#, no-wrap
+msgid ""
+"\n"
+"mybox ~ # <i>emerge mirrorselect</i>\n"
+"mybox ~ # <i>mirrorselect -i -o &gt;&gt; /etc/make.conf</i>\n"
+"mybox ~ # <i>mirrorselect -i -r -o &gt;&gt; /etc/make.conf</i>\n"
+"<comment>(Usually, (the number of processors + 1) is a good value)</comment>\n"
+"mybox ~ # <i>echo 'MAKEOPTS=\"-j2\"' &gt;&gt; /etc/make.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):72
+msgid ""
+"Now is a good time to enable or disable some USE flags. Run <c>emerge -vpe "
+"world</c> to list all currently installed packages and their enabled and "
+"disabled USE flags. Either edit <path>/etc/make.conf</path> or use the "
+"following command to define the USE variable:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):79
+msgid "View USE flags in use and enable or disable some"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):79
+#, no-wrap
+msgid ""
+"\n"
+"mybox ~ # <i>emerge -vpe world</i>\n"
+"<comment>(Portage displays the packages and their USE flags, as an example, let's\n"
+"disable ipv6 and fortran, and enable unicode)</comment>\n"
+"mybox ~ # <i>echo 'USE=\"nptl nptlonly -ipv6 -fortran unicode\"' &gt;&gt; /etc/make.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):86
+msgid ""
+"Recent versions of glibc use <path>/etc/locale.gen</path> to define locale "
+"settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):91
+msgid "Define locales"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):91
+#, no-wrap
+msgid ""
+"\n"
+"mybox ~ # <i>cd /etc</i>\n"
+"mybox etc # <i>nano -w locale.gen</i>\n"
+"mybox etc # <i>locale-gen</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):97
+msgid ""
+"Last but not least, you may want to alter the <c>CFLAGS</c> variable in your "
+"<path>/etc/make.conf</path> to optimise the code to your specific needs. "
+"Please note that using a long list of flags is rarely needed and can even "
+"lead to a broken system. It is recommended to specify the processor type in "
+"the <c>march</c> option and stick to <c>-O2 -pipe</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):105
+msgid ""
+"You may also want to switch to <b>~x86</b>. You should only do this if you "
+"can deal with the odd broken ebuild or package. If you'd rather keep your "
+"system stable, <e>don't</e> add the <c>ACCEPT_KEYWORDS</c> variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):111
+msgid "Last edit of make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):111
+#, no-wrap
+msgid ""
+"\n"
+"mybox etc # <i>nano -w make.conf</i>\n"
+"<comment>(Set -march to your CPU type in CFLAGS)</comment>\n"
+"CFLAGS=\"-O2 -march=<i>athlon-xp</i> -pipe\"\n"
+"<comment>(Only add the following if you know what you're doing)</comment>\n"
+"ACCEPT_KEYWORDS=\"~x86\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):119
+msgid ""
+"You might want to recompile your whole system twice to make full use of your "
+"latest configuration changes. It would take quite a long time to complete "
+"and yield minimal speed benefits. You can let your system optimise itself "
+"gradually over time when new versions of packages are released. However, "
+"recompiling is a still good idea from the standpoint of maintaining system "
+"consistency. Please see the <uri link=\"/doc/en/gcc-upgrading.xml\">Gentoo "
+"GCC Upgrading Guide</uri> for a discussion on the benefits of ensuring a "
+"consistently built system and world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):130
+msgid ""
+"Recompiling only the packages that have already been updated since the "
+"release or that are affected by your new USE flags will take enough time. "
+"You might also have to remove packages that block your upgrade. Look for "
+"\"[blocks <brite>B</brite> ]\" in the output of <c>emerge -vpuD --newuse "
+"world</c> and use <c>emerge -C</c> to remove them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):138
+msgid "Update your packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):138
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Please note that the switch to ~x86 causes many packages to be upgraded)</comment>\n"
+"mybox etc # <i>emerge -vpuD --newuse world</i>\n"
+"<comment>(Take a good look at the package list and their USE flags,\n"
+"remove blocking packages if any, and start the lengthy process)</comment>\n"
+"mybox etc # <i>time emerge -vuD --newuse world</i>\n"
+"<comment>(79 packages have been (re)compiled)</comment>\n"
+"\n"
+"real  180m13.276s\n"
+"user  121m22.905s\n"
+"sys   36m31.472s\n"
+"\n"
+"<comment>(Remerge libtool to avoid further potential problems)</comment>\n"
+"mybox etc # <i>emerge --oneshot libtool</i>\n"
+"\n"
+"<comment>(Update config files, make sure you <b>do not</b> let dispatch-conf\n"
+"update config files you have edited)</comment>\n"
+"mybox etc # <i>dispatch-conf</i>\n"
+"\n"
+"<comment>(If perl has been updated, you should run the perl-cleaner script)</comment>\n"
+"mybox etc # <i>time perl-cleaner all</i>\n"
+"real  1m6.495s\n"
+"user  0m42.699s\n"
+"sys   0m10.641s\n"
+"\n"
+"<comment>(In case of a major upgrade of python, you should run the python-updater script)</comment>\n"
+"mybox etc # <i>python-updater</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(title):170
+msgid "What to do next"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):173
+msgid ""
+"Depending on what your new Gentoo machine is supposed to do, you will "
+"probably want to install server applications or a desktop system. Just as an "
+"example, <c>emerge gnome</c> and <c>emerge kde</c> have been timed on the "
+"~x86 system installed as describe above. Both have been installed from the "
+"same starting point."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(p):181
+msgid ""
+"You should check our <uri link=\"/doc/en/\">documentation index</uri> to "
+"find out how to install and configure the applications of your choice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(impo):186
+msgid ""
+"The following is only an example. It is in no way meant as a recommended "
+"setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):190
+msgid "Emerge GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):190
+#, no-wrap
+msgid ""
+"\n"
+"mybox etc # <i>emerge -vp gnome</i>\n"
+"<comment>(Look at the list of packages and their USE flags,\n"
+"then edit make.conf if required.</comment>\n"
+"mybox etc # <i>nano -w /etc/make.conf</i>\n"
+"<comment>(The following USE flags have been defined)</comment>\n"
+"USE=\"nptl nptlonly -ipv6 -fortran unicode svg hal dbus \\\n"
+"     -kde -qt4 -arts -eds -esd gnome gstreamer gtk firefox\"\n"
+"\n"
+"mybox etc # <i>time emerge gnome</i>\n"
+"<comment>(326 packages have been emerged)</comment>\n"
+"\n"
+"real  520m44.532s\n"
+"user  339m21.144s\n"
+"sys   146m22.337s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre:caption):207
+msgid "Emerge KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(pre):207
+#, no-wrap
+msgid ""
+"\n"
+"mybox etc # <i>emerge -vp kde-meta</i>\n"
+"<comment>(Look at the list of packages and their USE flags,\n"
+"then edit make.conf if required.</comment>\n"
+"mybox etc # <i>nano -w /etc/make.conf</i>\n"
+"<comment>The following USE flags have been defined)</comment>\n"
+"USE=\"nptl nptlonly -ipv6 -fortran unicode svg hal dbus \\\n"
+"     kde qt4 -arts -eds -esd -gnome -gstreamer -gtk -firefox\"\n"
+"\n"
+"mybox etc # <i>time emerge kde-meta</i>\n"
+"<comment>(391 packages have been emerged)</comment>\n"
+"\n"
+"real  1171m25.318s\n"
+"user  851m26.393s\n"
+"sys   281m45.629s\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-after-reboot.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-x86-quickinstall-media.xml.po b/doc/gettext/ru/gentoo-x86-quickinstall-media.xml.po
new file mode 100644
index 0000000..0e3145a
--- /dev/null
+++ b/doc/gettext/ru/gentoo-x86-quickinstall-media.xml.po
@@ -0,0 +1,241 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(version):7
+msgid "5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(date):8
+msgid "2009-10-04"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):11
+msgid "Installation Media"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):14
+msgid ""
+"Download a CD from one of our <uri link=\"/main/en/mirrors.xml\">mirrors</"
+"uri>. You can find the minimal CD ISO in <path>releases/x86/current-iso/</"
+"path>. The <e>minimal</e> installation CD is only useful for Internet-based "
+"installations. This guide will use the minimal CD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):21
+msgid "<uri link=\"/doc/en/faq.xml#isoburning\">Burn</uri> the CD and boot it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):28
+msgid "Booting the CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):31
+msgid ""
+"Press <c>F2</c> at the boot screen to find out what boot options exist. You "
+"can either start <c>gentoo</c> or <c>gentoo-nofb</c>, the latter disables "
+"the framebuffer. If you booted the LiveCD, don't forget to add the <c>nox</"
+"c> option to prevent the X graphical environment from starting. Several "
+"options allow to enable or disable some features. If all goes well, your "
+"hardware will be detected and all modules will be loaded. If the kernel "
+"fails to boot properly or if your computer hangs during the boot procedure, "
+"you may have to experiment with different configurations. The safest way is "
+"probably to use the <c>nodetect</c> option and then load required modules "
+"explicitly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):43
+msgid "Boot the minimal CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):43
+#, no-wrap
+msgid ""
+"\n"
+"Gentoo Linux Installation LiveCD                     http://www.gentoo.org\n"
+"Enter to Boot; F1 for kernels  F2 for options.\n"
+"boot: <i>gentoo-nofb</i>\n"
+"  <comment>(or in case of problems)</comment>\n"
+"boot: <i>gentoo-nofb nodetect</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):54
+msgid "Optional: loading modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):57
+msgid ""
+"If you used the <c>nodetect</c> option, once booted, load the required "
+"modules. You need to enable networking and have access to your disks. The "
+"<c>lspci</c> command can help you identify your hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):63
+msgid "Load required modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):63
+#, no-wrap
+msgid ""
+"\n"
+"livecd root # <i>lspci</i>\n"
+"<comment>(Use lspci's output to identify required modules)</comment>\n"
+"\n"
+"<comment>(The following is an example, adapt it to your hardware)</comment>\n"
+"livecd root # <i>modprobe 3w-9xxx</i>\n"
+"livecd root # <i>modprobe r8169</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):75
+msgid "Network Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):78
+msgid ""
+"If your network does not work already, you can use <c>net-setup</c> to "
+"configure your network. You might need to load support for your network card "
+"using <c>modprobe</c> prior to the configuration. If you have ADSL, use "
+"<c>pppoe-setup</c> and <c>pppoe-start</c>. For PPTP support, first edit "
+"<path>/etc/ppp/chap-secrets</path> and <path>/etc/ppp/options.pptp</path> "
+"and then use <c>pptp &lt;server&nbsp;ip&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):87
+msgid ""
+"For wireless access, use <c>iwconfig</c> to set the wireless parameters and "
+"then use either <c>net-setup</c> again or run <c>ifconfig</c>, <c>dhcpcd</c> "
+"and/or <c>route</c> manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):93
+msgid ""
+"If you are behind a proxy, do not forget to initialize your system using "
+"<c>export http_proxy</c>, <c>ftp_proxy</c> and <c>RSYNC_PROXY</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):98
+msgid "Configure networking the guided way"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):98
+#, no-wrap
+msgid ""
+"\n"
+"livecd root # <i>net-setup eth0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):102
+msgid ""
+"Alternatively, you can start networking manually. The following example "
+"assigns the IP address 192.168.1.10 to your PC and defines 192.168.1.1 as "
+"your router and name server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):108
+msgid "Configure networking the manual way"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):108
+#, no-wrap
+msgid ""
+"\n"
+"livecd root # <i>ifconfig eth0 192.168.1.10/24</i>\n"
+"livecd root # <i>route add default gw 192.168.1.1</i>\n"
+"livecd root # <i>echo nameserver 192.168.1.1 &gt; /etc/resolv.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):114
+msgid ""
+"The installation CD allows you to start an <c>sshd</c> server, add "
+"additional users, run <c>irssi</c> (a command-line chat client) and surf the "
+"web using <c>links</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(title):123
+msgid "Optional: connect to your new box over ssh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):126
+msgid ""
+"The most interesting feature is of course <c>sshd</c>. You can start it and "
+"then connect from another machine and cut and paste commands from this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):131
+msgid "Start sshd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):131
+#, no-wrap
+msgid ""
+"\n"
+"livecd root # <i>time /etc/init.d/sshd start</i>\n"
+" * Generating hostkey ...\n"
+"<comment>(sshd generates the key and displays more output)</comment>\n"
+" * starting sshd ...                            [ok]\n"
+"\n"
+"real   0m13.688s\n"
+"user   0m9.420s\n"
+"sys    0m0.090s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):142
+msgid ""
+"Now, set the root password on the liveCD so that you can connect to it from "
+"another PC. Please note that allowing root to connect over ssh is not "
+"recommended under normal circumstances. If you can't trust your local "
+"network, use a long and complex password, you should use it only once as it "
+"will disappear after your first reboot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):150
+msgid "Set the root password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):150
+#, no-wrap
+msgid ""
+"\n"
+"livecd root # <i>passwd</i>\n"
+"New UNIX password: <comment>type_a_password</comment>\n"
+"Retype new UNIX password: <comment>type_a_password</comment>\n"
+"passwd: password updated successfully\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(p):157
+msgid ""
+"Now, you can start a terminal on another PC and connect to your new box, "
+"follow the rest of this guide in another window, and cut and paste commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre:caption):162
+msgid "Connect to your new box from another PC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(pre):162
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Use the IP address of your new box)</comment>\n"
+"$ <i>ssh root@192.168.1.10</i>\n"
+"The authenticity of host '192.168.1.10 (192.168.1.10)' can't be established.\n"
+"RSA key fingerprint is 96:e7:2d:12:ac:9c:b0:94:90:9f:40:89:b0:45:26:8f.\n"
+"Are you sure you want to continue connecting (yes/no)? <i>yes</i>\n"
+"Warning: Permanently added '192.168.1.10' (RSA) to the list of known hosts.\n"
+"Password: <comment>type_the_password</comment>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-media.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-x86-quickinstall-stage.xml.po b/doc/gettext/ru/gentoo-x86-quickinstall-stage.xml.po
new file mode 100644
index 0000000..7646b59
--- /dev/null
+++ b/doc/gettext/ru/gentoo-x86-quickinstall-stage.xml.po
@@ -0,0 +1,218 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(version):7
+msgid "10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(date):8
+msgid "2009-10-04"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(title):11
+msgid "Setting Up The Stage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):14
+msgid ""
+"First make sure your date and time is set correctly using <c>date "
+"MMDDhhmmYYYY</c>. Use UTC time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):19
+msgid "Set the date and UTC time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):19
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Check the clock)</comment>\n"
+"livecd gentoo # <i>date</i>\n"
+"Mon Mar  6 00:14:13 UTC 2006\n"
+"\n"
+"<comment>(Set the current date and time if required)</comment>\n"
+"livecd gentoo # <i>date 030600162006</i> <comment>(Format is MMDDhhmmYYYY)</comment>\n"
+"Mon Mar  6 00:16:00 UTC 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):29
+msgid ""
+"Next, download a stage from one of our <uri link=\"/main/en/mirrors.xml"
+"\">mirrors</uri>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):34
+msgid "Download a stage3 archive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):34
+#, no-wrap
+msgid ""
+"\n"
+"livecd gentoo # <i>links http://www.gentoo.org/main/en/mirrors.xml</i>\n"
+"<comment>(Pick a mirror, move to the releases/x86/current-stage3/ directory, highlight the stage3 of your choice, probably the i686 stage3 and press D to download it)</comment>\n"
+"\n"
+"<comment>(<b>Or</b> download it directly with wget without choosing a nearby mirror)</comment>\n"
+"livecd gentoo # <i>wget ftp://distfiles.gentoo.org/pub/gentoo/releases/x86/current-stage3/stage3-i686-*.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):42
+msgid ""
+"Go to <path>/mnt/gentoo</path> and unpack the stage using <c>tar xjpf &lt;"
+"stage3 tarball&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):47
+msgid "Unpack the stage3 archive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):47
+#, no-wrap
+msgid ""
+"\n"
+"livecd gentoo # <i>time tar xjpf stage3*</i>\n"
+"\n"
+"real  1m14.157s\n"
+"user  1m2.920s\n"
+"sys   0m7.530s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):55
+msgid ""
+"Install the latest Portage snapshot. Proceed as for the stage3 archive: "
+"choose a nearby mirror from our <uri link=\"/main/en/mirrors.xml\">list</"
+"uri>, download the latest snapshot and unpack it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):61
+msgid "Download the latest Portage snapshot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):61
+#, no-wrap
+msgid ""
+"\n"
+"livecd gentoo # <i>cd /mnt/gentoo/usr</i>\n"
+"livecd usr # <i>links http://www.gentoo.org/main/en/mirrors.xml</i>\n"
+"<comment>(Pick a mirror, move to the snapshots/ directory,\n"
+"highlight <b>portage-latest.tar.bz2</b> and press D to download it)</comment>\n"
+"\n"
+"<comment>(<b>Or</b> download it directly with wget without choosing a nearby mirror)</comment>\n"
+"livecd gentoo # <i>cd /mnt/gentoo/usr</i>\n"
+"livecd usr # <i>wget http://distfiles.gentoo.org/snapshots/portage-latest.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):72
+msgid "Unpack the Portage snapshot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):72
+#, no-wrap
+msgid ""
+"\n"
+"livecd usr # <i>time tar xjf portage-lat*</i>\n"
+"\n"
+"real  0m40.523s\n"
+"user  0m28.280s\n"
+"sys   0m8.240s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(title):83
+msgid "Chrooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):86
+msgid ""
+"Mount the <path>/proc</path> &amp; <path>/dev</path> file systems, copy over "
+"the <path>/etc/resolv.conf</path> file, then chroot into your Gentoo "
+"environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):92
+msgid "Chroot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):92
+#, no-wrap
+msgid ""
+"\n"
+"livecd usr # <i>cd /</i>\n"
+"livecd / # <i>mount -t proc proc /mnt/gentoo/proc</i>\n"
+"livecd / # <i>mount -o bind /dev /mnt/gentoo/dev</i>\n"
+"livecd / # <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/</i>\n"
+"livecd / # <i>chroot /mnt/gentoo /bin/bash</i>\n"
+"livecd / # <i>env-update &amp;&amp; source /etc/profile</i>\n"
+"&gt;&gt;&gt; Regenerating /etc/ld.so.cache...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(title):105
+msgid "Set your time zone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):108
+msgid ""
+"Set your time zone information by using the correct listing in <path>/usr/"
+"share/zoneinfo</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):113
+msgid "Setting your timezone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):113
+#, no-wrap
+msgid ""
+"\n"
+"livecd / # <i>ls /usr/share/zoneinfo</i>\n"
+"<comment>(Using Brussels as an example)</comment>\n"
+"livecd / # <i>cp /usr/share/zoneinfo/Europe/Brussels /etc/localtime</i>\n"
+"\n"
+"livecd / # <i>date</i>\n"
+"Wed Mar  8 00:46:05 CET 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(title):125
+msgid "Set your host name and domain name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(p):128
+msgid ""
+"Set your host name in <path>/etc/conf.d/hostname</path> and <path>/etc/"
+"hosts</path>. In the following example, we use <c>mybox</c> as host name and "
+"<c>at.myplace</c> as domain name. You can either edit the config files with "
+"<c>nano</c> or use the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre:caption):135
+msgid "Set host and domain name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(pre):135
+#, no-wrap
+msgid ""
+"\n"
+"livecd / # <i>cd /etc</i>\n"
+"livecd etc # <i>echo \"127.0.0.1 mybox.at.myplace mybox localhost\" &gt; hosts</i>\n"
+"livecd etc # <i>sed -i -e 's/HOSTNAME.*/HOSTNAME=\"mybox\"/' conf.d/hostname</i>\n"
+"<comment>(Use defined host name and check)</comment>\n"
+"livecd etc # <i>hostname mybox</i>\n"
+"livecd etc # <i>hostname -f</i>\n"
+"mybox.at.myplace\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-stage.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-x86-quickinstall-system.xml.po b/doc/gettext/ru/gentoo-x86-quickinstall-system.xml.po
new file mode 100644
index 0000000..cc85c7c
--- /dev/null
+++ b/doc/gettext/ru/gentoo-x86-quickinstall-system.xml.po
@@ -0,0 +1,339 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(version):7
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(date):8
+msgid "2008-03-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):11
+msgid "Configure the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):15
+msgid ""
+"Edit your <path>/etc/fstab</path> and replace <c>BOOT</c>, <c>ROOT</c> and "
+"<c>SWAP</c> with the actual partition names. Don't forget to check that the "
+"file systems match your installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):21
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):38
+msgid "Example fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):21
+#, no-wrap
+msgid ""
+"\n"
+"livecd linux # <i>cd /etc</i>\n"
+"livecd etc # <i>nano -w fstab</i>\n"
+"/dev/<i>sda1</i>   /boot     ext2    noauto,noatime     1 2\n"
+"/dev/<i>sda3</i>   /         ext3    noatime            0 1\n"
+"/dev/<i>sda2</i>   none      swap    sw                 0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):32
+msgid ""
+"Edit your <path>/etc/fstab</path> and replace <c>BOOT</c>, <c>ROOT</c> and "
+"<c>SWAP</c> with the actual partition names and add your logical volumes. "
+"Don't forget to check that the file systems match your installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):38
+#, no-wrap
+msgid ""
+"\n"
+"livecd linux # <i>cd /etc</i>\n"
+"livecd etc # <i>nano -w fstab</i>\n"
+"/dev/<i>md1</i>          /boot                   ext2  noauto,noatime  1 2\n"
+"/dev/<i>md3</i>          /                       ext3  noatime         0 1\n"
+"/dev/<i>sda2</i>         none                    swap  sw,pri=1        0 0\n"
+"/dev/<i>sdb2</i>         none                    swap  sw,pri=1        0 0\n"
+"/dev/vg/usr       /usr                    ext3  noatime         1 2\n"
+"/dev/vg/portage   /usr/portage            ext2  noatime         1 2\n"
+"/dev/vg/distfiles /usr/portage/distfiles  ext2  noatime         1 2\n"
+"/dev/vg/home      /home                   ext3  noatime         1 2\n"
+"/dev/vg/opt       /opt                    ext3  noatime         1 2\n"
+"/dev/vg/tmp       /tmp                    ext2  noatime         1 2\n"
+"/dev/vg/var       /var                    ext3  noatime         1 2\n"
+"/dev/vg/vartmp    /var/tmp                ext2  noatime         1 2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):58
+msgid ""
+"Configure your network in <path>/etc/conf.d/net</path>. Add the <c>net.eth0</"
+"c> init script to the default run level. If you have multiple NICs, symlink "
+"them to the <c>net.eth0</c> init script and add them to the default run "
+"level as well. Either edit <path>/etc/conf.d/net</path> with <c>nano</c> or "
+"use the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):66
+msgid "Configure networking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):66
+#, no-wrap
+msgid ""
+"\n"
+"livecd etc # <i>cd conf.d</i>\n"
+"livecd conf.d # <i>echo 'config_eth0=( \"192.168.1.10/24\" )' &gt;&gt; net</i>\n"
+"livecd conf.d # <i>echo 'routes_eth0=( \"default via 192.168.1.1\" )' &gt;&gt; net</i>\n"
+"livecd conf.d # <i>rc-update add net.eth0 default</i>\n"
+"<comment>(If you compiled your network card driver as a module,\n"
+"add it to /etc/modules.autoload.d/kernel-2.6)</comment>\n"
+"livecd conf.d # <i>echo r8169 &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+"<comment>(If you want to reconnect via ssh after you have rebooted your new box)</comment>\n"
+"livecd conf.d # <i>rc-update add sshd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):78
+msgid "Emerge <c>pcmciautils</c> if you need support for PCMCIA cards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):82
+msgid "Set the root password using <c>passwd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):86
+msgid "Set the root password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):86
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>passwd</i>\n"
+"New UNIX password: <comment>type_the_password</comment>\n"
+"Retype new UNIX password: <comment>type_the_password_again</comment>\n"
+"passwd: password updated successfully\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):93
+msgid ""
+"Edit <path>/etc/conf.d/clock</path> to define the time zone you used "
+"previously."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):98
+msgid "Edit /etc/conf.d/clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):98
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>nano -w /etc/conf.d/clock</i>\n"
+"TIMEZONE=\"Europe/Brussels\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):103
+msgid ""
+"Check the system configuration in <path>/etc/rc.conf</path>, <path>/etc/conf."
+"d/rc</path>, <path>/etc/conf.d/keymaps</path> and edit any of those files if "
+"required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):109
+msgid "Optional: edit some config files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):109
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>nano -w /etc/rc.conf</i>\n"
+"livecd conf.d # <i>nano -w /etc/conf.d/rc</i>\n"
+"livecd conf.d # <i>nano -w /etc/conf.d/keymaps</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):118
+msgid "Installing System Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):122
+msgid "Install RAID and LVM2 utilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):126
+msgid "Install RAID LVM2 tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):126
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>emerge mdadm lvm2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):133
+msgid ""
+"Install a system logger like <c>syslog-ng</c> and a cron daemon like "
+"<c>vixie-cron</c>, and add them to the default run level."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):138
+msgid ""
+"Cron daemons depend on an MTA. <c>mail-mta/ssmtp</c> will be pulled in as a "
+"dependency. If you want to use a more advanced MTA, you might want to "
+"install it now. If you are in a hurry, let ssmtp be installed and remove it "
+"later when you install the MTA of your choice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):145
+msgid "Install a syslogger and a cron daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):145
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>time emerge syslog-ng vixie-cron</i>\n"
+"\n"
+"real  1m54.099s\n"
+"user  1m2.630s\n"
+"sys   0m34.620s\n"
+"livecd conf.d # <i>rc-update add syslog-ng default</i>\n"
+"livecd conf.d # <i>rc-update add vixie-cron default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):155
+msgid ""
+"Install the necessary file system tools (<c>xfsprogs</c>, <c>reiserfsprogs</"
+"c> or <c>jfsutils</c>) and networking tools (<c>dhcpcd</c> or <c>ppp</c>) if "
+"you need any."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):161
+msgid "Install extra tools if required"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):161
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>emerge xfsprogs</i>       <comment>(If you use the XFS file system)</comment>\n"
+"livecd conf.d # <i>emerge jfsutils</i>       <comment>(If you use the JFS file system)</comment>\n"
+"livecd conf.d # <i>emerge reiserfsprogs</i>  <comment>(If you use the Reiser file system)</comment>\n"
+"livecd conf.d # <i>emerge dhcpcd</i>         <comment>(If you need a DHCP client)</comment>\n"
+"livecd conf.d # <i>emerge ppp</i>            <comment>(If you need PPPoE ADSL connectivity)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):173
+msgid "Configuring the Bootloader"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):176
+msgid "Emerge <c>grub</c> and configure it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):180
+msgid "Emerge grub and edit its configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):180
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>time emerge grub</i>\n"
+"\n"
+"real  1m4.634s\n"
+"user  0m39.460s\n"
+"sys   0m15.280s\n"
+"livecd conf.d # <i>nano -w /boot/grub/grub.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):189
+msgid "Example grub.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):189
+#, no-wrap
+msgid ""
+"\n"
+"default 0\n"
+"timeout 10\n"
+"\n"
+"title Gentoo\n"
+"root (hd0,0)\n"
+"kernel /boot/kernel root=<keyval id=\"root\"></keyval>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):198
+msgid "Install grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):198
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>grub</i>\n"
+"Probing devices to guess BIOS drives. This may take a long time.\n"
+"\n"
+"grub&gt; <i>root (hd0,0)</i>\n"
+" Filesystem type is ext2fs, partition type 0xfd\n"
+"\n"
+"grub&gt; <i>setup (hd0)</i>\n"
+" Checking if \"/boot/grub/stage1\" exists... yes\n"
+" Checking if \"/boot/grub/stage2\" exists... yes\n"
+" Checking if \"/boot/grub/e2fs_stage1_5\" exists... yes\n"
+" Running \"embed /boot/grub/e2fs_stage1_5 (hd0)\"...  16 sectors are embedded.\n"
+"succeeded\n"
+" Running \"install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/\n"
+"grub/menu.lst\"... succeeded\n"
+"Done.\n"
+"\n"
+"grub&gt; <i>quit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):218
+msgid "Install grub on both disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):218
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>grub</i>\n"
+"Probing devices to guess BIOS drives. This may take a long time.\n"
+"\n"
+"grub&gt; <i>root (hd0,0)</i>\n"
+" Filesystem type is ext2fs, partition type 0xfd\n"
+"\n"
+"grub&gt; <i>setup (hd0)</i>\n"
+" Checking if \"/boot/grub/stage1\" exists... yes\n"
+" Checking if \"/boot/grub/stage2\" exists... yes\n"
+" Checking if \"/boot/grub/e2fs_stage1_5\" exists... yes\n"
+" Running \"embed /boot/grub/e2fs_stage1_5 (hd0)\"...  16 sectors are embedded.\n"
+"succeeded\n"
+" Running \"install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/\n"
+"grub/menu.lst\"... succeeded\n"
+"Done.\n"
+"\n"
+"grub&gt; <i>root (hd1,0)</i>\n"
+" Filesystem type is ext2fs, partition type 0xfd\n"
+"\n"
+"grub&gt; <i>setup (hd1)</i>\n"
+"\n"
+"grub&gt; <i>quit</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-x86-quickinstall.xml.po b/doc/gettext/ru/gentoo-x86-quickinstall.xml.po
new file mode 100644
index 0000000..dfd7014
--- /dev/null
+++ b/doc/gettext/ru/gentoo-x86-quickinstall.xml.po
@@ -0,0 +1,257 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):6
+msgid "Gentoo Linux x86 Quick Install Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(key):9
+msgid "no"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(key):10
+msgid "/dev/sda3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(author:title):13
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(author:title):16
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(author:title):19
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(mail:link):14
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(mail:link):17
+msgid "swift"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(author):19
+msgid "Steven Wagner"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(abstract):21
+msgid ""
+"The Quick Install guide covers the Gentoo install process in a non-verbose "
+"manner. Its purpose is to allow users to perform a stage3 install in no "
+"time. Users should already have prior experience with installing Gentoo "
+"Linux if they want to follow this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(version):32
+msgid "25"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(date):33
+msgid "2010-01-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):36
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):40
+msgid ""
+"This guide contains all the commands you should use to complete a stage3 "
+"installation of Gentoo. You need a connection to the Internet to download "
+"the stage3 and Portage snapshots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(impo):46
+msgid ""
+"New users should read the <uri link=\"/doc/en/handbook/index.xml\">Handbook</"
+"uri> as it gives a better overview about the installation process. The Quick "
+"Install guide is designed for experienced users who just need a checklist to "
+"follow."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):52
+msgid ""
+"Timing output follows all commands that take more than a couple of seconds "
+"to finish. Commands were timed on an AMD 2000 1.66 Ghz PC with 512 MB of RAM "
+"and two SATA disks connected to a hardware controller."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):58
+msgid "Test box specs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):58
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(The following specs and the timing information should help you determine\n"
+"a rough estimate of the time you need to complete your install)</comment>\n"
+"\n"
+"# <i>grep bogo /proc/cpuinfo</i>\n"
+"bogomips       : 3337.81\n"
+"\n"
+"# <i>hdparm -tT /dev/sda</i>\n"
+"/dev/sda:\n"
+" Timing cached reads:   1100 MB in  2.00 seconds = 549.97 MB/sec\n"
+" Timing buffered disk reads:  224 MB in  3.01 seconds =  74.36 MB/sec\n"
+"\n"
+"# <i>grep MemTotal /proc/meminfo</i>\n"
+"MemTotal:       509248 kB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):79
+msgid "Quick Install Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):86
+msgid "Preparing the Disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):89
+msgid ""
+"Use <c>fdisk</c> or <c>cfdisk</c> to create your partition layout. You need "
+"at least a swap partition (type 82) and one Linux partition (type 83). The "
+"following scenario creates a <path>/boot</path>, a swap and a main partition "
+"as used in our handbook. Replace <path>sda</path> with your disk. Most "
+"systems ignore the bootable flag, but a few need it. Set this flag on your "
+"boot partition with fdisk's <c>a</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):98
+msgid "Create the partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):98
+#, no-wrap
+msgid ""
+"\n"
+"livecd ~ # <i>fdisk /dev/sda</i>\n"
+"\n"
+"<comment>(The rest of this guide uses the following partitioning scheme)</comment>\n"
+"livecd ~ # <i>fdisk -l /dev/sda</i>\n"
+"\n"
+"Disk /dev/sda: 599.9 GB, 599978409984 bytes\n"
+"255 heads, 63 sectors/track, 72943 cylinders\n"
+"Units = cylinders of 16065 * 512 = 8225280 bytes\n"
+"\n"
+"   Device Boot      Start         End      Blocks   Id  System\n"
+"/dev/sda1   *           1          12       96358+  83  Linux\n"
+"/dev/sda2              13         110      787185   82  Linux swap / Solaris\n"
+"/dev/sda3             111       72943   585031072+  83  Linux\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):114
+msgid ""
+"Use <c>mke2fs</c>, <c>mke2fs -j</c>, <c>mkreiserfs</c>, <c>mkfs.xfs</c> and "
+"<c>mkfs.jfs</c> to create file systems on your Linux partitions. Initialize "
+"your swap partition using <c>mkswap</c> and <c>swapon</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):120
+msgid "Create the file systems and activate swap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):120
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(ext2 is all you need on the /boot partition)</comment>\n"
+"livecd ~ # <i>mke2fs /dev/sda1</i>\n"
+"\n"
+"<comment>(Let's use ext3 on the main partition)</comment>\n"
+"livecd ~ # <i>mke2fs -j /dev/sda3</i>\n"
+"\n"
+"<comment>(Create and activate swap)</comment>\n"
+"livecd ~ # <i>mkswap /dev/sda2 &amp;&amp; swapon /dev/sda2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):131
+msgid ""
+"Mount the freshly created file systems on <path>/mnt/gentoo</path>. Create "
+"directories for the other mount points (like <path>/mnt/gentoo/boot</path>) "
+"if you need them and mount them too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):137
+msgid "Mount the file systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):137
+#, no-wrap
+msgid ""
+"\n"
+"livecd ~ # <i>mount /dev/sda3 /mnt/gentoo</i>\n"
+"livecd ~ # <i>mkdir /mnt/gentoo/boot</i>\n"
+"livecd ~ # <i>mount /dev/sda1 /mnt/gentoo/boot</i>\n"
+"livecd ~ # <i>cd /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):152
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):155
+msgid ""
+"Install a kernel source (usually <c>gentoo-sources</c>), configure it, "
+"compile it and copy the <path>arch/i386/boot/bzImage</path> file to <path>/"
+"boot</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):160
+msgid "Install a kernel source, compile it and install the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):160
+#, no-wrap
+msgid ""
+"\n"
+"livecd etc # <i>time emerge gentoo-sources</i>\n"
+"\n"
+"real  2m51.435s\n"
+"user  0m58.220s\n"
+"sys   0m29.890s\n"
+"livecd etc # <i>cd /usr/src/linux</i>\n"
+"livecd linux # <i>make menuconfig</i>\n"
+"<comment>(Configure your kernel)</comment>\n"
+"livecd linux # <i>time make -j2</i>\n"
+"\n"
+"<comment>(Elapsed time depends highly on the options you selected)</comment>\n"
+"real  3m51.962s\n"
+"user  3m27.060s\n"
+"sys   0m24.310s\n"
+"\n"
+"livecd linux # <i>make modules_install</i>\n"
+"livecd linux # <i>cp arch/i386/boot/bzImage /boot/kernel</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(title):188
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre:caption):195
+msgid "Reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(p):191
+msgid "Exit the chrooted environment, unmount all file systems and reboot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(pre):195
+#, no-wrap
+msgid ""
+"\n"
+"livecd conf.d # <i>exit</i>\n"
+"livecd / # <i>umount /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i>\n"
+"livecd / # <i>reboot</i>\n"
+"<comment>(Don't forget to remove the CD)</comment>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoo-x86-tipsntricks.xml.po b/doc/gettext/ru/gentoo-x86-tipsntricks.xml.po
new file mode 100644
index 0000000..8720883
--- /dev/null
+++ b/doc/gettext/ru/gentoo-x86-tipsntricks.xml.po
@@ -0,0 +1,659 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(guide:link):5
+msgid "/doc/en/gentoo-x86-tipsntricks.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):6
+msgid "Gentoo/x86 Installation Tips &amp; Tricks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(mail:link):12
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(mail):12
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(abstract):15
+msgid ""
+"The Gentoo installation allows for very flexible approaches to the various "
+"installation methods. As it is almost impossible to insert every single tip "
+"or trick in the installation instructions this document tries to deal with "
+"all submitted tips and tricks for reference purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(version):26
+msgid "1.15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(date):27
+msgid "2007-09-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):30
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):32
+msgid "Preliminary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):35
+msgid ""
+"This document contains various tips and tricks for the Gentoo/x86 "
+"installation. Most of them are discussed in a dense way - they are meant as "
+"an addendum to the installation instructions and not as a replacement."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):44
+msgid "Contents"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):52
+msgid "#software-raid"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):52
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):82
+msgid "Software RAID"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):53
+msgid "#ata-raid-2.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):53
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):182
+msgid "ATA RAID using 2.4 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):54
+msgid "#livecd-kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):54
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):257
+msgid "Using the Installation CD kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):62
+msgid "#leave_terminal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):62
+msgid "Leaving the Terminal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):70
+msgid "#checking-disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):70
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):393
+msgid "Extensive Testing of your Disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri:link):72
+msgid "#recover"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(uri):72
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):411
+msgid "Recovering from a malfunctioning installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):80
+msgid "Advanced Installations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(note):85
+msgid ""
+"If you are not familiar with software raid, please read the <uri link="
+"\"http://tldp.org/HOWTO/Software-RAID-HOWTO.html\">Software-RAID-HOWTO</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(note):90
+msgid ""
+"A more detailed procedure can be found in our <uri link=\"/doc/en/gentoo-"
+"x86+raid+lvm2-quickinstall.xml\">Software Raid and LVM2 x86 Quick Install "
+"Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):96
+msgid ""
+"Once you are booted from the Installation CD, load the appropriate RAID "
+"modules. For instance, if you plan on using RAID-1:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):101
+msgid "Loading the RAID-1 module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):101
+#, no-wrap
+msgid ""
+"\n"
+"# <i>modprobe raid1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):105
+msgid ""
+"When you partition your disks, make sure that your partitions use <c>fd</c> "
+"(Linux raid autodetect) as Partition Type instead of <c>83</c> (Linux "
+"native). You can alter the partition type using the <c>t</c> command in "
+"<c>fdisk</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):111
+msgid ""
+"Now before we start creating the RAID arrays, we need to create the "
+"metadevice nodes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):116
+msgid "Creating metadevice nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):116
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mknod /dev/md1 b 9 1</i>\n"
+"# <i>mknod /dev/md2 b 9 2</i>\n"
+"# <i>mknod /dev/md3 b 9 3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):122
+msgid ""
+"After partitioning, create the <path>/etc/mdadm.conf</path> file (yes, "
+"indeed, on the Installation CD environment) using <c>mdadm</c>, an advanced "
+"tool for <uri link=\"http://www.linuxdevcenter.com/pub/a/linux/2002/12/05/"
+"RAID.html\">RAID management</uri>. For instance, to have your boot, swap and "
+"root partition mirrored (RAID-1) covering <path>/dev/sda</path> and <path>/"
+"dev/sdb</path>, you can use:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):131
+msgid "Creating raid devices with the mdadm command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):131
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mdadm --create --verbose /dev/md1 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1</i>\n"
+"# <i>mdadm --create --verbose /dev/md2 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2</i>\n"
+"# <i>mdadm --create --verbose /dev/md3 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(impo):137
+msgid ""
+"You should not use any form of striping such as RAID-0 or RAID-5 on the "
+"partition you boot from."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):142
+msgid ""
+"The Linux Software RAID driver will start creating the metadevices. You can "
+"see its progress in <path>/proc/mdstat</path>. Wait until the metadevices "
+"are completely finished before proceeding."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):148
+msgid "Saving information about the created devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):148
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mdadm --detail --scan &gt; /etc/mdadm.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):152
+msgid ""
+"From now onwards, use <path>/dev/md1</path> for the boot partition, <path>/"
+"dev/md2</path> for the swap partition and <path>/dev/md3</path> for the root "
+"partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):158
+msgid ""
+"Right before chrooting, don't forget to copy over <path>/etc/mdadm.conf</"
+"path> to <path>/mnt/gentoo/etc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):163
+msgid ""
+"When you're configuring your kernel, make sure you have the appropriate RAID "
+"support <e>in</e> your kernel and not as module."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):168
+msgid ""
+"When installing extra tools, emerge <c>mdadm</c> as well. Note that this "
+"isn't available on all Installation CDs so you might not be able to install "
+"Gentoo on a Software RAID when using a networkless installation!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):174
+msgid ""
+"When configuring your bootloader, make sure it gets installed in the MBR of "
+"<e>both</e> disks if you use mirroring."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):185
+msgid ""
+"Make sure you boot your Installation CD using the <c>doataraid</c> option. "
+"Once booted, check the contents of <path>/dev/ataraid</path>. It should "
+"contain various <path>disc*</path> directories for each harddisk available "
+"in the ATA RAID. An entire disk is displayed as <path>disc</path> while "
+"partitions are <path>part*</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):193
+msgid ""
+"Write down the various <path>/dev/ataraid/disc*/*</path> device files that "
+"you use to install Gentoo on. You will need to substitute the <path>/dev/"
+"hda</path> examples in the installation with this path."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):199
+msgid ""
+"Before chrooting, bind-mount the <path>/dev</path> structure in the new "
+"environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):204
+msgid "Bind-mounting /dev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):204
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount -o bind /dev /mnt/gentoo/dev</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):208
+msgid ""
+"When configuring your kernel, make sure you enable support for your ATA RAID "
+"chipset and options. For instance, a popular ATA RAID system is a <e>Promise "
+"FastTrack built-in RAID</e> in which case you definitely need <c>Promise "
+"FastTrack Options</c> built in into your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):215
+msgid ""
+"When configuring GRUB, you first have to create a GRUB bootdisk. This is not "
+"as hard as you think. First install GRUB as you would, but when you come to "
+"the part where GRUB is getting installed in the MBR, follow the following "
+"instructions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):222
+msgid "Creating a GRUB bootdisk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):222
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /boot/grub</i>\n"
+"# <i>dd if=stage1 of=/dev/fd0 bs=512 count=1</i>\n"
+"# <i>dd if=stage2 of=/dev/fd0 bs=512 seek=1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):228
+msgid ""
+"You still need to write your <path>grub.conf</path> file. This is no "
+"different from the installation instructions, just make sure that your "
+"<c>root=</c> points to the ATA RAID device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):234
+msgid ""
+"After finishing the installation, boot with your GRUB bootdisk. You will be "
+"greeted by a GRUB prompt. Now configure GRUB to boot from the ATA RAID "
+"device:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):239
+msgid "Installing GRUB on the ATA RAID"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):239
+#, no-wrap
+msgid ""
+"\n"
+"grub&gt; root (hd0,x)\n"
+"grub&gt; setup (hd0)\n"
+"grub&gt; quit\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):245
+msgid "Now reboot (with the GRUB bootfloppy removed)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):249
+msgid ""
+"LILO users can safely use the instructions mentioned in the installation "
+"instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):260
+msgid ""
+"If you don't want to compile a kernel yourself you can use the kernel from "
+"the Installation CD and copy it to your system. When you come to the point "
+"that you're asked to compile a kernel, go to another terminal (press Alt-F2) "
+"and log in with the root password you've supplied at the beginning of the "
+"installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):268
+msgid "Copy over the kernel and modules to your Gentoo system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):272
+msgid "Copying over the Installation CD kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):272
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(${KN} is the kernel name, usually something like 'gentoo' or 'smp')</comment>\n"
+"cdimage ~# <i>cp /mnt/cdrom/isolinux/${KN} /mnt/cdrom/isolinux/${KN}.igz /mnt/gentoo/boot</i>\n"
+"cdimage ~# <i>mkdir -p /mnt/gentoo/lib/modules</i>\n"
+"cdiamge ~# <i>cp -Rp /lib/modules/`uname -r` /mnt/gentoo/lib/modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):279
+msgid ""
+"To have all modules that are currently running (from the Installation CD) "
+"loaded during bootup of your Gentoo system, run the following command from "
+"within the chrooted environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):285
+msgid "Adding all running modules to the modules.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):285
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cat /proc/modules | cut -d ' ' -f 1 &gt;&gt; \\</i>\n"
+"  <i>/etc/modules.autoload.d/kernel-`uname -r | cut -d . -f -2`</i>\n"
+"# <i>update-modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):296
+msgid "Simplifying the Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):298
+msgid "Leaving your Terminal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):301
+msgid ""
+"Many people want to leave their system when it's compiling. In certain cases "
+"this is rather difficult as the installation is done in a public environment "
+"where you cannot trust everyone. If this is the case, you want to be able to "
+"perform the compilation in the background and log out from all terminals."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):308
+msgid ""
+"There are several possible solutions for this. The first one is to use "
+"<c>screen</c>. After booting the Installation CD, set your root password and "
+"start a screen session:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(note):314
+msgid ""
+"Not all Installation CDs provide screen. If this is the case, you will have "
+"to use one of the other methods described in this section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):319
+msgid "Starting a screen session"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):319
+#, no-wrap
+msgid ""
+"\n"
+"# <i>screen -S gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):323
+msgid ""
+"Once inside the screen session you can perform the entire installation. When "
+"you want to leave your terminal, press <c>Ctrl-a, d</c> (that is, control "
+"and a at the same time, then followed by a d) to <e>detach</e> your screen "
+"session. You can now safely log out of your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):330
+msgid ""
+"To regain access to your terminal, log in as root again and <e>attach</e> to "
+"the running screen session:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):335
+msgid "Attaching to a screen session"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):335
+#, no-wrap
+msgid ""
+"\n"
+"# <i>screen -x gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):339
+msgid ""
+"If you can't use screen, there is still a way to leave your terminal. Follow "
+"the installation instructions, but when you come to the point where a long-"
+"term compilation would be started (for instance the <c>./scripts/bootstrap."
+"sh</c> step), use <c>nohup</c> which allows for a process to continue even "
+"when you log out. Don't forget the trailing \"&amp;\", otherwise the process "
+"won't be placed in the background! Remember where you are (the <c>pwd</c> "
+"command will show you that) as you will need to know this later on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):349
+msgid "Using nohup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):349
+#, no-wrap
+msgid ""
+"\n"
+"# <i>pwd</i>\n"
+"/usr/portage\n"
+"# <i>nohup ./scripts/bootstrap.sh &amp;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):355
+msgid ""
+"Now exit the chrooted environment (<c>exit</c>) and the Installation CD "
+"session. Your compilation will continue in the background."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):360
+msgid ""
+"When you want to check the compilation, log in as root (on the Installation "
+"CD) and chroot back into your environment and go to the directory where you "
+"left off:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):366
+msgid "Chrooting back"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):366
+#, no-wrap
+msgid ""
+"\n"
+"# <i>chroot /mnt/gentoo /bin/bash</i>\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+"# <i>cd /usr/portage</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):372
+msgid ""
+"Now use the <c>less</c> command on the <path>nohup.out</path> file that is "
+"situated inside that directory. The compilation will append its output to "
+"that file, so if you want to follow the compilation progress, run <c>less "
+"nohup.out</c> and press <c>F</c> to follow the changes. When the compilation "
+"is finished, you can continue with the next step of the installation "
+"instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):380
+msgid ""
+"If you ever get tired of following the changes, press <c>Ctrl-C</c> followed "
+"by a <c>q</c>. This won't stop the compilation process, only the <c>less</c> "
+"process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(title):391
+msgid "Fixing Errors/Issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):396
+msgid ""
+"If you think your disk needs to be thoroughly checked for consistency (bad "
+"sectors and such), you can use the <c>-c</c> option while placing the ext2 "
+"or ext3 filesystem on it (using <c>mke2fs</c>). This will format, perform a "
+"read-test and mark all bad blocks as such. If you are really paranoid, use "
+"<c>-c -c</c> to format your disk and perform an extensive read/write test."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre:caption):404
+msgid "Checking for disk consistency"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(pre):404
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mke2fs -j -c /dev/hda3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):414
+msgid ""
+"If for some reason your Gentoo installation fails, you don't have to redo "
+"the installation all over again. Instead, you can safely \"go\" to the point "
+"where you think you made a mistake (or where you think the instructions are "
+"flawed) and try a different approach."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):421
+msgid ""
+"First of all you need to chroot back into your Gentoo Linux environment. "
+"Follow the instructions again, but ignore the partitioning steps as your "
+"partitions are already created and even populated. You can therefore "
+"immediately mount those partitions at <path>/mnt/gentoo</path>. You should "
+"also ignore the steps about stage extraction and modifying <path>make.conf</"
+"path> - you don't want to overwrite your files do you?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):430
+msgid ""
+"Once chrooted inside your Gentoo Linux environment, immediately go to the "
+"step where you think you should try a different approach. Don't redo all the "
+"steps like bootstrapping and such unless that is the place where you think "
+"things went wrong."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):437
+msgid ""
+"For instance, if you believe that you have a wrongly configured <path>grub."
+"conf</path>, you can immediately fire up your editor to update <path>/boot/"
+"grub/grub.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):443
+msgid ""
+"Once you have tried a different approach for your situation, you should "
+"consider how much of the subsequent steps you need to perform again. If the "
+"subsequent steps are depending on your change, you will need to redo those."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):449
+msgid "For instance,"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(li):454
+msgid ""
+"if you have changed a variable inside <path>make.conf</path> you will need "
+"to do all subsequent compiling since those depend on the settings inside "
+"<path>make.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(li):459
+msgid ""
+"if you have altered <path>/boot/grub/grub.conf</path> you can immediately "
+"exit the chrooted environment and reboot as no subsequent steps are "
+"depending on <path>grub.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(li):464
+msgid ""
+"if you have recompiled your kernel you only need to make sure that your "
+"bootloader configuration points to the correct kernel image (double-check "
+"that you mounted your <path>/boot</path>!), then you can exit the chrooted "
+"environment and reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(li):470
+msgid ""
+"if you have altered <path>/etc/fstab</path> you can exit the chrooted "
+"environment and reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(p):476
+msgid ""
+"As you can see, for most recovery operations you can immediately reboot. "
+"Only in certain cases will you need to redo the subsequent installation "
+"steps."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-tipsntricks.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gentoolkit.xml.po b/doc/gettext/ru/gentoolkit.xml.po
new file mode 100644
index 0000000..0467827
--- /dev/null
+++ b/doc/gettext/ru/gentoolkit.xml.po
@@ -0,0 +1,1016 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):6
+msgid "Gentoolkit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):9
+msgid "mbutcher@aleph-null.tv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):9
+msgid "Matt Butcher"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):23
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):26
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author:title):29
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(author):11
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):15
+msgid "erwin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):15
+msgid "Erwin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):18
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):18
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):21
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):21
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):24
+msgid "karltk@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):24
+msgid "Karl Trygve"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):27
+msgid "yoswink@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):27
+msgid "José Luis Rivero"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail:link):30
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(mail):30
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(abstract):33
+msgid ""
+"Gentoolkit is a suite of tools to ease the administration of a Gentoo "
+"system. This document covers the basics of some of the tools present in "
+"Gentoolkit."
+msgstr ""
+
+#. Licensed under GFDL
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(version):40
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(date):41
+msgid "2010-10-03"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):44
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):112
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):443
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):46
+msgid "What is Gentoolkit?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):49
+msgid ""
+"Gentoo is a unique distribution and presents some complexities that simply "
+"don't exist for other distributions. As Gentoo developers and contributors "
+"discovered some of these complexities, they also wrote tools to help users "
+"and administrators work around them. Many of these tools have been "
+"contributed to the Gentoo project and are included in the package <c>app-"
+"portage/gentoolkit</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):58
+msgid ""
+"As of now, there are two versions of gentoolkit: <c>app-portage/gentoolkit</"
+"c> and <c>app-portage/gentoolkit-dev</c>. While the former contains "
+"administration scripts, the latter contains scripts specific to help "
+"development on Gentoo. If you are a developer, you can have your scripts "
+"included into <c>gentoolkit-dev</c> by contacting the Gentoolkit maintainer. "
+"This document discusses gentoolkit only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):67
+msgid ""
+"Gentoolkit contains a whole bunch of useful tools to help manage your "
+"packages and keep track of what is going on in your system. Most users --"
+"&nbsp;particularly those who update systems often&nbsp;-- will benefit from "
+"having gentoolkit installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):77
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):80
+msgid "Just as with any Gentoo package, installation is just a simple emerge."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):84
+msgid "Getting gentoolkit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):84
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gentoolkit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):88
+msgid ""
+"Many of the tools in gentoolkit reveal important information about your "
+"system or require root privilege. For that reason, some of the programs may "
+"only be executed (or only function properly) if run by a user with root "
+"permission."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):97
+msgid "Finding Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):100
+msgid ""
+"Any documentation that a program might have (other than man pages) is stored "
+"in <path>/usr/share/doc/gentoolkit-[version]/[program-name]/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):110
+msgid "equery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):115
+msgid ""
+"<c>equery</c> is a tool that displays a great deal of useful information "
+"about the packages on your system and much more. <c>equery --help</c> gives "
+"you the full set of options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):121
+msgid ""
+"Not all features listed by <c>equery --help</c> have been implemented yet. "
+"Those that have not been, are mentioned clearly. You will also see that "
+"every command has a short option, e.g. <c>b</c> instead of <c>belongs</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):127
+msgid ""
+"Be aware that equery currently changes the format of the output if it is "
+"sent through a pipe. The piped format is intended to be easier to parse by "
+"tools, but you can also turn it off by adding the <c>--no-pipe</c> option. "
+"If you write scripts that employ equery, you should be aware of this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):137
+msgid "Finding the Package That a File Came From"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):140
+msgid ""
+"<c>equery</c> also provides the functionality of finding the package that a "
+"file came from, using <c>belongs</c> command (or just <c>b</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):145
+msgid "Finding the ebuild that installed a given file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):145
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery belongs /usr/bin/audacious</i>\n"
+"[ Searching for file(s) /usr/bin/audacious in *... ]\n"
+"media-sound/audacious-1.1.2 (/usr/bin/audacious)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):151
+msgid ""
+"By using the <c>-f</c> option, you may search for packages with files "
+"matching any regular expression. The <c>-e</c> option is useful for "
+"terminating your search immediately when a match is found."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):160
+msgid "Verifying Package Integrity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):163
+msgid ""
+"Sometimes it is useful to check a package's integrity. <c>equery</c> can "
+"verify md5 sums as well as timestamps to indicate when a package might have "
+"been corrupted, replaced, or removed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):169
+msgid "OK package integrity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):169
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery check gentoolkit</i>\n"
+"[ Checking app-portage/gentoolkit-0.2.0 ]\n"
+" * 54 out of 54 files good\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):175
+msgid ""
+"Please note that if you change configuration files after installation, these "
+"may be reported as \"not good\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):183
+msgid "List of all packages depending on ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):186
+msgid ""
+"<c>equery</c> is able to list all direct dependencies matching a package. "
+"The function we should use to do this is <c>depends</c> and it's as easy as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):191
+msgid "Looking for packages depending on pygtk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):191
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery depends pygtk</i>\n"
+"[ Searching for packages depending on pygtk... ]\n"
+"app-office/dia-0.93\n"
+"dev-python/gnome-python-2.0.0-r1\n"
+"gnome-extra/gdesklets-core-0.26.2\n"
+"media-gfx/gimp-2.0.4\n"
+"x11-libs/vte-0.11.11-r1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):204
+msgid "Dependency Graphs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):207
+msgid ""
+"<c>equery</c> is capable of giving us a dependency graph for a specified "
+"package. The dependency graph gives a listing of all the packages that have "
+"direct and indirect dependencies on the package in question."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):213
+msgid "Dependency Graph for cdrtools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):213
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery depgraph cdrtools</i>\n"
+"Displaying dependencies for app-cdr/cdrtools-2.01_alpha37\n"
+"`-- app-cdr/cdrtools-2.01_alpha37\n"
+" `-- sys-libs/glibc-2.3.4.20040808 (virtual/libc)\n"
+"  `-- sys-kernel/linux-headers-2.4.22 (virtual/os-headers)\n"
+"   `-- sys-apps/baselayout-1.10.4\n"
+"    `-- sys-apps/sysvinit-2.85-r1\n"
+"     `-- sys-apps/gawk-3.1.3-r1\n"
+"      `-- sys-apps/util-linux-2.12-r4\n"
+"          `-- sys-apps/sed-4.0.9\n"
+"        `-- sys-libs/ncurses-5.4-r4\n"
+"            `-- sys-apps/pam-login-3.14\n"
+"            `-- sys-libs/pam-0.77-r1\n"
+"                 `-- sys-libs/cracklib-2.7-r10\n"
+"               `-- sys-apps/miscfiles-1.3-r1\n"
+"              `-- app-arch/gzip-1.3.5-r1\n"
+"              `-- sys-apps/portage-2.0.50-r10\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):233
+msgid ""
+"For example, while glibc is a direct dependency for cdrtools,linux-headers "
+"are an indirect dependency. Note that the output also includes information "
+"about virtual packages. In the example above, <c>cdrtools</c> is actually "
+"written to require virtual/libc, not sys-libs/glibc, but on the given system "
+"in the example sys-libs/glibc provides virtual/libc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):244
+msgid "Listing Files Belonging to an Ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):247
+msgid ""
+"<c>equery</c> can list the files that belong to an installed ebuild. If I "
+"don't know the files that Gentoolkit has installed on the system, I will use "
+"<c>equery</c> to show them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):253
+msgid "Listing files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):253
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery files gentoolkit</i>\n"
+"[ Searching for packages matching gentoolkit... ]\n"
+"app-portage/gentoolkit-0.2.0\n"
+"* Contents of app-portage/gentoolkit-0.2.0:\n"
+"/usr\n"
+"/usr/bin\n"
+"/usr/bin/equery\n"
+"/usr/bin/etcat\n"
+"/usr/bin/euse\n"
+"/usr/bin/glsa-check\n"
+"/usr/bin/qpkg\n"
+"/usr/bin/revdep-rebuild\n"
+"/usr/lib\n"
+"/usr/lib/gentoolkit\n"
+"/usr/lib/gentoolkit/pym\n"
+"/usr/lib/gentoolkit/pym/gentoolkit\n"
+"/usr/lib/gentoolkit/pym/gentoolkit/__init__.py\n"
+"/usr/lib/gentoolkit/pym/gentoolkit/gentoolkit.py\n"
+"/usr/lib/gentoolkit/pym/gentoolkit/pprinter.py\n"
+"/usr/lib/gentoolkit/pym/glsa.py\n"
+"/usr/sbin\n"
+"/usr/share\n"
+"/usr/share/doc\n"
+"/usr/share/doc/gentoolkit-0.2.0_pre10\n"
+"\n"
+"[...]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):282
+msgid ""
+"The command <c>files</c> of <c>equery</c> provide some options to modify the "
+"output. You can look them all up in the <c>equery</c> man page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):290
+msgid "Looking for packages that use a specific USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):293
+msgid ""
+"If you want to find which packages on your system that make use of a "
+"specific USE flag, <c>equery</c> has the function <c>hasuse</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):298
+msgid "Searching packages which use the firefox USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):298
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery hasuse firefox</i>\n"
+"[ Searching for USE flag firefox in all categories among: ]\n"
+" * installed packages\n"
+"[I--] [  ] dev-python/gnome-python-extras-2.14.0-r1 (0)\n"
+"[I--] [  ] media-video/totem-2.16.4 (0)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):309
+msgid "Listing Packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):312
+msgid ""
+"<c>equery</c> has a power feature to list packages belonging to our system, "
+"portage or even an overlay. Let's try this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):317
+msgid "Listing packages with equery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):317
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery list gentoolkit</i>\n"
+"[ Searching for package 'gentoolkit' in all categories among: ]\n"
+" * installed packages\n"
+"[I--] [  ] app-portage/gentoolkit-0.2.0 (0)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):324
+msgid ""
+"The standard query will search our installed packages for the name given. If "
+"found, the following info will be displayed: the package location between "
+"the first square brackets (I for Installed packages, P for Portage, O for "
+"Overlay), the possible masks between the second (~ by keyword, - by arch or "
+"M hard masked), then the category and complete name and last of all, the "
+"slot in which the package is stored."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):333
+msgid ""
+"Another example, this time we are going to use the local options in order to "
+"look for packages in our portage tree and overlay."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):338
+msgid "Using local options with equery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):338
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery list -p -o vim</i>\n"
+"[ Searching for package 'vim' in all categories among: ]\n"
+" * installed packages\n"
+"[I--] [  ] app-editors/vim-6.3-r4 (0)\n"
+" * Portage tree (/usr/portage)\n"
+"[-P-] [M~] app-editors/vim-7.0_alpha20050126 (0)\n"
+"[-P-] [M~] app-editors/vim-7.0_alpha20050201 (0)\n"
+"[-P-] [  ] app-editors/vim-6.3-r2 (0)\n"
+"[-P-] [M~] app-editors/vim-7.0_alpha20050122 (0)\n"
+"[-P-] [M~] app-editors/vim-core-7.0_alpha20050126 (0)\n"
+"[-P-] [  ] app-editors/vim-core-6.3-r3 (0)\n"
+"[-P-] [M~] app-editors/vim-core-7.0_alpha20050122 (0)\n"
+"[-P-] [M~] app-editors/vim-core-7.0_alpha20050201 (0)\n"
+"[-P-] [  ] app-editors/vim-core-6.3-r4 (0)\n"
+" * overlay tree (/opt/ebuilds)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):359
+msgid "Finding Package Sizes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):362
+msgid ""
+"Ever been curious to find out how much space a specific package is "
+"occupying? Since a package could have its files over a number of "
+"directories, the usual <c>du -hc</c> might not give you the correct figure. "
+"Not to worry, here comes <c>equery</c> to the rescue!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):369
+msgid "Package Size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):369
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery size openoffice-bin</i>\n"
+"* app-office/openoffice-bin-1.1.2\n"
+"     Total Files : 2908\n"
+"     Total Size  : 223353.31 KiB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):376
+msgid ""
+"As you can see, <c>equery</c> prints the total space used in kilobytes and "
+"also lists the total number of files the package has."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):384
+msgid "Package-wise list of USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):387
+msgid ""
+"<c>equery</c> can be used to give us information about what USE flags are "
+"being used by a specific package. It also tells us what our current USE "
+"flags are for a package and also what USE flags are available for the "
+"package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):393
+msgid "Set and Unset USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):393
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery uses wireshark</i>\n"
+"[ Colour Code : set unset ]\n"
+"[ Legend    : (U) Col 1 - Current USE flags        ]\n"
+"[           : (I) Col 2 - Installed With USE flags ]\n"
+"\n"
+" U I [ Found these USE variables in : net-analyzer/wireshark-0.99.4 ]\n"
+" - - adns      : Adds support for the adns DNS client library\n"
+" + + gtk       : Adds support for x11-libs/gtk+ (The GIMP Toolkit)\n"
+" - - ipv6      : Adds support for IP version 6\n"
+" - - kerberos  : Adds kerberos support\n"
+" - - portaudio : Adds support for the crossplatform portaudio audio API\n"
+" - - selinux   : !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur\n"
+" - - snmp      : Adds support for the Simple Network Management Protocol if available\n"
+" + + ssl       : Adds support for Secure Socket Layer connections\n"
+" - - threads   : Adds threads support for various packages. Usually pthreads\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):411
+msgid ""
+"I have installed wireshark with only the gtk and ssl flags set, but there "
+"are several other USE flags for wireshark still available. For more "
+"information on USE flags, please refer to the <uri link=\"/doc/en/handbook/"
+"handbook-x86.xml?part=2&amp;chap=2\">USE Flags</uri> chapter of the <uri "
+"link=\"/doc/en/handbook/\">Gentoo Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):422
+msgid "Where's the ebuild?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):425
+msgid ""
+"We can also find out which ebuild is being used for a specific package using "
+"<c>equery</c>. This is done by using the <c>equery which</c> command which "
+"displays the full path to the ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):431
+msgid "Displaying the ebuild path"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):431
+#, no-wrap
+msgid ""
+"\n"
+"# <i>equery which cdrtools</i>\n"
+"/usr/portage/app-cdr/cdrtools/cdrtools-2.01_alpha37.ebuild\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):441
+msgid "euse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):446
+msgid ""
+"<c>euse</c> is a tool to see, set and unset USE flags at various places. For "
+"more information on USE flags, please refer to the <uri link=\"/doc/en/"
+"handbook/handbook-x86.xml?part=2&amp;chap=2\">USE Flags</uri>. Please see "
+"<c>euse -h</c> for complete help and all options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):456
+msgid "Viewing, Setting and Unsetting USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):459
+msgid ""
+"The <c>euse -a</c> command reads the current active USE flags and displays "
+"them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):464
+msgid ""
+"There are 5 \"columns\" that <c>euse</c> now uses to show whether a flag is "
+"set/unset and where all the flag has been set. The columns are as follows -- "
+"+/-, set in the Environment, set in make.Conf, set in make.Defaults, and set "
+"in make.Globals. The output looks like [+ECDG]."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):471
+msgid "Viewing all active USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):471
+#, no-wrap
+msgid ""
+"\n"
+"# <i>euse -a</i>\n"
+"X                   [+ CD ]\n"
+"aalib               [+    ]\n"
+"acpi                [+ C  ]\n"
+"alsa                [+ C  ]\n"
+"apache2             [+ C  ]\n"
+"apm                 [+  D ]\n"
+"avi                 [+  D ]\n"
+"berkdb              [+  D ]\n"
+"bitmap-fonts        [+  D ]\n"
+"bonobo              [+    ]\n"
+"cdr                 [+ C  ]\n"
+"crypt               [+ CD ]\n"
+"cscope              [+ C  ]\n"
+"cups                [+ CD ]\n"
+"curl                [+    ]\n"
+"emboss              [+  D ]\n"
+"encode              [+  D ]\n"
+"esd                 [+    ]\n"
+"fam                 [+    ]\n"
+"fbcon               [+ C  ]\n"
+"firefox             [+ C  ]\n"
+"font-server         [+  D ]\n"
+"foomaticdb          [+  D ]\n"
+"fortran             [+  D ]\n"
+"gd                  [+ C  ]\n"
+"gdbm                [+  D ]\n"
+"gif                 [+ CD ]\n"
+"gimpprint           [+ C  ]\n"
+"gnome               [+ CD ]\n"
+"gphoto2             [+    ]\n"
+"gpm                 [+ CD ]\n"
+"gstreamer           [+ C  ]\n"
+"gtk                 [+  D ]\n"
+"gtkhtml             [+ C  ]\n"
+"guile               [+    ]\n"
+"imagemagick         [+    ]\n"
+"imlib               [+ CD ]\n"
+"innodb              [+    ]\n"
+"ipv6                [+  D ]\n"
+"javascript          [+ C  ]\n"
+"jpeg                [+ CD ]\n"
+"kde                 [+  D ]\n"
+"ldap                [+    ]\n"
+"libg++              [+ CD ]\n"
+"libwww              [+ CD ]\n"
+"mad                 [+ CD ]\n"
+"mbox                [+ C  ]\n"
+"md5sum              [+ C  ]\n"
+"mikmod              [+ CD ]\n"
+"mmx                 [+ C  ]\n"
+"motif               [+ CD ]\n"
+"mp3                 [+    ]\n"
+"mpeg                [+ CD ]\n"
+"mpeg4               [+ C  ]\n"
+"mysql               [+ C  ]\n"
+"ncurses             [+ CD ]\n"
+"nls                 [+  D ]\n"
+"nvidia              [+ C  ]\n"
+"odbc                [+    ]\n"
+"offensive           [+    ]\n"
+"ogg                 [+ CD ]\n"
+"opengl              [+ CD ]\n"
+"oss                 [+  D ]\n"
+"pam                 [+ CD ]\n"
+"pdflib              [+ CD ]\n"
+"perl                [+ CD ]\n"
+"png                 [+ CD ]\n"
+"python              [+ CD ]\n"
+"qt                  [+  D ]\n"
+"quicktime           [+ CD ]\n"
+"readline            [+ CD ]\n"
+"ruby                [+    ]\n"
+"sdl                 [+ CD ]\n"
+"slang               [+  D ]\n"
+"spell               [+ CD ]\n"
+"sse                 [+ C  ]\n"
+"ssl                 [+ CD ]\n"
+"svga                [+ CD ]\n"
+"tcltk               [+ C  ]\n"
+"tcpd                [+  D ]\n"
+"tiff                [+ C  ]\n"
+"truetype            [+ CD ]\n"
+"usb                 [+ C  ]\n"
+"vanilla             [+ C  ]\n"
+"x86                 [+ C  ]\n"
+"xml                 [+    ]\n"
+"xosd                [+ C  ]\n"
+"xv                  [+ CD ]\n"
+"xvid                [+ C  ]\n"
+"zlib                [+ CD ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):565
+msgid ""
+"Similarly you can use the <c>euse -a -g</c> command to only view active "
+"global USE flags. The <c>euse -a -l</c> command does the same for active "
+"local USE flags.<c>-g</c> &amp; <c>-l</c> are suboptions to <c>euse</c> and "
+"need an option before them (like <c>-a</c>) to function correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):572
+msgid "Viewing active local USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):572
+#, no-wrap
+msgid ""
+"\n"
+"# <i>euse -a -l</i>\n"
+"bitmap-fonts        [+  D ]\n"
+"font-server         [+  D ]\n"
+"fortran             [+  D ]\n"
+"gimpprint           [+ C  ]\n"
+"md5sum              [+ C  ]\n"
+"mpeg4               [+ C  ]\n"
+"nvidia              [+ C  ]\n"
+"offensive           [+    ]\n"
+"truetype            [+ CD ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):585
+msgid ""
+"We can also use <c>euse</c> to set or unset use flags. The commands used for "
+"this are <c>euse -E flagname</c> (enable a flag) and <c>euse -D flagname</c> "
+"(disable a flag)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(warn):591
+msgid ""
+"Do not use the <c>euse -E</c> or <c>euse -D</c> commands by themselves "
+"(without a flag). It will set/unset ALL USE flags in <c>/etc/make.conf</c>. "
+"Although a backup is kept at <path>/etc/make.conf.euse_backup</path>, please "
+"be careful while using <c>euse -E</c> or <c>euse -D</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):598
+msgid "Setting and Unsetting USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):598
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Enabling a USE Flag)</comment>\n"
+"# <i> euse -E 3dfx</i>\n"
+"/etc/make.conf was modified, a backup copy has been placed at /etc/make.conf.euse_backup\n"
+"\n"
+"<comment>(/etc/make.conf after the command)</comment>\n"
+"USE=\"alsa acpi apache2 -arts cups cdr crypt cscope -doc fbcon \\\n"
+"     firefox gd gif gimpprint gnome gpm gstreamer gtkhtml imlib \\\n"
+"     innodb -java javascript jpeg libg++ libwww mad mbox md5sum \\\n"
+"     mikmod mmx motif mpeg mpeg4 mysql ncurses nvidia \\\n"
+"     ogg odbc offensive opengl pam pdflib perl png python \\\n"
+"     quicktime readline sdl spell sse ssl svga tcltk tiff truetype usb \\\n"
+"     vanilla X xosd xv xvid x86 zlib 3dfx\"\n"
+"\n"
+"<comment>(Disabling the USE Flag)</comment>\n"
+"# <i> euse -D 3dfx</i>\n"
+"/etc/make.conf was modified, a backup copy has been placed at /etc/make.conf.euse_backup\n"
+"\n"
+"<comment>(/etc/make.conf after the command)</comment>\n"
+"USE=\"alsa acpi apache2 -arts cups cdr crypt cscope -doc fbcon \\\n"
+"     firefox gd gif gimpprint gnome gpm gstreamer gtkhtml imlib \\\n"
+"     innodb -java javascript jpeg libg++ libwww mad mbox md5sum \\\n"
+"     mikmod mmx motif mpeg mpeg4 mysql ncurses nvidia \\\n"
+"     ogg odbc offensive opengl pam pdflib perl png python \\\n"
+"     quicktime readline sdl spell sse ssl svga tcltk tiff truetype usb \\\n"
+"     vanilla X xosd xv xvid x86 zlib -3dfx\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):626
+msgid ""
+"<c>euse</c> does not physically remove the flag from make.conf. It just adds "
+"a - (minus) before the flag to unset it. You may have to manually clean up "
+"your make.conf to avoid unwanted variables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):637
+msgid "Other tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):639
+msgid "revdep-rebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):642
+msgid ""
+"This tool is Gentoo's Reverse Dependency rebuilder. It will scan your "
+"installed ebuilds to find packages that have become broken as a result of an "
+"upgrade of a package they depend on. It can emerge those packages for you "
+"but it can also happen that a given package does not work anymore with the "
+"currently installed dependencies, in which case you should upgrade the "
+"broken package to a more recent version. revdep-rebuild will pass flags to "
+"emerge which lets you use the <c>--pretend</c> flag to see what is going to "
+"be emerged again before you go any further."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):653
+msgid "Running revdep-rebuild in pretend mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):653
+#, no-wrap
+msgid ""
+"\n"
+"# <i>revdep-rebuild -p</i>\n"
+"\n"
+"Checking reverse dependencies...\n"
+"Packages containing binaries and libraries broken by any package update,\n"
+"will be recompiled.\n"
+"\n"
+"Collecting system binaries and libraries... done.\n"
+"  (/root/.revdep-rebuild.1_files)\n"
+"\n"
+"Collecting complete LD_LIBRARY_PATH... done.\n"
+"  (/root/.revdep-rebuild.2_ldpath)\n"
+"\n"
+"Checking dynamic linking consistency...\n"
+"  broken /usr/lib/ao/plugins-2/libarts.so (requires libartsc.so.0)\n"
+"  broken /usr/lib/kde3/libkpresenterpart.so (requires libartskde.so.1 libqtmcop.so.1\n"
+"         libsoundserver_idl.so.1 libkmedia2_idl.so.1 libartsflow.so.1 libartsflow_idl.so.1 libmcop.so.1)\n"
+"  broken /usr/lib/ruby/site_ruby/1.8/i686-linux/fox.so (requires libFOX-1.0.so.0)\n"
+"  broken /usr/lib/xine/plugins/1.0.0/xineplug_ao_out_arts.so (requires libartsc.so.0)\n"
+"  broken /usr/lib/perl5/vendor_perl/5.8.0/i686-linux/auto/SDL_perl/SDL_perl.so (requires libSDL_gfx.so.0)\n"
+"  broken /usr/lib/libloudmouth-1.so.0.0.0 (requires libgnutls.so.10)\n"
+"  broken /usr/bin/k3b (requires libartskde.so.1 libqtmcop.so.1 libsoundserver_idl.so.1 libkmedia2_idl.so.1\n"
+"         libartsflow.so.1 libartsflow_idl.so.1 libmcop.so.1)\n"
+"  broken /usr/bin/lua (requires libhistory.so.4)\n"
+"  broken /usr/bin/lyx (requires libAiksaurus-1.0.so.0)\n"
+"  broken /usr/bin/luac (requires libhistory.so.4)\n"
+"  broken /usr/bin/avidemux2 (requires libartsc.so.0)\n"
+"  broken /usr/bin/pptout (requires libxml++-0.1.so.11)\n"
+"  broken /usr/bin/xml2ps (requires libxml++-0.1.so.11)\n"
+" done.\n"
+"  (/root/.revdep-rebuild.3_rebuild)\n"
+"\n"
+"Assigning files to ebuilds... done.\n"
+"  (/root/.revdep-rebuild.4_ebuilds)\n"
+"\n"
+"Evaluating package order... done.\n"
+"  (/root/.revdep-rebuild.5_order)\n"
+"\n"
+"All prepared. Starting rebuild...\n"
+"emerge --oneshot --nodeps -p =app-cdr/k3b-0.11.14 =app-office/koffice-1.3.2 =app-office/lyx-1.3.4 \\\n"
+"       =app-office/passepartout-0.2 =dev-lang/lua-5.0.2 =dev-ruby/fxruby-1.0.29 =media-libs/libao-0.8.5 \\\n"
+"       =media-libs/xine-lib-1_rc5-r3 =media-video/avidemux-2.0.26 =net-libs/loudmouth-0.16\n"
+"\n"
+"These are the packages that I would merge, in order:\n"
+"\n"
+"Calculating dependencies ...done!\n"
+"[ebuild   R   ] app-cdr/k3b-0.11.14\n"
+"[ebuild   R   ] app-office/koffice-1.3.2\n"
+"[ebuild   R   ] app-office/lyx-1.3.4\n"
+"[ebuild   R   ] app-office/passepartout-0.2\n"
+"[ebuild   R   ] dev-lang/lua-5.0.2\n"
+"[ebuild   R   ] dev-ruby/fxruby-1.0.29\n"
+"[ebuild   R   ] media-libs/libao-0.8.5\n"
+"[ebuild   R   ] media-libs/xine-lib-1_rc5-r3\n"
+"[ebuild   R   ] media-video/avidemux-2.0.26\n"
+"[ebuild   R   ] net-libs/loudmouth-0.16\n"
+"\n"
+"Now you can remove -p (or --pretend) from arguments and re-run revdep-rebuild.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):713
+msgid ""
+"If you need to rebuild some packages, you may run <c>revdep-rebuild</c> "
+"without the <c>-p</c> flag and the listed packages will be emerged again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):721
+msgid "glsa-check"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):724
+msgid ""
+"<c>glsa-check</c> is mainly a test tool that keeps track of the various "
+"GLSAs (Gentoo Linux Security Advisory) and will eventually be integrated "
+"into <c>emerge</c> and <c>equery</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):733
+msgid "eread"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):736
+msgid ""
+"<c>eread</c> is a simple utility to display elog files produced by &gt;"
+"=<c>portage-2.1</c>. You can set the saving of elog files by setting a "
+"couple of variables in <path>/etc/make.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):742
+msgid "Enabling elog in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):742
+#, no-wrap
+msgid ""
+"\n"
+"PORTAGE_ELOG_CLASSES=\"log\"\n"
+"PORTAGE_ELOG_SYSTEM=\"save\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(note):747
+msgid ""
+"This is just one way of saving elog messages. For more information on how "
+"Portage's elog system works, please refer to the appropriate page in the "
+"<uri link=\"/doc/en/handbook/handbook-x86.xml?part=3&amp;"
+"chap=1#doc_chap4\">Portage Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):754
+msgid ""
+"Once you've set up elog to your satisfaction, just run <c>eread</c> to view "
+"your log files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre:caption):759
+msgid "Using eread"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(pre):759
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>eread</i>\n"
+"\n"
+"This is a list of portage log items. Choose a number to view that file or type\n"
+"q to quit.\n"
+"\n"
+"1) app-portage:gentoolkit-0.2.4_pre2:20070320-000256.log\n"
+"2) app-portage:gentoolkit-0.2.4_pre2:20070320-000258.log\n"
+"3) app-portage:gentoolkit-0.2.4_pre2:20070320-000319.log\n"
+"4) app-portage:gentoolkit-0.2.3:20070320-000408.log\n"
+"Choice?\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):772
+msgid ""
+"Select a number and the file will be displayed using the paging program "
+"specified in the PAGER environment variable. If PAGER is not set, it will "
+"use <c>less</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):778
+msgid ""
+"After displaying the elog item, you will be prompted if you want to delete "
+"the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(title):786
+msgid "eclean"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):789
+msgid ""
+"<c>eclean</c> is a tool to remove old source files and old binary packages "
+"from your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):794
+msgid ""
+"When you build and install packages, the source files are downloaded and "
+"preserved in DISTDIR, usually <path>/usr/portage/distfiles</path>. This can "
+"accumulate several gigs of material over time if you don't clean it "
+"periodically. You can run <c>eclean-dist</c> to clean only source files from "
+"DISTDIR."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):802
+msgid ""
+"You can create archives of installed packages by using <c>quickpg</c> or "
+"FEATURES=\"buildpkg\". These archived packages are kept in PKGDIR, usually "
+"<path>/usr/portage/packages</path>. When you no longer need to keep them "
+"around, or if they're too old, you can run <c>eclean-pkg</c> to remove them "
+"from PKGDIR. It's a good way to ensure that any binary packages you have are "
+"only the latest versions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(p):811
+msgid ""
+"For more information on <c>eclean</c> and tips on maintaining a cruft-free "
+"system, please read <c>man eclean</c>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gentoolkit.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gnome-config.xml.po b/doc/gettext/ru/gnome-config.xml.po
new file mode 100644
index 0000000..b6298d8
--- /dev/null
+++ b/doc/gettext/ru/gnome-config.xml.po
@@ -0,0 +1,349 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):6
+msgid "The GNOME Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail:link):12
+msgid "lars@strojny.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail):12
+msgid "Lars Strojny"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(abstract):18
+msgid ""
+"A frequently used environment is GNOME. This HOWTO tries to describe all "
+"aspects of GNOME, including installation, configuration, usage, ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(version):27
+msgid "1.24"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(date):28
+msgid "2010-06-07"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):31
+msgid "What is GNOME?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):33
+msgid "The Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):36
+msgid ""
+"The <uri link=\"http://www.gnome.org\">GNOME</uri> project is a free "
+"software project dedicated to the development of GNOME, a Unix/Linux desktop "
+"suite and development platform. The <uri link=\"http://foundation.gnome.org"
+"\">GNOME Foundation</uri> coordinates the development and other aspects of "
+"the GNOME Project."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):47
+msgid "The Software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):50
+msgid ""
+"GNOME is a desktop environment and a development platform. This piece of "
+"free software is the desktop of choice for several industry leaders. It is "
+"interesting both for business users, home users as well as developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):59
+msgid "The Community"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):62
+msgid ""
+"Like with any big free software project, GNOME has an extensive user- and "
+"development base. <uri link=\"http://www.gnomedesktop.org\">Footnotes</uri> "
+"contains GNOME Desktop news for users; <uri link=\"http://planet.gnome.org"
+"\">GnomePlanet</uri> is for hackers/contributors and <uri link=\"http://"
+"developer.gnome.org\">Developer.Gnome.Org</uri> is for the GNOME developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):75
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):113
+msgid "Installing GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):77
+msgid "What do you need?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(impo):80
+msgid ""
+"First read and follow the instructions in the <uri link=\"/doc/en/xorg-"
+"config.xml\">X Server Configuration Howto</uri> to setup your X environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):86
+msgid ""
+"Before you start installing GNOME, you might want to edit your USE "
+"variables. Make sure that <c>X</c>, <c>gtk</c>, and <c>gnome</c> are in your "
+"USE variable listed in <path>/etc/make.conf</path>. If you want support for "
+"<c>hald</c>, the hardware abstraction layer daemon add <c>hal</c> to your "
+"USE flags. The same goes for <c>dbus</c>, a system message bus Gnome uses "
+"extensively. If you don't want KDE support (the other big desktop "
+"environment), remove <c>qt4</c> and <c>kde</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):96
+msgid "Example USE in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):96
+#, no-wrap
+msgid ""
+"\n"
+"USE=\"-qt4 -kde X dbus gtk gnome hal\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):100
+msgid ""
+"You can add the <c>branding</c> USE flag to get a lovely Gentoo-branded "
+"splashscreen instead of the default Gnome splashscreen:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):105
+msgid "Enabling Gentoo branding"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):105
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"gnome-base/gnome-session branding\" &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):109
+msgid "Once done, start installing GNOME by emerging <c>gnome</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):113
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gnome</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):117
+msgid ""
+"You can also opt for a minimal Gnome installation using <c>gnome-light</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):121
+msgid "Installing a minimal GNOME environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):121
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gnome-light</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):125
+msgid ""
+"This will take a while, so you might want to start reading all those books "
+"your mother bought you but you never opened. Done? Great, now update your "
+"environment variables:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):131
+msgid "Updating environment variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):131
+#, no-wrap
+msgid ""
+"\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):135
+msgid "Next we'll clean up the remaining services."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):139
+msgid "Adding hald and dbus to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):139
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/hald start</i>\n"
+"# <i>rc-update add hald default</i>\n"
+"\n"
+"# <i>/etc/init.d/dbus start</i>\n"
+"# <i>rc-update add dbus default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):150
+msgid "First Impressions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):153
+msgid ""
+"Let us first take a look at what we just built. Exit your root shell and log "
+"on as a regular user. We will configure our session to run GNOME when we "
+"issue the <c>startx</c> command (see also <uri link=\"/doc/en/xorg-config."
+"xml#using_startx\">Using startx</uri> in the <uri link=\"/doc/en/xorg-config."
+"xml\">X Server Configuration Howto</uri>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):161
+msgid "Having GNOME as default desktop environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):161
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>echo \"exec gnome-session\" &gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):165
+msgid ""
+"Starting with <c>gnome-base/gnome-session-2.26.2</c>, you will need to "
+"prepend the XDG_MENU_PREFIX variable to get the Gnome menus if you're using "
+"the <path>~/.xinitrc</path> method to start your desktop. (If you're not "
+"using <path>~/.xinitrc</path>, it will be handled automatically for you; no "
+"additional configuration is needed.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):173
+msgid "Prepending XDG_MENU_PREFIX to ~/.xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):173
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>sed -i '1i\\export XDG_MENU_PREFIX=gnome-' ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):177
+msgid "Now start your graphical environment by running <c>startx</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):181
+msgid "Starting GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):181
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>startx</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):185
+msgid ""
+"If all goes well, you should be greeted by GNOME. Congratulations. Now let "
+"us take a look at how you can configure GNOME to suit your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):194
+msgid "Configuring GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):196
+msgid "GNOME's Graphical Login Manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):199
+msgid ""
+"If you want the GNOME Display Manager (GDM) to run automatically when you "
+"boot (so you can log on graphically), you must add the <c>xdm</c> init "
+"script to the default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):205
+msgid "Adding xdm to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):205
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add xdm default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):209
+msgid ""
+"Now edit <path>/etc/conf.d/xdm</path> and alter the DISPLAYMANAGER variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):213
+msgid "Editing /etc/conf.d/xdm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):213
+#, no-wrap
+msgid ""
+"\n"
+"DISPLAYMANAGER=\"gdm\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):217
+msgid ""
+"If you reboot now, the GNOME Display Manager will prompt you for your "
+"username and password and will default to using GNOME as Desktop Environment "
+"(even though you will have the option of selecting a different one of "
+"course, choosing from those available in <path>/usr/share/xsessions/</"
+"path>). Thus, if you use GDM, you don't need to edit <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):225
+msgid ""
+"To use the functionality of <c>hald</c> you need to add your user to the "
+"<c>plugdev</c> group. If you want support for devices not handled by the "
+"<c>nautilus</c> file manager, or if you're not using <c>nautilus</c> at all, "
+"you might want to make sure that <c>gnome-volume-manager</c> is built with "
+"the <c>automount</c> USE flag, and that it's started every time you login."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gnupg-user.xml.po b/doc/gettext/ru/gnupg-user.xml.po
new file mode 100644
index 0000000..f6e2868
--- /dev/null
+++ b/doc/gettext/ru/gnupg-user.xml.po
@@ -0,0 +1,1196 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):6
+msgid "GnuPG Gentoo User Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail:link):9
+msgid "humpback@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail):9
+msgid "Gustavo Felisberto"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail:link):12
+msgid "zhen@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail):12
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail:link):15
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(mail):15
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(abstract):18
+msgid ""
+"This small guide will teach you the basics of using GnuPG, a tool for secure "
+"communication."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(version):27
+msgid "1.13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(date):28
+msgid "2010-06-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):33
+msgid "What you will get in this guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):36
+msgid ""
+"This guide assumes that you are familiar with public-key cryptography, "
+"encryption, and digital signatures. If this is not the case jump to <uri "
+"link=\"#doc_chap6\">Public Key Cryptography</uri> or take a look at the <uri "
+"link=\"http://www.gnupg.org/documentation/guides.html\">GnuPG handbook</"
+"uri>, chapter 2, and then come back."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):44
+msgid ""
+"This guide will teach you how to install GnuPG, how to create your key pair, "
+"how to add keys to your keyring, how to submit your public key to a key "
+"server and how to sign, encrypt, verify or decode messages you send or "
+"receive. You will also learn how to encrypt files on your local computer to "
+"prevent people from reading their contents."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):55
+msgid "Installation of required software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):58
+msgid ""
+"At a very basic level you need to <c>emerge gnupg</c>. Many aplications "
+"today have some sort of support for gpg, so having <e>crypt</e> in your USE "
+"variable is probably a good idea. If you wish to have an email client "
+"capable of using gnupg you can use pine (<c>emerge pinepgp</c>), mutt "
+"(<c>emerge mutt</c>), Mozilla Thunderbird (<c>emerge thunderbird</c>), "
+"evolution (evolution is a GNOME Microsoft Outlook work alike) and KDE's own "
+"KMail (KMail is part of the kdepim package)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):68
+msgid ""
+"<c>Kgpg</c> might interest you if you use KDE. This small program allows you "
+"to generate key pairs, import keys from ASCII files, sign imported keys, "
+"export keys and a few more features."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):79
+msgid "Generating your key and adding keys to your public keyring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):81
+msgid "Creating your key"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):84
+msgid ""
+"To create your key, just run <c>gpg --gen-key</c>. The first time you run "
+"it, it will create some directories; run it again to create the keys:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):89
+msgid "key generation process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):89
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>gpg --gen-key</i>\n"
+"gpg (GnuPG) 1.0.7; Copyright (C) 2002 Free Software Foundation, Inc.\n"
+"This program comes with ABSOLUTELY NO WARRANTY.\n"
+"This is free software, and you are welcome to redistribute it\n"
+"under certain conditions. See the file COPYING for details.\n"
+"\n"
+"Please select what kind of key you want:\n"
+"   (1) DSA and ElGamal (default)\n"
+"   (2) DSA (sign only)\n"
+"   (4) ElGamal (sign and encrypt)\n"
+"   (5) RSA (sign only)\n"
+"   Your selection? <i>1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):104
+msgid ""
+"Here you can choose the type of key you want to use. Most users will go for "
+"the default DSA and ElGamal. Next is the key size - remember that bigger is "
+"better but don't use a size larger than 2048 with DSA/ElGamal keys. "
+"Generally 1024 is more than enough for normal email."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):111
+msgid ""
+"After size comes the expiration date. Here smaller is better, but most users "
+"can go for a key that never expires or to something like 2 or 3 years."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):116
+msgid "Choosing key size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):116
+#, no-wrap
+msgid ""
+"\n"
+"DSA keypair will have 1024 bits.\n"
+"About to generate a new ELG-E keypair.\n"
+"              minimum keysize is  768 bits\n"
+"              default keysize is 1024 bits\n"
+"    highest suggested keysize is 2048 bits\n"
+"    What keysize do you want? (1024) <i>2048</i>\n"
+"Requested keysize is 2048 bits       \n"
+"Please specify how long the key should be valid.\n"
+"         0 = key does not expire\n"
+" &lt;n&gt;= key expires in n days\n"
+" &lt;n&gt;w = key expires in n weeks\n"
+" &lt;n&gt;m = key expires in n months\n"
+" &lt;n&gt;y = key expires in n years\n"
+" Key is valid for? (0) <i>0</i>\n"
+"Key does not expire at all\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):134
+msgid ""
+"Now it is time to enter some personal information about yourself. If you are "
+"going to send your public key to other people you have to use your real "
+"email address here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):140
+msgid "Entering user information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):140
+#, no-wrap
+msgid ""
+"\n"
+"Is this correct (y/n)? <i>y</i>\n"
+"                        \n"
+"You need a User-ID to identify your key; the software constructs the user id\n"
+"from Real Name, Comment and Email Address in this form:\n"
+"\"Heinrich Heine (Der Dichter) &lt;heinrichh@duesseldorf.de&gt;\"\n"
+"\n"
+"Real name: <i>John Doe</i>\n"
+"Email address: <i>john@nowhere.someplace.flick</i>\n"
+"Comment: <i>The Real John Doe</i>\n"
+"You selected this USER-ID:\n"
+"\"John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\"\n"
+"\n"
+"Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? <i>O</i> \n"
+"You need a Passphrase to protect your secret key.    \n"
+"\n"
+"Enter passphrase: \n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):159
+msgid ""
+"Now enter your key passphrase twice. It is a good idea to use a strong "
+"password. If someone ever gets hold of your private key and cracks your "
+"password, they will be able to send messages signed by \"you\", making "
+"everyone believe the mails were sent by you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):166
+msgid ""
+"Next, GnuPG will generate your key. Moving the mouse or having a mp3 playing "
+"in the background will help speed up the process because it generates random "
+"data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):174
+msgid "Generating a revocation certificate"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(impo):177
+msgid "This part is very important and you must do it <e>NOW</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):181
+msgid ""
+"After creating your keys you should create a revocation certificate. Doing "
+"this allows you to revoke your key in case something nasty happens to your "
+"key (someone gets hold of your key/passphrase)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):187
+msgid "Generating revoke certificate"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):187
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>gpg --list-keys</i>\n"
+"/home/humpback/.gnupg/pubring.gpg\n"
+"---------------------------------\n"
+"pub  1024D/75447B14 2002-12-08 John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\n"
+"sub  2048g/96D6CDAD 2002-12-08\n"
+"\n"
+"$ <i>gpg --output revoke.asc --gen-revoke 75447B14</i>\n"
+"\n"
+"sec  1024D/75447B14 2002-12-08   John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\n"
+"\n"
+"Create a revocation certificate for this key? <i>y</i>\n"
+"Please select the reason for the revocation:   \n"
+"  0 = No reason specified\n"
+"  1 = Key has been compromised\n"
+"  2 = Key is superseded\n"
+"  3 = Key is no longer used\n"
+"  Q = Cancel\n"
+"(Probably you want to select 1 here)\n"
+"Your decision? <i>1</i>\n"
+"Enter an optional description; end it with an empty line:\n"
+"&gt; <i>Someone cracked me and got my key and passphrase</i>\n"
+"&gt;\n"
+"Reason for revocation: Key has been compromised\n"
+"Someone cracked me and got my key and passphrase\n"
+"Is this okay? <i>y</i>\n"
+"\n"
+"You need a passphrase to unlock the secret key for\n"
+"user: \"John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\"\n"
+"1024-bit DSA key, ID 75447B14, created 2002-12-08\n"
+"\n"
+"ASCII armored output forced.\n"
+"Revocation certificate created.\n"
+"\n"
+"Please move it to a medium which you can hide away; if Mallory gets\n"
+"access to this certificate he can use it to make your key unusable.\n"
+"It is smart to print this certificate and store it away, just in case\n"
+"your media become unreadable.  But have some caution:  The print system of\n"
+"your machine might store the data and make it available to others!\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):228
+msgid ""
+"The <c>gpg --list-keys</c> command lists keys in your public keyring. You "
+"may use it to see the ID of your key so that you can create the revocation "
+"certificate. Now it is a good idea to copy all the .gnupg directory and the "
+"revocation certificate (in ASCII armor - <path>revoke.asc</path>) to some "
+"secure medium (two floppy's or a CD-R you store in safe location). Remember "
+"that <path>revoke.asc</path> can be used to revoke your keys and make them "
+"unusable in the future."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(note):238
+msgid ""
+"If you have several email addresses that you would like to use with this "
+"key, you can run <c>gpg --edit-key YOUR_ID</c> and then use the <c>adduid</"
+"c> command. It will ask you for the name, email and comment of the second ID "
+"you will be using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):248
+msgid "Exporting keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):251
+msgid ""
+"To export your key, you type <c>gpg --armor --output john.asc --export "
+"john@nowhere.someplace.flick</c>. You can almost always use the key ID or "
+"something that identifies the key (here we used an email address). John now "
+"has a <path>john.asc</path> that he can send his friends, or place on his "
+"web page so that people can communicate safely with him."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):262
+msgid "Importing keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):265
+msgid ""
+"To add files to your public keyring, you must first import it, then check "
+"the key fingerprint. After you have verified the fingerprint you should "
+"validate it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(note):270
+msgid ""
+"You should be careful when verifying keys. This is one of the weak points of "
+"public key cryptography."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):275
+msgid ""
+"Now we will be adding Luis Pinto's (a friend of mine) public key to our "
+"public keyring. After giving him a call and asking him for his key "
+"fingerprint, I compare the fingerprint with the output of the <c>fpr</c> "
+"command. As the key is authentic, I add it to the public keyring. In this "
+"particular case, Luis's key will expire in 2003-12-01 so I am asked if I "
+"want my signature on his key to expire at the same time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):284
+msgid "Importing and signing keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):284
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>gpg --import luis.asc</i>\n"
+"gpg: key 462405BB: public key imported\n"
+"gpg: Total number processed: 1\n"
+"gpg:               imported: 1\n"
+"$ <i>gpg --list-keys</i>\n"
+"/home/humpback/.gnupg/pubring.gpg\n"
+"---------------------------------\n"
+"pub  1024D/75447B14 2002-12-08 John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\n"
+"sub  2048g/96D6CDAD 2002-12-08\n"
+"\n"
+"pub  1024D/462405BB 2002-12-01 Luis Pinto &lt;lmpinto@student.dei.uc.pt&gt;\n"
+"uid                            Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\n"
+"sub  4096g/922175B3 2002-12-01 [expires: 2003-12-01]\n"
+"\n"
+"$ <i>gpg --edit-key lmpinto@dei.uc.pt</i>\n"
+"gpg (GnuPG) 1.0.7; Copyright (C) 2002 Free Software Foundation, Inc.\n"
+"This program comes with ABSOLUTELY NO WARRANTY.\n"
+"This is free software, and you are welcome to redistribute it\n"
+"under certain conditions. See the file COPYING for details.\n"
+"\n"
+"\n"
+"gpg: checking the trustdb\n"
+"gpg: checking at depth 0 signed=0 ot(-/q/n/m/f/u)=0/0/0/0/0/1\n"
+"pub  1024D/462405BB  created: 2002-12-01 expires: 2003-12-01 trust: -/-\n"
+"sub  4096g/922175B3  created: 2002-12-01 expires: 2003-12-01\n"
+"(1)  Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\n"
+"(2). Luis Pinto &lt;lmpinto@student.dei.uc.pt&gt;\n"
+"\n"
+"Command&gt; <i>fpr</i>\n"
+"pub  1024D/462405BB 2002-12-01 Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\n"
+"             Fingerprint: F056 3697 ADE3 CF98 B80B  8494 0AD3 E57B 4624 05BB\n"
+"     \n"
+"Command&gt; <i>sign</i>\n"
+"Really sign all user IDs? <i>y</i>\n"
+"                           \n"
+"pub  1024D/462405BB  created: 2002-12-01 expires: 2003-12-01 trust: -/-\n"
+"             Fingerprint: F056 3697 ADE3 CF98 B80B  8494 0AD3 E57B 4624 05BB\n"
+"\n"
+"     Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\n"
+"     Luis Pinto &lt;lmpinto@student.dei.uc.pt&gt;\n"
+"\n"
+"This key is due to expire on 2003-12-01.\n"
+"Do you want your signature to expire at the same time? (Y/n) <i>Y</i>\n"
+"How carefully have you verified the key you are about to sign actually belongs\n"
+"to the person named above?  If you don't know what to answer, enter \"0\".\n"
+"\n"
+"   (0) I will not answer. (default)\n"
+"   (1) I have not checked at all.\n"
+"   (2) I have done casual checking.\n"
+"   (3) I have done very careful checking.\n"
+"\n"
+"   Your selection? <i>3</i>\n"
+"Are you really sure that you want to sign this key\n"
+"with your key: \"John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\"\n"
+"\n"
+"I have checked this key very carefully.\n"
+"\n"
+"Really sign? <i>y</i>\n"
+"              \n"
+"You need a passphrase to unlock the secret key for\n"
+"user: \"John Doe (The Real John Doe) &lt;john@nowhere.someplace.flick&gt;\"\n"
+"1024-bit DSA key, ID 75447B14, created 2002-12-08\n"
+"\n"
+"Command&gt; <i>check</i>\n"
+"uid  Luis Pinto &lt;lmpinto@dei.uc.pt&gt;\n"
+"sig!3       462405BB 2002-12-01   [self-signature]\n"
+"sig!3       75447B14 2002-12-08   John Doe (The Real John Doe) &lt;john@nowhe\n"
+"uid  Luis Pinto &lt;lmpinto@student.dei.uc.pt&gt;\n"
+"sig!3       462405BB 2002-12-01   [self-signature]\n"
+"sig!3       75447B14 2002-12-08   John Doe (The Real John Doe) &lt;john@nowhe\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):362
+msgid "Exchanging keys with keyservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):364
+msgid "Sending keys to keyservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):367
+msgid ""
+"Now that you have your key, it is probably a good idea to send it to the "
+"world key server. There are a lot of keyservers in the world and most of "
+"them exchange keys between them. Here we are going to send John Doe's key to "
+"the subkeys.pgp.net server. This uses HTTP, so if you need to use a proxy "
+"for HTTP traffic don't forget to set it (<c>export http_proxy=http://"
+"proxy_host:port/</c>). The command for sending the key is: <c>gpg --"
+"keyserver subkeys.pgp.net --keyserver-options honor-http-proxy --send-key "
+"75447B14</c> where <c>75447B14</c> is the key ID. If you don't need a HTTP "
+"proxy you can remove the <e>--keyserver-options honor-http-proxy</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):379
+msgid ""
+"You can also send other people's keys that you have signed to the keyserver. "
+"We could send Luis Pinto's key to the keyserver. This way someone who trusts "
+"your key can use the signature that you have placed there to trust Luis's "
+"key."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):388
+msgid "Getting Keys from keyservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):391
+msgid ""
+"Now we are going to search for Gustavo Felisberto's key and add it to the "
+"keyring of John Doe (just in case you did not notice Gustavo Felisberto is "
+"the author this guide :))."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):397
+msgid "Searching keys from keyservers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):397
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>gpg --keyserver subkeys.pgp.net --keyserver-options honor-http-proxy --search-keys humpback@felisberto.net</i>\n"
+"gpg: searching for \"humpback@felisberto.net\" from HKP server subkeys.pgp.net\n"
+"Keys 1-5 of 5 for \"humpback@felisberto.net\"\n"
+"(1)Gustavo Felisberto (apt-get install anarchy) &lt;humpback@felisberto.net&gt; 1024\n"
+"  created 2002-12-06, key B9F2D52A\n"
+"(2)Gustavo Felisberto &lt;humpback@altavista.net&gt; 1024\n"
+"  created 1999-08-03, key E97E0B46\n"
+"(3)Gustavo A.S.R. Felisberto &lt;humpback@altavista.net&gt; 1024\n"
+"  created 1998-12-10, key B59AB043\n"
+"(4)Gustavo Adolfo Silva Ribeiro Felisberto &lt;humpback@altavista.net&gt; 1024\n"
+"  created 1998-08-26, key 39EB133D\n"
+"(5)Gustavo Adolfo Silva Ribeiro Felisberto &lt;humpback@altavista.net&gt; 1024\n"
+"  created 1998-06-14, key AE02AF87\n"
+"  Enter number(s), N)ext, or Q)uit &gt;<i>1</i>\n"
+"gpg: requesting key B9F2D52A from HKP keyserver subkeys.pgp.net\n"
+"gpg: key B9F2D52A: public key imported\n"
+"gpg: Total number processed: 1\n"
+"gpg:               imported: 1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):418
+msgid ""
+"As you can see from the server response I have a few keys submitted to the "
+"key server, but I currently only use <e>B9F2D52A</e>. Now John Doe can get "
+"it and sign it if he trusts it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):429
+msgid "Using a GPG Agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):431
+msgid "What is a GPG Agent?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):434
+msgid ""
+"Sometimes working with certain applications requires you to use your GPG key "
+"very frequently, which means that you have to type your passphrase a lot of "
+"times. Several applications used to support a passphrase caching mechanism "
+"to make life easier for users. However, this disallowed sharing this cache "
+"across programs (how secure would that be?) and forced applications to "
+"reinvent the wheel over and over again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):443
+msgid ""
+"A GPG agent is a separate application that GPG uses to cache the passphrase "
+"in a standard and secure way. It allows applications to use GPG "
+"concurrently: if you enter your passphrase while working in one application, "
+"the other application can work with GPG without reiterating the request for "
+"the passphrase to unlock the key - if the GPG agent is configured to allow "
+"so, of course."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):452
+msgid ""
+"Gentoo provides a few GPG agent applications. The <c>app-crypt/gnupg-1.9.*</"
+"c> package contains what could be considered the reference one, and will be "
+"the one we'll use in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):461
+msgid "Installing and Configuring gpg-agent and pinentry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):464
+msgid ""
+"You should install <c>gnupg-1.9.*</c>, which includes <c>gpg-agent</c>, and "
+"<c>pinentry</c>. <c>pinentry</c> is the helper application that gpg-agent "
+"uses to request the passphrase in a graphical window. It comes in three "
+"flavors: it can popup a window using the gtk+, Qt, or curses library "
+"(depending on the USE flag you set when emerging it)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):472
+msgid "Installing gpg-agent and pinentry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):472
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge \\&gt;=gnupg-1.9.20 pinentry</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):476
+msgid ""
+"Next, create a file called <path>~/.gnupg/gpg-agent.conf</path> and enter "
+"the following lines which define the default timeout of the passphrase (e.g. "
+"30 minutes) and the application to be called for when the passphrase should "
+"be retrieved the first time (e.g. the Qt version of pinentry)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):483
+msgid "Editing ~/.gnupg/gpg-agent.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):483
+#, no-wrap
+msgid ""
+"\n"
+"pinentry-program /usr/bin/pinentry-qt\n"
+"no-grab\n"
+"default-cache-ttl 1800\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):489
+msgid ""
+"Now configure GnuPG to use an agent when appropriate. Edit <path>~/.gnupg/"
+"gpg.conf</path> and add the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):494
+msgid "Configuring GnuPG to use a GPG Agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):494
+#, no-wrap
+msgid ""
+"\n"
+"use-agent\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):498
+msgid "Now your system is (almost) set to use the GPG agent."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):505
+msgid "Automatically Starting the GPG Agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):508
+msgid ""
+"If you use KDE as graphical environment, edit <path>/usr/kde/3.x/env/agent-"
+"startup.sh</path> (system-wide) or <path>~/.kde/env/gpgagent.sh</path> "
+"(local user) and add the following command to it to have KDE automatically "
+"starting the GPG agent:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):515
+msgid "Make KDE automatically start the GPG agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):515
+#, no-wrap
+msgid ""
+"\n"
+"eval \"$(gpg-agent --daemon)\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):519
+msgid ""
+"If you use a different graphical environment, put that line (the same one as "
+"mentioned above) in <path>~/.xinitrc</path> (if you use <c>startx</c>) or "
+"<path>~/.xsession</path> (if you use XDM/GDM/KDM/...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):530
+msgid "Working with documents"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):532
+msgid "Encrypting and signing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):535
+msgid ""
+"Let's say that you have a file that you wish to send Luis. You can encrypt "
+"it, sign it, or encrypt it and sign it. Encrypting means that only Luis will "
+"be able to open it. The signature tells Luis that it was really you who "
+"created the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):542
+msgid ""
+"The next three commands will do just that, encrypt, sign and encrypt/sign."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):546
+msgid "Encrypting and Signing files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):546
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>gpg --output doc.gpg --encrypt --recipient lmpinto@dei.uc.pt doc_to_encrypt</i>\n"
+"$ <i>gpg --output doc.gpg --sign --recipient lmpinto@dei.uc.pt doc_to_sign</i>\n"
+"$ <i>gpg --output doc.gpg --encrypt --sign --recipient lmpinto@dei.uc.pt doc_to_encrypt_and_sign</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):552
+msgid ""
+"This will create binary files. If you wish to create ASCII files, just add a "
+"<c>--clearsign</c> to the beginning of the command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):560
+msgid "Decrypting and verifying signatures"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):563
+msgid ""
+"Suppose that you have received a file which is encrypted to you. The command "
+"to decrypt it is <c>gpg --output document --decrypt encrypted_doc.gpg</c>. "
+"This will decrypt the document and verify the signature (if there is one)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):572
+msgid "Encrypting and decrypting without keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):575
+msgid ""
+"It is also possible to encrypt files using passwords instead of keys. Well, "
+"the password itself will function as the key - it will be used as a "
+"<e>symmetric cypher</e>. You can encrypt the file using <c>gpg</c>'s <c>--"
+"symmetric</c> argument; decrypting uses the same command as we talked about "
+"before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):582
+msgid "Encrypting files using a password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):582
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>gpg --output document.gpg --symmetric document</i>\n"
+"<comment>(GnuPG will ask for a passphrase and a passphrase verification)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):590
+msgid "Advanced Features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):593
+msgid ""
+"There are some nice advanced features in GnuPG. To find them, open the "
+"<path>~/.gnupg/gpg.conf</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):598
+msgid "~/.gnupg/gpg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):598
+#, no-wrap
+msgid ""
+"\n"
+"#keyserver x-hkp://subkeys.pgp.net\n"
+"#keyserver-options auto-key-retrieve include-disabled include-revoked\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):603
+msgid ""
+"Search for the above two lines and uncomment them. With this any time GnuPG "
+"needs to check a signature and it does not find the public key on the local "
+"keyring it will contact the key server at <uri link=\"http://subkeys.pgp."
+"net:11371/\">subkeys.pgp.net</uri> and will try to fetch it from there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):611
+msgid ""
+"Another nice command is <c>gpg --refresh-keys</c>. This will contact the "
+"keyserver defined in the options file and refresh public keys in your local "
+"key ring from there, searching for revoked keys, new IDs, and new signatures "
+"on keys. You should probably run this once or twice a month so that if "
+"someone revokes his key you will be notified."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):624
+msgid "GnuPG interfaces"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):626
+msgid "About email signatures"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):629
+msgid ""
+"95% of the time you will use GnuPG with email, signing/encrypting your "
+"outgoing messages and reading signed/encrypted messages. So it is only fair "
+"that I talk about that first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):635
+msgid ""
+"There are two ways two sign/encrypt a email with GnuPG, the old way and the "
+"new way :). In the old way messages would appear in plain text, with no "
+"possible formatting and attached files would be unsigned/unencrypted. Here "
+"is an example of a message signed the old way:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):642
+msgid "A plain text signature"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):642
+#, no-wrap
+msgid ""
+"\n"
+"-----BEGIN PGP SIGNED MESSAGE-----\n"
+"Hash: SHA1\n"
+"\n"
+"Test message\n"
+"\n"
+"-----BEGIN PGP SIGNATURE-----\n"
+"Version: PGPfreeware 6.5.8 for non-commercial use\n"
+"\n"
+"iQA/AwUBP8461jMX0745gR7AEQIEOwCg011GbufXO3ED3FkLWXmfzg7xm1cAoJD0\n"
+"0EU3Kd2EKNCqataEqM5qjpPs\n"
+"=LchZ\n"
+"-----END PGP SIGNATURE-----\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):657
+msgid ""
+"Messages this way are no good in today's world, where we have nice GUIs and "
+"email readers that understand html."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):662
+msgid ""
+"To solve this an addition to the MIME (Multipurpose Internet Mail "
+"Extensions) was created. This adds a field to the email that tells the mail "
+"reader that the full content of the message is signed and/or encrypted. The "
+"problem with this is that not all mail readers support this. And some even "
+"mess up the content; Microsoft's Outlook is famous for not working with this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):673
+msgid "Kgpg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):676
+msgid ""
+"Kgpg is a nice GUI for GnuPG. In the main screen you can paste the text that "
+"you wish to sign or encrypt, and you can also paste the ASCII armored text "
+"that you which to decrypt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(figure:link):682
+msgid "/images/kgpg1.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(figure:short):682
+msgid "kgpg main window"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):684
+msgid ""
+"In this image you can see the Kgpg main window with ASCII armored and "
+"encrypted text pasted into it. From here you can decrypt it (you will have "
+"to provide your password), encrypt other files, paste new text to sign...."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(figure:link):690
+msgid "/images/kgpg2.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(figure:short):690
+msgid "kgpg key manage window"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):692
+msgid ""
+"Now you can see the key managing window. From here we see our good key for "
+"John Doe. The two trusted keys for Gustavo and Luis, and the untrusted key "
+"for Daniel Robbins (I still have not given him a call to check his "
+"fingerprint :))."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):701
+msgid "Seahorse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):704
+msgid ""
+"Seahorse aims to be a GnuPG GUI interface for the Gnome desktop. The "
+"software has been evolving fast, but it still lacks many important features "
+"that can be found in Kgpg or the command line version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):713
+msgid "Enigmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):716
+msgid ""
+"Enigmail is a plug-in for Mozilla-based email clients (such as Thunderbird "
+"and Seamonkey) that is pretty simple to configure. In Seamonkey, you just go "
+"to Preferences -&gt; Privacy &amp; Security -&gt; Enigmail. There you enter "
+"your key email and that's it. You must first <c>emerge enigmail</c> to use "
+"it with Thunderbird. Then you can configure it by going to Edit -&gt; "
+"Account Settings -&gt; OpenPGP Security."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):725
+msgid ""
+"Mails that come with an untrusted pgp or gpg signature will be marked with a "
+"broken pen. Others that have good signatures will appear with a nice "
+"straight pen. Enigmail even comes with the ability to get keys from "
+"keyservers, but if it has problems it will print some very weird messages "
+"(but you still remember how to use the command line, right?)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):736
+msgid "KMail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):739
+msgid ""
+"If you have the <c>crypt</c> USE flag set, KMail will be compiled with gpg "
+"support, and will be able to encrypt and decrypt inline PGP mails "
+"automatically as well as encrypting OpenPGP/MIME mails. If you want to "
+"decrypt OpenPGP/MIME mails as well (which you probably want) you need to "
+"have a running GPG agent (see <uri link=\"#gpg-agent\">Using a GPG Agent</"
+"uri>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):747
+msgid ""
+"You can verify if KMail is properly configured by going to <c>Settings</c>, "
+"<c>Configure KMail</c>, <c>Security</c>, <c>Crypto Backends</c>. You should "
+"see a GpgME-based backend listed and you should be able to fill the OpenPGP "
+"checkbox. If it is listed but grayed out, click on <c>Rescan</c>. If the "
+"GpgME-based backend remains grayed out, KMail is not working properly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):755
+msgid ""
+"If you still are unable to get KMail to behave, please see the <uri link="
+"\"http://kmail.kde.org/kmail-pgpmime-howto.html\">KMail PGP HowTo</uri> page "
+"for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):764
+msgid "Claws-Mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):767
+msgid ""
+"This mail reader is <e>very</e> fast with big mailboxes, has all the nice "
+"features one wants in mail readers and works pretty well with gpg. The only "
+"problem is that it does not work with the old PGP signatures, so when you "
+"receive those kind of mails you have to hand check the signatures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):774
+msgid ""
+"To use your gpg key with Claws-Mail just go to the account configuration and "
+"select the privacy tab. Once there just choose which key to use, probably "
+"most users will go with the default key."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):785
+msgid "Public Key Cryptography"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):787
+msgid "Basic Public Key Cryptography"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):790
+msgid ""
+"The concept of public key cryptography was originally devised by Whitfield "
+"Diffie and Martin Hellman in 1976. When I first heard the words \"public key"
+"\" and \"cryptography\" in the same sentence back in '93 I thought to myself "
+"that it would be impossible to do such a thing. In those days there was no "
+"Internet (well there was, but not for me) so I went to the public library "
+"and asked for books on Cryptography. I must say that I was 16 at the time so "
+"the clerk there looked to me in astonishment and brought me a book for "
+"children on substitution cyphers (those where you change a letter for "
+"another like the famous Caesar Cypher or ROT-13 (Tragbb Ebpxf, naq lbh xabj "
+"vg vf tbbq orpnhfr lbh ner ernqvat guvf qbp.), (<c>emerge rotix</c> if you "
+"cannot read the preceding text)). I was very upset with this and started to "
+"search for more info. It is good to have mathematicians in the family, "
+"because as soon as I talked to one of them I was introduced to a new world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):806
+msgid "And now a bit of mathematics:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre:caption):810
+msgid "Mathematical Concepts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(pre):810
+#, no-wrap
+msgid ""
+"\n"
+"Definitions:\n"
+"\n"
+"1- A prime number is a positive integer number greater than one that is only\n"
+"divisible by 1 and itself (the remainder of the division is 0).\n"
+"The first 8 prime numbers are 2,3,5,7,11,13,17,19\n"
+"\n"
+"Theorem (No proof here)\n"
+"1- For any non prime positive integer it is possible to break it as the product\n"
+"of prime numbers, and that product is unique.\n"
+"4=2*2\n"
+"6=2*3\n"
+"8=2*4=2*2*2\n"
+"10=2*5\n"
+"12=2*6=2*2*3\n"
+"\n"
+"\"Facts\":\n"
+"1- It is mathematically easy to multiply two large integers\n"
+"2- It is hard to find the prime factors of a given positive integer.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):831
+msgid ""
+"If I give you the number 35 and I tell you that this number is the product "
+"of two prime numbers it is easy to find that it was 5 and 7. But if I tell "
+"you the same for 1588522601 you will spend alot of time (or CPU cycles) to "
+"find it was 49811*31891. And if this number is really really big this task "
+"becomes \"impossible\". So now if I give the world my large number that is "
+"the product of two primes I know something about that number that no one "
+"else knows."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):840
+msgid ""
+"This is the basis for Public Key Cryptography (PKC) implementations today. "
+"As an (unrealistic) example, I give anyone my number and that someone will "
+"use if for cyphering a message to me. Anyone can see the cyphered message, "
+"because I am the only one who knows a shortcut to read it, anyone else will "
+"first have to \"split\" that big number to be able to read the message, and "
+"it is a \"fact\" that it is impossible to do that in a short amount of time "
+"(todays methods and the fastest computers in the world would take thousands "
+"of years to do that). In this setup the two large prime numbers would be "
+"called the PRIVATE KEY, and the large non prime number is the PUBLIC KEY."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):852
+msgid ""
+"In practice this is not 100% accurate with reality, but will give a good "
+"idea to the newcomer. For more information, check Wikipedia on the <uri link="
+"\"http://en.wikipedia.org/wiki/Diffie-Hellman\">Diffie-Hellman</uri> "
+"protocol. For even more info go to the public library and grab a copy of the "
+"<uri link=\"http://www.cacr.math.uwaterloo.ca/hac/\">\"Handbook of Applied "
+"Cryptography\"</uri> by Alfred J. Menezes, Paul C. van Oorschot and Scott A. "
+"Vanstone. This book is also available online for free at the above site."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):862
+msgid ""
+"One consequence of the above is that if you cypher a message to me, and you "
+"loose the original uncyphered message you will no longer be able to retrieve "
+"it from the cyphered version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):871
+msgid "Signatures"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):874
+msgid ""
+"We already saw how someone can send us a cyphered message if they have our "
+"public key. But how do we know that the author of the message is really who "
+"he claims to be? Or in other words: If I receive an email from you how do I "
+"really know it was you and not someone else claiming to be you?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):881
+msgid ""
+"Remember me saying that PKC was not as simple as I had said? The idea is "
+"that when you cypher a message to me you sign it with your private key so "
+"that, when I receive it, I can first use your public key to check your "
+"signature and then use my private key to decypher the message. As you can "
+"see we could not do that in the setup I described before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):889
+msgid ""
+"It's also very important to sign messages so that you don't have to cypher "
+"them beforehand. Now you can create messages that can be read by anyone, but "
+"that come with your \"branding\". And if any single character is changed in "
+"the message it can (and will) be detected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):899
+msgid "Key Servers and Signed Keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):902
+msgid ""
+"But let's say that I have no previous contact with you until you send me a "
+"message: how do I get your public key, and how do I really know it is yours?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):907
+msgid ""
+"To solve this problem public Key Servers were created. When you create your "
+"key pair (Public and Private key), you send your public key to the key "
+"server. After this everyone can retrieve your key from there. This solves "
+"the problem of finding the key. But how do I really know that that key is "
+"the author's key? For this another concept must be introduced, and that is "
+"key signing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):915
+msgid ""
+"Key signing means that if I have the public key of another person, and I "
+"know <e>for sure</e> that it is really that persons key (it is my personal "
+"friend, someone I know in real life, etc.) I can sign that public key and "
+"send it to keyservers, that way I am telling the world: \"This key really "
+"belongs to the person it claims to belong.\". That way persons that have my "
+"public key and trust me can use that trust to trust other keys."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):924
+msgid "This can sometimes be confusing so let's see a real world situation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):928
+msgid ""
+"Let's imagine a 3 person situation: John, Mary, and Lisa. John is a good "
+"friend of Mary but does not know Lisa; Lisa is a good friend of Mary but "
+"does not know John. One day Lisa sends John a signed email. John will fetch "
+"Lisa's Public Key from the keyserver and test the message, if all went ok he "
+"will see that whoever wrote that message also created that key. But how do I "
+"know it was really the person it claims to be?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):937
+msgid ""
+"He then sees that it is signed by Mary, which he can check because he "
+"already has Mary's key and he trusts that key. With this ring of trust he "
+"continues to conclude that the email he received was really written by Lisa."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):943
+msgid ""
+"You are now ready to use this guide, you can go back to chapter 1 and learn "
+"how to use gpg."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):953
+msgid "Final thoughts and Credits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):955
+msgid "Some problems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):958
+msgid ""
+"I had some problems with photos in keys. Check the version you are using. If "
+"you have GnuPG 1.2.1-r1 and up you are probably OK, older versions may have "
+"problems. Also most keyservers don't like keys with photos, so you are "
+"better if you don't add photos."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):965
+msgid ""
+"The latest versions of gnupg don't seem to work with the <c>gpg --send-keys</"
+"c> that was used so send all keys in your keyring to the public server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):974
+msgid "What is not here"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):977
+msgid ""
+"<c>gpg</c> is a very complex tool, it lets you do much more than what I have "
+"covered here. This document is for the user who is new to GnuPG. For more "
+"information, you should check the <uri link=\"http://www.gnupg.org\">GnuPG "
+"Website</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):984
+msgid ""
+"I did not write about other tools like <c>pgp4pine</c>, <c>gpgpine</c>, "
+"<c>evolution</c> and maybe Windows tools, but I will probably extend this "
+"document in the future."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(title):993
+msgid "Credits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):996
+msgid ""
+"John Michael Ashley's <uri link=\"http://www.gnupg.org\">GnuPG Handbook</"
+"uri> it is a very good book for beginners."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):1001
+msgid "Swift (Sven Vermeulen) for pushing me to re-write this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):1005
+msgid "Everyone in the #gentoo-doc team you guys rock."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(p):1009
+msgid "Tiago Serra for getting me back to the privacy track."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gnupg-user.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/gpm.xml.po b/doc/gettext/ru/gpm.xml.po
new file mode 100644
index 0000000..e03f797
--- /dev/null
+++ b/doc/gettext/ru/gpm.xml.po
@@ -0,0 +1,273 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(guide:link):5
+msgid "/doc/en/gpm.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):6
+msgid "Using a Mouse within the Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(mail:link):9
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(mail):9
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(abstract):12
+msgid ""
+"This guide shows you how to set up and use GPM (the General Purpose Mouse "
+"server) from within a command line interface. This is especially useful for "
+"new Gentoo installations or for systems that cannot or do not use an X "
+"server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(version):22
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(date):23
+msgid "2006-02-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):26
+msgid "Getting GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):30
+msgid ""
+"If you've just installed Gentoo, you almost certainly don't have your mouse "
+"set up to work within a command line interface (CLI) yet. Or perhaps you "
+"can't use or don't need an X server, yet you still need to use a mouse. The "
+"solution is simple: <c>gpm</c>, the General Purpose Mouse server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):37
+msgid "First, you will need to get GPM:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):41
+msgid "Obtaining GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):41
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gpm</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):45
+msgid ""
+"You might have noticed a few messages during the compilation that warned "
+"about configuring the server. You must do this before starting GPM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):55
+msgid "Configuring GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):59
+msgid ""
+"Before you can use GPM, you will need to uncomment the lines corresponding "
+"to the location and protocol of your mouse. You do this by editing the GPM "
+"configuration file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):65
+msgid "Setting up GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):65
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/gpm</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):69
+msgid ""
+"In my case, I have a USB mouse on <path>/dev/input/mouse0</path>. So, I have "
+"uncommented <path>/dev/input/mice</path>, as this is the cumulative device "
+"for all mice on the system, and the appropriate protocol. Try using <path>/"
+"dev/input/mice</path> before <path>/dev/psaux</path>, as the latter is "
+"deprecated and can be disabled in the latest 2.6 kernels. If <path>/dev/"
+"input/mice</path> fails, then fall back to other devices. Here is my example "
+"<path>/etc/conf.d/gpm</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):79
+msgid "Example GPM config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):79
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Please uncomment the type of mouse you have and the appropriate MOUSEDEV entry)</comment>\n"
+"\n"
+"#MOUSE=ps2\n"
+"MOUSE=imps2\n"
+"#MOUSEDEV=/dev/psaux\n"
+"MOUSEDEV=/dev/input/mice\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):88
+msgid ""
+"If you have a wheelmouse, you will want to use the imps2 protocol, so "
+"uncomment that line. If imps2 and ps2 both fail to work for you, please "
+"refer to the GPM info page (<c>info gpm</c>) for other protocols to try. "
+"Also, if you want to be able to click on hyperlinks in terminals to navigate "
+"to a website, it is a good idea to follow the suggestion in the <c>/etc/conf."
+"d/gpm</c> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):96
+msgid "Other options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):96
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Please uncomment this line if you want GPM to understand charsets\n"
+"used in URLs and names with ~ or : in them, etc.\n"
+"This is a good idea to turn on!)</comment>\n"
+"\n"
+"APPEND=\"-l \\\"a-zA-Z0-9_.:~/\\300-\\326\\330-\\366\\370-\\377\\\"\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):104
+msgid ""
+"The rest of the conf.d file contains other suggestions for your mouse "
+"server; uncomment the various options according to your needs. See <c>man "
+"gpm</c> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):115
+msgid "Running GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):119
+msgid ""
+"Now that your mouse server is installed and configured, it's time to start "
+"using it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):124
+msgid "The GPM init script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):124
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/gpm start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):128
+msgid ""
+"You should see a block cursor appear. Remember that only root can run the "
+"GPM init script. However, to avoid having to <c>su</c> and run the script "
+"every single time you begin a new session, why not set GPM to begin every "
+"time you turn on your computer?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):135
+msgid "Adding GPM to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):135
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add gpm default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):139
+msgid ""
+"Now, whenever you start your computer, you'll be greeted by the console "
+"cursor by the time you get to the login prompt. The mouse server will "
+"continue to run even if you're not logged in as root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):150
+msgid "Working with GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):152
+msgid "Copying and pasting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):155
+msgid ""
+"Copying and pasting large blocks of text with a working mouse server is very "
+"easy. Simply highlight the text with the left mouse button (it will stay "
+"highlighted when you release the button), switch to a different terminal if "
+"you wish, position the cursor, and press the middle mouse button to paste "
+"the text where you placed the cursor. Note that you can copy and paste "
+"without ever leaving the terminal you started. This makes posting the output "
+"of error messages to the <uri link=\"http://forums.gentoo.org\">Gentoo "
+"Forums</uri> extremely simple."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(title):169
+msgid "Text-mode browsing and GPM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):172
+msgid ""
+"If you have a message on one screen and a text-mode web browser on the "
+"other, you can copy the error message by highlighting it, then change to the "
+"other terminal, left-click the appropriate text entry box to select it, and "
+"then press the middle mouse button. Voilà! Your error message can now be "
+"posted to the forums."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):180
+msgid ""
+"Though discussion of text-only browsers is somewhat beyond the scope of this "
+"guide, inevitably users will need to find a compatible console browser. "
+"Though <c>lynx</c> is most likely the oldest and well established browser, "
+"its interface has poor mouse support and recognition. Instead, try using "
+"<c>links</c> which has excellent mouse integration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre:caption):188
+msgid "Obtaining links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(pre):188
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge links</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(p):192
+msgid ""
+"This concludes the guide to using a mouse within the console. Happy mousing!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gpm.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/grub-error-guide.xml.po b/doc/gettext/ru/grub-error-guide.xml.po
new file mode 100644
index 0000000..cdf37b6
--- /dev/null
+++ b/doc/gettext/ru/grub-error-guide.xml.po
@@ -0,0 +1,842 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(guide:link):5
+msgid "/doc/en/grub-error-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):6
+msgid "Gentoo Grub Error Collection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(author:title):8
+msgid "Thread Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(author):8
+msgid "Hartwig Brandl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(author:title):9
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(author:title):12
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(mail:link):10
+msgid "deathwing00@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(mail):10
+msgid "Ioannis Aslanidis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(mail:link):13
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(mail):13
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(abstract):16
+msgid ""
+"The objective of this error collection is to list the GRUB problems and "
+"errors people can be facing. All these solutions have been acquired through "
+"the cooperation of many users of the Gentoo Forums."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(version):26
+msgid "1.9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(date):27
+msgid "2008-01-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):30
+msgid "Starting notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):33
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):36
+msgid ""
+"Many thanks to <uri link=\"http://forums.gentoo.org/profile.php?"
+"mode=viewprofile&amp;u=18420\">Earthwings</uri>, <uri link=\"http://forums."
+"gentoo.org/profile.php?mode=viewprofile&amp;u=39305\">penetrode</uri>, <uri "
+"link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;"
+"u=41638\">loyaltonone</uri>, <uri link=\"http://forums.gentoo.org/profile."
+"php?mode=viewprofile&amp;u=4980\">pilla</uri>, <uri link=\"http://forums."
+"gentoo.org/profile.php?mode=viewprofile&amp;u=3139\">airhead</uri>, <uri "
+"link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;"
+"u=13816\">nephros</uri>, <uri link=\"http://forums.gentoo.org/profile.php?"
+"mode=viewprofile&amp;u=25859\">yamakawa</uri> and all the others for the "
+"suggestions on the original <uri link=\"http://forums.gentoo.org/viewtopic."
+"php?t=122656\">thread</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):53
+msgid "Disclaimer warning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):56
+msgid ""
+"The examples provided are just examples. Be sure to change partition numbers "
+"and the like according to your systems specs. Follow the solutions provided "
+"by this document at your own risk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):67
+msgid "Grub loading, please wait..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):69
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):116
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):157
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):301
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):339
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):373
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):408
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):439
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):472
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):502
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):560
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):594
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):620
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):647
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):674
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):709
+msgid "Situation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):72
+msgid "Grub output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):72
+#, no-wrap
+msgid ""
+"\n"
+"GRUB loading stage 1.5\n"
+"GRUB loading, please wait...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):77
+msgid ""
+"After this message, the system stops. If you attempt to boot the system "
+"using a grub floppy, the problem disappears."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):85
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):131
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):314
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):351
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):385
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):424
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):454
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):486
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):513
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):576
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):605
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):631
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):657
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):685
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):728
+msgid "Solution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):88
+msgid ""
+"According to <uri link=\"http://forums.gentoo.org/profile.php?"
+"mode=viewprofile&amp;u=3134\">The_Bell</uri> you could change the boot order "
+"in your BIOS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):94
+msgid "Tell your BIOS to not boot from your floppy first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):98
+msgid ""
+"<uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;"
+"u=39305\">penetrode</uri> wrote that this may also be due to bad CFLAGS "
+"settings. Although the current grub ebuild filters out <c>-fstack-protector</"
+"c>, it can't hurt to recompile grub with clean CFLAGS if nothing else helps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):105
+msgid "Using a clean CFLAG to rebuild GRUB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):105
+#, no-wrap
+msgid ""
+"\n"
+"# <i>CFLAGS=\"-O2 -march=i686 -fomit-frame-pointer -pipe\" emerge grub</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):114
+msgid "Grub Error 12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):119
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):304
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):342
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):376
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):415
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):446
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):568
+msgid "Grub Output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):119
+#, no-wrap
+msgid ""
+"\n"
+"12 : Invalid device requested.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):123
+msgid ""
+"This error is returned if the device strings syntax is correct but other "
+"than that, an error occurred that isn't defined by any other error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):134
+msgid ""
+"When you installed grub in your boot record using the interactive commands, "
+"did you execute the two lines below in the grub prompt?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):139
+msgid "Interactive installation commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):139
+#, no-wrap
+msgid ""
+"\n"
+"grub&gt; <i>root (hd0,0)</i>\n"
+"grub&gt; <i>setup (hd0)</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):144
+msgid ""
+"(hd0,0) must be replaced with your boot partition and (hd0) with the HDD you "
+"have chosen. Remember that (hd0) will install the bootloader in the Master "
+"Boot Record of the first hard disk, the primary master."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):155
+msgid "Grub Error 15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):160
+msgid ""
+"This error can occur in two different stages of the GRUB configuration, "
+"either during the initial configuration (installing GRUB in the master boot "
+"record) or after booting the system and attempting to launch Linux (or any "
+"other entry)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):166
+msgid "Grub Output - Initial Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):166
+#, no-wrap
+msgid ""
+"\n"
+"grub&gt; <i>root (hd0,0)</i>\n"
+" Filesystem type is xfs, partition type 0x83\n"
+"\n"
+"grub&gt; <i>setup (hd0)</i>\n"
+" Checking if \"/boot/grub/stage1\" exists... no\n"
+" Checking if \"/grub/stage1\" exists... no\n"
+"\n"
+"Error 15: File not found\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):177
+msgid "Grub Output - Booting an Entry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):177
+#, no-wrap
+msgid ""
+"\n"
+"Booting 'gentoo Linux'\n"
+"\n"
+"root (hd0,0)\n"
+"Filesystem type is ext2fs, partition type 0x83\n"
+"kernel (hd0,0)/boot/kernel-2.4.20 root=/dev/hda3 vga=792\n"
+"\n"
+"Error 15: File not found\n"
+"Press any key to continue...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):191
+msgid "Solution - Initial Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):194
+msgid ""
+"This error is returned if the specified file name cannot be found, but "
+"everything else (like the disk/partition info) is OK."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):199
+msgid ""
+"Frequently, the error notes a missing kernel image file. Make sure that the "
+"file it is referring to exists on your boot partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):204
+msgid ""
+"To find out the exact name of your kernel, boot from the installation cd, "
+"mount your root and (if applicable) boot partition. Next, chroot into your "
+"Gentoo system and do a listing of the available files to see what kernel "
+"images you have available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):211
+msgid "Verifying kernel image existence"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):211
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /boot</i>\n"
+"# <i>ls</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):216
+msgid ""
+"This will list all the kernels that you've got on your boot partition. If "
+"your kernel is missing make sure that you compiled a kernel (using "
+"<c>genkernel</c> or manually):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):222
+msgid "Recompile the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):222
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux/</i>\n"
+"# <i>make menuconfig</i>\n"
+"# <i>make</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):228
+msgid "And that you copied it to your boot partition:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):232
+msgid "Copying the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):232
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp /usr/src/linux/arch/i386/boot/bzImage /boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):236
+msgid ""
+"Verify that the name of the kernel is exactly the same as the one mentioned "
+"in your <path>grub.conf</path> file. Also make sure that the <c>kernel</c> "
+"line in your <path>grub.conf</path> file is referring to that partition "
+"(either explicitly or implicitly)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):243
+msgid ""
+"Another reported mistake is to have the BIOS ignore the disk on which the "
+"kernel or grub stages reside. Also, the partition on which grub stores its "
+"stages should not use a software RAID-5 (or other striping technology) "
+"configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):252
+msgid "Solution - Booting an Entry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):255
+msgid ""
+"First, verify that the <c>root</c> and <c>setup</c> lines you have used are "
+"correct."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):260
+msgid ""
+"If you are certain they are valid, then you <e>might</e> be using a flawed "
+"GRUB version (0.93.20031222). Upgrade your Portage tree or mask this version "
+"of grub:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):266
+msgid "Masking Grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):266
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Execute this from within the chrooted environment)</comment>\n"
+"# <i>echo \"=sys-boot/grub-0.93.20031222\" &gt;&gt; /etc/portage/package.mask</i>\n"
+"# <i>emerge grub -p</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):272
+msgid ""
+"You could also try to use the <c>grub-install</c> script as is recommended "
+"by the GRUB authors:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):277
+msgid "Using grub-install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):277
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(The --root-directory is needed if you are using a separate boot\n"
+"partition,\n"
+" otherwise you should leave it out)</comment>\n"
+"# <i>grub-install --root-directory=/boot /dev/hda</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):284
+msgid ""
+"When all this fails, your boot partition may be corrupt. Check the partition "
+"for errors:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):289
+msgid "Checking a partition for errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):289
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Make sure the boot partition, /dev/hda1 in this case, is unmounted)</comment>\n"
+"# <i>fsck -y /dev/hda1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):299
+msgid "Grub Error 17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):304
+#, no-wrap
+msgid ""
+"\n"
+"root (hd0,0)\n"
+"filesystem type unknown partition type 0x7\n"
+"\n"
+"Error 17 : Cannot mount selected partition\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):317
+msgid ""
+"This error is returned if the partition requested exists, but the filesystem "
+"type cannot be recognized by GRUB."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):322
+msgid "Be sure to check your root(x,y) settings in your grub.conf."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):326
+msgid ""
+"Also, if you are trying to boot Windows, make sure that your <path>grub."
+"conf</path> file has the <c>root (hdX,Y)</c> (or <c>rootnoverify (hdX,Y)</"
+"c>) and <c>chainloader (hdX,Y)+1</c> in it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):337
+msgid "Grub Error 18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):342
+#, no-wrap
+msgid ""
+"\n"
+"kernel (hd1,4)/bzImage root=/dev/hdb7\n"
+"\n"
+"Error 18: Selected cylinder exceeds max supported by BIOS\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):354
+msgid ""
+"This error is returned when a read is attempted at a linear block address "
+"beyond the end of the BIOS translated area. This generally happens if your "
+"disk is larger than the BIOS can handle (512MB for (E)IDE disks on older "
+"machines or larger than 8GB in general)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):361
+msgid ""
+"Try an update for your BIOS and/or move your boot partition to the front (or "
+"at least into the appropriate range)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):371
+msgid "GRUB GRUB GRUB GRUB GRUB ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):376
+#, no-wrap
+msgid ""
+"\n"
+"GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB\n"
+"  GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB\n"
+"...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):388
+msgid ""
+"According to <uri link=\"http://forums.gentoo.org/profile.php?"
+"mode=viewprofile&amp;u=3139\">airhead</uri> this can be caused by having "
+"your bios detect your disks automatically. Try to set your bios entry to "
+"User Type HDD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):395
+msgid ""
+"Another possibility is that you had Grub installed on your MBR and tried "
+"reinstalling it (for instance due to hard disk changes) but used the wrong "
+"<c>setup</c> and <c>root</c> commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):406
+msgid "Probing Devices to Guess BIOS Drives. This May Take a Long Time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):411
+msgid ""
+"While trying to install grub, it hangs after displaying the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):415
+#, no-wrap
+msgid ""
+"\n"
+"# <i>grub</i>\n"
+"\n"
+"Probing devices to guess BIOS drives. This may take a long time.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):427
+msgid ""
+"One reported cause was an exotic configuration of disk devices, like ultra/"
+"non-ultra DMA disks on one cable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):437
+msgid "When Installing Grub, It Just Hangs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):442
+msgid "When installing grub, it hangs:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):446
+#, no-wrap
+msgid ""
+"\n"
+"# <i>grub</i>\n"
+"<comment>(At this stage, the installation stops)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):457
+msgid ""
+"If you haven't got a floppy drive, have you used the --no-floppy switch?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):461
+msgid "Installing grub using the --no-floppy switch"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):461
+#, no-wrap
+msgid ""
+"\n"
+"# <i>grub --no-floppy</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):470
+msgid "Uncompressing Linux... Ok, booting the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):475
+msgid "The system hangs after displaying the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):479
+msgid "Linux Output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):479
+#, no-wrap
+msgid ""
+"\n"
+"Uncompressing Linux... Ok, booting the kernel.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):489
+msgid ""
+"Strictly speaking, this is no grub error. One possible cause is that ACPI is "
+"not working correctly but is enabled in the kernel. Try to disable it in "
+"your bios or in your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):500
+msgid "Grub Just Shows a Grub Prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):505
+msgid ""
+"When booting the system, you receive a grub prompt instead of a list of "
+"entries you have defined in your <path>grub.conf</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):516
+msgid ""
+"Mount your boot partition and verify if the <path>grub/grub.conf</path> file "
+"exists."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):521
+msgid "Mounting and verifying"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):521
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount /dev/hda1 /mnt/gentoo/boot</i>\n"
+"# <i>cat /mnt/gentoo/boot/grub/grub.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):526
+msgid "Also make sure that the <path>menu.lst</path> symbolic link exists:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):530
+msgid "Verifying the symbolic link"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):530
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls -l /mnt/gentoo/boot/grub/menu.lst</i>\n"
+"lrwxrwxrwx  1 root root 9 Mar  7 14:00 /mnt/gentoo/boot/grub/menu.lst -&gt; grub.conf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):535
+msgid "If not, recreate the symbolic link:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):539
+msgid "Recreating the menu.lst symbolic link"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):539
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /mnt/gentoo/boot/grub</i>\n"
+"# <i>ln -snf grub.conf menu.lst</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):544
+msgid "If this is the case, reinstall grub:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):548
+msgid "Reinstalling Grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):548
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Run from within the chrooted environment)</comment>\n"
+"# <i>grub-install --root-directory=/boot /dev/hda</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):558
+msgid "Could Not Find Device For /boot/boot: Not Found Or Not a Block Device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):563
+msgid ""
+"When running <c>grub-install</c> during the GRUB installation, you receive "
+"the following error:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):568
+#, no-wrap
+msgid ""
+"\n"
+"# <i>grub-install --root-directory=/boot /dev/hda</i>\n"
+"Could not find device for /boot/boot: not found or not a block device\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):579
+msgid "Check that you didn't forget the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):583
+msgid "Updating the mtab file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):583
+#, no-wrap
+msgid ""
+"\n"
+"# <i>grep -v rootfs /proc/mounts &gt; /etc/mtab</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):592
+msgid "The System Reboots After Hitting Return At The Grub Menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):597
+msgid ""
+"After hitting Return at the Grub menu during the system boot, the system "
+"reboots."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):608
+msgid ""
+"Try disabling framebuffer support in your kernel. If this does not help, "
+"disable APM and ACPI."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):618
+msgid "After Hitting Return At The Grub Menu, The Screen Blanks Out"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):623
+msgid ""
+"After hitting Return at the Grub menu during system boot, the screen blanks "
+"out, but the system is responsive (for instance, your numlock led is "
+"switcheable)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):634
+msgid ""
+"Turn off framebuffer (typically remove <c>vga=XYZ</c> from your <path>grub."
+"conf</path>) and check the processor architecture in your kernel config."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):645
+msgid "Missing Grub Image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):650
+msgid "When booting the system, you do not see that spify Gentoo splashscreen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):660
+msgid ""
+"First of all check if the splashscreen file you are referring to in your "
+"<path>grub.conf</path> really exists. If that is the case, go and check the "
+"grub ebuild. Maybe the patch for the splash image is commented out in the "
+"version that you are using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):672
+msgid "Failing To Boot Windows From a Second Harddrive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):677
+msgid ""
+"After selecting the Windows entry, the system refuses to boot without any "
+"clear reason as to why."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):688
+msgid ""
+"<uri link=\"http://forums.gentoo.org/profile.php?mode=viewprofile&amp;"
+"u=14595\">cyrillic</uri> informed us that you can \"map\" your disks in a "
+"different order by changing your <path>grub.conf</path>'s Windows entry like "
+"so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):695
+msgid "Mapping disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):695
+#, no-wrap
+msgid ""
+"\n"
+"title Windows XP\n"
+"  map (hd0) (hd1)\n"
+"  map (hd1) (hd0)\n"
+"  chainloader (hd1,0)+1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(title):707
+msgid "Grub segfaults when trying to install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):712
+msgid ""
+"The situation described below is only relevant for grub-0.95.x at the moment "
+"of installing grub at the boot sector."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre:caption):717
+msgid "Installing Grub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(pre):717
+#, no-wrap
+msgid ""
+"\n"
+"grub&gt; root (hd0,0)\n"
+"\n"
+"grub&gt; setup (hd0)\n"
+"\n"
+"Segmentation fault\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(p):731
+msgid ""
+"This is a known bug related to this problem and has been fixed in grub 0.96. "
+"It is also known that grub 0.94 r1 and grub 0.94 r2 should work correctly. "
+"If that fails too, you can try to emerge grub-static which is currently "
+"stable on amd64 and unstable on x86 (~x86). Check out bug <uri link=\"http://"
+"bugs.gentoo.org/show_bug.cgi?id=79378\">#79378</uri> for additional "
+"information."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//grub-error-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/guide-localization.xml.po b/doc/gettext/ru/guide-localization.xml.po
new file mode 100644
index 0000000..d88ed43
--- /dev/null
+++ b/doc/gettext/ru/guide-localization.xml.po
@@ -0,0 +1,781 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(guide:link):5
+msgid "/doc/en/guide-localization.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):6
+msgid "Gentoo Linux Localization Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author):7
+msgid "Alexander Holler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):10
+msgid "Translator/Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):11
+msgid "slucy@uchicago.edu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):11
+msgid "Steven Lucy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):13
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):16
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):19
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):22
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(author:title):25
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):14
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):14
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):17
+msgid "pylon@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):17
+msgid "Lars Weiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):20
+msgid "dertobi123@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):20
+msgid "Tobias Scherbaum"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):23
+msgid "flammie@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail):23
+msgid "Flammie Pirinen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(mail:link):26
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(abstract):29
+msgid ""
+"This guide should help users localize their Gentoo Linux distribution to any "
+"European locale. It uses Germany as a case-study, since it is translated "
+"from the German doc. Includes configuration for use of the euro currency "
+"symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(version):35
+msgid "1.46"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(date):36
+msgid "2010-02-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):39
+msgid "Time zone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):43
+msgid ""
+"In order to keep time properly, you need to select your timezone so that "
+"your system knows where it is located. Look for your timezone in <path>/usr/"
+"share/zoneinfo</path>. You then set your timezone in <path>/etc/conf.d/"
+"clock</path>. Please avoid the <path>/usr/share/zoneinfo/Etc/GMT*</path> "
+"timezones as their names do not indicate the expected zones. For instance, "
+"<path>GMT-8</path> is in fact GMT+8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):52
+msgid "Setting the timezone information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):52
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls /usr/share/zoneinfo</i>\n"
+"<comment>(Suppose you want to use Brussels)</comment>\n"
+"<comment>(First copy the proper zone to localtime)</comment>\n"
+"# <i>cp /usr/share/zoneinfo/Europe/Brussels /etc/localtime</i>\n"
+"<comment>(Now specify your timezone)</comment>\n"
+"# <i>nano -w /etc/conf.d/clock</i>\n"
+"TIMEZONE=\"Europe/Brussels\"\n"
+"\n"
+"# <i>date</i>\n"
+"Wed Mar  8 00:46:05 CET 2006\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):65
+msgid ""
+"Make sure that the timezone indicator (in this case \"CET\") is correct for "
+"your area."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):70
+msgid ""
+"You can set the value of <c>TZ</c> to be everything after the <path>/usr/"
+"share/zoneinfo</path> in your shell rc file (<path>.bash_profile</path> for "
+"bash) for a user-level setting. In this case <c>TZ=\"Europe/Berlin\"</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):82
+msgid "Hardware Clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):86
+msgid ""
+"In most Gentoo Linux installations, your hardware clock is set to UTC (or "
+"GMT, Greenwich Mean Time) and then your timezone is taken into account to "
+"determine the actual, local time. If, for some reason, you need your "
+"hardware clock not to be in UTC, you will need to edit <path>/etc/conf.d/"
+"clock</path> and change the value of <c>CLOCK</c> from <c>UTC</c> to "
+"<c>local</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):95
+msgid "local vs. GMT clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):95
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(recommended:)</comment>\n"
+"CLOCK=\"UTC\"\n"
+"<comment>(or:)</comment>\n"
+"CLOCK=\"local\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):107
+msgid "Locale system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):109
+msgid "What are locales?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):112
+msgid ""
+"A Locale is a set of information that most programs use for determining "
+"country and language specific settings. The locales and their data are part "
+"of the system library and can be found at <path>/usr/share/locale</path> on "
+"most systems. A locale name is generally named <c>ab_CD</c> where <c>ab</c> "
+"is your two (or three) letter language code (as specified in ISO-639) and "
+"<c>CD</c> is your two letter country code (as specified in ISO-3166). "
+"Variants are often appended to locale names, e.g. <c>en_GB.UTF-8</c> or "
+"<c>de_DE@euro</c>. Please explore <uri link=\"http://en.wikipedia.org/wiki/"
+"Locale\">Wikipedia</uri> to read more about locales and related articles."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):127
+msgid "Environment variables for locales"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):130
+msgid ""
+"Locale settings are stored in environment variables. These are typically set "
+"in the <path>/etc/env.d/02locale</path> (for system-wide settings) and "
+"<path>~/.bashrc</path> (for user-specific settings) file. The variables "
+"controlling different aspects of locale settings are given in the table "
+"below. All of them take one name of a locale in <c>ab_CD</c> format given "
+"above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(th):141
+msgid "Variable name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(th):142
+msgid "Explanation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):145
+msgid "LANG"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):146
+msgid ""
+"Defines all locale settings at once, while allowing further individual "
+"customization via the LC_* settings below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):152
+msgid "LC_COLLATE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):153
+msgid ""
+"Define alphabetical ordering of strings. This affects e.g. output of sorted "
+"directory listing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):159
+msgid "LC_CTYPE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):160
+msgid ""
+"Define the character handling properties for the system. This determines "
+"which characters are seen as part of alphabet, numeric and so on. This also "
+"determines the character set used, if applicable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):167
+msgid "LC_MESSAGES"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):168
+msgid ""
+"Programs' localizations for applications that use message based localization "
+"scheme (majority of Gnu programs, see next chapters for closer information "
+"which do, and how to get the programs, that don't, to work)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):175
+msgid "LC_MONETARY"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):176
+msgid "Defines currency units and formatting of currency type numeric values."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):179
+msgid "LC_NUMERIC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):180
+msgid ""
+"Defines formatting of numeric values which aren't monetary. Affects things "
+"such as thousand separator and decimal separator."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):186
+msgid "LC_TIME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):187
+msgid "Defines formatting of dates and times."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):190
+msgid "LC_PAPER"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):191
+msgid "Defines default paper size."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):194
+msgid "LC_ALL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(ti):195
+msgid "A special variable for overriding all other settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):201
+msgid ""
+"Some programs are written in such a way that they expect traditional English "
+"ordering of the alphabet, while some locales, most notably the Estonian one, "
+"use a different ordering. Therefore it's recommended to explicitly set "
+"LC_COLLATE to C when dealing with system-wide settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(warn):208
+msgid ""
+"Using LC_ALL is strongly discouraged as it can't be overridden later on. "
+"Please use it only when testing and <e>never</e> set it in a startup file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):213
+msgid ""
+"Most typically users only set the LANG variable on the global basis. This "
+"example is for a unicode German locale:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):218
+msgid "Setting the default system locale in /etc/env.d/02locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):218
+#, no-wrap
+msgid ""
+"\n"
+"LANG=\"de_DE.UTF-8\"\n"
+"LC_COLLATE=\"C\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):223
+msgid ""
+"Use <c>de_DE@euro</c> as your LANG if you want to use the Euro currency "
+"symbol (€)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):228
+msgid ""
+"It's also possible, and pretty common especially in a more traditional UNIX "
+"environment, to leave the global settings unchanged, i.e. in the \"<c>C</c>"
+"\" locale. Users can still specify their preferred locale in their own shell "
+"RC file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):235
+msgid "Setting the user locale in ~/.bashrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):235
+#, no-wrap
+msgid ""
+"\n"
+"export LANG=\"de_DE.UTF-8\"\n"
+"export LC_COLLATE=\"C\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):240
+msgid ""
+"Another way of configuring system is to leave it in the default C locale, "
+"but enable UTF-8 character representation at the same time. This option is "
+"achieved using the following settings in <path>/etc/env.d/02locale</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):246
+msgid "Using traditional C locale while specifying UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):246
+#, no-wrap
+msgid ""
+"\n"
+"LC_CTYPE=de_DE.UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):250
+msgid ""
+"Using the above snippet, users will be able to see localized file names "
+"properly, while not being forced to your preferred language."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):255
+msgid ""
+"For message based localization to work in programs that support it, you will "
+"probably need to have programs compiled with the <c>nls</c> (Native language "
+"support) USE flag set. Most of the programs using nls also need the gettext "
+"library to extract and use localized messages. Of course, Portage will "
+"automatically install it when needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):263
+msgid ""
+"Once you have set the right locale, be sure to update your environment "
+"variables to make your system aware of the change:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):268
+msgid "Update the environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):268
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(For system-wide default locale:)</comment>\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+"\n"
+"<comment>(For user-specific locale:)</comment>\n"
+"$ <i>source ~/.bashrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):276
+msgid ""
+"After this, you will need to kill your X server by pressing <c>Ctrl-Alt-"
+"Backspace</c>, log out, then log in as user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):281
+msgid "Now, verify that the changes have taken effect:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):285
+msgid "Verify env changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):285
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>locale</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):289
+msgid ""
+"There is also additional localisation variable called LINGUAS, which affects "
+"to localisation files that get installed in gettext-based programs, and "
+"decides used localisation for some specific software packages, such as "
+"<c>kde-base/kde-l10n</c> and <c>app-office/openoffice</c>. The variable "
+"takes in <e>space</e>-separated list of language codes, and suggested place "
+"to set it is <path>/etc/make.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):298
+msgid "Setting LINGUAS in make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):298
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/make.conf</i>\n"
+"<comment>(Add in the LINGUAS variable. For instance, \n"
+"for German, Finnish and English:)</comment>\n"
+"LINGUAS=\"de fi en\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):309
+msgid "Generating Specific Locales"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):312
+msgid ""
+"You will probably only use one or maybe two locales on your system. You can "
+"specify locales you will need in <path>/etc/locale.gen</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):317
+msgid "Adding locales to /etc/locale.gen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):317
+#, no-wrap
+msgid ""
+"\n"
+"en_GB ISO-8859-1\n"
+"en_GB.UTF-8 UTF-8\n"
+"de_DE ISO-8859-1\n"
+"de_DE@euro ISO-8859-15\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):324
+msgid ""
+"The next step is to run <c>locale-gen</c>. It will generate all the locales "
+"you have specified in the <path>/etc/locale.gen</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):329
+msgid ""
+"<c>locale-gen</c> is available in <c>glibc-2.3.6-r4</c> and newer. If you "
+"have an older version of glibc, you should update it now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):334
+msgid ""
+"You can verify that your selected locales are available by running <c>locale "
+"-a</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):344
+msgid "Keyboard layout for the console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):348
+msgid ""
+"The keyboard layout used by the console is set in <path>/etc/conf.d/keymaps</"
+"path> by the <c>KEYMAP</c> variable. Valid values can be found in <path>/usr/"
+"share/keymaps/<c>{arch}</c>/</path>. <path>i386</path> has further "
+"subdivisions into layout (<path>qwerty/</path>, <path>azerty/</path>, etc.). "
+"Some languages have multiple options, so you may wish to experiment to "
+"decide which one fits your needs best."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):359
+msgid "Setting the console keymap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):359
+#, no-wrap
+msgid ""
+"\n"
+"KEYMAP=\"de\"\n"
+"KEYMAP=\"de-latin1\"\n"
+"KEYMAP=\"de-latin1-nodeadkeys\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):370
+msgid "Keyboard layout for the X server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):374
+msgid ""
+"The keyboard layout to be used by the X server is specified in <path>/etc/"
+"X11/xorg.conf</path> by the <c>XkbLayout</c> option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):380
+msgid "Setting the X keymap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):380
+#, no-wrap
+msgid ""
+"\n"
+" Section \"InputDevice\"\n"
+"     Identifier  \"Keyboard1\"\n"
+"     ...\n"
+"     Option \"XkbLayout\"    \"de\"\n"
+"     #Option \"XkbModel\"     \"pc105\"    <comment>## this is for international keyboards.</comment>\n"
+"     # Option \"XkbVariant\"  \"nodeadkeys\" <comment>## this would be used for xterm input</comment>\n"
+"     ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):390
+msgid ""
+"If you have an international keyboard layout, you should set the option "
+"<c>XkbModel</c> to <c>pc102</c> or <c>pc105</c>, as this will allow mapping "
+"of the additional keys specific to your keyboard."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):396
+msgid ""
+"Deadkeys allow you to press keys that will not show immediately but will be "
+"combined with another letter to produce a single character such as é,è,á,à, "
+"etc. Setting <c>XkbVariant</c> to <c>nodeadkeys</c> allows input these "
+"special characters into X terminals."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):403
+msgid ""
+"If you would like to switch between more than one keyboard layout (for "
+"example English and Russian), all you have to do is add a few lines to "
+"<path>xorg.conf</path> that specify the desired layouts and the shortcut "
+"command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):410
+msgid "Switching between two keyboard layouts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):410
+#, no-wrap
+msgid ""
+"\n"
+" Section \"InputDevice\"\n"
+"     Identifier  \"Keyboard1\"\n"
+"     ...\n"
+"     Option \"XkbLayout\"    \"us,ru\"\n"
+"     Option \"XkbOptions\"   \"grp:alt_shift_toggle,grp_led:scroll\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):418
+msgid ""
+"Here, <c>XkbOptions</c> allows you to toggle between keyboard layouts by "
+"simply pressing <c>Alt-Shift</c>. This will also toggle the Scroll Lock "
+"light on or off, thanks to the <c>grp_led:scroll</c> option. This is a handy "
+"visual indicator of which keyboard layout you are using at the moment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):430
+msgid "KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):434
+msgid ""
+"For KDE you have to install the <c>kde-base/kde-l10n</c> and <c>app-office/"
+"koffice-l10n</c> packages. These respect the <uri link=\"#variables"
+"\">LINGUAS variable</uri> described earlier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):445
+msgid "The Euro Symbol for the Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):449
+msgid ""
+"In order to get your console to display the Euro symbol, you will need to "
+"set <c>CONSOLEFONT</c> in <path>/etc/conf.d/consolefont</path> to a file "
+"found in <path>/usr/share/consolefonts/</path> (without the <c>.psfu.gz</"
+"c>). <c>lat9w-16</c> has the Euro symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):456
+msgid "Setting the console font"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):456
+#, no-wrap
+msgid ""
+"\n"
+"CONSOLEFONT=\"lat9w-16\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):460
+msgid "You should verify that <c>CONSOLEFONT</c> is in the boot runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):464
+msgid "Verify the proper runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):464
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update -v show | grep -i consolefont</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):468
+msgid ""
+"If no runlevel is displayed for <c>CONSOLEFONT</c>, then add it to the "
+"proper level:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):472
+msgid "Add consolefont to boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):472
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add consolefont boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):481
+msgid "The Euro Symbol in X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):483
+msgid "Most Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):486
+msgid ""
+"Getting the Euro symbol to work properly in X is a little bit tougher. The "
+"first thing you should do is change the <c>fixed</c> and <c>variable</c> "
+"definitions in <path>/usr/share/fonts/misc/fonts.alias</path> to end in "
+"<c>iso8859-15</c> instead of <c>iso8859-1</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):493
+msgid "Setting default X fonts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):493
+#, no-wrap
+msgid ""
+"\n"
+"fixed        -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-15\n"
+"variable     -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):498
+msgid ""
+"Some applications use their own font, and you will have to tell them "
+"separately to use a font with the Euro symbol. You can do this at a user-"
+"specific level in <path>.Xdefaults</path> (you can copy this file to <path>/"
+"etc/skel/</path> for use by new users), or at a global level for any "
+"application with a resource file in <path>/usr/share/X11/app-defaults/</"
+"path> (like xterm). In these files you generally have to change an existing "
+"line, rather than adding a new one. To change our xterm font, for instance:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):508
+msgid "Setting fonts for xterm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):508
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(in your home directory)</comment>\n"
+"$ <i>echo 'XTerm*font: fixed' &gt;&gt; .Xresources </i>\n"
+"$ <i>xrdb -merge .Xresources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):517
+msgid "The Euro symbol in (X)Emacs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):520
+msgid ""
+"To use the Euro symbol in (X)Emacs, add the following to <path>.Xdefaults</"
+"path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):525
+msgid "setting the font for emacs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):525
+#, no-wrap
+msgid ""
+"\n"
+"Emacs.default.attributeFont: -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-15\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):529
+msgid ""
+"For XEmacs (not plain Emacs), you have to do a little more. In <path>/home/"
+"user/.xemacs/init.el</path>, add:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre:caption):534
+msgid "setting the font for xemacs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(pre):534
+#, no-wrap
+msgid ""
+"\n"
+"(define-key global-map '(EuroSign) '[€])\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(note):538
+msgid "The symbol in the []s is the Euro symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(title):545
+msgid "OpenOffice.Org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(p):548
+msgid ""
+"The current stable <c>app-office/openoffice</c> and <c>app-office/openoffice-"
+"bin</c> ebuilds support the <uri link=\"#variables\">LINGUAS variable</uri> "
+"for selecting installed GUI language packs. To see the status of GUI "
+"translation, hyphenation, spell checking and other localisations on your "
+"language, please refer to <uri link=\"http://l10n.openoffice.org/languages."
+"html\">OpenOffice.Org localisation web site</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//guide-localization.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/guide-to-mutt.xml.po b/doc/gettext/ru/guide-to-mutt.xml.po
new file mode 100644
index 0000000..7c80654
--- /dev/null
+++ b/doc/gettext/ru/guide-to-mutt.xml.po
@@ -0,0 +1,743 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(guide:link):6
+msgid "/doc/en/guide-to-mutt.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):8
+msgid "QuickStart Guide to Mutt E-Mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail:link):11
+msgid "mikpolniak@adelphia.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail):11
+msgid "Mike Polniak"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(author:title):13
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail:link):14
+msgid "antifa@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail):14
+msgid "Ken Nowack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(author:title):16
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail:link):17
+msgid "hitch17@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(mail):17
+msgid "John Hitchings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(abstract):20
+msgid ""
+"This guide shows you how to begin using the powerful command line tools for "
+"e-mail: fetchmail, procmail, mutt, nbsmtp, msmtp."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(version):29
+msgid "1.7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(date):30
+msgid "2006-09-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):33
+msgid "Introduction to E-Mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):37
+msgid ""
+"If you're not a fan of e-mail clients with fancy graphical user interfaces, "
+"or if you would just like to experiment with other mail clients before "
+"deciding which is best for you, here is the easy way to begin using these "
+"powerful command line tools:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):48
+msgid ""
+"These programs are not only powerful and highly customizable but also small "
+"and efficient. Once you are up and running with this e-mail system you will "
+"be amazed at what you can do with it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):54
+msgid ""
+"Because this is a quick start guide, we will eliminate the Mail Transfer "
+"Agent (MTA) such as sendmail, postfix or exim. This means no complex MTA "
+"configuration. It also eliminates using port 25 for mail service."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):60
+msgid ""
+"We can do this because fetchmail can force the mail it retrieves directly to "
+"a Mail Delivery Agent (MDA) rather than forwarding to port 25. And we don't "
+"need to use a complex MTA for plain old outgoing mail delivery."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):66
+msgid "These are the programs you will need to get your e-mail running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):70
+msgid "Getting needed programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):70
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge fetchmail nbsmtp procmail mutt</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):74
+msgid ""
+"Then just four quick steps to configure files and you will be up and running "
+"a brand new e-mail system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(impo):79
+msgid ""
+"After each step you can run a test to make sure the setup is correct. This "
+"means you will have a complete working e-mail system when you are done."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):89
+msgid "Fetchmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):93
+msgid ""
+"Fetchmail fetches mail from remote servers and forwards it to your local "
+"machines delivery system. To use it you need to set up a <path>.fetchmailrc</"
+"path> file in your home directory like this example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):99
+msgid "Sample .fetchmailrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):103
+msgid ""
+"Once you have created a <path>.fetchmailrc</path> file, you have to change "
+"the permissions on the file using the chmod command. The file must be "
+"readable only by the file owner. Set the permissions with the following "
+"command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):109
+msgid "Changing Permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):109
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>chmod 600 .fetchmailrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):113
+msgid ""
+"To see fetchmail in action, use the verbose mode (-v). To fetch all messages "
+"use -a. And you must use the option -m to tell fetchmail to send the mail to "
+"procmail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(warn):119
+msgid ""
+"While testing, it's a good idea to tell fetchmail to keep (-k) the mail on "
+"the remote server in case something goes wrong and you need to fetch it "
+"again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):124
+msgid "Run it now to see fetchmail in action!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):128
+msgid "Fetchmail test #1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):128
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):250
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>fetchmail -akv -m \"/usr/bin/procmail -d %T\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):132
+msgid ""
+"Once you have a working mail system you can set this as a cron job or put it "
+"in a monitor like gkrellm. Fetchmail can also run in a daemon mode for which "
+"you specify a polling interval in seconds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):143
+msgid "Procmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):147
+msgid ""
+"Procmail is the processor that filters the mail that is forwarded to it by "
+"fetchmail. It also acts as the MDA to deliver mail to your mailboxes where "
+"mutt (your e-mail client) can read it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):153
+msgid ""
+"To use procmail you need to create a <path>.procmailrc</path> file in your "
+"home directory. For our quickstart purposes we will use a very simple <path>."
+"procmailrc</path> that will filter mail from three gentoo mailing lists into "
+"these mailboxes:<e>gentoo-dev, gentoo-user</e> and <e>gentoo-announce</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(note):160
+msgid ""
+"The procmail filter rules are called recipes, and I have also included "
+"recipes to filter out some spam."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):165
+msgid "Sample .procmailrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):165
+#, no-wrap
+msgid ""
+"\n"
+"MAILDIR=$HOME/MuttMail                ##you better make sure it exists\n"
+"LOGFILE=$HOME/.procmaillog\n"
+"LOGABSTRACT=no\n"
+"#VERBOSE=on...is only used for debugging\n"
+"VERBOSE=off\n"
+"FORMAIL=/usr/bin/formail\n"
+"NL=\"\n"
+"\"\n"
+"##recipe lines begin with :0\n"
+"##dont put comments on recipe lines\n"
+"##disable a recipe with the false condition !\n"
+"##condition lines begin with * and regex is your friend\n"
+"##conditions are anded and everything after * is fed straight into egrep\n"
+"##one action line follows the conditions, in this case it is a mailbox name\n"
+"\n"
+"#catch duplicates using formail\n"
+":0 Whc: .msgid.lock\n"
+"| $FORMAIL -D 16384 .msgid.cache\n"
+"\n"
+":0 a\n"
+"$MAILDIR/duplicates\n"
+"\n"
+"#people we always allow mail from\n"
+":0\n"
+"* ^From:.*(craig\\@hotmail|renee\\@local.com)\n"
+"$MAILDIR/friends\n"
+"\n"
+"#now flush some spam out\n"
+":0\n"
+"* ^Subject:.*(credit|cash|money|debt|sex|sale|loan)\n"
+"$MAILDIR/spam\n"
+"\n"
+"#no more html messages\n"
+":0\n"
+"* ^Content-Type:.*html\n"
+"$MAILDIR/junk\n"
+"\n"
+"#now put my mail lists into mailboxes\n"
+":0\n"
+"* ^List-Id:.*gentoo-user\n"
+"gentoo-user\n"
+"\n"
+":0\n"
+"* ^List-Id:.*gentoo-dev\n"
+"gentoo-dev\n"
+"\n"
+":0\n"
+"* ^List-Id:.*gentoo-announce\n"
+"gentoo-announce\n"
+"\n"
+"#catch any other gentoo mail\n"
+":0\n"
+"* ^From:.*gentoo.org\n"
+"gentoo\n"
+"\n"
+":0\n"
+"* ^From:.*@freshmeat\\.net\n"
+"freshmeat\n"
+"\n"
+"################################\n"
+"# Last rule: mail that gets    #\n"
+"# this far goes in default box #\n"
+"################################\n"
+":0\n"
+"* .*\n"
+"default\n"
+"\n"
+"# End of file\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(note):236
+msgid ""
+"It is only required to make the MAILDIR <path>$HOME/MuttMail</path> as "
+"Procmail will create all the mailbox files as needed in this directory using "
+"the names on the action lines. For some useful links visit <uri>http://www."
+"procmail.org/</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):243
+msgid ""
+"You can now test <path>.procmailrc</path> by re-running the fetchmail "
+"command we tested in the first step. Remember the -k option to keep all mail "
+"on the remote server so we have it if we need to rerun it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):250
+msgid "Procmail test #1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):254
+msgid ""
+"Now that fetchmail and procmail have run, go to <path>$HOME/MuttMail</path> "
+"and read your messages with <c>less</c> or your file manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):264
+msgid "Mutt e-mail client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):268
+msgid ""
+"Mutt is used to read and compose e-mail. It is powerful and highly "
+"customizable but also small and efficient."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):273
+msgid ""
+"Mutt supports reading and writing of four different mailbox formats: mbox, "
+"MMDF, MH and Maildir. The mailbox type is autodetected. In our case we are "
+"using the mbox format, where all messages of a mailbox are stored in a "
+"single file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):280
+msgid ""
+"Mutt also has the ability to work with folders located on a remote IMAP "
+"server. See IMAP Support in section 4.11 of the Mutt manual and the Mutt web "
+"site <uri>http://www.mutt.org/</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):286
+msgid ""
+"When you emerged mutt in the first step it installed a configuration file in "
+"<path>/etc/mutt/Muttrc</path>. You also need to create a <path>.muttrc</"
+"path> file in your home directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):292
+msgid "Sample .muttrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):292
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Be sure to read the fine Mutt manual in /usr/share/doc/mutt*)\n"
+"(Any settings here override the system settings in /etc/mutt/Muttrc)</comment>\n"
+"\n"
+"# <i>cp /etc/mutt/Muttrc ~/.muttrc</i>\n"
+"# <i>nano -w .muttrc</i>\n"
+"set pager_context=1\n"
+"set pager_index_lines=6                 #show a mini-index in pager\n"
+"set menu_scroll\n"
+"set pgp_verify_sig=no                   #dont show pgp in pager\n"
+"set status_on_top                       #put status line at top\n"
+"set sort=threads                        #sort by message threads in index\n"
+"\n"
+"set status_format=\" %r %b %f %n      Del %d      Msgs %m %l %&gt; (%P)\"\n"
+"set pager_format=\"%-10.10i %[!%a %b %d %R]\"\n"
+"set date_format=\"!%H:%M %a %d %b     \"\n"
+"set index_format=\"%4C %Z %[%b%d] %-15.15F %s\"\n"
+"set folder_format=\"%2C %t %8s %d %N %f\"\n"
+"\n"
+"#set sendmail=\"/usr/bin/nbsmtp -d isp.net -h smtp.isp.net -f yourname@isp.net\"\n"
+"\n"
+"#set from=\"default-mailaddress\"         #set to your from address\n"
+"#set realname=\"myname\"\n"
+"\n"
+"set record=\"$HOME/MuttMail/sent\"        #sent mail is saved here\n"
+"set delete=yes                          #delete without prompting\n"
+"set include=yes                         #quote msg in reply\n"
+"set fast_reply=yes                      #no prompting on reply\n"
+"set beep=no                             #no noise\n"
+"set markers=no                          #no + on wrapped lines\n"
+"set confirmappend=no                    #no prompt for save to =keep\n"
+"set to_chars=\" +TCF\"                    #no L for mail_list\n"
+"\n"
+"set folder = $HOME/MuttMail\n"
+"mailboxes =gentoo-user\n"
+"mailboxes =gentoo-dev\n"
+"mailboxes =gentoo-announce\n"
+"mailboxes =gentoo\n"
+"mailboxes =freshmeat\n"
+"mailboxes =duplicates\n"
+"mailboxes =default\n"
+"mailboxes =friends\n"
+"mailboxes =junk\n"
+"mailboxes =spam\n"
+"mailboxes =keep\n"
+"\n"
+"save-hook .* =keep                      #default mbox to (s)ave mail is =keep\n"
+"subscribe gentoo-user gentoo-dev        #subscribed to these lists\n"
+"\n"
+"bind pager h display-toggle-weed        #toggle headers with h key\n"
+"\n"
+"# simulate the old url menu\n"
+"macro index \\cb |urlview\\n 'call urlview to extract URLs out of a message'\n"
+"macro pager \\cb |urlview\\n 'call urlview to extract URLs out of a message'\n"
+"\n"
+"#run fetchmail by hitting key of G\n"
+"macro index G \"!fetchmail -a -m 'procmail -d %T'\\r\"\n"
+"macro pager G \"!fetchmail -a -m 'procmail -d %T'\\r\"\n"
+"\n"
+"#use to edit .muttrc and then source it...no restart necessary\n"
+"macro generic ,sm \":source $HOME/.muttrc\\r\"\n"
+"macro generic \\cj \"!rxvt -bg wheat -e joe $HOME/.muttrc\\r\"\n"
+"\n"
+"# default list of header fields to weed out when displaying mail\n"
+"#ignore them all and then unignore what you want to see\n"
+"ignore *\n"
+"unignore  Date To From: Subject X-Mailer Organization User-Agent\n"
+"hdr_order Date From To Subject X-Mailer User-Agent Organization\n"
+"\n"
+"##your Mutt has to have some colors\n"
+"##these are for four levels of quoted text\n"
+"##they override the system settings in /etc/mutt/Muttrc\n"
+"\n"
+"#color quoted green  default\n"
+"color quoted1 magenta blue\n"
+"#color quoted2 yellow default\n"
+"#color quoted3 red default\n"
+"#color signature cyan cyan\n"
+"\n"
+"\n"
+"#this color setup is copied from /etc/mutt/Muttrc.color\n"
+"#comment it out if you want the default colors in /etc/mutt/Muttrc\n"
+"# Je vois la vie en rose :-)\n"
+"color   hdrdefault      brightcyan      blue\n"
+"color   header          brightwhite     blue \"^from:\"\n"
+"color   header          brightwhite     blue   \"^subject:\"\n"
+"\n"
+"color   quoted          brightgreen     blue\n"
+"color   signature       brightwhite     blue\n"
+"\n"
+"color   indicator       blue            green\n"
+"\n"
+"color   error           red             black\n"
+"mono    error           bold\n"
+"color   status          black cyan\n"
+"mono    status          bold\n"
+"color   tree            yellow          blue\n"
+"\n"
+"color   tilde           brightmagenta   blue\n"
+"color   body            brightwhite     blue    \"[-a-z_0-9.]+@[-a-z_0-9.]+\"\n"
+"mono    body            bold                    \"[-a-z_0-9.]+@[-a-z_0-9.]+\"\n"
+"color   body            brightyellow    black   \"^Good signature\"\n"
+"mono    body            bold                    \"^Good signature\"\n"
+"color   body            brightwhite     red     \"^Bad signature from.*\"\n"
+"mono    body            bold                    \"^Bad signature from.*\"\n"
+"color   normal          white           blue\n"
+"color   message         green           black\n"
+"color   attachment      brightgreen     blue\n"
+"\n"
+"# End of file...but it can go on and on and on....:)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):404
+msgid ""
+"For the record, this is just a sample <path>.muttrc</path>. There are many "
+"more options that you can configure, such as integration with GPG. Have a "
+"look at <uri>http://www.dotfiles.com/index.php?app_id=27</uri> for more "
+"examples and help."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):411
+msgid "You are now ready to test your <path>.muttrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):415
+msgid "Testing .muttrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):415
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>mutt -y</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):419
+msgid ""
+"This should open Mutt with a menu showing the Mutt mailboxes that you "
+"created in Test 2 when you ran the fetchmail command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):424
+msgid "Type the ? for help in navigating the Mutt Mailboxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):433
+msgid "SMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):437
+msgid ""
+"The final step is setting up nbsmtp the 'No-Brainer SMTP' used to send mail "
+"to your SMTP server. This setup is the easiest of all, as it only requires "
+"adding an entry in your <path>.muttrc</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):443
+msgid ""
+"domain: The domain you want nbsmtp to say it belongs to. This will almost "
+"invariably be the same as the domain in your e-mail address."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):448
+msgid ""
+"from@addr: This is the address you want nbsmtp to say the message is from. "
+"Note that this can be different than the \"From:\" line in your MUA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):453
+msgid "host: This is the smtp server you are sending to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):457
+msgid "Adding SMTP support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):457
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>nano -w .muttrc</i>\n"
+"set sendmail=\"/usr/bin/nbsmtp -d isp.net -h smtp.isp.net -f urname@isp.net\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):462
+msgid ""
+"You are now ready to send a message. So in the Mutt pager or index hit the "
+"<c>m</c> key to compose a test message to send to your e-mail address. Mutt "
+"will use the value of the EDITOR or VISUAL for the composition editor unless "
+"you set <c>editor=</c> in the <path>.muttrc</path>. When you are done "
+"composing hit <c>y</c> to send your message. If there are no errors you will "
+"see 'sending mail' followed by 'Mail sent.'"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):471
+msgid ""
+"Remember in <path>.muttrc</path> we have set where to save sent mail with "
+"<c>set record=\"$HOME/MuttMail/sent\"</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):476
+msgid ""
+"Now to complete the test, run fetchmail again to get all your mail and "
+"verify you have received the message you sent to your e-mail address. When "
+"you find your test message, hit the <c>h</c> key to toggle a view of all the "
+"headers and see the complete mail transfer path."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(note):483
+msgid ""
+"There is one more program you probably want to add called urlview. This "
+"extracts the urls in message texts and sends them to your browser."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):488
+msgid "Getting urlview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):488
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge urlview</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):492
+msgid ""
+"Then create <path>~/.urlview</path> by copying the configuration file from "
+"<path>/usr/share/doc/urlview*/</path> and setting your browser command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):497
+msgid ""
+"You now have a powerful and highly customizable mail system. To take "
+"advantage of its flexibility, read all the manuals and docs and find the "
+"many user configuration files available on the web: search for "
+"<path>procmailrc</path> and <path>muttrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):509
+msgid "Authenticated SMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):511
+msgid "Using nbSMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):514
+msgid ""
+"If you need to pass a username and password to your SMTP server, you can "
+"edit the <c>set sendmail</c> command in your <path>.muttrc</path> to include "
+"<c>-U &lt;username&gt; -P &lt;password&gt;</c>, like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):520
+msgid "Setting username and password for SMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):520
+#, no-wrap
+msgid ""
+"\n"
+"set sendmail=\"/usr/bin/nbsmtp -U <i>username</i> -P <i>password</i> -d isp.net -h smtp.isp.net -f urname@isp.net\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):524
+msgid ""
+"If you do not want this information to be present in your <path>.muttrc</"
+"path> file, you can also create a <path>.nbsmtprc</path> file in which you "
+"include all information:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):530
+msgid "~/.nbsmtprc example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):530
+#, no-wrap
+msgid ""
+"\n"
+"auth_user = <i>username</i>\n"
+"auth_pass = <i>password</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(title):538
+msgid "Alternative: Using msmtp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):541
+msgid ""
+"<c>msmtp</c> is a simple alternative to <c>nbsmtp</c> with similar "
+"possibilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):546
+msgid "Installing msmtp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):546
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge msmtp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):550
+msgid ""
+"Now login as a normal user and configure msmtp by creating a <path>~/."
+"msmtprc</path> file, filling in your SMTP server's information. Remember to "
+"set the permissions to a secure value!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):556
+msgid "Configuring msmtp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):556
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>nano -w .msmtprc</i>\n"
+"account default\n"
+"host <i>smtp.your_provider.net</i>\n"
+"from <i>your_username@provider1.net</i>\n"
+"<comment>#see man page for more auth options</comment>\n"
+"auth login\n"
+"user <i>your_username</i>\n"
+"password <i>your_password</i>\n"
+"<comment>#If your SMTP Server supports TLS encryption, uncomment the next line\n"
+"#tls</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):569
+msgid "Now set the permissions of the file to a secure value:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):573
+msgid "Setting the permissions for the configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):573
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>chmod 600 .msmtprc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):577
+msgid "Finally, edit or add the following line to <path>.muttrc</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre:caption):581
+msgid "Using msmtp with Mutt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(pre):581
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>nano -w .muttrc</i>\n"
+"set sendmail=\"/usr/bin/msmtp\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(p):586
+msgid ""
+"Fire up <c>mutt</c> and send yourself a test email to see if it worked! See "
+"the msmtp man page for more options and another example."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//guide-to-mutt.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/home-router-howto.xml.po b/doc/gettext/ru/home-router-howto.xml.po
new file mode 100644
index 0000000..973a3c4
--- /dev/null
+++ b/doc/gettext/ru/home-router-howto.xml.po
@@ -0,0 +1,1152 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(guide:link):5
+msgid "/doc/en/home-router-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):6
+msgid "Home Router Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(mail:link):9
+msgid "vapier@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(mail):9
+msgid "Mike Frysinger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(abstract):12
+msgid ""
+"This document details how to turn an old Gentoo machine into a router for "
+"connecting your home network to the internet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(version):20
+msgid "1.40"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(date):21
+msgid "2009-09-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):28
+msgid ""
+"Building your own router out of old spare parts has many advantages over "
+"buying a pre-made canned router by say Linksys. The biggest one by far is "
+"control over the connection. The other advantages are left up to your "
+"imagination; just about anything can be done in this scenario, it's just a "
+"matter of needing it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):36
+msgid ""
+"This guide will show you how to setup Network Address Translation (NAT) on "
+"the router (kernel and iptables), add and configure common services (Domain "
+"Name System (DNS) via dnsmasq, dhcp via dhcpcd, ADSL via ppp), and conclude "
+"with more elaborate and fun things that can be done (port forwarding, "
+"traffic shaping, proxies/caching, etc...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):44
+msgid ""
+"Before getting started, there's a few basic requirements you must meet. "
+"First, you'll need a computer that has at least 2 Network Interface Cards "
+"(NICs) in it. Next, you'll need the configuration settings for your internet "
+"connection (may include things like IP/DNS/Gateway/username/password). "
+"Finally, you'll need a bit of spare time and some Gentoo loving."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):52
+msgid "The conventions used in this guide are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):57
+msgid "eth0 - NIC connected to the Local Area Network (LAN)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):58
+msgid "eth1 - NIC connected to the Wide Area Network (WAN)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):59
+msgid "LAN utilizes the private 192.168.0.xxx network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):60
+msgid "router is hardcoded to the standard 192.168.0.1 IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(li):61
+msgid "router is running Linux 2.4 or 2.6; you're on your own with 2.0/2.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(impo):64
+msgid ""
+"Due to security precautions, I would highly suggest you shut down any "
+"unneeded services on the router until we have a chance to get the firewall "
+"up and rolling. To view the currently running services, just run <c>rc-"
+"status</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):75
+msgid "Kernel setup (know thyself first)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):79
+msgid ""
+"Your kernel needs to have the drivers running for both your NICs. To see if "
+"your cards are already setup, just run <c>ifconfig</c>. Your output may "
+"differ slightly from the following, that's fine. What matters is that the "
+"interface shows up at all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):86
+msgid "Checking NICs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):86
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ifconfig -a</i>\n"
+"eth0      Link encap:Ethernet  HWaddr 00:60:F5:07:07:B8\n"
+"          BROADCAST MULTICAST  MTU:1500  Metric:1\n"
+"          RX packets:0 errors:0 dropped:0 overruns:0 frame:0\n"
+"          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0\n"
+"          collisions:0 txqueuelen:1000\n"
+"          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)\n"
+"          Interrupt:11 Base address:0x9800\n"
+"\n"
+"eth1      Link encap:Ethernet  HWaddr 00:60:F5:07:07:B9\n"
+"          BROADCAST MULTICAST  MTU:1500  Metric:1\n"
+"          RX packets:0 errors:0 dropped:0 overruns:0 frame:0\n"
+"          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0\n"
+"          collisions:0 txqueuelen:1000\n"
+"          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)\n"
+"          Interrupt:10 Base address:0x9400\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):105
+msgid ""
+"If you do not see your two cards showing up and you're not sure what kind of "
+"cards you have, try running <c>lspci | grep Ethernet</c>. You can get that "
+"from <c>emerge pciutils</c>. Once you have this information, go into your "
+"kernel and add support for the correct drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):112
+msgid ""
+"The next thing you'll need is support for iptables and NAT (and packet "
+"shaping if you want). The following list is split up into always required "
+"(*), required only for adsl via PPPoE (a), suggested for everyone (x), and "
+"only for shaper (s) features. It does not matter whether you build the "
+"features into the kernel or as a module so long as when the feature is "
+"needed, the correct module(s) are loaded (module loading is left to the "
+"reader as a fun exercise however)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):122
+msgid "Network Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):122
+#, no-wrap
+msgid ""
+"\n"
+"Networking options  ---&gt;\n"
+"   [*] TCP/IP networking\n"
+"      [*] IP: advanced router\n"
+"   [*] Network packet filtering (replaces ipchains)\n"
+"<comment>If you use 2.4.x, you have to enable the following for DHCP:</comment>\n"
+"   [*] Socket Filtering\n"
+"\n"
+"   IP: Netfilter Configuration  ---&gt;\n"
+"      [*] Connection tracking (required for masq/NAT)\n"
+"         [x] FTP protocol support\n"
+"         [x] IRC protocol support\n"
+"      [*] IP tables support (required for filtering/masq/NAT)\n"
+"         [*] IP range match support\n"
+"         [x] MAC address match support\n"
+"         [*] Multiple port match support\n"
+"         [*] Packet filtering\n"
+"            [*] REJECT target support\n"
+"            [x] REDIRECT target support\n"
+"         [*] Full NAT\n"
+"            [*] MASQUERADE target support\n"
+"         [s] Packet mangling\n"
+"            [s] MARK target support\n"
+"         [x] LOG target support\n"
+"\n"
+"   QoS and/or fair queueing  ---&gt;\n"
+"      [s] QoS and/or fair queueing\n"
+"         [s] HTB packet scheduler\n"
+"         [s] Ingress Qdisc\n"
+"\n"
+"   [a] PPP (point-to-point protocol) support\n"
+"      [a] PPP filtering\n"
+"      [a] PPP support for async serial ports\n"
+"      [a] PPP support for sync tty ports\n"
+"      [a] PPP Deflate compression\n"
+"      [a] PPP BSD-Compress compression\n"
+"      [a] PPP over Ethernet\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):161
+msgid ""
+"Some things may be slightly different in a 2.4 vs 2.6 kernel, but you should "
+"be able to figure it out :). Even among 2.6 kernels, these options have a "
+"tendency to move around. Good luck!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):172
+msgid "Hug the WAN (a.k.a. The Internet)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):175
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):494
+msgid "Intro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):178
+msgid ""
+"There are many ways to connect to the internet so I'll just cover the ones "
+"I'm familiar with. That leaves us with ADSL (PPPoE) and cable modems (static/"
+"dynamic). If there are other methods out there, feel free to write up a "
+"little blurb and e-mail me. Feel free to skip any of the following sections "
+"in this chapter that don't apply to you. This chapter is just about getting "
+"the router connected to the internet via eth1."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):190
+msgid "ADSL and PPPoE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):193
+msgid ""
+"All the fancy PPPoE software that used to be provided by rp-pppoe (<uri link="
+"\"http://www.roaringpenguin.com/\">Roaring Penguin</uri>) has been "
+"integrated into the <uri link=\"http://samba.org/ppp/\">standard PPP "
+"package</uri>. Simply <c>emerge ppp</c> and you'll be on your way. Remember "
+"how I said you'll need username/password information? Well I wasn't lying so "
+"I hope you have it now! Load up <path>/etc/conf.d/net</path> in your "
+"favorite editor and set it up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):203
+msgid ""
+"In order for the following net settings to work, you must have "
+"baselayout-1.12.9 or later installed on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):208
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):259
+msgid "Setting up eth1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):208
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace 'vla9h924' with your username and 'boogie' with your password)</comment>\n"
+"\n"
+"# <i>nano /etc/conf.d/net</i>\n"
+"<comment>Tell baselayout to use adsl over eth1 for ppp0:</comment>\n"
+"config_ppp0=( \"ppp\" )\n"
+"link_ppp0=\"eth1\"\n"
+"plugins_ppp0=( \"pppoe\" )\n"
+"pppd_ppp0=(\n"
+"  \"defaultroute\"\n"
+"  \"usepeerdns\"\n"
+"  <comment>There may be other settings you want, see /etc/conf.d/net.example</comment>\n"
+")\n"
+"username_ppp0=\"vla9h924\"\n"
+"password_ppp0=\"boogie\"\n"
+"\n"
+"# <i>ln -s net.lo /etc/init.d/net.ppp0</i>\n"
+"# <i>rc-update add net.ppp0 default</i>\n"
+"# <i>/etc/init.d/net.ppp0 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(warn):229
+msgid ""
+"When the DSL interface comes up, it will create ppp0. Although your NIC is "
+"called eth1, the IP is actually bound to ppp0. From now on, when you see "
+"examples that utilize 'eth1', substitute with 'ppp0'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(warn):235
+msgid ""
+"Make sure you change the permissions of the /etc/conf.d/net file so that "
+"only root can read/write it since you're sticking your username/password in "
+"it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(warn):240
+msgid ""
+"For people transitioning from the <c>rp-pppoe</c> package, or for people who "
+"hit weird connection resets, see the MTU section in the Troubleshooting "
+"chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):250
+msgid "Cable and/or dynamic/static IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):253
+msgid ""
+"If you have a static IP then you will need a few more details than if you "
+"have a dynamic IP. For static users, you will need your IP, gateway, and DNS "
+"servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):259
+#, no-wrap
+msgid ""
+"\n"
+"<comment>Dynamic IP Users:</comment>\n"
+"# <i>emerge dhcpcd</i>\n"
+"# <i>nano /etc/conf.d/net</i>\n"
+"<comment>You'll need an entry like so:</comment>\n"
+"config_eth1=( \"dhcp\" )\n"
+"\n"
+"<comment>Static IP Users:</comment>\n"
+"# <i>nano /etc/conf.d/net</i>\n"
+"<comment>You'll need entries like so:</comment>\n"
+"config_eth1=( \"66.92.78.102 broadcast 66.92.78.255 netmask 255.255.255.0\" )\n"
+"routes_eth1=( \"default gw 66.92.78.1\" )\n"
+"# <i>nano /etc/resolv.conf</i>\n"
+"<comment>Add one line per DNS server:</comment>\n"
+"nameserver 123.123.123.123\n"
+"\n"
+"<comment>Dynamic and Static Setup:</comment>\n"
+"# <i>ln -s net.lo /etc/init.d/net.eth1</i>\n"
+"# <i>rc-update add net.eth1 default</i>\n"
+"# <i>/etc/init.d/net.eth1 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):281
+msgid "You should be all set to go now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):290
+msgid "Hug the LAN (bring along some friends)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):294
+msgid "This step is a breeze compared to the previous one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):298
+msgid "Setting up eth0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):298
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/net</i>\n"
+"<comment>Add a line like the following:</comment>\n"
+"config_eth0=( \"192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0\" )\n"
+"# <i>rc-update add net.eth0 default</i>\n"
+"# <i>/etc/init.d/net.eth0 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):311
+msgid "LAN Services (because we're nice people)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):314
+msgid "DHCP Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):317
+msgid ""
+"I bet it'd be nice if everyone else in your house could just plug their "
+"computers into the network and things would just work. No need to remember "
+"mind-numbing details or make them stare at confusing configuration screens! "
+"Life would be grand eh? Introducing the Dynamic Host Configuration Protocol "
+"(DHCP) and why you should care."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):325
+msgid ""
+"DHCP is exactly what its name implies. It's a protocol that allows you to "
+"dynamically configure other hosts automatically. You run a DHCP server on "
+"the router, give it all the information about your network (valid IPs, DNS "
+"servers, gateways, etc...), and then when the other hosts start up, they run "
+"a DHCP client to automatically configure themselves. No fuss, no muss! For "
+"more information about DHCP, you can always visit <uri link=\"http://en."
+"wikipedia.org/wiki/DHCP\">Wikipedia</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):335
+msgid ""
+"We'll use a package called dnsmasq which provides both DHCP and DNS "
+"services. For now lets just focus on the DHCP aspect. Note that if you want "
+"to run a different DHCP server, you can find another example in the Fun "
+"Things chapter. Also, if you wish to tinker with the DHCP server settings, "
+"just read the comments in <path>/etc/dnsmasq.conf</path>. All the defaults "
+"should work fine though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):344
+msgid "Setting up a DHCP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):344
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge dnsmasq</i>\n"
+"# <i>nano /etc/dnsmasq.conf</i>\n"
+"<comment>Add this line to enable dhcp:</comment>\n"
+"dhcp-range=192.168.0.100,192.168.0.250,72h\n"
+"<comment>Restrict dnsmasq to just the LAN interface</comment>\n"
+"interface=eth0\n"
+"\n"
+"# <i>rc-update add dnsmasq default</i>\n"
+"# <i>/etc/init.d/dnsmasq start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):356
+msgid ""
+"Now your little router is a bona-fide DHCP server! Plugin those computers "
+"and watch them work! With Windows systems you should go into the TCP/IP "
+"Properties and select the 'Obtain an IP address automatically' and 'Obtain "
+"DNS server address automatically' options. Sometimes the changes aren't "
+"instantaneous, so you may have to open a command prompt and run <c>ipconfig /"
+"release</c> and <c>ipconfig /renew</c>. But enough about Windows, let's get "
+"back to our favorite penguin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):370
+msgid "DNS Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):373
+msgid ""
+"When people want to visit a place on the internet, they remember names, not "
+"a string of funky numbers. After all, what's easier to remember, ebay.com or "
+"66.135.192.87? This is where the DNS steps in. DNS servers run all over the "
+"internet, and whenever someone wants to visit 'ebay.com', these servers turn "
+"'ebay.com' (what we understand) into '66.135.192.87' (what our computers "
+"understand). For more information about DNS, you can always visit <uri link="
+"\"http://en.wikipedia.org/wiki/DNS\">Wikipedia</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):383
+msgid ""
+"Since we're using dnsmasq for our DHCP server, and it includes a DNS server, "
+"you've got nothing left to do here! Your little router is already providing "
+"DNS to its DHCP clients. Bet you wish everything was this easy ;)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):389
+msgid ""
+"You're welcome to choose other DNS servers if you're more comfortable with "
+"them, but the reason dnsmasq is great is because it was designed to do "
+"exactly what we want and nothing more. It's a little DNS caching/forwarding "
+"server for local networks. We're not looking to provide DNS for our own "
+"domain here, just offer simple DNS services to everyone else on our LAN."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):401
+msgid "NAT (a.k.a. IP-masquerading)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):404
+msgid ""
+"At this point, people on your network can talk to each other and they can "
+"look up hostnames via DNS, but they still can't actually connect to the "
+"internet. While you may think that's great (more bandwidth for you!), I bet "
+"they're not too happy just yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):411
+msgid ""
+"This is where Network Address Translation (NAT) steps in. NAT is a way of "
+"connecting multiple computers in a private LAN to the internet when you have "
+"a smaller number of public IP addresses available to you. Typically you are "
+"given 1 IP by your ISP, but you want to let your whole house connect to the "
+"internet. NAT is the magic that makes this possible. For more information "
+"about NAT, you can always visit <uri link=\"http://en.wikipedia.org/wiki/NAT"
+"\">Wikipedia</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):420
+msgid ""
+"Before we get started, make sure you have iptables on your system. Although "
+"it is automatically installed on most systems, you may not have it. If you "
+"don't, just run <c>emerge iptables</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):426
+msgid "Setting up iptables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):426
+#, no-wrap
+msgid ""
+"\n"
+"<comment>First we flush our current rules</comment>\n"
+"# <i>iptables -F</i>\n"
+"# <i>iptables -t nat -F</i>\n"
+"\n"
+"<comment>Setup default policies to handle unmatched traffic</comment>\n"
+"# <i>iptables -P INPUT ACCEPT</i>\n"
+"# <i>iptables -P OUTPUT ACCEPT</i>\n"
+"# <i>iptables -P FORWARD DROP</i>\n"
+"\n"
+"<comment>Copy and paste these examples ...</comment>\n"
+"# <i>export LAN=eth0</i>\n"
+"# <i>export WAN=eth1</i>\n"
+"\n"
+"<comment>Then we lock our services so they only work from the LAN</comment>\n"
+"# <i>iptables -I INPUT 1 -i ${LAN} -j ACCEPT</i>\n"
+"# <i>iptables -I INPUT 1 -i lo -j ACCEPT</i>\n"
+"# <i>iptables -A INPUT -p UDP --dport bootps ! -i ${LAN} -j REJECT</i>\n"
+"# <i>iptables -A INPUT -p UDP --dport domain ! -i ${LAN} -j REJECT</i>\n"
+"\n"
+"<comment>(Optional) Allow access to our ssh server from the WAN</comment>\n"
+"# <i>iptables -A INPUT -p TCP --dport ssh -i ${WAN} -j ACCEPT</i>\n"
+"\n"
+"<comment>Drop TCP / UDP packets to privileged ports</comment>\n"
+"# <i>iptables -A INPUT -p TCP ! -i ${LAN} -d 0/0 --dport 0:1023 -j DROP</i>\n"
+"# <i>iptables -A INPUT -p UDP ! -i ${LAN} -d 0/0 --dport 0:1023 -j DROP</i>\n"
+"\n"
+"<comment>Finally we add the rules for NAT</comment>\n"
+"# <i>iptables -I FORWARD -i ${LAN} -d 192.168.0.0/255.255.0.0 -j DROP</i>\n"
+"# <i>iptables -A FORWARD -i ${LAN} -s 192.168.0.0/255.255.0.0 -j ACCEPT</i>\n"
+"# <i>iptables -A FORWARD -i ${WAN} -d 192.168.0.0/255.255.0.0 -j ACCEPT</i>\n"
+"# <i>iptables -t nat -A POSTROUTING -o ${WAN} -j MASQUERADE</i>\n"
+"<comment>Tell the kernel that ip forwarding is OK</comment>\n"
+"# <i>echo 1 &gt; /proc/sys/net/ipv4/ip_forward</i>\n"
+"# <i>for f in /proc/sys/net/ipv4/conf/*/rp_filter ; do echo 1 &gt; $f ; done</i>\n"
+"\n"
+"<comment>This is so when we boot we don't have to run the rules by hand</comment>\n"
+"# <i>/etc/init.d/iptables save</i>\n"
+"# <i>rc-update add iptables default</i>\n"
+"# <i>nano /etc/sysctl.conf</i>\n"
+"<comment>Add/Uncomment the following lines:</comment>\n"
+"net.ipv4.ip_forward = 1\n"
+"net.ipv4.conf.default.rp_filter = 1\n"
+"\n"
+"<comment>If you have a dynamic internet address you probably want to enable this:</comment>\n"
+"net.ipv4.ip_dynaddr = 1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):474
+msgid ""
+"Once you've typed out all of that, the rest of your network should now be "
+"able to use the internet as if they were directly connected themselves."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):479
+msgid ""
+"The ip_dynaddr option is useful for dial on demand systems or when your ISP "
+"gives out dynamic addresses. This works around the problem where a "
+"connection is attempted before the internet interface is fully setup. Really "
+"this just provides for a smoother network experience for users behind your "
+"router."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):491
+msgid "Fun Things (for a rainy day)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):497
+msgid ""
+"Believe it or not, you're done :). From here on out, I'll cover a bunch of "
+"common topics that may interest you. Everything in this chapter is "
+"completely optional."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):507
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):510
+msgid ""
+"Sometimes you would like to be able to host services on a computer behind "
+"the router, or just to make your life easier when connecting remotely. "
+"Perhaps you want to run a FTP, HTTP, SSH, or VNC server on one or more "
+"machines behind your router and be able to connect to them all. The only "
+"caveat is that you can only have one service/machine combo per port. For "
+"example, there is no practical way to setup three FTP servers behind your "
+"router and then try to connect to them all through port 21; only one can be "
+"on port 21 while the others would have to be on say port 123 and port 567."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):521
+msgid ""
+"All the port forwarding rules are of the form <c>iptables -t nat -A "
+"PREROUTING [-p protocol] --dport [external port on router] -i ${WAN} -j DNAT "
+"--to [ip/port to forward to]</c>. Unfortunately, iptables does not accept "
+"hostnames when port forwarding. If you are forwarding an external port to "
+"the same port on the internal machine, you can omit the destination port. "
+"See the iptables(8) man page for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):530
+msgid "Running the iptables commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):530
+#, no-wrap
+msgid ""
+"\n"
+"<comment>Copy and paste these examples ...</comment>\n"
+"# <i>export LAN=eth0</i>\n"
+"# <i>export WAN=eth1</i>\n"
+"\n"
+"<comment>Forward port 2 to ssh on an internal host</comment>\n"
+"# <i>iptables -t nat -A PREROUTING -p tcp --dport 2 -i ${WAN} -j DNAT --to 192.168.0.2:22</i>\n"
+"\n"
+"<comment>FTP forwarding to an internal host</comment>\n"
+"# <i>iptables -t nat -A PREROUTING -p tcp --dport 21 -i ${WAN} -j DNAT --to 192.168.0.56</i>\n"
+"\n"
+"<comment>HTTP forwarding to an internal host</comment>\n"
+"# <i>iptables -t nat -A PREROUTING -p tcp --dport 80 -i ${WAN} -j DNAT --to 192.168.0.56</i>\n"
+"\n"
+"<comment>VNC forwarding for internal hosts</comment>\n"
+"# <i>iptables -t nat -I PREROUTING -p tcp --dport 5900 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n"
+"# <i>iptables -t nat -I PREROUTING -p tcp --dport 5901 -i ${WAN} -j DNAT --to 192.168.0.3:5900</i>\n"
+"<comment>If you want to VNC in to 192.168.0.3, then just add ':1' to the router's hostname</comment>\n"
+"\n"
+"<comment>SAMBA forwarding to an internal host (excess ports to cover Windows)</comment>\n"
+"# <i>iptables -t nat -I PREROUTING -p tcp --dport 135 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n"
+"# <i>iptables -t nat -I PREROUTING -p tcp --dport 139 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n"
+"# <i>iptables -t nat -I PREROUTING -p tcp --dport 445 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n"
+"# <i>iptables -t nat -I PREROUTING -p udp --dport 137:138 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n"
+"# <i>iptables -t nat -I PREROUTING -p udp --dport 445 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n"
+"\n"
+"<comment>Bittorrent forwarding</comment>\n"
+"# <i>iptables -t nat -A PREROUTING -p tcp --dport 6881:6889 -i ${WAN} -j DNAT --to 192.168.0.2</i>\n"
+"\n"
+"<comment>eDonkey/eMule forwarding</comment>\n"
+"# <i>iptables -t nat -A PREROUTING -p tcp --dport 4662 -i ${WAN} -j DNAT --to 192.168.0.55</i>\n"
+"\n"
+"<comment>Game Cube Warp Pipe support</comment>\n"
+"# <i>iptables -t nat -A PREROUTING -p udp --dport 4000 -i ${WAN} -j DNAT --to 192.168.0.56</i>\n"
+"\n"
+"<comment>Playstation 2 Online support</comment>\n"
+"# <i>iptables -t nat -A PREROUTING -p tcp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>\n"
+"# <i>iptables -t nat -A PREROUTING -p udp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>\n"
+"\n"
+"<comment>Xbox Live</comment>\n"
+"# <i>iptables -t nat -A PREROUTING -p tcp --dport 3074 -i ${WAN} -j DNAT --to 192.168.0.69</i>\n"
+"# <i>iptables -t nat -A PREROUTING -p udp --dport 3074 -i ${WAN} -j DNAT --to 192.168.0.69</i>\n"
+"# <i>iptables -t nat -A PREROUTING -p udp --dport 88 -i ${WAN} -j DNAT --to 192.168.0.69</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):575
+msgid ""
+"If you have other common / cool examples, please <mail link=\"vapier@gentoo."
+"org\">e-mail me</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):584
+msgid "Identd (for IRC)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):587
+msgid ""
+"Internet Relay Chat utilizes the ident service pretty heavily. Now that the "
+"IRC clients are behind the router, we need a way to host ident for both the "
+"router and the clients. One such server has been created called <c>midentd</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):594
+msgid "Setting up ident"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):594
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge midentd</i>\n"
+"# <i>rc-update add midentd default</i>\n"
+"# <i>/etc/init.d/midentd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):600
+msgid ""
+"There are a few other ident servers in portage. Depending on your needs, I "
+"would recommend checking out <c>oidentd</c> and <c>fakeidentd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):682
+msgid "Time Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):685
+msgid ""
+"Keeping your system time correct is essential in maintaining a healthy "
+"system. One of the most common ways of accomplishing this is with the "
+"Network Time Protocol (NTP) and the ntp package (which provides "
+"implementations for both server and client)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):692
+msgid ""
+"Many people run ntp clients on their computers. Obviously, the more clients "
+"in the world, the larger the load the ntp servers need to shoulder. In "
+"environments like home networks though, we can help keep the load down on "
+"public servers while still providing the proper time to all our computers. "
+"As an added bonus, our private updates will be a lot faster for the clients "
+"too! All we have to do is run a ntp server on our router that synchronizes "
+"itself with the public internet servers while providing the time to the rest "
+"of the computers in the network. To get started, simply <c>emerge ntp</c> on "
+"the router."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):704
+msgid "Setting up the NTP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):704
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/ntp-client</i>\n"
+"<comment>Customize if you wish but the defaults should be fine</comment>\n"
+"# <i>rc-update add ntp-client default</i>\n"
+"\n"
+"# <i>nano /etc/ntp.conf</i>\n"
+"<comment>Add the follwing lines:</comment>\n"
+"restrict default ignore\n"
+"restrict 192.168.0.0 mask 255.255.255.0 notrust nomodify notrap\n"
+"<comment>These will allow only ntp clients with an IP\n"
+"address in the 192.168.0.xxx range to use your ntp server</comment>\n"
+"# <i>nano /etc/conf.d/ntpd</i>\n"
+"<comment>Customize if you wish but the defaults should be fine</comment>\n"
+"# <i>rc-update add ntpd default</i>\n"
+"\n"
+"# <i>/etc/init.d/ntp-client start</i>\n"
+"# <i>/etc/init.d/ntpd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):723
+msgid ""
+"You should make sure that you allow inbound and outbound communication on "
+"the ntp port (123/udp) when setting up the server. The client just needs "
+"outbound access on port 123 over udp."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):729
+msgid ""
+"Now, on your clients, have them <c>emerge ntp</c> also. However, we will "
+"just run the ntp client so setup is a lot simpler."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):734
+msgid "Setting up a NTP client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):734
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/ntp-client</i>\n"
+"<comment>Change the 'pool.ntp.org' server in the NTPCLIENT_OPTS variable to '192.168.0.1'</comment>\n"
+"# <i>rc-update add ntp-client default</i>\n"
+"# <i>/etc/init.d/ntp-client start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):745
+msgid "Rsync Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):748
+msgid ""
+"For those who run multiple Gentoo boxes on the same lan, you often want to "
+"keep from having every machine running <c>emerge sync</c> with remote "
+"servers. By setting up a local rsync, you save on both your bandwidth and "
+"the Gentoo rsync servers' bandwidth. It's pretty simple to do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(note):755
+msgid ""
+"For a much more in-depth rsync guide, please see the official <uri link=\"/"
+"doc/en/rsync.xml#local\">rsync guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):760
+msgid ""
+"Since every Gentoo machine requires rsync, theres no need to emerge it. Edit "
+"the default <path>/etc/rsyncd.conf</path> config file, uncomment the <c>"
+"[gentoo-portage]</c> section, and make sure you add an <c>address</c> "
+"option. All the other defaults should be fine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):767
+msgid "Rsync server config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):767
+#, no-wrap
+msgid ""
+"\n"
+"pid file = /var/run/rsyncd.pid\n"
+"use chroot = yes\n"
+"read only = yes\n"
+"address = 192.168.0.1\n"
+"\n"
+"[gentoo-portage]\n"
+"  path = /mnt/space/portage\n"
+"  comment = Gentoo Linux Portage tree\n"
+"  exclude = /distfiles /packages\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):779
+msgid "Then you need to start the service (again, the defaults are OK)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):783
+msgid "Starting the rsync server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):783
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/rsyncd start</i>\n"
+"# <i>rc-update add rsyncd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):788
+msgid "Only thing left is to set tell your clients to sync against the router."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):792
+msgid "Client SYNC settings in make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):792
+#, no-wrap
+msgid ""
+"\n"
+"SYNC=\"rsync://192.168.0.1/gentoo-portage\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):800
+msgid "Mail Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):803
+msgid ""
+"Sometimes it's nice to run your own Simple Mail Transfer Protocol (SMTP) "
+"server on the router. You may have your own reason for wanting to do so, but "
+"I run it so that the users see mail as being sent instantly and the work of "
+"retrying/routing is left up to the mail server. Some ISPs also don't allow "
+"for mail relaying for accounts that aren't part of their network (like "
+"Verizon). Also, you can easily throttle the delivery of mail so that large "
+"attachments won't seriously lag your connection for half an hour."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):813
+msgid "Setting up SMTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):813
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge netqmail</i>\n"
+"<comment>make sure the output of `hostname` is correct</comment>\n"
+"# <i>emerge --config netqmail</i>\n"
+"# <i>iptables -I INPUT -p tcp --dport smtp ! -i ${LAN} -j REJECT</i>\n"
+"# <i>ln -s /var/qmail/supervise/qmail-send /service/qmail-send</i>\n"
+"# <i>ln -s /var/qmail/supervise/qmail-smtpd /service/qmail-smtpd</i>\n"
+"# <i>cd /etc/tcprules.d</i>\n"
+"# <i>nano tcp.qmail-smtp</i>\n"
+"\n"
+"<comment>Add an entry like so to the allow section:</comment>\n"
+"192.168.0.:allow,RELAYCLIENT=\"\"\n"
+"\n"
+"# <i>make</i>\n"
+"# <i>rc-update add svscan default</i>\n"
+"# <i>/etc/init.d/svscan start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):837
+msgid ""
+"I'm a huge fan of qmail, but you're free to use a different mta :). When you "
+"setup e-mail on the hosts in your network, tell them that their SMTP server "
+"is 192.168.0.1 and everything should be peachy. You might want to visit the "
+"<uri link=\"http://netqmail.org/\">netqmail homepage</uri> for more "
+"documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):867
+msgid "Full DHCP Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):870
+msgid ""
+"Earlier we used dnsmasq to provide DHCP service to all our clients. For most "
+"people with a simple small LAN, this is perfect. But you may need something "
+"with more features. Thus we turn to a full-featured DHCP server as provided "
+"by the <uri link=\"http://www.isc.org/products/DHCP\">ISC</uri> folks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):877
+msgid "Setting up dhcpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):877
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge dhcp</i>\n"
+"# <i>nano /etc/dhcp/dhcpd.conf</i>\n"
+"<comment>(Here is a sample configuration file:)</comment>\n"
+"authoritative;\n"
+"ddns-update-style interim;\n"
+"subnet 192.168.0.0 netmask 255.255.255.0 {\n"
+"    range 192.168.0.100 192.168.0.250;\n"
+"    default-lease-time 259200;\n"
+"    max-lease-time 518400;\n"
+"    option subnet-mask 255.255.255.0;\n"
+"    option broadcast-address 192.168.0.255;\n"
+"    option routers 192.168.0.1;\n"
+"    option domain-name-servers 192.168.0.1;\n"
+"}\n"
+"# <i>nano /etc/conf.d/dhcpd</i>\n"
+"<comment>(Set IFACE=\"eth0\")</comment>\n"
+"# <i>rc-update add dhcpd default</i>\n"
+"# <i>/etc/init.d/dhcpd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):898
+msgid ""
+"This is the minimal setup required to replace the dnsmasq DHCP functionality "
+"that we used earlier. Speaking of which, you did remember to disable the "
+"DHCP features in dnsmasq didn't you? If not, you should do so now (just "
+"comment out the <c>dhcp-range</c> setting in <path>/etc/dnsmasq.conf</path> "
+"and restart the service)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):910
+msgid "Connect Another LAN (or two or three or ...)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):913
+msgid ""
+"Sometimes you have need of connecting the router to another LAN. Maybe you "
+"want to hook up a group of friends temporarily, or you're a neat freak and "
+"want to section off different groups of computers, or you're just really "
+"really bored. Whatever the reasons, extending the router to other LAN "
+"networks should be pretty straightforward. In the following examples, I will "
+"assume that this new network is connected via a third ethernet card, namely "
+"<c>eth2</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):923
+msgid ""
+"First you need to configure the interface. Just take the instructions in the "
+"<uri link=\"#doc_chap4_pre1\">4.1 code listing</uri> and replace <c>eth0</c> "
+"with <c>eth2</c> and <c>192.168.0</c> with <c>192.168.1</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):929
+msgid ""
+"Then you need to tweak dnsmasq to service the new interface. Just edit the "
+"<path>/etc/conf.d/dnsmasq</path> file again and append <c>-i eth2</c> to "
+"DNSMASQ_OPTS; using -i multiple times is OK. Then edit <path>/etc/dnsmasq."
+"conf</path> and add another line like the dhcp-range line in the <uri link="
+"\"#doc_chap5_pre1\">5.1 code listing</uri>, replacing <c>192.168.0</c> with "
+"<c>192.168.1</c>. Having multiple dhcp-range lines is OK too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):939
+msgid ""
+"Finally, see the rules in the <uri link=\"#doc_chap5_pre2\">5.2 code "
+"listing</uri> and duplicate the rules that have <c>-i ${LAN}</c> in them. "
+"You may want to create another variable, say <c>LAN2</c>, to make things "
+"easier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):951
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):954
+msgid "Useful Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):957
+msgid ""
+"If you're having trouble getting your computers to communicate, you may way "
+"to try out the following tools (they can all be found in the <c>net-"
+"analyzer</c> portage category):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(th):965
+msgid "Utility"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(th):966
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):969
+msgid "wireshark"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):970
+msgid "GUI tool to view all raw network data according to filters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):973
+msgid "tcpdump"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):974
+msgid "Console tool to dump all raw network data according to filters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):977
+msgid "iptraf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):978
+msgid "ncurses based IP LAN monitor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):981
+msgid "ettercap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(ti):982
+msgid "ncurses based network monitor/control"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):990
+msgid "DHCP Fails To Start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):993
+msgid ""
+"When starting the dhcp init.d script for the first time, it may fail to load "
+"but neglect to give you any useful info."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):998
+msgid "DHCP Failing Example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):998
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/dhcp start</i>\n"
+" * Setting ownership on dhcp.leases ...          [ ok ]\n"
+" * Starting dhcpd ...                            [ !! ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1004
+msgid ""
+"The trick is to know where dhcpd is sending its output. Simply browse to "
+"<path>/var/log</path> and read the log files. Since the exact log file "
+"depends on the package you are using as a syslog, try running <c>grep -Rl "
+"dhcpd /var/log</c> to narrow down the possibilities. Chances are you made a "
+"typo in your config file. You could also try running <c>dhcpd -d -f</c> "
+"(short for debug / foreground) and debug the error based upon the output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):1017
+msgid "Incorrect MTU Value"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1020
+msgid ""
+"If you experience odd errors (such as not being able to access some webpages "
+"while others load fine), you may be having Path MTU Discovery trouble. The "
+"quick way to test is to run this iptables command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre:caption):1026
+msgid "Circumvent MTU issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(pre):1026
+#, no-wrap
+msgid ""
+"\n"
+"# <i>iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1030
+msgid ""
+"This will affect all new connections, so just refresh the website you're "
+"having problems with in order to test. In case it helps, the standard MTU "
+"value for 100mbit ethernet connections is <c>1500</c>; this value also "
+"applies to PPPoA. For PPPoE connections it is <c>1492</c>. For more info, "
+"you should read Chapter 15 of the <uri link=\"http://lartc.org/howto/"
+"\">Linux Advanced Routing &amp; Traffic Control HOWTO</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1039
+msgid ""
+"If that command does not work for you, you may want to try putting the rule "
+"into the mangle table. Simply add <c>-t mangle</c> to the command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):1048
+msgid "Unable to connect two machines directly"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1051
+msgid ""
+"If (for whatever reason) you want to connect two machines directly together "
+"without a hub or switch, a regular ethernet cable will likely not work, "
+"unless you have an Auto MDI/MDI-X (also known as \"autosensing\") capable "
+"network adapter. You will need a different cable called a crossover cable. "
+"This <uri link=\"http://en.wikipedia.org/wiki/Ethernet_crossover_cable"
+"\">Wikipedia</uri> page explains the low level details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(title):1066
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(p):1070
+msgid ""
+"I have no final notes other than if you experience any troubles with the "
+"guide, please contact <mail link=\"vapier@gentoo.org\">me</mail> or file a "
+"bug with <uri link=\"http://bugs.gentoo.org/\">Gentoo's Bugtracking Website</"
+"uri>. If you have some interesting bits you think would enhance this guide, "
+"by all means send it my way for inclusion."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//home-router-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/hpc-howto.xml.po b/doc/gettext/ru/hpc-howto.xml.po
new file mode 100644
index 0000000..03e9d49
--- /dev/null
+++ b/doc/gettext/ru/hpc-howto.xml.po
@@ -0,0 +1,1431 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):6
+msgid "High Performance Computing on Gentoo Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):9
+msgid "marc@adelielinux.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):9
+msgid "Marc St-Pierre"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):12
+msgid "benoit@adelielinux.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):12
+msgid "Benoit Morin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):17
+msgid "Assistant/Research"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):15
+msgid "jean-francois@adelielinux.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):15
+msgid "Jean-Francois Richard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):18
+msgid "olivier@adelielinux.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):18
+msgid "Olivier Crete"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):20
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):21
+msgid "dberkholz@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail):21
+msgid "Donnie Berkholz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#. No licensing information; this document has been written by a third-party
+#.      organisation without additional licensing information.
+#.
+#.      In other words, this is copyright adelielinux R&D; Gentoo only has
+#.      permission to distribute this document as-is and update it when appropriate
+#.      as long as the adelie linux R&D notice stays
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(abstract):35
+msgid ""
+"This document was written by people at the Adelie Linux R&amp;D Center &lt;"
+"http://www.adelielinux.com&gt; as a step-by-step guide to turn a Gentoo "
+"System into a High Performance Computing (HPC) system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(version):41
+msgid "1.7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(date):42
+msgid "2010-06-07"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):45
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):49
+msgid ""
+"Gentoo Linux, a special flavor of Linux that can be automatically optimized "
+"and customized for just about any application or need. Extreme performance, "
+"configurability and a top-notch user and developer community are all "
+"hallmarks of the Gentoo experience."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):56
+msgid ""
+"Thanks to a technology called Portage, Gentoo Linux can become an ideal "
+"secure server, development workstation, professional desktop, gaming system, "
+"embedded solution or... a High Performance Computing system. Because of its "
+"near-unlimited adaptability, we call Gentoo Linux a metadistribution."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):63
+msgid ""
+"This document explains how to turn a Gentoo system into a High Performance "
+"Computing system. Step by step, it explains what packages one may want to "
+"install and helps configure them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):69
+msgid ""
+"Obtain Gentoo Linux from the website <uri>http://www.gentoo.org</uri>, and "
+"refer to the <uri link=\"/doc/en/\">documentation</uri> at the same location "
+"to install it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):80
+msgid "Configuring Gentoo Linux for Clustering"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):82
+msgid "Recommended Optimizations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):85
+msgid ""
+"We refer to the <uri link=\"/doc/en/handbook/\">Gentoo Linux Handbooks</uri> "
+"in this section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):90
+msgid ""
+"During the installation process, you will have to set your USE variables in "
+"<path>/etc/make.conf</path>. We recommended that you deactivate all the "
+"defaults (see <path>/etc/make.profile/make.defaults</path>) by negating them "
+"in make.conf. However, you may want to keep such use variables as 3dnow, "
+"gpm, mmx, nptl, nptlonly, sse, ncurses, pam and tcpd. Refer to the USE "
+"documentation for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):99
+msgid "USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):99
+#, no-wrap
+msgid ""
+"\n"
+"USE=\"-oss 3dnow -apm -avi -berkdb -crypt -cups -encode -gdbm -gif gpm -gtk\n"
+"-imlib -java -jpeg -kde -gnome -libg++ -libwww -mikmod mmx -motif -mpeg ncurses\n"
+"-nls nptl nptlonly -ogg -opengl pam -pdflib -png -python -qt4 -qtmt\n"
+"-quicktime -readline -sdl -slang -spell -ssl -svga tcpd -truetype -vorbis -X\n"
+"-xml2 -xv -zlib\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):107
+msgid "Or simply:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):111
+msgid "USE Flags - simplified version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):111
+#, no-wrap
+msgid ""
+"\n"
+"USE=\"-* 3dnow gpm mmx ncurses pam sse tcpd\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):115
+msgid ""
+"The <e>tcpd</e> USE flag increases security for packages such as xinetd."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):119
+msgid ""
+"In step 15 (\"Installing the kernel and a System Logger\") for stability "
+"reasons, we recommend the vanilla-sources, the official kernel sources "
+"released on <uri>http://www.kernel.org/</uri>, unless you require special "
+"support such as xfs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):126
+msgid "Installing vanilla-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):126
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a syslog-ng vanilla-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):130
+msgid ""
+"When you install miscellaneous packages, we recommend installing the "
+"following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):135
+msgid "Installing necessary packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):135
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a nfs-utils portmap tcpdump ssmtp iptables xinetd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):142
+msgid "Communication Layer (TCP/IP Network)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):145
+msgid ""
+"A cluster requires a communication layer to interconnect the slave nodes to "
+"the master node. Typically, a FastEthernet or GigaEthernet LAN can be used "
+"since they have a good price/performance ratio. Other possibilities include "
+"use of products like <uri link=\"http://www.myricom.com/\">Myrinet</uri>, "
+"<uri link=\"http://quadrics.com/\">QsNet</uri> or others."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):153
+msgid ""
+"A cluster is composed of two node types: master and slave. Typically, your "
+"cluster will have one master node and several slave nodes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):158
+msgid ""
+"The master node is the cluster's server. It is responsible for telling the "
+"slave nodes what to do. This server will typically run such daemons as "
+"dhcpd, nfs, pbs-server, and pbs-sched. Your master node will allow "
+"interactive sessions for users, and accept job executions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):165
+msgid ""
+"The slave nodes listen for instructions (via ssh/rsh perhaps) from the "
+"master node. They should be dedicated to crunching results and therefore "
+"should not run any unnecessary services."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):171
+msgid ""
+"The rest of this documentation will assume a cluster configuration as per "
+"the hosts file below. You should maintain on every node such a hosts file "
+"(<path>/etc/hosts</path>) with entries for each node participating node in "
+"the cluster."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):178
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):178
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /etc/hosts\n"
+"\n"
+"127.0.0.1       localhost\n"
+"\n"
+"192.168.1.100   master.adelie master\n"
+"\n"
+"192.168.1.1     node01.adelie node01\n"
+"192.168.1.2     node02.adelie node02\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):190
+msgid ""
+"To setup your cluster dedicated LAN, edit your <path>/etc/conf.d/net</path> "
+"file on the master node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):195
+msgid "/etc/conf.d/net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):195
+#, no-wrap
+msgid ""
+"\n"
+"# Global config file for net.* rc-scripts\n"
+"\n"
+"# This is basically the ifconfig argument without the ifconfig $iface\n"
+"#\n"
+"\n"
+"iface_eth0=\"192.168.1.100 broadcast 192.168.1.255 netmask 255.255.255.0\"\n"
+"# Network Connection to the outside world using dhcp -- configure as required for you network\n"
+"iface_eth1=\"dhcp\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):207
+msgid ""
+"Finally, setup a DHCP daemon on the master node to avoid having to maintain "
+"a network configuration on each slave node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):212
+msgid "/etc/dhcp/dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):212
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /etc/dhcp/dhcpd.conf\n"
+"\n"
+"log-facility local7;\n"
+"ddns-update-style none;\n"
+"use-host-decl-names on;\n"
+"\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"        option domain-name \"adelie\";\n"
+"        range 192.168.1.10 192.168.1.99;\n"
+"        option routers 192.168.1.100;\n"
+"\n"
+"        host node01.adelie {\n"
+"                # MAC address of network card on node 01\n"
+"                hardware ethernet 00:07:e9:0f:e2:d4;\n"
+"                fixed-address 192.168.1.1;\n"
+"        }\n"
+"        host node02.adelie {\n"
+"                # MAC address of network card on node 02\n"
+"                hardware ethernet 00:07:e9:0f:e2:6b;\n"
+"                fixed-address 192.168.1.2;\n"
+"        }\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):241
+msgid "NFS/NIS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):244
+msgid ""
+"The Network File System (NFS) was developed to allow machines to mount a "
+"disk partition on a remote machine as if it were on a local hard drive. This "
+"allows for fast, seamless sharing of files across a network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):250
+msgid ""
+"There are other systems that provide similar functionality to NFS which "
+"could be used in a cluster environment. The <uri link=\"http://www.openafs."
+"org\">Andrew File System from IBM</uri>, recently open-sourced, provides a "
+"file sharing mechanism with some additional security and performance "
+"features. The <uri link=\"http://www.coda.cs.cmu.edu/\">Coda File System</"
+"uri> is still in development, but is designed to work well with disconnected "
+"clients. Many of the features of the Andrew and Coda file systems are slated "
+"for inclusion in the next version of <uri link=\"http://www.nfsv4.org\">NFS "
+"(Version 4)</uri>. The advantage of NFS today is that it is mature, "
+"standard, well understood, and supported robustly across a variety of "
+"platforms."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):264
+msgid "Ebuilds for NFS-support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):264
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a nfs-utils portmap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):268
+msgid "Configure and install a kernel to support NFS v3 on all nodes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):272
+msgid "Required Kernel Configurations for NFS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):272
+#, no-wrap
+msgid ""
+"\n"
+"CONFIG_NFS_FS=y\n"
+"CONFIG_NFSD=y\n"
+"CONFIG_SUNRPC=y\n"
+"CONFIG_LOCKD=y\n"
+"CONFIG_NFSD_V3=y\n"
+"CONFIG_LOCKD_V4=y\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):281
+msgid ""
+"On the master node, edit your <path>/etc/hosts.allow</path> file to allow "
+"connections from slave nodes. If your cluster LAN is on 192.168.1.0/24, your "
+"<path>hosts.allow</path> will look like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):287
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):446
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):457
+msgid "hosts.allow"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):287
+#, no-wrap
+msgid ""
+"\n"
+"portmap:192.168.1.0/255.255.255.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):291
+msgid ""
+"Edit the <path>/etc/exports</path> file of the master node to export a work "
+"directory structure (/home is good for this)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):296
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):826
+msgid "/etc/exports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):296
+#, no-wrap
+msgid ""
+"\n"
+"/home/  *(rw)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):300
+msgid "Add nfs to your master node's default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):304
+msgid "Adding NFS to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):304
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add nfs default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):308
+msgid ""
+"To mount the nfs exported filesystem from the master, you also have to "
+"configure your salve nodes' <path>/etc/fstab</path>. Add a line like this "
+"one:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):314
+msgid "/etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):314
+#, no-wrap
+msgid ""
+"\n"
+"master:/home/  /home  nfs  rw,exec,noauto,nouser,async  0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):318
+msgid ""
+"You'll also need to set up your nodes so that they mount the nfs filesystem "
+"by issuing this command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):323
+msgid "Adding nfsmount to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):323
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add nfsmount default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):330
+msgid "RSH/SSH"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):333
+msgid ""
+"SSH is a protocol for secure remote login and other secure network services "
+"over an insecure network. OpenSSH uses public key cryptography to provide "
+"secure authorization. Generating the public key, which is shared with remote "
+"systems, and the private key which is kept on the local system, is done "
+"first to configure OpenSSH on the cluster."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):341
+msgid ""
+"For transparent cluster usage, private/public keys may be used. This process "
+"has two steps:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):347
+msgid "Generate public and private keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):348
+msgid "Copy public key to slave nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):351
+msgid "For user based authentication, generate and copy as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):355
+msgid "SSH key authentication"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):355
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ssh-keygen -t dsa</i>\n"
+"Generating public/private dsa key pair.\n"
+"Enter file in which to save the key (/root/.ssh/id_dsa): /root/.ssh/id_dsa\n"
+"Enter passphrase (empty for no passphrase):\n"
+"Enter same passphrase again:\n"
+"Your identification has been saved in /root/.ssh/id_dsa.\n"
+"Your public key has been saved in /root/.ssh/id_dsa.pub.\n"
+"The key fingerprint is:\n"
+"f1:45:15:40:fd:3c:2d:f7:9f:ea:55:df:76:2f:a4:1f root@master\n"
+"\n"
+"<comment>WARNING! If you already have an \"authorized_keys\" file,\n"
+"please append to it, do not use the following command.</comment>\n"
+"\n"
+"# <i>scp /root/.ssh/id_dsa.pub node01:/root/.ssh/authorized_keys</i>\n"
+"root@master's password:\n"
+"id_dsa.pub   100%  234     2.0MB/s   00:00\n"
+"\n"
+"# <i>scp /root/.ssh/id_dsa.pub node02:/root/.ssh/authorized_keys</i>\n"
+"root@master's password:\n"
+"id_dsa.pub   100%  234     2.0MB/s   00:00\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):378
+msgid ""
+"Host keys must have an empty passphrase. RSA is required for host-based "
+"authentication."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):383
+msgid ""
+"For host based authentication, you will also need to edit your <path>/etc/"
+"ssh/shosts.equiv</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):388
+msgid "/etc/ssh/shosts.equiv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):388
+#, no-wrap
+msgid ""
+"\n"
+"node01.adelie\n"
+"node02.adelie\n"
+"master.adelie\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):394
+msgid "And a few modifications to the <path>/etc/ssh/sshd_config</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):398
+msgid "sshd configurations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):398
+#, no-wrap
+msgid ""
+"\n"
+"# $OpenBSD: sshd_config,v 1.42 2001/09/20 20:57:51 mouring Exp $\n"
+"# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin\n"
+"\n"
+"# This is the sshd server system-wide configuration file. See sshd(8)\n"
+"# for more information.\n"
+"\n"
+"# HostKeys for protocol version 2\n"
+"HostKey /etc/ssh/ssh_host_rsa_key\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):409
+msgid ""
+"If your application require RSH communications, you will need to emerge "
+"<c>net-misc/netkit-rsh</c> and <c>sys-apps/xinetd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):414
+msgid "Installing necessary applicaitons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):414
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a xinetd</i>\n"
+"# <i>emerge -a netkit-rsh</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):419
+msgid ""
+"Then configure the rsh deamon. Edit your <path>/etc/xinet.d/rsh</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):423
+msgid "rsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):423
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /etc/xinetd.d/rsh\n"
+"\n"
+"service shell\n"
+"{\n"
+"        socket_type     = stream\n"
+"        protocol        = tcp\n"
+"        wait            = no\n"
+"        user            = root\n"
+"        group           = tty\n"
+"        server          = /usr/sbin/in.rshd\n"
+"        log_type        = FILE /var/log/rsh\n"
+"        log_on_success  = PID HOST USERID EXIT DURATION\n"
+"        log_on_failure  = USERID ATTEMPT\n"
+"        disable         = no\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):442
+msgid "Edit your <path>/etc/hosts.allow</path> to permit rsh connections:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):446
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /etc/hosts.allow\n"
+"\n"
+"in.rshd:192.168.1.0/255.255.255.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):453
+msgid "Or you can simply trust your cluster LAN:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):457
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /etc/hosts.allow\n"
+"\n"
+"ALL:192.168.1.0/255.255.255.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):464
+msgid ""
+"Finally, configure host authentication from <path>/etc/hosts.equiv</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):468
+msgid "hosts.equiv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):468
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /etc/hosts.equiv\n"
+"\n"
+"master\n"
+"node01\n"
+"node02\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):477
+msgid "And, add xinetd to your default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):481
+msgid "Adding xinetd to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):481
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add xinetd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):488
+msgid "NTP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):491
+msgid ""
+"The Network Time Protocol (NTP) is used to synchronize the time of a "
+"computer client or server to another server or reference time source, such "
+"as a radio or satellite receiver or modem. It provides accuracies typically "
+"within a millisecond on LANs and up to a few tens of milliseconds on WANs "
+"relative to Coordinated Universal Time (UTC) via a Global Positioning "
+"Service (GPS) receiver, for example. Typical NTP configurations utilize "
+"multiple redundant servers and diverse network paths in order to achieve "
+"high accuracy and reliability."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):502
+msgid ""
+"Select a NTP server geographically close to you from <uri link=\"http://www."
+"eecis.udel.edu/~mills/ntp/servers.html\">Public NTP Time Servers</uri>, and "
+"configure your <path>/etc/conf.d/ntp</path> and <path>/etc/ntp.conf</path> "
+"files on the master node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):509
+msgid "Master /etc/conf.d/ntp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):509
+#, no-wrap
+msgid ""
+"\n"
+"# /etc/conf.d/ntpd\n"
+"\n"
+"# NOTES:\n"
+"#  - NTPDATE variables below are used if you wish to set your\n"
+"#    clock when you start the ntp init.d script\n"
+"#  - make sure that the NTPDATE_CMD will close by itself ...\n"
+"#    the init.d script will not attempt to kill/stop it\n"
+"#  - ntpd will be used to maintain synchronization with a time\n"
+"#    server regardless of what NTPDATE is set to\n"
+"#  - read each of the comments above each of the variable\n"
+"\n"
+"# Comment this out if you dont want the init script to warn\n"
+"# about not having ntpdate setup\n"
+"NTPDATE_WARN=\"n\"\n"
+"\n"
+"# Command to run to set the clock initially\n"
+"# Most people should just uncomment this line ...\n"
+"# however, if you know what you're doing, and you\n"
+"# want to use ntpd to set the clock, change this to 'ntpd'\n"
+"NTPDATE_CMD=\"ntpdate\"\n"
+"\n"
+"# Options to pass to the above command\n"
+"# Most people should just uncomment this variable and\n"
+"# change 'someserver' to a valid hostname which you\n"
+"# can acquire from the URL's below\n"
+"NTPDATE_OPTS=\"-b ntp1.cmc.ec.gc.ca\"\n"
+"\n"
+"##\n"
+"# A list of available servers is available here:\n"
+"# http://www.eecis.udel.edu/~mills/ntp/servers.html\n"
+"# Please follow the rules of engagement and use a\n"
+"# Stratum 2 server (unless you qualify for Stratum 1)\n"
+"##\n"
+"\n"
+"# Options to pass to the ntpd process that will *always* be run\n"
+"# Most people should not uncomment this line ...\n"
+"# however, if you know what you're doing, feel free to tweak\n"
+"#NTPD_OPTS=\"\"\n"
+"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):551
+msgid ""
+"Edit your <path>/etc/ntp.conf</path> file on the master to setup an external "
+"synchronization source:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):556
+msgid "Master ntp.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):556
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /etc/ntp.conf\n"
+"\n"
+"# Synchronization source #1\n"
+"server ntp1.cmc.ec.gc.ca\n"
+"restrict ntp1.cmc.ec.gc.ca\n"
+"# Synchronization source #2\n"
+"server ntp2.cmc.ec.gc.ca\n"
+"restrict ntp2.cmc.ec.gc.ca\n"
+"stratum 10\n"
+"driftfile /etc/ntp.drift.server\n"
+"logfile /var/log/ntp\n"
+"broadcast 192.168.1.255\n"
+"restrict default kod\n"
+"restrict 127.0.0.1\n"
+"restrict 192.168.1.0 mask 255.255.255.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):575
+msgid ""
+"And on all your slave nodes, setup your synchronization source as your "
+"master node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):580
+msgid "Node /etc/conf.d/ntp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):580
+#, no-wrap
+msgid ""
+"\n"
+"# /etc/conf.d/ntpd\n"
+"\n"
+"NTPDATE_WARN=\"n\"\n"
+"NTPDATE_CMD=\"ntpdate\"\n"
+"NTPDATE_OPTS=\"-b master\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):588
+msgid "Node ntp.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):588
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /etc/ntp.conf\n"
+"\n"
+"# Synchronization source #1\n"
+"server master\n"
+"restrict master\n"
+"stratum 11\n"
+"driftfile /etc/ntp.drift.server\n"
+"logfile /var/log/ntp\n"
+"restrict default kod\n"
+"restrict 127.0.0.1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):602
+msgid "Then add ntpd to the default runlevel of all your nodes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):606
+msgid "Adding ntpd to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):606
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add ntpd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):610
+msgid ""
+"NTP will not update the local clock if the time difference between your "
+"synchronization source and the local clock is too great."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):618
+msgid "IPTABLES"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):621
+msgid "To setup a firewall on your cluster, you will need iptables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):625
+msgid "Installing iptables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):625
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a iptables</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):629
+msgid "Required kernel configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):633
+msgid "IPtables kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):633
+#, no-wrap
+msgid ""
+"\n"
+"CONFIG_NETFILTER=y\n"
+"CONFIG_IP_NF_CONNTRACK=y\n"
+"CONFIG_IP_NF_IPTABLES=y\n"
+"CONFIG_IP_NF_MATCH_STATE=y\n"
+"CONFIG_IP_NF_FILTER=y\n"
+"CONFIG_IP_NF_TARGET_REJECT=y\n"
+"CONFIG_IP_NF_NAT=y\n"
+"CONFIG_IP_NF_NAT_NEEDED=y\n"
+"CONFIG_IP_NF_TARGET_MASQUERADE=y\n"
+"CONFIG_IP_NF_TARGET_LOG=y\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):646
+msgid "And the rules required for this firewall:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):650
+msgid "rule-save"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):650
+#, no-wrap
+msgid ""
+"\n"
+"# Adelie Linux Research &amp; Development Center\n"
+"# /var/lib/iptables/rule-save\n"
+"\n"
+"*filter\n"
+":INPUT ACCEPT [0:0]\n"
+":FORWARD ACCEPT [0:0]\n"
+":OUTPUT ACCEPT [0:0]\n"
+"-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT\n"
+"-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT\n"
+"-A INPUT -s 192.168.1.0/255.255.255.0 -i eth1 -j ACCEPT\n"
+"-A INPUT -s 127.0.0.1 -i lo -j ACCEPT\n"
+"-A INPUT -p icmp -j ACCEPT\n"
+"-A INPUT -j LOG\n"
+"-A INPUT -j REJECT --reject-with icmp-port-unreachable\n"
+"COMMIT\n"
+"*nat\n"
+":PREROUTING ACCEPT [0:0]\n"
+":POSTROUTING ACCEPT [0:0]\n"
+":OUTPUT ACCEPT [0:0]\n"
+"-A POSTROUTING -s 192.168.1.0/255.255.255.0 -j MASQUERADE\n"
+"COMMIT\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):674
+msgid "Then add iptables to the default runlevel of all your nodes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):678
+msgid "Adding iptables to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):678
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add iptables default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):687
+msgid "HPC Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):689
+msgid "OpenPBS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):692
+msgid ""
+"The Portable Batch System (PBS) is a flexible batch queueing and workload "
+"management system originally developed for NASA. It operates on networked, "
+"multi-platform UNIX environments, including heterogeneous clusters of "
+"workstations, supercomputers, and massively parallel systems. Development of "
+"PBS is provided by Altair Grid Technologies."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):700
+msgid "Installing openpbs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):700
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a openpbs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):704
+msgid ""
+"OpenPBS ebuild does not currently set proper permissions on var-directories "
+"used by OpenPBS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):709
+msgid ""
+"Before starting using OpenPBS, some configurations are required. The files "
+"you will need to personalize for your system are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):715
+msgid "/etc/pbs_environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):716
+msgid "/var/spool/PBS/server_name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):717
+msgid "/var/spool/PBS/server_priv/nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):718
+msgid "/var/spool/PBS/mom_priv/config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):719
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):726
+msgid "/var/spool/PBS/sched_priv/sched_config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):722
+msgid "Here is a sample sched_config:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):726
+#, no-wrap
+msgid ""
+"\n"
+"#\n"
+"# Create queues and set their attributes.\n"
+"#\n"
+"#\n"
+"# Create and define queue upto4nodes\n"
+"#\n"
+"create queue upto4nodes\n"
+"set queue upto4nodes queue_type = Execution\n"
+"set queue upto4nodes Priority = 100\n"
+"set queue upto4nodes resources_max.nodect = 4\n"
+"set queue upto4nodes resources_min.nodect = 1\n"
+"set queue upto4nodes enabled = True\n"
+"set queue upto4nodes started = True\n"
+"#\n"
+"# Create and define queue default\n"
+"#\n"
+"create queue default\n"
+"set queue default queue_type = Route\n"
+"set queue default route_destinations = upto4nodes\n"
+"set queue default enabled = True\n"
+"set queue default started = True\n"
+"#\n"
+"# Set server attributes.\n"
+"#\n"
+"set server scheduling = True\n"
+"set server acl_host_enable = True\n"
+"set server default_queue = default\n"
+"set server log_events = 511\n"
+"set server mail_from = adm\n"
+"set server query_other_jobs = True\n"
+"set server resources_default.neednodes = 1\n"
+"set server resources_default.nodect = 1\n"
+"set server resources_default.nodes = 1\n"
+"set server scheduler_iteration = 60\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):763
+msgid ""
+"To submit a task to OpenPBS, the command <c>qsub</c> is used with some "
+"optional parameters. In the example below, \"-l\" allows you to specify the "
+"resources required, \"-j\" provides for redirection of standard out and "
+"standard error, and the \"-m\" will e-mail the user at beginning (b), end "
+"(e) and on abort (a) of the job."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):771
+msgid "Submitting a task"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):771
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(submit and request from OpenPBS that myscript be executed on 2 nodes)</comment>\n"
+"# <i>qsub -l nodes=2 -j oe -m abe myscript</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):776
+msgid ""
+"Normally jobs submitted to OpenPBS are in the form of scripts. Sometimes, "
+"you may want to try a task manually. To request an interactive shell from "
+"OpenPBS, use the \"-I\" parameter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):782
+msgid "Requesting an interactive shell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):782
+#, no-wrap
+msgid ""
+"\n"
+"# <i>qsub -I</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):786
+msgid "To check the status of your jobs, use the qstat command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):790
+msgid "Checking the status of the jobs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):790
+#, no-wrap
+msgid ""
+"\n"
+"# <i>qstat</i>\n"
+"Job id  Name  User   Time Use S Queue\n"
+"------  ----  ----   -------- - -----\n"
+"2.geist STDIN adelie 0        R upto1nodes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):800
+msgid "MPICH"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):803
+msgid ""
+"Message passing is a paradigm used widely on certain classes of parallel "
+"machines, especially those with distributed memory. MPICH is a freely "
+"available, portable implementation of MPI, the Standard for message-passing "
+"libraries."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):810
+msgid ""
+"The mpich ebuild provided by Adelie Linux allows for two USE flags: <e>doc</"
+"e> and <e>crypt</e>. <e>doc</e> will cause documentation to be installed, "
+"while <e>crypt</e> will configure MPICH to use <c>ssh</c> instead of <c>rsh</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):817
+msgid "Installing the mpich application"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):817
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a mpich</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):821
+msgid ""
+"You may need to export a mpich work directory to all your slave nodes in "
+"<path>/etc/exports</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):826
+#, no-wrap
+msgid ""
+"\n"
+"/home  *(rw)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):830
+msgid ""
+"Most massively parallel processors (MPPs) provide a way to start a program "
+"on a requested number of processors; <c>mpirun</c> makes use of the "
+"appropriate command whenever possible. In contrast, workstation clusters "
+"require that each process in a parallel job be started individually, though "
+"programs to help start these processes exist. Because workstation clusters "
+"are not already organized as an MPP, additional information is required to "
+"make use of them. Mpich should be installed with a list of participating "
+"workstations in the file <path>machines.LINUX</path> in the directory <path>/"
+"usr/share/mpich/</path>. This file is used by <c>mpirun</c> to choose "
+"processors to run on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):843
+msgid "Edit this file to reflect your cluster-lan configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):847
+msgid "/usr/share/mpich/machines.LINUX"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):847
+#, no-wrap
+msgid ""
+"\n"
+"# Change this file to contain the machines that you want to use\n"
+"# to run MPI jobs on. The format is one host name per line, with either\n"
+"#    hostname\n"
+"# or\n"
+"#    hostname:n\n"
+"# where n is the number of processors in an SMP. The hostname should\n"
+"# be the same as the result from the command \"hostname\"\n"
+"master\n"
+"node01\n"
+"node02\n"
+"# node03\n"
+"# node04\n"
+"# ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):863
+msgid ""
+"Use the script <c>tstmachines</c> in <path>/usr/sbin/</path> to ensure that "
+"you can use all of the machines that you have listed. This script performs "
+"an <c>rsh</c> and a short directory listing; this tests that you both have "
+"access to the node and that a program in the current directory is visible on "
+"the remote node. If there are any problems, they will be listed. These "
+"problems must be fixed before proceeding."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):872
+msgid ""
+"The only argument to <c>tstmachines</c> is the name of the architecture; "
+"this is the same name as the extension on the machines file. For example, "
+"the following tests that a program in the current directory can be executed "
+"by all of the machines in the LINUX machines list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):879
+msgid "Running a test"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):879
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/usr/local/mpich/sbin/tstmachines LINUX</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(note):883
+msgid ""
+"This program is silent if all is well; if you want to see what it is doing, "
+"use the -v (for verbose) argument:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):888
+msgid "Running a test verbosively"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):888
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/usr/local/mpich/sbin/tstmachines -v LINUX</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):892
+msgid "The output from this command might look like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):896
+msgid "Output of the above command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):896
+#, no-wrap
+msgid ""
+"\n"
+"Trying true on host1.uoffoo.edu ...\n"
+"Trying true on host2.uoffoo.edu ...\n"
+"Trying ls on host1.uoffoo.edu ...\n"
+"Trying ls on host2.uoffoo.edu ...\n"
+"Trying user program on host1.uoffoo.edu ...\n"
+"Trying user program on host2.uoffoo.edu ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):905
+msgid ""
+"If <c>tstmachines</c> finds a problem, it will suggest possible reasons and "
+"solutions. In brief, there are three tests:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):911
+msgid ""
+"<e>Can processes be started on remote machines?</e> tstmachines attempts to "
+"run the shell command true on each machine in the machines files by using "
+"the remote shell command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):916
+msgid ""
+"<e>Is current working directory available to all machines?</e> This attempts "
+"to ls a file that tstmachines creates by running ls using the remote shell "
+"command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):921
+msgid ""
+"<e>Can user programs be run on remote systems?</e> This checks that shared "
+"libraries and other components have been properly installed on all machines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):928
+msgid "And the required test for every development tool:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre:caption):932
+msgid "Testing a development tool"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(pre):932
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd ~</i>\n"
+"# <i>cp /usr/share/mpich/examples1/hello++.c ~</i>\n"
+"# <i>make hello++</i>\n"
+"# <i>mpirun -machinefile /usr/share/mpich/machines.LINUX -np 1 hello++</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):939
+msgid ""
+"For further information on MPICH, consult the documentation at <uri link="
+"\"http://www-unix.mcs.anl.gov/mpi/mpich/docs/mpichman-chp4/mpichman-chp4.htm"
+"\">http://www-unix.mcs.anl.gov/mpi/mpich/docs/mpichman-chp4/mpichman-chp4."
+"htm</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):947
+msgid "LAM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):950
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):960
+msgid "(Coming Soon!)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):957
+msgid "OMNI"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(title):969
+msgid "Bibliography"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(p):973
+msgid ""
+"The original document is published at the <uri link=\"http://www.adelielinux."
+"com\">Adelie Linux R&amp;D Centre</uri> web site, and is reproduced here "
+"with the permission of the authors and <uri link=\"http://www.cyberlogic.ca"
+"\">Cyberlogic</uri>'s Adelie Linux R&amp;D Centre."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):982
+msgid "<uri>http://www.gentoo.org</uri>, Gentoo Foundation, Inc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):983
+msgid ""
+"<uri link=\"http://www.adelielinux.com\">http://www.adelielinux.com</uri>, "
+"Adelie Linux Research and Development Centre"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):987
+msgid ""
+"<uri link=\"http://nfs.sourceforge.net/\">http://nfs.sourceforge.net</uri>, "
+"Linux NFS Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):991
+msgid ""
+"<uri link=\"http://www-unix.mcs.anl.gov/mpi/mpich/\">http://www-unix.mcs.anl."
+"gov/mpi/mpich/</uri>, Mathematics and Computer Science Division, Argonne "
+"National Laboratory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(uri:link):996
+msgid "http://www.ntp.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(uri):996
+msgid "http://ntp.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):998
+msgid ""
+"<uri link=\"http://www.eecis.udel.edu/~mills/\">http://www.eecis.udel.edu/"
+"~mills/</uri>, David L. Mills, University of Delaware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):1002
+msgid ""
+"<uri link=\"http://www.ietf.org/html.charters/secsh-charter.html\">http://"
+"www.ietf.org/html.charters/secsh-charter.html</uri>, Secure Shell Working "
+"Group, IETF, Internet Society"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):1006
+msgid ""
+"<uri link=\"http://www.linuxsecurity.com/\">http://www.linuxsecurity.com/</"
+"uri>, Guardian Digital"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(li):1010
+msgid ""
+"<uri link=\"http://www.openpbs.org/\">http://www.openpbs.org/</uri>, Altair "
+"Grid Technologies, LLC."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//hpc-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/index.xml.po b/doc/gettext/ru/index.xml.po
new file mode 100644
index 0000000..424768e
--- /dev/null
+++ b/doc/gettext/ru/index.xml.po
@@ -0,0 +1,101 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(version):10
+msgid "11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(title):12
+msgid "Gentoo Documentation Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(title):19
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(p):22
+msgid ""
+"Welcome to the Gentoo Documentation Resources. This page will give you a "
+"quick overview on the documentation we provide. Most documentation is "
+"released under the <uri link=\"http://creativecommons.org/licenses/by-"
+"sa/2.5\">Creative Commons - Attribution / Share Alike</uri> license, an open "
+"documentation license. All documentation should also be available in a "
+"printer-friendly format. To view this document, append <path>?"
+"style=printable</path> to the URL. You'll also find a \"Print\" link on the "
+"top-right corner of each document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(p):32
+msgid ""
+"If you find bugs in our documentation or have proposals, please use our <uri "
+"link=\"http://bugs.gentoo.org\">Bugtracking System</uri> and fill in a bug "
+"report for \"Documentation\" or \"Doc Other\". These bug reports will then "
+"be handled by the <uri link=\"/proj/en/gdp/\">Gentoo Documentation Project</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(title):42
+msgid "Documentation Repository"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(p):45
+msgid ""
+"Our documentation is <uri link=\"index.xml#doc_chap2\">categorized</uri> and "
+"hierarchically navigable. If you want a quick overview of all available "
+"documentation without the additional information, please use our <uri link="
+"\"list.xml\">Documentation Listing</uri> page. We also have a <uri link="
+"\"list.xml?desc=1\">full listing</uri> of all our documents with their "
+"descriptions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):59
+msgid "faq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):60
+msgid "install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):61
+msgid "desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):62
+msgid "upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):63
+msgid "gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):64
+msgid "sysadmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):65
+msgid "gentoodev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):66
+msgid "project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(catid):67
+msgid "other"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//index.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/info-guide.xml.po b/doc/gettext/ru/info-guide.xml.po
new file mode 100644
index 0000000..b939b20
--- /dev/null
+++ b/doc/gettext/ru/info-guide.xml.po
@@ -0,0 +1,533 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(guide:link):5
+msgid "/doc/en/info-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):6
+msgid "Gentoo Info Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(abstract):12
+msgid ""
+"This guide is meant to show how to navigate info pages using the info "
+"command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(version):20
+msgid "1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(date):21
+msgid "2006-03-28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):26
+msgid "What is info?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):29
+msgid ""
+"Most of you may be familiar with the <c>man</c> documentation system. While "
+"man is good with quickly looking up items, it lacks structure in linking man "
+"pages together. This is where <c>info</c> comes in. Info pages are made "
+"using the <c>texinfo</c> tools, and can link with other pages, create menus "
+"and ease navigation in general. The next section will look at how info pages "
+"are laid out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):41
+msgid "Info pages layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):44
+msgid ""
+"The main info pages are held in <path>/usr/share/info</path>. Unlike the man "
+"style directory layout, <path>/usr/share/info</path> contains what is "
+"largely a rather extensive collection of files. These files have the "
+"following format:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):50
+msgid "info file format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):50
+#, no-wrap
+msgid ""
+"\n"
+"pagename.info[-node].gz\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):54
+msgid ""
+"<c>pagename</c> is the actual name of the page (example: <c>wget</c>). <c>[-"
+"node]</c> is an optional construct that designates another node level "
+"(generally these are referenced to by the toplevel of the info document in "
+"question). In order to save space these info pages are compressed using the "
+"<c>gzip</c> compression scheme. Additional info pages can be listed with the "
+"<c>INFOPATH</c> environment variable (usually set through the various <path>/"
+"etc/env.d/</path> files). To get started, it's important to note the <path>/"
+"usr/share/info/dir</path> file. This special file is used when info is ran "
+"with no parameters. It contains a listing of all info pages available for "
+"users to browse. To begin looking at navigating around in info, we'll go "
+"ahead and bring it up with no arguments:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):68
+msgid "Starting up info"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):68
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>info</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):72
+msgid ""
+"Now in the next chapter we'll look at dealing with basic info navigation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):80
+msgid "Working with info pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):82
+msgid "Browsing with menus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):85
+msgid "Now that info is started, we're given a screen similar to this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):89
+msgid "Sample info screen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):89
+#, no-wrap
+msgid ""
+"\n"
+"File: dir,      Node: Top       This is the top of the INFO tree\n"
+"\n"
+"  This (the Directory node) gives a menu of major topics.\n"
+"  Typing \"q\" exits, \"?\" lists all Info commands, \"d\" returns here,\n"
+"  \"h\" gives a primer for first-timers,\n"
+"  \"mEmacs&lt;Return&gt;\" visits the Emacs manual, etc.\n"
+"\n"
+"  In Emacs, you can click mouse button 2 on a menu item or cross reference\n"
+"  to select it.\n"
+"\n"
+"* Menu:\n"
+"\n"
+"User Interface Toolkit\n"
+"* GDK: (gdk).           The General Drawing Kit\n"
+"* GTK: (gtk).           The GIMP Toolkit\n"
+"\n"
+"GNU programming tools\n"
+"* Autoconf v2.1: (autoconf).         Create source code configuration scripts.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):110
+msgid ""
+"Right now there are a bunch of entries with an asterisk before them. These "
+"are menu items for navigating through different node levels. There are two "
+"ways of selecting menus. We'll look at the first now and the other way "
+"later. First off, we'll go ahead and look at the <c>wget</c> info page. To "
+"do so, use the down arrow key until you reach the area indicated by the blue "
+"highlighting:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):118
+msgid "Navigating to the wget info menu entry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):118
+#, no-wrap
+msgid ""
+"\n"
+"Network Applications\n"
+"* GnuTLS: (gnutls).                     Package for Transport Layer Security.\n"
+"* <i>Wget: (wget).</i>         The non-interactive network downloader.\n"
+"* certtool: (gnutls)Invoking certtool.  Manipulate certificates and keys.\n"
+"* gnutls-cli: (gnutls)Invoking gnutls-cli.      GNU TLS test client.\n"
+"* gnutls-cli-debug: (gnutls)Invoking gnutls-cli-debug.  GNU TLS debug client.\n"
+"* gnutls-serv: (gnutls)Invoking gnutls-serv.    GNU TLS test server.\n"
+"* srptool: (gnutls)Invoking srptool.    Simple SRP password tool.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):129
+msgid ""
+"Once you get to this area, hit the <c>ENTER</c> key to select the menu item. "
+"This will bring up the info page for <c>wget</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):134
+msgid "The wget info page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):134
+#, no-wrap
+msgid ""
+"\n"
+"File: wget.info,  Node: Top,  Next: Overview,  Up: (dir)\n"
+"\n"
+"Wget 1.10.2\n"
+"***********\n"
+"\n"
+"This manual documents version 1.10.2 of GNU Wget, the freely available\n"
+"utility for network downloads.\n"
+"\n"
+"   Copyright (C) 1996-2005 Free Software Foundation, Inc.\n"
+"\n"
+"* Menu:\n"
+"\n"
+"* Overview::            Features of Wget.\n"
+"* Invoking::            Wget command-line arguments.\n"
+"* Recursive Download::  Downloading interlinked pages.\n"
+"* Following Links::     The available methods of chasing links.\n"
+"* Time-Stamping::       Mirroring according to time-stamps.\n"
+"* Startup File::        Wget's initialization file.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):155
+msgid ""
+"Now that we have an info page up, the next section will look at basic "
+"navigation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):163
+msgid "Basic navigation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):166
+msgid ""
+"In terms of nodes, this is considered the <c>Top</c> node for the wget page. "
+"Consider the <c>Top</c> node to be the same as the table of contents for "
+"that particular info page. Now to navigate the actual page itself, you have "
+"a couple of different methods. First off is the standard info method. This "
+"is using the <c>SPACE</c> key to move forward a page and the <c>BACKSPACE/"
+"DELETE</c> keys to move back a page. This is the recommended method as it "
+"automatically advances/retreats to the appropriate node in the document. "
+"This allows for a somewhat linear browsing for those used to man pages. "
+"Another way is through the <c>PAGE UP/PAGE DOWN</c> keys. These work, but "
+"they will not advance/retreat like <c>SPACE/BACKSPACE/DELETE</c> will. If "
+"you want to skip entire nodes without using <c>SPACE/BACKSPACE/DELETE</c>, "
+"you can also use the <c>[</c> (advance backwards) and <c>]</c> (advance "
+"forwards) keys."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):181
+msgid ""
+"As mentioned earlier, there are 2 ways of navigating menus. The other way "
+"will now be described here. The numbers <c>1-9</c> can be used to reference "
+"to the first-ninth menu entries in a document. This can be used to quickly "
+"peruse through documents. For example, we'll use <c>3</c> to reach the "
+"<c>Recursive Download</c> menu entry. So press <c>3</c> and it will bring up "
+"the <c>Recursive Download</c> screen:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):190
+msgid "Resulting Recursive Download screen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):190
+#, no-wrap
+msgid ""
+"\n"
+"File: wget.info,  Node: Recursive Download,  Next: Following Links,  Prev: Invoking,  Up: Top\n"
+"\n"
+"3 Recursive Download\n"
+"********************\n"
+"\n"
+"GNU Wget is capable of traversing parts of the Web (or a single HTTP or\n"
+"FTP server), following links and directory structure.  We refer to this\n"
+"as to \"recursive retrieval\", or \"recursion\".\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):201
+msgid ""
+"Now we're at the <c>Recursive Download</c> screen. Here is a good time to "
+"note a few things. First off the top header section. This header shows the "
+"navigation capable from this particular screen. The page indicated by "
+"<c>Next: </c> can be accessed by pressing the <c>n</c> key, and the page "
+"indicated by <c>Prev: </c> can be accessed by pressing the <c>p</c> key. "
+"Please note that this will only work for the same level. If overused you "
+"could round up in totally unrelated content. It's better to use <c>SPACE/"
+"BACKSPACE/DELETE/[/]</c> to navigate in a linear fashion."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):212
+msgid ""
+"If for some reason you get lost, there are a few ways to get out. First is "
+"the <c>t</c> key. This will take you straight to the toplevel (table of "
+"contents) for the particular info page you're browsing. If you want to "
+"return to the last page you looked out, you can do so with the <c>l</c> key. "
+"If you want to go to the above level, you can do so with the <c>u</c> key. "
+"Now that you have some idea of navigating a page, the next chapter will look "
+"at searching for content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):226
+msgid "Searching through info"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):228
+msgid "Navigating to other info pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):231
+msgid ""
+"Now that you can navigate an individual info page, it's important to look at "
+"accessing other info pages. The first obvious way is to go to the info page "
+"through the <c>dir</c> index listing of info pages. To get to the <c>dir</c> "
+"index from deep within a document, simply press the <c>d</c> key. From there "
+"you can search for the appropriate page you want. However, if you know the "
+"actual page, there is an easier way through the <c>Goto node (g key)</c> "
+"command. To go to an info page by name, type <c>g</c> to bring up the prompt "
+"and enter the name of the page in parentheses:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):242
+msgid "Going to an info page by name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):242
+#, no-wrap
+msgid ""
+"\n"
+"* Startup File::        Wget's initialization file.\n"
+"* Examples::            Examples of usage.\n"
+"* Various::             The stuff that doesn't fit anywhere else.\n"
+"* Appendices::          Some useful references.\n"
+"* Copying::             You may give out copies of Wget and of this manual.\n"
+"--zz-Info: (wget.info.gz)Top, 24 lines --Top-------------------------------\n"
+"Goto node: <i>(libc)</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):252
+msgid "This will bring up the libc page as shown here:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):256
+msgid "Result of the Goto node command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):256
+#, no-wrap
+msgid ""
+"\n"
+"File: libc.info,  Node: Top,  Next: Introduction,  Prev: (dir),  Up: (dir)\n"
+"\n"
+"Main Menu\n"
+"*********\n"
+"\n"
+"This is Edition 0.10, last updated 2001-07-06, of `The GNU C Library\n"
+"Reference Manual', for Version 2.3.x of the GNU C Library.\n"
+"\n"
+"* Menu:\n"
+"\n"
+"* Introduction::                 Purpose of the GNU C Library.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):270
+msgid ""
+"Now that we know how to go to info pages by name, the next section will look "
+"at searching for pieces of information using the info page's index."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):278
+msgid "Searching using an index"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):281
+msgid ""
+"In this example we'll see how to lookup the <c>printf</c> function of the c "
+"library using the <c>libc</c> info page's index. You should still be at the "
+"libc info page from the last section, and if not, use the Goto node command "
+"to do so. To utilize the index search, hit the <c>i</c> key to bring up the "
+"prompt, then enter your search term. We'll do so for <c>printf</c> below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):289
+msgid "Entering an index search query"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):289
+#, no-wrap
+msgid ""
+"\n"
+"* Character Set Handling::       Support for extended character sets.\n"
+"* Locales::                      The country and language can affect the\n"
+"                                   behavior of library functions.\n"
+"* Message Translation::          How to make the program speak the user's\n"
+"                                   language.\n"
+"--zz-Info: (libc.info.gz)Top, 1291 lines --Top-- Subfile: libc.info-1.gz-----\n"
+"Index entry: <i>printf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):299
+msgid ""
+"After pressing enter upon completion of our query, we're brought to the "
+"<c>libc</c> definition for <c>printf</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):304
+msgid "Result of the index search query"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):304
+#, no-wrap
+msgid ""
+"\n"
+"File: libc.info,  Node: Formatted Output Functions,  Next: Dynamic Output,  Prev: Other Output Conversions,  Up: Formatted Output\n"
+"\n"
+"12.12.7 Formatted Output Functions\n"
+"----------------------------------\n"
+"\n"
+"This section describes how to call <i>`printf'</i> and related functions.\n"
+"Prototypes for these functions are in the header file `stdio.h'.\n"
+"Because these functions take a variable number of arguments, you _must_\n"
+"declare prototypes for them before using them.  Of course, the easiest\n"
+"way to make sure you have all the right prototypes is to just include\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):317
+msgid ""
+"We've now successfully performed a search using the <c>libc</c> info page "
+"index. However, sometimes what we want is in the page itself. The next "
+"section will look at performing searches within the page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):326
+msgid "Searching using the search command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):329
+msgid ""
+"Starting from the previous location at the <c>Formatted Output Functions</c> "
+"node, we'll look at searching for the <c>sprintf</c> variation of the "
+"<c>printf</c> function. To perform a search, press the <c>s</c> key to bring "
+"up the search prompt, and then enter the query (sprintf in this case):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):336
+msgid "Entering a search query"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):336
+#, no-wrap
+msgid ""
+"\n"
+" -- Function: int wprintf (const wchar_t *TEMPLATE, ...)\n"
+"     The `wprintf' function prints the optional arguments under the\n"
+"     control of the wide template string TEMPLATE to the stream\n"
+"     `stdout'.  It returns the number of wide characters printed, or a\n"
+"--zz-Info: (libc.info.gz)Formatted Output Functions, 127 lines --Top-- Subfile: libc.info-3.gz--\n"
+"Search for string []: <i>sprintf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):345
+msgid "Hit <c>ENTER</c> and it will show the result of the query:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre:caption):349
+msgid "Result of the search query"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(pre):349
+#, no-wrap
+msgid ""
+"\n"
+"-- Function: int <i>sprintf</i> (char *S, const char *TEMPLATE, ...)\n"
+"     This is like `printf', except that the output is stored in the\n"
+"     character array S instead of written to a stream.  A null\n"
+"     character is written to mark the end of the string.\n"
+"\n"
+"     The `sprintf' function returns the number of characters stored in\n"
+"     the array S, not including the terminating null character.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):359
+msgid "And we have the function we need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):368
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):370
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):373
+msgid ""
+"This concludes the overview of using info to view info pages. As always "
+"comments are both welcome and appreciated. Clicking on the my name (Chris "
+"White) on the right side will send me an email."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(title):382
+msgid "Additional Program Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):385
+msgid ""
+"In order to make things easier for those that wish to browse info pages "
+"through a more friendly graphical interface, the following are available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(li):391
+msgid "app-text/info2html - Convert info pages to a browse-able HTML format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(li):392
+msgid "app-text/pinfo - <c>ncurses</c> based info viewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(li):393
+msgid "app-text/tkinfo - a <c>tcl/tk</c> based info browser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(li):394
+msgid "app-vim/info - a <c>vim</c> based info browser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(p):397
+msgid ""
+"The <c>KDE</c> browser <c>Konqueror</c> also allows you to browse info pages "
+"through the <c>info: </c> URI."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//info-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/inserts.xml.po b/doc/gettext/ru/inserts.xml.po
new file mode 100644
index 0000000..98593b2
--- /dev/null
+++ b/doc/gettext/ru/inserts.xml.po
@@ -0,0 +1,238 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(inserts:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(version):6
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):7
+msgid "Content"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):8
+msgid "Credits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):9
+msgid "Updated <docdate/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):10
+msgid ""
+"The <uri link=\"$originalversion\">original version</uri> of this document "
+"was last updated <docdate/>"
+msgstr ""
+
+#. Doc not in /doc/LL/metadoc.xml
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):12
+msgid "This translation is not maintained anymore"
+msgstr ""
+
+#. Doc in /doc/LL/metadoc.xml but not in /doc/en/metadoc.xml
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):14
+msgid "The original version of this translation is not maintained anymore"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):15
+msgid "Summary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):16
+msgid "Figure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):17
+msgid "Note"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):18
+msgid "Warning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):19
+msgid "Important"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):20
+msgid "Code Listing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):21
+msgid "Gentoo Linux Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):22
+msgid "Printable Linux Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):23
+msgid "Printable Linux Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):25
+msgid "Print"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):26
+msgid "View a printer-friendly version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):27
+msgid "View all"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):28
+msgid "View all handbook in one page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):29
+msgid "Home"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):30
+msgid ""
+"The contents of this document are licensed under the <uri link=\"http://"
+"creativecommons.org/licenses/by-sa/2.5\">Creative Commons - Attribution / "
+"Share Alike</uri> license."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):35
+msgid "Link to other book part not available"
+msgstr ""
+
+#. Metadoc stuff
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):37
+msgid "Gentoo Linux Documentation Categories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):38
+msgid "Members"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):39
+msgid "Member"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):40
+msgid "Lead"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):41
+msgid "Name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):42
+msgid "Nickname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):43
+msgid "E-mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):44
+msgid "Position"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):45
+msgid "Files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):46
+msgid "Filename"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):47
+msgid "Version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):48
+msgid "Original Version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):49
+msgid "Editing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):50
+msgid "N/A"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):51
+msgid "Bugs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):52
+msgid "Showstoppers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):53
+msgid "Normal Bugs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):54
+msgid "Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):55
+msgid "Bug ID"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):56
+msgid "Untranslated files"
+msgstr ""
+
+#. Disclaimer and redirect stuff
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):59
+msgid "Disclaimer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):60
+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.<br/> This document "
+"is not actively maintained."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):67
+msgid ""
+"This handbook has been replaced by a newer version and is not maintained "
+"anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):70
+msgid ""
+"This document is a work in progress and should not be considered official "
+"yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):73
+msgid "This document is not valid and is not maintained anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(insert):76
+msgid ""
+"You should be redirected to <uri link=\"$redirect\">the new version</uri> "
+"within a few seconds."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//inserts.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/ipv6.xml.po b/doc/gettext/ru/ipv6.xml.po
new file mode 100644
index 0000000..573ebe5
--- /dev/null
+++ b/doc/gettext/ru/ipv6.xml.po
@@ -0,0 +1,1343 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):6
+msgid "Gentoo IPv6 Router Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):8
+msgid "Developer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):9
+msgid "latexer@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):9
+msgid "Peter Johanson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):12
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):12
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(author:title):14
+msgid "Editor, Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):15
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):15
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):18
+msgid "cam@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):18
+msgid "Camille Huot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):21
+msgid "okun@hack.fi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail):21
+msgid "Pasi Valminen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(abstract):27
+msgid ""
+"This guide shows how to setup IPv6 on a Gentoo system. This includes "
+"establishing a tunnel with a tunnel broker, some basic DNS configuration and "
+"configuring clients to use the system to connect to IPv6 addresses."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(version):37
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(date):38
+msgid "2010-08-11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):41
+msgid "Preliminaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):43
+msgid "Basic Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):46
+msgid ""
+"Any of the 2.6 kernel trees availables in Gentoo will easily support IPv6 "
+"connections. The new USAGI IPv6 stack is integrated to the kernel since "
+"Linux 2.6.0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):52
+msgid "Emerging a kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):52
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gentoo-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):56
+msgid ""
+"Now we are ready to enter the kernel source directory and begin our actual "
+"kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):61
+msgid "Configuring the Linux Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):61
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):66
+msgid ""
+"This assumes the symlink <path>/usr/src/linux</path> points to the sources "
+"you will be using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):71
+msgid "'make menuconfig' options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):71
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"Networking support ---&gt;\n"
+"Networking options ---&gt;\n"
+"   &lt;*&gt; The IPv6 protocol (EXPERIMENTAL)\n"
+"<comment>(The IPv6 options beneath this one can be useful for many other applications,</comment>\n"
+"<comment>but should not be needed for a basic setup)</comment>\n"
+"\n"
+"<comment>(This option is only required if you are using ptrtd for 6to4 conversion)</comment>\n"
+"[*] Network device support\n"
+"   &lt;*&gt; Universal TUN/TAP device driver support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):87
+msgid "Testing IPv6 Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):90
+msgid ""
+"After enabling the recommended options, recompile your kernel and reboot "
+"into your new IPv6-enabled kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):95
+msgid ""
+"If you don't already have <b>iproute2</b> installed, we urge you to do it "
+"now. iproute2 is a network configuration suite that contains <c>ip</c>, the "
+"famous replacement for <c>ifconfig</c>, <c>route</c>, <c>iptunnel</c> and "
+"others..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):101
+msgid "Installing iproute2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):101
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge sys-apps/iproute2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(warn):105
+msgid ""
+"Use of ifconfig can cause serious headaches if you have multiple tunnel "
+"devices. You have to remove the tunnels in backorder, which means that the "
+"latest created must be removed first. You have been warned!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):111
+msgid "If IPv6 is working, the loopback device should show an IPv6 address:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):115
+msgid "Checking the loopback device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):115
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ip -6 addr show lo</i>\n"
+"1: lo: &lt;LOOPBACK,UP&gt; mtu 16436\n"
+"    inet6 ::1/128 scope host \n"
+"       valid_lft forever preferred_lft forever\n"
+"    <comment>(The above lines show things are working)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):123
+msgid ""
+"Before going any further, make sure that you add <e>ipv6</e> to your list of "
+"USE variables in <path>make.conf</path>, so that future emerges of packages "
+"will include IPv6 support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):134
+msgid "Tunnel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):136
+msgid "Basic Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):139
+msgid ""
+"Most ISPs still do not offer any native IPv6 connections. To get around this "
+"limitation, there are several \"tunnel brokers\" around the globe that offer "
+"free IPv6 tunnels. This will allow you to tunnel all your IPv6 connections "
+"through an IPv4 connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):147
+msgid "Broker"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):147
+msgid "Location"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):149
+msgid "http://tunnelbroker.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):149
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):179
+msgid "Hurricane Electric"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):150
+msgid "North America, Europe, Asia"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):153
+msgid "http://gogonet.gogo6.com/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):153
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):238
+msgid "Freenet6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):154
+msgid "US"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):157
+msgid "http://www.sixxs.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):157
+msgid "Sixxs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):158
+msgid "Europe"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):161
+msgid "http://tunnel-broker.singnet.com.sg/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):161
+msgid "Singnet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):162
+msgid "Singapore"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):165
+msgid "http://broker.aarnet.net.au/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):165
+msgid "Aarnet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):166
+msgid "Australia/South Pacific"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):170
+msgid ""
+"Below are two examples for setting up a tunnel with two popular North "
+"American tunnels, Hurricane Electric (applies for non-heartbeat tunnels from "
+"sixxs.net as well) and Freenet6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):182
+msgid ""
+"Hurricane Electric (HE for short) offers free IPv6 tunnels and allocates "
+"a /64 block of addresses for you. It also allows configuration of reverse "
+"DNS. Getting a tunnel from HE is as easy as going to <uri>http://www."
+"tunnelbroker.net/</uri> and filling out a one page form."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):189
+msgid ""
+"Registration includes listing information like your address and phone number."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):194
+msgid ""
+"After you have a tunnel approved and have a /64 block allocated, you can "
+"configure your Gentoo box. HE provides sample configurations based on "
+"ifconfig and the iproute utilities. The following two examples assume you "
+"have the following configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):203
+msgid "Local IPv4 Address (eth0)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):203
+msgid "68.36.91.195"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):206
+msgid "HE IPv4 Address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):206
+msgid "64.71.128.82"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):209
+msgid "Local IPv6 tunnel Address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):209
+msgid "2001:470:1F00:FFFF::189"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):212
+msgid "IPv6 Block"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):212
+msgid "2001:470:1F00:296::/64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):216
+msgid ""
+"Using the iproute2 package and the <c>ip</c> command, you would do the "
+"following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):221
+msgid "Configuration of an IPv6 tunnel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):221
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Create a tunnel between the local (eth0) IPv4 and HE's remote IPv4 address)</comment>\n"
+"# <i>ip tunnel add sixbone mode sit remote 64.71.128.82 local 68.36.91.195 ttl 64 dev eth0</i>\n"
+"<comment>(Extract the tunneling overhead from the MTU)</comment>\n"
+"# <i>ip link set sixbone mtu 1280</i>\n"
+"<comment>(Bring the tunnel up)</comment>\n"
+"# <i>ip link set sixbone up</i>\n"
+"<comment>(Assign the IPv6 address to it)</comment>\n"
+"# <i>ip addr add 2001:470:1F00:FFFF::189 dev sixbone</i>\n"
+"<comment>(Route all global unicast IPv6 addresses through our 'sixbone' tunnel device)</comment>\n"
+"# <i>ip route add 2000::/3 dev sixbone</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):241
+msgid ""
+"<uri link=\"http://gogonet.gogo6.com/\">Freenet6</uri> is another free "
+"tunnel broker. Optional registration only requires a username and a valid "
+"email address. They have chosen to turn the tunnel management into a client/"
+"server setup and have created the <c>gateway6</c> client. The client is "
+"available in Portage. To install it do:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):249
+msgid "Installing the Freenet6 client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):249
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gateway6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):253
+msgid ""
+"Now if you chose to connect with authentification, you need to configure "
+"<c>gateway6</c> by editing <path>/etc/gateway6/gw6c.conf</path>. You should "
+"only have to change the <e>userid</e> and <e>passwd</e> fields to match "
+"those assigned from Freenet6 and change the gateway server. Below is a "
+"sample config file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):261
+msgid "gw6c.conf example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):261
+#, no-wrap
+msgid ""
+"\n"
+"auth_method=any\n"
+"<i>userid=anonymous</i>\n"
+"<i>passwd=foobar</i>\n"
+"template=linux\n"
+"server=broker.freenet6.net\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):273
+msgid "Testing your connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):276
+msgid ""
+"Now that your tunnel is configured, you can test your connection. The "
+"easiest way to do this is to use the <c>ping6</c> utility and try to ping an "
+"IPv6 host."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):282
+msgid "Testing the connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):282
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge iputils</i>\n"
+"# <i>ping6 www.kame.net</i>\n"
+"PING www.kame.net(orange.kame.net) 56 data bytes\n"
+"64 bytes from orange.kame.net: icmp_seq=1 ttl=52 time=290 ms\n"
+"64 bytes from orange.kame.net: icmp_seq=2 ttl=52 time=277 ms\n"
+"64 bytes from orange.kame.net: icmp_seq=3 ttl=52 time=280 ms\n"
+"64 bytes from orange.kame.net: icmp_seq=4 ttl=52 time=279 ms\n"
+"64 bytes from orange.kame.net: icmp_seq=5 ttl=52 time=277 ms\n"
+"\n"
+"--- www.kame.net ping statistics ---\n"
+"5 packets transmitted, 5 received, 0% packet loss, time 4038ms\n"
+"rtt min/avg/max/mdev = 277.040/281.041/290.046/4.699 ms\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):297
+msgid ""
+"Further work is currently in progress to add better IPv6 support to the "
+"network init scripts. If you'd like to know the status of this and/or help "
+"out, email <mail link=\"latexer@gentoo.org\">latexer@gentoo.org</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):309
+msgid "IPv6 Support in Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):312
+msgid "Re-emerging packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):315
+msgid ""
+"Unless you had <e>USE=\"ipv6\"</e> in your <path>/etc/make.conf</path> "
+"previously, you probably need to re-emerge a bunch of packages to compile in "
+"IPv6 support for them. To get a list of all the installed packages which are "
+"affected by USE flag changes, use Portage's <c>--newuse</c> (<c>-N</c>) "
+"option:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):322
+msgid "Candidates for re-emerging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):322
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -uDNav world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):326
+msgid ""
+"If you have changed a lot of USE flags, the list could be quite long. It's "
+"suggested to keep your system up-to-date, so it won't hurt if you recompile "
+"all affected packages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):332
+msgid ""
+"Some packages detect IPv6 support automagically and hence have no ipv6 USE "
+"flag. Thus not all packages, which should support IPv6, will support it if "
+"you have not compiled it with an IPv6 enabled kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):342
+msgid "IPv6 Specific Packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):345
+msgid ""
+"There are a few packages which specifically deal with IPv6 items. Most of "
+"these are located in <path>/usr/portage/net-misc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):351
+msgid "Package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):351
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):353
+msgid "net-misc/ipv6calc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):354
+msgid "Converts an IPv6 address to a compressed format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):357
+msgid "net-misc/netcat6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):358
+msgid "netcat version that supports IPv6 and IPv4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):361
+msgid "dev-perl/Socket6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):362
+msgid "IPv6 related part of the C socket.h defines and structure manipulators"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):373
+msgid "DNS setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):375
+msgid "IPv6 and DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):378
+msgid ""
+"Just as DNS for IPv4 uses A records, DNS for IPv6 uses AAAA records. (This "
+"is because IPv4 is an address space of 2^32 while IPv6 is an address space "
+"of 2^128). For reverse DNS, the INT standard is deprecated but still widely "
+"supported. ARPA is the latest standard. Support for the ARPA format will be "
+"described here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):390
+msgid "BIND configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):393
+msgid ""
+"Recent versions of BIND include excellent IPv6 support. This section will "
+"assume you have at least minimal knowledge about the configuration and use "
+"of BIND. We will assume you are not running bind in a chroot. If you are, "
+"simply append the chroot prefix to most of the paths in the following "
+"section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):401
+msgid ""
+"First you need to add entries for both forward and reverse DNS zone files in "
+"<path>/etc/bind/named.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):406
+msgid "named.conf entries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):406
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(We allow bind to listen to IPv6 addresses.</comment>\n"
+"<comment>Using 'any' is the only way to do it prior to bind-9.3)</comment>\n"
+"options {\n"
+"    [...]\n"
+"    listen-on-v6 { any; }\n"
+"    [...]\n"
+"};\n"
+"<comment>(This will provide the forward DNS for the domain 'ipv6-rules.com':)</comment>\n"
+"zone \"ipv6-rules.com\" IN {\n"
+"    type master;\n"
+"    file \"pri/ipv6-rules.com\";\n"
+"};\n"
+"<comment>(This format for reverse DNS is \"bitwise.\" It's done by taking the IPv6 prefix,</comment>\n"
+"<comment>reversing the order of the numbers and putting a period between each number)</comment>\n"
+"zone \"6.9.2.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa\" {\n"
+"        type master;\n"
+"        file \"pri/rev-ipv6-rules.com.arpa\";\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):427
+msgid ""
+"Now we must create those zone files and add entries for all of our hosts:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):432
+msgid "pri/ipv6-rules.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):432
+#, no-wrap
+msgid ""
+"\n"
+"$TTL    2h\n"
+"@       IN      SOA     ipv6-rules.com. webmaster.ipv6-rules.com.  (\n"
+"                                2003052501 ; Serial\n"
+"                                28800      ; Refresh\n"
+"                                14400      ; Retry\n"
+"                                3600000    ; Expire\n"
+"                                86400 )    ; Minimum\n"
+"                NS      ns1.ipv6-rules.com\n"
+"\n"
+"        IN      AAAA    2001:470:1f00:296::1 ; address for ipv6-rules.com\n"
+"host1   IN      AAAA    2001:470:1f00:296::2 ; address for host1.ipv6-rules.com\n"
+"host2   IN      AAAA    2001:470:1f00:296::3:3 ; address for host2.ipv6-rules.com\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):447
+msgid "pri/rev-ipv6-rules.com.arpa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):447
+#, no-wrap
+msgid ""
+"\n"
+"$TTL 3d ; Default TTL (bind 8 needs this, bind 9 ignores it)\n"
+"@       IN SOA ipv6-rules.com. webmaster.ipv6-rules.com. (\n"
+"                        2003052501      ; Serial number (YYYYMMdd)\n"
+"                        24h             ; Refresh time\n"
+"                        30m             ; Retry time\n"
+"                        2d              ; Expire time\n"
+"                        3d )            ; Default TTL\n"
+"        IN      NS     ns1.ipv6-rules.com.\n"
+"; IPv6 PTR entries\n"
+"$ORIGIN 6.9.2.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.\n"
+"\n"
+"1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN      PTR     ipv6-rules.com.\n"
+"2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN      PTR     host1.ipv6-rules.com.\n"
+"3.0.0.0.3.0.0.0.0.0.0.0.0.0.0.0 IN      PTR     host2.ipv6-rules.com.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):468
+msgid "DJBDNS configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):471
+msgid ""
+"There are currently some third-party patches to DJBDNS available at "
+"<uri>http://www.fefe.de/dns/</uri> that allow it to do IPv6 nameserving. "
+"DJBDNS can be installed with these patches by emerging it with <e>ipv6</e> "
+"in your USE variables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(warn):478
+msgid ""
+"Not all record types are support yet with these patches. In particular, NS "
+"and MX records are not supported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):483
+msgid "Installing djbdns"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):483
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge djbdns</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):487
+msgid ""
+"After djbdns is installed, it can be setup by running <c>tinydns-setup</c> "
+"and answering a few questions about which IP addresses to bind to, where to "
+"install tinydns, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):493
+msgid "Setting up tinydns"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):493
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tinydns-setup</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):497
+msgid ""
+"Assuming we've installed <c>tinydns</c> into <path>/var/tinydns</path>, we "
+"can now edit <path>/var/tinydns/root/data</path>. This file will contain all "
+"the data needed to get tinydns handling DNS for your IPv6 delegation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):503
+msgid "sample data file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):503
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(*.ipv6-rules.com is authoritatively handled by 192.168.0.1)</comment>\n"
+".ipv6-rules.com:192.168.0.1:a:259200\n"
+"<comment>(Authoritative reverse DNS for 2001:470:1f00:296::/64)</comment>\n"
+".6.9.2.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa:192.168.0.1:a\n"
+"<comment>(Specify the IPs for host1 and host2)</comment>\n"
+"6host1.ipv6-rules.com:200104701f0002960000000000000001:86400\n"
+"6host2.ipv6-rules.com:200104701f0002960000000000000002:86400\n"
+"<comment>(Point www to host1)</comment>\n"
+"3www.ipv6-rules.com:200104701f0002960000000000000002:86400\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):515
+msgid ""
+"Lines prefixed with a <c>6</c> will have both an AAAA and a PTR record "
+"created. Those prefixed with a <c>3</c> will only have an AAAA record "
+"created. Besides manually editing the <path>data</path> file, you can use "
+"the scripts <c>add-host6</c> and <c>add-alias6</c> to add new entries. After "
+"changes are made to the <path>data</path> file, you simply need to run "
+"<c>make</c> from <path>/var/tinydns/root</path>. This will create <path>/var/"
+"tinydns/root/data.cfb</path>, which tinydns will use as its source of "
+"information for DNS requests."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):531
+msgid "IPv6 Router"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):533
+msgid "Configure routing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):536
+msgid ""
+"Further configuration is required if we want to use our system as a router "
+"for other clients wishing to connect to the outside world with IPv6. We need "
+"to enable forwarding of IPv6 packets. We can do this in one of two ways."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):543
+msgid "Enabling forwarding"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):543
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo 1 &gt; /proc/sys/net/ipv6/conf/all/forwarding</i>\n"
+"or\n"
+"# <i>sysctl -w net.ipv6.conf.all.forwarding=1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(warn):549
+msgid ""
+"The <c>radvd</c> init script explained in the next chapter enables (and "
+"disables) forwarding, making the next step unnecessary."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):554
+msgid ""
+"To enable forwarding at boot, you'll need to edit <path>/etc/sysctl.conf</"
+"path> and add the following line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):559
+msgid "sysctl.conf addition"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):559
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(If you will be using radvd, this step is unnecessary)</comment>\n"
+"net.ipv6.conf.default.forwarding=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):564
+msgid ""
+"Traffic should now be forwarded from this box through the tunnel we've "
+"established with our broker."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):569
+msgid ""
+"To assign IPv6 addresses to clients, the IPv6 specification allows for both "
+"stateless and stateful IP assignment. Stateless assignment uses a process "
+"called Router Advertisement and allows clients to obtain an IP and a default "
+"route by simply bringing an interface up. It is called \"stateless\" because "
+"there is no record of IPs assigned and the host they are assigned to. "
+"Stateful assignment is handled by DHCPv6. It is \"stateful\" because the "
+"server keeps a state of the clients who've requested IPs and received them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):584
+msgid "Stateless Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):587
+msgid ""
+"Stateless configuration is easily accomplished using the Router "
+"Advertisement Daemon, or <c>radvd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):592
+msgid "Configuring radvd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):592
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge radvd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):596
+msgid ""
+"After having emerged <c>radvd</c>, we need to create <path>/etc/radvd/radvd."
+"conf</path> that contains information about what IP block to assign IPs "
+"from. Here is a sample <path>radvd.conf</path> file using the prefix we've "
+"been assigned from our tunnel broker."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):603
+msgid "Sample radvd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):603
+#, no-wrap
+msgid ""
+"\n"
+"interface eth1\n"
+"{\n"
+"        <comment>(Send advertisement messages to other hosts)</comment>\n"
+"        AdvSendAdvert on;\n"
+"        <comment>(Fragmentation is bad(tm))</comment>\n"
+"        AdvLinkMTU 1280;\n"
+"        MaxRtrAdvInterval 300;\n"
+"        <comment>(IPv6 subnet prefix we've been assigned by our PoP)</comment>\n"
+"        prefix 2001:470:1F00:296::/64\n"
+"        {\n"
+"                AdvOnLink on;\n"
+"                AdvAutonomous on;\n"
+"        };\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(warn):620
+msgid ""
+"Make sure the interface on the first line is correct so you broadcast router "
+"advertisement to your intranet and not to your ISP!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):625
+msgid ""
+"Further information is available in <c>man radvd.conf</c>. We can now start "
+"<c>radvd</c> and set it to start at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):630
+msgid "Starting up radvd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):630
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/radvd start</i>\n"
+"# <i>rc-update add radvd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):639
+msgid "Stateful Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):642
+msgid ""
+"If you'd like to use stateful configuration, you'll need to install and "
+"configure dhcpv6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):647
+msgid "Installing dhcpv6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):647
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge dhcpv6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):651
+msgid ""
+"Next we must configure the DHCPv6 server by editing <path>/etc/dhcp6s.conf</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):656
+msgid "Sample dhcp6s.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):656
+#, no-wrap
+msgid ""
+"\n"
+"prefer-life-time 10000;\n"
+"valid-life-time 20000;\n"
+"renew-time 5000;\n"
+"rebind-time 8000;\n"
+"interface eth1 {\n"
+"    link AAA {\n"
+"        allow unicast;\n"
+"        send unicast;\n"
+"        allow rapid-commit;\n"
+"        send server-preference 5;\n"
+"        renew-time 1000;\n"
+"        rebind-time 2400;\n"
+"        prefer-life-time 2000;\n"
+"        valid-life-time 3000;\n"
+"        pool{\n"
+"            range 2001:470:1f00:296::10 to 2001:470:1f00:296::110/64;\n"
+"            prefix 2001:470:1f00:296::/64;\n"
+"        };\n"
+"    };\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):679
+msgid "We can now start dhcp6s, and configure it to start at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):683
+msgid "Starting dhcp6s"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):683
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/dhcp6s start</i>\n"
+"# <i>rc-update add dhcp6s default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):693
+msgid "IPv6 Clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):695
+msgid "Using radvd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):698
+msgid ""
+"Clients behind this router should now be able to connect to the rest of the "
+"net via IPv6. If using radvd, configuring hosts should be as easy as "
+"bringing the interface up. (This is probably already done by your net.ethX "
+"init scripts)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):705
+msgid "Connecting through IPv6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):705
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ip link set eth0 up</i>\n"
+"# <i>ip addr show eth0</i>\n"
+"1: eth0: &lt;BROADCAST,MULTICAST,UP&gt; mtu 1400 qdisc pfifo_fast qlen 1000\n"
+"    link/ether 00:01:03:2f:27:89 brd ff:ff:ff:ff:ff:ff\n"
+"    inet6 2001:470:1f00:296:209:6bff:fe06:b7b4/128 scope global\n"
+"       valid_lft forever preferred_lft forever\n"
+"    inet6 fe80::209:6bff:fe06:b7b4/64 scope link\n"
+"       valid_lft forever preferred_lft forever\n"
+"    inet6 ff02::1/128 scope global\n"
+"       valid_lft forever preferred_lft forever\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):722
+msgid "Using DHCPv6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):725
+msgid ""
+"If your router is set up to use DHCPv6, your clients will also need to have "
+"the <c>net-misc/dhcpv6</c> package installed. After having done this, you "
+"need to configure your client by editing <path>/etc/dhcp6c.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):731
+msgid "Sample dhcp6c.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):731
+#, no-wrap
+msgid ""
+"\n"
+"interface eth0 {\n"
+"        send rapid-commit;\n"
+"        request domain-name-servers;\n"
+"        iaid 11111;\n"
+"        renew-time 11000;\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):745
+msgid "Using 6to4 Conversion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):747
+msgid "Basic principles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):750
+msgid ""
+"6to4 conversion can be used if you want to have hosts that talk to IPv4 "
+"hosts over a purely IPv6 connection. Thus you can have an entirely IPv6 "
+"internal network, with one host dealing with connecting to the outside IPv4/"
+"IPv6 world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):761
+msgid "DNS configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):764
+msgid ""
+"To get 6to4 conversion working, a DNS proxy, <c>totd</c>, needs to be "
+"configured that will send you AAAA records for sites that really only have A "
+"records. These AAAA records will point to IPv6 addresses which don't "
+"actually exist, but which will get routed through a 6to4 proxy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):771
+msgid "First, install <c>totd</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):775
+msgid "Installing totd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):775
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge totd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):779
+msgid ""
+"Next, we need to setup <path>/etc/totd.conf</path> with some basic "
+"configuration information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):784
+msgid "Sample /etc/totd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):784
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Points to a real DNS nameserver)</comment>\n"
+"forwarder 192.168.0.2 port 53\n"
+"<comment>(What prefix to put before faked AAAA records)</comment>\n"
+"prefix 3ffe:abcd:1234:9876::\n"
+"<comment>(What port to run totd on)</comment>\n"
+"port 5005\n"
+"<comment>(What PID file to use)</comment>\n"
+"pidfile /var/run/totd.pid\n"
+"<comment>(Actually do 6to4 stuff)</comment>\n"
+"stf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):797
+msgid ""
+"<c>totd</c> must be set to use a port different than port 53 if another "
+"nameserver is running on the same machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):806
+msgid "6to4 proxy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):809
+msgid ""
+"<c>ptrtd</c> will be used as a 6to4 proxy, enabling connections between the "
+"internal IPv6 host and the outside IPv4 host."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):814
+msgid "Installing ptrtd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):814
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge ptrtd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):818
+msgid ""
+"We now need to configure <c>ptrtd</c>, telling it what fake prefix (the one "
+"we setup <c>totd</c> to use) to create proxy connections for. Edit <path>/"
+"etc/conf.d/ptrtd</path> and set <c>IPV6_PREFIX</c>. This should be the same "
+"prefix as was configured with <c>totd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):825
+msgid "Sample /etc/ptrtd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):825
+#, no-wrap
+msgid ""
+"\n"
+"IPV6_PREFIX=\"3ffe:abcd:1234:9876::\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):829
+msgid "You can now start totd, and enable it to start at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):833
+msgid "Starting totd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):833
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/totd start</i>\n"
+"# <i>rc-update add totd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):842
+msgid "Client configuration and testing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):845
+msgid ""
+"Clients may now be configured to connect to both IPv4 and IPv6 hosts through "
+"an IPv6 only connection. Assuming that the clients are already receiving an "
+"IP address from radvd, we simply need to add a new DNS resolver entry, and "
+"add a default route for those \"fake addresses\". First, add an entry at the "
+"top of your <path>/etc/resolv.conf</path> pointing to the machine running "
+"<c>totd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):854
+msgid "/etc/resolv.conf sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):854
+#, no-wrap
+msgid ""
+"\n"
+"nameserver 2001:470:1f00:296::1 <comment>(The server running totd)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):858
+msgid ""
+"To test name resolution, request an AAAA record for a known IPv4 only site."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):863
+msgid "Testing name resolution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):863
+#, no-wrap
+msgid ""
+"\n"
+"# <i>dig aaaa google.com</i>\n"
+";; ANSWER SECTION:\n"
+"google.com.             300     IN      AAAA     3ffe:abcd:1234:9876::d8ef:3364\n"
+"google.com.             300     IN      AAAA     3ffe:abcd:1234:9876::d8ef:3564\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):870
+msgid ""
+"We will now add a default route for all addresses prefixed with our chosen "
+"fake prefix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):875
+msgid "Adding the default route"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):875
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Assuming your IPv6 interface is eth0)</comment>\n"
+"# <i>ip route add 3ffe:abcd:1234:9876::/64 via 2001:470:1f00:296::1 dev eth0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):880
+msgid ""
+"Finally, use <c>ping6</c> to ping google.com at it's fake IPv6 location."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre:caption):884
+msgid "Testing 6to4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(pre):884
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ping6 -c 2 google.com</i>\n"
+"PING 3ffe:abcd:1234:9876::d8ef:3364(3ffe:abcd:1234:9876::d8ef:3364) 56 data bytes\n"
+"64 bytes from 3ffe:abcd:1234:9876::d8ef:3364: icmp_seq=1 ttl=54 time=0.106 ms\n"
+"64 bytes from 3ffe:abcd:1234:9876::d8ef:3364: icmp_seq=2 ttl=54 time=0.090 ms\n"
+"\n"
+"--- 3ffe:abcd:1234:9876::d8ef:3364 ping statistics ---\n"
+"2 packets transmitted, 2 received, 0% packet loss, time 1000ms\n"
+"rtt min/avg/max/mdev = 0.090/0.098/0.106/0.008 ms\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(note):895
+msgid ""
+"The router running <c>ptrtd</c> is actually replying, but this at least "
+"tells us things are working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(title):905
+msgid "Other Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):909
+msgid "There are many excellent resources online pertaining to IPv6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):914
+msgid "Websites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(th):914
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):916
+msgid "http://www.ipv6.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):916
+msgid "www.ipv6.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):917
+msgid "General IPv6 Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):920
+msgid "http://www.linux-ipv6.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):920
+msgid "www.linux-ipv6.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):921
+msgid "USAGI Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):924
+msgid "http://www.deepspace6.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):924
+msgid "www.deepspace6.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):925
+msgid "Linux/IPv6 site"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri:link):936
+msgid "http://www.kame.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(uri):936
+msgid "www.kame.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(ti):937
+msgid "*BSD implementation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(p):941
+msgid ""
+"On IRC, you can try <c>#ipv6</c> on <uri link=\"http://www.freenode.net/"
+"\">Freenode</uri>. You can connect to the Freenode servers using an IPv6 "
+"enabled client by connecting to <b>irc.ipv6.freenode.net</b>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//ipv6.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/java.xml.po b/doc/gettext/ru/java.xml.po
new file mode 100644
index 0000000..2dfb340
--- /dev/null
+++ b/doc/gettext/ru/java.xml.po
@@ -0,0 +1,890 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):6
+msgid "Gentoo Java Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail:link):9
+msgid "nichoj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail):9
+msgid "Joshua Nichols"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail:link):12
+msgid "karltk@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail):12
+msgid "Karl Trygve Kalleberg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail:link):15
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(mail):15
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(abstract):18
+msgid ""
+"This guide will introduce you to Java and explain how to use Java with "
+"Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(version):27
+msgid "0.23"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(date):28
+msgid "2010-07-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):31
+msgid "What is Java?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):33
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):170
+msgid "Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):36
+msgid ""
+"Java is a programming language developed by engineers of Sun Microsystems. "
+"The language is object-oriented and designed to run on multiple platforms "
+"without the need of recompiling code for each platform. Although Java can be "
+"compiled as a native program, much of Java's popularity can be attributed to "
+"its portability, along with other features such as garbage collection. To "
+"make platform independence possible the Java compiler compiles the Java code "
+"to an intermediate representation called \"Java bytecode\" that runs on a "
+"JRE (Java Runtime Environment) and not directly on the operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):47
+msgid ""
+"In order to run Java bytecode, one needs to have a JRE (Java Runtime "
+"Environment) installed. A JRE provides core libraries, a platform dependent "
+"Java Virtual Machine, plugins for browsers, among other things. A JDK (Java "
+"Development Kit) adds programming tools, such as a bytecode compiler and a "
+"debugger."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):60
+msgid "Before You Begin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):62
+msgid "Existing installs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):65
+msgid ""
+"For existing installs, regardless of if you have installed anything Java "
+"before, make sure you have followed the <uri link=\"/proj/en/java/java-"
+"upgrade.xml\">Java Upgrade Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):74
+msgid "New installs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):77
+msgid "New installs should require no further preparation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):86
+msgid "Installing a Virtual Machine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):88
+msgid "The choices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):91
+msgid ""
+"Gentoo provides numerous Runtime Environments (JREs) and Development Kits "
+"(JDKs). Among the current choices, we have:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):98
+msgid "Vendor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):99
+msgid "JDK"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):100
+msgid "JRE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):103
+msgid "Sun's Java Kit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):104
+msgid "dev-java/sun-jdk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):105
+msgid "dev-java/sun-jre-bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):108
+msgid "The IBM Java Kit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):109
+msgid "dev-java/ibm-jdk-bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):110
+msgid "dev-java/ibm-jre-bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):113
+msgid "BEA WebLogic's J2SE Development Kit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):114
+msgid "dev-java/jrockit-jdk-bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):126
+msgid "Installing a JRE/JDKs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):129
+msgid ""
+"To install your profile's default JDK, you can run <c>emerge virtual/jdk</"
+"c>. Or to install your profile's default JRE, you can <c>emerge virtual/jre</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):134
+msgid ""
+"In recent events, Sun has relicensed their JDK and JRE under a more Linux "
+"distro friendly license. As a result, Sun Java 1.5 and onwards are freely "
+"downloadable, without any further hassle."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):140
+msgid ""
+"A JDK also includes a JRE, so if you install a JDK you shouldn't have to "
+"also have to install a JRE."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):148
+msgid "Installing fetch-restricted virtual machines"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):151
+msgid ""
+"Some of the JDKs and JREs require you to jump through a few hoops before "
+"installing. Simply emerge the packages as you normally would. The ebuilds "
+"will then instruct you where to go and what to download."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):157
+msgid ""
+"You should download the indicated file(s) into <path>/usr/portage/distfiles</"
+"path>. Once there, you can rerun the emerge command, at which point the JRE/"
+"JDK will be begin to install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):168
+msgid "Configuring your virtual machine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):173
+msgid ""
+"Gentoo has the ability to have multiple JDKs and JREs installed without "
+"causing conflicts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):178
+msgid ""
+"Using the <c>java-config</c> tool, you can set the system-wide default "
+"(provided you have root access). Users can also use <c>java-config</c> to "
+"set up their own personal default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):184
+msgid ""
+"You can also use <e>eselect</e> to change the system and user vm. See "
+"<c>eselect java-vm help</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):192
+msgid "Setting a default virtual machine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):195
+msgid ""
+"Running the command <c>java-config --list-available-vms</c> will give you a "
+"list of all JREs and JDKs installed on your system. Here is an example of "
+"output:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):201
+msgid "Listing available VMs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):201
+#, no-wrap
+msgid ""
+"\n"
+"# <i>java-config --list-available-vms</i>\n"
+"The following VMs are available for generation-2:\n"
+"1)      IcedTea6-bin 1.4.1 [icedtea6-bin]\n"
+"2)      Sun JDK 1.5.0.20 [sun-jdk-1.5] <comment>(Build Only)</comment>\n"
+"*)      Sun JDK 1.6.0.16 [sun-jdk-1.6]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):209
+msgid ""
+"VMs marked as Build Only may contain security vulnerabilities and/or be EOL. "
+"Gentoo recommends not setting these VMs as either your system or user VM. "
+"Please see <uri link=\"java.xml#build-only\">Build Only VM</uri> for more "
+"information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):216
+msgid ""
+"The <e>*</e> indicates this is the current active vm (system-vm or user-vm "
+"when set). The name in the brackets (<e>[]</e>) is the handle or ID for that "
+"particular VM. You use the handle or the number to <c>java-config --set-"
+"system-vm</c>. Here is an example of how to set the system VM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):223
+msgid "Setting the System VM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):223
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(By handle (preferred))</comment>\n"
+"# <i>java-config --set-system-vm sun-jdk-1.6</i>\n"
+"Now using sun-jdk-1.6 as your generation-2 system JVM\n"
+"<comment>(By number)</comment>\n"
+"# <i>java-config --set-system-vm 3</i>\n"
+"Now using sun-jdk-1.6 as your generation-2 system JVM\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):232
+msgid "As a regular user, you can use <c>java-config --set-user-vm</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):236
+msgid ""
+"You no longer have to <c>source</c> the profile for updates to the user/"
+"system VM take place."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):244
+msgid "Build Only VM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):247
+msgid ""
+"Some virtual machines are flagged as build-only due to being EOL and/or "
+"containing security vulnerabilities. These virtual machines will not "
+"automatically be used by Gentoo for the running of applications using Gentoo "
+"launchers but will still be available for use by Gentoo's build environment "
+"as some packages may require them for building. The setting of these virtual "
+"machines as either your system or user VM is strongly discouraged as these "
+"VMs will then be used when running the <path>/usr/bin/{java,javac,..}</path> "
+"executables and will also be used by any packages not using Gentoo's "
+"launcher scripts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):262
+msgid "Preferred Build VM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):265
+msgid ""
+"While merging Java packages, the VM used for building can sometimes be "
+"different from the one currently set as the system VM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):270
+msgid ""
+"This merge time VM switching is needed when, for example, your system-vm is "
+"set to a 1.6 VM and the package you are merging requires a 1.5 VM. While "
+"merging it will select and use a 1.5 VM, leaving your system-vm choice "
+"intact."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):276
+msgid ""
+"To define which VM is selected when a switch is needed, we have created a "
+"list of <e>default/supported VMs</e> per arch. You can find them in <path>/"
+"usr/share/java-config-2/config/jdk-defaults.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):282
+msgid ""
+"Of course, Gentoo is all about choice, so you can override these defaults "
+"(and even your selected system VM) in <path>/etc/java-config-2/build/jdk."
+"conf</path> and have complete control over which VM will get used for "
+"merging. Some examples:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):289
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):294
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):299
+msgid "Example /etc/java-config-2/build/jdk.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):289
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(I always want it to use a sun-jdk, ie sun-jdk-1.4 for 1.4, sun-jdk-1.5 for 1.5, etc)</comment>\n"
+"*=sun-jdk\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):294
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Always use sun-jdk-1.5 wherever possible, except for when a 1.4 or 1.3 VM is explicitly required)</comment>\n"
+"*=sun-jdk-1.5\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):299
+#, no-wrap
+msgid ""
+"\n"
+"<comment># For 1.3 I prefer sun-jdk 1.4 but when it is not available, use ibm-jdk-bin,\n"
+"# For 1.5, use sun-jdk </comment>\n"
+"1.3=sun-jdk-1.4 ibm-jdk-bin\n"
+"1.5=sun-jdk\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(warn):306
+msgid ""
+"You do not <e>have</e> to edit this file. If you change these options to use "
+"a unsupported VM, things could possibly break. Because of the wide variety "
+"of available VMs, we do not have the resources to test and verify every "
+"package works on all of them. Bugs reported with a unsupported VM won't be "
+"prioritized as much as bugs present within supported VMs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):319
+msgid "Compilers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):323
+msgid ""
+"The standard Java compiler used for building is javac, which comes with each "
+"JDK. In addition to configuring the VM used at build time, it is also "
+"possible configure which compiler is used. Essentially, you define a list "
+"your preference for which compiler to use in <path>/etc/java-config-2/build/"
+"compilers.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):331
+msgid "/etc/java-config-2/build/compilers.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):331
+#, no-wrap
+msgid ""
+"\n"
+"# If the ebuild supports it\n"
+"# it will check the COMPILERS var front to back and\n"
+"# use the first compiler that is installed\n"
+"\n"
+"COMPILERS=\"ecj-X.Y jikes javac\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):339
+msgid ""
+"Some compilers don't support all possible -target and -source arguments. "
+"Therefore, each compiler in the list is checked to see if it can support the "
+"desired -source/-target. javac will work in all cases, so if no other "
+"suitable compiler is found, it will be used instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):346
+msgid "More details about each compiler are provided below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):352
+msgid "Name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):353
+msgid "Handle"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):354
+msgid "Package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(th):355
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):358
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):359
+msgid "javac"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):360
+msgid "N/A"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):361
+msgid ""
+"This is the default compiler that will be used, and comes with each JDK."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):366
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):367
+msgid "jikes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):368
+msgid "dev-java/jikes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):369
+msgid ""
+"Jikes was originally developed by IBM. Anecdotally, it is generally quicker "
+"than javac. Note however, that it is more pedantic, and will fail under a "
+"few circumstances where javac has no issue. It also does not support Java "
+"1.5 syntax yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):377
+msgid "Eclipse Compiler for Java"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):378
+msgid "ecj"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):379
+msgid "dev-java/eclipse-ecj"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(ti):380
+msgid ""
+"ECJ is the compiler used by the Eclipse software development kit. It is very "
+"full featured, and is pretty fast. It does support Java 1.5 syntax."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):392
+msgid "Setting a default CLASSPATH"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(warn):396
+msgid ""
+"The options explained in this section should be considered deprecated and "
+"will most likely be removed in the future. We strongly recommend against "
+"using these, because your Java projects or application should ideally manage "
+"their own classpaths. If you choose to specify a default CLASSPATH, some "
+"applications may behave unexpectedly, because classes they weren't expecting "
+"would be on the classpath."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):405
+msgid ""
+"<c>java-config</c> can also be used to set a system-wide default CLASSPATH, "
+"as well a user-specific default CLASSPATH."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):410
+msgid ""
+"First, you will want to list available Java libraries installed on your "
+"system that might want to be put in your CLASSPATH. Here is an example of "
+"output:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):415
+msgid "Listing classes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):415
+#, no-wrap
+msgid ""
+"\n"
+"# <i>java-config --list-available-packages</i>\n"
+"[xerces-2] The next generation of high performance, fully compliant XML parsers in the Apache Xerces family (/usr/share/xerces-2/package.env)\n"
+"[junit] Simple framework to write repeatable tests (/usr/share/junit/package.env)\n"
+"[bsh] BeanShell: A small embeddable Java source interpreter (/usr/share/bsh/package.env)\n"
+"[bcel] The Byte Code Engineering Library: analyze, create, manipulate Java class files (/usr/share/bcel/package.env)\n"
+"[log4j] A low-overhead robust logging package for Java (/usr/share/log4j/package.env)\n"
+"...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):425
+msgid ""
+"Again, the names in brackets (<e>[]</e>) are the IDs that you have to pass "
+"to <c>java-config --set-system-classpath</c>. Here is an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):430
+msgid "Setting classpaths"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):430
+#, no-wrap
+msgid ""
+"\n"
+"# <i>java-config --set-system-classpath log4j,xerces-2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):434
+msgid ""
+"The current directory (<path>.</path>) will not be part of the system "
+"classpath, as that should be added in your system's login profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):439
+msgid ""
+"You will have to update your environment by logging out, then in again or "
+"sourcing <path>/etc/profile</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):444
+msgid ""
+"For users, <c>java-config --set-user-classpath</c> will create <path>~/."
+"gentoo/java-env-classpath</path>, which you should then source from your "
+"shell's profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):450
+msgid "Sourcing user specific classpath"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):456
+msgid ""
+"If you really want a system wide or user default classpath you can add "
+"something like the following to your shell's profile. But we would advise "
+"against it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):462
+msgid "Setting classpath"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):462
+#, no-wrap
+msgid ""
+"\n"
+"# <i>export CLASSPATH=\"${CLASSPATH}:$(java-config --classpath log4j,xerces-2)\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):471
+msgid "Java Browser Plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):473
+msgid "Installing a plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):476
+msgid ""
+"You can install a Java plugin for your web browser by emerging a Java VM "
+"with the <c>nsplugin</c> USE flag set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(note):481
+msgid ""
+"<c>nsplugin</c> is not available for all architectures. Check for available "
+"plugins on your arch before trying to install a VM by running <c>emerge -pv "
+"&lt;java-vm&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):487
+msgid ""
+"Portage will allow you to install multiple versions of Java plugins, though "
+"only one will be used by your browser. You can check the list of available "
+"plugins by running:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):493
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):562
+msgid "Viewing available plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):493
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect java-nsplugin list</i>\n"
+"   [1]   sun-jre-bin-1.6\n"
+"   [2]   icedtea6-bin\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):499
+msgid "In this example, <c>sun-jre-bin</c> is selected for the browser plugin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):503
+msgid "Selecting a plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):503
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect java-nsplugin set sun-jre-bin-1.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):507
+msgid "Verify that the correct plugin was selected:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):511
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):586
+msgid "Verifying the correct plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):511
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect java-nsplugin list</i>\n"
+"   [1]   sun-jre-bin-1.6  current\n"
+"   [2]   icedtea6-bin\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):517
+msgid ""
+"Java.com also provides a link to <uri link=\"http://java.com/en/download/"
+"installed.jsp\">verify your installed plugin</uri>. Additionally, if you are "
+"using a Mozilla-based browser, you can verify your Java plugin by typing "
+"<c>about:plugins</c> into the address bar."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):527
+msgid "Plugins on multilib systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):530
+msgid ""
+"If you are running a mixed 64-bit and 32-bit multilib system (for example, "
+"on AMD64), you can use 64-bit and 32-bit Java plugins. Unless you have a "
+"pressing need to run 32-bit Java applications, we recommend using native 64-"
+"bit plugins on 64-bit web browsers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):537
+msgid ""
+"There are several native 64-bit browser plugins available. The default JDK/"
+"JRE pair, <c>sun-jdk</c> and <c>sun-jre-bin</c>, both include browser "
+"plugins. Just emerge one of them with the <c>nsplugin</c> USE flag enabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):543
+msgid "Installing a 64-bit plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):543
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"dev-java/sun-jre-bin nsplugin\" &gt;&gt; /etc/portage/package.use</i>\n"
+"# <i>emerge sun-jre-bin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):548
+msgid ""
+"To use a 32-bit plugin on a 32-bit browser, you will need to emerge <c>emul-"
+"linux-x86-java</c> with the <c>nsplugin</c> USE flag enabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):553
+msgid "Installing a 32-bit plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):553
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"app-emulation/emul-linux-x86-java nsplugin\" &gt;&gt; /etc/portage/package.use</i>\n"
+"# <i>emerge emul-linux-x86-java</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):558
+msgid "Next, check which plugins are available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):562
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect java-nsplugin list</i>\n"
+"Available 32-bit Java browser plugins\n"
+"  [1]   emul-linux-x86-java-1.5\n"
+"  [2]   emul-linux-x86-java-1.6\n"
+"Available 64-bit Java browser plugins\n"
+"  [1]   icedtea6-bin\n"
+"  [2]   sun-jre-bin-1.6\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):572
+msgid "Now select the right plugin for your browsers:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre:caption):576
+msgid "Selecting plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):576
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Choose the plugins for 32-bit and 64-bit browsers)</comment>\n"
+"# <i>eselect java-nsplugin set 32bit emul-linux-x86-java-1.6</i>\n"
+"# <i>eselect java-nsplugin set 64bit sun-jre-bin-1.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):582
+msgid "Verify the correct plugin was selected:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(pre):586
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect java-nsplugin list</i>\n"
+"Available 32-bit Java browser plugins\n"
+"  [1]   emul-linux-x86-java-1.5\n"
+"  [2]   emul-linux-x86-java-1.6  current\n"
+"Available 64-bit Java browser plugins\n"
+"  [1]   icedtea6-bin\n"
+"  [2]   sun-jre-bin-1.6  current\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):601
+msgid "USE flags for use with Java"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):603
+msgid "Setting USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(p):606
+msgid ""
+"For more information regarding USE flags, refer to the <uri link=\"/doc/en/"
+"handbook/handbook-x86.xml?part=2&amp;chap=2\">USE flags</uri> chapter from "
+"the Gentoo Handbook."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):615
+msgid "The flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):619
+msgid "The <b>java</b> flag adds support for Java in a variety of programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):620
+msgid ""
+"The <b>nsplugin</b> flag adds support for Mozilla-like browsers (including "
+"Firefox). You will need this for viewing Java applets in your Mozilla-like "
+"browser."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):625
+msgid ""
+"The <b>source</b> flag installs a zip of the source code of a package. This "
+"is traditionally used for IDEs to 'attach' source to the libraries you are "
+"using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):630
+msgid "The <b>jce</b> flag adds support for the Java Cryptography Engine"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):631
+msgid ""
+"For Java packages, the <b>doc</b> flag will build API documentation using "
+"javadoc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):642
+msgid "Additional resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):644
+msgid "Off-line resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):648
+msgid "java-config man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(title):655
+msgid "Online resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):659
+msgid ""
+"The <uri link=\"http://www.gentoo.org/proj/en/java/\">Java Project Page</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):663
+msgid ""
+"The <uri link=\"http://news.gmane.org/gmane.linux.gentoo.java\">gentoo-java</"
+"uri>, <uri link=\"http://news.gmane.org/gmane.linux.gentoo.user\">gentoo-"
+"user</uri>, and <uri link=\"http://news.gmane.org/gmane.linux.gentoo.devel"
+"\">gentoo-dev</uri> mailing list archives"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):672
+msgid ""
+"<uri link=\"irc://irc.gentoo.org/gentoo\">#gentoo</uri> and <uri link="
+"\"irc://irc.gentoo.org/gentoo-java\">#gentoo-java</uri> on IRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(uri:link):678
+msgid "http://en.wikipedia.org/wiki/Java_programming_language"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(uri):678
+msgid "Wikipedia's entry for Java"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(li):681
+msgid ""
+"If you have suggestions or questions regarding this document, please email "
+"the Gentoo Java team: <mail>java@gentoo.org</mail>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//java.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/jffnms.xml.po b/doc/gettext/ru/jffnms.xml.po
new file mode 100644
index 0000000..163ffb7
--- /dev/null
+++ b/doc/gettext/ru/jffnms.xml.po
@@ -0,0 +1,557 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(guide:link):5
+msgid "/doc/en/jffnms.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):6
+msgid "Jffnms Installation and Setup Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(mail:link):9
+msgid "angusyoung@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(mail):9
+msgid "Otavio R. Piske"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(abstract):12
+msgid ""
+"This guide shows you how to proceed with the post installation setup of "
+"Jffnms, a network management and monitoring system, and how to monitor your "
+"systems with it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(version):22
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(date):23
+msgid "2008-03-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):26
+msgid "Jffnms Basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):31
+msgid ""
+"<uri link=\"http://www.jffnms.org\">Jffnms</uri> is a network management and "
+"monitoring system. It allows you to grab information from many different "
+"kinds of hosts and protocols. With this guide, we aim to show you how to get "
+"Jffnms properly installed and have your systems monitored by this amazing "
+"tool."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):43
+msgid "Initial Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):45
+msgid "Choosing your USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):48
+msgid "The Jffnms ebuild has the following USE flags available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(th):54
+msgid "USE Flags for Jffnms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(th):55
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(th):88
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):59
+msgid "Uses Mysql to store Jffnms data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):63
+msgid "Uses PostgreSQL to store Jffnms data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):67
+msgid ""
+"Adds support for snmp, which enables jffnms to gather data from other hosts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):76
+msgid "USE flags for PHP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):79
+msgid ""
+"Being written in PHP, Jffnms is heavily dependent on PHP USE flags. In order "
+"to install Jffnms successfully, you are required to have your PHP package "
+"installed with (at least) the following USE flags:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(th):87
+msgid "USE Flags for PHP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):92
+msgid "Adds support for media-libs/gd (to generate graphics on the fly)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):96
+msgid "Adds support for Web Distributed Data eXchange"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):100
+msgid "Adds support for tcp/ip sockets"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):104
+msgid "Adds persistent session support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):108
+msgid "Adds support for the Standard PHP Library"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(ti):112
+msgid "Enable CLI SAPI"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):119
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):122
+msgid ""
+"Just like any package in Portage, jffnms can be installed with <c>emerge</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):126
+msgid "Installing Jffnms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):126
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge jffnms</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):130
+msgid "Jffnms should be installed in <path>/opt/jffnms/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):137
+msgid "Configuring Apache 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(warn):140
+msgid ""
+"This very basic configuration procedure for Apache does not cover all "
+"aspects of setting up a web server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):145
+msgid ""
+"Sometimes you will want to run Jffnms on your local computer instead of a "
+"remote server. If this is your case, it is very likely that you don't have "
+"an apache setup running. Don't worry about installing apache though, Portage "
+"has already done that for you. Nevertheless, you still have to configure and "
+"test apache, which (luckily) is pretty straightforward. Start by adding "
+"Apache to your default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):154
+msgid "Adding apache2 to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):154
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add apache2 default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):158
+msgid "If you haven't done it yet, it's time to start apache2:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):162
+msgid "Starting apache2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):162
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/apache2 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):166
+msgid ""
+"Finally, point your browser at <uri>http://localhost/</uri> and you should "
+"be presented with a home page about your newly installed Apache 2. Now that "
+"we know that Apache is up and running, we can proceed to the mod_php "
+"configuration. Fire up your favorite text editor, open <path>/etc/conf.d/"
+"apache2</path> and add <c>-D PHP5</c> the APACHE2_OPTS variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):175
+msgid "Apache 2 Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):175
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/conf.d/apache2</i>\n"
+"APACHE2_OPTS=\"-D DEFAULT_VHOST -D PHP5\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):180
+msgid ""
+"After that, you should create a symlink to the Jffnms install directory in "
+"your Apache document root dir. In Gentoo, by default, Apache uses <path>/var/"
+"www/localhost/htdocs</path> as document root. So, you should do the "
+"following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):187
+msgid "Creating Jffnms symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):187
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /var/www/localhost/htdocs &amp;&amp; ln -s /opt/jffnms/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):194
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):204
+msgid "Configuring PHP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):197
+msgid ""
+"Now that Apache is running, it is time to configure PHP. Jffnms requires "
+"that you set some variables in php.ini in order to run. The <path>php.ini</"
+"path> file is usually located in <path>/etc/php/apache2-php5/php.ini</path>. "
+"You have to set these variables to the following values:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):204
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/php/apache2-php5/php.ini</i>\n"
+"register_globals = On\n"
+"register_argc_argv = On \n"
+"error_reporting  =  E_ALL &amp; ~E_NOTICE\n"
+"allow_url_fopen = On\n"
+"include_path = \".:/usr/share/php5:/usr/share/php:/usr/share/php/PEAR\"\n"
+"short_open_tag = On\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):217
+msgid "Database setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(warn):220
+msgid ""
+"Please note again that this a very basic configuration procedure for any "
+"database system and does not cover all aspects of setting up such systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):225
+msgid ""
+"Jffnms allows you to use either PostgreSQL or MySQL as its database. Here "
+"we'll show you how to create the database and necessary tables where Jffnms "
+"will store its data. It's important to note that it isn't necessary to have "
+"a database running locally to run Jffnms and except for the fact that you "
+"need to run this commands on the remote host, the procedure is the same."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):236
+msgid "Setting up PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(note):239
+msgid ""
+"If you already have a PostgreSQL database up and running, you can proceed to "
+"the <uri link=\"#use-pg\">next section</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):244
+msgid ""
+"You should add PostgreSQL to your default runlevel so it's started each time "
+"you boot your computer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):249
+msgid "Adding PostgreSQL to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):249
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add postgresql default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):253
+msgid "Now you must setup the PostgreSQL database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):257
+msgid "Preparing PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):257
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --config postgresql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):261
+msgid "Now start PostgreSQL:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):265
+msgid "Starting PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):265
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/postgresql start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):272
+msgid "Using PostgreSQL as database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):275
+msgid ""
+"Once you have your PostgreSQL set up and running, you have to create a "
+"Jffnms user and a database to store host data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):280
+msgid "Creating the Jffnms user and database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):280
+#, no-wrap
+msgid ""
+"\n"
+"# <i>psql template1 postgres</i>\n"
+"template1=# <i>create user jffnms password 'jfnms' createdb;</i>\n"
+"template1=# <i>\\connect template1 jffnms</i>\n"
+"template1=# <i>create database jffnms;</i>\n"
+"template1=# <i>\\q</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):288
+msgid "Finally, you need to create all the tables where data will be stored:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):292
+msgid "Creating Jffnms tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):292
+#, no-wrap
+msgid ""
+"\n"
+"# <i>psql jffnms jffnms &lt; /opt/jffnms/docs/jffnms-0.8.3.pgsql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):296
+msgid ""
+"Once you have run those steps, the PostgreSQL database configuration for "
+"Jffnms should be ok."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):304
+msgid "Using MySQL as database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(warn):307
+msgid ""
+"Installing and configuring a MySQL database is not covered in this guide. "
+"Please see our <uri link=\"/doc/en/mysql-howto.xml\">MySQL Startup Guide</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):312
+msgid ""
+"In case you want to run Jffnms with MySQL, you'll first need to create a "
+"database and a MySQL user. After that, create your MySQL table:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):317
+msgid "Create a mysql table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):317
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mysql -u jffnms -pjffnms jffnms &lt; /opt/jffnms/docs/jffnms-0.8.3.mysql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):324
+msgid "UDP Port Monitoring and discovery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(warn):327
+msgid ""
+"This section covers setting up and running suid programs, so it may not be "
+"adequate for systems where security is too much an issue."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):332
+msgid ""
+"If you want UDP port monitoring and discovery, you need to set <c>nmap</c> "
+"and <c>fping</c> as a SUID programs. This may give you security hole in case "
+"there's a bug in one of them. To set them as a SUID you can run the "
+"following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):339
+msgid "Setting up udp port monitoring and discovery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):339
+#, no-wrap
+msgid ""
+"\n"
+"# <i>chmod +s /usr/bin/nmap ; chmod a+x /usr/bin/nmap</i>\n"
+"# <i>chmod +s /usr/sbin/fping ; chmod a+x /usr/sbin/fping</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):349
+msgid "Configuring Jffnms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):351
+msgid "Configuring the poller process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):354
+msgid ""
+"The poller process is responsible for gathering data from hosts. In order to "
+"collect this data at regular intervals, it must be added to crontab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre:caption):359
+msgid "Collecting data at regular intervals"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(pre):359
+#, no-wrap
+msgid ""
+"\n"
+"# <i>crontab -u jffnms /opt/jffnms/docs/unix/crontab</i>\n"
+"# <i>crontab -e -u jffnms</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):367
+msgid "Final setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):370
+msgid ""
+"By now, Jffnms should be correctly installed on your system. You still need, "
+"however, to configure Jffnms. Luckily, Jffnms provides us with an easy to "
+"use web page where it's possible to configure access to database, user "
+"access as well as check if the current host configuration suffices Jffnms "
+"needs. You can access this web interface through the following URL: "
+"<uri>http://localhost/jffnms/admin/setup.php</uri>. You can login to your "
+"new installation by using the username and password <c>admin</c>. You should "
+"visit <uri link=\"http://www.jffnms.org/\">Jffnms's home page</uri> for "
+"details on how to properly configure it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(title):387
+msgid "Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(p):391
+msgid ""
+"Though Jffnms is a wonderful application, it is a bit hard to get it up and "
+"running. So if you run into problems with Jffnms, there are some places "
+"where you can look for help:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):399
+msgid "http://www.jffnms.org/docs/installing.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):399
+msgid "Jffnms Installation Manual"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):403
+msgid "http://www.jffnms.org/docs/jffnms.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):403
+msgid "Jffnms Manual"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):405
+msgid "http://forums.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):405
+msgid "Gentoo Forums"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):407
+msgid "http://www.postgresql.org/docs/8.0/static/index.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):407
+msgid "PostgreSQL 8 Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri:link):410
+msgid "http://dev.mysql.com/doc/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(uri):410
+msgid "MySQL Documentation"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//jffnms.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/kde-config.xml.po b/doc/gettext/ru/kde-config.xml.po
new file mode 100644
index 0000000..b00b977
--- /dev/null
+++ b/doc/gettext/ru/kde-config.xml.po
@@ -0,0 +1,61 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(guide:redirect):7
+msgid "/proj/en/desktop/kde/kde4-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(title):9
+msgid "The KDE Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(mail:link):12
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(mail):12
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(abstract):15
+msgid ""
+"One of the most used desktop environments is KDE. This guide tries to "
+"describe all aspects of KDE, including installation, configuration and usage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(version):24
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(date):25
+msgid "2008-04-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(title):28
+msgid "Moved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(p):32
+msgid ""
+"This document was moved to <uri>/proj/en/desktop/kde/kde4-guide.xml</uri>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//kde-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/kde-split-ebuilds.xml.po b/doc/gettext/ru/kde-split-ebuilds.xml.po
new file mode 100644
index 0000000..d89ce94
--- /dev/null
+++ b/doc/gettext/ru/kde-split-ebuilds.xml.po
@@ -0,0 +1,75 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(guide:redirect):7
+msgid "/proj/en/desktop/kde/kde-split-ebuilds.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(title):9
+msgid "The KDE Split Ebuilds HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(mail:link):12
+msgid "danarmak@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(mail):12
+msgid "Dan Armak"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(mail:link):15
+msgid "greg_g@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(mail):15
+msgid "Gregorio Guidi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(abstract):18
+msgid ""
+"With KDE 3.4, the 'split ebuilds' were introduced into Portage. This page "
+"documents the reasons behind the transition, the new features it brings and "
+"the way to upgrade from the old-style 'monolithic' ebuilds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(version):28
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(date):29
+msgid "2008-04-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(title):32
+msgid "Moved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(p):36
+msgid ""
+"This document was moved to <uri>/proj/en/desktop/kde/kde-split-ebuilds.xml</"
+"uri>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//kde-split-ebuilds.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/kernel-config.xml.po b/doc/gettext/ru/kernel-config.xml.po
new file mode 100644
index 0000000..cf3308c
--- /dev/null
+++ b/doc/gettext/ru/kernel-config.xml.po
@@ -0,0 +1,819 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(guide:link):5
+msgid "/doc/en/kernel-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):6
+msgid "Gentoo Linux Kernel Configuration Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):9
+msgid "dsd@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):9
+msgid "Daniel Drake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):17
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):12
+msgid "curtis119@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):12
+msgid "Curtis Napier"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):15
+msgid "jdr@xemoka.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):15
+msgid "Justin Robinson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):18
+msgid "rane@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):18
+msgid "Łukasz Damentko"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):21
+msgid "smithj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail):21
+msgid "Jonathan Smith"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(abstract):27
+msgid ""
+"This document aims to introduce the concepts of manual kernel configuration, "
+"and to detail some of the most common configuration pitfalls."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(version):36
+msgid "1.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(date):37
+msgid "2010-03-21"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):40
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):44
+msgid ""
+"Gentoo provides two ways for you to handle kernel installation and upgrade: "
+"<e>automatic</e> (genkernel), and <e>manual</e>. Although the automatic "
+"method can be regarded as <e>easier</e> for the user, there are a number of "
+"reasons why a large proportion of Gentoo users choose to configure their "
+"kernel manually: greater flexibility, smaller kernel, shorter compilation "
+"time, learning experience, severe boredom, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):53
+msgid ""
+"This guide does not cover the automatic method (genkernel). If you'd prefer "
+"to use genkernel to compile and install your kernel, head over to the <uri "
+"link=\"/doc/en/genkernel.xml\">Genkernel documentation</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):59
+msgid ""
+"This guide does not attempt to document the manual configuration process "
+"from start to finish -- the configuration process relies upon a large degree "
+"of common sense, and a relatively high level of technical knowledge about "
+"your system. Instead, this document will introduce the concepts of manual "
+"configuration and detail the most common pitfalls which users face."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):67
+msgid ""
+"This document is written with recent kernels in mind, for the most common "
+"computer architectures. Some details may differ for older kernels or more "
+"exotic architectures, but much of the content will still be relevant."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):73
+msgid ""
+"At this point, you are assumed to have Linux kernel sources unpacked on your "
+"hard disk (usually somewhere under <c>/usr/src</c>), and you are expected to "
+"know how to enter the <c>menuconfig</c> configuration utility and move "
+"through the menu system. If you are not already at this stage, we do have "
+"other documentation available to help you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):82
+msgid ""
+"The <uri link=\"/doc/en/gentoo-kernel.xml\">Kernel Guide</uri> lists the "
+"various kernel source packages we have available"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):86
+msgid ""
+"The <uri link=\"/doc/en/kernel-upgrade.xml\">Kernel Upgrade Guide</uri> "
+"explains how to upgrade your kernel or switch from one to another."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):90
+msgid ""
+"The <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> covers "
+"some aspects of kernel installation too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):101
+msgid "Configuration Concepts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):103
+msgid "The basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):106
+msgid ""
+"The general process is actually rather simple: you are presented with a "
+"series of options, categorised into individual menus and sub-menus, and you "
+"select the hardware support and kernel features relevant for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):112
+msgid ""
+"The kernel includes a <e>default configuration</e>, which is presented to "
+"you the first time you run menuconfig on a particular set of sources. The "
+"defaults are generally broad and sensible, which means that the majority of "
+"users will only have to make a small number of changes to the base config. "
+"If you decide to disable an option that was enabled by default, make sure "
+"you have a relatively good understanding of exactly what that option does, "
+"and the consequences of disabling it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):122
+msgid ""
+"If this is your first time configuring a Linux kernel, you should probably "
+"aim to be conservative: don't be too adventurous, and aim to make as few "
+"modifications to the default settings as possible. At the same time, keep in "
+"mind that there are certain parts of the configuration which you absolutely "
+"must customise to your system setup to actually allow it to boot!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):133
+msgid "Built-in vs modular"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):136
+msgid ""
+"Most configuration options are <e>tristate</e>: they can be either not built "
+"at all, built directly into your kernel (Y), or built as a module (M). "
+"Modules are stored externally on the filesystem, whereas built-in items are "
+"built directly into the kernel image itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):143
+msgid ""
+"There is an important difference between built-in and modular: with a few "
+"exceptions, the kernel makes no attempt whatsoever to load any external "
+"modules when you might need them (it is left up to the user). While certain "
+"other parts of the system may have load-on-demand facilities, and there are "
+"some automatic module loading utilities available, it is recommended that "
+"you build hardware support and kernel features directly into the kernel. The "
+"kernel can then ensure the functionality and hardware support is available "
+"whenever it needs it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):154
+msgid ""
+"Of course, for some parts of the configuration, built-in is an absolute "
+"requirement. For example, if your root partition was an <c>ext2</c> "
+"filesystem, your system would not boot if ext2 was built as a module (the "
+"system would have to look on the root partition to find the ext2 module, but "
+"it cannot look on the root partition unless it already has ext2 support "
+"loaded!)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):165
+msgid "Hardware support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):168
+msgid ""
+"Beyond detecting the <e>architecture type</e> of your system, the "
+"configuration utility makes no attempt to identify which hardware is "
+"actually present in your system. While there are default settings for some "
+"hardware support, you almost certainly need to find and select the "
+"configuration options relevant to your system's hardware configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):176
+msgid ""
+"This simply requires knowledge of the components inside and connected to "
+"your computer, or for you to identify these components. For most internal "
+"components, you need to identify the <e>chipset</e> used on each one, rather "
+"than the retail product name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):183
+msgid ""
+"There are some utilities available that will help you. <c>lspci</c> (part of "
+"the <c>sys-apps/pciutils</c> package) will identify your PCI-based and AGP-"
+"based hardware, and this includes components built onto the motherboard "
+"itself. <c>lsusb</c> (from the <c>sys-apps/usbutils</c> package) will "
+"identify devices connected to USB ports."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):191
+msgid ""
+"The situation is somewhat confused by varying degrees of standardisation in "
+"the hardware world. Unless you really deviate from the defaults, your IDE "
+"hard disks will \"just work\", as will your PS/2 or USB keyboard and mouse. "
+"You'll get basic VGA display support. However, some devices such as ethernet "
+"adapters are barely standardised at all, so you'll have to identify the "
+"ethernet chipset and select the appropriate hardware support for your "
+"specific card to get any network access at all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):201
+msgid ""
+"In addition, while some things just-about-work with the default settings, "
+"you may need to select more specialised options to get the full potential "
+"from your system. For example, if you do not enable the support for the "
+"appropriate IDE chipset, your IDE hard disks will run <e>very</e> slowly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):211
+msgid "Kernel features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):214
+msgid ""
+"As well as hardware support, you also need to think in terms of the software "
+"features you require in your kernel. One important example of such a feature "
+"is filesystem support: you need to select support for the filesystems in use "
+"on your hard disk, as well as any filesystems you might be using on external "
+"storage (e.g. VFAT on USB flash disks)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):222
+msgid ""
+"Another common example is advanced network functionality. If you want to do "
+"some kind of routing or firewalling, you need to ensure the relevant "
+"configuration items are included in your kernel config."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):231
+msgid "Ready?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):234
+msgid ""
+"Now that we've introduced the concepts, you should be able to start "
+"identifying your hardware and browsing through the configuration menus, "
+"selecting the required kernel options for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):240
+msgid ""
+"The rest of this page aims to clear up common areas of confusion, and "
+"provide advice for how to avoid common problems which users often run into. "
+"Good luck!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):250
+msgid "Common problems and areas of confusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):253
+msgid "SATA disks are SCSI"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):256
+msgid ""
+"Most modern desktop systems ship with storage devices (hard disk and CD/DVD "
+"drives) on a <uri link=\"http://en.wikipedia.org/wiki/SATA\">Serial ATA</"
+"uri> bus, rather than the older <uri link=\"http://en.wikipedia.org/wiki/"
+"Parallel_ATA\">IDE</uri> (ribbon cable) bus type."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):264
+msgid ""
+"SATA support in Linux is implemented in a layer referred to as <e>libata</"
+"e>, which sits below the SCSI subsystem. For this reason, SATA drivers are "
+"found in the SCSI driver section of the configuration. Additionally, your "
+"storage devices will be treated as SCSI devices, which means SCSI disk/cdrom "
+"support is required too. Your SATA hard disk will be named as (e.g.) <c>/dev/"
+"sda</c> and your SATA CD/DVD drive will be named as (e.g.) <c>/dev/sr0</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):273
+msgid ""
+"Although the majority of these drivers are for SATA controllers, libata was "
+"not designed to be SATA-specific. All common IDE drivers will also be ported "
+"to libata in the near future, and at this point, the above considerations "
+"will also apply for IDE users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):280
+msgid "Configuration options for libata"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):280
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+" SCSI device support  ---&gt;\n"
+"  &lt;*&gt; SCSI device support\n"
+"  &lt;*&gt;   SCSI disk support\n"
+"  &lt;*&gt;   SCSI CDROM support\n"
+"\n"
+"  SCSI low-level drivers  ---&gt;\n"
+"   &lt;*&gt; Serial ATA (SATA) support\n"
+"    <comment>Select your chipset from the choices listed below the above option</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):295
+msgid "IDE chipsets and DMA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):298
+msgid ""
+"Despite the introduction of SATA, IDE devices are still very common and "
+"depended upon by many. IDE is a fairly generic technology, and as such, "
+"Linux supports almost all IDE controllers out-of-the-box without any "
+"controller-specific options selected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):305
+msgid ""
+"However, IDE is an old technology, and in it's original <e>Programmed Input/"
+"Output</e> incarnation, it is unable to provide the transfer rates required "
+"for speedy access to modern storage devices. The generic IDE driver is "
+"limited to these PIO transfer modes, which result in slow data transfer "
+"rates, and significantly high CPU usage while data is being transferred to/"
+"from disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):313
+msgid ""
+"Unless you're dealing with a pre-1995 system, your IDE controller will also "
+"support an alternative transfer mode, known as <e>Direct Memory Access</e> "
+"(DMA). DMA is much much faster, and CPU utilisation is barely affected while "
+"data transfers are taking place. If you are suffering from really poor "
+"general system performance and you are using an IDE disk, chances are that "
+"DMA is not being used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(note):322
+msgid ""
+"As mentioned earlier, libata is available even for IDE drives. If you're "
+"using libata, then all your drives, including your IDE drives, will be using "
+"DMA. There's no need to do any further checking or configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):328
+msgid ""
+"If you're not using libata for your IDE disks, then you'll need to check for "
+"DMA usage and enable it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):333
+msgid "Checking if DMA is enabled on your IDE disk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):333
+#, no-wrap
+msgid ""
+"\n"
+"# <i>hdparm -d /dev/hda</i>\n"
+"\n"
+"/dev/hda:\n"
+" using_dma    =  0 (off)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):340
+msgid ""
+"To enable DMA on your IDE devices, you simply need to enable the "
+"configuration option for your IDE controller."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):345
+msgid "Configuration options for IDE controllers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):345
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+" ATA/ATAPI/MFM/RLL support  ---&gt;\n"
+"  &lt;*&gt; ATA/ATAPI/MFM/RLL support\n"
+"  &lt;*&gt;   Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support\n"
+"  [*]     PCI IDE chipset support\n"
+"  <comment>Select your chipset from the choices listed below the above option</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):357
+msgid "USB Host Controllers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):360
+msgid ""
+"<uri link=\"http://en.wikipedia.org/wiki/USB\">USB</uri> is a widely adopted "
+"bus for connecting external peripherals to your computer. One of the reasons "
+"behind the success of USB is that it is a standardised protocol, however the "
+"USB <e>host controller devices</e> (HCDs) implemented on the host computer "
+"do vary a little. There are 3 main types:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):369
+msgid ""
+"<c>UHCI</c> is the Universal Host Controller Interface. It supports USB 1.1, "
+"and is usually found on motherboards based on a VIA or Intel chipset."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):373
+msgid ""
+"<c>OHCI</c> is the Open Host Controller Interface. It supports USB 1.1 and "
+"is usually found on motherboards based on an Nvidia or SiS chipset."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):377
+msgid ""
+"<c>EHCI</c> is the Extended Host Controller Interface. It is the only common "
+"host controller to support USB 2.0, and can typically be found on any "
+"computer that supports USB 2.0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):384
+msgid ""
+"Most systems will come with two of the above interface types: EHCI (USB "
+"2.0), plus either UHCI or OHCI (USB 1.1). It is important that you select "
+"both types present on your system. While all USB 2.0 devices are backwards "
+"compatible with USB 1.1, a large proportion of USB devices (even the ones "
+"being manufactured today) are based on the USB 1.1 interface - why would a "
+"USB mouse need more than 1.5mbit/sec?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):393
+msgid ""
+"If you do not select the relevant options corresponding to the USB HCD types "
+"present on your system, you may experience 'dead' USB ports: you plug a "
+"device in, but it does not get power or respond in any way."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):399
+msgid ""
+"A neat <c>lspci</c> trick (from the <c>sys-apps/pciutils</c> package) makes "
+"it relatively easy to detect which HCDs are present in your system. Ignoring "
+"the FireWire controller which was also matched, it is easy to spot that my "
+"system requires OHCI and EHCI support:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):406
+msgid "Using lspci to detect HCD type"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):406
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lspci -v | grep HCI</i>\n"
+"00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) (prog-if 10 <i>[OHCI]</i>)\n"
+"00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) (prog-if 20 <i>[EHCI]</i>)\n"
+"01:0b.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 61) (prog-if 10 [OHCI])\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):413
+msgid "Configuration for USB HCDs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):413
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+" USB support  ---&gt;\n"
+"  &lt;*&gt; Support for Host-side USB\n"
+"  ---   USB Host Controller Drivers\n"
+"  &lt;*&gt;   EHCI HCD (USB 2.0) support\n"
+"  &lt;*&gt;   OHCI HCD support\n"
+"  &lt;*&gt;   UHCI HCD (most Intel and VIA) support\n"
+"  <comment>Select the HCDs present on your system, or all 3 if you are unsure.</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):427
+msgid "Multiprocessor, Hyper-Threading and Dual Core systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):430
+msgid ""
+"Many computer systems are based on multiple processors, but not always in "
+"immediately obvious ways."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):436
+msgid ""
+"Many of Intel's CPUs support a technology which they call <uri link=\"http://"
+"en.wikipedia.org/wiki/Hyperthreading\">hyper-threading</uri>, which is where "
+"the CPU is actually viewed by the system as two <e>logical</e> processors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):442
+msgid ""
+"Some of the most recent Intel/AMD CPUs actually consist of multiple physical "
+"processors inside a single package, these are known as <uri link=\"http://en."
+"wikipedia.org/wiki/Dual_core\">dual core</uri> processors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):447
+msgid ""
+"Some high-end computer systems actually have multiple physical processors "
+"installed on specialised motherboards to provide a significant performance "
+"increase over a <e>uniprocessor</e> system. You'll probably know if you have "
+"such a system, since they aren't cheap."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):455
+msgid ""
+"In all of these cases, you need to select the appropriate kernel options to "
+"obtain optimum performance from these setups."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):460
+msgid "Configuration for multi-processing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):460
+#, no-wrap
+msgid ""
+"\n"
+"Processor type and features  ---&gt;\n"
+" [*] Symmetric multi-processing support\n"
+" <comment>Select the above option if you are on a multi-processor system (of any type)</comment>\n"
+" [*]   SMT (Hyperthreading) scheduler support\n"
+" <comment>Select the above option if you are on an Intel Hyper-Threading CPU</comment>\n"
+" [*]   Multi-core scheduler support (NEW)\n"
+" <comment>Select the above option if your CPU is dual core</comment>\n"
+"Power management and ACPI options  ---&gt;\n"
+" [*] ACPI (Advanced Configuration and Power Interface) Support\n"
+" <comment>The above option not only enables power management features, but might\n"
+" also be a requirement for making all CPUs available to your system</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):477
+msgid "x86 High Memory support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):480
+msgid ""
+"Due to limitations in the 32-bit address space of the x86 architecture, a "
+"kernel with default configuration can only support up to 896mb RAM. If your "
+"system has more memory, only the first 896mb will be visible, unless you "
+"enable high memory support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(note):487
+msgid ""
+"This limitation is specific to the x86 (IA32) architecture. Other "
+"architectures naturally support large amounts of memory, with no "
+"configuration tweaks required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):493
+msgid ""
+"High memory support is not enabled by default, because it introduces a small "
+"system overhead. Do not be distracted by this, the overhead is insignificant "
+"when compared to the performance increase of having more memory available!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):499
+msgid "Enabling high memory support on x86"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):499
+#, no-wrap
+msgid ""
+"\n"
+"Processor type and features  ---&gt;\n"
+" High Memory Support  ---&gt;\n"
+"  (X) 4GB\n"
+"  ( ) 64GB\n"
+"  <comment>Choose the 4GB option, unless your system has more than 4GB of RAM.</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):512
+msgid "Other kernel configuration documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):516
+msgid ""
+"So far, we have only discussed general concepts and specific problems "
+"related to kernel configuration, without going into any precise details "
+"(such details are for you to discover!). However, other parts of the Gentoo "
+"documentation collection provide specialised details for the topics at hand."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):523
+msgid ""
+"You may find these documents helpful while configuring those specific areas, "
+"but if you are new to kernel configuration, don't be too adventurous. Start "
+"by getting a basic system up and running, you can always come back later to "
+"add support for your audio, printing, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):531
+msgid ""
+"The <uri link=\"/doc/en/alsa-guide.xml\">ALSA Guide</uri> details the "
+"configuration options required for sound card support. Note that ALSA is one "
+"exception to the suggested scheme of not building things as modules: ALSA is "
+"actually much easier to configure when the components are modular."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):537
+msgid ""
+"The <uri link=\"/doc/en/bluetooth-guide.xml\">Bluetooth Guide</uri> details "
+"the options you need in order to use bluetooth devices on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):541
+msgid ""
+"The <uri link=\"/doc/en/ipv6.xml\">IPv6 Router Guide</uri> describes how to "
+"configure your kernel for routing using the next generation network "
+"addressing scheme."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):546
+msgid ""
+"If you will be using the closed-source nVidia graphics drivers for improved "
+"3D graphics performance, the <uri link=\"/doc/en/nvidia-guide.xml\">nVidia "
+"Guide</uri> lists the options that should and should not be selected on such "
+"a system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):552
+msgid ""
+"Amongst other things, the <uri link=\"/doc/en/power-management-guide.xml"
+"\">Power Management Guide</uri> explains how to configure your kernel for "
+"CPU frequency scaling, and for suspend and hibernate functionality."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):558
+msgid ""
+"If you are running a PowerPC system, the <uri link=\"/doc/en/gentoo-ppc-faq."
+"xml\">PPC FAQ</uri> has a few sections about kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):563
+msgid ""
+"The <uri link=\"/doc/en/printing-howto.xml\">Printing HOWTO</uri> lists the "
+"kernel options needed to support printing in Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(li):567
+msgid ""
+"The <uri link=\"/doc/en/usb-guide.xml\">USB Guide</uri> details the "
+"configuration required to use common USB devices such as keyboards/mice, "
+"storage devices, and printers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):579
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):581
+msgid "Configuration changes do not take effect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):584
+msgid ""
+"It is very common for users to make a configuration change, but then make a "
+"small mistake in the process following on from that point. They reboot into "
+"a kernel image that is not the one they just reconfigured, observe that "
+"whatever problem they were trying to solve is still present, and conclude "
+"that the configuration change does not solve the problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):592
+msgid ""
+"The process of compiling and installing kernels is outside the scope of this "
+"document, you should refer to the <uri link=\"/doc/en/kernel-upgrade.xml"
+"\">Kernel Upgrade Guide</uri> for general guidance. In short, the process "
+"is: configure, compile, mount /boot (if not already mounted), copy new "
+"kernel image over, reboot. If you miss out any of those final stages, your "
+"changes will not take effect!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):601
+msgid ""
+"It is possible to verify if the kernel you are booted from matches the "
+"kernel compiled on your hard disk by examining the date and time of "
+"compilation. Assuming your architecture is x86 and your kernel sources are "
+"installed at <path>/usr/src/linux</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre:caption):608
+msgid "Verifying you are booted from your modified kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(pre):608
+#, no-wrap
+msgid ""
+"\n"
+"# <i>uname -v</i>\n"
+"#4 SMP PREEMPT Sat Jul 15 08:49:26 BST 2006\n"
+"<comment>The above command displays the date and time that the kernel you are currently booted from was compiled.</comment>\n"
+"\n"
+"# <i>ls -l /usr/src/linux/arch/i386/boot/bzImage</i>\n"
+"-rw-r--r-- 1 dsd users 1504118 Jul 15 08:49 /usr/src/linux/arch/i386/boot/bzImage\n"
+"<comment>The above command displays the date and time that the kernel image on your hard disk was last compiled.</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):618
+msgid ""
+"If the two times from the above commands differ by more than 2 minutes, it "
+"indicates that you have made a mistake during kernel reinstallation and you "
+"are not booted from the kernel image that you thought you were!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(title):627
+msgid "Modules do not get loaded automatically"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):630
+msgid ""
+"As mentioned earlier in this document, the kernel configuration system hides "
+"a large behavioural change when selecting a kernel component as a module (M) "
+"rather than built-in (Y). It is worth repeating this again because so many "
+"users fall into this trap."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):637
+msgid ""
+"When you select a component as built-in, the code is built into the kernel "
+"image (bzImage). When the kernel needs to use that component, it can "
+"initialise and load it automatically, without any user intervention."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):643
+msgid ""
+"When you select a component as a module, the code is built into a kernel "
+"module file and installed on your filesystem. In general, when the kernel "
+"needs to use that component, it can't! With some exceptions, the kernel "
+"makes no effort to actually load these modules - this task is left up to the "
+"user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):650
+msgid ""
+"So, if you build support for your network card as a module, and you then "
+"find that you cannot access your network, it is probably because the module "
+"is not loaded - you must either do this manually or configure your system to "
+"autoload it at boot time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(p):657
+msgid ""
+"Unless you have reasons to do otherwise, save yourself some time by building "
+"these components directly into the kernel image, so that the kernel can "
+"automatically set these things up for you."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//kernel-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/kernel-upgrade.xml.po b/doc/gettext/ru/kernel-upgrade.xml.po
new file mode 100644
index 0000000..e0a727d
--- /dev/null
+++ b/doc/gettext/ru/kernel-upgrade.xml.po
@@ -0,0 +1,569 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(guide:link):5
+msgid "/doc/en/kernel-upgrade.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):6
+msgid "Gentoo Linux Kernel Upgrade Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(mail:link):8
+msgid "dsd@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(mail):8
+msgid "Daniel Drake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(abstract):11
+msgid ""
+"This document describes the process of upgrading your kernel from one "
+"release to another."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(version):20
+msgid "0.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(date):21
+msgid "2007-06-22"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):28
+msgid ""
+"The kernel is one of the few package classes in portage that requires some "
+"manual intervention to complete the upgrade. Portage will download and "
+"install the kernel source for you, but then it is up to you to step in and "
+"compile the new kernel before any changes will take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):35
+msgid ""
+"Although this guide is targeted at users upgrading from one kernel release "
+"to another, it will also be useful for users migrating from one kernel "
+"package to another."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):41
+msgid ""
+"<c>gentoo-sources</c> is used as an example in this document, however, the "
+"instructions here also apply to the other packages present in our tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):51
+msgid "Why upgrade the kernel?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):55
+msgid ""
+"Generally, upgrading from one minor kernel release to the next won't bring "
+"any major differences. There are several reasons to upgrade the kernel. One "
+"is to take advantage of a specific new feature or driver; another is to be "
+"protected against a security vulnerability, or just to maintain an up-to-"
+"date and healthy system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):63
+msgid ""
+"Even if you choose not to update to every new kernel revision, it is "
+"recommended that you at least upgrade from time to time. It is strongly "
+"recommended that you immediately upgrade to a new kernel if that new release "
+"solves a security problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):75
+msgid "Obtaining the newer sources through Portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):79
+msgid ""
+"You upgrade the kernel sources like you would upgrade any other package - "
+"using the <c>emerge</c> utility. It will probably be the case that you want "
+"to upgrade your kernel when you see the upgrade appearing on your world "
+"updates list. For example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):86
+msgid "New kernel sources appearing on update list"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):86
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -Dup world</i>\n"
+"Calculating dependencies ...done!\n"
+"[ebuild    NS ] sys-kernel/gentoo-sources-2.6.9-r2 [2.6.8-r5]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(note):92
+msgid ""
+"The \"NS\" label in the above output means that the new kernel will be "
+"installed in a New Slot, i.e. the sources of your old kernel will be kept "
+"around, until you manually remove them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):98
+msgid "You can then go ahead and install the update, e.g.:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):102
+msgid "Upgrading your kernel sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):102
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -u gentoo-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):106
+msgid ""
+"The kernel sources will then be installed into a subdirectory of <path>/usr/"
+"src</path>. In the above example, the new kernel sources will be installed "
+"at <path>/usr/src/linux-2.6.9-gentoo-r2</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):117
+msgid "Updating the /usr/src/linux symbolic link"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):121
+msgid ""
+"Gentoo requires that the <path>/usr/src/linux</path> symbolic link points to "
+"the sources of the kernel you are running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):126
+msgid ""
+"Portage can update the symlink automatically when you emerge new kernel "
+"sources. All you have to do is add the <c>symlink</c> flag to the USE "
+"variable in <path>/etc/make.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):132
+msgid "Example of USE variable in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):132
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Add the symlink keyword)</comment>\n"
+"USE=\"<i>symlink</i> x86 3dnow 3dnowex X aac aalib adns alsa apache2\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):137
+msgid ""
+"Alternatively, you could use <c>app-admin/eselect</c> to modify the symlink."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):141
+msgid "Using eselect to symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):141
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Install eselect if you don't have it)</comment>\n"
+"# <i>emerge eselect</i>\n"
+"<comment>(See the list of available kernels)</comment>\n"
+"# <i>eselect kernel list</i>\n"
+"Available kernel symlink targets:\n"
+"  [1]   linux-2.6.9-gentoo-r1\n"
+"  [2]   linux-2.6.9-gentoo-r2\n"
+"<comment>(Select the correct kernel)</comment>\n"
+"# <i>eselect kernel set 1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):153
+msgid ""
+"If you really want to do it yourself, the following example shows you how to "
+"make the link point to <path>linux-2.6.9-gentoo-r2</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):158
+msgid "Updating the /usr/src/linux softlink manually"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):158
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src</i>\n"
+"# <i>ln -sfn linux-2.6.9-gentoo-r2 linux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):168
+msgid "Configuring, compiling and installing the new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):172
+msgid ""
+"For either of these options, you should refer to the instructions given in "
+"the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri> relating to "
+"<e>Configuring the Kernel</e> and <e>Configuring the Bootloader</e>. Below "
+"is an outline of the required actions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):182
+msgid "Option 1: Automatic kernel setup with Genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):185
+msgid ""
+"If you are a genkernel user, you just need to repeat the stages you went "
+"through when installing your kernel for the first time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):190
+msgid "Simply run genkernel in the normal way:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):194
+msgid "Invoking genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):194
+#, no-wrap
+msgid ""
+"\n"
+"# <i>genkernel all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):198
+msgid ""
+"You can also use extra parameters for other genkernel functionality. For "
+"example, if you wish to configure some extra kernel options using "
+"<c>menuconfig</c> and you wish genkernel to automatically update your grub "
+"boot loader configuration, then invoke genkernel as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):205
+msgid "Invoking genkernel with some common arguments"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):205
+#, no-wrap
+msgid ""
+"\n"
+"# <i>genkernel --menuconfig --bootloader=grub all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):209
+msgid ""
+"For more info, follow the <uri link=\"/doc/en/genkernel.xml\">Gentoo Linux "
+"Genkernel Guide</uri>, or refer to the <uri link=\"/doc/en/handbook/"
+"\">Gentoo Handbook</uri>. Many of the options can be set in the "
+"configuration file for <c>genkernel</c>, <path>/etc/genkernel.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):219
+msgid "Option 2: Manual configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):222
+msgid "To begin, open the <c>menuconfig</c> utility in the kernel source tree:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):226
+msgid "Invoking menuconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):226
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):231
+msgid ""
+"Select the options required for your hardware and operating environment. For "
+"additional information on kernel configuration, refer to the chapter "
+"entitled <e>Configuring the Kernel</e> of the <uri link=\"/doc/en/handbook/"
+"index.xml\">Gentoo Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):238
+msgid ""
+"Next, compile your kernel and copy it over to your boot partition. Again, "
+"follow the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> "
+"instructions outlined in the chapter on <e>Configuring the Bootloader</e>. "
+"If <path>/boot</path> is a separate partition, ensure it is mounted before "
+"copying the compiled kernel to this directory! Failing to do so would keep "
+"you from booting the system with your new kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):247
+msgid "Compiling and installing the new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):247
+#, no-wrap
+msgid ""
+"\n"
+"# <i>make &amp;&amp; make modules_install</i>\n"
+"# <i>mount /boot</i>\n"
+"# <i>cp arch/i386/boot/bzImage /boot/bzImage-2.6.9-gentoo-r2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):253
+msgid ""
+"Finally, you should update your boot loader configuration, adding an entry "
+"for the new kernel (don't delete the old one just yet!) and unmount the "
+"<path>/boot</path> partition. Again, refer to the <uri link=\"/doc/en/"
+"handbook/index.xml\">Gentoo Handbook</uri> for detailed instructions on this "
+"procedure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):266
+msgid "Reinstalling external modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):270
+msgid ""
+"If you use any kernel modules that are not included in the kernel source "
+"tree but are provided elsewhere in Portage (e.g. ALSA drivers and NVIDIA or "
+"ATI graphics drivers), then you must reinstall these after upgrading the "
+"kernel. This is as simple as re-merging the packages involved. For more "
+"information, refer to the chapter on <e>Configuring the Kernel</e> in the "
+"<uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):279
+msgid ""
+"We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which "
+"rebuilds all the kernel modules you have installed using separate ebuilds "
+"for the kernel at <path>/usr/src/linux</path>. Its use is straightforward. "
+"After emerging it, simply run <c>module-rebuild populate</c> to populate the "
+"database with a list of packages that will need to be rebuilt after "
+"upgrading the kernel. Once you have finished upgrading or recompiling your "
+"kernel, run <c>module-rebuild rebuild</c> to rebuild the drivers for your "
+"new kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):289
+msgid ""
+"For more information, run <c>module-rebuild</c> without any options to see a "
+"list of commands that can be passed to the utility."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):299
+msgid "Rebooting into the new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):303
+msgid ""
+"Next, close all applications and reboot your system. If you followed the "
+"above instructions correctly, the boot loader menu should include an entry "
+"for the new kernel. Select the new kernel and let the system boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):309
+msgid ""
+"Hopefully, your system successfully boots with the new kernel, and you can "
+"log in to resume whatever you were doing. If this is the case, then the "
+"upgrade is complete."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):315
+msgid ""
+"If you made a mistake and the system fails to boot with the new kernel, "
+"reboot the system and select the entry from the boot loader that corresponds "
+"to the last known working kernel. You can then restart from the <uri link="
+"\"#install\"> Configuring, compiling, and installing the new kernel</uri> "
+"stage -- making the appropriate changes to correct your mistake. In some "
+"cases, you might not even need to reboot to do this (e.g. you missed a "
+"driver for an audio device, Ethernet adapter, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):330
+msgid "Running multiple kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):334
+msgid ""
+"You may have noticed, that when installing the sources for your newer "
+"kernel, the sources for your existing kernel were not removed. This is by "
+"design -- it allows you to easily switch between running different kernels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):340
+msgid ""
+"Switching between multiple kernels is as simple as leaving the kernel "
+"sources under <path>/usr/src/</path> and leaving the <path>bzImage</path> "
+"binaries on your <path>/boot</path> partition (referenced by entries in your "
+"boot loader configuration). Every time you boot up, you will be presented "
+"with a choice of which kernel to boot into."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):353
+msgid "Removing older kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):357
+msgid ""
+"Continuing on from the last section, you may be happy with your new kernel "
+"and not have any need to keep older kernel versions around. To easily remove "
+"all sources for a particular kernel except for the newest one, you can take "
+"advantage of the <e>prune</e> option available through <c>emerge</c>. "
+"Continuing the example using <c>gentoo-sources</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):365
+msgid "Pruning old versions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):365
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -P gentoo-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):369
+msgid ""
+"In most cases, temporary files used during compilation will still remain "
+"under the appropriate source directory under <path>/usr/src</path>. It is "
+"safe to remove these using <c>rm</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):375
+msgid ""
+"You can also safely delete any modules that were used by this kernel. This "
+"can be done by removing the appropriate directories under <path>/lib/modules/"
+"</path> that relate to the kernel versions you are removing. Be careful not "
+"to delete modules belonging to kernels that you still use!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):382
+msgid ""
+"Finally, you can mount your <path>/boot</path> partition and remove the "
+"<path>bzImage</path> file(s) for the kernel(s) you are pruning. You should "
+"also edit your boot loader configuration so that it no longer references "
+"such kernel(s)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):394
+msgid "Advanced: Using your old kernel .config to configure a new one"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):398
+msgid ""
+"It is sometimes possible to save time by re-using the configuration file "
+"from your old kernel when configuring the new one. Note that this is "
+"generally unsafe -- too many changes between every kernel release for this "
+"to be a reliable upgrade path."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):405
+msgid ""
+"The only situation where this is appropriate is when upgrading from one "
+"Gentoo kernel revision to another. For example, the changes made between "
+"<c>gentoo-sources-2.6.9-r1</c> and <c>gentoo-sources-2.6.9-r2</c> will be "
+"very small, so it is usually OK to use the following method. However, it is "
+"not appropriate to use it in the example used throughout this document: "
+"upgrading from 2.6.8 to 2.6.9. Too many changes between the official "
+"releases, and the method described below does not display enough context to "
+"the user, often resulting in the user running into problems because they "
+"disabled options that they really didn't want to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):417
+msgid ""
+"To reuse your old <path>.config</path>, you simply need to copy it over and "
+"then run <c>make oldconfig</c>. In the following example, we take the "
+"configuration from <c>gentoo-sources-2.6.9-r1</c> and import it into "
+"<c>gentoo-sources-2.6.9-r2</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):424
+msgid "Reusing your old config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):424
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux-2.6.9-gentoo-r2</i>\n"
+"# <i>cp ../linux-2.6.9-gentoo-r1/.config .</i>\n"
+"# <i>make oldconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):430
+msgid "Reusing your old config with genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):430
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/kernels</i>\n"
+"# <i>cp kernel-config-x86-2.6.9-gentoo-r1 kernel-config-x86-2.6.9-gentoo-r2</i>\n"
+"# <i>genkernel all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):436
+msgid ""
+"At this point, you may be asked to produce answers for configuration options "
+"which have changed between the two versions. Once you have done that, you "
+"can compile and install your kernel as normal, without having to go through "
+"the <c>menuconfig</c> configuration process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):443
+msgid ""
+"A much safer upgrading method is to copy your config as previously shown, "
+"and then simply run <c>make menuconfig</c>. This avoids the problems of "
+"<c>make oldconfig</c> mentioned previously, as <c>make menuconfig</c> will "
+"load up your previous configuration as much as possible into the menu. Now "
+"all you have to do is go through each option and look for new sections, "
+"removals, and so on. By using <c>menuconfig</c>, you gain context for all "
+"the new changes, and can easily view the new choices and review help screens "
+"much easier. You can even use this for upgrades such as 2.6.8 to 2.6.9; just "
+"make sure you read through the options carefully. Once you've finished, "
+"compile and install your kernel as normal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):461
+msgid "Problems after a kernel upgrade?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):465
+msgid ""
+"With the rapid development of the Linux kernel, it is inevitable that some "
+"changes made from one kernel release to another may cause some problems. If "
+"you have any issues with the latest versions of <uri link=\"/doc/en/gentoo-"
+"kernel.xml#doc_chap2\"> Gentoo-supported kernels</uri> then please do report "
+"the issues to us."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/keychain-guide.xml.po b/doc/gettext/ru/keychain-guide.xml.po
new file mode 100644
index 0000000..33ad5fe
--- /dev/null
+++ b/doc/gettext/ru/keychain-guide.xml.po
@@ -0,0 +1,495 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):6
+msgid "Gentoo Linux Keychain Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail:link):9
+msgid "eric.brown@dnbrown.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail):9
+msgid "Eric Brown"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail:link):12
+msgid "vanquirius@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail):12
+msgid "Marcelo Góes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(abstract):18
+msgid ""
+"This document describes how to use ssh shared keys along with the keychain "
+"program. It assumes basic knowledge of public key cryptography."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(version):27
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(date):28
+msgid "2010-04-21"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):31
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):33
+msgid "The problem at hand"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):36
+msgid ""
+"So you have all of these lovely Gentoo machines running <c>sshd</c>, but "
+"it's a little inconvenient for you to keep typing in all of those login "
+"passwords, right? Or maybe you have a script or cron-job that needs a "
+"convenient way to use an ssh connection. Either way, there is a solution to "
+"this problem, and it begins with public key authentication."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):47
+msgid "How does public key authentication work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):50
+msgid ""
+"Assume we have a client that wants to connect to sshd on a server. The "
+"client first generates a key pair and gives the public key to the server. "
+"Afterwards, whenever the client attempts to connect, the server sends a "
+"challenge that is encrypted with that public key. Only the holder of the "
+"corresponding private key (the client) is able to decrypt it, so as you "
+"might have guessed, the correct response leads to successful authentication."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):63
+msgid "How to use public key authentication"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):65
+msgid "Generating your key pair"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):68
+msgid ""
+"The first step is to create your key pair. To do this, we will use the "
+"<c>ssh-keygen</c> command as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):73
+msgid "Generating the key pair"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):73
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>ssh-keygen -t dsa</i>\n"
+"<comment>(Just accept the default values, and make sure to enter a strong passphrase)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(warn):78
+msgid ""
+"Be sure to choose a strong passphrase, especially if this key is used for "
+"root logons!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):83
+msgid ""
+"You should now have a private key in <path>~/.ssh/id_dsa</path> and a public "
+"key in <path>~/.ssh/id_dsa.pub</path>. We are ready to copy the public key "
+"over to the remote host."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):92
+msgid "Preparing the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):95
+msgid ""
+"We will be copying the <path>~/.ssh/id_dsa.pub</path> file over to the "
+"server that runs sshd. We will also be adding it to the <path>~/.ssh/"
+"authorized_keys</path> file that belongs the connecting user on that server. "
+"Here's an example of how to do that if you already have ssh access to the "
+"server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):103
+msgid "Copying the public key to the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):103
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>scp ~/.ssh/id_dsa.pub server_user@server:~/myhost.pub</i>\n"
+"$ <i>ssh server_user@server \"cat ~/myhost.pub &gt;&gt; ~/.ssh/authorized_keys\"</i>\n"
+"$ <i>ssh server_user@server \"cat ~/.ssh/authorized_keys\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):109
+msgid ""
+"The output from that last line should show you the contents of the <path>~/."
+"ssh/authorized_keys</path> file. Make sure it looks correct."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):117
+msgid "Testing the setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):120
+msgid ""
+"Theoretically, if all went well, and the ssh daemon on the server allows it, "
+"we should be able to get ssh access without a password on the server now. We "
+"will still need to decrypt the private key on the client with the passphrase "
+"we used before, but this should not be confused with the passphrase of the "
+"user account on the server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):128
+msgid "Testing the keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):128
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>ssh server_user@server</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):132
+msgid ""
+"Hopefully, it asked you for your passphrase for id_dsa, and you were able to "
+"gain ssh access as server_user on the server. If not, login as server_user, "
+"and verify the contents of <path>~/.ssh/authorized_keys</path> to make sure "
+"each entry is on a single line. You might also want to check the sshd "
+"configuration to make sure that it prefers to use public key authorization "
+"when available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):140
+msgid ""
+"At this point, you're probably thinking, \"What's the point, I just replaced "
+"one password with another?!\" Relax, the next section will show you exactly "
+"how we can use this to save your precious time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):150
+msgid "Making public key authentication convenient"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):152
+msgid "Typical key management with ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):155
+msgid ""
+"If you've been following along, you're probably thinking that it would be "
+"great if we could somehow decrypt our private key(s) once, and gain the "
+"ability to ssh freely, without any passwords. You are in luck, that is "
+"exactly what the program <c>ssh-agent</c> is for."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):162
+msgid ""
+"The program <c>ssh-agent</c> is usually started at the beginning of your X "
+"session, or from a shell startup script like <path>~/.bash_profile</path>. "
+"It works by creating a unix-socket, and registering the appropriate "
+"environment variables so that all subsequent applications can take advantage "
+"of it's services by connecting to that socket. Clearly, it only makes sense "
+"to start it in the parent process of your X session if you want to use the "
+"set of decrypted private keys in all subsequent X applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):172
+msgid "Preparing ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):172
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>ssh-agent</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(note):176
+msgid ""
+"This ssh-agent will keep keys decrypted until you kill ssh-agent. If you "
+"want to set a lifetime for the keys, use the -t argument as described in "
+"<c>man ssh-agent</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):182
+msgid ""
+"When you run ssh-agent, it should tell you the PID of the running ssh-agent, "
+"and also set a few environment variables, namely <c>SSH_AUTH_SOCK</c> and "
+"<c>SSH_AGENT_PID</c>. It should also automatically add <path>~/.ssh/id_dsa</"
+"path> to it's collection and ask you for the corresponding passphrase. If "
+"you have other private keys you want to add to the running ssh-agent, you "
+"can use the <c>ssh-add</c> command as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):191
+msgid "Adding more keys to ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):191
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>ssh-add somekeyfile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):195
+msgid ""
+"Now for the magic. Since you should now have your decrypted private key "
+"ready, you should be able to ssh into the server without entering any "
+"passwords."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):200
+msgid "Ssh without passwords"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):200
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>ssh server</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):204
+msgid ""
+"It would be nice to know how to shut down ssh-agent in case you need to, "
+"right?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):208
+msgid "Shutting down ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):208
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>ssh-agent -k</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(note):212
+msgid ""
+"If you had problems getting ssh-agent to work, it might still be running. "
+"You can kill it like any other process by running <c>killall ssh-agent</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):217
+msgid ""
+"If you want even more convenience from ssh-agent, proceed to the next "
+"section on using keychain. Be sure to kill the running ssh-agent as in the "
+"example above if you decide to do so."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):226
+msgid "Squeezing the last drop of convenience out of ssh-agent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):229
+msgid ""
+"Keychain will allow you to reuse an ssh-agent between logins, and optionally "
+"prompt for passphrases each time the user logs in. Before we get ahead of "
+"ourselves though, let's emerge it first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):235
+msgid "Installing keychain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):235
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge keychain</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):239
+msgid ""
+"Assuming that was successful, we can now use keychain freely. Add the "
+"following to your <path>~/.bash_profile</path> to enable it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):244
+msgid "Enabling keychain in .bash_profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):244
+#, no-wrap
+msgid ""
+"\n"
+"keychain ~/.ssh/id_dsa\n"
+". ~/.keychain/$HOSTNAME-sh\n"
+". ~/.keychain/$HOSTNAME-sh-gpg\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(note):250
+msgid ""
+"You can add more private keys to the command line as you desire. Also, if "
+"you want it to ask for passphrases each time you spawn a shell, add the --"
+"clear option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(note):256
+msgid ""
+"If you are not using bash, check the <b>EXAMPLES</b> section of <c>man "
+"keychain</c> for examples of use in other shells. The idea is to get those "
+"commands to run each time you use a shell."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):262
+msgid ""
+"Let's test it. First make sure we killed the ssh-agent from the previous "
+"section, then start up a new shell, usually by just logging in, or spawning "
+"a new terminal. It should prompt you for the password for each key you "
+"specified on the command line. All shells opened after that point should "
+"reuse the ssh-agent, allowing you to make passwordless ssh connections over "
+"and over."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):273
+msgid "Using keychain with KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):276
+msgid ""
+"If you are a KDE user, instead of using <path>~/.bash_profile</path>, you "
+"can let KDE manage ssh-agent for you. In order to do so, you will have to "
+"edit <path>/etc/kde/agent-startup.sh</path>, which is read during KDE's "
+"startup, and <path>/etc/kde/shutdown/agent-shutdown.sh</path>, which is "
+"executed during KDE's shutdown. Here is how you could edit those files:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):284
+msgid "Editing /etc/kde/agent-startup.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):284
+#, no-wrap
+msgid ""
+"\n"
+"if [ -x /usr/bin/ssh-agent ]; then\n"
+"  eval \"$(/usr/bin/ssh-agent -s)\"\n"
+"fi\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):290
+msgid "Editing /etc/kde/shutdown/agent-shutdown.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):290
+#, no-wrap
+msgid ""
+"\n"
+"if [ -n \"${SSH_AGENT_PID}\" ]; then\n"
+"  eval \"$(ssh-agent -k)\"\n"
+"fi\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):296
+msgid ""
+"Now, all you have to do is launch a term of your choice, like Konsole, and "
+"load the keys you would like to use. For example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre:caption):301
+msgid "Loading ssh key"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(pre):301
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>keychain ~/.ssh/id_dsa</i>\n"
+"<comment>(Enter your key password)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):306
+msgid ""
+"Your keys will be remembered until you end your KDE session or kill the ssh-"
+"agent manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):316
+msgid "Concluding remarks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):318
+msgid "Security considerations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):321
+msgid ""
+"Of course, the use of ssh-agent may add a bit of insecurity to your system. "
+"If another user were to use your shell while you were in the bathroom, he "
+"could login to all of your servers without passwords. As a result, it is a "
+"risk to the servers you are connecting to, and you should be sure to consult "
+"the local security policy. If you do use it, be sure to take the appropriate "
+"measures to ensure the security of your sessions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(title):333
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(p):336
+msgid ""
+"Most of this should work pretty well, but if you encounter problems, you'll "
+"certainly want to know a few useful things."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(li):342
+msgid ""
+"If you are unable to connect without ssh-agent, consider using ssh with the "
+"arguments -vvv to find out what's happening. Sometimes the server is not "
+"configured to use public key authentication, sometimes it is configured to "
+"ask for local passwords anyway! If that is the case, you may want to also "
+"use the -o option with ssh, or change the server sshd_config."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(li):349
+msgid ""
+"If you are having problems with ssh-agent or keychain, it may be that you "
+"are not using a shell that understands the commands they use. Consult the "
+"man pages for ssh-agent and keychain for details on working with other "
+"shells."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//keychain-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/ldap-howto.xml.po b/doc/gettext/ru/ldap-howto.xml.po
new file mode 100644
index 0000000..d0dde72
--- /dev/null
+++ b/doc/gettext/ru/ldap-howto.xml.po
@@ -0,0 +1,667 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):6
+msgid "Gentoo Guide to OpenLDAP Authentication"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):9
+msgid "sj7trunks@pendulus.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail):9
+msgid "Benjamin Coles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):12
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail):12
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):15
+msgid "tseng@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail):15
+msgid "Brandon Hale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):18
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail):18
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):21
+msgid "jokey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(abstract):27
+msgid ""
+"This guide introduces the basics of LDAP and shows you how to setup OpenLDAP "
+"for authentication purposes between a group of Gentoo boxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(version):36
+msgid "4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(date):37
+msgid "2010-07-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):40
+msgid "Getting Started with OpenLDAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):42
+msgid "What is LDAP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):45
+msgid ""
+"LDAP stands for <e>Lightweight Directory Access Protocol</e>. Based on X.500 "
+"it encompasses most of its primary functions, but lacks the more esoteric "
+"functions that X.500 has. Now what is this X.500 and why is there an LDAP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):52
+msgid ""
+"X.500 is a model for Directory Services in the OSI concept. It contains "
+"namespace definitions and the protocols for querying and updating the "
+"directory. However, X.500 has been found to be overkill in many situations. "
+"Enter LDAP. Like X.500 it provides a data/namespace model for the directory "
+"and a protocol too. However, LDAP is designed to run directly over the TCP/"
+"IP stack. See LDAP as a slim-down version of X.500."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):65
+msgid "I don't get it. What is a directory?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):68
+msgid ""
+"A directory is a specialized database designed for frequent queries but "
+"infrequent updates. Unlike general databases they don't contain transaction "
+"support or roll-back functionality. Directories are easily replicated to "
+"increase availability and reliability. When directories are replicated, "
+"temporary inconsistencies are allowed as long as they get synchronised "
+"eventually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):81
+msgid "How is information structured?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):84
+msgid ""
+"All information inside a directory is structured hierarchically. Even more, "
+"if you want to enter data inside a directory, the directory must know how to "
+"store this data inside a tree. Lets take a look at a fictional company and "
+"an Internet-like tree:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):91
+msgid "Organisational structure for GenFic, a Fictional Gentoo company"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):91
+#, no-wrap
+msgid ""
+"\n"
+"dc:         com\n"
+"             |\n"
+"dc:        genfic         <comment>(Organisation)</comment>\n"
+"          /      \\\n"
+"ou:   People   servers    <comment>(Organisational Units)</comment>\n"
+"      /    \\     ..\n"
+"uid: ..   John            <comment>(OU-specific data)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):101
+msgid ""
+"Since you don't feed data to the database in this ascii-art like manner, "
+"every node of such a tree must be defined. To name such nodes, LDAP uses a "
+"naming scheme. Most LDAP distributions (including OpenLDAP) already contain "
+"quite a number of predefined (and general approved) schemes, such as the "
+"inetorgperson, a frequently used scheme to define users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):109
+msgid ""
+"Interested users are encouraged to read the <uri link=\"http://www.openldap."
+"org/doc/admin24/\">OpenLDAP Admin Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):117
+msgid "So... What's the Use?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):120
+msgid ""
+"LDAP can be used for various things. This document focuses on centralised "
+"user management, keeping all user accounts in a single LDAP location (which "
+"doesn't mean that it's housed on a single server, LDAP supports high "
+"availability and redundancy), yet other goals can be achieved using LDAP as "
+"well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):128
+msgid "Public Key Infrastructure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):129
+msgid "Shared Calendar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):130
+msgid "Shared Addressbook"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):131
+msgid "Storage for DHCP, DNS, ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):132
+msgid ""
+"System Class Configuration Directives (keeping track of several server "
+"configurations)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(li):136
+msgid "..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):144
+msgid "Configuring OpenLDAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):146
+msgid "Initial Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(note):149
+msgid ""
+"In this document we use the genfic.com address as an example. You will "
+"ofcourse have to change this. However, make sure that the top node is an "
+"official top level domain (net, com, cc, be, ...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):155
+msgid "Let's first emerge OpenLDAP:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):159
+msgid "Install OpenLDAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):159
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge openldap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):163
+msgid "Now generate an encrypted password we'll use later on:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):167
+msgid "Generate password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):167
+#, no-wrap
+msgid ""
+"\n"
+"# <i>slappasswd</i>\n"
+"New password: my-password\n"
+"Re-enter new password: my-password\n"
+"{SSHA}EzP6I82DZRnW+ou6lyiXHGxSpSOw2XO4\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):174
+msgid ""
+"Now edit the LDAP Server config at <path>/etc/openldap/slapd.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):178
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):417
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):440
+msgid "/etc/openldap/slapd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):178
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Include the needed data schemes below core.schema</comment>\n"
+"include         /etc/openldap/schema/cosine.schema\n"
+"include         /etc/openldap/schema/inetorgperson.schema\n"
+"include         /etc/openldap/schema/nis.schema\n"
+"\n"
+"<comment>Uncomment modulepath and hdb module</comment>\n"
+"# Load dynamic backend modules:\n"
+"modulepath    /usr/lib/openldap/openldap\n"
+"# moduleload    back_shell.so\n"
+"# moduleload    back_relay.so\n"
+"# moduleload    back_perl.so\n"
+"# moduleload    back_passwd.so\n"
+"# moduleload    back_null.so\n"
+"# moduleload    back_monitor.so\n"
+"# moduleload    back_meta.so\n"
+"moduleload    back_hdb.so\n"
+"# moduleload    back_dnssrv.so\n"
+"\n"
+"<comment># Uncomment sample access restrictions (Note: maintain indentation!)</comment>\n"
+"access to dn.base=\"\" by * read\n"
+"access to dn.base=\"cn=Subschema\" by * read\n"
+"access to *\n"
+"   by self write\n"
+"   by users read\n"
+"   by anonymous auth\n"
+"\n"
+"\n"
+"<comment># BDB Database definition</comment>\n"
+"\n"
+"database        hdb\n"
+"suffix          \"dc=genfic,dc=com\"\n"
+"checkpoint      32      30 # &lt;kbyte&gt; &lt;min&gt;\n"
+"rootdn          \"cn=Manager,dc=genfic,dc=com\"\n"
+"rootpw          <i>{SSHA}EzP6I82DZRnW+ou6lyiXHGxSpSOw2XO4</i>\n"
+"directory       /var/lib/openldap-ldbm\n"
+"index           objectClass     eq\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):217
+msgid "Next we edit the LDAP Client configuration file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):221
+msgid "/etc/openldap/ldap.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):221
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/openldap/ldap.conf</i>\n"
+"<comment>(Add the following...)</comment>\n"
+"\n"
+"BASE         dc=genfic, dc=com\n"
+"URI          ldap://auth.genfic.com:389/\n"
+"TLS_REQCERT  allow\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):230
+msgid ""
+"Now edit <path>/etc/conf.d/slapd</path> and uncomment the following OPTS "
+"line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):234
+msgid "/etc/conf.d/slapd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):234
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Note: we don't use cn=config here, so stay with this line:</comment>\n"
+"OPTS=\"-F /etc/openldap/slapd.d -h 'ldaps:// ldap:// ldapi://%2fvar%2frun%2fopenldap%2fslapd.sock'\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):239
+msgid "Start slapd:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):243
+msgid "Starting SLAPd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):243
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/slapd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):247
+msgid "You can test with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):251
+msgid "Test the SLAPd daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):251
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ldapsearch -x -D \"cn=Manager,dc=genfic,dc=com\" -W</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):255
+msgid ""
+"If you receive an error, try adding <c>-d 255</c> to increase the verbosity "
+"and solve the issue you have."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):265
+msgid "Client Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):267
+msgid "Migrate existing data to ldap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):270
+msgid ""
+"Go to <uri link=\"http://www.padl.com/OSS/MigrationTools.html\">http://www."
+"padl.com/OSS/MigrationTools.html</uri> and fetch the scripts there. "
+"Configuration is stated on the page. We don't ship this anymore because the "
+"scripts are a potential security hole if you leave them on the system after "
+"porting. When you've finished migrating your data, continue to the next "
+"section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):282
+msgid "Configuring PAM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):285
+msgid ""
+"First, we will configure PAM to allow LDAP authorization. Install <c>sys-"
+"auth/pam_ldap</c> so that PAM supports LDAP authorization, and <c>sys-auth/"
+"nss_ldap</c> so that your system can cope with LDAP servers for additional "
+"information (used by <path>nsswitch.conf</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):292
+msgid "Installing pam_ldap and nss_ldap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):292
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge pam_ldap nss_ldap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):296
+msgid ""
+"Now add the following lines in the right places to <path>/etc/pam.d/system-"
+"auth</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):301
+msgid "/etc/pam.d/system-auth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):301
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Note: only add them. Don't kill stuff already in there or your box won't let you login again!</comment>\n"
+"\n"
+"auth       sufficient   pam_ldap.so use_first_pass\n"
+"account    sufficient   pam_ldap.so\n"
+"password   sufficient   pam_ldap.so use_authtok use_first_pass\n"
+"session    optional     pam_ldap.so\n"
+"\n"
+"<comment># Example file:</comment>\n"
+"#%PAM-1.0\n"
+"\n"
+"auth       required     pam_env.so\n"
+"auth       sufficient   pam_unix.so try_first_pass likeauth nullok\n"
+"<i>auth       sufficient   pam_ldap.so use_first_pass</i>\n"
+"auth       required     pam_deny.so\n"
+"\n"
+"<i>account    sufficient   pam_ldap.so</i>\n"
+"account    required     pam_unix.so\n"
+"\n"
+"password   required     pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 try_first_pass retry=3\n"
+"password   sufficient   pam_unix.so try_first_pass use_authtok nullok md5 shadow\n"
+"<i>password   sufficient   pam_ldap.so use_authtok use_first_pass</i>\n"
+"password   required     pam_deny.so\n"
+"\n"
+"session    required     pam_limits.so\n"
+"session    required     pam_unix.so\n"
+"<i>session    optional     pam_ldap.so</i>\n"
+"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):331
+msgid "Now change <path>/etc/ldap.conf</path> to read:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):335
+msgid "/etc/ldap.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):335
+#, no-wrap
+msgid ""
+"\n"
+"<comment>#host 127.0.0.1</comment>\n"
+"<comment>#base dc=padl,dc=com</comment>\n"
+"\n"
+"suffix          \"dc=genfic,dc=com\"\n"
+"<comment>#rootbinddn uid=root,ou=People,dc=genfic,dc=com</comment>\n"
+"\n"
+"uri ldap://auth.genfic.com/\n"
+"pam_password exop\n"
+"\n"
+"ldap_version 3\n"
+"pam_filter objectclass=posixAccount\n"
+"pam_login_attribute uid\n"
+"pam_member_attribute memberuid\n"
+"nss_base_passwd ou=People,dc=genfic,dc=com\n"
+"nss_base_shadow ou=People,dc=genfic,dc=com\n"
+"nss_base_group  ou=Group,dc=genfic,dc=com\n"
+"nss_base_hosts  ou=Hosts,dc=genfic,dc=com\n"
+"\n"
+"scope one\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):357
+msgid ""
+"Next, copy over the (OpenLDAP) <path>ldap.conf</path> file from the server "
+"to the client so the clients are aware of the LDAP environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):362
+msgid "Copying over the OpenLDAP ldap.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):362
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Substitute ldap-server with your LDAP server name)</comment>\n"
+"# <i>scp ldap-server:/etc/openldap/ldap.conf /etc/openldap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):367
+msgid ""
+"Finally, configure your clients so that they check the LDAP for system "
+"accounts:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):372
+msgid "/etc/nsswitch.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):372
+#, no-wrap
+msgid ""
+"\n"
+"passwd:         files ldap\n"
+"group:          files ldap\n"
+"shadow:         files ldap\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):378
+msgid "To test the changes, type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre:caption):382
+msgid "Testing LDAP Auth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):382
+#, no-wrap
+msgid ""
+"\n"
+"# <i>getent passwd|grep 0:0</i>\n"
+"\n"
+"<comment>(You should get two entries back:)</comment>\n"
+"root:x:0:0:root:/root:/bin/bash\n"
+"root:x:0:0:root:/root:/bin/bash\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):390
+msgid ""
+"If you noticed one of the lines you pasted into your <path>/etc/ldap.conf</"
+"path> was commented out (the <c>rootbinddn</c> line): you don't need it "
+"unless you want to change a user's password as superuser. In this case you "
+"need to echo the root password to <path>/etc/ldap.secret</path> in "
+"plaintext. This is <brite>DANGEROUS</brite> and should be chmoded to 600. "
+"What I do is keep that file blank and when I need to change someones "
+"password thats both in the ldap and <path>/etc/passwd</path> I put the pass "
+"in there for 10 seconds while I change it and remove it when I'm done."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):406
+msgid "LDAP Server Security Settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):408
+msgid "OpenLDAP permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):411
+msgid ""
+"If we take a look at <path>/etc/openldap/slapd.conf</path> you'll see that "
+"you can specify the ACLs (permissions if you like) of what data users can "
+"read and/or write:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):417
+#, no-wrap
+msgid ""
+"\n"
+"access to *\n"
+"  by dn=\"uid=root,ou=People,dc=genfic,dc=com\" write\n"
+"  by users read\n"
+"  by anonymous auth\n"
+"\n"
+"access to attrs=userPassword,gecos,description,loginShell\n"
+"  by self write\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):427
+msgid ""
+"This gives you access to everything a user should be able to change. If it's "
+"your information, then you got write access to it; if it's another user "
+"their information then you can read it; anonymous people can send a login/"
+"pass to get logged in. There are four levels, ranking them from lowest to "
+"greatest: <c>auth search read write</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):435
+msgid ""
+"The next ACL is a bit more secure as it blocks normal users to read other "
+"people their shadowed password:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(pre):440
+#, no-wrap
+msgid ""
+"\n"
+"access to attrs=\"userPassword\"\n"
+"  by dn=\"uid=root,ou=People,dc=genfic,dc=com\" write\n"
+"  by dn=\"uid=John,ou=People,dc=genfic,dc=com\" write\n"
+"  by anonymous auth\n"
+"  by self write\n"
+"  by * none\n"
+"\n"
+"access to *\n"
+"  by dn=\"uid=root,ou=People,dc=genfic,dc=com\" write\n"
+"  by dn=\"uid=John,ou=People,dc=genfic,dc=com\" write\n"
+"  by * search\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):454
+msgid ""
+"This example gives root and John access to read/write/search for everything "
+"in the the tree below <path>dc=genfic,dc=com</path>. This also lets users "
+"change their own <path>userPassword</path>'s. As for the ending statement "
+"everyone else just has a search ability meaning they can fill in a search "
+"filter, but can't read the search results. Now you can have multiple acls "
+"but the rule of the thumb is it processes from bottom up, so your toplevel "
+"should be the most restrictive ones."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):469
+msgid "Working with OpenLDAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):471
+msgid "Maintaining the directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):474
+msgid ""
+"You can start using the directory to authenticate users in apache/proftpd/"
+"qmail/samba. You can manage it with Webmin, which provides an easy "
+"management interface. You can also use phpldapadmin, diradm, jxplorer, or "
+"lat."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(title):486
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(p):490
+msgid ""
+"We would like to thank Matt Heler for lending us his box for the purpose of "
+"this guide. Thanks also go to the cool guys in #ldap @ irc.freenode.net"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//ldap-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/list.xml.po b/doc/gettext/ru/list.xml.po
new file mode 100644
index 0000000..63307d0
--- /dev/null
+++ b/doc/gettext/ru/list.xml.po
@@ -0,0 +1,66 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(version):9
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(title):11
+msgid "Gentoo Documentation Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):19
+msgid "faq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):20
+msgid "install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):21
+msgid "desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):22
+msgid "upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):23
+msgid "gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):24
+msgid "sysadmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):25
+msgid "gentoodev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):26
+msgid "project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):27
+msgid "articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(list):28
+msgid "other"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//list.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/liveusb.xml.po b/doc/gettext/ru/liveusb.xml.po
new file mode 100644
index 0000000..aa266c6
--- /dev/null
+++ b/doc/gettext/ru/liveusb.xml.po
@@ -0,0 +1,409 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):6
+msgid "Gentoo Linux LiveUSB HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(mail:link):9
+msgid "brix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(mail:link):12
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(abstract):15
+msgid ""
+"This HOWTO explains how to create a Gentoo Linux LiveUSB or, in other words, "
+"how to emulate an x86 or AMD64 Gentoo Linux LiveCD using a USB flash drive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(version):24
+msgid "7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(date):25
+msgid "2009-11-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):30
+msgid "The LiveUSB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):33
+msgid ""
+"This HOWTO explains how to create a <e>Gentoo Linux LiveUSB</e> or, in other "
+"words, how to emulate an x86 or AMD64 Gentoo Linux LiveCD using a USB flash "
+"drive. This is particularly useful for installing Gentoo Linux on a modern "
+"laptop with no CD-ROM drive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):40
+msgid ""
+"The <c>sys-boot/unetbootin</c> package provides a much easier alternative to "
+"create a bootable USB stick from any bootable CD image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):45
+msgid ""
+"Although the instructions found in this document aim at emulating a Gentoo "
+"Linux LiveCD using a USB flash drive, they should work for any arbitrary "
+"block device as long as you adjust the device names accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):54
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):57
+msgid "In order to use a Gentoo Linux LiveUSB you need the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(li):62
+msgid "Bootable USB flash drive with at least 1GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(li):63
+msgid "i686 or x86_64 computer with support for booting from USB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):66
+msgid "You will also need access to the following for creating the LiveUSB:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(li):71
+msgid ""
+"A computer running Gentoo Linux (or alternatively another Linux distribution)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):81
+msgid "Preparing the USB flash drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):83
+msgid "Partitioning the drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(warn):86
+msgid ""
+"These instructions will erase all data from the USB flash drive. Make sure "
+"to backup your data first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(impo):91
+msgid ""
+"This HOWTO assumes that the <path>/dev/sdc</path> device node corresponds to "
+"your USB flash drive. If you have other SCSI-like devices make sure to use "
+"the correct device node."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):97
+msgid ""
+"Create a FAT16 partition on your USB flash drive and mark it bootable using "
+"<c>fdisk</c>. An example partitioning scheme can be seen below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):102
+msgid "If your key is 4GB or larger, use partition type <c>b</c> (W95 FAT32)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):106
+msgid "Example partitioning scheme"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):106
+#, no-wrap
+msgid ""
+"\n"
+"# <i>fdisk -l /dev/sdc</i>\n"
+"\n"
+"Disk /dev/sdc: 2063 MB, 2063597056 bytes\n"
+"255 heads, 63 sectors/track, 250 cylinders\n"
+"Units = cylinders of 16065 * 512 = 8225280 bytes\n"
+"\n"
+"   Device Boot      Start         End      Blocks   Id  System\n"
+"/dev/sdc1   *           1         250     2008124+   6  FAT16\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):120
+msgid "Creating the filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):123
+msgid "Create a FAT16 filesystem on the USB flash drive using <c>mkdosfs</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):127
+msgid ""
+"If your key is 4GB or larger, use <c>-F 32</c> to create a FAT32 filesystem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):131
+msgid "Running mkdosfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):131
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Make sure you have sys-fs/dosfstools installed)</comment>\n"
+"# <i>emerge -av sys-fs/dosfstools</i>\n"
+"# <i>mkdosfs -F 16 /dev/sdc1</i>\n"
+"mkdosfs 2.11 (12 Mar 2005)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):141
+msgid "Installing a Master Boot Record"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):144
+msgid ""
+"Install the precompiled Master Boot Record (MBR) from <c>syslinux</c> on the "
+"USB flash drive:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):149
+msgid "Installing a master boot record"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):149
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Make sure you have sys-boot/syslinux-3.00 or later installed)</comment>\n"
+"# <i>emerge -av '&gt;sys-boot/syslinux-3'</i>\n"
+"# <i>dd if=/usr/share/syslinux/mbr.bin of=/dev/sdc</i>\n"
+"0+1 records in\n"
+"0+1 records out\n"
+"304 bytes (304 B) copied, 0.0162317 s, 18.7 kB/s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):163
+msgid "Copying the files to your key"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):165
+msgid "Mounting the Gentoo Linux Installation CD"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):168
+msgid ""
+"Download the Gentoo Weekly Minimal Install CD for your architecture from "
+"your local Gentoo Linux <uri link=\"/main/en/where.xml\">mirror</uri> site "
+"and mount the ISO image on <path>/mnt/cdrom</path> as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):174
+msgid "Mounting the Gentoo Linux Installation CD ISO image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):174
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Create the /mnt/cdrom mount point if needed)</comment>\n"
+"# <i>mkdir -p /mnt/cdrom</i>\n"
+"# <i>mount -o loop,ro -t iso9660 /path/to/iso.iso /mnt/cdrom</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):180
+msgid ""
+"If you receive a <e>Could not find any loop device</e> error message when "
+"mounting the iso, you need to enable the <c>Loopback device support</c> "
+"option in your kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):189
+msgid "Mounting the LiveUSB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):192
+msgid ""
+"Mount the newly formatted USB flash drive on <path>/mnt/usb</path> as shown "
+"below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):197
+msgid "Mounting the USB flash drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):197
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Create the /mnt/usb mount point if needed)</comment>\n"
+"# <i>mkdir -p /mnt/usb</i>\n"
+"# <i>mount -t vfat /dev/sdc1 /mnt/usb</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):206
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):215
+msgid "Copying the files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):209
+msgid ""
+"Copy the files from the Gentoo Linux Installation CD to the LiveUSB. The "
+"files need to be reordered a bit as we will be using the <c>syslinux</c> "
+"bootloader instead of <c>isolinux</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):215
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp -r /mnt/cdrom/* /mnt/usb</i>\n"
+"# <i>mv /mnt/usb/isolinux/* /mnt/usb</i>\n"
+"# <i>mv /mnt/usb/isolinux.cfg /mnt/usb/syslinux.cfg</i>\n"
+"# <i>rm -rf /mnt/usb/isolinux*</i>\n"
+"\n"
+"<comment>(The memtest86 kernel needs to be renamed for loading it via syslinux)</comment>\n"
+"# <i>mv /mnt/usb/memtest86 /mnt/usb/memtest</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):225
+msgid "You can now unmount the ISO image:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):229
+msgid "Unmounting the ISO image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):229
+#, no-wrap
+msgid ""
+"\n"
+"# <i>umount /mnt/cdrom</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):236
+msgid "Adjusting the bootloader configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):239
+msgid ""
+"Adjust the syslinux configuration file using <c>sed</c> as shown below. The "
+"<c>slowusb</c> parameter will introduce some extra delays before attempting "
+"to mount the filesystem. This is needed to allow the USB flash drive to "
+"settle upon detection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):246
+msgid "Adjusting the boot parameters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):246
+#, no-wrap
+msgid ""
+"\n"
+"# <i>sed -i \\\n"
+"    -e \"s:cdroot:cdroot slowusb:\" \\\n"
+"    -e \"s:kernel memtest86:kernel memtest:\" \\\n"
+"    /mnt/usb/syslinux.cfg</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):258
+msgid "Installing a bootloader"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):260
+msgid "Unmounting the drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):263
+msgid ""
+"Make sure you unmount the USB flash drive before installing the bootloader:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):267
+msgid "Unmounting the USB flash drive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):267
+#, no-wrap
+msgid ""
+"\n"
+"# <i>umount /mnt/usb</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):274
+msgid "Installing syslinux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):277
+msgid "Finally install the <c>syslinux</c> bootloader on the USB flash drive:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre:caption):281
+msgid "Running syslinux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(pre):281
+#, no-wrap
+msgid ""
+"\n"
+"# <i>syslinux /dev/sdc1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(impo):285
+msgid ""
+"You will need to rerun <c>syslinux /dev/sdc1</c> each time you modify the "
+"<path>syslinux.cfg</path> file for the configuration changes to take affect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(note):289
+msgid ""
+"If this is the first time you have used syslinux, you will need to edit "
+"<path>/etc/mtools/mtools.conf</path> on your host. Simply commenting out "
+"<c>SAMPLE FILE</c> will suffice for the purpose of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):299
+msgid "Using the LiveUSB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(title):301
+msgid "Booting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):304
+msgid ""
+"Insert the USB flash drive and turn on the computer, making sure the BIOS is "
+"set to boot from USB. If all goes well you should be presented with a "
+"standard syslinux prompt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(p):310
+msgid ""
+"You should be able to follow the generic installation instructions found in "
+"the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri> from here on."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//liveusb.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/logcheck.xml.po b/doc/gettext/ru/logcheck.xml.po
new file mode 100644
index 0000000..92b5259
--- /dev/null
+++ b/doc/gettext/ru/logcheck.xml.po
@@ -0,0 +1,310 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):6
+msgid "Logcheck Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(mail:link):9
+msgid "phajdan.jr"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(abstract):15
+msgid "This guide shows you how to analyze system logs with logcheck."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(version):23
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(date):24
+msgid "2010-10-12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):27
+msgid "Getting Started With logcheck"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):29
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):32
+msgid ""
+"<c>logcheck</c> is an updated version of <c>logsentry</c> (from the "
+"<c>sentrytools</c> package), which is a tool to analyze the system logs. "
+"Additionally, <c>logcheck</c> comes with a built-in database of common, not-"
+"interesting log messages to filter out the noise. The general idea of the "
+"tool is that all messages are interesting, except the ones explicitly marked "
+"as noise. <c>logcheck</c> periodically sends you an e-mail with a summary of "
+"interesting messages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):45
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):65
+msgid "Installing logcheck"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(impo):48
+msgid ""
+"It is strongly recommended to remove logsentry if you have it installed on "
+"your system. Additionally, you should remove /etc/logcheck to avoid "
+"permission and file collision problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):54
+msgid "Removing logsentry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):54
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Uninstall the logsentry package)</comment>\n"
+"# <i>emerge -C logsentry</i>\n"
+"<comment>(Remove leftover files)</comment>\n"
+"# <i>rm -rf /etc/logcheck</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):61
+msgid "Now you can proceed with the installation of logcheck."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):65
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av app-admin/logcheck</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):72
+msgid "Basic configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):75
+msgid ""
+"<c>logcheck</c> creates a separate user \"logcheck\" to avoid running as "
+"root. Actually, it will refuse to run as root. To allow it to analyze the "
+"logs, you need to make sure they are readable by logcheck. Here is an "
+"example for <c>syslog-ng</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):82
+msgid "/etc/syslog-ng/syslog-ng.conf snippet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):82
+#, no-wrap
+msgid ""
+"\n"
+"options {\n"
+"        owner(root);\n"
+"\n"
+"        <comment>(Make log files group-readable by logcheck)</comment>\n"
+"        group(logcheck);\n"
+"        perm(0640);\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):92
+msgid ""
+"Now reload the configuration and make sure the changes work as expected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):96
+msgid "Reload syslog-ng configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):96
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/syslog-ng reload</i>\n"
+"<comment>(Make sure /var/log/messages has correct permissions)</comment>\n"
+"# <i>ls -l /var/log/messages</i>\n"
+"-rw-r----- 1 root logcheck 1694438 Feb 12 12:18 /var/log/messages\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):103
+msgid ""
+"You should now adjust some basic <c>logcheck</c> settings in <path>/etc/"
+"logcheck/logcheck.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):108
+msgid "Basic /etc/logcheck/logcheck.conf setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):108
+#, no-wrap
+msgid ""
+"\n"
+"# Controls the level of filtering:\n"
+"# Can be Set to \"workstation\", \"server\" or \"paranoid\" for different\n"
+"# levels of filtering. Defaults to server if not set.\n"
+"<comment>(The workstation level includes server, and server includes paranoid.\n"
+"The paranoid level filters almost no messages)</comment>\n"
+"REPORTLEVEL=\"server\"\n"
+"\n"
+"# Controls the address mail goes to:\n"
+"# *NOTE* the script does not set a default value for this variable!\n"
+"# Should be set to an offsite \"emailaddress@some.domain.tld\"\n"
+"<comment>(Make sure you can receive the logcheck e-mails. Testing is strongly\n"
+"recommended)</comment>\n"
+"SENDMAILTO=\"root\"\n"
+"\n"
+"# Controls if syslog-summary is run over each section.\n"
+"# Alternatively, set to \"1\" to enable extra summary.\n"
+"# HINT: syslog-summary needs to be installed.\n"
+"<comment>(If you get a lot of similar messages in the logs, you\n"
+"may want to install app-admin/syslog-summary and enable\n"
+"this setting)</comment>\n"
+"SYSLOGSUMMARY=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):132
+msgid ""
+"You also have to tell <c>logcheck</c> which log files to scan (<path>/etc/"
+"logcheck/logcheck.logfiles</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):137
+msgid "Basic /etc/logcheck/logcheck.logfiles setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):137
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(This is an example for syslog-ng)</comment>\n"
+"/var/log/messages\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):142
+msgid "Finally, enable the logcheck cron job."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):146
+msgid "Enable logcheck cron job"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):146
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Edit the cron file and follow the instructions inside)</comment>\n"
+"# <i>nano -w /etc/cron.hourly/logcheck.cron</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(note):151
+msgid ""
+"For more information about cron read the <uri link=\"/doc/en/cron-guide.xml"
+"\">Cron Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):156
+msgid ""
+"Congratulations! Now you will be regularly getting important log messages by "
+"email. An example message looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):161
+msgid "Example logcheck message"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):161
+#, no-wrap
+msgid ""
+"\n"
+"System Events\n"
+"=-=-=-=-=-=-=\n"
+"Feb 10 17:13:53 localhost kernel: [30233.238342] conftest[25838]: segfault at 40 ip 40061403 sp bfc443c4 error 4\n"
+"in libc-2.10.1.so[4003e000+142000]\n"
+"Feb 11 12:31:21 localhost postfix/pickup[18704]: fatal: could not find any active network interfaces\n"
+"Feb 11 12:31:22 localhost postfix/master[3776]: warning: process //usr/lib/postfix/pickup pid 18704 exit status 1\n"
+"Feb 11 12:31:22 localhost postfix/master[3776]: warning: //usr/lib/postfix/pickup: bad command startup -- throttling\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):176
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(title):178
+msgid "General tips"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(p):181
+msgid ""
+"You can use the logcheck's <c>-d</c> switch to display more debugging "
+"information. Example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre:caption):186
+msgid "Debugging logcheck"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(pre):186
+#, no-wrap
+msgid ""
+"\n"
+"# <i>su -s /bin/bash -c '/usr/sbin/logcheck -d' logcheck</i>\n"
+"D: [1281318818] Turning debug mode on\n"
+"D: [1281318818] Sourcing - /etc/logcheck/logcheck.conf\n"
+"D: [1281318818] Finished getopts c:dhH:l:L:m:opr:RsS:tTuvw\n"
+"D: [1281318818] Trying to get lockfile: /var/lock/logcheck/logcheck.lock\n"
+"D: [1281318818] Running lockfile-touch /var/lock/logcheck/logcheck.lock\n"
+"D: [1281318818] cleanrules: /etc/logcheck/cracking.d/kernel\n"
+"...\n"
+"D: [1281318818] cleanrules: /etc/logcheck/violations.d/su\n"
+"D: [1281318818] cleanrules: /etc/logcheck/violations.d/sudo\n"
+"...\n"
+"D: [1281318825] logoutput called with file: /var/log/messages\n"
+"D: [1281318825] Running /usr/sbin/logtail2 on /var/log/messages\n"
+"D: [1281318825] Sorting logs\n"
+"D: [1281318825] Setting the Intro\n"
+"D: [1281318825] Checking for security alerts\n"
+"D: [1281318825] greplogoutput: kernel\n"
+"...\n"
+"D: [1281318825] greplogoutput: returning 1\n"
+"D: [1281318825] Checking for security events\n"
+"...\n"
+"D: [1281318825] greplogoutput: su\n"
+"D: [1281318825] greplogoutput: Entries in checked\n"
+"D: [1281318825] cleanchecked - file: /tmp/logcheck.uIFLqU/violations-ignore/logcheck-su\n"
+"D: [1281318825] report: cat'ing - Security Events for su\n"
+"...\n"
+"D: [1281318835] report: cat'ing - System Events\n"
+"D: [1281318835] Setting the footer text\n"
+"D: [1281318835] Sending report: 'localhost 2010-08-09 03:53 Security Events' to root\n"
+"D: [1281318835] cleanup: Killing lockfile-touch - 17979\n"
+"D: [1281318835] cleanup: Removing lockfile: /var/lock/logcheck/logcheck.lock\n"
+"D: [1281318835] cleanup: Removing - /tmp/logcheck.uIFLqU\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//logcheck.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/ltsp.xml.po b/doc/gettext/ru/ltsp.xml.po
new file mode 100644
index 0000000..92afac0
--- /dev/null
+++ b/doc/gettext/ru/ltsp.xml.po
@@ -0,0 +1,713 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(guide:link):5
+msgid "/doc/en/ltsp.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):6
+msgid "Gentoo - LTSP Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(author:title):7
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail:link):8
+msgid "lanius@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail):8
+msgid "Heinrich Wendel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail:link):11
+msgid "josiah@ritchietribe.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail):11
+msgid "Josiah Ritchie"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(author:title):13
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail:link):14
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(mail):14
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(abstract):17
+msgid "This guide shows you how to setup a LTSP Server with Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(version):23
+msgid "1.14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(date):24
+msgid "2008-09-28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):27
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):29
+msgid "What is LTSP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):32
+msgid ""
+"LTSP is an abbreviation for \"Linux Terminal Server Project\". Installed on "
+"a server it can supply many workstations (so called thin-clients) with "
+"identical environments. All applications run on the server and therefore you "
+"can use old PCs and convert them into XTerminals. This reduces costs and "
+"maintenance especially in an environment where you need to have an uniform "
+"workspace on each computer you login, e.g. in schools or firms."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):47
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):61
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):49
+msgid "Preliminaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):52
+msgid ""
+"All of the examples in this document presume that your server's IP is "
+"192.168.0.254, your domain is named yourdomain.com and your network is "
+"192.168.0.0/24."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):64
+msgid ""
+"First of all, you must have a working Gentoo system. Please read the Gentoo "
+"Installation Manual for your architecture on <uri link=\"http://www.gentoo."
+"org/doc\">Gentoo's Documentation Website</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):70
+msgid "Then lets begin with the easiest step, installing the ltsp package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):74
+msgid "Emerge LTSP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):74
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge ltsp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):78
+msgid "This will install the following packages as dependencies:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):83
+msgid "<b>XFree</b>: They are called XTerminals, guess why :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):84
+msgid ""
+"<b>DHCP</b>: DHCP is a protocol for automating the configuration of "
+"computers that use TCP/IP, used by ltsp to distribute IPs to the "
+"workstations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):89
+msgid ""
+"<b>NFS</b>: NFS is a protocol to allow access to harddisks through the "
+"network, used by ltsp to mount a base system for the workstations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):94
+msgid ""
+"<b>TFTP</b>: TFTP is a simple file transfer protocol, used by ltsp to "
+"transfer the kernel to the workstations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):98
+msgid ""
+"<b>XINETD</b>: Xinetd is a powerful replacement for inetd, with advanced "
+"features, used by ltsp to start tftp."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(note):104
+msgid ""
+"If you have the kde/gnome useflag set, it will also install a complete kde/"
+"gnome system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):114
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):118
+msgid "After the emerge process has finished all services must be configured:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):125
+msgid "System Logger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):128
+msgid ""
+"To analyze problems easier, the system logger must be configured to accept "
+"remote connections. Please read the documentation of your system logger on "
+"how to achieve this. If, for example, you are using sysklogd, all you need "
+"to do is edit <path>/etc/conf.d/sysklogd</path> and add \"-r\" to the "
+"SYSLOGD line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):136
+msgid "/etc/conf.d/sysklogd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):136
+#, no-wrap
+msgid ""
+"\n"
+"SYSLOGD=\"-m 0 -r\"\n"
+"KLOGD=\"-c 3 -2\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):144
+msgid "NFS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):147
+msgid ""
+"Next step is to edit your <path>/etc/exports</path> file, in order to allow "
+"the workstations to mount the root filesystem. There should be at least two "
+"lines in it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):153
+msgid "/etc/exports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):153
+#, no-wrap
+msgid ""
+"\n"
+"/opt/ltsp-4.1/i386         192.168.0.0/255.255.255.0(ro,no_root_squash,async)\n"
+"/var/opt/ltsp/swapfiles    192.168.0.0/255.255.255.0(rw,no_root_squash,async)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(note):158
+msgid ""
+"You have to alter the network/netmask to match your network/netmask settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):163
+msgid "Now start NFS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):167
+msgid "Starting nfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):167
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add nfs default</i>\n"
+"# <i>/etc/init.d/nfs start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):175
+msgid "xinetd/tftp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):177
+msgid ""
+"TFTP requires a bit of configuring to get it to work properly. First, edit "
+"<path>/etc/conf.d/in.tftpd</path> to set tftpd's options and path correctly:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):182
+msgid "/etc/conf.d/in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):182
+#, no-wrap
+msgid ""
+"\n"
+"INTFTPD_PATH=\"/tftpboot\"\n"
+"INTFTPD_OPTS=\"-s ${INTFTPD_PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):187
+msgid ""
+"The -s flag specifies that TFTP is to run in secure chrooted mode "
+"(recommended). This means that you don't need to include the <path>/"
+"tftpboot</path> path for example in the DHCP configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):193
+msgid ""
+"Next, configure xinetd to run TFTP and allow remote connections. By default "
+"TFTP won't be started by xinetd, so edit <path>/etc/xinetd.d/tftp</path> and "
+"replace <c>disable=yes</c> with <c>disable=no</c>. If the file is missing "
+"just go ahead and create <path>/etc/xinetd.d/tftp</path> with the contents "
+"below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):200
+msgid "/etc/xinetd.d/tftp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):200
+#, no-wrap
+msgid ""
+"\n"
+"service tftp\n"
+"{\n"
+"        disable = no\n"
+"        socket_type = dgram\n"
+"        protocol = udp\n"
+"        wait = yes\n"
+"        user = root\n"
+"        server = /usr/sbin/in.tftpd\n"
+"        server_args = -s /tftpboot\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):213
+msgid ""
+"Now edit <path>/etc/xinetd.conf</path> and comment out the line <c>only_from "
+"= localhost</c> by prefacing it with a <c>#</c>. Finally, start xinetd."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):218
+msgid "Starting xinetd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):218
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add xinetd default</i>\n"
+"# <i>/etc/init.d/xinetd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):226
+msgid "Name resolving"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):229
+msgid ""
+"In order for the workstation to reach all resources, a correct name "
+"resolving must be available. There are several ways to achieve this. One is "
+"to configure a DNS server for the local network, the other (and more simple) "
+"is to have almost identical <path>/etc/hosts</path> files on all systems. We "
+"are going to use the latter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):237
+msgid ""
+"All workstations must be listed in <path>/etc/hosts</path>. Take a look at "
+"the example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):242
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):242
+#, no-wrap
+msgid ""
+"\n"
+"127.0.0.1        localhost\n"
+"192.168.0.254    server      server.yourdomain.com\n"
+"192.168.0.1      ws001       ws001.yourdomain.com\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):251
+msgid "DHCP Config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):254
+msgid ""
+"This is the most complicated step in my opinion, you have to create a valid "
+"DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):260
+msgid "dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):260
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Some general options)</comment>\n"
+"default-lease-time            21600;\n"
+"max-lease-time                21600;\n"
+"use-host-decl-names           on;\n"
+"ddns-update-style             ad-hoc;\n"
+"\n"
+"<comment>(Bootp options)</comment>\n"
+"allow booting;\n"
+"allow bootp;\n"
+"\n"
+"<comment>(Network Options)</comment>\n"
+"option subnet-mask            255.255.255.0;\n"
+"option broadcast-address      192.168.0.255;\n"
+"option routers                192.168.0.254;\n"
+"option domain-name-servers    192.168.0.254;\n"
+"option log-servers            192.168.0.254;\n"
+"option domain-name            \"yourdomain.com\";\n"
+"\n"
+"<comment>(LTSP Path Options)</comment>\n"
+"option root-path              \"192.168.0.254:/opt/ltsp-4.1/i386\";\n"
+"filename                      \"/lts/vmlinuz-2.4.26-ltsp-2\";\n"
+"<comment>(Address of the tftp server to download the ltsp file from)</comment>\n"
+"next-server                   192.168.0.254;\n"
+"\n"
+"<comment>(If your workstations have ISA NICs uncomment the following)</comment>\n"
+"<comment>(lines and alter the driver and IO)</comment>\n"
+"#option option-128 code 128 = string;\n"
+"#option option-129 code 129 = text;\n"
+"#option option-128 e4:45:74:68:00:00;\n"
+"#option option-129 \"NIC=ne IO=0x300\";\n"
+"\n"
+"shared-network WORKSTATIONS {\n"
+"  subnet 192.168.0.0 netmask 255.255.255.0 {\n"
+"    <comment>(Distribute dynamic IPs to the workstations)</comment>\n"
+"    range dynamic-bootp 192.168.0.1 192.168.0.16;\n"
+"    <comment>(Workstation specific configuration for PXE booting)</comment>\n"
+"    #host ws001 {\n"
+"    #  hardware ethernet     00:E0:06:E8:00:84;\n"
+"    #  fixed-address         192.168.0.1;\n"
+"    #}\n"
+"  }\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):305
+msgid ""
+"If your workstations support PXE, you should list each one of them as we "
+"have done with <e>host ws001</e> (don't forget to uncomment it). Don't give "
+"them an adress in the dynamic range, otherwise it would be possible that "
+"more workstations have the same IP (which is troublesome). Remember, if you "
+"cut-n-paste the above example, replace any \"//\" comments with \"##\", or "
+"else dhcp will fail to start."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):314
+msgid ""
+"For more documentation on this item read the official dhcp handbook: "
+"<uri>http://www.dhcp-handbook.com/</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):319
+msgid "Now start DHCP as you did with NFS and xinetd:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):323
+msgid "start dhcp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):323
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add dhcp default</i>\n"
+"# <i>/etc/init.d/dhcp start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(note):328
+msgid ""
+"DHCPD needs CONFIG_PACKET and CONFIG_FILTER activated in the kernel to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):335
+msgid "LTSP Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):338
+msgid ""
+"There are many options to configure your workstations, visit <uri>http://"
+"ltsp.mirrors.tds.net/pub/ltsp/docs/ltsp-4.1-en.html#AEN1190</uri> for a full "
+"description of <path>/opt/ltsp/i386/etc/lts.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):344
+msgid ""
+"As a few suggestions to get started, you will want to first copy <path>/opt/"
+"ltsp/i386/etc/lts.conf.example</path> to <path>/opt/ltsp/i386/etc/lts.conf</"
+"path> and edit it from there. You may want to try changing the <c>SCREEN_01</"
+"c> option to read <c>SCREEN_01 = startx</c>. To use a USB mouse on the "
+"remote client, add the following MODULE lines, and change the X_MOUSE_* "
+"lines as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):353
+msgid "/opt/ltsp/i386/etc/lts.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):353
+#, no-wrap
+msgid ""
+"\n"
+"MODULE_01          = usb-uhci\n"
+"MODULE_02          = mousedev\n"
+"MODULE_03          = usbmouse\n"
+"X_MOUSE_PROTOCOL   = \"IMPS/2\"\n"
+"X_MOUSE_DEVICE     = \"/dev/input/mice\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):364
+msgid "Displaymanager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):367
+msgid ""
+"Now you have to change your displaymanager's configuration to also accept "
+"remote connections."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):372
+msgid ""
+"First change your <path>/etc/X11/xdm/Xaccess</path> file, uncomment the "
+"following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):377
+msgid "/etc/X11/xdm/Xaccess"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):377
+#, no-wrap
+msgid ""
+"\n"
+"#*                   #any host can get a login window\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):381
+msgid "Now change the configuration of the displaymanager you use:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):385
+msgid ""
+"<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out "
+"<c>DisplayManager.requestPort: 0</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):390
+msgid ""
+"<b>KDM</b>: In <path>/usr/kde/3.1/share/config/kdm/kdmrc</path> look for the "
+"<c>[Xdmcp]</c> section and change <c>Enable = false</c> to <c>Enable = true</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):396
+msgid ""
+"<b>GDM</b>: In <path>/etc/X11/gdm/gdm.conf</path> look for the <c>[xdmcp]</"
+"c> section and change <c>Enable = false</c> to <c>Enable = True</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):402
+msgid "Then start the displaymanager:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):406
+msgid "Starting xdm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):406
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add xdm default</i>\n"
+"# <i>/etc/init.d/xdm start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(warn):411
+msgid ""
+"There seem to be problems currently with XDM and GDM. The author used KDM to "
+"resolve these issues."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):416
+msgid ""
+"Remember, if your display manager is already running, restarting the X "
+"server via CTRL-ALT-BACKSPACE doesn't restart the display manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):424
+msgid "Creating a bootfloppy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):427
+msgid ""
+"If your workstations don't support PXE booting, you can create a boot-floppy "
+"which is used to start your workstations and connect to the terminal server. "
+"Go to <uri>http://www.rom-o-matic.net</uri>, select the latest version, "
+"select your NIC, press <e>Get ROM</e> and write the image to a floppy:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre:caption):434
+msgid "Write floppy image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(pre):434
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cat nicfile.zdsk &gt; /dev/fd0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):443
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):447
+msgid ""
+"There are a lot of things that can be the source of trouble, but there are "
+"also several resources around which help you solve your problems:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):453
+msgid ""
+"The official documentation: <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/"
+"Documentation</uri>, especially the <uri link=\"http://wiki.ltsp.org/twiki/"
+"bin/view/Ltsp/TroubleShooting\"> Troubleshooting section</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):460
+msgid ""
+"The gentoo IRC channel: <uri link=\"irc://irc.gentoo.org/gentoo\">#gentoo</"
+"uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):464
+msgid "The ltsp irc channel: irc.freenode.org #ltsp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(li):465
+msgid ""
+"The ltsp mailinglists <uri>http://marc.info/?l=ltsp-discuss</uri> are full "
+"of some real good knowledge."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):476
+msgid "FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):480
+msgid ""
+"<b>Q:</b> My workstations have Pentium II CPUs, but my server is compiled "
+"with <c>march=athlon-xp</c>, does this work?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):485
+msgid ""
+"<b>A:</b> This is no problem, because all applications run on the server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):489
+msgid "<b>Q:</b> Which CPU and how much RAM should the server have?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):493
+msgid ""
+"<b>A:</b> There is a good document with suggestions at <uri>http://wiki.ltsp."
+"org/twiki/bin/view/Ltsp/ServerSizing</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):498
+msgid "<b>Q:</b> Do you have more information about this PXE stuff?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):502
+msgid ""
+"<b>A:</b> Yes, take a look at <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/"
+"PXE</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):507
+msgid ""
+"<b>Q:</b> Is it possibly to use 3D-Accelerated software on the workstations?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):511
+msgid ""
+"<b>A:</b> If you are using NVidia cards take a look at <uri>http://wiki.ltsp."
+"org/twiki/bin/view/Ltsp/NvidiaLtsp411</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):516
+msgid "<b>Q:</b> In some applications the fonts look crappy, what to do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):520
+msgid ""
+"<b>A:</b> You have to setup the XFontServer, add <c>USE_XFS=Y</c> to your "
+"<path>lts.conf</path>, edit <path>/etc/X11/fs/config</path> and comment "
+"<c>no-listen: tcp</c> out, replace <c>XFS_PORT=\"-1\"</c> with <c>XFS_PORT="
+"\"7100\"</c> in <path>/etc/conf.d/xfs</path> and start xfs: <c>/etc/init.d/"
+"xfs start</c>. Also doublecheck that <path>/etc/X11/XF86Config</path> (or "
+"<path>/etc/X11/xorg.conf</path>) contains <c>FontPath \"unix/:7100\"</c> in "
+"the Files-section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):530
+msgid "<b>Q: </b> How can I use the soundcard of my workstation?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):534
+msgid ""
+"<b>A: </b> There is a ltsp-sound package in gentoo, for more instructions "
+"read the included <path>README</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(title):544
+msgid "Glossary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):548
+msgid ""
+"<b><uri link=\"http://www.ltsp.org\">LTSP</uri></b> \"The LTSP provides a "
+"simple way to utilize low cost workstations as either graphical or character "
+"based terminals on a GNU/Linux server.\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(p):554
+msgid ""
+"<b><uri link=\"http://www.webopedia.com/TERM/P/PXE.html\">PXE</uri></b> "
+"\"Short for Pre-Boot Execution Environment. Pronounced pixie, PXE is one of "
+"the components of Intel's WfM specification. It allows a workstation to boot "
+"from a server on a network prior to booting the operating system on the "
+"local hard drive. A PXE-enabled workstation connects its NIC to the LAN via "
+"a jumper, which keeps the workstation connected to the network even when the "
+"power is off.\""
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//ltsp.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/lvm2.xml.po b/doc/gettext/ru/lvm2.xml.po
new file mode 100644
index 0000000..454a685
--- /dev/null
+++ b/doc/gettext/ru/lvm2.xml.po
@@ -0,0 +1,699 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(guide:link):5
+msgid "/doc/en/lvm2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):6
+msgid "Gentoo LVM2 installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail:link):9
+msgid "avi@CFFtechnologies.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail):9
+msgid "Avi Schwartz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(author:title):11
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail:link):12
+msgid "rajiv@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail):12
+msgid "Rajiv Manglani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail:link):15
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(mail):15
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(abstract):18
+msgid ""
+"This guide describes how to setup your Gentoo machine using the Logical "
+"Volume Manager version 2 (LVM2)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(version):27
+msgid "2.7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(date):28
+msgid "2009-02-10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):35
+msgid ""
+"This guide is based on an example with two IDE hard disks. It means that you "
+"will more than likely need to change the drive, partition names and "
+"partition sizes to match your own setup and needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(warn):41
+msgid ""
+"This document is not intended to be an LVM2 tutorial. It serves as a "
+"supplement to the Gentoo installation procedure as described in the <uri "
+"link=\"/doc/en/handbook/handbook-x86.xml?part=1\">Handbook, Part 1</uri>. "
+"Make sure you <e>read</e> the Gentoo Installation Manual <e>before</e> you "
+"start your installation process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):49
+msgid ""
+"For a complete LVM HOWTO point your browser to <uri>http://tldp.org/HOWTO/"
+"LVM-HOWTO</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):57
+msgid "Initial requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):60
+msgid ""
+"If you do a fresh install of Gentoo, you will need to use a bootable CD with "
+"LVM2 support such as a Gentoo Installation CD. You can find the Installation "
+"CDs for an x86 architecture on our <uri link=\"/main/en/mirrors.xml"
+"\">mirrors</uri> under <path>/releases/x86/current/installcd</path>. Other "
+"architectures might be supported as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):68
+msgid ""
+"If you install LVM2 on a currently running system with some spare hard disk "
+"space, you will need to enable the LVM2 module (<path>dm-mod</path>). This "
+"module is available in <path>gentoo-sources</path>. Compiling your kernel "
+"and getting LVM2 to work is covered later in this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):75
+msgid "Not all 2.4 kernels provided by Gentoo support LVM2!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):82
+msgid "Partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):85
+msgid ""
+"Our example system has two IDE hard disks and will be partitioned as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):90
+msgid "/dev/hda1 -- /boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):91
+msgid "/dev/hda2 -- (swap)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):92
+msgid "/dev/hda3 -- /"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):93
+msgid "/dev/hda4 -- Will be used by LVM2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):94
+msgid "/dev/hdb1 -- Will be used by LVM2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(impo):97
+msgid ""
+"Pay attention to the partition names as it is easy to confuse the a's and "
+"b's, and the partition numbers. One false move could wipe out the wrong "
+"partition. You have been warned!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):103
+msgid "OK, time to start..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):112
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):116
+msgid ""
+"Follow the handbook, but with the following amendments to chapter <e>4. "
+"Preparing the Disks</e>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):121
+msgid ""
+"Use <c>fdisk</c> as described in the handbook, but use the partition scheme "
+"mentioned above as an example. It is only <e>an example</e>, adapt it to "
+"your own needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):127
+msgid ""
+"Create a small physical <path>/boot</path> partition (hda1). In this "
+"example, <path>/boot</path> will be not managed by LVM2. This partition will "
+"contain your bootloader and your kernel(s). A 64MB partition should be well "
+"enough for quite a few kernel generations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):134
+msgid "Create a swap partition (hda2)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):138
+msgid ""
+"Create a / (root) partition (hda3). If you are interested in trying to put "
+"your root partition under LVM management (which we do not recommend), see "
+"the resources section at the end of this guide for a link to a mini-howto on "
+"how to do this. The size of the root partition need not be large if you will "
+"keep <path>/opt /usr /home /var</path> and <path>/tmp</path> in an LVM2 "
+"Volume Group (vg). In this case, 1GB should be sufficient."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):147
+msgid ""
+"It is <b>not</b> recommended to put the following directories in an LVM2 "
+"partition: <path>/etc</path>, <path>/lib</path>, <path>/mnt</path>, <path>/"
+"proc</path>, <path>/sbin</path>, <path>/dev</path>, and <path>/root</path>. "
+"This way, you would still be able to log into your system (crippled, but "
+"still somewhat usable, as root) if something goes terribly wrong."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):155
+msgid ""
+"Assuming the <path>/boot</path>, swap and root partitions do not use the "
+"whole physical disk, create a fourth partition on this disk and set it to "
+"type 8e (Linux LVM). If you have more physical drives you would like to use "
+"with LVM, create one partition on each and give them the same type (8e)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):162
+msgid ""
+"Considering the huge size of current disks, you might consider splitting "
+"your hard disks into smaller partitions instead of creating a big partition "
+"that will be added to an LVM2 volume group in one block. LVM2 makes it easy "
+"to extend your volumes after all. This leaves you some unallocated "
+"partitions you might need to use outside of an LVM2 group. In short, don't "
+"use your disk space until you know you need it. As an example, one "
+"contributor had split his 160&nbsp;Gb hard disk into 8 partitions of 20&nbsp;"
+"Gb each."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):172
+msgid ""
+"Create the filesystems on <path>/dev/hda1</path> and <path>/dev/hda3</path>, "
+"and create and activate the swap on <path>/dev/hda2</path> as described in "
+"the handbook."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):178
+msgid "Load the LVM2 <path>dm-mod</path> module."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):182
+msgid "Loading the LVM2 module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):182
+#, no-wrap
+msgid ""
+"\n"
+"# <i>modprobe dm-mod</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):186
+msgid ""
+"Before scanning and activating LVM, you might want to edit <path>/etc/lvm/"
+"lvm.conf</path> to exclude some devices. By default, LVM2 will scan all "
+"devices, even your CDROM which can generate error messages. In the following "
+"example, the line that allows scanning of all devices is replaced by one "
+"that rejects every device but our two IDE disks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):194
+msgid "Activating LVM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):194
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Avoid scanning all devices but our disks)</comment>\n"
+"# <i>nano -w /etc/lvm/lvm.conf</i>\n"
+"<comment>(Look for the following line)</comment>\n"
+"    filter = [ \"a/.*/\" ]\n"
+"<comment>(Replace it with the following one to scan\n"
+"/dev/hda and /dev/hdb and reject anything else)</comment>\n"
+"    filter = [ \"a|/dev/hd[ab]|\", \"r/.*/\" ]\n"
+"<comment>(Save the file and quit nano)</comment>\n"
+"# <i>vgscan</i>\n"
+"  Reading all physical volumes.  This may take a while...\n"
+"  No volume groups found\n"
+"<comment>(Make any previously set up volume groups available)</comment>\n"
+"# <i>vgchange -a y</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):210
+msgid "Prepare the partitions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):214
+msgid "Preparing the partitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):214
+#, no-wrap
+msgid ""
+"\n"
+"# <i>pvcreate /dev/hda4 /dev/hdb1</i>\n"
+"  No physical volume label read from /dev/hda4\n"
+"  Physical volume \"/dev/hda4\" successfully created\n"
+"  No physical volume label read from /dev/hdb1\n"
+"  Physical volume \"/dev/hdb1\" successfully created\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):222
+msgid ""
+"Setup a volume group. A volume group is the result of combining several "
+"physical units into a single logical device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):227
+msgid ""
+"In our example, <path>/dev/hda1</path>, <path>/dev/hda2</path> and <path>/"
+"dev/hda3</path> are the <path>/boot</path>, swap and root partitions so we "
+"need to combine <path>/dev/hda4</path> and <path>/dev/hdb1</path>. It can be "
+"done with a single command, but, as an example, we will create our volume "
+"group and extend it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):235
+msgid "Creating and extending a volume group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):235
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Create a volume group named vg)</comment>\n"
+"# <i>vgcreate vg /dev/hda4</i>\n"
+"  /etc/lvm/backup: fsync failed: Invalid argument <comment>(Ignore this warning)</comment>\n"
+"  Volume group \"vg\" successfully created\n"
+"<comment>(Extending an existing volume group)</comment>\n"
+"# <i>vgextend vg /dev/hdb1</i>\n"
+"  /etc/lvm/backup: fsync failed: Invalid argument <comment>(Ignore this warning, again and later as well)</comment>\n"
+"  Volume group \"vg\" successfully extended\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):246
+msgid ""
+"Create the logical volumes. Logical volumes are the equivalent of partitions "
+"you would create using fdisk in a non LVM2 environment. In our example, we "
+"create the following partitions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(th):254
+msgid "Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(th):255
+msgid "Size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):258
+msgid "/usr"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):259
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):271
+msgid "10 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):262
+msgid "/home"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):263
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):267
+msgid "5 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):266
+msgid "/opt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):270
+msgid "/var"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):274
+msgid "/tmp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(ti):275
+msgid "2 GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):279
+msgid ""
+"Since we are going to use LVM2, we should not worry too much about partition "
+"sizes because they can always be expanded as needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):284
+msgid ""
+"As Terje Kvernes commented, it is easier to increase the size of a partition "
+"then to shrink it. You might therefore want to start with smaller partitions "
+"and increase their size as needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):290
+msgid "Creating and extending logical volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):290
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lvcreate -L10G -nusr  vg</i>\n"
+"  Logical volume \"usr\" created <comment>(Further similar messages not displayed)</comment>\n"
+"# <i>lvcreate -L5G  -nhome vg</i>\n"
+"# <i>lvcreate -L5G  -nopt  vg</i>\n"
+"# <i>lvcreate -L10G -nvar  vg</i>\n"
+"# <i>lvcreate -L2G  -ntmp  vg</i>\n"
+"<comment>(As an example, let's extend a logical volume with 5 extra Gbytes)</comment>\n"
+"# <i>lvextend -L+5G /dev/vg/home</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):301
+msgid ""
+"Create filesystems on the logical volumes the same way you would on a "
+"regular partition. We use ext3 on the logical volumes but any filesystem of "
+"your choice will work:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):307
+msgid "Creating the filesystems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):307
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mke2fs -j /dev/vg/usr</i>\n"
+"# <i>mke2fs -j /dev/vg/home</i>\n"
+"# <i>mke2fs -j /dev/vg/opt</i>\n"
+"# <i>mke2fs -j /dev/vg/var</i>\n"
+"# <i>mke2fs -j /dev/vg/tmp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):315
+msgid ""
+"Mount your partitions as described in the handbook and mount your LVM2 "
+"logical volumes as if they were partitions. Replace the usual <path>/dev/"
+"hdxx</path> with <path>/dev/vg/logical_volumename</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):321
+msgid "Mounting your logical volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):321
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Make sure you have mounted your root partition as described in the handbook first)</comment>\n"
+"# <i>mkdir /mnt/gentoo/usr</i>\n"
+"# <i>mount /dev/vg/usr /mnt/gentoo/usr</i>\n"
+"# <i>mkdir /mnt/gentoo/home</i>\n"
+"# <i>mount /dev/vg/home /mnt/gentoo/home</i>\n"
+"# <i>mkdir /mnt/gentoo/opt</i>\n"
+"# <i>mount /dev/vg/opt /mnt/gentoo/opt</i>\n"
+"# <i>mkdir /mnt/gentoo/var</i>\n"
+"# <i>mount /dev/vg/var /mnt/gentoo/var</i>\n"
+"# <i>mkdir /mnt/gentoo/tmp</i>\n"
+"# <i>mount /dev/vg/tmp /mnt/gentoo/tmp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(note):335
+msgid ""
+"The rest of the installation handbook is mostly unchanged so we shall not "
+"walk you through it again except to point out differences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):340
+msgid ""
+"When configuring your kernel, make sure to configure your kernel to support "
+"LVM2 (not all 2.4 kernels do). Select the LVM2 module as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):345
+msgid "Selecting the LVM2 module in a 2.4.x kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):345
+#, no-wrap
+msgid ""
+"\n"
+"Multi-device support (RAID and LVM)  ---&gt;\n"
+"  [*] Multiple devices driver support (RAID and LVM)\n"
+"  &lt; &gt;  RAID support\n"
+"<comment>(Note that LVM is not selected on purpose, this was for LVM1)</comment>\n"
+"  &lt; &gt;  Logical volume manager (LVM) support\n"
+"  &lt;M&gt;  Device-mapper support\n"
+"  &lt; &gt;   Mirror (RAID-1) support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):355
+msgid "Selecting the LVM2 module in a 2.6.x kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):355
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+" Multi-device support (RAID and LVM)  ---&gt;\n"
+"   [*] Multiple devices driver support (RAID and LVM)\n"
+"   &lt; &gt;   RAID support\n"
+"   &lt;M&gt;   Device mapper support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):363
+msgid "The compiled module is called <path>dm-mod.ko</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):367
+msgid ""
+"After you have built your kernel and installed its modules, add the "
+"following line to your <path>/etc/modules.autoload.d/kernel-{KV}</path> "
+"where {KV} represents your kernel version (2.4 or 2.6) so that the LVM2 "
+"module gets loaded when your machine is booted:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):374
+msgid "Adding the LVM2 module into /etc/modules.autoload.d/kernel-2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):374
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>\n"
+"<comment>(Add the following line)</comment>\n"
+"dm-mod\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):380
+msgid "Now, install the lvm2 package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(impo):384
+msgid ""
+"Make sure your <path>/usr/src/linux</path> link points to the kernel sources "
+"you are using because the lvm2 ebuild depends on the device-mapper ebuild "
+"which will check the presence of a required source file under <path>/usr/src/"
+"linux/include/linux</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):391
+msgid "Emerging the LVM2 package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):391
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge lvm2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):395
+msgid ""
+"Edit <path>/etc/lvm/lvm.conf</path> as described <uri link="
+"\"#doc_chap2_pre2\">earlier</uri>. The file you previously edited is part of "
+"your installation environment and will disappear after the next reboot. This "
+"time, you edit the real one inside your new Gentoo install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):402
+msgid ""
+"When editing your <path>/etc/fstab</path> file, follow the handbook and add "
+"your LVM2 logical volumes as needed. Again, here are a few lines needed for "
+"our example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):408
+msgid "Extract of /etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):408
+#, no-wrap
+msgid ""
+"\n"
+"/dev/hda1     /boot   ext3    noauto,noatime 1 2\n"
+"/dev/hda2     none    swap    sw             0 0\n"
+"/dev/hda3     /       ext3    noatime        0 1\n"
+"# Logical volumes\n"
+"/dev/vg/usr   /usr    ext3    noatime        0 2\n"
+"/dev/vg/home  /home   ext3    noatime        0 2\n"
+"/dev/vg/opt   /opt    ext3    noatime        0 2\n"
+"/dev/vg/var   /var    ext3    noatime        0 2\n"
+"/dev/vg/tmp   /tmp    ext3    noatime        0 2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):420
+msgid ""
+"When you reach the end of the installation part of the handbook, don't "
+"forget to umount all your LVM2 logical volumes as well and for a good "
+"measure run the following command before you reboot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):426
+msgid "Shutting down LVM2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):426
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vgchange -a n</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):430
+msgid "Restart your machine and all partitions should be visible and mounted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):439
+msgid "Continuing After a Reboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):443
+msgid ""
+"If you have interrupted the Gentoo installation at one point and want to "
+"continue, you need to create the volume device nodes first:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):448
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre:caption):457
+msgid "Reactivating the volumes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):448
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vgscan --mknodes</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):452
+msgid ""
+"Installation CDs with less recent tools might need to reactivate the volumes "
+"instead:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(pre):457
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Deactivate all volumes first)</comment>\n"
+"# <i>vgchange -a n</i>\n"
+"<comment>(Export all the volumes)</comment>\n"
+"# <i>vgexport -a</i>\n"
+"<comment>(Import all volumes)</comment>\n"
+"# <i>vgimport -a</i>\n"
+"<comment>(Reactivate all volumes)</comment>\n"
+"# <i>vgchange -a y</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):473
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):478
+msgid ""
+"The official <uri link=\"http://sources.redhat.com/lvm2\">LVM2 home page</"
+"uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):481
+msgid "The <uri link=\"http://tldp.org/HOWTO/LVM-HOWTO\">LVM Howto</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):484
+msgid ""
+"Daniel Robbins's articles on LVM for IBM's DeveloperWorks: <uri link=\"/doc/"
+"en/articles/lvm-p1.xml\">Part 1</uri> and <uri link=\"/doc/en/articles/lvm-"
+"p2.xml\">Part 2</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(li):489
+msgid ""
+"How to boot your root FS off of LVM1: <uri>http://www.the-infinite.org/"
+"archive/docs/lvm/howto-boot-off-root-lv.txt</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(title):500
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(p):504
+msgid ""
+"Thanks <mail link=\"bangert@gentoo.org\">Thilo Bangert</mail> and <mail link="
+"\"terjekv@math.uio.no\">Terje Kvernes</mail> for their help and comments on "
+"this document."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//lvm2.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/lxde-howto.xml.po b/doc/gettext/ru/lxde-howto.xml.po
new file mode 100644
index 0000000..df22aed
--- /dev/null
+++ b/doc/gettext/ru/lxde-howto.xml.po
@@ -0,0 +1,349 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):6
+msgid "The LXDE Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(mail:link):9
+msgid "nathanzachary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(mail:link):12
+msgid "yngwin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(abstract):18
+msgid ""
+"This guide introduces the user to LXDE, explains its components, and leads "
+"the user through the installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(version):27
+msgid "1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(date):28
+msgid "2009-11-30"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):33
+msgid "What is LXDE?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):36
+msgid ""
+"After installing your base Gentoo system, and <uri link=\"/doc/en/xorg-"
+"config.xml\">the X Server</uri>, you have to make many choices regarding "
+"your graphical environment, if you want one at all. There are many options "
+"available to you, ranging from minimalistic window managers like <uri link="
+"\"/doc/en/openbox.xml\">Openbox</uri>, to full-featured desktop environments "
+"like <uri link=\"/proj/en/desktop/kde/kde-config.xml\"> KDE</uri>, and <uri "
+"link=\"/doc/en/gnome-config.xml\">GNOME</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):46
+msgid ""
+"You may find yourself saying \"well, I like the idea of having a lightweight "
+"graphical environment, but I don't want to install and configure every "
+"component individually like with Openbox.\" For quite some time, such users "
+"installed <uri link=\"/doc/en/xfce-config.xml\">Xfce</uri>. While it "
+"provides a nice full-featured environment without the extensive resource "
+"usage of KDE or GNOME, it could still become a bit on the heavy side. Now, "
+"you have another choice: the <uri link=\"http://www.lxde.org\">Lightweight "
+"X11 Desktop Environment</uri>, or <uri link=\"http://www.lxde.org\">LXDE</"
+"uri> for short."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):60
+msgid "Components of LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):63
+msgid ""
+"LXDE, being a desktop environment, is comprised of several components. Each "
+"program offers a certain functionality, and together they form the complete "
+"desktop environment. Currently, there are eleven core components, and "
+"several other programs necessary to make a complete LXDE installation. These "
+"programs are the ones pulled in by the <uri link=\"http://packages.gentoo."
+"org/package/lxde-base/lxde-meta\">LXDE meta</uri> package, discussed in the "
+"installation section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):76
+msgid "Core Components"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):80
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxappearance"
+"\">LXappearance</uri> is a GTK theme and icon configurator that allows you "
+"to customise the look of LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):86
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxde-common\">LXDE-"
+"common</uri> is a collection of default configuration files and the main set "
+"of icons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):91
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxmenu-data"
+"\">LXmenu-data</uri> is the application menu manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):96
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxinput\">LXinput</"
+"uri> is a keyboard and mouse configurator"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):101
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxpanel\">LXpanel</"
+"uri> is the panel that includes the application menu, system tray, and clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):106
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxrandr\">LXrandr</"
+"uri> is a graphical interface to X Resize and Rotate, allowing for display "
+"manipulation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):112
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxsession"
+"\">LXsession</uri> is a session manager, providing options to shutdown, "
+"reboot, and suspend the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):118
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxsession-edit\"> "
+"LXsession-edit</uri> allows you to enable/disable applications at startup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):122
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxshortcut"
+"\">LXshortcut</uri> is an easy way to edit application shortcuts, especially "
+"for desktop icons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):127
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxtask\">LXtask</"
+"uri> is the task manager used to view/edit running services and programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):131
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxterminal"
+"\">LXterminal</uri> is the vte-based tabbed terminal emulator"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):141
+msgid "Other Applications used by LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):145
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-wm/openbox\">OpenBox</"
+"uri> is the window manager, responsible for drawing the containers for "
+"programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):150
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/pcmanfm\">PCManFM</"
+"uri> is the incredibly fast, tabbed file manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):155
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/obconf\">ObConf</"
+"uri> is the configurator for OpenBox, allowing you to change window "
+"decorations and more"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):161
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/media-gfx/gpicview\">GPicView "
+"</uri> is the default image viewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):172
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):174
+msgid "Initial installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):177
+msgid ""
+"After you have emerged and configured <uri link=\"/doc/en/xorg-config\">xorg-"
+"server</uri>, you are ready to install LXDE. While you may install each "
+"component individually, the more efficient and preferred method is to emerge "
+"the meta package set:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(pre:caption):184
+msgid "Installing LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(pre):184
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av lxde-meta</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):188
+msgid ""
+"If everything looks to your liking (meaning the current set of USE flags, "
+"etc.), then say \"yes\" when asked if you want to emerge the packages. Just "
+"like with other desktop environments, you will need to tell the X Server to "
+"load LXDE automatically, by adding it to your <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(pre:caption):196
+msgid "Adding LXDE to your .xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(pre):196
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>echo \"exec startlxde\" &gt;&gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):200
+msgid ""
+"This will automatically start your LXDE session when you type <c>startx</c> "
+"at the console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(note):205
+msgid ""
+"If you use a login manager like SLiM, XDM, GDM, or KDM, you do not need to "
+"edit your <path>~/.xinitrc</path>. LXDE will simply show up as a choice in "
+"your login manager's screen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(impo):211
+msgid ""
+"As each user has his or her own <path>.xinitrc</path>, you need to make sure "
+"to issue that command as <e>your user</e>, not as root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):221
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):223
+msgid "GTK icon warning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):226
+msgid ""
+"Now that the X server knows to start LXDE on command, type in <c>startx</c> "
+"to fire up LXDE. The first thing you may notice is that you get a warning "
+"about an improper GTK icon set. To fix this minor hangup, you simply need to "
+"change the icon theme. To do so, click on the LXDE application menu (in the "
+"lower left-hand corner of the panel), and go to Preferences --&gt; "
+"Appearance. In the LXappearance menu, click on the \"Icon\" tab, and choose "
+"nuoveXT.2.2. Hit \"Apply,\" and then \"Close.\" The next time you login to "
+"LXDE, the error message will not appear. However, you are not limited to "
+"using the nuoveXT.2.2 icon theme. You may install any other icon theme "
+"through LXappearance, and when it is selected, the GTK icon warning will no "
+"longer appear when starting PCManFM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):242
+msgid "Right-click menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):245
+msgid ""
+"In LXDE, every appearance option is not handled through LXappearance as one "
+"might believe. Rather, there are some common options that are handled "
+"through a right-click menu on the desktop. At the bottom of that menu is the "
+"\"Desktop Settings\" menu. In here, you can find icon sizes, single-click "
+"and double-click behavior, maximum thumbnail size, and desktop wallpaper "
+"settings. It may behoove you to look through the these tabs for additional "
+"appearance settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(note):255
+msgid ""
+"These \"Desktop Settings\" can also be found by opening up the file manager "
+"(PCManFM), and going to Edit --&gt; Preferences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):265
+msgid "Further documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(title):267
+msgid "External resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(p):270
+msgid ""
+"Though this guide will help you get LXDE installed, the documentation does "
+"not stop here. There are many resources available to you regarding the "
+"various facets of the Lightweight X11 Desktop Environment. Some such "
+"resources are listed below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):278
+msgid ""
+"On the <uri link=\"http://www.lxde.org\">Official LXDE website</uri> you "
+"will find information regarding developmental progress, a community of "
+"support, and recommend system specifications for running LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(li):283
+msgid ""
+"The <uri link=\"http://wiki.lxde.org/en/Main_Page\">LXDE wiki</uri> contains "
+"instructions for customising your LXDE installation, including keyboard "
+"layouts, autostarting applications, changing the default window manager, and "
+"much more"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//lxde-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/macos-guide.xml.po b/doc/gettext/ru/macos-guide.xml.po
new file mode 100644
index 0000000..599e20f
--- /dev/null
+++ b/doc/gettext/ru/macos-guide.xml.po
@@ -0,0 +1,65 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(guide:link):6
+msgid "/doc/en/macos-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(guide:redirect):6
+msgid "/proj/en/gentoo-alt/macos/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(title):8
+msgid "Gentoo For Mac OS X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(mail:link):11
+msgid "ppc-macos@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(mail):11
+msgid "PPC MacOS Team"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(abstract):14
+msgid "This guide has been removed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(version):22
+msgid "2.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(date):23
+msgid "2005-11-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(title):26
+msgid "Notice"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(p):30
+msgid ""
+"This guide has been removed. Please check the <uri link=\"/proj/en/gentoo-"
+"alt/macos/\">Portage for Darwin/Mac OS X</uri> project page for more "
+"information."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//macos-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/mailfilter-guide.xml.po b/doc/gettext/ru/mailfilter-guide.xml.po
new file mode 100644
index 0000000..f15e995
--- /dev/null
+++ b/doc/gettext/ru/mailfilter-guide.xml.po
@@ -0,0 +1,2631 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(guide:link):6
+msgid "/doc/en/mailfilter-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):7
+msgid "Gentoo mailfiltering gateway guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail:link):10
+msgid "jaervosz@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail):10
+msgid "Sune Kloppenborg Jeppesen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(author:title):12
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail:link):13
+msgid "gentoo@hilli.dk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail):13
+msgid "Jens Hilligsøe"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(author:title):15
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail:link):16
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(mail):16
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(abstract):19
+msgid ""
+"This guide is step-by-step guide for installing spam fighting technologies "
+"for Postfix. Among them Amavisd-new using Spamassassin and ClamAV, "
+"greylisting and SPF."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(version):29
+msgid "0.14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(date):30
+msgid "2007-08-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):33
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1296
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1521
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):37
+msgid ""
+"This guide describe step by step how to install a spam and virus filtering "
+"mail gateway. It is quite simple to adopt this to a single server solution."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):45
+msgid "The big picture"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):48
+msgid ""
+"This document describe how to setup a spam filtering mail gateway with "
+"multiple domains. This server is meant to run in front of the mail servers "
+"actually keeping the mail accounts i.e. Microsoft Exchange or Lotus Notes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):55
+msgid ""
+"In this setup applications with good security records and readable "
+"configuration files have been chosen. The email MTA is postfix which has a "
+"good security record and is fairly easy to setup right. Postfix will listen "
+"normally on port 25 for incoming mail. Upon reception it will forward it to "
+"Amavisd-new on port 10024. Amavisd-new will then filter the mail through "
+"different filters before passing the mail back to Postfix on port 10025 "
+"which in turn will forward the mail to the next mail server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):65
+msgid ""
+"Amavisd-new is a content filtering framework utilizing helper applications "
+"for virus filtering and spam filtering. In this setup we will be using two "
+"helper applications one ClamAV for filtering virus mails and Spamassassin "
+"for filtering spam. Spamassassin itself can function as yet another layer of "
+"content filtering framework and utilize the helper applications Vipul's "
+"Razor2 and DCC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):73
+msgid ""
+"Unlike many other spam fighting technologies like RBLs and others "
+"Spamassassin does not simply accept or reject a given email based on one "
+"single test. It uses a lot of internal tests and external helper "
+"applications to calculate a spam score for every mail passed through. This "
+"score is based on the following tests:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):81
+msgid "Bayesian filtering"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):82
+msgid "Static rules based on regular expressions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):85
+msgid "RBLs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):86
+msgid "Razor2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):87
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2106
+msgid "Pyzor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):88
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):236
+msgid "DCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):83
+msgid "Distributed and collaborative networks: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):93
+msgid ""
+"The first part (chapters 1 to 4) of the guide will describe the basic setup "
+"of a mailfiltering gateway. The next chapters can be implemented "
+"individually with no dependence between each chapter. These chapters "
+"describe how to:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):100
+msgid ""
+"setup special IMAP folders for learning of the Bayesian filter and for "
+"delivery of false positives"
+msgstr ""
+
+#. <li>setup log analyzers to create daily reports</li>
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):107
+msgid "setup greylisting with Postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):108
+msgid "setup Amavisd-new to use a MySQL backend for user preferences"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):109
+msgid "setup Spamassassin to use a MySQL backend for AWL and Bayes data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):112
+msgid ""
+"The IMAP folders will be using the maildir format. Having each mail in a "
+"separate file makes handling much simpler. If you're using mbox I propose to "
+"give maildir a try. If you're not already using maildir emerge the necessary "
+"tools with <c>emerge courier-imap</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):119
+msgid ""
+"A planned fifth part will contain various tips regarding performance and "
+"things you may want to know (running chrooted, postfix restrictions, etc.)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):124
+msgid ""
+"Delegating responsibility to third parties is not without risks. You have to "
+"know and trust these third parties. In this setup only the decision to "
+"quarantine virus mails are based on a single third party. Using "
+"Spamassassin's scoring system the decision to stop spam mails are not made "
+"by a single authority except perhaps Spamassassins own static rules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):132
+msgid ""
+"When rejecting spam mails at the MTA level you have to be very careful when "
+"selecting the RBL's you want to use, i.e. SpamCop is a bad RBL to use at the "
+"MTA level because you will experience false positives because sometimes "
+"their listing is just too aggressive. Further info at <uri link=\"http://www."
+"geekcomix.com/cgi-bin/classnotes/wiki.pl?UNIX03/"
+"Realtime_Blackhole_Lists_Are_Bad\">Realtime Blackhole Lists Are Bad</uri> "
+"and <uri link=\"http://theory.whirlycott.com/~phil/antispam/rbl-bad/rbl-bad."
+"html\">The Spam Problem: Moving Beyond RBLs</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):146
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1572
+msgid "Preparations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):149
+msgid ""
+"Before you start make sure that you have a working Postfix installation "
+"where you can send and receive mails also you need a backend mailserver. If "
+"you're not experienced with setting up Postfix it might quickly become too "
+"complicated if all should be set up at once. If you need help you can find "
+"it in the excellent <uri link=\"http://www.gentoo.org/doc/en/virt-mail-howto."
+"xml\">Virtual Mailhosting System with Postfix Guide</uri> in the Gentoo "
+"Documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):163
+msgid "Installing the programs needed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):167
+msgid ""
+"We start out by installing the most important programs: Amavisd-new, "
+"Spamassassin and ClamAV."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):172
+msgid "Installing Amavis, Spamassassin and Clamav"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):172
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge amavisd-new spamassassin clamav </i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):176
+msgid ""
+"As previously mentioned you should already have a working <c>postfix</c> "
+"instance running on the box. Basically this shouldn't be much more than "
+"<c>emerge postfix</c><e>and</e> have a basic understanding of how Postfix is "
+"working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):186
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):204
+msgid "Setting up DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):189
+msgid ""
+"If you're not setting up a gateway server but have the mailboxes on the same "
+"server you only have to create the MX-Record."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):194
+msgid ""
+"While the programs are emerging fire up another shell and create the needed "
+"DNS records."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):199
+msgid ""
+"Start out by creating a <c>MX</c> record for the mail gateway and an <c>A</"
+"c> record for the next destination."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):204
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Create a MX record for the gateway server)</comment>\n"
+"                MX      10      mailgateway.mydomain.tld.\n"
+"<comment>(Create an A record for the gateway server)</comment>\n"
+"mailgateway     A       mgw.ip.add.here\n"
+"<comment>(Create an A record for the next hop mail server)</comment>\n"
+"mail            A       ms.ip.add.here\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):213
+msgid ""
+"Some ADSL providers might block port 25 and force you to relay mail through "
+"one of their servers. Typically you have to create a secondary MX-Record "
+"like <c>MX 20 backup-mx.some-isp.tld</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):222
+msgid "Opening the firewall"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):225
+msgid ""
+"In addition to allowing normal mail traffic you have to allow a few services "
+"through your firewall to allow the network checks to communicate with the "
+"servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(th):233
+msgid "Application"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(th):233
+msgid "Protocol"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(th):233
+msgid "Port"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):236
+msgid "UDP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):236
+msgid "6277"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):239
+msgid "Razor(outgoing ping)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):239
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):242
+msgid "TCP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):239
+msgid "7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):242
+msgid "Razor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(ti):242
+msgid "2703"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):246
+msgid "Razor uses pings to discover what servers are closest to it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):253
+msgid "Configuring Postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):256
+msgid ""
+"First we have to tell <c>postfix</c> to listen on port 10025 and we remove "
+"most of the restrictions as they have already been applied by the "
+"<c>postfix</c> instance listening on port 25. Also we ensure that it will "
+"only listen for local connections on port 10025. To accomplish this we have "
+"to add the following at the end of <path>/etc/postfix/master.cf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):264
+msgid "Changing the master.cf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):264
+#, no-wrap
+msgid ""
+"\n"
+"smtp-amavis     unix -        -       n     -       2  smtp\n"
+"  -o smtp_data_done_timeout=1200\n"
+"  -o smtp_send_xforward_command=yes\n"
+"<comment>#Equivalently when using lmtp:\n"
+"#lmtp-amavis    unix -        -       n     -       2  lmtp\n"
+"#   -o lmtp_data_done_timeout=1200\n"
+"#   -o lmtp_send_xforward_command=yes</comment>\n"
+"\n"
+"127.0.0.1:10025 inet n        -       n     -       -  smtpd\n"
+"  -o content_filter=\n"
+"  -o local_recipient_maps=\n"
+"  -o relay_recipient_maps=\n"
+"  -o smtpd_restriction_classes=\n"
+"  -o smtpd_client_restrictions=\n"
+"  -o smtpd_helo_restrictions=\n"
+"  -o smtpd_sender_restrictions=\n"
+"  -o smtpd_recipient_restrictions=permit_mynetworks,reject\n"
+"  -o mynetworks=127.0.0.0/8\n"
+"  -o strict_rfc821_envelopes=yes\n"
+"  -o smtpd_error_sleep_time=0\n"
+"  -o smtpd_soft_error_limit=1001\n"
+"  -o smtpd_hard_error_limit=1000\n"
+"\n"
+"<comment>#If you want to use proxy filtering instead\n"
+"#smtp            inet n         -       n      -       8 smtpd\n"
+"# -o smtpd_proxy_filter=127.0.0.1:10024\n"
+"# -o smtpd_client_connection_count_limit=4\n"
+"#If you don't want to scan outgoing mail use this\n"
+"#10.0.0.2:smtp   inet n         -       n       -      - smtpd\n"
+"#-o content_filter=</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):297
+msgid ""
+"The <c>smtp-amavis</c> line specifies that a maximum of two of these "
+"processes may run at any time. If you need a greater degree of concurrency "
+"tune this number to fit your needs. Remember that to match the number with "
+"<c>$max_servers</c> in <path>amavisd.conf</path>. Keep in mind that "
+"<c>amavisd-new</c> is quite memory-intensive and raising the amount of "
+"<c>amavisd-new</c> processes too high can easily lead to memory starvation "
+"and heavy swapping, which leads to drastically reduced performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):307
+msgid ""
+"If you want to reject spam early on in the process you can use the Before-"
+"Queue (proxy) method instead of the filter method. If you uncomment the "
+"three lines you will have to set <c>content_filter=</c> in <path>main.cf</"
+"path>. This is not recommended for high traffic servers as the number of "
+"concurrent connections are limited to the number of amavisd instances."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):316
+msgid "The Before-Queue(proxy) method is still not properly tested."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):320
+msgid ""
+"If you, for any reason whatsoever, want to send mail from this box and don't "
+"want it scanned, add another postfix instance by uncommenting the last two "
+"lines and substitute with a proper IP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):326
+msgid ""
+"The file <path>master.cf</path> tells the postfix master program how to run "
+"each individual postfix process. More info with <c>man 8 master</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):332
+msgid ""
+"Next we need the main <c>postfix</c> instance listening on port 25 to filter "
+"the mail through <c>amavisd-new</c> listening on port 10024."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):337
+msgid ""
+"We also need to set the next hop destination for mail. Tell Postfix to "
+"filter all mail through an external content filter and enable explicit "
+"routing to let Postfix know where to forward the mail to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):343
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):985
+msgid "Modifying /etc/postfix/main.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):343
+#, no-wrap
+msgid ""
+"\n"
+"biff = no\n"
+"empty_address_recipient = MAILER-DAEMON\n"
+"queue_minfree = 120000000\n"
+"\n"
+"content_filter = smtp-amavis:[127.0.0.1]:10024\n"
+"<comment>#Equivalently when using lmtp:\n"
+"#content_filter = lmtp-amavis:[127.0.0.1]:10024\n"
+"\n"
+"# TRANSPORT MAP\n"
+"#\n"
+"# Insert text from sample-transport.cf if you need explicit routing.</comment>\n"
+"transport_maps = hash:/etc/postfix/transport\n"
+"\n"
+"relay_domains = $transport_maps\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):360
+msgid ""
+"Postfix has a lot of options set in <path>main.cf</path>. For further "
+"explanation of the file please consult <c>man 5 postconf</c> or the same "
+"online <uri link=\"http://www.postfix.org/postconf.5.html\">Postfix "
+"Configuration Parameters</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):367
+msgid ""
+"The format of the <path>transport</path> file is the normal Postfix hash "
+"file. Mail to the domain on the left hand side is forwarded to the "
+"destination on the right hand side."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):373
+msgid "/etc/postfix/transport"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):373
+#, no-wrap
+msgid ""
+"\n"
+"mydomain.tld                          smtp:mail.mydomain.tld\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):377
+msgid ""
+"After we have edited the file we need to run the <c>postmap</c> command. "
+"Postfix does not actually read this file so we have to convert it to the "
+"proper format with <c>postmap /etc/postfix/transport</c>. This creates the "
+"file <path>/etc/postfix/transport.db</path>. There is no need to reload "
+"Postfix as it will automatically pick up the changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):385
+msgid ""
+"If the next hop mail server is not listening on the standard SMTP port 25 "
+"you can tell postfix to use a given port number, like <c>smtp:mail.mydomain."
+"tld:25000</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):391
+msgid ""
+"If your first attempts to send mail result in messages bouncing, you've "
+"likely made a configuration error somewhere. Try temporarily enabling "
+"<c>soft_bounce</c> while you work out your configuration issues. This "
+"prevents postfix from bouncing mails on delivery errors by treating them as "
+"temporary errors. It keeps mails in the mail queue until <c>soft_bounce</c> "
+"is disabled or removed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):400
+msgid "Enabling soft_bounce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):400
+#, no-wrap
+msgid ""
+"\n"
+"# <i>postconf -e \"soft_bounce = yes\"</i>\n"
+"# <i>/etc/init.d/postfix reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):405
+msgid ""
+"Once you've finished creating a working configuration, be sure to disable or "
+"remove <c>soft_bounce</c> and reload postfix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):413
+msgid "Configuring Amavisd-new"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):416
+msgid ""
+"Amavisd-new is used to handle all the filtering and allows you to easily "
+"glue together severel different technologies. Upon reception of a mail "
+"message it will extract the mail, filter it through some custom filters, "
+"handle white and black listing, filter the mail through various virus "
+"scanners and finally it will filter the mail using SpamAssassin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):424
+msgid "Amavisd-new itself has a number of extra features:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):429
+msgid ""
+"it identifies dangerous file attachments and has policies to handle them"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):435
+msgid "whitelists"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):436
+msgid "blacklists"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):437
+msgid "spam score thresholds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):438
+msgid "virus and spam policies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(li):432
+msgid "per-user, per-domain and system-wide policies for: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):443
+msgid ""
+"Apart from <c>postfix</c> and <c>freshclam</c> we will run all applications "
+"as the user <c>amavis</c>."
+msgstr ""
+
+#. <p>
+#. Create the new home directory and set the proper permissions.
+#. </p>
+#.
+#. <pre caption="Create the new home directory and set the proper permissions">
+#. # <i>mkdir /var/amavis</i>
+#. # <i>chown amavis:amavis /var/amavis</i>
+#. # <i>chmod 750 /var/amavis</i>
+#. </pre>
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):466
+msgid "Edit the following lines in <path>/etc/amavisd.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):470
+msgid "Editing /etc/amavisd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):470
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Insert the domains to be scanned)</comment>\n"
+"$mydomain = 'example.com';\n"
+"<comment>(Bind only to loopback interface)</comment>\n"
+"$inet_socket_bind = '127.0.0.1';\n"
+"<comment>(Forward to Postfix on port 10025)</comment>\n"
+"$forward_method = 'smtp:127.0.0.1:10025';\n"
+"$notify_method = $forward_method;\n"
+"<comment>(Define the account to send virus alert emails)</comment>\n"
+"$virus_admin = \"virusalert\\@$mydomain\";\n"
+"<comment>(Always add spam headers)</comment>\n"
+"$sa_tag_level_deflt  = -100;\n"
+"<comment>(Add spam detected header aka X-Spam-Status: Yes)</comment>\n"
+"$sa_tag2_level_deflt = 5;\n"
+"<comment>(Trigger evasive action at this spam level)</comment>\n"
+"$sa_kill_level_deflt = $sa_tag2_level_deflt;\n"
+"<comment>(Do not send delivery status notification to sender.  It does not affect\n"
+"delivery of spam to recipient. To do that, use the kill_level)</comment>\n"
+"$sa_dsn_cutoff_level = 10;\n"
+"<comment>Don't bounce messages left and right, quarantine\n"
+"instead</comment>\n"
+"$final_virus_destiny      = D_DISCARD;  # (defaults to D_DISCARD)\n"
+"$final_banned_destiny     = D_DISCARD;  # (defaults to D_BOUNCE)\n"
+"$final_spam_destiny       = D_DISCARD;  # (defaults to D_BOUNCE)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):496
+msgid ""
+"With this line <c>$sa_tag2_level_deflt = 5;</c> you set the Spamassassin "
+"spam score to 5. This might be a bit low. As you might have noticed the "
+"Amavisd-new default is <c>6.3</c>. If you don't want to see a single spam "
+"mail in your mail folder choose <c>5</c>, but if you don't want to deal with "
+"false positives choose <c>6.3</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):504
+msgid ""
+"Create a quarantine directory for the virus mails as we don't want these "
+"delivered to our users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):509
+msgid "Create a quarantine directory for the virus mails"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):509
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /var/amavis/virusmails</i>\n"
+"# <i>chown amavis:amavis /var/amavis/virusmails</i>\n"
+"# <i>chmod 750 /var/amavis/virusmails</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):515
+msgid "Amavisd-new offers finer policy tuning by using policy banks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):522
+msgid "Configuring ClamAV"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):525
+msgid ""
+"As virus scanner we use ClamAV as it has a fine detection rate comparable "
+"with commercial offerings, it is very fast and it is Open Source Software. "
+"We love log files, so make <c>clamd</c> log using <c>syslog</c> and turn on "
+"verbose logging. Also do not run <c>clamd</c> as <c>root</c>. Now edit "
+"<path>/etc/clamd.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):533
+msgid "Edit /etc/clamd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):533
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Verbose logging with syslog)</comment>\n"
+"LogSyslog\n"
+"LogVerbose\n"
+"LogFacility LOG_MAIL\n"
+"<comment>(Change pid file location)</comment>\n"
+"PidFile /var/run/amavis/clamd.pid\n"
+"<comment>(Set the clamav socket)</comment>\n"
+"LocalSocket /var/amavis/clamd\n"
+"<comment>(Close the connection when this limit is exceeded)</comment>\n"
+"StreamMaxLength 10M\n"
+"<comment>(Don't run clamd as root)</comment>\n"
+"User amavis\n"
+"<comment>(Newer versions require you to uncomment this)</comment>\n"
+"ScanMail\n"
+"ScanArchive\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):551
+msgid "Also remember to remove the Example directive to make ClamAV work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):555
+msgid ""
+"ClamAV comes with the <c>freshclam</c> deamon dedicated to periodical checks "
+"of virus signature updates. Instead of updating virus signatures twice a day "
+"we will make <c>freshclam</c> update virus signatures every two hours."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):561
+msgid "Edit /etc/freshclam.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):561
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Syslog logging)</comment>\n"
+"LogSyslog\n"
+"<comment>(Verbose logging)</comment>\n"
+"LogVerbose\n"
+"<comment>(Explicitly drop root privileges)</comment>\n"
+"DatabaseOwner clamav\n"
+"<comment>(Check for updates every two hours. That is the official recommendation)</comment>\n"
+"Checks 12\n"
+"<comment>(Use the mirror closest to you. Replace XY with your country code</comment>\n"
+"DatabaseMirror db.XY.clamav.net\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):574
+msgid ""
+"Start <c>clamd</c> with <c>freshclam</c> using the init scripts by modifying "
+"<path>/etc/conf.d/clamd</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):579
+msgid "Modifying /etc/conf.d/clamd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):579
+#, no-wrap
+msgid ""
+"\n"
+"START_CLAMD=yes\n"
+"FRESHCLAM_OPTS=\"-d\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):584
+msgid ""
+"At last modify <path>amavisd.conf</path> with the new location of the socket."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):589
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1087
+msgid "Modifying /etc/amavisd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):589
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Uncomment the clamav scanner and modify socket location)</comment>\n"
+"['ClamAV-clamd',\n"
+"\\&amp;ask_daemon, [\"CONTSCAN {}\\n\", \"/var/amavis/clamd\"],\n"
+"  qr/\\bOK$/, qr/\\bFOUND$/,\n"
+"  qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ],\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):597
+msgid ""
+"Do NOT modify the <c>$unix_socketname</c> unless you know what you're doing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):604
+msgid "Configuring Vipul's Razor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):607
+msgid ""
+"Razor2 is a collaborative and distributed spam checksum network. Install it "
+"with <c>emerge razor</c> and create the needed configuration files. Do this "
+"as user <c>amavis</c> by running <c>su - amavis</c> followed <c>razor-admin -"
+"create</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):614
+msgid "Creating the required configuration files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):614
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge razor</i>\n"
+"\n"
+"<comment>(Temporarily set amavis' shell to bash)</comment>\n"
+"# <i>usermod -s /bin/bash amavis</i>\n"
+"# <i>su - amavis</i>\n"
+"$ <i>razor-admin -create</i>\n"
+"$ <i>exit</i>\n"
+"\n"
+"<comment>(Reset the shell to /bin/false)</comment>\n"
+"# <i>usermod -s /bin/false amavis</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):630
+msgid "Configuring Distributed Checksum Clearinghouse (dcc)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):633
+msgid ""
+"Like Razor2, dcc is a collaborative and distributed spam checksum network. "
+"Its philosopy is to count the number of recipients of a given mail "
+"identifying each mail with a fuzzy checksum."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):639
+msgid "Installing DCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):639
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge dcc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):646
+msgid "Configuring Spamassassin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):649
+msgid ""
+"Amavis is using the Spamassassin Perl libraries directly so there is no need "
+"to start the service. Also this creates some confusion about the "
+"configuration as some Spamassassin settings are configured in <path>/etc/"
+"mail/spamassassin/local.cf</path> and overridden by options in <path>/etc/"
+"amavisd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):657
+msgid "Create /etc/mail/spamassassin/local.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):657
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Enable the Bayes system</comment>\n"
+"use_bayes               1\n"
+"\n"
+"<comment># Enable all network checks</comment>\n"
+"skip_rbl_checks         0\n"
+"\n"
+"<comment># Mail using languages used in these country codes will not be marked\n"
+"# as being possibly spam in a foreign language.\n"
+"# - danish english norwegian swedish</comment>\n"
+"ok_languages            da en no sv\n"
+"\n"
+"<comment># Mail using locales used in these country codes will not be marked\n"
+"# as being possibly spam in a foreign language.</comment>\n"
+"ok_locales              en\n"
+"\n"
+"<comment># Use a sensible bayes path</comment>\n"
+"bayes_path              /var/amavis/.spamassassin/bayes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):677
+msgid ""
+"With Spamassassin version 3.1 you have to enable DCC, Razor2 by uncommenting "
+"the corresponding lines in <path>v310.pre</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):682
+msgid ""
+"You can find inspiration for your <path>local.cf</path> file by trying the "
+"<uri link=\"http://www.yrex.com/spam/spamconfig.php\">SpamAssassin "
+"Configuration Generator</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):688
+msgid ""
+"You might also want to switch the <c>ok_languages</c> and <c>ok_locales</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):697
+msgid "Every good rule has good exceptions as well"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):701
+msgid ""
+"Once mail really starts passing through this mail gateway you will probably "
+"discover that the above setup is not perfect. Maybe some of your customers "
+"like to receive mails that others wouldn't. You can whitelist/blacklist "
+"envelope senders quite easily. Uncomment the following line in <path>amavisd."
+"conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):709
+msgid "Modifying amavisd.conf to do sitewide scoring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):709
+#, no-wrap
+msgid ""
+"\n"
+"read_hash(\"/var/amavis/sender_scores_sitewide\"),\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):713
+msgid ""
+"In the <path>sender_scores_sitewide</path> file you put complete email "
+"addresses or just the domian parts and then note a positive/negative score "
+"to add to the spam score."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):719
+msgid "whitelist_sender example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):719
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Whitelist all emails from the specific email address)</comment>\n"
+"postmaster@example.net                -3.0\n"
+"<comment>(Whitelist all emails from the example.net excluding subdomains)</comment>\n"
+".example.net                          1.0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):726
+msgid "See <path>/etc/amavisd.conf</path> for more examples."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):730
+msgid ""
+"Placing these addresses outside <path>amavisd.conf</path> is a cleaner and "
+"safer solution."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):735
+msgid ""
+"Alternatively it can be done in Spamassassin's configuration file <path>/etc/"
+"mail/spamassassin/local.cf</path> but I think it is cleaner to do it in "
+"<path>/etc/amavisd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):741
+msgid ""
+"In a later chapter I will show how to implement per-user policies using "
+"MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):746
+msgid ""
+"While waiting for a better method you can add the following to <path>amavisd."
+"conf</path> to bypass spam checks for <c>postmaster</c> and <c>abuse</c> "
+"mailboxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):752
+msgid "By pass spam filters for all postmaster and abuse mails"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):752
+#, no-wrap
+msgid ""
+"\n"
+"map { $bypass_spam_checks{lc($_)}=1 } (qw(\n"
+"        postmaster@\n"
+"        abuse@\n"
+"));\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(impo):759
+msgid ""
+"While we are at it we should <e>never</e> automatically discard mails to the "
+"<c>postmaster</c> or the <c>abuse</c> accounts. See <uri link=\"http://www."
+"ietf.org/rfc/rfc2142.txt\">RFC 2142 MAILBOX NAMES FOR COMMON SERVICES, ROLES "
+"AND FUNCTIONS</uri>. Otherwise your domains might end up listed in some of "
+"the evil lists over at <uri link=\"http://www.rfc-ignorant.org/\">rfc-"
+"ignorant.org</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):773
+msgid "Adding more rules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):777
+msgid ""
+"If you want to use more rules provided by the SARE Ninjas over at the <uri "
+"link=\"http://www.rulesemporium.com/\">SpamAssassin Rules Emporium</uri> you "
+"can easily add and update them using the <c>sa-update</c> mechanism included "
+"in Spamassassin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):784
+msgid ""
+"A brief guide to using SARE rulesets with <c>sa-update</c> can be found <uri "
+"link=\"http://daryl.dostech.ca/sa-update/sare/sare-sa-update-howto.txt"
+"\">here</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):794
+msgid "Testing and finishing up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):796
+msgid "Testing the setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):799
+msgid ""
+"Now before you start <c>freshclam</c> you can manually verify that it works."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):803
+msgid "Testing freshclam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):803
+#, no-wrap
+msgid ""
+"\n"
+"# <i>freshclam</i>\n"
+"ClamAV update process started at Sun May  2 09:13:41 2004\n"
+"Reading CVD header (main.cvd): OK\n"
+"Downloading main.cvd [*]\n"
+"main.cvd updated (version: 22, sigs: 20229, f-level: 1, builder: tkojm)\n"
+"Reading CVD header (daily.cvd): OK\n"
+"Downloading daily.cvd [*]\n"
+"daily.cvd updated (version: 298, sigs: 1141, f-level: 2, builder: diego)\n"
+"Database updated (21370 signatures) from database.clamav.net (193.1.219.100).\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):815
+msgid ""
+"Now you have updated virus definitions and you know that <path>freshclam."
+"conf</path> is working properly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):820
+msgid ""
+"Test freshclam and amavisd from the cli and amavisd testmails. Start "
+"<c>clamd</c> and <c>amavis</c> with the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):825
+msgid "Start amavisd and clamd and reload postfix configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):825
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/clamd start</i>\n"
+"# <i>/etc/init.d/amavisd start</i>\n"
+"# <i>/etc/init.d/postfix reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):831
+msgid ""
+"If everything went well <c>postfix</c> should now be listening for mails on "
+"port 25 and for reinjected mails on port 10024. To verify this check your "
+"log file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):836
+msgid "Checking log files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):836
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tail -f /var/log/mail.log</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):840
+msgid ""
+"Depending on your log settings the correct path might be <path>/var/log/"
+"messages</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):845
+msgid ""
+"Now if no strange messages appear in the log file it is time for a new test."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):850
+msgid ""
+"Use <c>netcat</c> to manually connect to <c>amavisd</c> on port 10024 and "
+"<c>postfix</c> on port 10025."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):855
+msgid ""
+"Netcat can be used as an advanced replacement for <c>telnet</c>. Install it "
+"with <c>emerge netcat</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):860
+msgid ""
+"For some unknown reason you can not complete a manual mail injection to "
+"<c>amavisd</c> with netcat. Use <c>telnet</c> instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):865
+msgid ""
+"Manually checking that amavisd and postfix are listning to the new ports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):865
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nc localhost 10024</i>\n"
+"<comment>(Amavis working)</comment>\n"
+"220 [127.0.0.1] ESMTP amavisd-new service ready\n"
+"<i>nc localhost 10025</i>\n"
+"<comment>(Postfix reinject working)</comment>\n"
+"220 example.com ESMTP Postfix\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):874
+msgid ""
+"If you want to see the complete output from amavisd-new start <c>amavisd "
+"debug-sa</c> as the <c>amavis</c> user and send a mail. For this to work you "
+"might have to change the default shell in <path>/etc/passwd</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):881
+msgid "Add <c>amavisd</c> and <c>clamd</c> to the <c>default</c> runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):885
+msgid "Add amavisd and clamd to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):885
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add clamd default</i>\n"
+"# <i>rc-update add amavisd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):890
+msgid ""
+"We do not add <c>spamd</c> to the default runlevel as <c>amavisd</c> uses "
+"the Spamassassin Perl libraries directly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):895
+msgid ""
+"You might notice <c>Net::Server: Couldn't POSIX::setuid to ... []</c> lines "
+"in your log. According to <uri link=\"http://www.ijs.si/software/amavisd/"
+"README.chroot\">amavis chroot README</uri>, if the process UID remains 0 "
+"(<c>root</c>), the program will terminate, otherwise you can consider the "
+"message just as informative. This is because <c>POSIX::setuid()</c> returns "
+"a string <c>0 but true</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(impo):905
+msgid ""
+"If you enabled login for amavis remember to set back the login shell in "
+"<path>/etc/passwd</path> to <c>/bin/false</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):915
+msgid "Autolearning and sidelining emails"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):917
+msgid "Creating the spamtrap user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):920
+msgid "Create the spamtrap account and directories."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):924
+msgid "Create spamtrap account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):924
+#, no-wrap
+msgid ""
+"\n"
+"# <i>useradd -m spamtrap</i>\n"
+"# <i>maildirmake /home/spamtrap/.maildir</i>\n"
+"# <i>chown -R spamtrap:mailusers /home/spamtrap/.maildir</i>\n"
+"<comment>(Give the spamtrap user a sensible password)</comment>\n"
+"# <i>passwd spamtrap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):932
+msgid ""
+"If you manually want to check some of the mails to ensure that you have no "
+"false positives you can use the following <c>procmail</c> recipe to sideline "
+"spam found into different mail folders."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):941
+msgid "Creating .procmailrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):944
+msgid "Creating /home/spamtrap/.procmailrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):944
+#, no-wrap
+msgid ""
+"\n"
+"<comment>#Set some default variables</comment>\n"
+"MAILDIR=$HOME/.maildir\n"
+"\n"
+"SPAM_FOLDER=$MAILDIR/.spam-found/\n"
+"\n"
+"LIKELY_SPAM_FOLDER=$MAILDIR/.likely-spam-found/\n"
+"\n"
+"<comment>#Sort mails with a spamscore of 7+ to the spamfolder</comment>\n"
+":0:\n"
+"* ^X-Spam-Status: Yes\n"
+"* ^X-Spam-Level: \\*\\*\\*\\*\\*\\*\\*\n"
+"$SPAM_FOLDER\n"
+"\n"
+"<comment>#Sort mail with a spamscore between 5-7 to the likely spam folder</comment>\n"
+":0:\n"
+"* ^X-Spam-Status: Yes\n"
+"$LIKELY_SPAM_FOLDER\n"
+"\n"
+"<comment>#Sort all other mails to the inbox</comment>\n"
+":0\n"
+"*\n"
+"./\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):969
+msgid ""
+"If your mail server is going to receive a lot of mail you should NOT use the "
+"likely-spam recipe. Instead set <c>$sa_tag2_level_deflt</c> high enough to "
+"avoid false positives and filter it directly to <c>$SPAM_FOLDER</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):976
+msgid ""
+"If you haven't already installed <c>procmail</c> do it with <c>emerge "
+"procmail</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):981
+msgid "Now make sure that Postfix uses <c>procmail</c> to deliver mail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):985
+#, no-wrap
+msgid ""
+"\n"
+"mailbox_command = /usr/bin/procmail -a \"DOMAIN\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):992
+msgid "Create mailfolders"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):995
+msgid "Now we will create shared folders for ham and spam."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):999
+msgid "Create the necessary mailfolders"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):999
+#, no-wrap
+msgid ""
+"\n"
+"# <i>maildirmake /var/amavis/.maildir</i>\n"
+"# <i>maildirmake -S /var/amavis/.maildir/Bayes</i>\n"
+"# <i>maildirmake -s write -f spam /var/amavis/.maildir/Bayes</i>\n"
+"# <i>maildirmake -s write -f ham /var/amavis/.maildir/Bayes</i>\n"
+"# <i>maildirmake -s write -f redeliver /var/amavis/.maildir/Bayes</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1007
+msgid ""
+"Amavisd-new needs to be able to read these files as well as all mailusers. "
+"Therefore we add all the relevant users to the mailuser group along with "
+"amavis."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1012
+msgid "Setting the proper permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1012
+#, no-wrap
+msgid ""
+"\n"
+"# <i>groupadd mailusers</i>\n"
+"# <i>usermod -G mailusers spamtrap</i>\n"
+"# <i>chown -R amavis:mailusers /var/amavis/.maildir/</i>\n"
+"# <i>chown amavis:mailusers /var/amavis/</i>\n"
+"# <i>chmod -R 1733 /var/amavis/.maildir/Bayes/</i>\n"
+"# <i>chmod g+rx /var/amavis/.maildir/</i>\n"
+"# <i>chmod g+rx /var/amavis/.maildir/Bayes/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):1022
+msgid ""
+"This grants members of the <c>mailusers</c> groups access to <c>amavis</c> "
+"mail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1027
+msgid ""
+"This makes the spam and ham folders writable but not readable. This way "
+"users can safely submit their ham without anyone else being able to read it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1032
+msgid "Then run the following command as the <c>spamtrap</c> user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1036
+msgid "Adding the shared folders to the users mailfolder"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1036
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>maildirmake --add Bayes=/var/amavis/.maildir/Bayes $HOME/.maildir</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1040
+msgid ""
+"We have to give the group read permissions on the <path>Bayes</path> folder "
+"in order for the mail client to be able to see the subdirectories used by "
+"IMAP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1049
+msgid "Adding cron jobs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1052
+msgid ""
+"Now run <c>crontab -u amavis -e</c> to edit the amavis crontab to enable "
+"automatic learning of the Bayes filter every hour."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1057
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1128
+msgid "amavis crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1057
+#, no-wrap
+msgid ""
+"\n"
+"<comment>#Auto learn</comment>\n"
+"0 * * * *          /usr/bin/sa-learn --spam /var/amavis/.maildir/Bayes/.spam/{cur,new} \\\n"
+"                    &gt; /dev/null 2&gt;&amp;1\n"
+"0 * * * *          /usr/bin/sa-learn --ham /var/amavis/.maildir/Bayes/.ham/{cur,new} &gt; \\\n"
+"                   /dev/null 2&gt;&amp;1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1065
+msgid "<c>amavis</c> has to be a member of the <c>cron</c> group to run crons."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1070
+msgid ""
+"It seems like the shared maildir folders will make <c>sa-learn</c> examine "
+"all messages twice. This should not be a problem. The output will also show "
+"that the maximum of messages learned from is half or less than the messages "
+"examined."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1079
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1805
+msgid "Modifying amavisd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1082
+msgid ""
+"Now modify amavis to redirect spam emails to the <c>spamtrap</c> account and "
+"keep spamheaders."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1087
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Define the account to send virus spam emails)</comment>\n"
+"$spam_quarantine_to = \"spamtrap\\@$myhostname\";\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1095
+msgid "Redelivering false positives"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1098
+msgid ""
+"If you set the spam score very low like we do you will probably have some "
+"false positives. These are filtered into the folder <path>likely-spam</"
+"path>. These are manually reviewed and any false positive is moved to the "
+"<path>redeliver</path> mailfolder. From there it is first fed through <c>sa-"
+"learn --ham</c> and then redelivered with all headers intact using a patched "
+"version of <uri link=\"http://www.engelschall.com/sw/smtpclient/"
+"\">smtpclient</uri> by Ralf S. Engelschall."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1109
+msgid ""
+"The original version 1.0.0 of <c>smtpclient</c> is already in Portage "
+"however to keep all headers intact we use a modified version. Here is how "
+"you install the revised version:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1115
+msgid "Installing revised smtpclient"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1115
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Switch to your portage OVERLAY)</comment>\n"
+"# <i>wget http://home.coming.dk/files/smtpclient.tar.gz</i>\n"
+"# <i>tar xzf smtpclient.tar.gz</i>\n"
+"# <i>echo \"mail-client/smtpclient    ~x86\" &gt;&gt; /etc/portage/package.keywords</i>\n"
+"# <i>echo \"mail-client/smtpclient    fullheaders\" &gt;&gt; /etc/portage/package.use</i>\n"
+"# <i>emerge smtpclient</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1124
+msgid ""
+"Check for mails in the <path>redeliver</path> folder every minute using cron."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1128
+#, no-wrap
+msgid ""
+"\n"
+"<comment>#Redeliver false positives</comment>\n"
+"* * * * *          find /var/amavis/.maildir/Bayes/.redeliver/cur/ -type f -name \\\n"
+"                   \"[0-9]*\" -exec cp {} /var/amavis/.maildir/Bayes/.ham/cur/ \\; \\\n"
+"                   &amp;&amp; find /var/amavis/.maildir/Bayes/.redeliver/cur/ -type f \\\n"
+"                   -name \"[0-9]*\" -exec /usr/local/bin/redeliver.pl {} \\;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1136
+msgid ""
+"Now we only have to copy the <c>redeliver.pl</c> file to <path>/usr/local/"
+"bin/</path>. <uri link=\"http://home.coming.dk/files/redeliver.pl\">Download "
+"it</uri> or use the version below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1143
+msgid "redeliver.pl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1143
+#, no-wrap
+msgid ""
+"\n"
+"<comment>#!/usr/bin/perl -w\n"
+"\n"
+"# Redelivers mail using a modified version of smtpclient\n"
+"# By: Jens Hilligsoe &lt;gentoo@hilli.dk&gt;</comment>\n"
+"\n"
+"use strict;\n"
+"\n"
+"if(!($#ARGV == 0)) {\n"
+"        die \"Usage:\\n$0 maildir_mail\\n\";\n"
+"}\n"
+"\n"
+"my $mail = $ARGV[0];\n"
+"my $to = \"\";\n"
+"my $from = \"\";\n"
+"\n"
+"sub prunefile ( $ );\n"
+"\n"
+"<comment># Retrieve To and From envelope adresses</comment>\n"
+"open (MAIL, $mail) or die \"Could not open $mail: $?\\n\";\n"
+"while(&lt;MAIL&gt;) {\n"
+"    if(($to eq \"\") || ($from eq \"\")) {\n"
+"        chop;\n"
+"        (my $key, my $value) = split (/:/);\n"
+"        if($key eq \"X-Envelope-To\") {\n"
+"            $to = $value;\n"
+"            $to =~ s/[\\&lt;\\&gt;,]//g; # Remove \"&lt;\", \"&gt;\" and \",\"\n"
+"            $to =~ s/^\\s+|\\s+$//g; #Remove whitespace before and after\n"
+"        }\n"
+"        if($key eq \"X-Envelope-From\") {\n"
+"            $from = $value;\n"
+"            $from =~ s/[\\&lt;\\&gt;,]//g;\n"
+"            $from =~ s/^\\s+|\\s+$//g;\n"
+"            if($from eq \"\") {\n"
+"                $from = \"postmaster\";\n"
+"            }\n"
+"        }\n"
+"    }\n"
+"}\n"
+"\n"
+"if($to eq \"\") {\n"
+"    prunefile($ARGV[0]); # Just nuke it if to is empty\n"
+"} else {\n"
+"    my $redelivercmd = \"cat $ARGV[0] | smtpclient -F -S 127.0.0.1 -P 10025 -f $from $to\";\n"
+"    unless (system($redelivercmd) == 0 ) {\n"
+"        die \"Unable to redeliver: $?\";\n"
+"    }\n"
+"    prunefile($ARGV[0]); # Clean up\n"
+"}\n"
+"\n"
+"sub prunefile ( $ ) {\n"
+"    my ($file) = @_;\n"
+"    unless (unlink $file) {\n"
+"        die \"Unable to remove mail: $?\";\n"
+"    }\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1204
+msgid "Cleaning up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1207
+msgid ""
+"We don't want to keep mail forever so we use <c>tmpwatch</c> to clean up "
+"regularily. Emerge it with <c>emerge tmpwatch</c>. Only <c>root</c> is able "
+"to run <c>tmpwatch</c> so we have to edit the <c>root</c> crontab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1213
+msgid "Modifying root crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1213
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Clean up\n"
+"# Keep virusmails for a week (24*7 hours)</comment>\n"
+"15 0 * * *      /usr/sbin/tmpwatch -c -f -d --quiet 168 /var/amavis/virusmails/\n"
+"<comment># Delete spam and ham learned after a week</comment>\n"
+"15 0 * * *      /usr/sbin/tmpwatch -c -f -d --quiet 168 /var/amavis/.maildir/Bayes/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1294
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2072
+msgid "Greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1299
+msgid ""
+"Greylisting is one of the newer weapons in the spam fighting arsenal. As the "
+"name implies it is much like whitelisting and blacklisting. Each time an "
+"unknown mailserver tries to deliver mail the mail is rejected with a <e>try "
+"again later</e> message. This means that mail gets delayed but also that "
+"stupid spam bots that do not implement the RFC protocol will drop the "
+"attempt to deliver the spam and never retry. With time spam bots will "
+"probably adjust, however it will give other technologies more time to "
+"identify the spam."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1311
+msgid ""
+"If your ISP blocks incoming traffic on port 25 and relays all mail to you "
+"through their own mail server greylisting will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1316
+msgid ""
+"Postfix 2.1 come with a simple Perl greylisting policy server that "
+"implements such a scheme. However it suffers from unpredictable results when "
+"the partition holding the greylisting database run out of space. There "
+"exists an improved version that do not suffer this problem. First I will "
+"show how to install the builtin greylisting support that come with Postfix "
+"and then I will show how to configure the more robust replacement."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1326
+msgid ""
+"There are other greylisting policy servers for Postfix around (such as <uri "
+"link=\"http://www.gasmi.net/gld.html\">Gld</uri>, which is in Portage, and "
+"<uri link=\"http://sqlgrey.sourceforge.net/\">SQLgrey</uri>). Some of them "
+"support database backends, auto whitelisting and other neat features."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1336
+msgid "Simple greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1339
+msgid ""
+"If you prefer to use the improved greylisting with postgrey you can safely "
+"skip this section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1344
+msgid ""
+"We need the file <path>greylist.pl</path> but unfortunately the ebuild does "
+"not install it as default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1349
+msgid "Getting greylist.pl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1349
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp /usr/portage/distfiles/postfix-your-version-here.tar.gz /root/</i>\n"
+"# <i>tar xzf postfix-your-version-here.tar.gz</i>\n"
+"# <i>cp postfix-2.1.0/examples/smtpd-policy/greylist.pl /usr/bin/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1355
+msgid ""
+"Now we have the file in place we need to create the directory to hold the "
+"greylisting database:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1360
+msgid "Creating directory for the greylisting database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1360
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /var/mta</i>\n"
+"# <i>chown nobody /var/mta</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):1365
+msgid ""
+"Do not create the greylisting database directory on a partition that might "
+"run out of space. While postfix can recover from no-space-left situations "
+"for the mail queue and mail box situations, this is not the case with the "
+"greylisting database. If the file becomes corrupted you may not be able to "
+"receive mail at all until you delete the file by hand."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1377
+msgid "Configuring greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1380
+msgid ""
+"Now that we have all this ready all that is left is to add it to the postfix "
+"configuration. First we add the necessary information to the <path>master."
+"cf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1386
+msgid "Modifying master.cf to use greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1386
+#, no-wrap
+msgid ""
+"\n"
+"policy-greylist  unix  -       n       n       -       -       spawn\n"
+"   user=nobody argv=/usr/bin/perl /usr/bin/greylist.pl\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1391
+msgid ""
+"The postfix spawn daemon normally kills its child processes after 1000 "
+"seconds but this is too short for the greylisting process so we have to "
+"increase the timelimit in <path>main.cf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1397
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1481
+msgid "Modifying main.cf to use greylisting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1397
+#, no-wrap
+msgid ""
+"\n"
+"policy-greylist_time_limit = 3600\n"
+"<comment>(Under smtpd_recipient_restrictions add:)</comment>\n"
+"check_sender_access hash:/etc/postfix/sender_access\n"
+"<comment>(Later on add:)</comment>\n"
+"restriction_classes = greylist\n"
+"greylist = check_policy_service unix:private/policy-greylist\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):1406
+msgid ""
+"Be sure to specify <c>check_sender_access</c> AFTER "
+"<c>reject_unauth_destination</c> or else your system could become an open "
+"mail relay."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1412
+msgid ""
+"The greylist database gets polluted quickly with bogus addresses. It helps "
+"if you protect greylist lookups with other restrictions that reject unknown "
+"senders and/or recipients."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1418
+msgid ""
+"We don't want to use greylisting for all domains but only for those "
+"frequently abused by spammers. After all it will delay mail delivery. A list "
+"of frequently forged MAIL FROM domains can be found <uri link=\"http://www."
+"monkeys.com/anti-spam/filtering/sender-domain-validate.in\">online</uri>. "
+"Add the domains you receive a lot of spam from to <path>/etc/postfix/"
+"sender_access</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1427
+msgid "Format of sender_access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1427
+#, no-wrap
+msgid ""
+"\n"
+"aol.com     greylist\n"
+"hotmail.com greylist\n"
+"bigfoot.com greylist\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1433
+msgid "If you want a more extensive list:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1437
+msgid "Adding all domains to sender_access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1437
+#, no-wrap
+msgid ""
+"\n"
+"# <i>wget http://www.monkeys.com/anti-spam/filtering/sender-domain-validate.in</i>\n"
+"# <i>cat sender-domain-validate.in | sort | awk {'print $1 \"\\t\\t greylist\"'} &gt; /etc/postfix/sender_access</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1442
+msgid "Now we only have to initialize the <path>sender_access</path> database:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1447
+msgid "Initialize sender_access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1447
+#, no-wrap
+msgid ""
+"\n"
+"# <i>postmap /etc/postfix/sender_access</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1451
+msgid "Now the setup of simple greylisting is complete."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(warn):1455
+msgid ""
+"I tried this on one box handling thousands of mails daily and the results "
+"were almost a complete disaster. After four days the box was bogged down "
+"with hundreds of old <c>greylist.pl</c> processes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1464
+msgid "Configuring improved greylisting with postgrey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1467
+msgid ""
+"You can install the enhanced greylisting policy server with a simple "
+"<c>emerge</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1472
+msgid "Installing postgrey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1472
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge postgrey</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1476
+msgid ""
+"After installing <c>postgrey</c> we have to edit <path>main.cf</path>. "
+"Changes are almost exactly like the built in greylisting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1481
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Under smtpd_recipient_restrictions add:)</comment>\n"
+"check_sender_access hash:/etc/postfix/sender_access\n"
+"<comment>(Later on add:)</comment>\n"
+"smtpd_restriction_classes = greylist\n"
+"greylist = check_policy_service inet:127.0.0.1:10030\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1489
+msgid ""
+"The Postfix SMTPD_POLICY_README only uses <c>restriction_classes</c> but "
+"that does not appear to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1494
+msgid ""
+"If you want to greylist everything instead add <c>check_policy_service "
+"inet:127.0.0.1:10030</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1499
+msgid "Finally, start the server and add it to the proper runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1503
+msgid "Starting postgrey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1503
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/postgrey start</i>\n"
+"# <i>rc-update add postgrey default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1508
+msgid ""
+"Some people like to get their mail fast and thus greylisting is worthless. "
+"However if you employ a backup mail server you can safely setup greylisting "
+"on that server. My limited experiences tell me that it can stop up to a "
+"third of the spam received."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1519
+msgid "SPF (Sender Policy Framework)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1524
+msgid ""
+"SPF allows domain owners to state in their DNS records which IP addressess "
+"should be allowed to send mails from their domain. This will prevent "
+"spammers from spoofing the <c>Return-Path</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1530
+msgid ""
+"If your ISP blocks incoming traffic on port 25 and relays all mail to you "
+"through their own mail server SPF will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1535
+msgid ""
+"First domain owners have to create a special <c>TXT</c> DNS record. Then an "
+"SPF-enabled MTA can read this and if the mail originates from a server that "
+"is not described in the SPF record the mail can be rejected. An example "
+"entry could look like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1542
+msgid "Example SPF record"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1542
+#, no-wrap
+msgid ""
+"\n"
+"example.com.  IN TXT  \"v=spf1 a mx ptr -all\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1546
+msgid ""
+"The <c>-all</c> means to reject all mail by default but allow mail from the "
+"<c>A</c>(<c>a</c>), <c>MX</c>(<c>mx</c>) and <c>PTR</c>(<c>ptr</c>) DNS "
+"records. For more info consult further resources below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1553
+msgid ""
+"If you relay outgoing mail through your ISP you will have to add: <c>include:"
+"yourisp.com</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1558
+msgid ""
+"Spamassassin 3.0 has support for SPF, however it is not enabled by default "
+"and the new policy daemon in Postfix supports SPF so let's install SPF "
+"support for Postfix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1564
+msgid ""
+"If you want to use SPF with Spamassassin instead simply <c>emerge&nbsp;dev-"
+"perl/Mail-SPF-Query</c> and restart Amavisd-new."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1575
+msgid ""
+"First you have to install Postfix 2.1 as described above. When you have "
+"fetched the source grab the <path>spf.pl</path> with:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1581
+msgid "Installing spf.pl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1581
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp postfix-&lt;version&gt;/examples/smtpd-policy/spf.pl /usr/local/bin/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1585
+msgid ""
+"The <path>spf.pl</path> coming with Postfix is slightly buggy so find and "
+"uncomment the following line: <c>push @HANDLERS, \"sender_permitted_from\"; "
+"use Mail::SPF::Query;</c>. Furthermore in about line 199 substitute "
+"<c>comemnt</c> with <c>comment</c>. Alternatively you can download a <uri "
+"link=\"http://spf.pobox.com/postfix-policyd.txt\">development version</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1594
+msgid ""
+"This Perl script also needs some Perl libraries that are not in portage but "
+"it is still quite simple to install them:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1599
+msgid "Installing the needed Perl libraries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1599
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge Mail-SPF-Query Net-CIDR-Lite Sys-Hostname-Long</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1603
+msgid ""
+"Now that we have everything in place all we need is to configure Postfix to "
+"use this new policy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1608
+msgid "Modifying master.cf to use SPF"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1608
+#, no-wrap
+msgid ""
+"\n"
+"policy-spf  unix  -       n       n       -       -       spawn\n"
+"   user=nobody argv=/usr/bin/perl /usr/local/bin/spf.pl\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1613
+msgid ""
+"Now add the SPF check in <path>main.cf</path>. Properly configured SPF "
+"should do no harm so we could check SPF for all domains:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1618
+msgid "Modifying main.cf to use SPF"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1618
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Under smtpd_recipient_restrictions add:)</comment>\n"
+"check_policy_service unix:private/policy-spf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1623
+msgid ""
+"If you're experiencing problems with SPF, e.g. when using <c>fetchmail</c>, "
+"you might want to enable SPF for certain domains only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1633
+msgid "Configuring amavisd-new to use MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1635
+msgid "Configuring MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1638
+msgid ""
+"This has not been tested on versions higher than 2.2. Feedback is welcome :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1642
+msgid ""
+"For large domains the default values you can set in <path>amavisd.conf</"
+"path> might not suit all users. If you configure amavisd-new with MySQL "
+"support you can have individual settings for users or groups of users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1649
+msgid "Creating the MySQL database and user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1649
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mysql -u root -p mysql</i>\n"
+"Enter password:\n"
+"Welcome to the MySQL monitor.  Commands end with ; or \\g.\n"
+"Your MySQL connection id is 78 to server version: 4.0.18-log\n"
+"\n"
+"Type 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n"
+"mysql&gt; <i>create database maildb;</i>\n"
+"mysql&gt; <i>GRANT INSERT,UPDATE,DELETE,SELECT ON maildb.* TO 'mail'@'localhost' IDENTIFIED BY 'very_secret_password';</i>\n"
+"mysql&gt; <i>use maildb;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1661
+msgid ""
+"Now that the database is created we'll need to create the necessary tables. "
+"You can cut and paste the following into the mysql prompt:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1666
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1859
+msgid "MySQL table layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1666
+#, no-wrap
+msgid ""
+"\n"
+"CREATE TABLE users (\n"
+"    id         int unsigned NOT NULL auto_increment,\n"
+"    priority   int          NOT NULL DEFAULT '7',  -- 0 is low priority\n"
+"    policy_id  int unsigned NOT NULL DEFAULT '1',\n"
+"    email      varchar(255) NOT NULL,\n"
+"    fullname   varchar(255) DEFAULT NULL,    -- not used by amavisd-new\n"
+"    local      char(1),     -- Y/N  (optional field, see note further down)\n"
+"    PRIMARY KEY (id),\n"
+"    KEY email (email)\n"
+"    );\n"
+"CREATE UNIQUE INDEX users_idx_email ON users(email);\n"
+"\n"
+"<comment>(any e-mail address, external or local, used as senders in wblist)</comment>\n"
+"CREATE TABLE mailaddr (\n"
+"   id         int unsigned NOT NULL auto_increment,\n"
+"   priority   int          NOT NULL DEFAULT '7',  -- 0 is low priority\n"
+"   email      varchar(255) NOT NULL,\n"
+"   PRIMARY KEY (id),\n"
+"   KEY email (email)\n"
+"   );\n"
+"CREATE UNIQUE INDEX mailaddr_idx_email ON mailaddr(email);\n"
+"\n"
+"<comment>(-- per-recipient whitelist and/or blacklist,</comment>\n"
+"<comment>-- puts sender and recipient in relation wb)</comment>\n"
+"(white or blacklisted sender)\n"
+"CREATE TABLE wblist (\n"
+"   rid        int unsigned NOT NULL,     -- recipient: users.id\n"
+"   sid        int unsigned NOT NULL,     -- sender:    mailaddr.id\n"
+"   wb         char(1) NOT NULL, -- W or Y / B or N / space=neutral\n"
+"   PRIMARY KEY (rid,sid)\n"
+"   );\n"
+"\n"
+"CREATE TABLE policy (\n"
+"   id               int unsigned NOT NULL auto_increment,\n"
+"   policy_name      varchar(32),     -- not used by amavisd-new\n"
+"   virus_lover          char(1),     -- Y/N\n"
+"   spam_lover           char(1),     -- Y/N  (optional field)\n"
+"   banned_files_lover   char(1),     -- Y/N  (optional field)\n"
+"   bad_header_lover     char(1),     -- Y/N  (optional field)\n"
+"   bypass_virus_checks  char(1),     -- Y/N\n"
+"   bypass_spam_checks   char(1),     -- Y/N\n"
+"   bypass_banned_checks char(1),     -- Y/N  (optional field)\n"
+"   bypass_header_checks char(1),     -- Y/N (optional field)\n"
+"   spam_modifies_subj   char(1),     -- Y/N (optional field)\n"
+"   spam_quarantine_to   varchar(64) DEFAULT NULL, -- (optional field)\n"
+"   spam_tag_level  float,  -- higher score inserts spam info headers\n"
+"   spam_tag2_level float DEFAULT NULL,  -- higher score inserts\n"
+"               -- 'declared spam' info header fields\n"
+"   spam_kill_level float,  -- higher score activates evasive actions, e.g.\n"
+"               -- reject/drop, quarantine, ...\n"
+"               -- (subject to final_spam_destiny setting)\n"
+"   PRIMARY KEY (id)\n"
+"  );\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1722
+msgid ""
+"If you have problems using copy/paste you might have to copy this somewhere "
+"else and clean out the unneeded characters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1727
+msgid ""
+"Lookups trying to match email are done with raw (rfc2821-unquoted and "
+"unbracketed) addresses as a key, i.e.: <c>John \"Funny\" Smith@example.com</"
+"c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1733
+msgid ""
+"Lookups are performed in the following order: <c>SQL</c>, <c>LDAP</c>, "
+"<c>hash</c>, <c>ACL</c>, <c>regexp</c>, <c>constant</c>. The first that "
+"returns a definitive answer (not <c>undef/NULL</c>) stops the search."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1739
+msgid ""
+"If you wish to use whitelisting and blacklisting you must add the sender and "
+"receiver to <c>mailadr</c> after which you create the relation between the "
+"two e-mail addresses in <c>wblist</c> and state if it is whitelisting (<c>W</"
+"c>) or blacklisting (<c>B</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1746
+msgid ""
+"Now that we have created the tables let's insert a test user and a test "
+"policy:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1751
+msgid "Create test user and test policy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1751
+#, no-wrap
+msgid ""
+"\n"
+"INSERT INTO users\n"
+"   SET\n"
+"      id         =1,\n"
+"      priority   =9,\n"
+"      policy_id  =1,\n"
+"      email      =\"johndoe@example.com\",\n"
+"      fullname   =\"John Doe\",\n"
+"      local      =\"Y\";\n"
+"\n"
+"INSERT INTO policy\n"
+"   SET\n"
+"      id                     =1,\n"
+"      policy_name            =\"Test policy 1\",\n"
+"      virus_lover            =\"N\",\n"
+"      spam_lover             =\"N\",\n"
+"      banned_files_lover     =\"N\",\n"
+"      bad_header_lover       =\"N\",\n"
+"      bypass_virus_checks    =\"N\",\n"
+"      bypass_spam_checks     =\"N\",\n"
+"      bypass_banned_checks   =\"N\",\n"
+"      bypass_header_checks   =\"N\",\n"
+"      spam_modifies_subj     =\"N\",\n"
+"      spam_quarantine_to     =NULL,\n"
+"      spam_tag_level         =-50.0,\n"
+"      spam_tag2_level        =7.0,\n"
+"      spam_kill_level        =10.0;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1780
+msgid "Copy this to somewhere else and adjust to suit your own environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1784
+msgid ""
+"<c>local</c> should be set to <c>Y</c> otherwise the mail will not be "
+"scanned for spam."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1789
+msgid ""
+"This inserts a test user and a Test policy. Adjust these examples to fit "
+"your needs. Further explanation of the configuration names can be found in "
+"<path>amavisd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1798
+msgid "Configuring amavisd to use MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1801
+msgid "Now that MySQL is ready we need to tell amavis to use it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1805
+#, no-wrap
+msgid ""
+"\n"
+"@lookup_sql_dsn =\n"
+"   ( ['DBI:mysql:maildb:host1', 'mail', 'very_secret_password']  );\n"
+"\n"
+"<comment>(For clarity uncomment the default)</comment>\n"
+"$sql_select_policy = 'SELECT *,users.id FROM users,policy'.\n"
+"   ' WHERE (users.policy_id=policy.id) AND (users.email IN (%k))'.\n"
+"   ' ORDER BY users.priority DESC';\n"
+"\n"
+"<comment>(If you want sender white/blacklisting)</comment>\n"
+"   $sql_select_white_black_list = 'SELECT wb FROM wblist,mailaddr'.\n"
+"     ' WHERE (wblist.rid=?) AND (wblist.sid=mailaddr.id)'.\n"
+"     '   AND (mailaddr.email IN (%k))'.\n"
+"     ' ORDER BY mailaddr.priority DESC';\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1826
+msgid "Configuring Spamassassin to use MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1830
+msgid ""
+"As of Spamassassin 3.0 it is possible to store the Bayes and AWL data in a "
+"MySQL database. We will use MySQL as the backend as it can generally "
+"outperform other databases. Also, using MySQL for both sets of data makes "
+"system management much easier. Here I will show how to easily accomplish "
+"this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1837
+msgid ""
+"First start out by creating the new MySQL user and then create the needed "
+"tables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1842
+msgid "Creating the new MySQL database and user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1842
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mysql -u root -p mysql</i>\n"
+"Enter password:\n"
+"Welcome to the MySQL monitor.  Commands end with ; or \\g.\n"
+"Your MySQL connection id is 78 to server version: 4.0.18-log\n"
+"\n"
+"Type 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n"
+"mysql&gt; <i>create database dbname;</i>\n"
+"mysql&gt; <i>GRANT INSERT,UPDATE,DELETE,SELECT ON dbname.* TO 'dbuser'@'localhost' IDENTIFIED BY 'another_very_secret_password';</i>\n"
+"mysql&gt; <i>use dbname;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1854
+msgid ""
+"Now that the database is created we'll create the necessary tables. You can "
+"cut and paste the following into the mysql prompt:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1859
+#, no-wrap
+msgid ""
+"\n"
+"      CREATE TABLE bayes_expire (\n"
+"          id                    int(11)         NOT NULL default '0',\n"
+"          runtime               int(11)         NOT NULL default '0',\n"
+"          KEY bayes_expire_idx1 (id)\n"
+"          ) TYPE=MyISAM;\n"
+"\n"
+"      CREATE TABLE bayes_global_vars (\n"
+"          variable              varchar(30)     NOT NULL default '',\n"
+"          value                 varchar(200)    NOT NULL default '',\n"
+"          PRIMARY KEY           (variable)\n"
+"          ) TYPE=MyISAM;\n"
+"\n"
+"      INSERT INTO bayes_global_vars VALUES ('VERSION','3');\n"
+"\n"
+"      CREATE TABLE bayes_seen (\n"
+"          id                    int(11)         NOT NULL default '0',\n"
+"          msgid                 varchar(200) binary NOT NULL default '',\n"
+"          flag                  char(1)         NOT NULL default '',\n"
+"          PRIMARY KEY           (id,msgid)\n"
+"          ) TYPE=MyISAM;\n"
+"\n"
+"      CREATE TABLE bayes_token (\n"
+"          id                    int(11)         NOT NULL default '0',\n"
+"          token                 char(5)         NOT NULL default '',\n"
+"          spam_count            int(11)         NOT NULL default '0',\n"
+"          ham_count             int(11)         NOT NULL default '0',\n"
+"          atime                 int(11)         NOT NULL default '0',\n"
+"          PRIMARY KEY           (id, token),\n"
+"          INDEX (id, atime)\n"
+"          ) TYPE=MyISAM;\n"
+"\n"
+"      CREATE TABLE bayes_vars (\n"
+"          id                    int(11)         NOT NULL AUTO_INCREMENT,\n"
+"          username              varchar(200)    NOT NULL default '',\n"
+"          spam_count            int(11)         NOT NULL default '0',\n"
+"          ham_count             int(11)         NOT NULL default '0',\n"
+"          token_count           int(11)         NOT NULL default '0',\n"
+"          last_expire           int(11)         NOT NULL default '0',\n"
+"          last_atime_delta      int(11)         NOT NULL default '0',\n"
+"          last_expire_reduce    int(11)         NOT NULL default '0',\n"
+"          oldest_token_age      int(11)         NOT NULL default '2147483647',\n"
+"          newest_token_age      int(11)         NOT NULL default '0',\n"
+"          PRIMARY KEY           (id),\n"
+"          UNIQUE bayes_vars_idx1 (username)\n"
+"          ) TYPE=MyISAM;\n"
+"\n"
+"      CREATE TABLE awl (\n"
+"          username              varchar(100)    NOT NULL default '',\n"
+"          email                 varchar(200)    NOT NULL default '',\n"
+"          ip                    varchar(10)     NOT NULL default '',\n"
+"          count                 int(11)         default '0',\n"
+"          totscore              float           default '0',\n"
+"          PRIMARY KEY           (username,email,ip)\n"
+"          ) TYPE=MyISAM;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(impo):1916
+msgid "The <c>INSERT</c> line is needed otherwise Spamassassin will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1921
+msgid ""
+"This is also available in the source tarball in the files <path>awl_mysql."
+"sql</path> and <path>bayes_mysql.sql</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1929
+msgid "Configuring Spamassassin to use the MySQL backend"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1932
+msgid ""
+"If you have an old Bayes database in the DBM database and want to keep it "
+"follow these instructions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1937
+msgid "Converting Bayes data from a DBM Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1944
+msgid ""
+"Note that the last step should only be performed after the MySQL database "
+"and <path>secrets.cf</path> have been updated."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1949
+msgid "Now give Spamassassin the required info:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1953
+msgid "Modifying /etc/mail/spamassassin/secrets.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1953
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Tell Spamassassin to use MySQL for bayes data</comment>\n"
+"bayes_store_module              Mail::SpamAssassin::BayesStore::SQL\n"
+"bayes_sql_dsn                   DBI:mysql:sa_bayes:localhost:3306\n"
+"bayes_sql_username              db_name\n"
+"bayes_sql_password              another_very_secret_password\n"
+"\n"
+"<comment>(Tell Spamassassin to use MySQL for AWL data</comment>\n"
+"auto_whitelist_factory          Mail::SpamAssassin::SQLBasedAddrList\n"
+"user_awl_dsn                    DBI:mysql:sa_bayes:localhost:3306\n"
+"user_awl_sql_username           db_name\n"
+"user_awl_sql_password           another_very_secret_password\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1967
+msgid "Next, change its permissions for proper security:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre:caption):1971
+msgid "Changing permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(pre):1971
+#, no-wrap
+msgid ""
+"\n"
+"# <i>chmod 400 /etc/mail/spamassassin/secrets.cf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):1975
+msgid ""
+"To create a very secret password use <c>emerge app-admin/makepasswd</c> and "
+"<c>makepasswd -chars=8</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1980
+msgid "Now all you have to do is <c>/etc/init.d/amavisd restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1989
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):1991
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2100
+msgid "Amavisd-new"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):1994
+msgid ""
+"To troubleshoot Amavisd-new start out by stopping it with <c>/etc/init.d/"
+"amavisd stop</c> and then start it manually in the foreground with "
+"<c>amavisd debug</c> and watch it for anomalies in the output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2003
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2099
+msgid "Spamassassin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):2006
+msgid ""
+"To troubleshoot Spamassassin you can filter an email through it with "
+"<c>spamassassin -D &lt; mail</c>. To ensure that the headers are intact you "
+"can move it from another machine with IMAP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(note):2012
+msgid ""
+"If you need to troubleshoot you have to enable login for the user <c>amavis</"
+"c> by changing the login shell in <path>/etc/passwd</path> to <path>/bin/"
+"bash</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):2018
+msgid ""
+"If you want you can make get the same information and more with Amavisd-new "
+"using <c>amavisd debug-sa</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2026
+msgid "Getting help"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):2029
+msgid ""
+"If you need help a good place to go is the amavis-user mailing list. Before "
+"postting a question try searching the <uri link=\"http://marc.theaimsgroup."
+"com/?l=amavis-user\">Amavis User mailing list archives</uri>. If you find no "
+"answer here you can subscribe to the <uri link=\"https://lists.sourceforge."
+"net/lists/listinfo/amavis-user\">Amavis User mailing list</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(p):2039
+msgid ""
+"If your question is specific to SpamAssassin, DCC, Razor, or Postfix, please "
+"refer to their respective home pages listed below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2049
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2051
+msgid "For further information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2056
+msgid "http://www.ijs.si/software/amavisd/INSTALL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2056
+msgid "Amavisd-new INSTALL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2060
+msgid "http://www.ijs.si/software/amavisd/README.postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2060
+msgid "Amavisd-new Postfix README"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2064
+msgid "http://www.ijs.si/software/amavisd/amavisd-new-docs.html#pbanks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2064
+msgid "Amavisd-new Policy bank documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2068
+msgid "http://spamassassin.apache.org/full/3.0.x/dist/sql/README"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2068
+msgid "Spamassassin SQL README"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2072
+msgid "http://www.greylisting.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2075
+msgid "http://www.postfix.org/FILTER_README.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2075
+msgid "Postfix SMTPD_POLICY_README"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2079
+msgid "http://www.unixwiz.net/techtips/postfix-HELO.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2079
+msgid "Blocking spammers with Postfix HELO controls"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2083
+msgid "http://www.linuxjournal.com/article.php?sid=7327"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2083
+msgid "SPF Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2087
+msgid "http://jimsun.linxnet.com/misc/postfix-anti-UCE.txt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2087
+msgid "Jim Seymour's Postfix Anti-UCE Cheat Sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2095
+msgid "General resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2099
+msgid "http://www.spamassassin.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2100
+msgid "http://www.ijs.si/software/amavisd/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2102
+msgid "http://www.ijs.si/software/amavisd/amavisd-new-docs.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2102
+msgid "Amavisd-new documentation bits and pieces"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2105
+msgid "http://razor.sourceforge.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2105
+msgid "Vipuls's Razor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2106
+msgid "http://pyzor.sourceforge.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2108
+msgid "http://www.rhyolite.com/anti-spam/dcc/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2108
+msgid "Distributed Checksum Clearinghouse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2112
+msgid "http://www.renaissoft.com/projects/maia/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2112
+msgid "Maia Mailguard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(title):2120
+msgid "Other howtos"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri:link):2125
+msgid "http://www.flakshack.com/anti-spam/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(uri):2125
+msgid ""
+"Fairly-Secure Anti-SPAM Gateway Using OpenBSD, Postfix, Amavisd-new, "
+"SpamAssassin, Razor and DCC"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mailfilter-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/man-guide.xml.po b/doc/gettext/ru/man-guide.xml.po
new file mode 100644
index 0000000..218279e
--- /dev/null
+++ b/doc/gettext/ru/man-guide.xml.po
@@ -0,0 +1,602 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(guide:link):5
+msgid "/doc/en/man-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):6
+msgid "Gentoo Man Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(abstract):12
+msgid "This guide shows how to navigate man pages using man."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(version):20
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(date):21
+msgid "2006-06-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):26
+msgid "The man program"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):29
+msgid ""
+"Everyone at some point in their linux life has used it. \"It\" is the "
+"<c>man</c> command. However, while the man program itself appears to be "
+"rather simplistic in its construct, it has a few extra abilities than just "
+"simply scrolling through the page. This document hopes to help shed some "
+"light on these capabilities."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):40
+msgid "Man layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):43
+msgid ""
+"Man pages are mainly stored in the <path>/usr/share/man</path> directory. "
+"However, as long as a man page is located in the <c>MANPATH</c> environment "
+"variable, man will be able to pick it up. Gentoo will generally store "
+"<c>MANPATH</c> variables in <path>/etc/env.d</path>. Within these "
+"directories are some folders with the structure manX where X is the section "
+"number. For example, a standard man layout might look like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):52
+msgid "Standard man structure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):52
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>ls /usr/share/man | grep man</i>\n"
+"man0p\n"
+"man1\n"
+"man1p\n"
+"man2\n"
+"man3\n"
+"man3p\n"
+"man4\n"
+"man5\n"
+"man6\n"
+"man7\n"
+"man8\n"
+"man9\n"
+"mann\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):69
+msgid ""
+"The actual section numbering appears fairly standard. However, notice that "
+"there is a <path>mann</path> and some <path>man#p</path> folders. The "
+"following table lists the above man page directories and what is contained "
+"within them:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(th):77
+msgid "Man Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(th):78
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):81
+msgid "man0p"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):82
+msgid ""
+"The <c>p</c> here stands for POSIX, as with the other directories with p in "
+"their names. Man pages in this directory describe the functionality of "
+"various POSIX header files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):89
+msgid "man1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):90
+msgid ""
+"This section is for standard commands. Most programs will put their man "
+"pages here, so this section tends to be the largest."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):96
+msgid "man1p"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):97
+msgid ""
+"This section describes the POSIX versions of the commands described in 1p. "
+"Since it only describes basic commands, it is much smaller than man1."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):103
+msgid "man2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):104
+msgid "This section describes Linux kernel system calls."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):107
+msgid "man3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):108
+msgid "This section describes standard c library functions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):111
+msgid "man4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):112
+msgid ""
+"This section describes special devices. These devices are generally kernel "
+"oriented, but <c>Xorg-X11</c> has entries in here as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):118
+msgid "man5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):119
+msgid ""
+"This section describes both the makeup of certain files and what files a "
+"program uses. Those of you reading this document may be familiar with "
+"references to <c>man 5 portage</c> for a description of the <c>portage</c> "
+"file structure, and <c>man 5 make.conf</c> for <path>make.conf</path> makeup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):128
+msgid "man6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):129
+msgid "This section introduces games and other special toys."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):132
+msgid "man7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):133
+msgid ""
+"This section describes standards and other miscellaneous items. These "
+"standards can include things such as charsets, SQL statements, ISO standards "
+"and regular expressions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):140
+msgid "man8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):141
+msgid ""
+"This section describes administrative commands (those usually run by the "
+"root user)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):147
+msgid "man9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):148
+msgid ""
+"This section is somewhat sparse, but is meant to contain documentation for "
+"various parts of the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):154
+msgid "mann"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(ti):155
+msgid ""
+"This section is mainly used by <c>Tcl/Tk</c>. The <c>n</c> stands for new."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):161
+msgid ""
+"While this is not an extensive and detailed list, it does cover the man "
+"pages that most people will be interested in. However, sometimes you can "
+"find out what a section does as easily as looking at this table. The next "
+"chapter will look at using man to traverse this layout."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):173
+msgid "Working with the man layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):175
+msgid "Browsing the man layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):178
+msgid ""
+"Now that we understand the man layout, we can begin to look it over for "
+"commands. Sometimes we may need to narrow down what man page we want. The "
+"first way would be addressing by section. To found out a description of a "
+"section, once can use <c>man section intro</c> like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):185
+msgid "Using man intro to describe a section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):185
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>man 3 intro</i>\n"
+"<comment>(Output slightly modified to fit the document properly)</comment>\n"
+"INTRO(3)               Linux Programmer's Manual                INTRO(3)\n"
+"\n"
+"\n"
+"\n"
+"NAME\n"
+"       intro - Introduction to library functions\n"
+"\n"
+"DESCRIPTION\n"
+"       This chapter describes all library functions excluding the library\n"
+"       functions described in chapter 2, which implement system calls.\n"
+"       There are various function groups which can be identified by a\n"
+"       letter which is appended to the chapter number:\n"
+"....\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):203
+msgid ""
+"Unfortunately, this doesn't always work! However, luckily for us there is "
+"another way to search for commands that may return multiple results (such as "
+"a library call and system command having the same name). To do so, we use "
+"the <c>-K</c> parameter to man like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):210
+msgid "Using man -K to search by string"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):210
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>man -K sleep</i>\n"
+"/usr/share/man/man0p/time.h.0p.gz? [ynq] <i>n</i>\n"
+"/usr/share/man/man0p/unistd.h.0p.gz? [ynq] <i>n</i>\n"
+"/usr/share/man/man2/alarm.2.gz? [ynq] <i>n</i>\n"
+"/usr/share/man/man2/pause.2.gz? [ynq] <i>n</i>\n"
+"/usr/share/man/man2/futex.2.gz? [ynq] <i>n</i>\n"
+"/usr/share/man/man2/nanosleep.2.gz? [ynq] <i>y</i>\n"
+"/usr/share/man/man2/semop.2.gz? [ynq] <i>q</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):221
+msgid ""
+"Sometimes the output may be a lot larger. In this case it might be better to "
+"specify more specific keywords. Now that we know where to find the man page, "
+"the next section will look at viewing the man page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):230
+msgid "Viewing man pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):233
+msgid ""
+"Viewing man pages can be done in 2 ways, first is with <c>man [man page name]"
+"</c>. The second way is <c>man [section] [man page name]</c>. Let's take "
+"<c>bc</c> for example. I can view either the first man page that comes up on "
+"<c>bc</c> (which would be section 1, because it is the lowest section "
+"containing a man page on <c>bc</c>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):241
+msgid "Viewing the default man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):241
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>man bc</i>\n"
+"bc(1)                                            bc(1)\n"
+"\n"
+"\n"
+"NAME\n"
+"       bc - An arbitrary precision calculator language\n"
+"...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):251
+msgid ""
+"However, what if I want the POSIX version? Then I can use the second form:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):255
+msgid "Viewing a specific man page by section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):255
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>man 1p bc</i>\n"
+"BC(P)        POSIX Programmer's Manual           BC(P)\n"
+"\n"
+"\n"
+"NAME\n"
+"       bc - arbitrary-precision arithmetic language\n"
+"...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):265
+msgid ""
+"And the man page is displayed. Now that we have the man page up, it's time "
+"to work with it. The next section will look at navigation and searching."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):273
+msgid "Navigating and searching man pages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):276
+msgid ""
+"Navigating a man page is fairly simple. To move up and down line by line, "
+"use the up and down arrow keys. To move up page by page, you can use the "
+"page up and page down keys. Do however note that these navigation "
+"instructions assume the environmental <c>PAGER</c> variable is set to use "
+"the default pager, <c>less</c>. Less also has a few other commands for "
+"navigation, but the arrow keys usually suffice:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):285
+msgid "Additional less navigation keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):285
+#, no-wrap
+msgid ""
+"\n"
+"  e  ^E  j  ^N  CR  *  Forward  one line   (or N lines).\n"
+"  y  ^Y  k  ^K  ^P  *  Backward one line   (or N lines).\n"
+"  f  ^F  ^V  SPACE  *  Forward  one window (or N lines).\n"
+"  b  ^B  ESC-v      *  Backward one window (or N lines).\n"
+"  z                 *  Forward  one window (and set window to N).\n"
+"  w                 *  Backward one window (and set window to N).\n"
+"  ESC-SPACE         *  Forward  one window, but don't stop at end-of-file.\n"
+"  d  ^D             *  Forward  one half-window (and set half-window to N).\n"
+"  u  ^U             *  Backward one half-window (and set half-window to N).\n"
+"  ESC-)  RightArrow *  Left  one half screen width (or N positions).\n"
+"  ESC-(  LeftArrow  *  Right one half screen width (or N positions).\n"
+"  F                    Forward forever; like \"tail -f\".\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):300
+msgid ""
+"Searching, however, is more interesting. The two most basic searches are <c>/"
+"pattern</c> and <c>?pattern</c>. The first version searches forwards, and "
+"the second searches backwards. <c>pattern</c> is a regular expression "
+"pattern that is described in <c>man 7 regex</c>. Let's take for example "
+"searching for the <c>-D</c> option to <c>emerge</c>. First, bring up the "
+"emerge man page:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):308
+msgid "Bringing up the emerge man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):308
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>man emerge</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):312
+msgid ""
+"Then, at the screen, press the <c>/</c> key to bring up the entry prompt to "
+"search forwards and enter in our search pattern:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):317
+msgid "Bringing up the forward search prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):317
+#, no-wrap
+msgid ""
+"\n"
+"     gracefully handles updating installed packages to newer releases as well.\n"
+"     It handles both source and binary packages, and it can be used to create\n"
+"     binary packages for distribution.\n"
+"\n"
+"EBUILDS, TBZ2S, CLASSES AND DEPENDENCIES\n"
+"/<i>\\-D</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(note):326
+msgid ""
+"The <c>\\</c> is done to escape the <c>-</c> sign, which would normally be "
+"used as part of a regular expression."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):331
+msgid "This will search the man page, and bring the searched item into focus:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):335
+msgid "Forward search results"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):335
+#, no-wrap
+msgid ""
+"\n"
+"  --deep (-D)\n"
+"        When used in conjunction with --update, this flag forces emerge to consider the entire\n"
+"        dependency tree of packages, instead of checking only the immediate dependencies of\n"
+"        the packages.  As an example, this catches updates in libraries that are not directly\n"
+"        listed in the  dependencies of a package.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):343
+msgid ""
+"If you hit a search result by accident and want to continue searching for "
+"the same results, simply press the <c>/</c> key again, and press enter (i.e. "
+"don't put a pattern it). This will cause the search to default to the last "
+"pattern used. Now with some man pages, options are listed, then explained "
+"later on. Take the <c>man 5 portage</c> man page. It lists the files used, "
+"then explains their usage. Searching forward a few times would return the "
+"results, but there's an easier way to handle this, with the second search "
+"form, backwards searching. Let's use this to find the description on "
+"<path>package.unmask</path>. First, bring up <c>man 5 portage</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):355
+msgid "Bringing up the man 5 portage man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):355
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>man 5 portage</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):359
+msgid "Now press <c>SHIFT+g</c>. This will bring you to the end of the page:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):363
+msgid "End of the man page after SHIFT+g"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):363
+#, no-wrap
+msgid ""
+"\n"
+"SEE ALSO\n"
+"       emerge(1), ebuild(1), ebuild(5), make.conf(5)\n"
+"\n"
+"Portage 2.0.51        Jan 2004            PORTAGE(5)\n"
+"lines 418-442/442 (END)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):371
+msgid ""
+"Now we'll go ahead and enter the pattern to search for with the <c>?pattern</"
+"c> backwards search option. First press the <c>?</c> key to bring up the "
+"prompt, and then enter in <c>package.unmask</c>, our query:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):377
+msgid "Specifying our search"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):377
+#, no-wrap
+msgid ""
+"\n"
+"SEE ALSO\n"
+"       emerge(1), ebuild(1), ebuild(5), make.conf(5)\n"
+"\n"
+"Portage 2.0.51        Jan 2004           PORTAGE(5)\n"
+"?<i>package.unmask</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):385
+msgid "Then hit enter to bring up the result:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre:caption):389
+msgid "Our search result"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(pre):389
+#, no-wrap
+msgid ""
+"\n"
+"  package.unmask\n"
+"       Just like package.mask above, except here you list packages you want to unmask.\n"
+"       Useful for overriding the global  package.mask  file (see below).  Note that\n"
+"       this does not override packages that are masked via KEYWORDS.\n"
+"...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):397
+msgid ""
+"And the search is complete! Note that just as with <c>/</c>, using <c>?</c> "
+"search with no pattern will use the last pattern to search."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(title):405
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):408
+msgid ""
+"This concludes the man guide. This will hopefully shed some light on "
+"navigating man pages, and maybe even give a few new tips to the more "
+"experienced users. For those who prefer alternate means of navigating man "
+"pages, the following are also available:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(li):416
+msgid "app-text/man2html - a program for converting man pages to html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(li):417
+msgid "app-text/tkman - a tk based man page browser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(p):420
+msgid ""
+"Also the <c>KDE</c> web browser <c>Konqueror</c> can browse man pages using "
+"the <c>man:</c> syntax in the address bar."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//man-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/management-structure.xml.po b/doc/gettext/ru/management-structure.xml.po
new file mode 100644
index 0000000..843a6b8
--- /dev/null
+++ b/doc/gettext/ru/management-structure.xml.po
@@ -0,0 +1,400 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(guide:link):5
+msgid "/doc/en/management-structure.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):6
+msgid "Gentoo Top-Level Management Structure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(mail:link):9
+msgid "drobbins@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(mail):9
+msgid "Daniel Robbins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(mail:link):12
+msgid "pauldv@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(mail):12
+msgid "Paul de Vrieze"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(abstract):16
+msgid "Gentoo top-level management structure (work in progress)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(version):22
+msgid "1.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(date):23
+msgid "2003-07-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):27
+msgid "Gentoo top-level management structure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(brite):33
+msgid ""
+"As of May 2005, this document is no longer valid but kept for historical "
+"purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):40
+msgid "What was the purpose of the new management structure?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):43
+msgid ""
+"The purpose of the new management structure was to solve chronic management, "
+"coordination and communication issues in the Gentoo project. In particular, "
+"we had no clearly defined top-level management structure, and no official, "
+"regular meetings to communicate status updates between developers serving in "
+"critical roles. In general, most communication took place on irc and "
+"irregularly via email. There was also little to no accountability, even at a "
+"high level, to complete projects on time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):53
+msgid ""
+"Because of this prior state of affairs, it was difficult to set goals and "
+"track the status of projects. This lack of communication and coordination "
+"also made it difficult for top-level developers to manage their own "
+"projects. In addition, we had other chronic problem of not having clearly-"
+"defined roles and scopes of executive decision-making authority for top-"
+"level developers, which resulted in many top-level developers doubting that "
+"they even have the authority to manage their own projects and sub-projects. "
+"While this had *never* been the intention of top-level developers, it is the "
+"unfortunate result of an unstructured development process: no one knew what "
+"was going on, and everyone deferred to the Chief Architect for all executive "
+"decisions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):67
+msgid ""
+"Clearly, a plan was needed to swiftly and permanently address these issues "
+"by increasing communication, coordination, and accountability. Roles and "
+"scopes of executive decision-making authority needed to be defined for top "
+"developers so that they have a clear mandate as well as accountability to "
+"manage their projects and thus ensure their projects completed their "
+"appointed work efficiently and on-schedule."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):79
+msgid "Initial implementation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):82
+msgid ""
+"Initial implementation of the new management structure began by creating "
+"official top-level management structure. This management structure consists "
+"of the Chief Architect and a group of developers that will be given the "
+"title of Top-level Managers. Top-level Managers will be accountable for the "
+"projects they manage, and be responsible for communicating the status of "
+"their projects to the rest of the Top-level Managers and Chief Architect, as "
+"well as other responsibilities detailed later in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):92
+msgid ""
+"All the top-level projects in the Gentoo project are in the process of being "
+"clearly defined, including goals, sub-projects, members, roadmap and "
+"schedules. The \"Hardened Gentoo\" page at <uri>http://www.gentoo.org/proj/"
+"en/hardened/</uri> is an excellent example of such a top-level project "
+"definition, and many other top-level projects currently exist today."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):101
+msgid ""
+"Certain executive decision-making authority will be granted to these "
+"projects, as agreed upon by the Chief Architect, Top-level Managers and "
+"project members. Then, as part of the initial implementation of the new "
+"management structure, a Top-level Manager or managers will be officially "
+"adopt projects and ebuild herds. These managers will be responsible for "
+"tracking the status of the project, ensuring that the project meets targets "
+"and is generally managed properly. Manager responsibilities are described in "
+"detail later in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):115
+msgid "Management team"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):118
+msgid ""
+"The current top-level management team is as follows (in no particular order):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):123
+msgid "Seemant Kulleen (seemant)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):124
+msgid "Jay Pfeifer (pfeifer)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):125
+msgid "Joshua Brindle (method)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):126
+msgid "Kurt Lieber (klieber)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):127
+msgid "Pieter Van den Abeele (pvdabeel)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):128
+msgid "Jon Portnoy (avenj)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):129
+msgid "Paul de Vrieze (pauldv)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):130
+msgid "Sven Vermeulen (swift)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):136
+msgid "Management charter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):139
+msgid ""
+"1) Constructive, professional communication: All communication should be "
+"focused on improving the management of Gentoo projects, should be "
+"constructive in nature and should be shared in a friendly, professional "
+"manner."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):146
+msgid ""
+"2) Accountability to peers: Allow fellow members of this list to hold us "
+"accountable to follow-through on projects and meet deadlines. Keep fellow "
+"members accountable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):152
+msgid ""
+"3) Management of projects: empower managers to have the authority and "
+"strategic direction necessary to properly manage thier projects and efforts "
+"to ensure projects complete their appointed work on time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):158
+msgid ""
+"4) Results: our expectation is that our efforts, when properly executed, "
+"will result in the Gentoo project's ability to meet deadlines, have much "
+"better communication and coordination throughout the entire project, higher "
+"overall quality and a more positive experience for all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):168
+msgid "Manager responsibilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):171
+msgid ""
+"Every top-level Gentoo project will have a clearly defined scope, and "
+"clearly defined and explicit executive decision-making authority that will "
+"be granted to managers of the project to exercise and/or delegate as they "
+"see fit. Both the scope and any necessary decision-making authority must be "
+"agreed upon by both the Chief Architect and project members. The scope and "
+"executive authority of a project can be expanded over time as required as "
+"approved by the Top-level Managers and Chief Architect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):181
+msgid ""
+"In addition to decision-making authority, managers have the following "
+"responsibilities:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):187
+msgid ""
+"Keep a complete list of all projects and efforts you are managing, and "
+"associated gentoo.org project page up-to-date"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):192
+msgid ""
+"Manage and track the status of these efforts. This includes active direction "
+"as well as passive tracking of progress."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):197
+msgid ""
+"Define clear goals, roadmaps and timelines (preliminary if necessary) for "
+"every effort."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):202
+msgid "Proactively identify efforts that have problems and need help."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):204
+msgid ""
+"Ensure that your efforts are completed on-time, or that any efforts that are "
+"behind-schedule are reported in a timely manner."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):209
+msgid ""
+"Remain focused. Make sure that you are not managing more than you can handle."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):214
+msgid ""
+"Fulfill formal communication and coordination responsibilities required by "
+"top-level managers (weekly meetings, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):219
+msgid ""
+"Fulfill formal communication and coordination responsibilities required by "
+"individual efforts (project meetings, communication with project members, "
+"etc.) This is important as our management of projects means that we have the "
+"responsibility not only to communicate with our peers but also those who we "
+"are managing. This communication should be frequent, have a formal component "
+"(planned meetings, official status updates, etc.) and model good management "
+"practices to members of our teams."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(li):229
+msgid ""
+"<b>RECURSIVE FUNCTIONALITY</b>: At an appropriate time, implement these "
+"management practices for *sub*-projects (define managers, clear sub-project "
+"goals, grant executive authority) with you serving as primary authority."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):239
+msgid "Meetings, logs and status updates"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):242
+msgid ""
+"Currently, weekly manager meetings are held on irc, and all Gentoo "
+"developers are welcome to join the meeting channel and view the meeting in "
+"progress. In addition, after the meeting completes, the floor is opened for "
+"questions and comments by developers. The weekly meetings generally take "
+"place on Monday. After the meeting and open-floor session is concluded, a "
+"log of the meeting is posted to the gentoo-core mailing list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):251
+msgid ""
+"Status updates are very important to the proper functioning of our "
+"management structure. Currently, managers make an effort to email each other "
+"weekly status updates. Soon, we hope to post weekly status updates to our "
+"respective project pages so that the public can be apprised on the status of "
+"every top-level project."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(note):259
+msgid ""
+"Inability to attend due to time zone can be addressed by posting the full "
+"IRC log to gentoo-managers and allowing non-attending members to post ideas, "
+"comments and follow-ups."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):268
+msgid "Decision-making"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):271
+msgid ""
+"Currently, GLEPs (Gentoo Linux Enhancement Proposals) can be approved or "
+"rejected by the appropriate top-level manager under which the GLEP falls. If "
+"there is no clearly-defined manager under which the GLEP falls, the GLEP "
+"will be voted upon by the Managers and Chief Architect, and must be approved "
+"unanimously. In all cases, a public, written explanation must be provided "
+"detailing why the GLEP was approved or rejected, either by the manager who "
+"approved/rejected it, or the head of the GLEP sub-project (Grant Goodyear) "
+"if the GLEP was voted upon by the management team. This summary is meant to "
+"reflect the decision that was made by some of the managers at an early "
+"manager meeting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):283
+msgid ""
+"Currently, there is no formal general voting procedure in place. In the "
+"interim, any item to be voted upon must be approved by \"votable\" by the "
+"Chief Architect. Before voting takes place, all managers must have an "
+"opportunity to present their ideas before the other managers, with the "
+"general originator(s) of the idea having the opportunity to present first. "
+"After that, the Chief Architect and Managers can present their ideas, with "
+"the Chief Architect having the opportunity to present last. After this has "
+"happened, voting can take place, and the item will be approved on an "
+"unanimous vote. Managers or the Chief Architect can choose to abstain from "
+"voting, and the vote can still pass with abstainers as long as at least 50% "
+"of the members have voted. The voting must take place at an official "
+"managers meeting. Non-attending managers are allowed to vote via email. The "
+"vote must be officially tallied and posted to the managers list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):298
+msgid ""
+"The reason for the \"Chief Architect approval\" clause it to prevent the "
+"voting process from being abused by allowing voting items that make no "
+"sense, such as those that begin with a \"Should we continue to,\" where a "
+"\"nay\" result would result in a change in existing policy, as well as "
+"preventing managers for requesting that every small decision be voted upon. "
+"We currently have no clear policy to determine what is a \"votable\" item, "
+"and without this policy there needs to be some method to determine what is "
+"\"votable\" and what affects some immutable part of Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):309
+msgid ""
+"This section is subject to additional clarification and refinement in the "
+"future, as is the rest of this document. The purpose of this section is to "
+"document our currently-existing procedures rather than define ideal or "
+"\"final\" procedures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(title):319
+msgid "Top-level projects"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(p):323
+msgid ""
+"It is the responsibility of the <uri link=\"/proj/en/metastructure/"
+"\">metastructure</uri> top-level project to officially document and get "
+"changes approved to our management structure. The <uri link=\"/proj/en/"
+"metastructure/projects.xml\">official top-level project list</uri> can be "
+"viewed, and can be expected to change/expand slightly at the new management "
+"structure is implemented."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//management-structure.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/metadoc.xml.po b/doc/gettext/ru/metadoc.xml.po
new file mode 100644
index 0000000..f34f10f
--- /dev/null
+++ b/doc/gettext/ru/metadoc.xml.po
@@ -0,0 +1,1874 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(metadoc:lang):4
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(version):5
+msgid "1.155"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(lead):7
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):8
+msgid "cam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):9
+msgid "flammie"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):10
+msgid "fox2mike"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):11
+msgid "jkt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):13
+msgid "rane"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(member):14
+msgid "vanquirius"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):17
+msgid "Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):18
+msgid "Installation Related Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):19
+msgid "Installation Guides"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):20
+msgid "Other Installation Related Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):21
+msgid "Upgrade Guides"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):22
+msgid "Gentoo System Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):23
+msgid "Published Articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):24
+msgid "Portage and Related Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):25
+msgid "Configuring Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):26
+msgid "Gentoo Choices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):27
+msgid "Gentoo Articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):28
+msgid "Learning Linux Articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):29
+msgid "DeveloperWorks Common Threads"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):30
+msgid "Miscellaneous Articles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):31
+msgid "System Administration Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):32
+msgid "General System Administration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):33
+msgid "Specific Administration Guides"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):34
+msgid "Gentoo Development Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):35
+msgid "Gentoo Development Policies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):36
+msgid "Development Related Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):37
+msgid "Gentoo Desktop Documentation Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):38
+msgid "Installing your Desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):39
+msgid "Configuring your Desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):40
+msgid "Application Specific Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):41
+msgid "Other Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):42
+msgid "Project Specific Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):43
+msgid "Base Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):44
+msgid "Developer Relations Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):45
+msgid "Documentation Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):46
+msgid "Hardened Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):47
+msgid "Infrastructure Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):48
+msgid "Metastructure Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):49
+msgid "Public Relations Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):50
+msgid "Release Engineering Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):51
+msgid "Security Project Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):52
+msgid "Gentoo Forums Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(cat):53
+msgid "Gentoo Overlays Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):56
+msgid "/doc/en/metadoc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):57
+msgid "/doc/en/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):58
+msgid "/doc/en/list.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):59
+msgid "/doc/en/overview.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):60
+msgid "/doc/en/doc-languages.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):61
+msgid "/doc/en/inserts.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):62
+msgid "/main/en/name-logo.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):63
+msgid "/doc/en/articles/prompt-magic.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):64
+msgid "/doc/en/articles/bash-by-example-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):65
+msgid "/doc/en/articles/bash-by-example-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):66
+msgid "/doc/en/articles/bash-by-example-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):67
+msgid "/doc/en/articles/making-the-distro-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):68
+msgid "/doc/en/articles/making-the-distro-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):69
+msgid "/doc/en/articles/making-the-distro-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):70
+msgid "/doc/en/articles/lpi-101-fundamentals-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):71
+msgid "/doc/en/articles/lpi-101-administration-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):72
+msgid "/doc/en/articles/lpi-101-intermediate-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):73
+msgid "/doc/en/articles/lpi-101-advanced-p4.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):74
+msgid "/doc/en/articles/dynamic-iptables-firewalls.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):75
+msgid "/doc/en/articles/l-sed1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):76
+msgid "/doc/en/articles/l-sed2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):77
+msgid "/doc/en/articles/l-sed3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):78
+msgid "/doc/en/articles/l-awk1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):79
+msgid "/doc/en/articles/l-awk2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):80
+msgid "/doc/en/articles/l-awk3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):81
+msgid "/doc/en/articles/l-posix1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):82
+msgid "/doc/en/articles/l-posix2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):83
+msgid "/doc/en/articles/l-posix3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):84
+msgid "/doc/en/articles/linux-24-stateful-fw-design.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):85
+msgid "/doc/en/articles/afig-ct-ext3-intro.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):86
+msgid "/doc/en/articles/hardware-stability-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):87
+msgid "/doc/en/articles/hardware-stability-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):88
+msgid "/doc/en/articles/partitioning-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):89
+msgid "/doc/en/articles/partitioning-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):90
+msgid "/doc/en/articles/partition-planning-tips.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):91
+msgid "/doc/en/articles/maximum-swappage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):92
+msgid "/doc/en/articles/lvm-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):93
+msgid "/doc/en/articles/lvm-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):94
+msgid "/doc/en/articles/software-raid-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):95
+msgid "/doc/en/articles/software-raid-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):96
+msgid "/doc/en/articles/linux-kernel-compiling.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):97
+msgid "/doc/en/articles/openssh-key-management-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):98
+msgid "/doc/en/articles/openssh-key-management-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):99
+msgid "/doc/en/articles/openssh-key-management-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):100
+msgid "/doc/en/articles/l-afig-p8.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):101
+msgid "/doc/en/articles/samba-p1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):102
+msgid "/doc/en/articles/samba-p2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):103
+msgid "/doc/en/articles/samba-p3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):104
+msgid "/doc/en/articles/l-redesign-1.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):105
+msgid "/doc/en/articles/l-redesign-2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):106
+msgid "/doc/en/articles/l-redesign-3.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):107
+msgid "/doc/en/articles/l-redesign-4.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):108
+msgid "/doc/en/articles/autotools-practices.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):109
+msgid "/doc/en/bugzilla-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):110
+msgid "/doc/en/mysql-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):111
+msgid "/doc/en/postgres-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):112
+msgid "/doc/en/bluetooth-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):113
+msgid "/doc/en/utf-8.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):114
+msgid "/doc/en/cron-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):115
+msgid "/doc/en/ldap-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):116
+msgid "/doc/en/nvidia-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):117
+msgid "/doc/en/ati-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):118
+msgid "/doc/en/cvs-tutorial.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):119
+msgid "/doc/en/devfs-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):120
+msgid "/doc/en/distcc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):121
+msgid "/doc/en/cross-compiling-distcc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):122
+msgid "/doc/en/dri-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):123
+msgid "/doc/en/ebuild-submit.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):124
+msgid "/doc/en/gentoo-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):125
+msgid "/doc/en/migration-to-2.6.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):126
+msgid "/doc/en/altinstall.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):127
+msgid "/doc/en/faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):128
+msgid "/doc/en/gentoo-alpha-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):129
+msgid "/doc/en/gentoo-amd64-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):130
+msgid "/doc/en/handbook/handbook-alpha.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):131
+msgid "/doc/en/handbook/handbook-amd64.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):132
+msgid "/doc/en/handbook/handbook-arm.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):133
+msgid "/doc/en/handbook/handbook-hppa.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):134
+msgid "/doc/en/handbook/handbook-ia64.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):135
+msgid "/doc/en/handbook/handbook-mips.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):136
+msgid "/doc/en/handbook/handbook-ppc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):137
+msgid "/doc/en/handbook/handbook-ppc64.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):138
+msgid "/doc/en/handbook/handbook-sparc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):139
+msgid "/doc/en/handbook/handbook-x86.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):140
+msgid "/doc/en/handbook/hb-portage-branches.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):141
+msgid "/doc/en/handbook/hb-install-about.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):142
+msgid "/doc/en/handbook/hb-install-alpha-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):143
+msgid "/doc/en/handbook/hb-install-alpha-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):144
+msgid "/doc/en/handbook/hb-install-alpha-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):145
+msgid "/doc/en/handbook/hb-install-alpha-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):146
+msgid "/doc/en/handbook/hb-install-arm-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):147
+msgid "/doc/en/handbook/hb-install-arm-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):148
+msgid "/doc/en/handbook/hb-install-arm-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):149
+msgid "/doc/en/handbook/hb-install-arm-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):150
+msgid "/doc/en/handbook/hb-install-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):151
+msgid "/doc/en/handbook/hb-install-finalise.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):152
+msgid "/doc/en/handbook/hb-install-hppa-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):153
+msgid "/doc/en/handbook/hb-install-hppa-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):154
+msgid "/doc/en/handbook/hb-install-hppa-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):155
+msgid "/doc/en/handbook/hb-install-hppa-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):156
+msgid "/doc/en/handbook/hb-install-ia64-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):157
+msgid "/doc/en/handbook/hb-install-ia64-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):158
+msgid "/doc/en/handbook/hb-install-ia64-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):159
+msgid "/doc/en/handbook/hb-install-mips-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):160
+msgid "/doc/en/handbook/hb-install-mips-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):161
+msgid "/doc/en/handbook/hb-install-mips-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):162
+msgid "/doc/en/handbook/hb-install-mips-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):163
+msgid "/doc/en/handbook/hb-install-mips-stage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):164
+msgid "/doc/en/handbook/hb-install-mips-system.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):165
+msgid "/doc/en/handbook/hb-install-network.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):166
+msgid "/doc/en/handbook/hb-install-next.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):167
+msgid "/doc/en/handbook/hb-install-ppc-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):168
+msgid "/doc/en/handbook/hb-install-ppc-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):169
+msgid "/doc/en/handbook/hb-install-ppc-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):170
+msgid "/doc/en/handbook/hb-install-ppc-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):171
+msgid "/doc/en/handbook/hb-install-ppc64-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):172
+msgid "/doc/en/handbook/hb-install-ppc64-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):173
+msgid "/doc/en/handbook/hb-install-ppc64-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):174
+msgid "/doc/en/handbook/hb-install-ppc64-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):175
+msgid "/doc/en/handbook/hb-install-sparc-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):176
+msgid "/doc/en/handbook/hb-install-sparc-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):177
+msgid "/doc/en/handbook/hb-install-sparc-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):178
+msgid "/doc/en/handbook/hb-install-sparc-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):179
+msgid "/doc/en/handbook/hb-install-stage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):180
+msgid "/doc/en/handbook/hb-install-tools.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):181
+msgid "/doc/en/handbook/hb-install-x86+amd64-bootloader.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):182
+msgid "/doc/en/handbook/hb-install-x86+amd64-disk.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):183
+msgid "/doc/en/handbook/hb-install-x86+amd64-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):184
+msgid "/doc/en/handbook/hb-install-x86+amd64-medium.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):185
+msgid "/doc/en/handbook/hb-install-blockdevices.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):186
+msgid "/doc/en/handbook/hb-install-bootconfig.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):187
+msgid "/doc/en/handbook/hb-install-filesystems.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):188
+msgid "/doc/en/handbook/hb-install-kernelmodules.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):189
+msgid "/doc/en/handbook/hb-install-kernelparams.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):190
+msgid "/doc/en/handbook/hb-working-features.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):191
+msgid "/doc/en/handbook/hb-working-portage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):192
+msgid "/doc/en/handbook/hb-working-rcscripts.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):193
+msgid "/doc/en/handbook/hb-working-use.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):194
+msgid "/doc/en/handbook/hb-working-variables.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):195
+msgid "/doc/en/handbook/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):196
+msgid "/doc/en/handbook/hb-install-system.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):197
+msgid "/doc/en/handbook/hb-portage-configuration.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):198
+msgid "/doc/en/handbook/hb-portage-diverttree.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):199
+msgid "/doc/en/handbook/hb-portage-files.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):200
+msgid "/doc/en/handbook/hb-portage-tools.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):201
+msgid "/doc/en/handbook/hb-net-advanced.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):202
+msgid "/doc/en/handbook/hb-net-functions.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):203
+msgid "/doc/en/handbook/hb-net-management.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):204
+msgid "/doc/en/handbook/hb-net-modules.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):205
+msgid "/doc/en/handbook/hb-net-start.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):206
+msgid "/doc/en/handbook/hb-net-wireless.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):207
+msgid "/doc/en/lvm2.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):208
+msgid "/doc/en/gentoo-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):209
+msgid "/doc/en/gentoo-ppc-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):210
+msgid "/doc/en/alsa-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):211
+msgid "/doc/en/xorg-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):212
+msgid "/doc/en/quick-samba-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):213
+msgid "/doc/en/ltsp.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):214
+msgid "/doc/en/gentoolkit.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):215
+msgid "/doc/en/gnupg-user.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):216
+msgid "/doc/en/ipv6.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):217
+msgid "/doc/en/guide-localization.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):218
+msgid "/doc/en/guide-to-mutt.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):219
+msgid "/doc/en/uml.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):220
+msgid "/doc/en/java.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):221
+msgid "/doc/en/openafs.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):222
+msgid "/proj/en/desktop/kde/kde4-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):223
+msgid "/doc/en/nano-basics-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):224
+msgid "/doc/en/shoutcast-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):225
+msgid "/doc/en/vdr-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):226
+msgid "/doc/en/xml-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):227
+msgid "/doc/en/diskless-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):228
+msgid "/doc/en/prelink-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):229
+msgid "/doc/en/printing-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):230
+msgid "/doc/en/rsync.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):231
+msgid "/doc/en/qmail-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):232
+msgid "/doc/en/source_mirrors.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):233
+msgid "/doc/en/gentoo-x86-quickinstall.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):234
+msgid "/doc/en/gentoo-x86-quickinstall-after-reboot.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):235
+msgid "/doc/en/gentoo-x86-quickinstall-media.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):236
+msgid "/doc/en/gentoo-x86-quickinstall-stage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):237
+msgid "/doc/en/gentoo-x86-quickinstall-system.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):238
+msgid "/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):239
+msgid "/doc/en/vi-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):240
+msgid "/doc/en/virt-mail-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):241
+msgid "/doc/en/mailfilter-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):242
+msgid "/doc/en/genkernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):243
+msgid "/doc/en/gentoo-sparc-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):244
+msgid "/doc/en/mips-requirements.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):245
+msgid "/doc/en/udev-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):246
+msgid "/doc/en/gentoo-x86-tipsntricks.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):247
+msgid "/doc/en/gentoo-sparc-netboot-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):248
+msgid "/doc/en/gentoo-sparc-obpreference.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):249
+msgid "/doc/en/gnome-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):250
+msgid "/proj/en/desktop/gnome/howtos/gnome-2.26-upgrade.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):251
+msgid "/doc/en/gpm.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):252
+msgid "/doc/en/home-router-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):253
+msgid "/doc/en/arm-requirements.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):254
+msgid "/doc/en/power-management-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):255
+msgid "/doc/en/new-upgrade-to-gentoo-1.4.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):256
+msgid "/doc/en/portage-utils.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):257
+msgid "/proj/en/base/amd64/howtos/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):258
+msgid "/proj/en/base/amd64/howtos/bugs.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):259
+msgid "/proj/en/base/amd64/howtos/chroot-old.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):260
+msgid "/proj/en/base/amd64/howtos/fpic-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):261
+msgid "/proj/en/devrel/handbook/handbook.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):262
+msgid "/proj/en/gdp/doc/doc-policy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):263
+msgid "/proj/en/gdp/doc/doc-tipsntricks.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):264
+msgid "/proj/en/gdp/doc/handbook-release.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):265
+msgid "/proj/en/gdp/doc/gorg.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):266
+msgid "/main/en/about.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):267
+msgid "/main/en/philosophy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):268
+msgid "/main/en/contract.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):269
+msgid "/main/en/contact.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):270
+msgid "/main/en/graphics.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):271
+msgid "/main/en/irc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):272
+msgid "/main/en/lists.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):273
+msgid "/main/en/shots.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):274
+msgid "/main/en/sponsors.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):275
+msgid "/main/en/support.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):276
+msgid "/main/en/where.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):277
+msgid "/proj/en/site.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):278
+msgid "/doc/en/kernel-upgrade.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):279
+msgid "/proj/en/desktop/x/x11/modular-x-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):280
+msgid "/proj/en/desktop/x/x11/porting-modular-x-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):281
+msgid "/proj/en/desktop/x/x11/xorg-server-1.6-upgrade-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):282
+msgid "/proj/en/devrel/policy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):283
+msgid "/proj/en/gdp/doc/translators-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):284
+msgid "/proj/en/hardened/primer.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):285
+msgid "/proj/en/hardened/hardenedfaq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):286
+msgid "/proj/en/hardened/hardenedxorg.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):287
+msgid "/proj/en/hardened/pax-quickstart.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):288
+msgid "/proj/en/hardened/grsecurity.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):289
+msgid "/proj/en/hardened/capabilities.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):290
+msgid "/proj/en/hardened/selinux/selinux-handbook.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):291
+msgid "/proj/en/hardened/rsbac/overview.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):292
+msgid "/proj/en/hardened/rsbac/quickstart.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):293
+msgid "/proj/en/infrastructure/dev-email.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):294
+msgid "/proj/en/infrastructure/cvs-sshkeys.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):295
+msgid "/proj/en/infrastructure/dev-machines.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):296
+msgid "/proj/en/infrastructure/server-specs.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):297
+msgid "/proj/en/infrastructure/tenshi/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):298
+msgid "/proj/en/infrastructure/config-ntp.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):299
+msgid "/proj/en/infrastructure/config-ssh.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):300
+msgid "/proj/en/infrastructure/config-syslog.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):301
+msgid "/proj/en/infrastructure/dev-webspace.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):302
+msgid "/proj/en/infrastructure/faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):303
+msgid "/proj/en/infrastructure/mirrors-rsync.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):304
+msgid "/proj/en/metastructure/projectxml.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):305
+msgid "/proj/en/pr/docs/howto-presentation.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):306
+msgid "/proj/en/releng/catalyst/faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):307
+msgid "/proj/en/releng/installer/design.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):308
+msgid "/proj/en/releng/docs/release_guidelines.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):309
+msgid "/proj/en/releng/release/2004.0/releng/profile-update.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):310
+msgid "/proj/en/forums/forum-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):311
+msgid "/security/en/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):312
+msgid "/security/en/vulnerability-policy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):313
+msgid "/security/en/coordinator_guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):314
+msgid "/security/en/padawans.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):315
+msgid "/security/en/bug-searching.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):316
+msgid "/doc/en/keychain-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):317
+msgid "/proj/en/gdp/doc/metadoc-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):318
+msgid "/doc/en/hpc-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):319
+msgid "/proj/en/base/embedded/gnap-userguide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):320
+msgid "/doc/en/grub-error-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):321
+msgid "/doc/en/usb-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):322
+msgid "/doc/en/liveusb.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):323
+msgid "/doc/en/fluxbox-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):324
+msgid "/proj/en/vps/vserver-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):325
+msgid "/doc/en/security/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):326
+msgid "/doc/en/security/security-handbook.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):327
+msgid "/doc/en/security/shb-chroot.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):328
+msgid "/doc/en/security/shb-firewalls.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):329
+msgid "/doc/en/security/shb-intrusion.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):330
+msgid "/doc/en/security/shb-kernel.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):331
+msgid "/doc/en/security/shb-limits.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):332
+msgid "/doc/en/security/shb-logging.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):333
+msgid "/doc/en/security/shb-mounting.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):334
+msgid "/doc/en/security/shb-pam.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):335
+msgid "/doc/en/security/shb-perms.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):336
+msgid "/doc/en/security/shb-pre.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):337
+msgid "/doc/en/security/shb-tcp.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):338
+msgid "/doc/en/security/shb-services.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):339
+msgid "/doc/en/security/shb-tight.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):340
+msgid "/doc/en/security/shb-uptodate.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):341
+msgid "/proj/en/apache/doc/troubleshooting.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):342
+msgid "/proj/en/apache/doc/upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):343
+msgid "/proj/en/apache/doc/developer.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):344
+msgid "/doc/en/sudo-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):345
+msgid "/doc/en/gentoo-freebsd.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):346
+msgid "/doc/en/gentoo-mips-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):347
+msgid "/doc/en/mysql-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):348
+msgid "/doc/en/mysql-upgrade-slotted.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):349
+msgid "/doc/en/gcc-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):350
+msgid "/proj/en/base/x86/arch-testers-faq.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):351
+msgid "/doc/en/jffnms.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):352
+msgid "/doc/en/conky-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):353
+msgid "/doc/en/man-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):354
+msgid "/doc/en/info-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):355
+msgid "/proj/en/java/java-upgrade.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):356
+msgid "/doc/en/kernel-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):357
+msgid "/doc/en/zsh.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):358
+msgid "/doc/en/change-chost.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):359
+msgid "/doc/en/xfce-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):360
+msgid "/doc/en/openbox.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):361
+msgid "/doc/en/lxde-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):362
+msgid "/doc/en/gcc-optimization.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):363
+msgid "/doc/en/vpnc-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):364
+msgid "/proj/en/qa/autofailure.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):365
+msgid "/proj/en/qa/automagic.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):366
+msgid "/proj/en/qa/backtraces.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):367
+msgid "/proj/en/portage/doc/manually-fixing-portage.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):368
+msgid "/doc/en/xen-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):369
+msgid "/proj/en/overlays/userguide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):370
+msgid "/proj/en/overlays/devguide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):371
+msgid "/proj/en/overlays/policy.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):372
+msgid "/proj/en/base/pam/upgrade-0.99.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):373
+msgid "/proj/en/base/embedded/handbook/index.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):374
+msgid "/proj/en/tex/texlive-migration-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):375
+msgid "/doc/en/openrc-migration.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):376
+msgid "/doc/en/multipath.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):377
+msgid "/doc/en/bind-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):378
+msgid "/doc/en/logcheck.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(file):379
+msgid "/proj/en/qa/devmanual.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):383
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):697
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):705
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):708
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):711
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):715
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):719
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):723
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1006
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1046
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1077
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1080
+msgid "gentoodev_docs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):386
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):527
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):726
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):729
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):732
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):735
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):738
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):741
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):744
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):747
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):750
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):753
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):756
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):759
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):762
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):765
+msgid "other"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):389
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):392
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):395
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):407
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):410
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):413
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):416
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):485
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):488
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):491
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):494
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):497
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):500
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):503
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):506
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):509
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):512
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):515
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):518
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):521
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):524
+msgid "articles_linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):398
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):401
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):404
+msgid "articles_gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):419
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):422
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):425
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):428
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):431
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):434
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):437
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):440
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):443
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):446
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):449
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):452
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):455
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):458
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):461
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):464
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):467
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):470
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):473
+msgid "articles_commth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):476
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):479
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):482
+msgid "articles_others"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):530
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):533
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):645
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):648
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):651
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):654
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):657
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):660
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):664
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):667
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):673
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):676
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):679
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):682
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):685
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):688
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):691
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):694
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):798
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):808
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):849
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):856
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):860
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):863
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):972
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):978
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):999
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1002
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1019
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1023
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1027
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1031
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1053
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1056
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1083
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1089
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1111
+msgid "sysadmin_specific"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):536
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):540
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):663
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):801
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):807
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):811
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):815
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):818
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):821
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1059
+msgid "desktop_config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):539
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):633
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):636
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):639
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):642
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):812
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):842
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):845
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1009
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1062
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1065
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1071
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1074
+msgid "sysadmin_general"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):543
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):546
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):549
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1012
+msgid "install_guides"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):552
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):981
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):984
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1013
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1035
+msgid "project_base"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):555
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):558
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):561
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):564
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):567
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1016
+msgid "faq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):570
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):573
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):576
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):579
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):583
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):587
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):591
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):987
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):990
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):993
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):996
+msgid "install_other"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):580
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):584
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):588
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):846
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):857
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1003
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1020
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1024
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1028
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1032
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1039
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1043
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1050
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1068
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1105
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1108
+msgid "upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):594
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):599
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):604
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):609
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):614
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):617
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1086
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1093
+msgid "gentoo_portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):620
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):625
+msgid "gentoo_configuring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):630
+msgid "gentoo_choices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):669
+msgid "68740"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):698
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):867
+msgid "project_devrel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):701
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):866
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):946
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):956
+msgid "gentoodev_policies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):702
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):712
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):716
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):720
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):870
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):975
+msgid "project_gdp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):768
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):771
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):774
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):780
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):783
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):786
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):789
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):792
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):795
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1038
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1042
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1049
+msgid "desktop_install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):776
+msgid "83806"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):803
+msgid "48733"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):824
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):827
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):830
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):833
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):836
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):839
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):971
+msgid "desktop_apps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):851
+msgid "102481"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(bug):852
+msgid "115130"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):873
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):876
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):879
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):882
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):885
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):888
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):891
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):894
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):897
+msgid "project_hardened"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):900
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):903
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):906
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):909
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):912
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):915
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):918
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):921
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):924
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):927
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):930
+msgid "project_infra"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):933
+msgid "project_metastructure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):936
+msgid "project_pr"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):939
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):942
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):945
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):949
+msgid "project_releng"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):952
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):955
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):959
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):962
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):965
+msgid "project_security"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):968
+msgid "project_forums"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1092
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1096
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1100
+msgid "project_overlays"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1097
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1101
+msgid "gentdev_docs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(memberof):1102
+msgid "gentdev_policies"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//metadoc.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/migration-to-2.6.xml.po b/doc/gettext/ru/migration-to-2.6.xml.po
new file mode 100644
index 0000000..e446d0b
--- /dev/null
+++ b/doc/gettext/ru/migration-to-2.6.xml.po
@@ -0,0 +1,1596 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(guide:link):5
+msgid "/doc/en/migration-to-2.6.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):6
+msgid "The complete Gentoo Linux 2.6 migration guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):9
+msgid "dsd@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):9
+msgid "Daniel Drake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):14
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):12
+msgid "sergey_zlodey@mail.ru"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):12
+msgid "Sergey Galkin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):15
+msgid "svyatogor@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):15
+msgid "Sergey Kuleshov"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):18
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):18
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail:link):21
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(mail):21
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(abstract):24
+msgid ""
+"This document will aid you in the process of migrating from Linux 2.4 to "
+"Linux 2.6, devfs to udev, OSS to ALSA, and LVM to LVM2."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(version):29
+msgid "0.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(date):30
+msgid "2008-03-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):33
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):35
+msgid "What is new in Linux 2.6?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):38
+msgid ""
+"That is not an easy question to answer. Linux 2.6 is the result of over 2 "
+"years of rapid development and stabilisation of new features, and is "
+"architecturally quite different from its 2.4 counterpart. Some of the major "
+"changes are listed below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):46
+msgid ""
+"Scheduler/Interactivity improvements: Linux feels very smooth on desktop "
+"systems and copes much better than 2.4 while under load"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):50
+msgid ""
+"Scalability: Linux now scales much better at both ends - on small embedded "
+"devices and also systems with many processors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):54
+msgid "Performance: Throughput from common applications is much improved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):55
+msgid ""
+"Hardware support: Linux now supports many more architectures and hardware "
+"devices out-of-the-box than any other operating system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):61
+msgid ""
+"Joseph Pranevich has written a very detailed document, <uri link=\"http://"
+"www.kniggit.net/wwol26.html\">The Wonderful World Of Linux 2.6</uri> which "
+"you may be interested to glance over. If you are interested in the more "
+"technical details, you can refer to <uri link=\"http://www.codemonkey.org.uk/"
+"docs/post-halloween-2.6.txt\">The post-halloween document</uri> - but do "
+"bear in mind that this is somewhat outdated now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):74
+msgid "Gentoo and 2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):77
+msgid ""
+"From the 2005.0 release of Gentoo Linux, the default kernel is the latest "
+"2.6 series kernel. The default profile of the system is picked up from "
+"<path>/etc/make.profile</path> which on 2005.0 or above would be a symlink "
+"to <path>/usr/portage/profiles/default-linux/x86/2005.0</path> under which "
+"various important settings are taken care of."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):85
+msgid ""
+"If you are using a 2.4 profile, please change it to one that supports a 2.6 "
+"kernel by doing the following."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):90
+msgid "Changing your profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):90
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm -f /etc/make.profile</i>\n"
+"# <i>ln -snf /usr/portage/profiles/default-linux/x86/2005.1 /etc/make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):98
+msgid "What is udev?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):101
+msgid ""
+"In the past, Gentoo has instructed users to use <e>devfs</e> for managing "
+"the <path>/dev</path> directory, which contains a series of device "
+"interfaces to allow system applications to communicate with hardware "
+"(through the kernel)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):107
+msgid ""
+"<e>devfs</e>, whilst a good concept, has some internal problems, and has "
+"been completely removed from the main stable tree as of 2.6.13."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):112
+msgid ""
+"<e>udev</e> is the new way of managing device nodes. It addresses issues "
+"with previous device managers, and also attempts to solve some other "
+"problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):117
+msgid ""
+"The above may not mean much to you, but fear not, the hard working Gentoo "
+"developers have put effort into making the migration from devfs very easy. "
+"Please read the <uri link=\"/doc/en/udev-guide.xml\">Gentoo udev Guide</uri> "
+"for more information regarding the same."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):127
+msgid "What is ALSA?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):130
+msgid ""
+"With Linux 2.4, chances are that you used OSS (open sound system) drivers to "
+"power your sound card. OSS has been replaced by a newer and better set of "
+"sound drivers: ALSA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):136
+msgid ""
+"ALSA, the Advanced Linux Sound Architecture, is a new set of sound drivers "
+"with a new and improved API, present in the Linux 2.6 kernel. It is "
+"backwards compatible with OSS applications, provided that you select the "
+"right kernel configuration options!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):143
+msgid ""
+"If you do not have any sound/audio hardware, you can safely skip over any "
+"ALSA-related instructions in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):151
+msgid "What is LVM?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):154
+msgid ""
+"<e>Logical Volume Management</e> (LVM) exists as set of tools allowing you "
+"to manage your disk storage in a very flexible manner. Amongst other things, "
+"it allows powerful control over partitions (e.g. resizing without reboot), "
+"and makes operations like device changes relatively simple. LVM acts as an "
+"alternative to standard partition-based disk management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):162
+msgid ""
+"LVM support has historically been implemented in Linux 2.4. Linux 2.6 "
+"features a new version of LVM, named <e>LVM2</e>. The migration process "
+"requires you to install new versions of the user-level tools (covered later "
+"in this document) but will leave your data intact!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):169
+msgid ""
+"<e>If you do not currently use LVM for data-storage management, then LVM2 "
+"migration does not apply to you.</e> If this is the case, you can safely "
+"ignore any parts of this document referencing LVM/LVM2. Upgrading to Linux "
+"2.6 does <e>not</e> require you to store your data on LVM partitions - you "
+"can keep your data in the standard partition-format as it always has been."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):177
+msgid ""
+"If you are not a LVM user, but you think LVM2 sounds useful for you, you can "
+"convert your disks to this format at a later date, by following the <uri "
+"link=\"/doc/en/lvm2.xml\">Gentoo LVM2 Installation Guide</uri>. For now, let "
+"us just concentrate on getting a smooth 2.6 migration underway."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):189
+msgid "Preparation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):191
+msgid "Get your system up-to-date"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):194
+msgid ""
+"Some of the changes brought in with Linux 2.6 also required some changes in "
+"the base system applications. Before continuing, you should ensure that your "
+"system is relatively up-to-date, and to be perfectly sure, you should update "
+"all world and system packages where updates are available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):201
+msgid ""
+"In particular, make sure you have the latest stable versions of the "
+"following packages:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):209
+msgid ""
+"<c>sys-kernel/genkernel</c> (only if you wish to use genkernel as opposed to "
+"manual configuration)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):215
+msgid "Updating all world packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):215
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --sync</i>\n"
+"# <i>emerge -ua world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):223
+msgid "modutils vs module-init-tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):226
+msgid ""
+"<c>sys-apps/modutils</c> is the package that provides tools such as "
+"<c>modprobe</c>, <c>rmmod</c> and <c>insmod</c> for Linux 2.4."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):231
+msgid ""
+"Linux 2.6 introduces a new module format, and therefore requires new tools "
+"for handling modules. These are bundled up into the <c>sys-apps/module-init-"
+"tools</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):237
+msgid "You should now remove modutils and install module-init-tools:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):241
+msgid "Switching from modutils to module-init-tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):241
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --unmerge sys-apps/modutils</i>\n"
+"# <i>emerge module-init-tools</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):246
+msgid ""
+"Don't worry - even though you have just unmerged modutils, module-init-tools "
+"provides backwards compatibility for Linux 2.4, so you will still be able to "
+"boot into Linux 2.4 and handle modules for that kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):252
+msgid ""
+"For the above reason, module-init-tools might already be installed and "
+"working with your existing Linux 2.4 kernel. In this case, you don't need to "
+"worry about this stage - your system is already ready to deal with Linux 2.6 "
+"modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):261
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):269
+msgid "Installing udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):264
+msgid ""
+"There is no configuration involved here. Simply use <c>emerge</c> to install "
+"udev:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):269
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a udev</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):273
+msgid ""
+"You should now read the <uri link=\"/doc/en/udev-guide.xml\">Gentoo udev "
+"Guide</uri> to get a more complete idea about the differences between udev "
+"and devfs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):282
+msgid "Checking for essential device nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):285
+msgid ""
+"When the system boots up, the system requires some essential device nodes. "
+"As udev is not included in the kernel, it is not activated immediately. To "
+"work around this, you must ensure that you have some essential device nodes "
+"on your disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):292
+msgid ""
+"Our installation stage files will have created the required devices during "
+"the initial installation. However, some users have reported that this is not "
+"the case. We will use this opportunity to check that the device files exist, "
+"and create them if they do not."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):299
+msgid ""
+"As your existing device manager will be mounted at <path>/dev</path>, we "
+"cannot access it directly. So we will bind-mount your root partition to "
+"another location and access the <path>/dev</path> directory from there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):305
+msgid "Bind-mounting your root partition and listing static devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):305
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir -p /mnt/temp</i>\n"
+"# <i>mount -o bind / /mnt/temp</i>\n"
+"# <i>cd /mnt/temp/dev</i>\n"
+"# <i>ls -l console null</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):312
+msgid ""
+"If the above <e>ls</e> command reported that either <c>console</c> or "
+"<c>null</c> do not exist, then you must create them yourself, as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):317
+msgid "Creating the missing console and null nodes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):317
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mknod -m 660 console c 5 1</i>\n"
+"# <i>mknod -m 660 null c 1 3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):322
+msgid ""
+"You should now unmount your bind-mounted root partition, even if you did not "
+"have to create those devices:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):327
+msgid "Unmounting the bind-mounted root"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):327
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd</i>\n"
+"# <i>umount /mnt/temp</i>\n"
+"# <i>rmdir /mnt/temp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):336
+msgid "Installing ALSA utilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):339
+msgid ""
+"ALSA requires you to have some packages installed, so that applications can "
+"use the ALSA API. These packages will also allow you to control the mixer "
+"and volume levels. Install the required utilities as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):345
+msgid "Installing ALSA utilities and libraries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):345
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a alsa-lib alsa-utils alsa-tools alsa-headers alsa-oss</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):354
+msgid "Installing the Linux 2.6 sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):357
+msgid "Choosing and installing a kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):360
+msgid ""
+"The first thing you need to do is install sources of a 2.6 kernel of your "
+"choice. The two Gentoo-supported 2.6 kernels are currently <e>gentoo-"
+"sources</e> (for desktops) and <e>hardened-sources</e> (for servers). There "
+"are others available, see the <uri link=\"/doc/en/gentoo-kernel.xml\">Gentoo "
+"Linux Kernel Guide</uri> for more choices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):369
+msgid ""
+"In this guide, we'll use <c>gentoo-sources</c> as an example. Install your "
+"chosen set of kernel sources using the <c>emerge</c> utility:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):374
+msgid "Installing gentoo-sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):374
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a gentoo-sources</i>\n"
+"These are the packages that I would merge, in order:\n"
+"Calculating dependencies ...done!\n"
+"[ebuild  NS   ] sys-kernel/gentoo-sources-2.6.10-r4\n"
+"\n"
+"Do you want me to merge these packages? [Yes/No] <i>y</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):383
+msgid ""
+"When performing the above <c>emerge</c> command, if you find that it wants "
+"to install a 2.4 version of gentoo-sources (e.g. <c>gentoo-sources-2.4.26</"
+"c>), then it means that the profile you are using is not designed for Linux "
+"2.6 users. Please follow the <uri link=\"/doc/en/gentoo-upgrading.xml"
+"\">Gentoo Upgrading Document</uri> to switch to a 2.6-based profile, and "
+"retry installing 2.6 kernel sources."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):395
+msgid "Updating the /usr/src/linux symbolic link"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):398
+msgid ""
+"Various components of the Gentoo utilities rely on <path>/usr/src/linux</"
+"path> being a symbolic link to the kernel sources that you are running (or "
+"wish to compile against)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):404
+msgid ""
+"We will now update our <path>/usr/src/linux</path> link to point at the "
+"kernel sources we just installed. Continuing our example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):409
+msgid "Updating the /usr/src/linux softlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):409
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src</i>\n"
+"# <i>ln -sfn linux-2.6.10-gentoo-r4 linux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):419
+msgid "Known pitfalls with Linux 2.6 migration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):423
+msgid ""
+"Before we get stuck into configuring the kernel, I'll attempt to detail the "
+"most common errors that people make when migrating to Linux 2.6, as some of "
+"these points will influence the way you configure the new kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):429
+msgid ""
+"Not all of these points are relevant at this stage, but I will detail them "
+"all here in one place, and you can refer back at your leisure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):437
+msgid "Don't use \"make oldconfig\" with a 2.4 .config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):440
+msgid ""
+"If you don't understand what this means, don't worry, you won't make this "
+"mistake if you follow the rest of this guide correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):445
+msgid ""
+"You'll be asked many many questions, since there have been a large amount of "
+"changes. Many people who do try a <c>make oldconfig</c> from a 2.4 config "
+"end up creating an unworkable kernel (e.g. no output on-screen, no input "
+"from keyboard, etc). Please save yourself the trouble, and use the "
+"traditional <c>menuconfig</c> configuration method just this once."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):456
+msgid "Don't use ide-scsi for CD/DVD writing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):459
+msgid ""
+"In Linux 2.4, the only way to achieve good CD/DVD writing results was to "
+"enable the (rather ugly) <c>ide-scsi</c> emulation. Thankfully, the IDE "
+"layer in Linux 2.6 has been extended to support CD/DVD writers much better."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):465
+msgid ""
+"You don't need to enable any extra options to support CD writing. Just be "
+"sure <e>not</e> to enable <c>ide-scsi</c> as you used to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):473
+msgid "PC Speaker is now a configurable option"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):476
+msgid ""
+"You won't get your normal console beeps (or any response from the PC speaker "
+"at all) unless you specifically enable the new PC speaker option "
+"(<c>CONFIG_INPUT_PCSPKR</c>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):482
+msgid "Location of PC speaker option"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):482
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+" Input device support  ---&gt;\n"
+"  [*] Misc\n"
+"   &lt;*&gt;   PC Speaker support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):489
+msgid ""
+"By \"PC speaker\", I am referring to the analogue speaker that beeps once "
+"when your system is powering up, I am not referring to normal sound hardware "
+"used for playing music, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):498
+msgid "New USB Storage block device driver sometimes problematic"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):501
+msgid ""
+"Very recently, a new USB storage device driver has been added to the kernel. "
+"At the time of writing, this driver (\"ub\") is still in its early stages "
+"and some users find it to be unreliable. If you have problems accessing your "
+"USB hard disk, USB flash disk, USB card reader, or USB digital camera, then "
+"you could try reverting to the older SCSI-style driver:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):509
+msgid "Disabling ub"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):509
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+" Block devices  ---&gt;\n"
+"  &lt; &gt; Low Performance USB Block driver\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):515
+msgid ""
+"The older SCSI-style driver (USB Mass Storage support) is enabled by "
+"default. It can be found under \"Device Drivers --&gt; USB support\", but "
+"will generally not come into effect while ub is also present."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):524
+msgid "usbdevfs renamed to usbfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):527
+msgid ""
+"If you have edited your <path>/etc/fstab</path> file to customise the way "
+"that the USB device filesystem gets mounted, you may have to modify the "
+"filesystem type from <e>usbdevfs</e> to <e>usbfs</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):533
+msgid ""
+"Recent 2.4 kernels will also allow you to use \"usbfs\" as well as \"usbdevfs"
+"\", so you are not breaking any backwards compatibility by doing this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):541
+msgid "Don't renice X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):544
+msgid ""
+"If you are a desktop 2.4 user, you may have hacked your system into running "
+"X at a higher priority, as in some cases it seems to provide better desktop "
+"performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):550
+msgid ""
+"There have been many scheduler changes in 2.6 which change this behaviour. "
+"If you continue to run X at a higher priority, it will do exactly what it is "
+"supposed to (run the <e>display server</e> at a very high priority) and you "
+"will notice consequences such as sound stuttering and slow application load "
+"times because your CPU is spending too long serving X and only X."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):558
+msgid ""
+"In Linux 2.6, you no longer need to renice desktop applications to get good "
+"interactivity. Please remove your \"niceness\" hacks!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):566
+msgid "X11 config file should now use /dev/input/mice for PS/2 and USB mice"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):569
+msgid ""
+"One of the changes that a default udev configuration introduces is different "
+"organisation of the mouse device nodes. Previously, you would have had nodes "
+"such as <path>/dev/psaux</path> and <path>/dev/mouse</path>. You will now "
+"have nodes such as <path>/dev/input/mouse0</path>, <path>/dev/input/mouse1</"
+"path>, and a collective <path>/dev/input/mice</path> node which combines "
+"movements from all mice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):578
+msgid ""
+"Since the old X configurations typically reference <path>/dev/mouse</path> "
+"or <path>/dev/psaux</path> then you may get an error similar to the one "
+"shown below when you attempt to start X11:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):584
+msgid "Common error when starting X on a udev system for the first time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):584
+#, no-wrap
+msgid ""
+"\n"
+"(EE) xf86OpenSerial: Cannot open device /dev/mouse\n"
+"  No such file or directory.\n"
+"(EE) Mouse0: cannot open input device\n"
+"(EE) PreInit failed for input device \"Mouse0\"\n"
+"No core pointer\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):592
+msgid ""
+"To correct this, open your X11 config in a text editor, and update the mouse "
+"<e>InputDevice</e> section to use the <path>/dev/input/mice</path> device. "
+"An example is shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):598
+msgid "Opening your X11 config file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):598
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/X11/xorg.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):602
+msgid ""
+"If you are still using XFree86, your config file will be <path>/etc/X11/"
+"XF86Config</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):607
+msgid "Sample mouse InputDevice section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):607
+#, no-wrap
+msgid ""
+"\n"
+"Section \"InputDevice\"\n"
+"  Identifier  \"Mouse0\"\n"
+"  Driver      \"mouse\"\n"
+"  Option      \"Protocol\" \"auto\"\n"
+"  Option      \"Device\" \"/dev/input/mice\"\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):616
+msgid ""
+"If you are using a serial mouse, the new device path will be <path>/dev/"
+"tts/0</path> instead of <path>/dev/ttyS0</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):624
+msgid "New Serial-ATA (SATA) drivers name the devices differently"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):627
+msgid ""
+"If you used the original Serial ATA drivers under Linux 2.4, you probably "
+"observed your SATA devices having names such as <path>/dev/hde</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):632
+msgid ""
+"Linux 2.6 introduces some new SATA drivers (libata) which are based on the "
+"SCSI subsystem. As these drivers are based on SCSI, your SATA disks will now "
+"show up as SCSI devices. Your first SATA disk will be named <path>/dev/sda</"
+"path>. You will need to update your <path>/etc/fstab</path> file to reflect "
+"this, and you will need to bear this in mind when choosing the root/"
+"real_root kernel boot parameter later on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):641
+msgid ""
+"libata has been backported into recent versions of Linux 2.4, so you may "
+"already be familiar with the new device naming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):649
+msgid "bootsplash no longer maintained"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):652
+msgid ""
+"If you used the <c>gentoo-sources-2.4</c> kernel, you may have used the "
+"<e>bootsplash</e> functionality in order to provide yourself with a "
+"colourful framebuffer console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):658
+msgid ""
+"The developer of bootsplash appears to have lost interest in his project, "
+"given some design problems. However, Gentoo developer <e>Michał Januszewski</"
+"e> is developing a successor, <c>gensplash</c>, which in included in the "
+"gentoo-sources-2.6 kernel. You can follow Michał's <uri link=\"http://dev."
+"gentoo.org/~spock/projects/gensplash/archive/gensplash-in-5-easy-steps.txt"
+"\"> Gensplash in 5 easy steps</uri> document in order to familiarize "
+"yourself with how gensplash is operated."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):671
+msgid "I2C drivers now included in the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):674
+msgid ""
+"If you use <c>lm-sensors</c> to monitor system temperatures and power "
+"levels, you previously needed to install the <c>i2c</c> package in order to "
+"provide hardware support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):680
+msgid ""
+"The I2C hardware drivers are now included in the Linux 2.6 kernel, no "
+"external i2c package is required. Remember to compile support for your "
+"specific I2C devices into the kernel configuration. You will then be able to "
+"use <c>lm-sensors</c> as usual."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):694
+msgid "Configuring, building, and installing the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):698
+msgid ""
+"As with Linux 2.4, you have two options for managing your new kernel build."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):703
+msgid ""
+"The default method is to configure your kernel manually. This may seem "
+"daunting but is the preferred way as long as you know your system. If you "
+"wish to configure your new kernel manually, please continue on to the <uri "
+"link=\"#manual\">next chapter</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(li):709
+msgid ""
+"The alternative option is to use our <c>genkernel</c> utility to "
+"automatically configure, compile, and install a kernel for you. If you wish "
+"to use <c>genkernel</c> then skip over the next chapter and proceed with "
+"<uri link=\"#genkernel\">using genkernel</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):722
+msgid "Default: Manual configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):724
+msgid "Configuring the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):727
+msgid ""
+"We'll now get on with configuring the kernel. Open menuconfig in the usual "
+"way:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):731
+msgid "Invoking menuconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):731
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):736
+msgid ""
+"You will probably be familiar with using menuconfig from configuring 2.4 "
+"kernels. Fortunately, the front end has barely changed at all, but you will "
+"observe much better organisation of kernel options, plus <e>many</e> new "
+"options that weren't present in 2.4."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):743
+msgid "Be sure to enable the following important kernel options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):747
+msgid "Required kernel options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):747
+#, no-wrap
+msgid ""
+"\n"
+"File systems ---&gt;\n"
+"  Pseudo Filesystems ---&gt;\n"
+"    [*] /proc file system support\n"
+"    [*] Virtual memory file system support (former shm fs)\n"
+"\n"
+"<comment>(the following are required for udev):</comment>\n"
+"General setup  ---&gt;\n"
+" [*] Support for hot-pluggable devices\n"
+"\n"
+"<comment>(the following are required for ALSA):</comment>\n"
+"Device Drivers  ---&gt;\n"
+" Sound  ---&gt;\n"
+"  &lt;*&gt; Sound card support\n"
+"  Advanced Linux Sound Architecture  ---&gt;\n"
+"   &lt;M&gt; Advanced Linux Sound Architecture\n"
+"   &lt;M&gt; Sequencer support\n"
+"   &lt;M&gt; OSS Mixer API\n"
+"   [*] OSS Sequencer API\n"
+"<comment>   (and do not forget to select your soundcard from the submenus!)</comment>\n"
+"\n"
+"<comment>(the following are required if you use LVM for disk management):</comment>\n"
+"Device Drivers  ---&gt;\n"
+" Multi-device support (RAID and LVM)  ---&gt;\n"
+"  [*] Multiple devices driver support (RAID and LVM)\n"
+"   &lt;*&gt;   Device mapper support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(warn):775
+msgid ""
+"Previously you may have included support for the <path>/dev</path> file "
+"system (now marked OBSOLETE). Do not enable devfs support. We have installed "
+"udev, which we will be using instead of devfs from now on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):781
+msgid ""
+"Also, remember to enable support for the filesystems that you use, and the "
+"hardware present in your system. Be sure to enable support for the IDE "
+"controller on your motherboard if you wish to benefit from fast DMA disk "
+"access. Refer to the <uri link=\"/doc/en/handbook/handbook-x86.xml?"
+"part=1&amp;chap=7\">Configuring the Kernel</uri> section of the <uri link=\"/"
+"doc/en/handbook/index.xml\">Gentoo Handbook</uri> for additional guidance "
+"here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):794
+msgid "Building the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):797
+msgid ""
+"Now that we have configured the kernel, we can start the compilation process:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):801
+msgid "Compiling the kernel source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):801
+#, no-wrap
+msgid ""
+"\n"
+"# <i>make &amp;&amp; make modules_install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):805
+msgid ""
+"You may recall having to run <c>make dep</c> with Linux 2.4 sources. This is "
+"no longer required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):810
+msgid ""
+"Wait for the kernel compilation to complete (and observe the much more "
+"readable compilation output)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):818
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):826
+msgid "Installing the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):821
+msgid ""
+"The next step is mounting your <path>/boot</path> partition and copying the "
+"kernel image over. You must then update your bootloader config manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):826
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount /boot</i>\n"
+"# <i>cp arch/i386/boot/bzImage /boot/bzImage-2.6.10-gentoo-r4</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):831
+msgid ""
+"Note that the above instructions are examples only, you should follow your "
+"usual procedure of updating kernels by following the instructions in the "
+"<uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> (see the <uri "
+"link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=7\">Configuring the "
+"Kernel</uri> chapter)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):839
+msgid ""
+"When updating your bootloader config, do not remove the old entry pointing "
+"at your 2.4 kernel. This way, you will easily be able to switch between the "
+"two if something is not working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):845
+msgid ""
+"Now continue onto the <uri link=\"#modules\">Module Configuration</uri> "
+"section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):854
+msgid "Alternative: Using genkernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):858
+msgid ""
+"If you prefer to use genkernel instead of manually configuring your kernel, "
+"you will be happy to hear that using genkernel to produce 2.6 kernels is "
+"very similar to the process you performed when producing your previous 2.4 "
+"kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):864
+msgid "You should invoke genkernel as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):868
+msgid "Invoking genkernel with some common arguments"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):868
+#, no-wrap
+msgid ""
+"\n"
+"# <i>genkernel --udev --menuconfig --bootloader=grub all</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):872
+msgid ""
+"In the above example, we also take advantage of genkernel features to open "
+"menuconfig to allow you to customise the kernel configuration (if you wish), "
+"and to update the grub bootloader configuration after compilation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):878
+msgid ""
+"You should choose genkernel arguments that suit you, but do not forget to "
+"include the <c>--udev</c> argument! Refer to the <uri link=\"/doc/en/"
+"genkernel.xml\">Gentoo Linux Genkernel Guide</uri> and the <uri link=\"/doc/"
+"en/handbook/handbook-x86.xml?part=1&amp;chap=7\">Configuring the Kernel</"
+"uri> chapter of the <uri link=\"/doc/en/handbook/index.xml\">Gentoo "
+"Handbook</uri> for additional information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):887
+msgid ""
+"If you choose to update your bootloader config yourself, then you must "
+"remember to include the <c>udev</c> kernel parameter. A sample <e>grub</e> "
+"config section is shown below, but remember to adjust the <e>real_root</e> "
+"parameter for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):894
+msgid "Sample GRUB config for genkernel + udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):894
+#, no-wrap
+msgid ""
+"\n"
+"title Gentoo Linux (2.6 kernel)\n"
+"root (hd0,0)\n"
+"kernel /kernel-2.6.10-gentoo-r4 <i>udev</i> root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3\n"
+"initrd /initrd-2.6.10-gentoo-r4\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):906
+msgid "Module Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):909
+msgid "Installing external modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):912
+msgid ""
+"Many users will additionally rely on kernel modules that are built outside "
+"of the kernel tree. Common examples are the binary ATI and Nvidia graphics "
+"drivers. You now need to install those modules, which will compile against "
+"the 2.6 sources found at <path>/usr/src/linux</path>. This is the usual case "
+"of <c>emerge packagename</c> for all the external modules you are used to "
+"using with 2.4."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):921
+msgid ""
+"Refer again to the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;"
+"chap=7\">Configuring the Kernel</uri> chapter of the <uri link=\"/doc/en/"
+"handbook/index.xml\">Gentoo Handbook</uri> for more info."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):931
+msgid "Autoloading modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):934
+msgid ""
+"You may have decided to compile some kernel components as modules (as "
+"opposed to compiled directly into the kernel) and would like to have them "
+"autoloaded on bootup like you did with 2.4. Also, if you installed any "
+"external modules from the portage tree (as described above) you will "
+"probably want to autoload them too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):942
+msgid ""
+"You can achieve this similarly as to how you did with 2.4. Simply open up "
+"the file <path>/etc/modules.autoload.d/kernel-2.6</path> in a text editor "
+"and list the names of the modules you would like autoloaded."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):948
+msgid "Opening the module autoload list in nano"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):948
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):952
+msgid "Sample autoload list to load the 3c59x and nvidia modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):952
+#, no-wrap
+msgid ""
+"\n"
+"# /etc/modules.autoload.d/kernel-2.6:  kernel modules to load when system boots.\n"
+"#\n"
+"# Note that this file is for 2.6 kernels.\n"
+"#\n"
+"# Add the names of modules that you'd like to load when the system\n"
+"# starts into this file, one per line. Comments begin with # and\n"
+"# are ignored. Read man modules.autoload for additional details.\n"
+"\n"
+"3c59x\n"
+"nvidia\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):970
+msgid "LVM to LVM2 migration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):972
+msgid "Upgrading to LVM2 tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):975
+msgid ""
+"If you do not use LVM to manage your disk storage, you can safely skip this "
+"chapter and skip onto the next."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):980
+msgid ""
+"Fortunately, upgrading from the LVM1 user tools to the LVM2 versions is very "
+"simple:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):985
+msgid "Upgrading user-tools from LVM1 to LVM2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):985
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --unmerge lvm-user</i>\n"
+"# <i>emerge lvm2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):990
+msgid ""
+"You will need to re-emerge <c>lvm-user</c> if you plan to go back to booting "
+"a 2.4 kernel, as <c>lvm2</c> by itself isn't enough for 2.4 kernels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1000
+msgid "Booting into Linux 2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1004
+msgid ""
+"It's now time to boot into Linux 2.6. Close all applications and reboot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1008
+msgid "Rebooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1008
+#, no-wrap
+msgid ""
+"\n"
+"# <i>umount /boot</i>\n"
+"# <i>reboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1013
+msgid ""
+"When you reboot, if you followed this document correctly so far, you will "
+"have the option of either loading Linux 2.4 or Linux 2.6 from your "
+"bootloader. Choose Linux 2.6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1019
+msgid ""
+"Once the system has booted, check that things are working. If you made a "
+"mistake in the kernel configuration, don't worry, you can skip back to the "
+"<uri link=\"#conf\">Configuring, building, and installing the kernel</uri> "
+"section, make your change, recompile and install new kernel image, reboot, "
+"and try again!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1030
+msgid "Configuring and unmuting ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1033
+msgid ""
+"We will now complete the ALSA configuration and unmute the audio channels. "
+"The ALSA packages provide a useful utility to make this process relatively "
+"simple:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1038
+msgid "Invoking the automatic ALSA configuration utility"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1038
+#, no-wrap
+msgid ""
+"\n"
+"# <i>alsaconf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1042
+msgid ""
+"The process is straightforward: allow the <e>/etc/modules.d/alsa</e> file to "
+"be automatically updated, and then allow ALSA to be reloaded. alsaconf will "
+"then terminate, however you will need to run it multiple times if you have "
+"multiple sound devices installed in your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1049
+msgid ""
+"You should now add <c>alsasound</c> to your boot runlevel, so that volumes "
+"will be saved on shutdown and restored on bootup:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1054
+msgid "Adding alsasound to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1054
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add alsasound boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(note):1058
+msgid ""
+"The <c>alsaconf</c> utility chooses initial volume levels for your sound "
+"devices. If these are inappropriate, you can modify them at any time with "
+"the <c>alsamixer</c> utility."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1067
+msgid "Any immediate problems?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1070
+msgid ""
+"At this stage you should refer back to the <uri link=\"#pitfalls\">Known "
+"pitfalls with Linux 2.6 migration</uri> section which may be helpful with "
+"any issues you encounter immediately."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1081
+msgid "Header files and NPTL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1085
+msgid ""
+"By now you are running Linux 2.6 and hopefully have all issues ironed out. "
+"You should now update your Linux kernel header files and re-merge glibc so "
+"that userspace applications can take advantage of new Linux 2.6 features."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1091
+msgid "Updating to linux-headers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1091
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -u linux-headers</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1095
+msgid ""
+"After updating your headers package, you should generally re-merge glibc. "
+"There is a new feature here that you may be interested in - NPTL. NPTL is a "
+"new threading model present in Linux 2.6, which features much quicker thread "
+"create and destroy times. This won't make much of a difference to most "
+"systems, but you may wish to enable it during this migration process! To "
+"enable NPTL, edit <path>/etc/make.conf</path>, adding <e>nptl</e> to your "
+"USE variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(warn):1104
+msgid ""
+"If you choose to also enable the \"nptlonly\" flag, be aware that you will "
+"no longer be able to boot a 2.4 kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1109
+msgid ""
+"Now re-merge glibc (you should do this even if you did not choose to enable "
+"NPTL)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1114
+msgid "Reinstalling glibc against the new kernel headers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1114
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -a glibc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1118
+msgid ""
+"If you enabled NPTL, existing binaries will not use it until they are "
+"recompiled. However, any binaries compiled from this point onwards <e>will</"
+"e> use NPTL. You may wish to recompile all binaries now, e.g.:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1124
+msgid "Recompiling all packages on the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1124
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -e world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1128
+msgid ""
+"Alternatively, you can just let your system \"naturally\" convert itself to "
+"NPTL as you update to newer versions of packages when they are released."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1138
+msgid "Closing remarks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1140
+msgid "Problems?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1143
+msgid ""
+"With the incredible amount of work that went into Linux 2.6, it is sometimes "
+"inevitable that things which used to work fine, no longer function as "
+"expected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1148
+msgid ""
+"If you have any problems with your 2.6 kernel, and you can confirm that this "
+"problem does not exist with Linux 2.4, then please open a bug with us on our "
+"<uri link=\"http://bugs.gentoo.org\">Bugzilla</uri>. We will investigate the "
+"issue, and if we find that it is a problem in the mainline kernel, we may "
+"then ask you to file a report at the central kernel bugzilla."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1159
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1162
+msgid ""
+"Hopefully you have just completed a smooth migration and you are enjoying "
+"the benefits which Linux 2.6 brings over 2.4."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1167
+msgid ""
+"I would like to say a word of thanks to the many users who effectively "
+"'tested' this document while it was in its early stages, and provided "
+"feedback about how the migration process went. Sorry that I did not reply to "
+"all the emails (there were a lot!), but I did read every one, and refined "
+"this document where appropriate. Enjoy your 2.6-enhanced systems :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(title):1178
+msgid "Removing Linux 2.4 from your system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1181
+msgid ""
+"After you have been running 2.6 for a while, you may decide that you no "
+"longer have any requirement to be able to use Linux 2.4. The steps you can "
+"take to clean up your system are detailed below. <e>Only follow the "
+"procedure in this section if you are sure that you don't want/need to use "
+"2.4 again!</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1188
+msgid ""
+"The 2.4 kernel source code can be removed, using the emerge utility as "
+"usual. For example, assuming you have 2.4 versions of vanilla-sources and "
+"gentoo-sources installed, you could use the following command to remove them "
+"while keeping the 2.6 versions intact:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1195
+msgid "Example: Removing Linux 2.4 sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1195
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --unmerge =vanilla-sources-2.4.* =gentoo-sources-2.4.*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1199
+msgid ""
+"Portage will not completely clean out your 2.4 kernel source installations, "
+"because some temporary files are created during compilation. It is safe to "
+"remove these remnants with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1205
+msgid "Removing remaining temporary files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1205
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm -rf /usr/src/linux-2.4.*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1209
+msgid ""
+"You can additionally remove modules and information files relating to your "
+"old 2.4 kernel installations, as these are no longer needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1214
+msgid "Removing previously-installed 2.4 modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1214
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm -rf /lib/modules/2.4.*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1218
+msgid ""
+"The 2.4 kernel binaries you used to boot from can also be safely removed. "
+"You should mount your <c>/boot</c> partition, and remove those images. You "
+"should also update your bootloader configuration so that it no longer "
+"references these deleted kernel images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1225
+msgid ""
+"Some Linux 2.4 users will have previously installed the <c>alsa-driver</c> "
+"package to benefit from the new audio capabilities included in Linux 2.6. If "
+"you were one of these users, and you followed the advice given earlier in "
+"this document about building ALSA with the 2.6 kernel sources (as opposed to "
+"using the <c>alsa-driver</c> package), then you can safely remove this to "
+"prevent future conflicts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1234
+msgid ""
+"Additionally, <c>lm-sensors</c> users will have previously used the <c>i2c</"
+"c> package to provide the hardware drivers. As already mentioned, I2C "
+"drivers are now included in the kernel, so this package can also be removed "
+"in order to prevent future conflicts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1241
+msgid ""
+"The devfs management daemon, <c>devfsd</c>, can also safely be removed, now "
+"that we are using <c>udev</c> for device management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1246
+msgid "Removing alsa-driver, i2c, and devfsd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1246
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --unmerge alsa-driver i2c devfsd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(p):1250
+msgid ""
+"If you are LVM2 user, you may wish to convert your data into the LVM2 data "
+"format in order to benefit from the advantages which LVM2 provides. However, "
+"this operation will prevent you from ever accessing your LVM data from a 2.4 "
+"kernel. If you want to continue with the conversion (this is totally "
+"optional!), then you should examine the <c>vgconvert</c> man page for "
+"instructions on how to carry this out. An example is shown below, where "
+"<c>main</c> is the volume group name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre:caption):1260
+msgid "Converting a LVM1 volume to LVM2 format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(pre):1260
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vgconvert -M2 main</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//migration-to-2.6.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/mips-requirements.xml.po b/doc/gettext/ru/mips-requirements.xml.po
new file mode 100644
index 0000000..af78a7a
--- /dev/null
+++ b/doc/gettext/ru/mips-requirements.xml.po
@@ -0,0 +1,600 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):6
+msgid "Gentoo/MIPS Linux Hardware Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(mail:link):9
+msgid "kumba@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(mail):9
+msgid "Joshua Kinard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(mail:link):12
+msgid "redhatter@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(mail):12
+msgid "Stuart Longland"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(abstract):15
+msgid ""
+"This document provides an overview of the status of various MIPS-based "
+"systems for installing Gentoo Linux. If you find errors or omissions please "
+"email the maintainer or an editor."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(version):25
+msgid "1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(date):26
+msgid "2010-09-01"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):29
+msgid "General Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):32
+msgid "System Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):35
+msgid ""
+"The exact requirements will largely depend on what you intend to use the "
+"machine for and how you wish to go about installing Gentoo. The following "
+"table should give you a rough idea."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):44
+msgid "Minimum"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):45
+msgid "Recommended"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):46
+msgid "Ideal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):49
+msgid "RAM:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):50
+msgid "48~64MB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):51
+msgid "&gt;128MB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):52
+msgid "~256MB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):55
+msgid "HDD:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):56
+msgid "4GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):57
+msgid "&gt;8GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):58
+msgid "18GB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):66
+msgid "A Note about serial consoles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):69
+msgid ""
+"If you lack an appropriate Framebuffer, you will be required to use serial "
+"console. Serial console programs for linux include <c>minicom</c> and <c>xc</"
+"c>, and for Windows, <c>HyperTerminal</c> and <c>Tera Term Pro</c>. If you "
+"are running Windows, and intend to use HyperTerminal, it is advised that you "
+"seek out an updated client from the program's website instead of the one "
+"installed by default. An upgraded client provides much better serial support "
+"than the default one installed by Windows."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):82
+msgid "User Testimonies &amp; Kernel Configurations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):85
+msgid ""
+"As an aid to the project, a <uri link=\"http://stuartl.longlandclan.hopto."
+"org/gentoo/mips/\">hardware support database</uri> has been set up. This "
+"support database is intended to provide a quick and easy way to determine "
+"how well certain configurations are supported. The system also allows people "
+"to contribute their comments and kernel configs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):98
+msgid "Silicon Graphics Systems -- Stable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):102
+msgid ""
+"The following systems are known to be very stable overall. Just about all "
+"the core hardware is supported in these systems, and there are very few "
+"outstanding stability issues at this time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):111
+msgid "IP22: Indy, Indigo 2 and Challenge S"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):118
+msgid "<e>(on Indy and Challenge S)</e> R4000, R4400, R4600, R5000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):121
+msgid "<e>(on Indigo 2)</e> R4000, R4400"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):129
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):530
+msgid "Linux 2.4: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):130
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):264
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):298
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):358
+msgid "Linux 2.6: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):136
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):537
+msgid "32-bit: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):137
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):271
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):305
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):365
+msgid "64-bit: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):143
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):208
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):277
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):311
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):371
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):544
+msgid "o32: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):144
+msgid "n32: <e>Experimental</e> (Only on Linux 2.6 R5000/RM5200)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):145
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):210
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):279
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):313
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):373
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):546
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):582
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):628
+msgid "n64: <e>Not Available In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):151
+msgid ""
+"At present, only the Newport (XL) graphics framebuffer is supported in "
+"Linux. Therefore on systems with other framebuffers, you will need to use "
+"serial console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):156
+msgid ""
+"The Challenge S has its RJ-45 connector on a daughter board (Mezz) linked "
+"with an unsupported SCSI adapter, a WD33C95A. In order for this network "
+"connector to function, this SCSI bus needs to be activated, however it is "
+"not yet supported by Linux. As a result of this, the Challenge S can only "
+"get network connectivity via its AUI connector."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):163
+msgid ""
+"Indigo2 EISA Support is <e>highly</e> experimental. It isn't very well "
+"tested and may not work with all hardware. Hardware that it is known to "
+"function with is listed, and as more compatible hardware is discovered, it "
+"will be added. Please note that hardware requiring DMA support is currently "
+"not functional. This includes EISA/ISA-based soundcards. EISA Video cards "
+"requiring an x86-compatible BIOS are also not functional."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):179
+msgid "IP32: O2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):186
+msgid "<b>Stable:</b> R5000, RM5200"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):187
+msgid "<b>Experimental:</b> RM7000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):188
+msgid "<b>Unsupported:</b> R10000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):194
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):263
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):357
+msgid "Linux 2.4: <e>Unsupported in Kernel</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):195
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):531
+msgid "Linux 2.6: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):201
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):270
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):304
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):364
+msgid "32-bit: <e>Unsupported in Kernel</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):202
+msgid "64-bit: <e>Stable</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):209
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):312
+msgid "n32: <e>Experimental</e> (Only on Linux 2.6)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):216
+msgid ""
+"The O2 RM7000 Processor support is limited in Linux currently, as it "
+"requires a fairly recent kernel version (&gt;2.6.7), and has several notable "
+"issues. The first issue is a problem with SCSI at the moment, making the "
+"internal disks unusable at the current time. The Level 3 (Tertiary) Cache is "
+"also disabled due to there being no support for this cache in the linux "
+"kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):224
+msgid ""
+"Please be aware that this note only applies to the official SGI RM7000 "
+"running at 350MHz, not the 600MHz RM7000 that can be assembled using an "
+"RM5200 board. These \"modded\" CPU modules for O2 systems are not supported/"
+"tested, although, in theory, they should be functional, but may suffer from "
+"the same problems listed above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):240
+msgid "Silicon Graphics Systems -- Experimental/Unstable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):244
+msgid ""
+"The systems listed here are known to run Linux... <e>HOWEVER</e>, in many "
+"cases, there are known stability issues, and major gaps in the hardware "
+"support. In short, it will be a rough and bumpy ride."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):253
+msgid "IP27: Origin 200 and 2000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):257
+msgid "<b>Processor Options <e>(Experimental)</e>:</b> R10000, R12000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):278
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):372
+msgid "n32: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):287
+msgid "IP28: Indigo 2 Impact (a.k.a Indigo 2 R10k)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):291
+msgid "<b>Processor Options <e>(Experimental)</e>:</b> R10000"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):297
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):566
+msgid "Linux 2.4: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):331
+msgid ""
+"MIPS R10000 Microprocessor User's Manual (See <e>PDF Pages 51-55</e>) "
+"<uri>http://techpubs.sgi.com/library/manuals/2000/007-2490-001/"
+"pdf/007-2490-001.pdf</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):336
+msgid ""
+"Post to NetBSD sgimips Mailing List on 29 Jun 2000 <uri>http://mail-index."
+"netbsd.org/port-sgimips/2000/06/29/0006.html</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):319
+msgid ""
+"IP28 Indigo2 Impact support (classified as an Indigo2 system w/ an R10000 "
+"Processor) is <e>very experimental</e>. Most of the work is currently being "
+"done by Peter Fuerst, who maintains patches on his <uri link=\"http://www."
+"pfrst.de/download.html\">website</uri>. This kernel is <e>NOT</e> intended "
+"for stable, day-to-day use. The Indigo2 IP28 system suffers from an issue "
+"known as <e>Speculative Execution</e>, a feature of the R10000 Processor "
+"that is problematic on machines that are <e>Non Cache Coherent</e>, such as "
+"the IP28 Indigo2 and on R10000/R12000-based IP32 O2 systems. Details on the "
+"nature of Speculative Execution, and the issues it poses to the Indigo2 can "
+"be found at the following URLs: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):349
+msgid "IP30: Octane"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):353
+msgid "<b>Processor Options (Experimental):</b> R10000, R12000, R14000A"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):379
+msgid ""
+"Octane support in Linux should be regarded as experimental. Support for this "
+"particular machine from SGI has been progressing quite well and the Linux "
+"kernel functions reasonably well. The current status for this system may be "
+"found on <uri link=\"http://www.linux-mips.org/~skylark/\">Stanislaw "
+"Skowronek's page</uri>. Wider support in Gentoo for this system will be "
+"available in the future, so watch this space closely for more details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):388
+msgid ""
+"The serial ports on the Octane currently only support 9600 baud rate, 8-"
+"bits, no parity, 1 stop bit. Other baud rates do not currently work at "
+"present."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):402
+msgid "Silicon Graphics Systems -- Unsupported"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):406
+msgid ""
+"Just about all of these systems are totally unsupported at the kernel level "
+"-- making a full Linux system totally impossible. Little is known about a "
+"lot of the systems listed here -- therefore any support in the near future "
+"is highly unlikely. You may wish to keep an eye on the <uri link=\"http://"
+"www.linux-mips.org\">Linux/MIPS website</uri> for any news of ports -- "
+"either that, or start your own. :-)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):416
+msgid "IP12: Iris Indigo (R3000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):417
+msgid "IP20: Iris Indigo (R4000 or R4400 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):418
+msgid "IP26: Indigo 2 Power (R8000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):419
+msgid "IP34: Fuel (R14000A or R16000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):420
+msgid "IP35: Origin 3000 (R14000 or R14000A CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):421
+msgid "IP45: Origin 300 (R14000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):422
+msgid "IP53: Origin 350 &amp; Tezro (R16000 CPU)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):430
+msgid "Silicon Graphics Accessories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):434
+msgid ""
+"As with most systems, there is quite wide array of peripherals that one can "
+"obtain for Silicon Graphics systems. While a lot of these work in IRIX, "
+"Linux support is a bit touch-and-go on some of these items. The following "
+"table lists the support for each device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):443
+msgid "Stable Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):444
+msgid "Experimental Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(th):445
+msgid "Unsupported/Untested"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):448
+msgid ""
+"Indy/Indigo2: XL Graphics Card (Newport)<br/> Indy/Indigo2: SGI Seeq "
+"Ethernet 10Mbps<br/> Indy/Indigo2: WD33C93 SCSI<br/> Indy/Indigo2: HAL2 "
+"Sound/Audio<br/> Indy/Indigo2: Parallel Port<br/> Indy/Indigo2: Serial "
+"Port<br/> O2: SGI MACE Ethernet 10/100Mbps<br/> O2: Adaptec AIC7880 SCSI<br/"
+"> O2: Serial Port<br/> Indigo2 ISA: Parallel Port Card (PC-Style)<br/> "
+"Indigo2 ISA: NE2000 Compatible 10Mbps NIC (RTL8019)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):461
+msgid ""
+"Indy: I2C/VINO subsystem &amp; IndyCam<br/> Indigo2 EISA: 3COM 3c597 "
+"10/100Mbps<br/> O2: GBE Framebuffer<br/> O2: PCI Slot<br/> Octane: "
+"Keyboard<br/> Octane: Mardi Gras (MGRAS) Graphics<br/> Octane: QLogic "
+"ISP1040B SCSI<br/> Octane: RAD1 Audio<br/> Octane: SMP Support<br/> Octane: "
+"V6/V8/V10/V12 Graphics (Odyssey)<br/> Origin: IOC3 Ethernet 10/100Mbps<br/> "
+"Origin: QLogic ISP1020 SCSI<br/> O2 PCI: ALi 5273 USB 2.0 (Req. Kernel &gt;"
+"=2.6.8.1)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(ti):476
+msgid ""
+"(1)Indy/Indigo2: Impact &amp; Extreme/XZ graphics chipsets<br/> Indy: Phobos "
+"G130 10/100Mbps NIC<br/> Indigo2: GIO64 Slots<br/> Indigo2: Phobos G160 "
+"10/100Mbps NIC<br/> Challenge S: WD33C95A SCSI Adapter/RJ-45 Daughter "
+"Card<br/> O2: VICE Subsystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(note):487
+msgid ""
+"(1) Work has begun on porting the ImpactSR to the Indigo2 Impact (IP28) "
+"workstation. At the moment, it's early days, and the driver is not "
+"functional yet, but this may change in the coming months.<br/> Likewise with "
+"Extreme graphics... a few people were starting to look into writing drivers "
+"for this chipset. Nothing has been released yet, but we may see something in "
+"the not too distant future.<br/> We will update this page if such a driver "
+"is released."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):502
+msgid "Cobalt Servers -- Stable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):506
+msgid ""
+"The Cobalt servers are a set of machines all based around the QED RM523[01] "
+"CPU. They came in two varieties, the RaQ -- a rackmounted model, and the "
+"Qube, a small desktop model (1ft. cube). The big difference between these "
+"systems and the SGI systems above, is that these systems are <e>little "
+"endian</e> (<c>mipsel</c>) as opposed to <e>big endian</e> (<c>mips</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):514
+msgid ""
+"These were also sold under an OEM arragement to other companies, examples of "
+"this are the Gateway Microserver (Qube 2) and the Seagate NasRaQ (RaQ 2)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):522
+msgid "Qube/Raq 2800 (a.k.a Qube/Raq 2)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):526
+msgid "<b>Processor:</b> QED RM5231 @ 250MHz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):538
+msgid "64-bit: <e>Highly Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):545
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):581
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):627
+msgid "n32: <e>Not Available In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):556
+msgid "Cobalt Servers -- Experimental"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):558
+msgid "Raq 2700 (a.k.a Raq 1)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):562
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):608
+msgid "<b>Processor:</b> QED RM5230 @ 150MHz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):567
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):613
+msgid "Linux 2.6: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):573
+msgid "32-bit: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):574
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):620
+msgid "64-bit: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):580
+msgid "o32: <e>Experimental</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):592
+msgid "Cobalt Servers -- Unsupported"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(title):594
+msgid "Qube 2700 (a.k.a Qube 1)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(p):597
+msgid ""
+"The Qube 2700 was the first of this whole subarchitecture. Unfortunately, it "
+"lacks a serial port, making installation at present, damn near impossible. "
+"We're looking into ways we can support this system, but as none of the "
+"developers have access to one of these machines, we have no way to test our "
+"efforts. You may wish to have a look at <uri link=\"http://www.metzner.org/"
+"projects/qube/\">Jan Metzner's page</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):612
+msgid "Linux 2.4: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):619
+msgid "32-bit: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(li):626
+msgid "o32: <e>Untested In Gentoo</e>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mips-requirements.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/multipath.xml.po b/doc/gettext/ru/multipath.xml.po
new file mode 100644
index 0000000..204b8e9
--- /dev/null
+++ b/doc/gettext/ru/multipath.xml.po
@@ -0,0 +1,526 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):6
+msgid "Multipathing for Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):17
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):9
+msgid "tsunam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):12
+msgid "matthew.summers@liquidustech.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail):12
+msgid "Matthew Summers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):15
+msgid "richard.anderson@liquidustech.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail):15
+msgid "Richard Anderson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):18
+msgid "steve.rucker@liquidustech.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail):18
+msgid "Steve Rucker"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(mail:link):21
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(abstract):24
+msgid ""
+"This document teaches you how to set up multipathing services for data "
+"storage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(version):32
+msgid "1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(date):33
+msgid "2008-09-10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):36
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):40
+msgid ""
+"Multipathing services, generally deployed in enterprise environments, "
+"provide a means for high performance, load-balanced, and fault-tolerant data "
+"storage either locally or via a storage area network (SAN). Multipathing "
+"facilitates a single storage device to be transparently accessed across one "
+"or more paths. For example, if there are two connections from a server Host "
+"Bus Adapter (HBA) to two Fibre Channel switches and then to a SAN, when the "
+"HBA module loads and scans the bus, it will read four paths to the SAN: the "
+"paths from the server HBA to and from each Fibre Channel switch and at the "
+"storage device. Taking advantage of this situation, Multipath allows you to "
+"make use of each path simultaneously or independently to ensure a constant "
+"and reliable connection to the data in storage. Multipath serves as a "
+"failover for all connections points in the event of losing one path making "
+"critical data always available due to redundancy in the design and "
+"implementation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):56
+msgid ""
+"In the most basic sense, multipathing is made of two distinct parts: "
+"<c>device-mapper</c> and <c>multipath-tools</c>. <b>Device Mapper</b> is the "
+"first key element of this application. Administrators are probably familiar "
+"with Device Mapper from LVM, EVMS, dm-crypt, or in this case, Multipath. In "
+"short, working within the kernel space Device Mapper takes one block device "
+"such as <path>/dev/sda</path> (as all SAN based targets will be some type of "
+"SCSI device) and maps it to another device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):66
+msgid ""
+"On a lower level, Device Mapper creates a virtual block device accepting all "
+"of the commands of a regular block device, but passes on the actual data to "
+"the real block device. As previously stated, the mapping process is all "
+"handled in the kernel space and not in user space."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):73
+msgid ""
+"<b>Multipath Tools</b> is a set of userspace tools that interacts with the "
+"Device Mapper tools and creates structures for device handling, implementing "
+"I/O multipathing at the OS level. In a typical SAN environment, you will "
+"have multiple paths to the same storage device: a fiber card (or two) on "
+"your server that connects to a switch which then connects to the actual "
+"storage itself (as in the scenario discussed above). So administrators could "
+"possibly see the same device one to four times in such a situation (each "
+"card will see the LUN twice, once for each path it has available to it). "
+"Thus, a single drive could be recognized as <path>sda</path>, <path>sdb</"
+"path>, <path>sdc</path>, and <path>sdd</path>. If you were to mount <path>/"
+"dev/sda</path> to <path>/san1</path>, for instance, you would be going over "
+"the singular path from one fiber card to a switch and then to a port on the "
+"same storage device. If any of those points were to fail, you would lose "
+"your storage device suddenly and have to unmount and remount with another "
+"device (<path>sdb</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):90
+msgid ""
+"Consequently, this scenario is not ideal as you are only using one out of "
+"the four possible paths. This is where the combination of Multipath tools "
+"and Device Mapper are beneficial. As already explained, Device Mapper "
+"creates virtual block devices and then passes information to the real block "
+"devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):102
+msgid "Installation and Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):104
+msgid "Installation and Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):107
+msgid ""
+"You need to emerge <c>multipath-tools</c> and <c>sg3_utils</c>. On the disk, "
+"you want to find the <c>wwid</c>. You can use <c>sq_vpd</c> (provided by "
+"<c>sg3_utils</c>) to do this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):113
+msgid "Installing multipath-tools and initial configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):113
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge multipath-tools sg3_utils</i>\n"
+"<comment>(Replace /dev/DEVICE with your disk to find its wwid)</comment>\n"
+"# <i>/usr/bin/sq_vpd ?page=di /dev/DEVICE</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):119
+msgid ""
+"Where DEVICE is the sd device, the ID will come back with a <c>0x6</c>. "
+"Replace <c>0x</c> with <c>3</c>, and you will have the proper ID that you'll "
+"put into the multipath <c>wwid</c> in <path>/etc/multipath.conf</path>. More "
+"on this in the next chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):129
+msgid "Configuring Gentoo for multipathing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):132
+msgid ""
+"To configure Gentoo for multipath, your kernel needs the following settings:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):136
+msgid "Adding multipath support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):136
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+"  SCSI device support  ---&gt;\n"
+"    &lt;*&gt; SCSI target support\n"
+"    &lt;*&gt; SCSI disk support\n"
+"    [*] Probe all LUNs on each SCSI device\n"
+"  [*] Multiple devices driver support (RAID and LVM)  ---&gt;\n"
+"    &lt;*&gt;  Multipath I/O support\n"
+"    &lt;*&gt;  Device mapper support\n"
+"    &lt;*&gt;    Multipath target\n"
+"        <comment>(Select your device from the list)</comment>)\n"
+"    &lt;*&gt;      EMC CX/AX multipath support  \n"
+"    &lt;*&gt;      LSI/Engenio RDAC multipath support  \n"
+"    &lt;*&gt;      HP MSA multipath support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(note):152
+msgid ""
+"<c>scsi_id</c> is done by targets. IDE drives have two spots to which you "
+"can connect. An administrator has the ability to set a drive as a master and "
+"another drive as a slave or set to autoselect by changing the dip switches. "
+"scsi_id is similar. Each drive or Logical Unit Number (LUN) has a unique ID, "
+"which ranges from 0 to 254. A device that has ID 0 will be discovered before "
+"a device that has, for example, ID 120, because it performs a LIP (a scan of "
+"the SCSI bus for devices that respond) that starts from 0 and works its way "
+"upwards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):162
+msgid ""
+"In the kernel menu config, make sure CONFIG_SCSI_MULTI_LUN=y is set to "
+"ensure the SCSI subsystem is able to probe all Logical Unit Numbers (LUNs) "
+"(This is recommended as you'll stop scanning after ID 0 if you have a device "
+"on an ID of <c>0</c> but not <c>1</c> and then on an ID of <c>2</c>. Simply, "
+"you'll get your device for ID <c>0</c> but not <c>2</c>.) or whichever "
+"device you need for SCSI, such as a QLogic 2400 card, which is in the SCSI "
+"low-level drivers area."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):171
+msgid "For a better understanding, consider the following scenarios:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):175
+msgid ""
+"There are three drives with IDs of 0,1,2. Without the \"probe all LUNs\" "
+"setting, you will see IDs 0,1,2 as sda,sdb,sdc - all devices are seen. If "
+"you delete the ID 1 drive. IDs 0,2 will still be seen. It might seem to make "
+"sense that you would see sda and sdb now (sdc would move to sdb as there is "
+"no device to fill it up). However, if you don't probe all LUNs, it will "
+"perform in the following manner:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):184
+msgid ""
+"Scenario 1: Without \"probe all LUNs\", the scan will start and ID 0 will be "
+"seen. ID 0 will be set to sda and then move to find ID 1. If ID 1 is not "
+"detected, scanning will stop and be considered complete having perceived to "
+"have scanned all devices even if there is a device on ID 2 or any other "
+"subsequent ID. Reboot for scenario two."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):192
+msgid ""
+"Scenario 2: If you have \"probe all LUNs\", the scan will start and detect "
+"ID 0. This ID will be assigned sda and will continue to detect the next "
+"device. If ID 1 is not detected, scanning will continue to find more "
+"devices. ID 2 will be located and assigned to be sdb. If no devices (IDs) "
+"are detected beyond that, scanning will be considered complete."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(note):200
+msgid ""
+"Although it seems that it is unfeasible or even unnecessary to have devices "
+"spaced many LUNs apart, to account for all options it is necessary to still "
+"probe all LUNs. An administrator will encounter many reasons (business or "
+"personal) for such a setup. Therefore, the second scenario would be optimal "
+"to ensure that all devices are recognized and assigned an ID in the "
+"multipath setup process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):209
+msgid ""
+"So, once you probe all LUNs, all devices will be recognized and assigned an "
+"ID in Multipath."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):219
+msgid "Architectural Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):223
+msgid ""
+"As part of Multipath Tools, there are priority groups filled with the "
+"devices mentioned earlier. After you have configured <c>multipath-tools</c> "
+"and started it with <c>/etc/init.d/multipath start</c>, you can list the "
+"groups via <c>multipath -l</c>. The output will look like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):230
+msgid "multipath -l output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):230
+#, no-wrap
+msgid ""
+"\n"
+"EVA_SAN (3600508b4001044ee00013000031e0000)\n"
+"[size=300 GB][features=\"1 queue_if_no_path\"][hwhandler=\"0\"]\n"
+"\\_ round-robin 0 [active]\n"
+"\\_ 0:0:0:1 sda 8:0  [active]\n"
+"\\_ round-robin 0 [enabled]\n"
+"\\_ 0:0:1:1 sdb 8:16 [active]\n"
+"\n"
+"EVA_SAN2 (3600508b4001044ee0001300003880000)\n"
+"[size=300 GB][features=\"1 queue_if_no_path\"][hwhandler=\"0\"]\n"
+"\\_ round-robin 0 [active]\n"
+"\\_ 0:0:0:2 sdc 8:32 [active]\n"
+"\\_ round-robin 0 [enabled]\n"
+"\\_ 0:0:1:2 sdd 8:48 [active]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):246
+msgid ""
+"By default, it will pick the first priority group (the first top round-robin "
+"for the EVA_SAN2, for instance, being <path>sdc</path>). In this instance, "
+"due to round robin it will bounce back and forth. But if one path was to "
+"fail, it would push all information to the other path and continue. Only if "
+"all the devices in a path fail will it actually fail and go to the secondary "
+"priority group."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):257
+msgid "Typical Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):260
+msgid "A typical Multipath configuration looks like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):264
+msgid "A typical /etc/multipath.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):264
+#, no-wrap
+msgid ""
+"\n"
+"defaults {\n"
+"udev_dir                /dev\n"
+"polling_interval        15\n"
+"selector                \"round-robin 0\"\n"
+"path_grouping_policy    group_by_prio\n"
+"failback                5\n"
+"path_checker            tur\n"
+"prio_callout            \"/sbin/mpath_prio_tpc /dev/%n\"\n"
+"rr_min_io               100\n"
+"rr_weight               uniform\n"
+"no_path_retry           queue\n"
+"user_friendly_names     yes\n"
+"}\n"
+"blacklist {\n"
+"devnode cciss\n"
+"devnode fd\n"
+"devnode hd\n"
+"devnode md\n"
+"devnode sr\n"
+"devnode scd\n"
+"devnode st\n"
+"devnode ram\n"
+"devnode raw\n"
+"devnode loop\n"
+"devnode sda\n"
+"}\n"
+"\n"
+"multipaths {\n"
+"multipath {\n"
+"wwid\n"
+"<comment>(To find your wwid, please use /usr/bin/sq_vpd ?page=di /dev/DEVICE.\n"
+"The address will be a 0x6. Remove the 0x and replace it with 3.)</comment>\n"
+"alias DB_SAN\n"
+"}\n"
+"devices {\n"
+"device {\n"
+"<comment>(White spacing is important on these two items to match the vendor specifications.)</comment>\n"
+"\"IBM     \"\n"
+"\"1815      FAStT \"\n"
+"}\n"
+"}\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(impo):309
+msgid ""
+"On your devices, it is best to <c>cat</c><path>/sys/block/sd(device)/device/"
+"model</path> and <c>cat</c><path>/sys/block/device/sd(device)/device/vendor</"
+"path>, placing both directly into your devices section in <path>/etc/"
+"multipath.conf</path>. You might not always see the white spacing, and it's "
+"part of the name in this case. One reason for the device section is that not "
+"every vendor's string is in the kernel convention and naming, and the "
+"string, as such, is not always detected as required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):320
+msgid ""
+"A typical multipath configuration utilizing an EVA_SAN where the device "
+"information is in the kernel information regarding SAN hardware detection "
+"would look like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre:caption):326
+msgid "EVA_SAN configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(pre):326
+#, no-wrap
+msgid ""
+"\n"
+"multipaths {\n"
+"multipath {\n"
+"wwid  3600508b4001044ee00013000031e0000\n"
+"alias EVA_SAN\n"
+"}\n"
+"multipath {\n"
+"wwid    3600508b4001044ee0001300003880000\n"
+"alias   EVA_SAN2\n"
+"}\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(title):344
+msgid "Setting Up Your Own Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):348
+msgid ""
+"The multipath configuration is fairly simple to accomplish because the only "
+"file that needs modification is <path>/etc/multipath.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):353
+msgid ""
+"To begin, set the <b>polling interview</b> to how often (in seconds) path "
+"checks will be performed to ensure that the path is alive and healthy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):358
+msgid "<b>selector</b> will be set at <c>\"round-robin 0\"</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(note):362
+msgid ""
+"This round-robin value is the only selector value that will be used in this "
+"configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):367
+msgid ""
+"<b>prio_callout</b>: This one can be quite important, and there are a number "
+"of different priorities for different devices, such as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):373
+msgid "mpath_prio_alua"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):374
+msgid "mpath_prio_emc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):375
+msgid "mpath_prio_hds_modular"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):376
+msgid "mpath_prio_netapp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(li):377
+msgid "mpath_prio_tpc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(note):380
+msgid ""
+"For most people, <c>mpath_prio_tpc</c> will suffice as it's a conservative "
+"checker. Other devices like <c>mpath_prio_netapp</c> have special "
+"functionality for priority grouping, such as netapps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):386
+msgid ""
+"<b>path_grouping_policy</b> has a few different options: failover, multibus, "
+"group_by_prio. <c>Failover</c> will only have one disk per priority group. "
+"<c>Multibus</c> will put all devices into one priority group. "
+"<c>Group_by_prio</c> is done by a \"priority value.\" So routes that have "
+"the same priority value will be grouped together, the priority values being "
+"determined by the callout."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):395
+msgid ""
+"<b>no_path_retry</b> is set to <c>queue</c> as most people don't want data "
+"to fail to send at all. So, if all paths fail, for instance, the I/Os will "
+"queue up until the device returns and then sends everything again. Depending "
+"on your transfer, this can cause load issues."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):402
+msgid ""
+"<b>rr_min_io</b> are the number of I/Os to do per path before switching to "
+"the next I/Os in the same group. If <path>sda</path> and <path>sdb</path> "
+"were in the same group, rr_min_io would do 100 I/Os to <path>sda</path> then "
+"do 100 to <path>sdb</path>, bouncing back and forth. This is a setting to "
+"tweak for each instance to maximize performance because the data load and "
+"size of transfers/request vary by company. The default in the case is "
+"<c>1000</c>, but some may prefer a smaller number in order to switch ports "
+"more often, when possible."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(p):413
+msgid ""
+"<b>user_friendly_names</b> make it easier to see which device you are "
+"working with. For example, if you set user_friendly_names to <c>no</c>, then "
+"you'll see WWID instead of EVA_SAN for your device."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//multipath.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/mysql-howto.xml.po b/doc/gettext/ru/mysql-howto.xml.po
new file mode 100644
index 0000000..65a0f84
--- /dev/null
+++ b/doc/gettext/ru/mysql-howto.xml.po
@@ -0,0 +1,1360 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(guide:link):5
+msgid "/doc/en/mysql-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):6
+msgid "MySQL Startup Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail:link):12
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail):12
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail:link):15
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(mail):15
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(abstract):18
+msgid "This document helps a user set up and use MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(version):26
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(date):27
+msgid "2006-08-08"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):30
+msgid "Getting Started With MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):32
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):35
+msgid ""
+"MySQL is a popular database server that is used in various applications. SQL "
+"stands for (S)tructured (Q)uery (L)anguage, which is what MySQL uses to "
+"communicate with other programs. On top of that, MySQL has its own expanded "
+"SQL functions to provide additional functionality to users. In this "
+"document, we'll look at how to do the initial MySQL installation, set up "
+"databases and tables, and create new users. Let's start out with the "
+"installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):47
+msgid "MySQL Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):50
+msgid ""
+"First make sure you have MySQL installed on your system. In case you need "
+"specific functionality from MySQL, please make sure you have the required "
+"USE flags enabled as they will help fine tune your installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):56
+msgid "Installing MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):56
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(View available USE flags)</comment>\n"
+"# <i>emerge --pretend --verbose mysql</i>\n"
+"<comment>(Install MySQL)</comment>\n"
+"# <i>emerge mysql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):63
+msgid "Upon completion of the installation, you will see the following notice:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):67
+msgid "MySQL einfo message"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):67
+#, no-wrap
+msgid ""
+"\n"
+"You might want to run:\n"
+"\"emerge --config =dev-db/mysql-[version]\"\n"
+"if this is a new install.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):73
+msgid ""
+"Since this is a new installation, we run the command. You need to press "
+"<c>ENTER</c> when prompted while configuring the MySQL database. The "
+"configuration sets up the main MySQL database which contains administrative "
+"information such as databases, tables, users, permissions and more. The "
+"configuration recommends that you change your root password as soon as "
+"possible. We will definitely do this, otherwise someone could come along by "
+"chance and hack our default setup MySQL server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):83
+msgid "MySQL configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):83
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace [version] with the version number you have just installed.)</comment>\n"
+"# <i>emerge --config =dev-db/mysql-[version]</i>\n"
+" * MySQL DATADIR is /var/lib/mysql\n"
+" * Press ENTER to create the mysql database and set proper\n"
+" * permissions on it, or Control-C to abort now...\n"
+"\n"
+"   Preparing db table\n"
+"   Preparing host table\n"
+"   Preparing user table\n"
+"   Preparing func table\n"
+"   Preparing tables_priv table\n"
+"   Preparing columns_priv table\n"
+"   Installing all prepared tables\n"
+"\n"
+"   To start mysqld at boot time you have to copy support-files/mysql.server\n"
+"   to the right place for your system\n"
+"\n"
+"   PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !\n"
+"   To do so, issue the following commands to start the server\n"
+"   and change the applicable passwords:\n"
+"<comment>(Note the next 3 lines)</comment>\n"
+"   /etc/init.d/mysql start\n"
+"   /usr/bin/mysqladmin -u root -h pegasos password 'new-password'\n"
+"   /usr/bin/mysqladmin -u root password 'new-password'\n"
+"   Depending on your configuration, a -p option may be needed\n"
+"   in the last command. See the manual for more details.\n"
+"\n"
+"<comment>(Some MySQL non-ebuild specific information has been removed from here\n"
+"so as to keep this document as consistent as possible)</comment>\n"
+"\n"
+"   * For security reasons you should set your MySQL root\n"
+"   * password as soon as possible.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(impo):118
+msgid ""
+"As of mysql-4.0.24-r2, passwords are entered during the config phase making "
+"root password entry more secure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):123
+msgid ""
+"The config script has already printed out the commands we need to run to "
+"setup our password, so we shall now run them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):128
+msgid "Setting up your MySQL root password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):128
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/mysql start</i>\n"
+" * Re-caching dependency info (mtimes differ)...\n"
+" * Starting mysqld (/etc/mysql/my.cnf) ...        [ ok ]\n"
+"<comment>(Replace new-password with your desired password)</comment>\n"
+"# <i>/usr/bin/mysqladmin -u root -h localhost password 'new-password'</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):136
+msgid ""
+"You can now test that your root password was successfully configured by "
+"trying to login to your MySQL server:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):141
+msgid "Logging into the MySQL server using mysql"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):141
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>mysql -u root -h localhost -p</i>\n"
+"Enter password:\n"
+"Welcome to the MySQL monitor. Commands end with ; or \\g.\n"
+"Your MySQL connection id is 4 to server version: 4.0.25\n"
+"\n"
+"Type 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n"
+"\n"
+"mysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):152
+msgid ""
+"The <c>-u</c> switch sets the user that will be logging in. The <c>-h</c> "
+"switch sets the host. This will usually be <c>localhost</c> unless you are "
+"setting up a remote server. Finally, <c>-p</c> tells the mysql client that "
+"you will be entering a password to access your database. Notice the "
+"<c>mysql&gt;</c> prompt. This is where you type in all your commands. Now "
+"that we're in the mysql prompt as the root user, we can begin to setup our "
+"database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):166
+msgid "Setting Up The Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):168
+msgid "Creating A Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):171
+msgid ""
+"We have logged in and a mysql prompt is displayed. First let's take a look "
+"at the databases we currently have. To do so, we use the <c>SHOW DATABASES</"
+"c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):177
+msgid "Displaying MySQL databases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):177
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SHOW DATABASES;</i>\n"
+"+----------+\n"
+"| Database |\n"
+"+----------+\n"
+"| mysql    |\n"
+"| test     |\n"
+"+----------+\n"
+"2 rows in set (0.09 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(impo):188
+msgid ""
+"Please remember that MySQL commands should end with a semicolon -- <c>;</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):192
+msgid ""
+"Despite the fact that a test database is already created, we are going to "
+"create our own. Databases are created using the <c>CREATE DATABASE</c> "
+"command. We'll create one named \"gentoo\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):198
+msgid "Creating the gentoo database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):198
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>CREATE DATABASE gentoo;</i>\n"
+"Query OK, 1 row affected (0.08 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):203
+msgid ""
+"The response lets us know that the command was executed without any errors. "
+"In this case, 1 row was modified. This is a reference to the main mysql "
+"database, which carries a list of all the databases. You won't need to worry "
+"too much about the background details. The last number is how fast the query "
+"was executed. We can verify the database was created by running the <c>SHOW "
+"DATABASES</c> command again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):212
+msgid "Verifing the database is created"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):212
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SHOW DATABASES;</i>\n"
+"+----------+\n"
+"| Database |\n"
+"+----------+\n"
+"| gentoo   |\n"
+"| mysql    |\n"
+"| test     |\n"
+"+----------+\n"
+"3 rows in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):224
+msgid ""
+"Indeed our database has been created. In order to work with creating tables "
+"for our new gentoo database, we need to select it as our current database. "
+"To do so, we use the <c>USE</c> command. The <c>USE</c> command takes the "
+"name of the database you wish to use as your current database. Another "
+"option is to set it on the command line after the <c>-D</c> switch. Let's go "
+"ahead and switch to the gentoo database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):233
+msgid "Switching our database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):233
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>USE gentoo;</i>\n"
+"Database changed\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):238
+msgid ""
+"And the current database is now our previously created gentoo database. Now "
+"that we're using it, we can start to create some tables and put information "
+"in them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):249
+msgid "Working With Tables In MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):251
+msgid "Creating a Table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):254
+msgid ""
+"In the structure of MySQL, there are databases, tables, records, and fields. "
+"Databases hold together tables, tables hold together records, records hold "
+"together fields, which contain the actual information. This structure lets "
+"users select how they want to access their information. So far we've dealt "
+"with databases, now let's work with tables. First off, tables can be listed "
+"similiarly to databases using the <c>SHOW TABLES</c> command. Right now "
+"there are no tables in our gentoo database, as running the command will show "
+"us:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):264
+msgid "Empty gentoo Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):264
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SHOW TABLES;</i>\n"
+"Empty set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):269
+msgid ""
+"This means we need to create some tables. In order to do so, we use the "
+"<c>CREATE TABLE</c> command. However, this command is quite different from "
+"simple <c>CREATE DATABASE</c> command. This command takes a list of "
+"arguments. The form is as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):276
+msgid "CREATE TABLE Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):276
+#, no-wrap
+msgid ""
+"\n"
+"CREATE TABLE [table_name] ([field_name] [field_data_type]([size]));\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):280
+msgid ""
+"<b>table_name</b> is the name of the table we wish to create. In this case, "
+"let's make a table named <c>developers</c>. This table will contain the "
+"developer's name, email and job. <b>field_name</b> will contain the name of "
+"the field. We have 3 required names in this case: name, email, and job. The "
+"<b>field_data_type</b> is what type of information will be stored. The "
+"different formats available can be found at the <uri link=\"http://dev.mysql."
+"com/doc/mysql/en/column-types.html\">MySQL Column Types Page</uri>. For our "
+"purposes, we'll use the <c>VARCHAR</c> data type for all of our fields. "
+"<c>VARCHAR</c> is one of the simplest of data types when it comes to working "
+"with strings. <b>size</b> is how much of data a single field will store. In "
+"this case, we'll use 128. This means that the field can have <c>VARCHAR</c> "
+"data that is 128 bytes. You can safely think of this as 128 characters for "
+"the time being, though there is a somewhat more technical explanation that "
+"the above site will provide you with. Now that we know how we are going to "
+"create the table, let's do it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):298
+msgid "Creating our table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):298
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>CREATE TABLE developers ( name VARCHAR(128), email VARCHAR(128), job VARCHAR(128));</i>\n"
+"Query OK, 0 rows affected (0.11 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):303
+msgid ""
+"Looks like our table was created ok. Let's check it with the <c>SHOW TABLES</"
+"c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):308
+msgid "Verifying our table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):308
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SHOW TABLES;</i>\n"
+"+------------------+\n"
+"| Tables_in_gentoo |\n"
+"+------------------+\n"
+"| developers       |\n"
+"+------------------+\n"
+"1 row in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):318
+msgid ""
+"Yes, there's our table. However, it doesn't seem to have any information on "
+"the types of fields we setup. For that, we use the <c>DESCRIBE</c> command "
+"(or <c>DESC</c> for short), which takes the name of the table as its "
+"argument. Let's see what that gives us for our developers table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):325
+msgid "Describing our developers table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):325
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>DESCRIBE developers;</i>\n"
+"+-------+--------------+------+-----+---------+-------+\n"
+"| Field | Type         | Null | Key | Default | Extra |\n"
+"+-------+--------------+------+-----+---------+-------+\n"
+"| name  | varchar(128) | YES  |     | NULL    |       |\n"
+"| email | varchar(128) | YES  |     | NULL    |       |\n"
+"| job   | varchar(128) | YES  |     | NULL    |       |\n"
+"+-------+--------------+------+-----+---------+-------+\n"
+"3 rows in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):337
+msgid ""
+"This shows the different fields and their types. It also shows a few extra "
+"attributes that are beyond the scope of this howto. Feel free to refer to "
+"the <uri link=\"http://dev.mysql.com/doc/mysql/en/\">MySQL Reference Manual</"
+"uri> for more information. We now have a table to work with. Now let's go "
+"ahead and populate it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):348
+msgid "Populating Our MySQL Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):351
+msgid ""
+"We populate a table (or add data) using the <c>INSERT</c> command. Like the "
+"<c>CREATE TABLE</c> command, it also has a specific format:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):356
+msgid "INSERT Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):356
+#, no-wrap
+msgid ""
+"\n"
+"INSERT INTO table (col1, col2, ...) VALUES('value1', 'value2', ...);\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):360
+msgid ""
+"This command is used to insert a record into table. table contains the MySQL "
+"table we wish to enter the information into. The table name may be followed "
+"by the list of columns to insert data into and <c>VALUES()</c> contains the "
+"values you wish to insert into the table. You may omit the list of columns "
+"if you insert a value into each one and if you write the values in the same "
+"order the columns have been defined. In this case, we want to insert data "
+"into the developers table. Let's insert sample records:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):370
+msgid "Inserting information into our developers table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):370
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>INSERT INTO developers VALUES('Joe Smith', 'joesmith@gentoo.org', 'toolchain');</i>\n"
+"Query OK, 1 row affected (0.06 sec)\n"
+"<comment>(If you don't know the order of the columns in the table or want to insert an incomplete record)</comment>\n"
+"mysql&gt; <i>INSERT INTO developers (job, name) VALUES('outsourced', 'Jane Doe');</i>\n"
+"Query OK, 1 row affected (0.01 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):378
+msgid ""
+"According to our return result, it appears that the record was inserted "
+"correctly. What if we want to input more information than just one record? "
+"That's where the <c>LOAD DATA</c> command comes into play. This loads "
+"records from a tab separated file. Let's try that by editing a file in our "
+"home directory with the records. We'll call this file <path>records.txt</"
+"path>. Here's a sample:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):387
+msgid "~/records.txt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):387
+#, no-wrap
+msgid ""
+"\n"
+"John Doe\tjohndoe@gentoo.org\tportage\n"
+"Chris White\tchriswhite@gentoo.org\tdocumentation\n"
+"Sam Smith\tsamsmith@gentoo.org\tamd64\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(impo):393
+msgid ""
+"Be sure you know what data you're dealing with. It's very unsafe to use "
+"<c>LOAD DATA</c> when you are uncertain of the file's contents!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):398
+msgid ""
+"Now the <c>LOAD DATA</c> command has a somewhat enlongated definition, but "
+"we'll use the simplest form here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):403
+msgid "LOAD DATA Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):403
+#, no-wrap
+msgid ""
+"\n"
+"LOAD DATA LOCAL INFILE '/path/to/filename' INTO TABLE table;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):407
+msgid ""
+"<path>/path/to/filename</path> is the directory and filename that will be "
+"used. table is the name of our table. In this case, our file is <path>~/"
+"records.txt</path> and the table is developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):413
+msgid "Loading in our data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):413
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>LOAD DATA LOCAL INFILE '~/records.txt' INTO TABLE developers;</i>\n"
+"Query OK, 3 rows affected (0.00 sec)\n"
+"Records: 3  Deleted: 0  Skipped: 0  Warnings: 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(impo):419
+msgid ""
+"If you come up with any strange behaviour, make sure your fields are "
+"separated by tabs. If you paste information into your infile from another "
+"source, it may convert your tabs to spaces."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):425
+msgid ""
+"That worked well. However, this simply inserts records, and does not give "
+"you any sort of control over MySQL. Many web applications use sql scripts in "
+"order to setup MySQL quickly and easily. If you want to use an sql script, "
+"you'll need to run mysql in batch mode, or source the file. Here's an "
+"example of running mysql in batch mode:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):433
+msgid "MySQL in batch mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):433
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>mysql -u root -h localhost -p &lt; sqlfile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):437
+msgid ""
+"Like <c>LOAD DATA</c>, be sure you can tell what <path>sqlfile</path> does. "
+"<e>Failure to do so may cause your database to be compromised!</e> Another "
+"way you can accomplish this is to use the <c>source</c> command. This "
+"command will run mysql commands from an sql file while in the mysql "
+"interactive mode. Here is how to source an sql file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):445
+msgid "Sourcing an sql file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):445
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>source sqlfile;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):449
+msgid ""
+"If you see a web application wanting you to run an sql file, the two above "
+"commands can be used to accomplish that task. We have our table setup, so "
+"how do we check our fields? We do this by searching our table with queries."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):458
+msgid "Browsing MySQL Tables With Queries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):461
+msgid ""
+"Queries are one of the main features of any SQL database. They help us turn "
+"data in our tables into something useful. Most queries are done with the "
+"<c>SELECT</c> command. The <c>SELECT</c> command is fairly complex, and "
+"we're only going to look at three main forms of the command in this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):468
+msgid "SELECT forms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):468
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Select all entries in a table)</comment>\n"
+"SELECT * FROM table;\n"
+"<comment>(Select specific entries in a table)</comment>\n"
+"SELECT * FROM table WHERE field=value;\n"
+"<comment>(Select specific fields)</comment>\n"
+"SELECT field1,field2,field3 FROM table [WHERE field=value];\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):477
+msgid ""
+"Let's take a quick look at the first form. It's relatively simple and gives "
+"you an overall look of your table. We'll go ahead and run it to see what "
+"data we have so far."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):483
+msgid "Contents of our table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):483
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):679
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SELECT * FROM developers;</i>\n"
+"+-------------+-----------------------+----------------+\n"
+"| name        | email                 | job            |\n"
+"+-------------+-----------------------+----------------+\n"
+"| Joe Smith   | joesmith@gentoo.org   | toolchain      |\n"
+"| John Doe    | johndoe@gentoo.org    | portage        |\n"
+"| Chris White | chriswhite@gentoo.org | documentation  |\n"
+"| Sam Smith   | samsmith@gentoo.org   | amd64          |\n"
+"| Jane Doe    | NULL                  | Outsourced job |\n"
+"+-------------+-----------------------+----------------+\n"
+"5 rows in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):497
+msgid ""
+"We see both the data we inserted through <c>INSERT</c> and those inserted by "
+"<c>LOAD DATA</c> present. Now, let's say that we just want to see the record "
+"for Chris White. We can do so with the second form of select as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):503
+msgid "Selecting a specific record using SELECT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):503
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SELECT * FROM developers WHERE name = 'Chris White';</i>\n"
+"+-------------+-----------------------+---------------+\n"
+"| name        | email                 | job           |\n"
+"+-------------+-----------------------+---------------+\n"
+"| Chris White | chriswhite@gentoo.org | documentation |\n"
+"+-------------+-----------------------+---------------+\n"
+"1 row in set (0.08 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):513
+msgid ""
+"As expected, the specific entry that we were looking for has been selected. "
+"Now, let's say we only wanted to know the person's job and email address, "
+"not their name. We can do so with the third form of <c>SELECT</c> as shown "
+"here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):519
+msgid "Selecting a specific record and fields using SELECT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):519
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SELECT email,job FROM developers WHERE name = 'Chris White';</i>\n"
+"+-----------------------+---------------+\n"
+"| email                 | job           |\n"
+"+-----------------------+---------------+\n"
+"| chriswhite@gentoo.org | documentation |\n"
+"+-----------------------+---------------+\n"
+"1 row in set (0.04 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):529
+msgid ""
+"This method of selection is a lot easier to manage, expecially with larger "
+"amounts of information, as we'll see later on. Right now, being the root "
+"mysql user, we have unlimited permissions to do what we wish with the MySQL "
+"database. In a server environment, a user with such privileges can be quite "
+"problematic. In order to control who does what with the databases, we setup "
+"privileges."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):543
+msgid "MySQL Privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):545
+msgid "Granting Privileges with GRANT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):548
+msgid ""
+"Privileges are what kind of access users have to databases, tables, pretty "
+"much anything. Right now in the gentoo database, the MySQL root account is "
+"the only account that can access it, given its permissions. Now, let's "
+"create two somewhat generic users, guest and admin, who will access the "
+"gentoo database and work with the information in it. The guest account will "
+"be a restricted one. All it will be able to do is get information from the "
+"database, and that's it. admin will have the same control as root, but only "
+"for the gentoo database (not the main mysql databases). Before we start on "
+"that, let's have a closer look at this somewhat simplified format of the "
+"<c>GRANT</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):560
+msgid "GRANT Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):560
+#, no-wrap
+msgid ""
+"\n"
+"GRANT [privileges] ON database.* TO '[user]'@'[host]' IDENTIFIED BY '[password]';\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(note):564
+msgid ""
+"<c>GRANT</c> is considered to be the way to create a user. Later versions of "
+"MySQL, however, do contain a <c>CREATE_USER</c> function, though <c>GRANT</"
+"c> is still preferred."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):570
+msgid ""
+"First we have the privileges we wish to assign. With what we've learned so "
+"far, here are some of the privileges you can set:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):576
+msgid "<c>ALL</c> - Gives the all privilege control for the database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):577
+msgid "<c>CREATE</c> - Allows users to create tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):578
+msgid "<c>SELECT</c> - Allows users to query tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):579
+msgid "<c>INSERT</c> - Allows users to insert data into a table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):580
+msgid "<c>SHOW DATABASES</c> - Allows users to see a list of databases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):581
+msgid "<c>USAGE</c> - User has no privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):582
+msgid "<c>GRANT OPTION</c> - Allows users to grant privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(note):585
+msgid ""
+"If you're running MySQL to communicate data to a web application, <c>CREATE</"
+"c>, <c>SELECT</c>, <c>INSERT</c> (discussed here), <c>DELETE</c> and "
+"<c>UPDATE</c> (for further infomation look up the <uri link=\"http://dev."
+"mysql.com/doc/mysql/en/grant.html\"> MySQL Reference Manual - GRANT and "
+"REVOKE Syntax</uri> section) are the only permissions you will most likely "
+"need. A lot of people make the mistake of granting all permissions when it's "
+"not really necessary. Check with the application developers to see if such "
+"permissions will cause issues with general operation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):597
+msgid ""
+"For our admin user, ALL will do. For the guest user, <c>SELECT</c> will be "
+"sufficient for read only access. database is the database we wish the user "
+"to have these permissions on. In this example, gentoo is the database. The ."
+"* means all tables. If you wanted to, you could apply per table access. user "
+"is the name of the user and host is the hostname the user will be accessing "
+"from. In most cases, this will be localhost. Finally, password is the user's "
+"password. Given the information, let's go ahead and create our users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):607
+msgid "Creating the admin and guest user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):607
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(admin)</comment>\n"
+"mysql&gt; <i>GRANT ALL ON gentoo.* TO 'admin'@'localhost' IDENTIFIED BY 'password';</i>\n"
+"<comment>(guest)</comment>\n"
+"mysql&gt; <i>GRANT SELECT ON gentoo.* TO 'guest'@'localhost' IDENTIFIED BY 'password';</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):614
+msgid ""
+"Now that we have the users setup, let's test them out. First we quit mysql "
+"by typing <c>quit</c> at the command prompt:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):619
+msgid "Quitting MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):619
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>quit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):623
+msgid ""
+"We're now back at the console. Now that we have our users setup, let's go "
+"ahead and see what they can do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):631
+msgid "Testing User Permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):634
+msgid ""
+"We shall now attempt to login as the guest user. Currently, the guest user "
+"has <c>SELECT</c> only privileges. This basically comes down to being able "
+"to search and nothing more. Go ahead and login with the guest account."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):640
+msgid "Logging in with the guest account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):640
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>mysql -u guest -h localhost -p</i>\n"
+"Enter password:\n"
+"Welcome to the MySQL monitor. Commands end with ; or \\g.\n"
+"Your MySQL connection id is 6 to server version: 4.0.25\n"
+"\n"
+"Type 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n"
+"\n"
+"mysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):651
+msgid ""
+"Now we should test the user restriction(s). Let's switch to the gentoo "
+"database:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):655
+msgid "Switching to the gentoo database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):655
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>USE gentoo;</i>\n"
+"Reading table information for completion of table and column names\n"
+"You can turn off this feature to get a quicker startup with -A\n"
+"\n"
+"Database changed\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):663
+msgid ""
+"Now let's try to do something we are not supposed to. We'll attempt to "
+"create a table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):668
+msgid "Attempting to create a table with the guest user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):668
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>CREATE TABLE test (test VARCHAR(20), foobar VARCHAR(2));</i>\n"
+"ERROR 1044: Access denied for user: 'guest@localhost' to database 'gentoo'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):673
+msgid ""
+"As you can see, this function fails, as our user does not have the "
+"appropriate access. However, one access we did grant is the <c>SELECT</c> "
+"statement. Let's go ahead and try that:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):679
+msgid "Attempting the SELECT statement"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):693
+msgid ""
+"The command succeeds, and we're given a glimpse of what user permissions can "
+"do. We did, however, create an admin account as well. This was created to "
+"show that even all permissions granted users can still have limitations. Go "
+"ahead and quit MySQL and login as the admin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):700
+msgid "Logging in as admin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):700
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>quit</i>\n"
+"Bye\n"
+"$ <i>mysql -u admin -h localhost -p</i>\n"
+"Enter password:\n"
+"Welcome to the MySQL monitor. Commands end with ; or \\g.\n"
+"Your MySQL connection id is 7 to server version: 4.0.25\n"
+"\n"
+"Type 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n"
+"\n"
+"mysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):713
+msgid ""
+"To begin, we'll try creating a new database with our admin user. This admin "
+"user will have access similiar to the root MySQL account, and will be able "
+"to do any kind of modification to the gentoo database it chooses. This will "
+"test the user's access to the main MySQL database. Remember ealier that we "
+"only set permissions to a specific database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):721
+msgid "Attempting to create a new database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):721
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>CREATE DATABASE gentoo2;</i>\n"
+"ERROR 1044: Access denied for user: 'admin@localhost' to database 'gentoo2'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):726
+msgid ""
+"Indeed, the admin user cannot create databases on the main MySQL database, "
+"despite all his permissions on the gentoo database. However, we're still "
+"able to use the admin account to modify the gentoo database, as shown here "
+"by this example data insertion."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):733
+msgid "Admin permissions in gentoo database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):733
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>USE gentoo;</i>\n"
+"Reading table information for completion of table and column names\n"
+"You can turn off this feature to get a quicker startup with -A\n"
+"\n"
+"Database changed\n"
+"mysql&gt; <i>INSERT INTO developers VALUES('Bob Simmons', 'bobsimmons@gentoo.org', 'python');</i>\n"
+"Query OK, 1 row affected (0.08 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):743
+msgid ""
+"The admin user can access the database as they please. Now sometimes, we "
+"need to get rid of user permissions. This could be anything from a "
+"problematic user to a retired employee. Let's take a look at how to disable "
+"user permissions with the <c>REVOKE</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):753
+msgid "Removing User Access With The REVOKE Command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):756
+msgid ""
+"The <c>REVOKE</c> command lets us deny access to a user. We can either deny "
+"full access, or specific access. In fact, the format is very similiar to "
+"<c>GRANT</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):762
+msgid "REVOKE Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):762
+#, no-wrap
+msgid ""
+"\n"
+"REVOKE [privileges] ON database.* FROM '[user]'@'[host]';\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):766
+msgid ""
+"Options here are explained in the <c>GRANT</c> command section. In this "
+"section however, we're going to deny full access to a user. Let's say we "
+"find out the guest account is causing some problems security wise. We decide "
+"to revoke all privileges. We login as root and do the needful."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):773
+msgid "Revoking user permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):773
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>REVOKE ALL ON gentoo.* FROM 'guest'@'localhost';</i>\n"
+"Query OK, 0 rows affected (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(note):778
+msgid ""
+"In this case, user access is simple, so per database revoking is not a "
+"problem. However, in larger cases, you would most likely be using *.* "
+"instead of gentoo.* to remove user access to all other databases."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):784
+msgid "Now let's quit and attempt to login as a guest user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):788
+msgid "Attempting guest user login"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):788
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>mysql -u guest -h localhost -p</i>\n"
+"Enter password:\n"
+"Welcome to the MySQL monitor. Commands end with ; or \\g.\n"
+"Your MySQL connection id is 9 to server version: 4.0.25\n"
+"\n"
+"Type 'help;' or '\\h' for help. Type '\\c' to clear the buffer.\n"
+"\n"
+"mysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):799
+msgid "Although we're able to login, our access to gentoo is now gone."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):803
+msgid "Denied access to guest account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):803
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>USE gentoo;</i>\n"
+"ERROR 1044: Access denied for user: 'guest@localhost' to database 'gentoo'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):808
+msgid ""
+"And our problematic user is no longer able to access the gentoo database. "
+"Please note that the user was still able to login. That is because they "
+"remain in the main MySQL database. Let's take a look at how to completely "
+"remove an account with <c>DELETE</c> and the MySQL user table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):818
+msgid "Removing Accounts Using DELETE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):821
+msgid ""
+"The MySQL user table is a listing of all users and information about them. "
+"Make sure you're logged in as root. Then go ahead and use the main MySQL "
+"database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):826
+msgid "Using the main mysql database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):826
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>USE mysql;</i>\n"
+"Reading table information for completion of table and column names\n"
+"You can turn off this feature to get a quicker startup with -A\n"
+"\n"
+"Database changed\n"
+"mysql&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):835
+msgid "Now let's see what tables the mysql database has:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):839
+msgid "mysql database table listing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):839
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SHOW TABLES;</i>\n"
+"+-----------------+\n"
+"| Tables_in_mysql |\n"
+"+-----------------+\n"
+"| columns_priv    |\n"
+"| db              |\n"
+"| func            |\n"
+"| host            |\n"
+"| tables_priv     |\n"
+"| user            |\n"
+"+-----------------+\n"
+"6 rows in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):854
+msgid ""
+"The user table is the table we're after. However, the user table contains 30 "
+"different fields, making it very hard to read. In order to make things "
+"easier to read, we'll go ahead and use the third version of the <c>SELECT</"
+"c> statement. The fields we're after are Host and User."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):861
+msgid "Finding our guest user in the user table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):861
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>SELECT Host,User FROM user WHERE User = 'guest';</i>\n"
+"+-----------+-------+\n"
+"| Host      | User  |\n"
+"+-----------+-------+\n"
+"| localhost | guest |\n"
+"+-----------+-------+\n"
+"1 row in set (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):871
+msgid ""
+"Now that we have our information, we can get rid of the guest user. This is "
+"done with the <c>DELETE</c> command and the syntax is shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):876
+msgid "DELETE Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):876
+#, no-wrap
+msgid ""
+"\n"
+"DELETE FROM table WHERE field='value';\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):880
+msgid ""
+"You may notice that <c>DELETE</c> is somewhat similiar to the <c>SELECT</c> "
+"statement in its format. In this case, the field will be User, and the value "
+"guest. This will delete the record in the user table where the user is "
+"guest, successfully deleting our guest user account. Let's go ahead and do "
+"that:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):887
+msgid "Deleting the guest account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):887
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>DELETE FROM user WHERE User='guest';</i>\n"
+"Query OK, 1 row affected (0.07 sec)\n"
+"<comment>(FLUSH PRIVILEGES is needed to update user permissions)</comment>\n"
+"mysql&gt; <i>FLUSH PRIVILEGES;</i>\n"
+"Query OK, 0 rows affected (0.00 sec)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):895
+msgid ""
+"It seems to have worked ok. Let's test by logging out and attempting to "
+"login as our guest user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre:caption):900
+msgid "Attempting login as the guest user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(pre):900
+#, no-wrap
+msgid ""
+"\n"
+"mysql&gt; <i>quit</i>\n"
+"Bye\n"
+"$ <i>mysql -u guest -h localhost -p</i>\n"
+"Enter password:\n"
+"ERROR 1045: Access denied for user: 'guest@localhost' (Using password: YES)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):908
+msgid "Our user is now successfully deleted!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(title):915
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):918
+msgid ""
+"While this guide focuses mainly on setting up MySQL on the command line, a "
+"few alternatives are available in GUI form:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):924
+msgid ""
+"<uri link=\"http://www.phpmyadmin.net/home_page/\">phpMyAdmin</uri> - "
+"Popular php based MySQL administration tool."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):928
+msgid ""
+"<uri link=\"http://sourceforge.net/projects/mysqlnavigator/"
+"\">mysqlnavigator</uri> - QT frontend to MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):933
+msgid ""
+"<uri link=\"http://gmyclient.sourceforge.net/\">gmyclient</uri> - A GNOME "
+"based MySQL client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(li):937
+msgid "<uri link=\"http://www.knoda.org/\">knoda</uri> - A KDE MySQL client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(p):940
+msgid ""
+"This ends the MySQL introductory tutorial. I hope this gives you a better "
+"understanding of the basics behind MySQL and getting a database set up. "
+"Please email me at <mail>chriswhite@gentoo.org</mail> if you have any "
+"comments."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mysql-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/mysql-upgrade-slotted.xml.po b/doc/gettext/ru/mysql-upgrade-slotted.xml.po
new file mode 100644
index 0000000..c7f28f4
--- /dev/null
+++ b/doc/gettext/ru/mysql-upgrade-slotted.xml.po
@@ -0,0 +1,102 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(guide:link):5
+msgid "/doc/en/mysql-upgrade-slotted.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(title):6
+msgid "\"Unslotting\" a slotted MySQL Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(mail:link):9
+msgid "vivo@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(mail):9
+msgid "Francesco Riosa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(mail:link):12
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(mail):12
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(abstract):15
+msgid "This document describes how to go back to an unslotted MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(version):23
+msgid "6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(date):24
+msgid "2006-03-10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(title):27
+msgid "Upgrading to an unslotted MySQL version from a slotted one"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(title):29
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(p):32
+msgid ""
+"Due to the negative response from our user base, the MySQL team has decided "
+"to go back to unslotted MySQL. In other words, installing different versions "
+"of MySQL on the same system is not supported anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(p):38
+msgid ""
+"If you had upgraded to the slotted version, this guide should help you "
+"upgrade to the unslotted version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(title):46
+msgid "\"Unslotting\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(p):49
+msgid "The following script should do most of the work:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(pre:caption):53
+msgid "\"Unslotting\" script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(p):90
+msgid ""
+"It is also recommended that you move data directories listed in <path>/etc/"
+"mysql/my.cnf</path>. If you do that, don't forget to edit <path>/etc/mysql/"
+"my.cnf</path> as well."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrade-slotted.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/mysql-upgrading.xml.po b/doc/gettext/ru/mysql-upgrading.xml.po
new file mode 100644
index 0000000..39f7d1d
--- /dev/null
+++ b/doc/gettext/ru/mysql-upgrading.xml.po
@@ -0,0 +1,601 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(guide:link):5
+msgid "/doc/en/mysql-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):6
+msgid "Upgrade guide to MySQL 4.* or 5.0.*"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(mail:link):9
+msgid "citizen428@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(mail):9
+msgid "Michael Kohl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(mail:link):12
+msgid "vivo@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(mail):12
+msgid "Francesco Riosa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(abstract):15
+msgid ""
+"The MySQL herd is proud to announce that MySQL 5.0 will soon be found in "
+"Gentoo's stable tree. This document describes how to upgrade to MySQL 4.* "
+"and to 5.0.*."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(version):25
+msgid "1.17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(date):26
+msgid "2007-06-04"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):29
+msgid "Straight upgrade, suggested for 4.1 =&gt; 5.0 migration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):33
+msgid ""
+"The myisam storage engine in version 4.1 was already mature enough to allow "
+"a direct upgrade to the next major version of MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(note):38
+msgid ""
+"This is not true for MERGE tables. You will likely run into trouble if you "
+"attempt a direct upgrade for this (rarely used) type of table. You should "
+"dump and recreate those tables and restore their contents in the process of "
+"upgrading. If unsure, you should begin with <uri link="
+"\"#doc_chap2\">Upgrading from old versions of MySQL</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):46
+msgid ""
+"For this step two shells are required because locks belong to the mysql "
+"session."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):51
+msgid "Straight upgrade from 4.1 to 5.0.*"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):51
+#, no-wrap
+msgid ""
+"\n"
+"# <i>quickpkg dev-db/mysql</i>\n"
+"# <i>alias MYSQL=\"mysql --user=root --password=</i><comment>'your_password'</comment><i>\"</i>\n"
+"# <i>DATADIR=$(MYSQL --batch --raw --silent --skip-column-names \\</i>\n"
+"     <i>--execute='SHOW variables LIKE \"datadir\";' \\</i>\n"
+"     <i>| sed -e 's|datadir[ \\t]||')</i>\n"
+"\n"
+"<comment>(This next step should be done in the second shell)</comment>\n"
+"# <i>mysql --user=root --password=</i><comment>'your_password'</comment>\n"
+"mysql&gt; <i>FLUSH TABLES WITH READ LOCK;</i>\n"
+"\n"
+"<comment>(Return to the first shell to run this command)</comment>\n"
+"# <i>tar -cjpvf ~/mysql.$(date +%F\"T\"%H-%M).tar.bz2 \\</i>\n"
+"     <i>/etc/conf.d/mysql /etc/mysql/my.cnf \"${DATADIR}\"</i>\n"
+"\n"
+"<comment>(The following commands should be done in the second shell)</comment>\n"
+"mysql&gt; <i>UNLOCK TABLES;</i>\n"
+"mysql&gt; <i>quit</i>\n"
+"\n"
+"<comment>(Return to the first shell for the rest of the upgrade)</comment>\n"
+"# <i>tar -tjvf ~/mysql.*.tar.bz2</i>\n"
+"# <i>emerge -av \"&gt;dev-db/mysql-5.0\"</i>\n"
+"# <i>dispatch-conf</i>\n"
+"# <i>revdep-rebuild</i>\n"
+"# <i>/etc/init.d/mysql restart</i>\n"
+"# <i>mysql_upgrade_shell --user=root --password=</i><comment>'your_password'</comment><i> \\</i>\n"
+"     <i>--protocol=tcp --datadir=\"${DATADIR}\"</i>\n"
+"# <i>/etc/init.d/mysql restart</i>\n"
+"# <i>unset DATADIR</i>\n"
+"# <i>unalias MYSQL</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):88
+msgid "Upgrading from old versions of MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):92
+msgid ""
+"Users upgrading from an old version (&lt;4.0.24) of MySQL will first have to "
+"install MySQL 4.0.25. If you are already running a more recent version, you "
+"can skip this section and continue with the <uri link=\"#backup\">next one</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):98
+msgid "Simple upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):98
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av --buildpkg \"&lt;mysql-4.1\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):107
+msgid "Creating a backup of your current data"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):111
+msgid ""
+"Values inside primary keys are handled differently in various MySQL "
+"versions, see <uri link=\"http://bugs.gentoo.org/108502\">bug #108502</uri> "
+"for more details, it is higly recommended to scan your tables for values of "
+"\"0\" (zero) or less and update them to a value greater than or equal to "
+"\"1\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):118
+msgid ""
+"One of the most important tasks that every database administrator has to "
+"perform is backing up data. Here we go:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):123
+msgid "Dump of all databases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):123
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mysqldump \\</i>\n"
+"  <i>-uroot \\</i>\n"
+"  <i>--password=</i><comment>'your_password'</comment><i> \\</i>\n"
+"  <i>-hlocalhost \\</i>\n"
+"  <i>--all-databases \\</i>\n"
+"  <i>--opt \\</i>\n"
+"  <i>--allow-keywords \\</i>\n"
+"  <i>--flush-logs \\</i>\n"
+"  <i>--hex-blob \\</i>\n"
+"  <i>--master-data \\</i>\n"
+"  <i>--max_allowed_packet=16M \\</i>\n"
+"  <i>--quote-names \\</i>\n"
+"  <i>--result-file=BACKUP_MYSQL_4.0.SQL</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):139
+msgid ""
+"Now a file named <path>BACKUP_MYSQL_4.0.SQL</path> should exist, which can "
+"be used later to recreate your data. The data is described in the MySQL "
+"dialect of SQL, the Structured Query Language."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):145
+msgid ""
+"Now would also be a good time to see if the backup you have created is "
+"working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):154
+msgid "Upgrading from recent versions of MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):158
+msgid ""
+"If you have skipped step #1, you now have to create a backup package (of the "
+"database server, not the data) of the currently installed version:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):163
+msgid "Binary package backup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):163
+#, no-wrap
+msgid ""
+"\n"
+"# <i>quickpkg dev-db/mysql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):167
+msgid "Now it's time to clean out the current version and all of its data:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):171
+msgid "Uninstall MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):171
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/mysql stop</i>\n"
+"# <i>emerge -C mysql</i>\n"
+"# <i>tar cjpvf ~/mysql.$(date +%F\"T\"%H-%M).tar.bz2 /etc/mysql/my.cnf /var/lib/mysql/</i>\n"
+"# <i>ls -l ~/mysql.*</i>\n"
+"# <i>rm -rf /var/lib/mysql/ /var/log/mysql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(note):179
+msgid ""
+"Now two different backups should exist: the SQL one, which is portable "
+"between various versions of MySQL, and the other one that will allow you to "
+"quickly restore your database. This is covered later in this document in "
+"more detail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):185
+msgid ""
+"After you get rid of your old MySQL installation, you can now install the "
+"new version. Note that <c>revdep-rebuild</c> is necessary for rebuilding "
+"packages linking against MySQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):191
+msgid "Upgrading the binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):191
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av \"&gt;mysql-4.1\"</i>\n"
+"<comment>(Update your config files, you may also use dispatch-conf)</comment>\n"
+"# <i>etc-update</i>\n"
+"# <i>revdep-rebuild</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):198
+msgid ""
+"Now configure the newly installed version of MySQL and restart the daemon:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):202
+msgid "Configure MySQL 4.1 base setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):202
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --config =mysql-4.1.<comment>&lt;micro_version&gt;</comment></i>\n"
+"# <i>/etc/init.d/mysql start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):207
+msgid "Finally you can import the backup you have created during step #2."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):211
+msgid ""
+"The default <path>/etc/mysql/my.cnf</path> file sets binary logging on "
+"(<c>log-bin</c>) by default. This will log every single transaction that "
+"modifies data. If run on a very large database (1GB or more), this could "
+"create extremely large files that take up disk space rather quickly. If you "
+"are low on space, disabling binary logging might be a good idea."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):219
+msgid ""
+"The default character set in MySQL 4.1 and above is <c>utf8</c>. If the data "
+"contain <e>non</e>-ASCII characters, you may want to preserve the default "
+"character set of the database replacing all occurrences of <c>utf8</c> with "
+"<c>latin1</c> in the <path>/etc/mysql/my.cnf</path> config file. More "
+"information can be found <uri link=\"#On_charset_conversion\">Charset "
+"conversion</uri> chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):228
+msgid ""
+"The administrative <c>mysql</c> database that contains user names, passwords "
+"amongst other things is and <b>must</b> be encoded in utf8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):233
+msgid ""
+"Older mysqldump utilities may export tables in the wrong order when foreign "
+"keys are involved. To work around this problem, surround the SQL with the "
+"following statements:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):239
+msgid "Fixing foreign key checks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):239
+#, no-wrap
+msgid ""
+"\n"
+"SET FOREIGN_KEY_CHECKS=0\n"
+"SET FOREIGN_KEY_CHECKS=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):244
+msgid "Next, import the backup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):248
+msgid "Importing the SQL backup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):248
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cat BACKUP_MYSQL_4.0.SQL \\</i>\n"
+"     <i>| mysql \\</i>\n"
+"     <i>-uroot \\</i>\n"
+"     <i>--password=</i><comment>'your_password'</comment><i> \\</i>\n"
+"     <i>-hlocalhost \\</i>\n"
+"     <i>--max_allowed_packet=16M</i>\n"
+"\n"
+"# <i>mysql_fix_privilege_tables \\</i>\n"
+"     <i>--defaults-file=/etc/mysql/my.cnf \\</i>\n"
+"     <i>--user=root \\</i>\n"
+"     <i>--password=</i><comment>'your_password'</comment><i></i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):262
+msgid ""
+"If you restart your MySQL daemon now and everything goes as expected, you "
+"have a fully working version of 4.1.x."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):267
+msgid "Restart the MySQL instance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):267
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/mysql restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):271
+msgid ""
+"If you encountered any problems during the upgrade process, please report "
+"them on <uri link=\"http://bugs.gentoo.org\">Bugzilla</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):281
+msgid "Recover the old installation of MySQL 4.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):285
+msgid ""
+"If you are not happy with MySQL 4.1, it's possible to go back to MySQL 4.0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):289
+msgid "Reverting to the previous version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):289
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/mysql stop</i>\n"
+"# <i>emerge -C mysql</i>\n"
+"# <i>rm -rf /var/lib/mysql/ /var/log/mysql</i>\n"
+"# <i>emerge --usepkgonly \"&lt;mysql-4.1\"</i>\n"
+"<comment>(Replace &lt;timestamp&gt; with the one used when creating the backup.)</comment>\n"
+"# <i>tar -xjpvf mysql.&lt;timestamp&gt;.tar.bz2 -C /</i>\n"
+"# <i>/etc/init.d/mysql start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(impo):299
+msgid ""
+"If packages other than <c>dev-db/mysql</c> have been emerged following this "
+"guide, you need to run <c>revdep-rebuild</c> to ensure that every client is "
+"using the correct mysqlclient shared object."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):310
+msgid "On charset conversion:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):312
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):315
+msgid ""
+"This chapter is not intended to be an exhaustive guide on how to do such "
+"conversions, rather a short list of hints on which the reader can elaborate."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):320
+msgid ""
+"Converting a database may be a complex task and difficulty increases with "
+"data variancy. Things like serialized object and blobs are one example where "
+"it's difficult to keeps pieces together."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):329
+msgid "Indexes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):332
+msgid ""
+"Every utf-8 character is considered 3 bytes long within an index. Indexes in "
+"MySQL can be up to 1000 bytes long (767 bytes for InnoDB tables). Note that "
+"the limits are measured in bytes, whereas the length of a column is "
+"interpreted as number of characters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):339
+msgid ""
+"MySQL can also create indexes on parts of a column, this can be of some "
+"help. Below are some examples:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):344
+msgid "Indexing using prefixes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):344
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>mysql -uroot -p'<comment>your_password</comment>' test</i>\n"
+"\n"
+"mysql&gt; <i>SHOW variables LIKE \"version\" \\G</i>\n"
+"*************************** 1. row ***************************\n"
+"Variable_name: version\n"
+"    Value: <comment>5.0.24-log</comment>\n"
+"1 row in set (0.00 sec)\n"
+"\n"
+"mysql&gt; <i>CREATE TABLE t1 (</i>\n"
+"  -&gt;   <i>c1 varchar(255) NOT NULL default '',</i>\n"
+"  -&gt;   <i>c2 varchar(255) NOT NULL default ''</i>\n"
+"  -&gt;   <i>) ENGINE=MyISAM DEFAULT CHARSET=utf8;</i>\n"
+"Query OK, 0 rows affected (0.01 sec)\n"
+"\n"
+"mysql&gt; <i>ALTER TABLE t1</i>\n"
+"  -&gt;   <i>ADD INDEX idx1 ( c1 , c2 );</i>\n"
+"<comment>ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes</comment>\n"
+"\n"
+"mysql&gt; <i>ALTER TABLE t1</i>\n"
+"  -&gt;   <i>ADD INDEX idx1 ( c1(165) , c2(165) );</i>\n"
+"Query OK, 0 rows affected (0.01 sec)\n"
+"Records: 0  Duplicates: 0  Warnings: 0\n"
+"\n"
+"mysql&gt; <i>CREATE TABLE t2 (</i>\n"
+"  -&gt;   <i>c1 varchar(255) NOT NULL default '',</i>\n"
+"  -&gt;   <i>c2 varchar(255) NOT NULL default ''</i>\n"
+"  -&gt;   <i>) ENGINE=MyISAM DEFAULT CHARSET=sjis;</i>\n"
+"Query OK, 0 rows affected (0.00 sec)\n"
+"\n"
+"mysql&gt; <i>ALTER TABLE t2</i>\n"
+"  -&gt;   <i>ADD INDEX idx1 ( c1(250) , c2(250) );</i>\n"
+"Query OK, 0 rows affected (0.03 sec)\n"
+"Records: 0  Duplicates: 0  Warnings: 0\n"
+"\n"
+"mysql&gt; <i>CREATE TABLE t3 (</i>\n"
+"  -&gt;   <i>c1 varchar(255) NOT NULL default '',</i>\n"
+"  -&gt;   <i>c2 varchar(255) NOT NULL default ''</i>\n"
+"  -&gt;   <i>) ENGINE=MyISAM DEFAULT CHARSET=latin1;</i>\n"
+"Query OK, 0 rows affected (0.00 sec)\n"
+"\n"
+"mysql&gt; <i>ALTER TABLE t3</i>\n"
+"  -&gt;   <i>ADD INDEX idx1 ( c1 , c2 );</i>\n"
+"Query OK, 0 rows affected (0.03 sec)\n"
+"Records: 0  Duplicates: 0  Warnings: 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):394
+msgid "Environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):397
+msgid ""
+"The system must be configured to support the UTF-8 locale. You will find "
+"more information in our <uri link=\"/doc/en/utf-8.xml\">Using UTF-8 with "
+"Gentoo</uri> and <uri link=\"/doc/en/guide-localization.xml\">Localization "
+"Guide</uri> documents."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):404
+msgid ""
+"In this example, we set some shell environment variables to make use of the "
+"English UTF-8 locale in <path>/etc/env.d/02locale</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):409
+msgid "/etc/env.d/02locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):409
+#, no-wrap
+msgid ""
+"\n"
+"LC_ALL=en_US.UTF-8\n"
+"LANG=en_US.UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):414
+msgid ""
+"Be sure to run <c>env-update &amp;&amp; source /etc/profile</c> afterward."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):421
+msgid "iconv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):424
+msgid ""
+"<c>iconv</c>, provided by <c>sys-libs/glibc</c>, is used to convert text "
+"files from one charset to another. The <c>app-text/recode</c> package can be "
+"used as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre:caption):430
+msgid "Using iconv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(pre):430
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(From latin1 to utf8)</comment>\n"
+"$ <i>iconv -f ISO-8859-15 -t UTF-8 file1.sql &gt; file2.sql</i>\n"
+"\n"
+"<comment>(From Japanese to utf8)</comment>\n"
+"$ <i>iconv -f ISO2022JP -t UTF-8 file1.sql &gt; file2.sql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):438
+msgid ""
+"<c>iconv</c> can be used to recode a sql dump even if the environment is not "
+"set to utf8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):446
+msgid "SQL Mangling"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):449
+msgid ""
+"It's possible to use the <c>CONVERT()</c> and <c>CAST()</c> MySQL functions "
+"to convert data in your SQL scripts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(title):457
+msgid "Apache (webserver)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(p):460
+msgid ""
+"To use utf-8 with apache, you need to adjust the following variables in "
+"<path>httpd.conf</path>: AddDefaultCharset, CharsetDefault, "
+"CharsetSourceEnc. If your source html files aren't encoded in utf-8, they "
+"<b>must</b> be converted with <c>iconv</c> or <c>recode</c>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//mysql-upgrading.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/nagios-guide.xml.po b/doc/gettext/ru/nagios-guide.xml.po
new file mode 100644
index 0000000..fc91efb
--- /dev/null
+++ b/doc/gettext/ru/nagios-guide.xml.po
@@ -0,0 +1,573 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):6
+msgid "Gentoo System Monitoring with Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(abstract):12
+msgid ""
+"For system and network monitoring, the Nagios tool is a popular choice "
+"amongst various free software users. This guide helps you discover Nagios "
+"and how you can integrate it with your existing Gentoo infrastructure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(version):20
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(date):21
+msgid "2010-03-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):24
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):225
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):26
+msgid "System Monitoring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):29
+msgid ""
+"Single system users usually don't need a tool to help them identify the "
+"state of their system. However, when you have a couple of systems to "
+"administer, you will require an overview of your systems' health: do the "
+"partitions still have sufficient free space, is your CPU not overloaded, how "
+"many people are logged on, are your systems up to date with the latest "
+"security fixes, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):37
+msgid ""
+"System monitoring tools, such as the Nagios software we discuss here, offer "
+"an easy way of dealing with the majority of metrics you want to know about "
+"your system. In larger environments, often called \"enterprise environments"
+"\", the tools aggregate the metrics of the various systems onto a single "
+"location, allowing for centralized monitoring management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):48
+msgid "About Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):51
+msgid ""
+"The <uri link=\"http://www.nagios.org\">Nagios</uri> software is a popular "
+"software tool for host, service and network monitoring for Unix (although it "
+"can also capture metrics from the Microsoft Windows operating system "
+"family). It supports:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):59
+msgid ""
+"obtaining metrics for local system resources, such as diskspace, CPU usage, "
+"memory consumption, ..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):63
+msgid ""
+"discovering service availability (such as SSH, SMTP and other protocols),"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):66
+msgid ""
+"assuming network outages (when a group of systems that are known to be "
+"available on a network are all unreachable),"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):72
+msgid "and more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):76
+msgid ""
+"Basically, the Nagios software consists of a core tool (which manages the "
+"metrics), a web server module (which manages displaying the metrics) and a "
+"set of plugins (which obtain and send the metrics to the core tool)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):85
+msgid "About this Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):88
+msgid ""
+"The primary purpose of this document is to introduce you, Gentoo users, to "
+"the Nagios software and how you can integrate it within your Gentoo "
+"environment. The guide is not meant to describe Nagios in great detail - I "
+"leave this up to the documentation editors of Nagios itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):99
+msgid "Setting Up Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):101
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):121
+msgid "Installing Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):104
+msgid ""
+"Before you start installing Nagios, draw out and decide which system will "
+"become your master Nagios system (i.e. where the Nagios software is fully "
+"installed upon and where all metrics are stored) and what kind of metrics "
+"you want to obtain. You will not install Nagios on every system you want to "
+"monitor, but rather install Nagios on the master system and the TODO on the "
+"systems you want to receive metrics from."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):113
+msgid "Install the Nagios software on your central server:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(warn):117
+msgid ""
+"Nagios 3 is currently still ~arch masked, so you first need to unmask it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):121
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge nagios</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):125
+msgid ""
+"Follow the instructions the ebuild displays at the end of the installation "
+"(i.e. adding <c>nagios</c> to your active runlevel, configuring web server "
+"read access and more)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):131
+msgid "Really. Read it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):140
+msgid "Restricting Access to the Nagios Web Interface"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):143
+msgid ""
+"The Nagios web interface allows for executing commands on the various "
+"systems monitored by the Nagios plugins. For this purpose (and also because "
+"the metrics can have sensitive information) it is best to restrict access to "
+"the interface."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):149
+msgid ""
+"For this purpose, we introduce two access restrictions: one on IP level "
+"(from what systems can a user connect to the interface) and a basic "
+"authentication one (using the username / password scheme)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):155
+msgid ""
+"First, edit <path>/etc/apache2/modules/99_nagios3.conf</path> and edit the "
+"<c>allow from</c> definitions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):160
+msgid "Allow from definitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):160
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Example allowing access from the local host and the local network)</comment>\n"
+"Order allow,deny\n"
+"Allow from 127.0.0.1 192.168.1.1/24\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):166
+msgid ""
+"Next, create an Apache authorization table where you define the users who "
+"have access to the interface as well as their authorizations. The "
+"authentication definition file is called <path>.htaccess</path> and contains "
+"where the authentication information itself is stored."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):173
+msgid "Example .htaccess file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):173
+#, no-wrap
+msgid ""
+"\n"
+"AuthName \"Nagios Access\"\n"
+"AuthType Basic\n"
+"AuthUserFile /etc/nagios/auth.users\n"
+"Require valid-user\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):180
+msgid ""
+"Place this file inside the <path>/usr/share/nagios/htdocs</path> and <path>/"
+"usr/lib/nagios/cgi-bin</path> directories."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):185
+msgid ""
+"Create the <path>/etc/nagios/auth.users</path> file with the necessary user "
+"credentials. By default, the Gentoo nagios ebuild defines a single user "
+"called <c>nagiosadmin</c>. Let's create that user first:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):191
+msgid "Creating the nagiosadmin user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):191
+#, no-wrap
+msgid ""
+"\n"
+"# <i>htpasswd2 -c /etc/nagios/auth.users nagiosadmin</i>\n"
+"<comment>(Apache needs read access to auth.users)</comment>\n"
+"# <i>chown nagios:nagios /etc/nagios/auth.users</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):200
+msgid "Accessing Nagios"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):203
+msgid ""
+"Once Nagios and its dependencies are installed, fire up Apache and Nagios:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):207
+msgid "Starting the services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):207
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/nagios start</i>\n"
+"# <i>/etc/init.d/apache2 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):212
+msgid ""
+"Next, fire up your browser and connect to <uri link=\"http://localhost/nagios"
+"\">http://localhost/nagios</uri>. Log on as the <c>nagiosadmin</c> user and "
+"navigate to the <e>Host Detail</e> page. You should be able to see the "
+"monitoring states for the local system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):223
+msgid "Installing Client Daemons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):228
+msgid "There are various methods available to monitor remote hosts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):233
+msgid ""
+"Use the <e>NRPE</e> daemon on the remote host and have Nagios communicate to "
+"this daemon using the <path>check_nrpe</path> plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):237
+msgid "Use a password-less SSH connection to execute the command remotely"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):240
+msgid "Trap SNMP events and create Nagios alerts from it"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):245
+msgid ""
+"We focus on using the NRPE method as it is the most popular one and leave "
+"the other methods as an interesting excercise."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):253
+msgid "Installing NRPE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):256
+msgid ""
+"With NRPE, each remote host runs a daemon (the NRPE deamon) which allows the "
+"main Nagios system to query for certain metrics. One can run the NRPE daemon "
+"by itself or use an inetd program. I'll leave the inetd method as a nice "
+"exercise to the reader and give an example for running NRPE by itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):263
+msgid "First install the NRPE plugin:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):267
+msgid "Installing the NRPE plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):267
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge nagios-nrpe</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):271
+msgid ""
+"Next, edit <path>/etc/nagios/nrpe.cfg</path> to allow your main Nagios "
+"system to access the NRPE daemon and customize the installation to your "
+"liking. Another important change to the <path>nrpe.cfg</path> file is the "
+"list of commands that NRPE supports. For instance, to use <c>nagios-nrpe</c> "
+"version 2.12 with Nagios 3, you'll need to change the paths from <path>/usr/"
+"nagios/libexec</path> to <path>/usr/lib/nagios/plugins</path>. Finally, "
+"launch the NRPE daemon:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):280
+msgid "Launching the NRPE daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):280
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/nrpe start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):284
+msgid ""
+"Finally, we need to configure the main Nagios system to connect to this "
+"particular NRPE instance and request the necessary metrics. To introduce you "
+"to Nagios' object syntax, our next section will cover this a bit more "
+"throroughly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):293
+msgid "Configuring a Remote Host"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(note):296
+msgid ""
+"The following hands-on tutorial is an example, used to introduce the user to "
+"Nagios' object model. Do not see this as the \"Best Practice\" for "
+"configuring Nagios."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):302
+msgid ""
+"First, edit <path>/etc/nagios/nagios.cfg</path> and place a <c>cfg_dir</c> "
+"directive. This will tell Nagios to read in all object configuration files "
+"in the said directory - in our example, the directory will contain the "
+"definitions for remote systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):309
+msgid "Editing /etc/nagios/nagios.cfg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):309
+#, no-wrap
+msgid ""
+"\n"
+"cfg_dir=/etc/nagios/objects/remote\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):313
+msgid ""
+"Create the directory and start with the first file, <path>nrpe-command.cfg</"
+"path>. In this file, we configure a Nagios command called <c>check_nrpe</c> "
+"which will be used to trigger a plugin (identified by the placeholder <c>"
+"$ARG1$</c>) on the remote system (identified by the placeholder <c>"
+"$HOSTADDRESS$</c>). The <c>$USER1$</c> variable is a default pointer to the "
+"Nagios installation directory (for instance, <path>/usr/nagios/libexec</"
+"path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):323
+msgid "Defining the check_nrpe command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):323
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/nagios/objects/remote/nrpe-command.cfg</i>\n"
+"\n"
+"define command {\n"
+"  command_name check_nrpe\n"
+"  command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):332
+msgid ""
+"Next, create a file <path>nrpe-hosts.cfg</path> where we define the remote "
+"host(s) to monitor. In this example, we define two remote systems:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):337
+msgid "Defining two remote hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):337
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/nagios/objects/remote/nrpe-hosts.cfg</i>\n"
+"\n"
+"define host {\n"
+"  use linux-server\n"
+"  host_name webber\n"
+"  alias Gentoo Linux Web Server\n"
+"  address 192.168.2.1\n"
+"}\n"
+"\n"
+"define host {\n"
+"  use linux-server\n"
+"  host_name isync\n"
+"  alias Gentoo Linux RSync server\n"
+"  address 192.168.2.2\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):355
+msgid ""
+"Finally, define the service(s) you want to check on these hosts. As a prime "
+"example, we run the system load test and disk usage plugins:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre:caption):360
+msgid "Define the services to check"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(pre):360
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/nagios/objects/remote/nrpe-services.cfg</i>\n"
+"\n"
+"define service {\n"
+"  use generic-service\n"
+"  host_name webber,isync\n"
+"  service_description Current Load\n"
+"  check_command check_nrpe!check_load\n"
+"}\n"
+"\n"
+"define service {\n"
+"  use generic-service\n"
+"  host_name webber,isync\n"
+"  service_description Root Partition\n"
+"  check_command check_nrpe!check_disk\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):378
+msgid ""
+"That's it. If you now check the service details on the Nagions monitoring "
+"site you'll see that the remote hosts are connected and are transmitting "
+"their monitoring metrics to the Nagios server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):387
+msgid "Using Passwordless SSH Connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):390
+msgid ""
+"Just as we did by creating the <c>check_nrpe</c> command, we can create a "
+"command that executes a command remotely through a passwordless SSH "
+"connection. We leave this up as an interesting exercise to the reader."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):396
+msgid "A few pointers and tips:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):401
+msgid ""
+"Make sure the passwordless SSH connection is set up for a dedicated user "
+"(definitely not root) - most checks you want to execute do not need root "
+"privileges anyway"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):406
+msgid ""
+"Creating a passwordless SSH key can be accomplished with <c>ssh-keygen</c>, "
+"you install a key on the destination system by adding the public key to the "
+"<path>.ssh/authorized_keys</path> file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):417
+msgid "More Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):419
+msgid "Adding Gentoo Checks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(p):422
+msgid ""
+"It is quite easy to extend Nagios to include Gentoo-specific checks, such as "
+"security checks (GLSAs). Gentoo developer Wolfram Schlich has a "
+"<c>check_glsa.sh</c> script <uri link=\"http://dev.gentoo.org/~wschlich/misc/"
+"nagios/nagios-plugins-extra/nagios-plugins-extra-4/plugins/\">available</"
+"uri> amongst others."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(title):433
+msgid "Nagios Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):437
+msgid "<uri>http://www.nagios.org</uri>, the official Nagios website"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):440
+msgid ""
+"<uri>http://www.nagiosexchange.org</uri>, where you can find Nagios plugins "
+"and addons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):444
+msgid ""
+"<uri>http://www.nagiosforge.org</uri>, where developers host Nagios addon "
+"projects"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(li):448
+msgid ""
+"<uri>http://www.nagioswiki.org</uri>, for more information and tutorials on "
+"Nagios"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//nagios-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/nano-basics-guide.xml.po b/doc/gettext/ru/nano-basics-guide.xml.po
new file mode 100644
index 0000000..c95cee0
--- /dev/null
+++ b/doc/gettext/ru/nano-basics-guide.xml.po
@@ -0,0 +1,206 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(guide:link):5
+msgid "/doc/en/nano-basics-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):7
+msgid "Nano Basics Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(author:title):9
+msgid "Gentoo Doc Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(author):9
+msgid "Sherman Boyd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(author:title):12
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(mail:link):13
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(mail):13
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(abstract):16
+msgid ""
+"This guide is meant to be a simple introduction to nano. It will quickly "
+"help you to become familiar with its basic operation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(version):21
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(date):22
+msgid "2006-01-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):25
+msgid "Nano Basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):27
+msgid "Purpose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):30
+msgid ""
+"This guide was written to cover basic operations in nano, and is meant to be "
+"very concise. For more information about nano check out:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(uri):36
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(uri):153
+msgid "http://www.nano-editor.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):42
+msgid "Opening and creating files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):45
+msgid "Opening and creating files is simple in nano, simply type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(pre:caption):49
+msgid "Creating or opening a file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(pre):49
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano filename</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):53
+msgid ""
+"Nano is a modeless editor so you can start typing immediately to insert "
+"text. If you are editing a configuration file like <path>/etc/fstab</path> "
+"use the <c>-w</c> switch, for example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(pre:caption):59
+msgid "Disable the word wrapping"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(pre):59
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/fstab</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(warn):63
+msgid ""
+"It is very, very important that you use the <c>-w</c> switch when opening a "
+"config file. Failure to do so may keep your system from booting or cause "
+"other bad things."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):72
+msgid "Saving and exiting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):75
+msgid ""
+"If you want to save the changes you've made, press <c>Ctrl+O</c>. To exit "
+"nano, type <c>Ctrl+X</c>. If you ask nano to exit from a modified file, it "
+"will ask you if you want to save it. Just press <c>N</c> in case you don't, "
+"or <c>Y</c> in case you do. It will then ask you for a filename. Just type "
+"it in and press <c>Enter</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):83
+msgid ""
+"If you accidentally confirmed that you want to save the file but you "
+"actually don't, you can always cancel by pressing <c>Ctrl+C</c> when you're "
+"prompted for a filename."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):92
+msgid "Cutting and pasting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):95
+msgid ""
+"To cut a single line, you use <c>Ctrl+K</c> (hold down <c>Ctrl</c> and then "
+"press <c>K</c>). The line disappears. To paste it, you simply move the "
+"cursor to where you want to paste it and punch <c>Ctrl+U</c>. The line "
+"reappears. To move multiple lines, simply cut them with several <c>Ctrl+K</"
+"c>s in a row, then paste them with a single <c>Ctrl+U</c>. The whole "
+"paragraph appears wherever you want it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):104
+msgid ""
+"If you need a little more fine-grained control, then you have to mark the "
+"text. Move the cursor to the beginning of the text you want to cut. Hit "
+"<c>Ctrl+6</c> (or <c>Alt+A</c>). Now move your cursor to the end of the text "
+"you want to cut: the marked text gets highlighted. If you need to cancel "
+"your text marking, simply hit <c>Ctrl+6</c> again. Press <c>Ctrl+K</c> to "
+"cut the marked text. Use <c>Ctrl+U</c> to paste it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):116
+msgid "Searching for text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):119
+msgid ""
+"Searching for a string is easy as long as you think <e>\"WhereIs\"</e> "
+"instead of <e>\"Search\"</e>. Simply hit <c>Ctrl+W</c>, type in your search "
+"string, and press <c>Enter</c>. To search for the same string again, hit "
+"<c>Alt+W</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(note):125
+msgid ""
+"In nano's help texts the Ctrl-key is represented by a caret (<c>^</c>), so "
+"<c>Ctrl+W</c> is shown as <c>^W</c>, and so on. The Alt-key is represented "
+"by an <c>M</c> (from \"Meta\"), so <c>Alt+W</c> is shown as <c>M-W</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):134
+msgid "More options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):137
+msgid ""
+"If you're interested in tweaking nano, be sure to read <path>/etc/nanorc</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(title):144
+msgid "Wrap up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(p):147
+msgid ""
+"That is all! Thanks to kiyose and quazion from #gentoo. Again, for more "
+"information about nano check out:"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//nano-basics-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/new-upgrade-to-gentoo-1.4.xml.po b/doc/gettext/ru/new-upgrade-to-gentoo-1.4.xml.po
new file mode 100644
index 0000000..d6f894c
--- /dev/null
+++ b/doc/gettext/ru/new-upgrade-to-gentoo-1.4.xml.po
@@ -0,0 +1,328 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(guide:link):7
+msgid "/doc/en/new-upgrade-to-gentoo-1.4.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):9
+msgid "Gentoo 1.4 Upgrade Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(mail:link):12
+msgid "rac@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(mail):12
+msgid "Robert Coie"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(author:title):14
+msgid "Copy Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(mail:link):15
+msgid "avenj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(mail):15
+msgid "Jon Portnoy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(abstract):18
+msgid ""
+"A method for upgrading older Gentoo installations in place to Gentoo 1.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(version):26
+msgid "0.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(date):27
+msgid "2005-07-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):30
+msgid "Before you begin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):32
+msgid "Be prepared"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):35
+msgid ""
+"As with any major upgrade to the core of your Gentoo system, there is always "
+"the possibility that unforeseen problems will ensue. It is always prudent to "
+"back up all important data before beginning this process. If possible, try "
+"to allocate a large block of time for this upgrade, so that you will not "
+"feel rushed. All the software on your machine will need to be recompiled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):46
+msgid "Other options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):49
+msgid ""
+"This is not the only way to upgrade your system. You can install a new 1.4 "
+"system onto a separate partition and reuse some of your system configuration "
+"instead. This method also has the advantage that you can always go back to "
+"your old system in the meantime as a fallback. You may also decide to simply "
+"not upgrade your system. If you decide you want to upgrade in place, read on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):60
+msgid "General notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):63
+msgid ""
+"Whenever the code listings suggest running the <c>emerge</c> command, it is "
+"always a good idea to make a test run of the command using the <c>-p</c> or "
+"<c>--pretend</c> option to make sure that the command will do what you "
+"expect it to do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):74
+msgid "Upgrading in place"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):76
+msgid "Get Portage as current as possible"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):79
+msgid ""
+"Some of the syntax of current ebuilds is unreadable by older versions of "
+"Portage. If you don't have at least Portage 2.0.44, try upgrading Portage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):84
+msgid "Updating Portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):84
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --sync</i>\n"
+"# <i>emerge -u portage</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(note):89
+msgid ""
+"If your Portage version is very old, you may get an error message containing "
+"the phrase \"unscriptable object\". Read and follow the instructions in "
+"<path>/usr/portage/sys-apps/portage/files/README.RESCUE</path>. Your Portage "
+"install should then be current."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):99
+msgid "Preparing GCC for cohabitation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):102
+msgid ""
+"You will be installing a newer version of GCC during this upgrade. Versions "
+"of GCC older than 2.95.3-r8 are not designed to have multiple versions of "
+"GCC installed. You must therefore upgrade GCC to at least version 2.95.3-r8. "
+"This will also have the beneficial side-effect of installing the <c>gcc-"
+"config</c> package on your system, which can be used to switch back and "
+"forth between various installed versions of GCC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):111
+msgid "Updating GCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):111
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -u gcc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):115
+msgid "You can now check to see if gcc-config is working properly:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):119
+msgid "Verifying GCC profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):119
+#, no-wrap
+msgid ""
+"\n"
+"# <i>gcc-config --get-current-profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):123
+msgid ""
+"This should return i686-pc-linux-gnu-2.95.3 on most x86 systems. Older "
+"systems may return i586-pc-linux-gnu-2.95.3."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):131
+msgid "Installing GCC 3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):134
+msgid ""
+"Now you can install a newer version of GCC without damaging your current "
+"compiler. Look in <path>/usr/portage/sys-devel/gcc</path> for a version of "
+"the GCC ebuild that is at least 3.2.1-r6. Choose the highest version that is "
+"marked stable for your architecture. To see if an ebuild is considered "
+"stable for your architecture, look for the KEYWORDS line in the ebuild file. "
+"If it has your architecture listed without a ~ in front of it, it is "
+"considered stable. Assuming 3.2.2 is the most current stable version, we "
+"first need to remove the glibc dependency from gcc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):145
+msgid ""
+"Edit <path>/usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</path> and search for "
+"the line containing <c>DEPEND</c>. Remove the <c>glibc</c> dependency and "
+"save the ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):151
+msgid "Editing gcc-3.2.2.ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):151
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vim /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):155
+msgid "Now install the latest GCC version on your system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):159
+msgid "Install the latest GCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):159
+#, no-wrap
+msgid ""
+"\n"
+"# <i>USE=\"-java\" emerge /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):166
+msgid "Changing profiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):169
+msgid ""
+"Now you need to change two sets of profiles: your gcc-config profile and "
+"your Portage profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):174
+msgid "Change the Portage profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):174
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc</i>\n"
+"# <i>rm make.profile</i>\n"
+"<comment>(Replace \"x86\" with your architecture)</comment>\n"
+"# <i>ln -s ../usr/portage/profiles/default-x86-1.4 make.profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):181
+msgid "Change the GCC profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):181
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Note the one for the version you just emerged, use it below)</comment>\n"
+"# <i>gcc-config --list-profiles</i>\n"
+"<comment>(Replace with the version you noted above)</comment>\n"
+"# <i>gcc-config i686-pc-linux-gnu-3.2.2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):191
+msgid "Recompile toolchain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):194
+msgid ""
+"Now you need to recompile your core toolchain with your new compiler. If you "
+"are continuing in the same shell, you need to run <c>source /etc/profile</c> "
+"as gcc-config instructed you to. Then emerge glibc and binutils using your "
+"new compiler:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):201
+msgid "Rebuilding the toolchain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):201
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge glibc binutils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(warn):205
+msgid ""
+"It is quite likely that you will upgrade glibc from a 2.2 or older version "
+"to 2.3. Do not downgrade glibc afterwards. Any software you have compiled "
+"against glibc 2.3 will stop working, and this can make your system unusable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(title):214
+msgid "Recompiling everything with your new compiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(p):217
+msgid "Now you may recompile everything on your system with your new compiler:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre:caption):221
+msgid "Rebuilding the entire system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(pre):221
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -e world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(note):225
+msgid ""
+"If this command fails at any point due to errors, you can use <c>emerge --"
+"resume</c> to continue the process where you left off. This requires Portage "
+"2.0.47 or later."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//new-upgrade-to-gentoo-1.4.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/nvidia-guide.xml.po b/doc/gettext/ru/nvidia-guide.xml.po
new file mode 100644
index 0000000..16a3dae
--- /dev/null
+++ b/doc/gettext/ru/nvidia-guide.xml.po
@@ -0,0 +1,778 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):6
+msgid "Gentoo Linux nVidia Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail:link):12
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail):12
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail:link):15
+msgid "curtis119@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail):15
+msgid "M Curtis Napier"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail:link):18
+msgid "wolf31o2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(mail):18
+msgid "Chris Gianelloni"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(abstract):21
+msgid ""
+"Many Gentooists have an nVidia chipset on their system. nVidia provides "
+"specific Linux drivers to boost the performance of your card. This guide "
+"informs you how to install and configure these drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(version):31
+msgid "1.41"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(date):32
+msgid "2010-07-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):35
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):39
+msgid ""
+"The nVidia drivers in the tree are released by nVidia and are built against "
+"the Linux kernel. They contain a binary blob that does the heavy lifting for "
+"talking to the card. The drivers consist of two parts, a kernel module, and "
+"an X11 driver. Both parts are included in a single package. Due to the way "
+"nVidia has been packaging their drivers, you will need to make some choices "
+"before you install the drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):48
+msgid ""
+"The <c>nvidia-drivers</c> package contains the latest drivers from nVidia "
+"with support for <e>all</e> cards, with several versions available depending "
+"on how old your card is. It uses an eclass to detect what kind of card "
+"you're running so that it installs the proper version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):60
+msgid "Driver compatibility"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):62
+msgid "Which version?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):65
+msgid ""
+"The <c>nvidia-drivers</c> package supports the full range of available "
+"nVidia cards. Multiple versions are available for installation, depending on "
+"the card(s) you have."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):71
+msgid ""
+"Newer cards such as the GeForce 400, 300, 200, 100, 9, 8, 7, and 6 series "
+"should use the latest drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):76
+msgid ""
+"Older cards such as the GeForce FX 5 series should use the 173.x drivers, "
+"such as <c>nvidia-drivers-173.14.15</c>. For these cards, you should mask "
+"<c>&gt;=x11-drivers/nvidia-drivers-174.00</c> in your <path>/etc/portage/"
+"package.mask</path> file. This will prevent newer versions of the driver "
+"which are incompatible with your card from being installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):84
+msgid ""
+"Old cards such as the GeForce 3 or GeForce 4 series require the 96.x "
+"drivers. For these cards, you should mask <c>&gt;=x11-drivers/nvidia-"
+"drivers-97.00</c> in your <path>/etc/portage/package.mask</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):90
+msgid ""
+"The oldest NV2x-based cards (such as TNT, TNT2, GeForce, and GeForce 2) are "
+"no longer supported by <c>nvidia-drivers</c>. Instead, use an open-source "
+"driver: <c>xf86-video-nouveau</c> (recommended) or <c>xf86-video-nv</c> "
+"(old, deprecated)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):97
+msgid ""
+"You can check for driver compatibility for your card at to determine which "
+"driver supports it by viewing the README at its appropriate x86 or x86-64 "
+"<uri link=\"http://www.nvidia.com/object/unix.html\">release page</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):108
+msgid "Configuring your Card"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):110
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):113
+msgid ""
+"As mentioned above, the nVidia kernel driver installs and runs against your "
+"current kernel. It builds as a module, so it makes sense that your kernel "
+"must support the loading of kernel modules. If you used <c>genkernel all</c> "
+"to configure the kernel for you, then you're all set. If not, double check "
+"your kernel configuration so that this support is enabled:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):121
+msgid "Enabling the Loading of Kernel Modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):121
+#, no-wrap
+msgid ""
+"\n"
+"Loadable module support ---&gt;\n"
+"  [*] Enable loadable module support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):126
+msgid ""
+"You also need to enable <e>Memory Type Range Register</e> in your kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):130
+msgid "Enabling MTRR"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):130
+#, no-wrap
+msgid ""
+"\n"
+"Processor and Features ---&gt;\n"
+"  [*] MTRR (Memory Type Range Register) support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):135
+msgid ""
+"Also, if you have an AGP graphics card, you can optionally enable "
+"<c>agpgart</c> support to your kernel, either compiled in or as a module. If "
+"you do not use the in-kernel agpgart, then the drivers will use their own "
+"<c>agpgart</c> implementation, called <c>NvAGP</c>. On certain systems, this "
+"performs better than the in-kernel agpgart, and on others, it performs "
+"worse. You will need to evaluate this on your own system to get the best "
+"performance. If you are unsure what to do, use the in-kernel agpgart:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):144
+msgid "Enabling agpgart"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):144
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"Graphics Support ---&gt;\n"
+"-*- /dev/agpgart (AGP Support) ---&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(note):150
+msgid "On amd64, the IOMMU controls the agpgart setting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):157
+msgid "Arch-specific notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(impo):160
+msgid ""
+"For x86 and AMD64 processors, the in-kernel driver conflicts with the binary "
+"driver provided by nVidia. If you will be compiling your kernel for these "
+"CPUs, you must completely remove support for the in-kernel driver as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):166
+msgid "Remove the in-kernel driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):166
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"Graphics Support ---&gt;\n"
+"&lt;*&gt; Support for frame buffer devices ---&gt;\n"
+"&lt; &gt;   nVidia Framebuffer Support\n"
+"&lt; &gt;   nVidia Riva support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):174
+msgid ""
+"A framebuffer alternative is <c>uvesafb</c>, an <uri link=\"http://dev."
+"gentoo.org/~spock/projects/uvesafb/\">advanced framebuffer</uri>. Note that "
+"you can choose to compile it into your kernel, or as a module. The following "
+"example compiles uvesafb into the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):181
+msgid "Enable uvesafb support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):181
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"Graphics Support ---&gt;\n"
+"&lt;*&gt; Support for frame buffer devices ---&gt;\n"
+"&lt;*&gt;   Userspace VESA VGA graphics support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):189
+msgid "Or you can try <c>VESA</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):193
+msgid "Enable VESA support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):193
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"Graphics Support ---&gt;\n"
+"&lt;*&gt; Support for frame buffer devices ---&gt;\n"
+"[*]   VESA VGA graphics support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):201
+msgid ""
+"For more information, you can look up the documentation for your chosen "
+"framebuffer in <path>/usr/src/linux/Documentation/fb/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):209
+msgid "Continuing with Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):212
+msgid ""
+"The <c>nvidia-drivers</c> ebuild automatically discovers your kernel version "
+"based on the <path>/usr/src/linux</path> symlink. Please ensure that you "
+"have this symlink pointing to the correct sources and that your kernel is "
+"correctly configured. Please refer to the \"Configuring the Kernel\" section "
+"of the <uri link=\"/doc/en/handbook/\">Installation Handbook</uri> for "
+"details on configuring your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):221
+msgid ""
+"First, you'll need to choose the right kernel source using <c>eselect</c>. "
+"If you are using <c>gentoo-sources-2.6.34-r1</c>, your kernel listing might "
+"look something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):227
+msgid "Check your /usr/src/linux symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):227
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect kernel list</i>\n"
+"Available kernel symlink targets:\n"
+"  [1]   linux-2.6.34-gentoo-r1 *\n"
+"  [2]   linux-2.6.33-gentoo-r2\n"
+"  [3]   linux-2.6.32.9\n"
+"<comment>(Verify that the right kernel is marked with an asterisk</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):236
+msgid ""
+"In the above output, you'll notice that the <c>linux-2.6.34-gentoo-r1</c> "
+"kernel is marked with an asterisk (<b>*</b>) to show that it is the "
+"symlinked kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):241
+msgid ""
+"If the symlink is not pointing to the correct sources, you must update the "
+"link by selecting the number of your desired kernel sources, as in the "
+"example above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):247
+msgid "Create/Update /usr/src/linux symlink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):247
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Select the correct kernel)</comment>\n"
+"# <i>eselect kernel set 1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):255
+msgid "Installing the Appropriate Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):258
+msgid ""
+"Now it's time to install the drivers. You can do this by first following the "
+"<uri link=\"/doc/en/xorg-config.xml\">X Server Configuration HOWTO</uri> and "
+"setting <c>VIDEO_CARDS=\"nvidia\"</c> in <path>/etc/make.conf</path>. When "
+"you install the X server, it will then install the right version of "
+"<c>nvidia-drivers</c> for you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(note):266
+msgid ""
+"The drivers can be installed with the <c>gtk</c> USE flag set in <path>/etc/"
+"make.conf</path>. This will install <c>media-video/nvidia-settings</c>, a "
+"handy graphical tool for monitoring and configuring several aspects of your "
+"nVidia card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(impo):273
+msgid ""
+"Every time you <uri link=\"/doc/en/kernel-upgrade.xml\">compile a new "
+"kernel</uri> or recompile the current one, you will need to reinstall the "
+"nVidia kernel modules. An easy way to keep track of modules installed by "
+"ebuilds (such as <c>nvidia-drivers</c>) is to install <c>sys-kernel/module-"
+"rebuild</c>. Once you've installed it, simply run <c>module-rebuild "
+"populate</c> to populate its database with a list of packages to be rebuilt. "
+"Once you've finished compiling or recompiling a kernel, just run <c>module-"
+"rebuild rebuild</c> to rebuild the drivers for your new kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):284
+msgid ""
+"Once the installation has finished, run <c>modprobe nvidia</c> to load the "
+"kernel module into memory. If this is an upgrade, you should remove the "
+"previous module first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):290
+msgid "Loading the kernel module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):290
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lsmod | grep nvidia &amp;&amp; rmmod nvidia</i>\n"
+"# <i>modprobe nvidia</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):295
+msgid ""
+"To prevent you having to manually load the module on every bootup, you "
+"probably want to have this done automatically each time you boot your "
+"system, so edit <path>/etc/modules.autoload.d/kernel-2.6</path> and add "
+"<c>nvidia</c> to it. Don't forget to run <c>update-modules</c> afterwards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(impo):302
+msgid ""
+"If you compiled <c>agpgart</c> as a module, you will need to add it to "
+"<path>/etc/modules.autoload.d/kernel-2.6</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):307
+msgid "Running update-modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):307
+#, no-wrap
+msgid ""
+"\n"
+"# <i>update-modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):314
+msgid "Configuring the X Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):317
+msgid ""
+"Once the appropriate drivers are installed you need to configure your X "
+"Server to use the <c>nvidia</c> driver instead of the default <c>nv</c> "
+"driver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):322
+msgid ""
+"Open <path>/etc/X11/xorg.conf</path> with your favorite editor (such as "
+"<c>nano</c> or <c>vim</c>) and go to the <c>Device</c> section. In that "
+"section, change the <c>Driver</c> line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):328
+msgid "Changing nv to nvidia in the X Server configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):328
+#, no-wrap
+msgid ""
+"\n"
+"Section \"Device\"\n"
+"  Identifier \"nVidia Inc. GeForce2\"\n"
+"  <i>Driver     \"nvidia\"</i>\n"
+"  VideoRam   65536\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):336
+msgid ""
+"Then go to the <c>Module</c> section and make sure the <c>glx</c> module "
+"gets loaded while the <c>dri</c> module doesn't:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):341
+msgid "Updating the Module section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):341
+#, no-wrap
+msgid ""
+"\n"
+"Section \"Module\"\n"
+"  <comment>(...)</comment>\n"
+"  <i># Load  \"dri\"\n"
+"  Load  \"glx\"</i>\n"
+"  <comment>(...)</comment>\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):350
+msgid ""
+"Next, in section <c>Screen</c>, make sure that either the <c>DefaultDepth</"
+"c> directive is set to 16 or 24, or that you only have <c>Display</c> "
+"subsections with <c>Depth</c> settings of 16 or 24. Without it, the nVidia "
+"GLX extensions will not start."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):357
+msgid "Updating the Screen section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):357
+#, no-wrap
+msgid ""
+"\n"
+"Section \"Screen\"\n"
+"  <comment>(...)</comment>\n"
+"  <i>DefaultDepth 16</i>\n"
+"  Subsection \"Display\"\n"
+"  <comment>(...)</comment>\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):366
+msgid "Run <c>eselect</c> so that the X Server uses the nVidia GLX libraries:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):370
+msgid "Running eselect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):370
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect opengl set nvidia</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):377
+msgid "Adding your Users to the video Group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):380
+msgid ""
+"You have to add your user to the <c>video</c> group so he has access to the "
+"nVidia device files:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):385
+msgid "Adding your user to the video group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):385
+#, no-wrap
+msgid ""
+"\n"
+"# <i>gpasswd -a youruser video</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):389
+msgid ""
+"This might not be totally necessary if you aren't using <c>udev</c> but it "
+"doesn't hurt either and makes your system future-proof."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):397
+msgid "Testing your Card"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):400
+msgid ""
+"To test your nVidia card, fire up X and run <c>glxinfo</c>, which is part of "
+"the <c>mesa-progs</c> package. It should say that direct rendering is "
+"activated:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):405
+msgid "Checking the direct rendering status"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):405
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>glxinfo | grep direct</i>\n"
+"direct rendering: Yes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):410
+msgid "To monitor your FPS, run <c>glxgears</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):417
+msgid "Enabling nvidia Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):420
+msgid ""
+"Some tools, such as <c>mplayer</c> and <c>xine-lib</c>, use a local USE flag "
+"called <c>xvmc</c> which enables XvMCNVIDIA support, useful when watching "
+"high resolution movies. Add in <c>xvmc</c> in your USE variable in <path>/"
+"etc/make.conf</path> or add it as USE flag to <c>media-video/mplayer</c> and/"
+"or <c>media-libs/xine-lib</c> in <path>/etc/portage/package.use</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):428
+msgid ""
+"There are also some applications that use the <c>nvidia</c> USE flag, so you "
+"may want to add it to <path>/etc/make.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):433
+msgid ""
+"Then, run <c>emerge -uD --newuse world</c> to rebuild the applications that "
+"benefit from the USE flag change."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):441
+msgid "Using NVidia Settings Tool"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):444
+msgid ""
+"nVidia also provides you with a settings tool. This tool allows you to "
+"monitor and change graphical settings without restarting the X server and is "
+"available through Portage as <c>media-video/nvidia-settings</c>. As "
+"mentioned earlier, it will be pulled in automatically if you install the "
+"drivers with the <c>gtk</c> USE flag set in <path>/etc/make.conf</path> or "
+"in <path>/etc/portage/package.use</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):458
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):460
+msgid "Getting 2D to work on machines with 4Gb or more memory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):463
+msgid ""
+"If you are having troubles with the nVidia 2D acceleration it is likely that "
+"you are unable to set up a write-combining range with MTRR. To verify, check "
+"the contents of <path>/proc/mtrr</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):469
+msgid "Checking if you have write-combining enabled"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):469
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cat /proc/mtrr</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):473
+msgid ""
+"Every line should contain \"write-back\" or \"write-combining\". If you see "
+"a line with \"uncachable\" in it you will need to change a BIOS setting to "
+"fix this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):478
+msgid ""
+"Reboot and enter the BIOS, then find the MTRR settings (probably under \"CPU "
+"Settings\"). Change the setting from \"continuous\" to \"discrete\" and boot "
+"back into Linux. You will now find out that there is no \"uncachable\" entry "
+"anymore and 2D acceleration now works without any glitches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):488
+msgid "When I attempt to load the kernel module I receive a \"no such device\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):493
+msgid ""
+"This usually occurs when you don't have a matching video card. Make sure "
+"that you have an nVidia-powered graphical card (you can double-check this "
+"using <c>lspci</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):499
+msgid ""
+"If you are confident that you have an nVidia card, check your BIOS and see "
+"if the directive <e>Assign IRQ to VGA</e> is set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):509
+msgid "Expert Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):511
+msgid "Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):514
+msgid ""
+"The nVidia driver package also comes with comprehensive documentation. This "
+"is installed into <c>/usr/share/doc</c> and can be viewed with the following "
+"command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):520
+msgid "Viewing the NVIDIA documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):520
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>less /usr/share/doc/nvidia-drivers-*/README.gz</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):527
+msgid "Kernel module parameters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):530
+msgid ""
+"The <c>nvidia</c> kernel module accepts a number of parameters (options) "
+"which you can use to tweak the behaviour of the driver. Most of these are "
+"mentioned in the documentation. To add or change the values of these "
+"parameters, edit the file <c>/etc/modprobe.d/nvidia.conf</c>. Remember to "
+"run <c>update-modules</c> after modifying this file, and bear in mind that "
+"you will need to reload the <c>nvidia</c> module before the new settings "
+"take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):539
+msgid "Adjusting nvidia options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):539
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Edit /etc/modprobe.d/nvidia.conf in your favourite editor)</comment>\n"
+"# <i>nano -w /etc/modprobe.d/nvidia.conf</i>\n"
+"<comment>(Update module information)</comment>\n"
+"# <i>update-modules</i>\n"
+"<comment>(Unload the nvidia module...)</comment>\n"
+"# <i>modprobe -r nvidia</i>\n"
+"<comment>(...and load it once again)</comment>\n"
+"# <i>modprobe nvidia</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(title):553
+msgid "Advanced X configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):556
+msgid ""
+"The GLX layer also has a plethora of options which can be configured. These "
+"control the configuration of TV out, dual displays, monitor frequency "
+"detection, etc. Again, all of the available options are detailed in the "
+"documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(p):562
+msgid ""
+"If you wish to use any of these options, you need to list them in the "
+"relevant Device section of your X config file (usually <c>/etc/X11/xorg."
+"conf</c>). For example, suppose I wanted to disable the splash logo:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre:caption):568
+msgid "Advanced nvidia configuration in the X configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(pre):568
+#, no-wrap
+msgid ""
+"\n"
+"Section \"Device\"\n"
+"  Identifier \"nVidia Inc. GeForce2\"\n"
+"  Driver     \"nvidia\"\n"
+"  <i>Option     \"NoLogo\" \"true\"</i>\n"
+"  VideoRam   65536\n"
+"EndSection\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//nvidia-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/openafs.xml.po b/doc/gettext/ru/openafs.xml.po
new file mode 100644
index 0000000..b677db2
--- /dev/null
+++ b/doc/gettext/ru/openafs.xml.po
@@ -0,0 +1,1764 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(guide:link):6
+msgid "/doc/en/openafs.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):7
+msgid "Gentoo Linux OpenAFS Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):9
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):12
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):15
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):18
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):21
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(author:title):24
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):10
+msgid "stefaan@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):10
+msgid "Stefaan De Roeck"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):13
+msgid "darks@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):13
+msgid "Holger Brueckner"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):16
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):16
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):19
+msgid "blubber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):19
+msgid "Tiemo Kieft"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):22
+msgid "fnjordy@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):22
+msgid "Steven McCoy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail:link):25
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(mail):25
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(abstract):28
+msgid ""
+"This guide shows you how to install an OpenAFS server and client on Gentoo "
+"Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(version):37
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(date):38
+msgid "2007-06-29"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):41
+msgid "Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):43
+msgid "About this Document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):46
+msgid ""
+"This document provides you with all necessary steps to install an OpenAFS "
+"server on Gentoo Linux. Parts of this document are taken from the AFS FAQ "
+"and IBM's Quick Beginnings guide on AFS. Well, never reinvent the wheel. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):55
+msgid "What is AFS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):58
+msgid ""
+"AFS is a distributed filesystem that enables co-operating hosts (clients and "
+"servers) to efficiently share filesystem resources across both local area "
+"and wide area networks. Clients hold a cache for often used objects (files), "
+"to get quicker access to them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):66
+msgid ""
+"AFS is based on a distributed file system originally developed at the "
+"Information Technology Center at Carnegie-Mellon University that was called "
+"the \"Andrew File System\". \"Andrew\" was the name of the research project "
+"at CMU - honouring the founders of the University. Once Transarc was formed "
+"and AFS became a product, the \"Andrew\" was dropped to indicate that AFS "
+"had gone beyond the Andrew research project and had become a supported, "
+"product quality filesystem. However, there were a number of existing cells "
+"that rooted their filesystem as /afs. At the time, changing the root of the "
+"filesystem was a non-trivial undertaking. So, to save the early AFS sites "
+"from having to rename their filesystem, AFS remained as the name and "
+"filesystem root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):83
+msgid "What is an AFS cell?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):86
+msgid ""
+"An AFS cell is a collection of servers grouped together administratively and "
+"presenting a single, cohesive filesystem. Typically, an AFS cell is a set of "
+"hosts that use the same Internet domain name (for example, gentoo.org) Users "
+"log into AFS client workstations which request information and files from "
+"the cell's servers on behalf of the users. Users won't know on which server "
+"a file which they are accessing, is located. They even won't notice if a "
+"server will be located to another room, since every volume can be replicated "
+"and moved to another server without any user noticing. The files are always "
+"accessible. Well, it's like NFS on steroids :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):101
+msgid "What are the benefits of using AFS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):104
+msgid ""
+"The main strengths of AFS are its: caching facility (on client side, "
+"typically 100M to 1GB), security features (Kerberos 4 based, access control "
+"lists), simplicity of addressing (you just have one filesystem), scalability "
+"(add further servers to your cell as needed), communications protocol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):116
+msgid "Where can I get more information?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):119
+msgid ""
+"Read the <uri link=\"http://www.angelfire.com/hi/plutonic/afs-faq.html\">AFS "
+"FAQ</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):124
+msgid ""
+"OpenAFS main page is at <uri link=\"http://www.openafs.org\">www.openafs."
+"org</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):129
+msgid ""
+"AFS was originally developed by Transarc which is now owned by IBM. You can "
+"find some information about AFS on <uri link=\"http://www.transarc.ibm.com/"
+"Product/EFS/AFS/index.html\">Transarc's Webpage</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):139
+msgid "How Can I Debug Problems?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):142
+msgid ""
+"OpenAFS has great logging facilities. However, by default it logs straight "
+"into its own logs instead of through the system logging facilities you have "
+"on your system. To have the servers log through your system logger, use the "
+"<c>-syslog</c> option for all <c>bos</c> commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):154
+msgid "Upgrading from previous versions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):156
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):159
+msgid ""
+"This section aims to help you through the process of upgrading an existing "
+"OpenAFS installation to OpenAFS version 1.4.0 or higher (or 1.2.x starting "
+"from 1.2.13. The latter will not be handled specifically, as most people "
+"will want 1.4 for a.o. linux-2.6 support, large file support and bug fixes)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):166
+msgid ""
+"If you're dealing with a clean install of a 1.4 version of OpenAFS, then you "
+"can safely skip this chapter. However, if you're upgrading from a previous "
+"version, we strongly urge you to follow the guidelines in the next sections. "
+"The transition script in the ebuild is designed to assist you in quickly "
+"upgrading and restarting. Please note that it will (for safety reasons) not "
+"delete configuration files and startup scripts in old places, not "
+"automatically change your boot configuration to use the new scripts, etc. If "
+"you need further convincing, using an old OpenAFS kernel module together "
+"with the updated system binaries, may very well cause your kernel to freak "
+"out. So, let's read on for a clean and easy transition, shall we?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):179
+msgid ""
+"This chapter has been written bearing many different system configurations "
+"in mind. Still, it is possible that due to peculiar tweaks a user has made, "
+"his or her specific situation may not be described here. A user with enough "
+"self-confidence to tweak his system should be experienced enough to apply "
+"the given remarks where appropriate. Vice versa, a user that has done little "
+"to his system but install the previous ebuild, can skip most of the warnings "
+"further on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):192
+msgid "Differences to previous versions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):195
+msgid ""
+"Traditionally, OpenAFS has used the same path-conventions that IBM TransArc "
+"labs had used, before the code was forked. Understandably, old AFS setups "
+"continue using these legacy path conventions. More recent setups conform "
+"with FHS by using standard locations (as seen in many Linux distributions). "
+"The following table is a compilation of the configure-script and the README "
+"accompanying the OpenAFS distribution tarballs:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):206
+msgid "Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):207
+msgid "Purpose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):208
+msgid "Transarc Mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):209
+msgid "Default Mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(th):210
+msgid "translation to Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):213
+msgid "viceetcdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):214
+msgid "Client configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):215
+msgid "/usr/vice/etc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):216
+msgid "$(sysconfdir)/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):217
+msgid "/etc/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):220
+msgid "unnamed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):221
+msgid "Client binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):222
+msgid "unspecified"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):223
+msgid "$(bindir)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):224
+msgid "/usr/bin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):227
+msgid "afsconfdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):228
+msgid "Server configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):229
+msgid "/usr/afs/etc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):230
+msgid "$(sysconfdir)/openafs/server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):231
+msgid "/etc/openafs/server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):234
+msgid "afssrvdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):235
+msgid "Internal server binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):236
+msgid "/usr/afs/bin (servers)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):237
+msgid "$(libexecdir)/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):238
+msgid "/usr/libexec/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):241
+msgid "afslocaldir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):242
+msgid "Server state"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):243
+msgid "/usr/afs/local"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):244
+msgid "$(localstatedir)/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):245
+msgid "/var/lib/openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):248
+msgid "afsdbdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):249
+msgid "Auth/serverlist/... databases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):250
+msgid "/usr/afs/db"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):251
+msgid "$(localstatedir)/openafs/db"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):252
+msgid "/var/lib/openafs/db"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):255
+msgid "afslogdir"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):256
+msgid "Log files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):257
+msgid "/usr/afs/logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):258
+msgid "$(localstatedir)/openafs/logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):259
+msgid "/var/lib/openafs/logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):262
+msgid "afsbosconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):263
+msgid "Overseer config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):264
+msgid "$(afslocaldir)/BosConfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):265
+msgid "$(afsconfdir)/BosConfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):266
+msgid "/etc/openafs/BosConfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):270
+msgid ""
+"There are some other oddities, like binaries being put in <path>/usr/vice/"
+"etc</path> in Transarc mode, but this list is not intended to be "
+"comprehensive. It is rather meant to serve as a reference to those "
+"troubleshooting config file transition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):277
+msgid ""
+"Also as a result of the path changes, the default disk cache location has "
+"been changed from <path>/usr/vice/cache</path> to <path>/var/cache/openafs</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):283
+msgid ""
+"Furthermore, the init-script has been split into a client and a server part. "
+"You used to have <path>/etc/init.d/afs</path>, but now you'll end up with "
+"both <path>/etc/init.d/openafs-client</path> and <path>/etc/init.d/openafs-"
+"server</path>. Consequently, the configuration file <path>/etc/conf.d/afs</"
+"path> has been split into <path>/etc/conf.d/openafs-client</path> and <path>/"
+"etc/conf.d/openafs-server</path>. Also, options in <path>/etc/conf.d/afs</"
+"path> to turn either client or server on or off have been obsoleted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):295
+msgid ""
+"Another change to the init script is that it doesn't check your disk cache "
+"setup anymore. The old code required that a separate ext2 partition be "
+"mounted at <path>/usr/vice/cache</path>. There were some problems with that:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):302
+msgid ""
+"Though it's a very logical setup, your cache doesn't need to be on a "
+"separate partition. As long as you make sure that the amount of space "
+"specified in <path>/etc/openafs/cacheinfo</path> really is available for "
+"disk cache usage, you're safe. So there is no real problem with having the "
+"cache on your root partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):309
+msgid ""
+"Some people use soft-links to point to the real disk cache location. The "
+"init script didn't like this, because then this cache location didn't turn "
+"up in <path>/proc/mounts</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):314
+msgid ""
+"Many prefer ext3 over ext2 nowadays. Both filesystems are valid for usage as "
+"a disk cache. Any other filesystem is unsupported (like: don't try reiserfs, "
+"you'll get a huge warning, expect failure afterwards)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):325
+msgid "Transition to the new paths"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):328
+msgid ""
+"First of all, emerging a newer OpenAFS version should not overwrite any old "
+"configuration files. The script is designed to not change any files already "
+"present on the system. So even if you have a totally messed up configuration "
+"with a mix of old and new locations, the script should not cause further "
+"problems. Also, if a running OpenAFS server is detected, the installation "
+"will abort, preventing possible database corruption."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):337
+msgid ""
+"One caveat though -- there have been ebuilds floating around the internet "
+"that partially disable the protection that Gentoo puts on <path>/etc</path>. "
+"These ebuilds have never been distributed by Gentoo. You might want to check "
+"the <c>CONFIG_PROTECT_MASK</c> variable in the output of the following "
+"command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):344
+msgid "Checking your CONFIG_PROTECT_MASK"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):344
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge info | grep \"CONFIG_PROTECT_MASK\"</i>\n"
+"CONFIG_PROTECT_MASK=\"/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):349
+msgid ""
+"Though nothing in this ebuild would touch the files in <path>/etc/afs</"
+"path>, upgrading will cause the removal of your older OpenAFS installation. "
+"Files in <c>CONFIG_PROTECT_MASK</c> that belong to the older installation "
+"will be removed as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):356
+msgid ""
+"It should be clear to the experienced user that in the case he has tweaked "
+"his system by manually adding soft links (e.g. <path>/usr/afs/etc</path> to "
+"<path>/etc/openafs</path>), the new installation may run fine while still "
+"using the old configuration files. In this case, there has been no real "
+"transition, and cleaning up the old installation will result in a broken "
+"OpenAFS config."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):364
+msgid "Now that you know what doesn't happen, you may want to know what does:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):369
+msgid "<path>/usr/afs/etc</path> is copied to <path>/etc/openafs/server</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):372
+msgid "<path>/usr/vice/etc</path> is copied to <path>/etc/openafs</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):375
+msgid "<path>/usr/afs/local</path> is copied to <path>/var/lib/openafs</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):378
+msgid ""
+"<path>/usr/afs/local/BosConfig</path> is copied to <path>/etc/openafs/"
+"BosConfig</path>, while replacing occurrences of <path>/usr/afs/bin/</path> "
+"with <path>/usr/libexec/openafs</path>, <path>/usr/afs/etc</path> with "
+"<path>/etc/openafs/server</path> and <path>/usr/afs/bin</path> (without "
+"the / as previously) with <path>/usr/bin</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):386
+msgid "<path>/usr/afs/db</path> is copied to <path>/var/lib/openafs/db</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):389
+msgid ""
+"The configuration file <path>/etc/conf.d/afs</path> is copied to <path>/etc/"
+"conf.d/openafs-client</path>, as all known old options were destined for "
+"client usage only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):399
+msgid "The upgrade itself"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):402
+msgid ""
+"So you haven't got an OpenAFS server setup? Or maybe you do, the previous "
+"sections have informed you about what is going to happen, and you're still "
+"ready for it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):408
+msgid "Let's go ahead with it then!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):412
+msgid "If you do have a server running, you want to shut it down now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):416
+msgid "Stopping OpenAFS (in case you have a server)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):416
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):439
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/afs stop</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):420
+msgid "And then the upgrade itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):424
+msgid "Now upgrade!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):424
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -u openafs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):431
+msgid "Restarting OpenAFS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):434
+msgid ""
+"If you had an OpenAFS server running, you would have not have been forced to "
+"shut it down. Now is the time to do that."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):439
+msgid "Stopping OpenAFS client after upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):443
+msgid ""
+"As you may want keep the downtime to a minimum, so you can restart your "
+"OpenAFS server right away."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):448
+msgid "Restarting OpenAFS server after upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):448
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/openafs-server start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):452
+msgid "You can check whether it's running properly with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):456
+msgid "Checking OpenAFS server status"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):456
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/usr/bin/bos status localhost -localauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):460
+msgid ""
+"Before starting the OpenAFS client again, please take time to check your "
+"cache settings. They are determined by <path>/etc/openafs/cacheinfo</path>. "
+"To restart your OpenAFS client installation, please type the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):466
+msgid "Restarting OpenAFS client after upgrade"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):466
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/openafs-client start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):473
+msgid "Cleaning up afterwards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):476
+msgid ""
+"Before cleaning up, please make really sure that everything runs smoothly "
+"and that you have restarted after the upgrade (otherwise, you may still be "
+"running your old installation)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(impo):482
+msgid ""
+"Please make sure you're not using <path>/usr/vice/cache</path> for disk "
+"cache if you are deleting <path>/usr/vice</path>!!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):487
+msgid "The following directories may be safely removed from the system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):498
+msgid "The following files are also unnecessary:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):507
+msgid "Removing the old files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):507
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tar czf /root/oldafs-backup.tgz /etc/afs /usr/vice /usr/afs /usr/afsws</i>\n"
+"# <i>rm -R /etc/afs /usr/vice /usr/afs /usr/afsws</i>\n"
+"# <i>rm /etc/init.d/afs /etc/conf.d/afs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):513
+msgid ""
+"In case you've previously used ebuilds =openafs-1.2.13 or =openafs-1.3.85, "
+"you may also have some other unnecessary files:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):528
+msgid "Init Script changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):531
+msgid ""
+"Now most people would have their systems configured to automatically start "
+"the OpenAFS client and server on startup. Those who don't can safely skip "
+"this section. If you had your system configured to start them automatically, "
+"you will need to re-enable this, because the names of the init scripts have "
+"changed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):539
+msgid "Re-enabling OpenAFS startup at boot time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):539
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update del afs default</i>\n"
+"# <i>rc-update add openafs-client default</i>\n"
+"# <i>rc-update add openafs-server default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):545
+msgid ""
+"If you had <c>=openafs-1.2.13</c> or <c>=openafs-1.3.85</c>, you should "
+"remove <path>afs-client</path> and <path>afs-server</path> from the default "
+"runlevel, instead of <path>afs</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):554
+msgid "Troubleshooting: what if the automatic upgrade fails"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):557
+msgid ""
+"Don't panic. You shouldn't have lost any data or configuration files. So "
+"let's analyze the situation. Please file a bug at <uri link=\"http://bugs."
+"gentoo.org\">bugs.gentoo.org</uri> in any case, preferably with as much "
+"information as possible."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):564
+msgid ""
+"If you're having problems starting the client, this should help you "
+"diagnosing the problem:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):570
+msgid "Run <c>dmesg</c>. The client normally sends error messages there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):573
+msgid ""
+"Check <path>/etc/openafs/cacheinfo</path>. It should be of the form: /afs:"
+"{path to disk cache}:{number of blocks for disk cache}. Normally, your disk "
+"cache will be located at <path>/var/cache/openafs</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):579
+msgid ""
+"Check the output of <c>lsmod</c>. You will want to see a line beginning with "
+"the word openafs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):583
+msgid "<c>pgrep afsd</c> will tell you whether afsd is running or not"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):584
+msgid ""
+"<c>cat /proc/mounts</c> should reveal whether <path>/afs</path> has been "
+"mounted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):590
+msgid ""
+"If you're having problems starting the server, then these hints may be "
+"useful:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):595
+msgid ""
+"<c>pgrep bosserver</c> tells you whether the overseer is running or not. If "
+"you have more than one overseer running, then something has gone wrong. In "
+"that case, you should try a graceful OpenAFS server shutdown with <c>bos "
+"shutdown localhost -localauth -wait</c>, check the result with <c>bos status "
+"localhost -localauth</c>, kill all remaining overseer processes and then "
+"finally check whether any server processes are still running (<c>ls /usr/"
+"libexec/openafs</c> to get a list of them). Afterwards, do <c>/etc/init.d/"
+"openafs-server zap</c> to reset the status of the server and <c>/etc/init.d/"
+"openafs-server start</c> to try launching it again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(li):606
+msgid ""
+"If you're using OpenAFS' own logging system (which is the default setting), "
+"check out <path>/var/lib/openafs/logs/*</path>. If you're using the syslog "
+"service, go check out its logs for any useful information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):618
+msgid "Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):620
+msgid "Getting AFS Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):623
+msgid ""
+"You can get the original IBM AFS Documentation. It is very well written and "
+"you really want read it if it is up to you to administer a AFS Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):628
+msgid "Installing afsdoc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):628
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge app-doc/afsdoc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):632
+msgid ""
+"You also have the option of using the documentation delivered with OpenAFS. "
+"It is installed when you have the USE flag <c>doc</c> enabled while emerging "
+"OpenAFS. It can be found in <path>/usr/share/doc/openafs-*/</path>. At the "
+"time of writing, this documentation was a work in progress. It may however "
+"document newer features in OpenAFS that aren't described in the original IBM "
+"AFS Documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):646
+msgid "Client Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):648
+msgid "Building the Client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):651
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):783
+msgid "Installing openafs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):651
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):783
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge net-fs/openafs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):655
+msgid "After successful compilation you're ready to go."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):662
+msgid "A simple global-browsing client installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):665
+msgid ""
+"If you're not part of a specific OpenAFS-cell you want to access, and you "
+"just want to try browsing globally available OpenAFS-shares, then you can "
+"just install OpenAFS, not touch the configuration at all, and start <path>/"
+"etc/init.d/openafs-client</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):675
+msgid "Accessing a specific OpenAFS cell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):678
+msgid ""
+"If you need to access a specific cell, say your university's or company's "
+"own cell, then some adjustments to your configuration have to be made."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):683
+msgid ""
+"Firstly, you need to update <path>/etc/openafs/CellServDB</path> with the "
+"database servers for your cell. This information is normally provided by "
+"your administrator."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):689
+msgid ""
+"Secondly, in order to be able to log onto the OpenAFS cell, you need to "
+"specify its name in <path>/etc/openafs/ThisCell</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):694
+msgid "Adjusting CellServDB and ThisCell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):694
+#, no-wrap
+msgid ""
+"\n"
+"CellServDB:\n"
+"&gt;netlabs        #Cell name\n"
+"10.0.0.1        #storage\n"
+"\n"
+"ThisCell:\n"
+"netlabs\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(warn):703
+msgid ""
+"Only use spaces inside the <path>CellServDB</path> file. The client will "
+"most likely fail if you use TABs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):708
+msgid ""
+"CellServDB tells your client which server(s) it needs to contact for a "
+"specific cell. ThisCell should be quite obvious. Normally you use a name "
+"which is unique for your organisation. Your (official) domain might be a "
+"good choice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):715
+msgid ""
+"For a quick start, you can now start <path>/etc/init.d/openafs-client</path> "
+"and use <c>klog</c> to authenticate yourself and start using your access to "
+"the cell. For automatic logons to you cell, you want to consult the "
+"appropriate section below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):725
+msgid "Adjusting the cache"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):728
+msgid ""
+"Unfortunately the AFS Client needs a ext2/3 filesystem for its cache to run "
+"correctly. There are some issues when using other filesystems (using e.g. "
+"reiserfs is not a good idea)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):734
+msgid ""
+"You can house your cache on an existing filesystem (if it's ext2/3), or you "
+"may want to have a separate partition for that. The default location of the "
+"cache is <path>/var/cache/openafs</path>, but you can change that by editing "
+"<path>/etc/openafs/cacheinfo</path>. A standard size for your cache is "
+"200MB, but more won't hurt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):745
+msgid "Starting AFS on startup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):748
+msgid ""
+"The following command will create the appropriate links to start your afs "
+"client on system startup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(warn):753
+msgid ""
+"You should always have a running afs server in your domain when trying to "
+"start the afs client. Your system won't boot until it gets some timeout if "
+"your AFS server is down (and this is quite a long long time.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):759
+msgid "Adding AFS client to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):759
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add openafs-client default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):768
+msgid "Server Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):770
+msgid "Building the Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):773
+msgid ""
+"All commands should be written in one line!! In this document they are "
+"sometimes wrapped to two lines to make them easier to read."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):778
+msgid ""
+"If you haven't already done so, the following command will install all "
+"necessary binaries for setting up an AFS Server <e>and</e> Client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):790
+msgid "Starting AFS Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):793
+msgid ""
+"You need to run the <c>bosserver</c> command to initialize the Basic "
+"OverSeer (BOS) Server, which monitors and controls other AFS server "
+"processes on its server machine. Think of it as init for the system. Include "
+"the <c>-noauth</c> flag to disable authorization checking, since you haven't "
+"added the admin user yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(warn):801
+msgid ""
+"Disabling authorization checking gravely compromises cell security. You must "
+"complete all subsequent steps in one uninterrupted pass and must not leave "
+"the machine unattended until you restart the BOS Server with authorization "
+"checking enabled. Well, this is what the AFS documentation says. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):808
+msgid "Initialize the Basic OverSeer Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):808
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bosserver -noauth &amp;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):812
+msgid ""
+"Verify that the BOS Server created <path>/etc/openafs/server/CellServDB</"
+"path> and <path>/etc/openafs/server/ThisCell</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):817
+msgid "Check if CellServDB and ThisCell are created"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):817
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls -al /etc/openafs/server/</i>\n"
+"-rw-r--r--    1 root     root           41 Jun  4 22:21 CellServDB\n"
+"-rw-r--r--    1 root     root            7 Jun  4 22:21 ThisCell\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):826
+msgid "Defining Cell Name and Membership for Server Process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):829
+msgid "Now assign your cell's name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(impo):833
+msgid ""
+"There are some restrictions on the name format. Two of the most important "
+"restrictions are that the name cannot include uppercase letters or more than "
+"64 characters. Remember that your cell name will show up under <path>/afs</"
+"path>, so you might want to choose a short one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):840
+msgid ""
+"In the following and every instruction in this guide, for the &lt;server "
+"name&gt; argument substitute the full-qualified hostname (such as <b>afs."
+"gentoo.org</b>) of the machine you are installing. For the &lt;cell name&gt; "
+"argument substitute your cell's complete name (such as <b>gentoo</b>)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):848
+msgid "Run the <c>bos setcellname</c> command to set the cell name:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):852
+msgid "Set the cell name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):852
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos setcellname &lt;server name&gt; &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):859
+msgid "Starting the Database Server Process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):862
+msgid ""
+"Next use the <c>bos create</c> command to create entries for the four "
+"database server processes in the <path>/etc/openafs/BosConfig</path> file. "
+"The four processes run on database server machines only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):870
+msgid "kaserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):871
+msgid ""
+"The Authentication Server maintains the Authentication Database. This can be "
+"replaced by a Kerberos 5 daemon. If anybody wants to try that feel free to "
+"update this document :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):878
+msgid "buserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):879
+msgid "The Backup Server maintains the Backup Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):882
+msgid "ptserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):883
+msgid "The Protection Server maintains the Protection Database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):886
+msgid "vlserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(ti):887
+msgid ""
+"The Volume Location Server maintains the Volume Location Database (VLDB). "
+"Very important :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):894
+msgid "Create entries for the database processes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):894
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos create &lt;server name&gt; kaserver \\\n"
+"simple /usr/libexec/openafs/kaserver \\\n"
+"-cell &lt;cell name&gt; -noauth</i>\n"
+"# <i>bos create &lt;server name&gt; buserver \\\n"
+"simple /usr/libexec/openafs/buserver \\\n"
+"-cell &lt;cell name&gt; -noauth</i>\n"
+"# <i>bos create &lt;server name&gt; ptserver \\\n"
+"simple /usr/libexec/openafs/ptserver \\\n"
+"-cell &lt;cell name&gt; -noauth</i>\n"
+"# <i>bos create &lt;server name&gt; \\\n"
+"vlserver simple /usr/libexec/openafs/vlserver \\\n"
+"-cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):909
+msgid ""
+"You can verify that all servers are running with the <c>bos status</c> "
+"command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):913
+msgid "Check if all the servers are running"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):913
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos status &lt;server name&gt; -noauth</i>\n"
+"Instance kaserver, currently running normally.\n"
+"Instance buserver, currently running normally.\n"
+"Instance ptserver, currently running normally.\n"
+"Instance vlserver, currently running normally.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):924
+msgid "Initializing Cell Security"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):927
+msgid ""
+"Now we'll initialize the cell's security mechanisms. We'll begin by creating "
+"the following two initial entries in the Authentication Database: The main "
+"administrative account, called <b>admin</b> by convention and an entry for "
+"the AFS server processes, called <c>afs</c>. No user logs in under the "
+"identity <b>afs</b>, but the Authentication Server's Ticket Granting Service "
+"(TGS) module uses the account to encrypt the server tickets that it grants "
+"to AFS clients. This sounds pretty much like Kerberos :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):937
+msgid "Enter <c>kas</c> interactive mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):941
+msgid "Entering the interactive mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):941
+#, no-wrap
+msgid ""
+"\n"
+"# <i>kas -cell &lt;cell name&gt; -noauth</i>\n"
+"ka&gt; <i>create afs</i>\n"
+"initial_password:\n"
+"Verifying, please re-enter initial_password:\n"
+"ka&gt; <i>create admin</i>\n"
+"initial_password:\n"
+"Verifying, please re-enter initial_password:\n"
+"ka&gt; <i>examine afs</i>\n"
+"\n"
+"User data for afs\n"
+"key (0) cksum is 2651715259, last cpw: Mon Jun  4 20:49:30 2001\n"
+"password will never expire.\n"
+"An unlimited number of unsuccessful authentications is permitted.\n"
+"entry never expires.  Max ticket lifetime 100.00 hours.\n"
+"last mod on Mon Jun  4 20:49:30 2001 by &lt;none&gt;\n"
+"permit password reuse\n"
+"ka&gt; <i>setfields admin -flags admin</i>\n"
+"ka&gt; <i>examine admin</i>\n"
+"\n"
+"User data for admin (ADMIN)\n"
+"key (0) cksum is 2651715259, last cpw: Mon Jun  4 20:49:59 2001\n"
+"password will never expire.\n"
+"An unlimited number of unsuccessful authentications is permitted.\n"
+"entry never expires.  Max ticket lifetime 25.00 hours.\n"
+"last mod on Mon Jun  4 20:51:10 2001 by &lt;none&gt;\n"
+"permit password reuse\n"
+"ka&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):971
+msgid ""
+"Run the <c>bos adduser</c> command, to add the <b>admin</b> user to the "
+"<path>/etc/openafs/server/UserList</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):976
+msgid "Add the admin user to the UserList"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):976
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos adduser &lt;server name&gt; admin -cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):980
+msgid ""
+"Issue the <c>bos addkey</c> command to define the AFS Server encryption key "
+"in <path>/etc/openafs/server/KeyFile</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):985
+msgid ""
+"If asked for the input key, give the password you entered when creating the "
+"AFS entry with <c>kas</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):990
+msgid "Entering the password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):990
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos addkey  &lt;server name&gt; -kvno 0 -cell &lt;cell name&gt; -noauth</i>\n"
+"input key:\n"
+"Retype input key:\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):996
+msgid ""
+"Issue the <c>pts createuser</c> command to create a Protection Database "
+"entry for the admin user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):1001
+msgid ""
+"By default, the Protection Server assigns AFS UID 1 to the <b>admin</b> "
+"user, because it is the first user entry you are creating. If the local "
+"password file (<path>/etc/passwd</path> or equivalent) already has an entry "
+"for <b>admin</b> that assigns a different UID use the <c>-id</c> argument to "
+"create matching UIDs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1009
+msgid "Create a Protection Database entry for the database user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1009
+#, no-wrap
+msgid ""
+"\n"
+"# <i>pts createuser -name admin -cell &lt;cell name&gt; [-id &lt;AFS UID&gt;] -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1013
+msgid ""
+"Issue the <c>pts adduser</c> command to make the <b>admin</b> user a member "
+"of the system:administrators group, and the <c>pts membership</c> command to "
+"verify the new membership"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1019
+msgid "Make admin a member of the administrators group and verify"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1019
+#, no-wrap
+msgid ""
+"\n"
+"# <i>pts adduser admin system:administrators -cell &lt;cell name&gt; -noauth</i>\n"
+"# <i>pts membership admin -cell &lt;cell name&gt; -noauth</i>\n"
+"Groups admin (id: 1) is a member of:\n"
+"system:administrators\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1029
+msgid "Properly (re-)starting the AFS server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1032
+msgid ""
+"At this moment, proper authentication is possible, and the OpenAFS server "
+"can be started in a normal fashion. Note that authentication also requires a "
+"running OpenAFS client (setting it up is described in the previous chapter)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1042
+msgid "Shutdown bosserver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1042
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos shutdown &lt;server name&gt; -wait -noauth</i>\n"
+"# <i>killall bosserver</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1047
+msgid "Normal OpenAFS server (and client) startup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1047
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/openafs-server start</i>\n"
+"# <i>/etc/init.d/openafs-client start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1052
+msgid "Adding AFS server to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1052
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add openafs-server default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1056
+msgid "Getting a token as the admin user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1056
+#, no-wrap
+msgid ""
+"\n"
+"# <i>klog admin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1074
+msgid "Starting the File Server, Volume Server and Salvager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1077
+msgid ""
+"Start the <c>fs</c> process, which consists of the File Server, Volume "
+"Server and Salvager (fileserver, volserver and salvager processes)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1082
+msgid "Start the fs process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1082
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos create &lt;server name&gt; fs \\\n"
+"fs /usr/libexec/openafs/fileserver /usr/libexec/openafs/volserver /usr/libexec/openafs/salvager \\\n"
+"-cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1088
+msgid "Verify that all processes are running:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1092
+msgid "Check if all processes are running"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1092
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos status &lt;server name&gt; -long -noauth</i>\n"
+"Instance kaserver, (type is simple) currently running normally.\n"
+"Process last started at Mon Jun  4 21:07:17 2001 (2 proc starts)\n"
+"Last exit at Mon Jun  4 21:07:17 2001\n"
+"Command 1 is '/usr/libexec/openafs/kaserver'\n"
+"\n"
+"Instance buserver, (type is simple) currently running normally.\n"
+"Process last started at Mon Jun  4 21:07:17 2001 (2 proc starts)\n"
+"Last exit at Mon Jun  4 21:07:17 2001\n"
+"Command 1 is '/usr/libexec/openafs/buserver'\n"
+"\n"
+"Instance ptserver, (type is simple) currently running normally.\n"
+"Process last started at Mon Jun  4 21:07:17 2001 (2 proc starts)\n"
+"Last exit at Mon Jun  4 21:07:17 2001\n"
+"Command 1 is '/usr/libexec/openafs/ptserver'\n"
+"\n"
+"Instance vlserver, (type is simple) currently running normally.\n"
+"Process last started at Mon Jun  4 21:07:17 2001 (2 proc starts)\n"
+"Last exit at Mon Jun  4 21:07:17 2001\n"
+"Command 1 is '/usr/libexec/openafs/vlserver'\n"
+"\n"
+"Instance fs, (type is fs) currently running normally.\n"
+"Auxiliary status is: file server running.\n"
+"Process last started at Mon Jun  4 21:09:30 2001 (2 proc starts)\n"
+"Command 1 is '/usr/libexec/openafs/fileserver'\n"
+"Command 2 is '/usr/libexec/openafs/volserver'\n"
+"Command 3 is '/usr/libexec/openafs/salvager'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1122
+msgid ""
+"Your next action depends on whether you have ever run AFS file server "
+"machines in the cell."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1127
+msgid ""
+"If you are installing the first AFS Server ever in the cell, create the "
+"first AFS volume, <b>root.afs</b>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):1132
+msgid ""
+"For the partition name argument, substitute the name of one of the machine's "
+"AFS Server partitions. Any filesystem mounted under a directory called "
+"<path>/vicepx</path>, where x is in the range of a-z, will be considered and "
+"used as an AFS Server partition. Any unix filesystem will do (as opposed to "
+"the client's cache, which can only be ext2/3). Tip: the server checks for "
+"each <path>/vicepx</path> mount point whether a filesystem is mounted there. "
+"If not, the server will not attempt to use it. This behaviour can be "
+"overridden by putting a file named <path>AlwaysAttach</path> in this "
+"directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1143
+msgid "Create the root.afs volume"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1143
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vos create &lt;server name&gt; &lt;partition name&gt; root.afs -cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1147
+msgid ""
+"If there are existing AFS file server machines and volumes in the cell issue "
+"the <c>vos sncvldb</c> and <c>vos syncserv</c> commands to synchronize the "
+"VLDB (Volume Location Database) with the actual state of volumes on the "
+"local machine. This will copy all necessary data to your new server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1154
+msgid ""
+"If the command fails with the message \"partition /vicepa does not exist on "
+"the server\", ensure that the partition is mounted before running OpenAFS "
+"servers, or mount the directory and restart the processes using <c>bos "
+"restart &lt;server name&gt; -all -cell &lt;cell name&gt; -noauth</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1162
+msgid "Synchronise the VLDB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1162
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vos syncvldb &lt;server name&gt; -cell &lt;cell name&gt; -verbose -noauth</i>\n"
+"# <i>vos syncserv &lt;server name&gt; -cell &lt;cell name&gt; -verbose -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1170
+msgid "Starting the Server Portion of the Update Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1173
+msgid "Start the update server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1173
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bos create &lt;server name&gt; \\\n"
+"upserver simple \"/usr/libexec/openafs/upserver \\\n"
+"-crypt /etc/openafs/server -clear /usr/libexec/openafs\" \\\n"
+"-cell &lt;cell name&gt; -noauth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1183
+msgid "Configuring the Top Level of the AFS filespace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1186
+msgid ""
+"First you need to set some ACLs, so that any user can lookup <path>/afs</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):1191
+msgid ""
+"The default OpenAFS client configuration has <b>dynroot</b> enabled. This "
+"option turns <path>/afs</path> into a virtual directory composed of the "
+"contents of your <path>/etc/openafs/CellServDB</path> file. As such, the "
+"following command will not work, because it requires a real AFS directory. "
+"You can temporarily switch dynroot off by setting <b>ENABLE_DYNROOT</b> to "
+"<b>no</b> in <path>/etc/conf.d/openafs-client</path>. Don't forget to issue "
+"a client restart after changing parameters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1201
+msgid "Set access control lists"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1201
+#, no-wrap
+msgid ""
+"\n"
+"# <i>fs setacl /afs system:anyuser rl</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1205
+msgid ""
+"Then you need to create the root volume, mount it readonly on <path>/afs/&lt;"
+"cell name&gt;</path> and read/write on <path>/afs/.&lt;cell name&gt;</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1211
+msgid "Prepare the root volume"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1211
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vos create &lt;server name&gt; &lt;partition name&gt; root.cell</i>\n"
+"# <i>fs mkmount /afs/&lt;cell name&gt; root.cell</i>\n"
+"# <i>fs setacl /afs/&lt;cell name&gt; system:anyuser rl</i>\n"
+"# <i>fs mkmount /afs/.&lt;cell name&gt; root.cell -rw</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1218
+msgid "Adding volumes underneath"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1218
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vos create &lt;server name&gt; &lt;partition name&gt; &lt;myvolume&gt;</i>\n"
+"# <i>fs mkmount /afs/&lt;cell name&gt;/&lt;mymountpoint&gt; &lt;myvolume&gt;</i>\n"
+"# <i>fs mkmount /afs/&lt;cell name&gt;/.&lt;mymountpoint&gt; &lt;myvolume&gt; -rw</i>\n"
+"# <i>fs setquota /afs/&lt;cell name&gt;/.&lt;mymountpoint&gt; -max &lt;quotum&gt;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1225
+msgid ""
+"Finally you're done!!! You should now have a working AFS file server on your "
+"local network. Time to get a big cup of coffee and print out the AFS "
+"documentation!!!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(note):1231
+msgid ""
+"It is very important for the AFS server to function properly, that all "
+"system clocks are synchronized. This is best accomplished by installing a "
+"ntp server on one machine (e.g. the AFS server) and synchronize all client "
+"clocks with the ntp client. This can also be done by the AFS client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1243
+msgid "Basic Administration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1245
+msgid "Disclaimer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1248
+msgid ""
+"OpenAFS is an extensive technology. Please read the AFS documentation for "
+"more information. We only list a few administrative tasks in this chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(title):1256
+msgid "Configuring PAM to Acquire an AFS Token on Login"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1259
+msgid ""
+"To use AFS you need to authenticate against the KA Server if using an "
+"implementation AFS Kerberos 4, or against a Kerberos 5 KDC if using MIT, "
+"Heimdal, or ShiShi Kerberos 5. However in order to login to a machine you "
+"will also need a user account, this can be local in <path>/etc/passwd</"
+"path>, NIS, LDAP (OpenLDAP), or a Hesiod database. PAM allows Gentoo to tie "
+"the authentication against AFS and login to the user account."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1269
+msgid ""
+"You will need to update <path>/etc/pam.d/system-auth</path> which is used by "
+"the other configurations. \"use_first_pass\" indicates it will be checked "
+"first against the user login, and \"ignore_root\" stops the local superuser "
+"being checked so as to order to allow login if AFS or the network fails."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1277
+msgid "/etc/pam.d/system-auth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1277
+#, no-wrap
+msgid ""
+"\n"
+"auth       required     pam_env.so\n"
+"auth       sufficient   pam_unix.so likeauth nullok\n"
+"auth       sufficient   pam_afs.so.1 use_first_pass ignore_root\n"
+"auth       required     pam_deny.so\n"
+"\n"
+"account    required     pam_unix.so\n"
+"\n"
+"password   required     pam_cracklib.so retry=3\n"
+"password   sufficient   pam_unix.so nullok md5 shadow use_authtok\n"
+"password   required     pam_deny.so\n"
+"\n"
+"session    required     pam_limits.so\n"
+"session    required     pam_unix.so\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(p):1293
+msgid ""
+"In order for <c>sudo</c> to keep the real user's token and to prevent local "
+"users gaining AFS access change <path>/etc/pam.d/su</path> as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre:caption):1298
+msgid "/etc/pam.d/su"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(pre):1298
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Here, users with uid &gt; 100 are considered to belong to AFS and users with\n"
+"# uid &lt;= 100 are ignored by pam_afs.</comment>\n"
+"auth       sufficient   pam_afs.so.1 ignore_uid 100\n"
+"\n"
+"auth       sufficient   pam_rootok.so\n"
+"\n"
+"<comment># If you want to restrict users begin allowed to su even more,\n"
+"# create /etc/security/suauth.allow (or to that matter) that is only\n"
+"# writable by root, and add users that are allowed to su to that\n"
+"# file, one per line.\n"
+"#auth       required     pam_listfile.so item=ruser \\\n"
+"#       sense=allow onerr=fail file=/etc/security/suauth.allow\n"
+"\n"
+"# Uncomment this to allow users in the wheel group to su without\n"
+"# entering a passwd.\n"
+"#auth       sufficient   pam_wheel.so use_uid trust\n"
+"\n"
+"# Alternatively to above, you can implement a list of users that do\n"
+"# not need to supply a passwd with a list.\n"
+"#auth       sufficient   pam_listfile.so item=ruser \\\n"
+"#       sense=allow onerr=fail file=/etc/security/suauth.nopass\n"
+"\n"
+"# Comment this to allow any user, even those not in the 'wheel'\n"
+"# group to su</comment>\n"
+"auth       required     pam_wheel.so use_uid\n"
+"\n"
+"auth       required     pam_stack.so service=system-auth\n"
+"\n"
+"account    required     pam_stack.so service=system-auth\n"
+"\n"
+"password   required     pam_stack.so service=system-auth\n"
+"\n"
+"session    required     pam_stack.so service=system-auth\n"
+"session    optional     pam_xauth.so\n"
+"\n"
+"<comment># Here we prevent the real user id's token from being dropped</comment>\n"
+"session    optional     pam_afs.so.1 no_unlog\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//openafs.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/openbox.xml.po b/doc/gettext/ru/openbox.xml.po
new file mode 100644
index 0000000..dd2e04f
--- /dev/null
+++ b/doc/gettext/ru/openbox.xml.po
@@ -0,0 +1,1117 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):6
+msgid "The Openbox Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(mail:link):9
+msgid "nathanzachary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(abstract):15
+msgid ""
+"This guide shows you how to install the Openbox window manager, and "
+"references many potential programs to be used in conjunction with an Openbox "
+"session."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(version):24
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(date):25
+msgid "2010-09-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):28
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):31
+msgid "What is Openbox?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):34
+msgid ""
+"So, you've installed <uri link=\"/doc/en/xorg-config.xml\">The X Server</"
+"uri> and realised that TWM just isn't going to cut it for your needs. You "
+"may have also had some experience with big desktop environments like <uri "
+"link=\"/proj/en/desktop/kde/kde4-guide.xml\">KDE</uri>, <uri link=\"/doc/en/"
+"gnome-config.xml\">GNOME</uri>, and <uri link=\"/doc/en/xfce-config.xml"
+"\">Xfce</uri>. One component of those larger desktop suites is called the "
+"window manager (or WM for short). A window manager is responsible for the "
+"appearance and placement of the containers (or \"windows\") inside which "
+"programs run. Openbox is a minimalistic, no-frills-attached window manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):50
+msgid "Why should I use it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):53
+msgid ""
+"Openbox, unlike the larger desktop environments, depends on very few "
+"libraries. For that reason, it can provide a lightweight graphic environment "
+"that runs very quickly, even on older hardware. Whether your hardware is old "
+"or new, Openbox also provides a highly customisable and unobtrusive working "
+"environment. That means that if you don't want or need a panel, taskbar, "
+"clock, or any other program, those choices are yours to make!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):67
+msgid "Installation and configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):69
+msgid "Initial installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):72
+msgid ""
+"After you have emerged and configured <c>xorg-server</c>, installing Openbox "
+"can be done in one simple command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):77
+msgid "Installing Openbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):77
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av openbox</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):81
+msgid ""
+"Just like with other window managers and desktop environments, you will need "
+"to tell the X Server to load Openbox automatically, by adding it to your "
+"<path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):87
+msgid "Adding Openbox to your .xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):87
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>echo \"exec openbox-session\" &gt;&gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):91
+msgid ""
+"This will automatically start your Openbox session when you type <c>startx</"
+"c> at the terminal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(impo):96
+msgid ""
+"As each user has his or her own <path>.xinitrc</path>, you need to make sure "
+"to issue that command as <e>your user</e>, not as root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):101
+msgid ""
+"If you experience problems with automounting, or if you use dbus and "
+"ConsoleKit, you may want to put <c>exec ck-launch-session dbus-launch "
+"openbox-session</c> in your <path>.xinitrc</path> instead of the default "
+"mentioned above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):107
+msgid ""
+"You can also replace the KDE, GNOME, or Xfce default window manager with "
+"Openbox by following the <uri link=\"#inside-desktop-env\">Openbox inside "
+"desktop environments</uri> directions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):113
+msgid ""
+"Now that you have emerged Openbox and added it to your <path>.xinitrc</"
+"path>, go ahead and issue the <c>startx</c> command to see Openbox in "
+"action. As you can see, the desktop is simply a cluttered mess! In following "
+"with the Openbox philosophy, what you will see is a barebones environment "
+"from which you can build your desktop completely to your liking."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):121
+msgid ""
+"Since you're looking at nothing more than a black screen, you may be "
+"wondering where the menu is. If you click your right mouse button, you will "
+"notice that a menu pops up in the location of your cursor. This menu is "
+"nothing more than an example to illustrate the style of an Openbox menu. "
+"Since it <e>is</e> just an example, none of the items in the menu will work "
+"unless you have actually emerged those programs. In the next section, you "
+"will see how to create your own menu that contains links to <e>your</e> "
+"programs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(impo):131
+msgid ""
+"If you click to view the menu and notice that there is nothing legible, you "
+"need to install some fonts. Two common choices are <c>media-fonts/corefonts</"
+"c> and <c>media-fonts/ttf-bitstream-vera</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):140
+msgid "Menu configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):143
+msgid ""
+"Since the default Openbox menu is essentially useless to you for the reasons "
+"mentioned above, it's time that we create one that will work. Everything in "
+"the Openbox menu is written in the appropriately named <path>menu.xml</path> "
+"file, which can be in the user-specific location of <path>~/.config/openbox/"
+"menu.xml</path>, or in the system-wide location of <path>/etc/xdg/openbox/"
+"menu.xml</path>. By default, the only <path>menu.xml</path> file that is "
+"created is the system-wide one which applies to all users on the system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):154
+msgid ""
+"An easy way to get a basic menu file which you can modify is to use "
+"MenuMaker, which will generate a <path>menu.xml</path> file based on the "
+"programs which you currently have installed on your system. To do so, you "
+"must firstly emerge it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):161
+msgid "Installing MenuMaker"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):161
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge menumaker</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):165
+msgid ""
+"Once it is installed, make sure to logout of root, and back into your user "
+"account. You then instruct MenuMaker to create a menu specifically using the "
+"Openbox XML syntax:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):171
+msgid "Using MenuMaker to generate a basic Openbox menu.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):171
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>mmaker -v OpenBox3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):175
+msgid ""
+"The generated menu will be located at <path>~/.config/openbox/menu.xml</"
+"path>. You can then choose to leave it as your user-specific <path>menu.xml</"
+"path>, or to additionally copy it to the system-wide menu configuration as "
+"well:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):182
+msgid "Overwriting the default system-wide menu.xml files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):182
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp .config/openbox/menu.xml /etc/xdg/openbox/menu.xml</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(impo):186
+msgid ""
+"It is a good idea to use MenuMaker to generate a default menu, as it will "
+"have the Openbox root-menu items. These items include a virtual desktop "
+"switcher, and the commands to restart and exit your Openbox session."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):192
+msgid ""
+"When you open up the <path>menu.xml</path> file in your favourite editor "
+"(nano, for example), you will notice that the XML tags used are very human-"
+"readable and easily understandable. You may choose to modify the default "
+"file to fit your needs, or you may want to write it from scratch (don't "
+"worry, it's really not that difficult). The basic syntax for the menu XML is "
+"as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):200
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):219
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):284
+msgid "Editing the menu.xml file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):200
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
+"&lt;openbox_menu&gt;\n"
+"&lt;separator label=\"NAME_OF_SEPARATOR\" /&gt;\n"
+"&lt;menu id=\"IDENTIFIER\" label=\"NAME_OF_MENU\"&gt;\n"
+"  &lt;item label=\"NAME_OF_PROGRAM\"&gt;\n"
+"    &lt;action name=\"execute\"&gt;&lt;execute&gt;/LOCATION/OF/BINARY&lt;/execute&gt;&lt;/action&gt;\n"
+"  &lt;/item&gt;\n"
+"&lt;/menu&gt;\n"
+"&lt;/openbox_menu&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):212
+msgid ""
+"The above example will work for any applications that launch with standard "
+"options in their own windows, but what if you need to append options to the "
+"program at launch time? That is no problem either, but the syntax of the "
+"menu item is slightly different."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):219
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
+"&lt;openbox_menu&gt;\n"
+"&lt;separator label=\"NAME_OF_SEPARATOR\" /&gt;\n"
+"&lt;menu id=\"IDENTIFIER\" label=\"NAME_OF_MENU\"&gt;\n"
+"  &lt;item label=\"NAME_OF_PROGRAM\"&gt;\n"
+"    &lt;action name=\"execute\"&gt;&lt;command&gt;/LOCATION/OF/BINARY --OPTION1 --OPTION2&lt;/command&gt;&lt;/action&gt;\n"
+"  &lt;/item&gt;\n"
+"&lt;/menu&gt;\n"
+"&lt;/openbox_menu&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):231
+msgid ""
+"Simply replace anything in CAPS in the above two examples with your "
+"information. Alternatively, you can <c>emerge obmenu</c>, which is a "
+"graphical interface allowing you to create your menus without having to "
+"manually edit the <path>menu.xml</path> file. It is a very small application "
+"and offers a nice amount of customisation without typing any XML."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):242
+msgid "Openbox theme and behaviour configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):245
+msgid ""
+"Aside from being minimalistic and lightweight, Openbox is also surprisingly "
+"customisable and flexible. As a user, you can easily change various settings "
+"related to theme, appearance, window placement, docking, and more. There are "
+"two options for configuring these settings within Openbox. You may either "
+"manually edit <path>~/.config/openbox/rc.xml</path>, or you may want a GUI "
+"to help you quickly change settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):254
+msgid ""
+"If you want to manually edit <path>rc.xml</path>, you simply open up your "
+"favourite text editor and start making changes. You might want to make a "
+"backup of the original file just in case, and store it in a location like "
+"<path>~/.config/openbox/rc.xml.default</path>. There are plenty of comments "
+"within the document itself that should help you with editing. Alternatively, "
+"you may want to look at the <uri link=\"http://icculus.org/openbox/index.php/"
+"Help:Contents#Configuration\">Openbox configuration guides</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):265
+msgid ""
+"If manually editing <path>rc.xml</path> doesn't sound like your cup of tea, "
+"you may want to use the GTK+ application to manage your themes and "
+"behaviours in Openbox. The application that you will use is called ObConf, "
+"and can be installed on your system just as easily as was Openbox itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):272
+msgid "Installing ObConf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):272
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge obconf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):276
+msgid ""
+"You can then open the configurator by typing <c>obconf</c> in your terminal. "
+"Next, you can go and add an entry for ObConf into your <path>menu.xml</path> "
+"so it will show up in your Openbox menu. If the \"editing the menu.xml file"
+"\" code listing above seemed too vague to be helpful, we'll use ObConf as an "
+"example of a menu entry:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):284
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
+"&lt;openbox_menu&gt;\n"
+"&lt;menu id=\"1\" label=\"Configuration\"&gt;\n"
+"  &lt;item label=\"OpenBox Config\"&gt;\n"
+"    &lt;action name=\"execute\"&gt;&lt;execute&gt;/usr/bin/obconf&lt;/execute&gt;&lt;/action&gt;\n"
+"  &lt;/item&gt;\n"
+"&lt;/menu&gt;\n"
+"&lt;/openbox_menu&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):295
+msgid ""
+"While ObConf is a great GUI tool for editing many behaviour-related settings "
+"for Openbox, it doesn't allow one to manipulate nearly as many settings as "
+"are presented in the <path>rc.xml</path> file itself. If you are having "
+"trouble finding a particular setting which you would like to change, please "
+"consult the <uri link=\"http://openbox.org/wiki/Configuration\">Openbox "
+"Wiki</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):304
+msgid ""
+"In recent versions of Openbox (namely &gt;3.4.7.2), one may experience a "
+"delay in the submenu opening. This setting was introduced into the rc.xml "
+"file, and is listed as &lt;submenuShowDelay&gt;100&lt;/submenuShowDelay&gt;. "
+"Simply choose a lower number that suits your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):314
+msgid "Autostart configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):317
+msgid ""
+"As mentioned above, you don't see a whole lot when you issue the <c>startx</"
+"c> command for the first time after installing Openbox. In addition to "
+"customising your menus and changing the behaviour of the window manager, you "
+"will probably want to have some programs automatically start with your "
+"Openbox session. There is an easily-editable <path>autostart.sh</path> "
+"script that allows you to do just that. Just like with the <path>menu.xml</"
+"path> file, there are two different locations of the <path>autostart.sh</"
+"path> script--the system-wide (<path>/etc/xdg/openbox/autostart.sh</path>), "
+"and the user-defined (<path>~/.config/openbox/autostart.sh</path>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):329
+msgid ""
+"In the default <path>autostart.sh</path>, you will notice a bunch of lines "
+"calling for programs like the gnome-settings-daemon, XDG, and others. These "
+"lines will generate errors upon logout if you don't have the programs "
+"installed and configured. The easiest thing to do when getting started with "
+"Openbox is to just comment out these lines by using the # symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):336
+msgid "Commenting out lines in autostart.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):336
+#, no-wrap
+msgid ""
+"\n"
+"# Run XDG autostart things. By default don't run anything desktop-specific\n"
+"# DESKTOP_ENV=\"\"\n"
+"# if which /usr/lib/openbox/xdg-autostart &gt;/dev/null; then\n"
+"#  /usr/lib/openbox/xdg-autostart $DESKTOP_ENV\n"
+"# fi\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):344
+msgid ""
+"In the above example, the comment symbol (#) was added before each line. The "
+"commenting method is preferred to just deleting the lines because you may "
+"want to add support for some of those startup items at a later time. Thus, "
+"leaving the default lines in place could ease that process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):351
+msgid ""
+"Adding your own programs to the <path>autostart.sh</path> script is as easy "
+"as writing in the program name for many applications. For instance, if you "
+"have <uri link=\"http://packages.gentoo.org/package/app-admin/conky\">Conky</"
+"uri> (a lightweight system monitor) installed, and want it to start "
+"automatically with your Openbox session, you simply add the following line "
+"to your <path>autostart.sh</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):360
+msgid "Adding Conky to your autostart.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):360
+#, no-wrap
+msgid ""
+"\n"
+"conky &amp;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):364
+msgid ""
+"The ampersand (&amp;) after the command allows that application to load up "
+"in the background. You will most likely want to load all the applications in "
+"your <path>autostart.sh</path> script in the background because doing so "
+"will let Openbox and other programs load without the previous one finishing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):374
+msgid "Setting the background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):377
+msgid ""
+"Some things that you might take for granted in bigger desktop environments "
+"are not included by default in Openbox. One such thing is setting your "
+"desktop background. In order to place an image as your wallpaper, you will "
+"need to emerge a program like <uri link=\"http://packages.gentoo.org/package/"
+"media-gfx/feh\">feh</uri> or <uri link=\"http://packages.gentoo.org/package/"
+"x11-misc/nitrogen\">nitrogen</uri>. <c>feh</c> is a simple image viewer that "
+"can also set the background, <e>and</e> it can easily be put into the "
+"autostart script. Once you have emerged <c>feh</c>, you can issue the "
+"following command to set the background:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):389
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):405
+msgid "Using feh to set the background image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):389
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(feh has many other options instead of --bg-scale, \n"
+"which will scale the image to the screen dimensions.\n"
+"Consult the feh documentation.)</comment>\n"
+"$ <i>feh --bg-scale /path/to/image.jpg</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):396
+msgid ""
+"Once you have set the background manually, a file called <path>.fehbg</path> "
+"will be created in your home directory. This file simply contains the above "
+"command that you just entered in the terminal, and is automatically updated "
+"when you issue a different background command. Now, to set your background "
+"automatically upon login, you can add the following line to your "
+"<path>autostart.sh</path> script:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):405
+#, no-wrap
+msgid ""
+"\n"
+"source $HOME/.fehbg &amp;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):409
+msgid ""
+"If you don't particularly care for the idea of having to issue a command in "
+"the terminal in order to set your background, you can alternatively use "
+"<c>nitrogen</c>. It will allow you to set a folder for your background "
+"images, view thumbnails of those images, and fit, stretch, or tile them to "
+"your desktop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):417
+msgid ""
+"Installing <c>nitrogen</c> and getting it into your Openbox menu requires a "
+"few more steps than are readily apparent. First, you need to <c>emerge "
+"nitrogen</c>. Second, you need to run <c>nitrogen</c> with your backgrounds "
+"folder appended:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):423
+msgid "Starting nitrogen with your image folder"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):423
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>nitrogen /path/to/your/backgrounds/folder</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):427
+msgid ""
+"Third, you can set your background image, but it will not be there after you "
+"logout. Just as with <c>feh</c>, you need to restore your background by "
+"editing your <path>autostart.sh</path> script to have the following line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):433
+msgid "Restoring your background with nitrogen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):433
+#, no-wrap
+msgid ""
+"\n"
+"nitrogen --restore &amp;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):437
+msgid ""
+"This will cause nitrogen to load automatically when you start your Openbox "
+"session, and that can lead to a slightly slower load time than using feh."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):447
+msgid "Programs to use with Openbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):451
+msgid ""
+"The following is a list of some programs which you might want to use within "
+"your Openbox environment. While the list contains numerous terminal "
+"emulators, file managers, panels, and more, it should by no means be "
+"considered exhaustive. If none of the programs listed fit your needs, please "
+"check the appropriate categories in Portage for more options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):462
+msgid "Terminal emulators"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):466
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxterminal"
+"\">LXterminal</uri> is the default terminal emulator for LXDE. It is very "
+"lightweight, and based on VTE. While EvilVTE offers many more customisation "
+"options (including transparency), LXterminal has a graphical interface for "
+"some of the more common options (font, colors, et cetera)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):474
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-terms/evilvte\">EvilVTE</"
+"uri> is an extremely lightweight terminal emulator based on (you guessed it) "
+"VTE. It supports tabs, multiple encodings, as well as an easy and extensible "
+"configuration file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):481
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-terms/mrxvt\">Mrxvt</uri> "
+"is a multi-tabbed rxvt clone with XFT, transparent background and CJK "
+"support. It also features session support for each tab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):486
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-terms/aterm\">Aterm</uri> "
+"supports transparency and backwards compatibility with rxvt. It was "
+"originally designed for the AfterStep window manager, but easily integrates "
+"with other environments."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):492
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-terms/eterm\">Eterm</uri> "
+"is a terminal based on vt102 and designed to be a more feature-rich "
+"replacement for xterm."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):497
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-terms/rxvt-unicode\">Rxvt-"
+"unicode</uri> is a clone of rxvt that supports Unicode, daemons, embedded "
+"perl, and multiple fonts simultaneously."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):503
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-terms/terminal"
+"\">Terminal</uri> is the VTE-based default for the Xfce desktop environment, "
+"so it does require some Xfce libraries to run. However, it is still fairly "
+"speedy, and supports transparency and is easily customised."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):515
+msgid "File managers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):519
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/pcmanfm\">PCManFM</"
+"uri> is the lightweight filemanager from LXDE. It supports tabbed browsing, "
+"drag and drop, thumnails for images, bookmarks, volume management, "
+"searching, and more. It also provides supports for managing the desktop "
+"background and drawing desktop icons (both optionally)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):527
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/xfce-base/thunar\">Thunar</"
+"uri> is the standard file manager from Xfce. It features a bulk renamer, "
+"user-customisable actions, and an extension framework, along with many "
+"optional plugins, such as media tag editing. It depends on several Xfce "
+"libraries, but it's still slimmed down compared to other file managers like "
+"Nautilus (from GNOME), and Konqueror (from KDE)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):535
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/gnome-base/nautilus"
+"\">Nautilus</uri> is the powerful file manager from the GNOME desktop "
+"environment. It features volume management, thumbnails for images, "
+"searching, and some system configuration. As it depends on many of the GNOME "
+"libraries for proper function, it can seem a bit heavy compared to some of "
+"the other file managers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):544
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/app-misc/gentoo\">Gentoo</"
+"uri> (no relation to this glorious Linux distribution) is a two-pane style "
+"file manager. It is incredibly lightweight, but lacks a some features now "
+"prominent in modern file managers. It should definitely be considered for "
+"older hardware, or if you are wanting a barebones setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):551
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/app-misc/emelfm2\">emelFM2</"
+"uri> is another file manager in the vein of Midnight Commander. It features "
+"a two-pane window. As with the Gentoo file manager (listed above), it is "
+"barebones and does not include many features prevalent in newer file "
+"managers. However, it also offers a few features not found in other file "
+"managers, such as a built-in commandline in a separate pane."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):565
+msgid "Desktop management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):569
+msgid ""
+"Though <uri link=\"http://packages.gentoo.org/package/x11-misc/pcmanfm"
+"\">PCManFM</uri> is mainly a file manager, it also gives you the option to "
+"manage the desktop background (instead of using <c>feh</c> or <c>nitrogen</"
+"c>) and draw desktop icons."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):576
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/idesk\">iDesk</uri> "
+"is a simple program used to draw desktop icons. It supports shadowed and "
+"anti-aliased fonts, PNG images, \"snap-to-grid\" placement, and changing the "
+"desktop background."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):587
+msgid "Panels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):591
+msgid ""
+"<uri link=\"http://code.google.com/p/tint2/\">Tint2</uri> is a simple, "
+"lightweight panel and taskbar. It supports color, transparency, a clock, "
+"drag and drop between virtual desktops, a system tray, and comes with a "
+"battery monitor. You can even add a button to display the applications menu "
+"from your window manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):598
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/pypanel\">PyPanel</"
+"uri> is an easily customised panel written in Python and C. It features "
+"transparency, shading, tinting, location and layout configuration, font "
+"type, autohiding, application launcher, clock, and more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):605
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxpanel\">LXPanel</"
+"uri> is the default panel and taskbar from LXDE. It features a launcher, "
+"menu, clock, and a GUI-based configurator. It is feature-rich while "
+"depending on very few packages, making it a good choice for a lean system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):612
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/xfce-base/xfce4-panel\">Xfce4-"
+"panel</uri> is the default panel from the Xfce desktop environment. It "
+"supports application launchers, detachable menus, a pager, tasklist, clock, "
+"applets, and more. It does, however, require a few of the Xfce libraries "
+"which are not dependencies of some other panels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):620
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/fbpanel\">FBpanel</"
+"uri> is a simple, extremely lightweight panel that supports window lists, "
+"launchers, a clock, and a few other goodies. It's not the most featureful "
+"panel, and it can be cumbersome to configure, but it needs only GTK+ to run."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):632
+msgid "Pagers and systrays"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):636
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/netwmpager"
+"\">NetWMpager</uri> is an EWMH-compliant pager that integrates nicely into "
+"any of the *box environments. It is not as obtrusive, and is much more "
+"readily customisable than many of the other available pagers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):643
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/bbpager\">BBpager</"
+"uri> is a desktop pager that was originally written for BlackBox, but works "
+"nicely with Openbox as well. It does have some BlackBox dependencies though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):649
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-plugins/docker\">Docker</"
+"uri> is the system tray that is made especially for Openbox. It has no extra "
+"dependencies, and gives you the ability to view and use tray icons for "
+"supported GTK and QT-based applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):656
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/trayer\">Trayer</"
+"uri> is a system tray that was modified from the FBpanel code, and is often "
+"used with FVWM. One of its perks is that it supports transparency."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):666
+msgid "Session management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):670
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxsession\"> "
+"LXsession</uri> is the stripped down session manager from LXDE. It is "
+"designed to remember applications that the user was running at the last "
+"logout, and to automatically restart those programs. It also supports the "
+"HAL daemon."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):677
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/xfce-base/xfce4-session\"> "
+"Xfce4-session</uri> is the session manager from, you guessed it, Xfce. It is "
+"capable of saving several sessions, and provides methods for logging out, "
+"rebooting, and suspending your computer. It does, however, have many Xfce "
+"dependencies."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):689
+msgid "Configuration tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):693
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/obconf\">ObConf</"
+"uri> is a GUI application allowing you to customise the Openbox window "
+"manager without manually editing <path>~/.config/openbox/rc.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):698
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/lxde-base/lxappearance"
+"\">LXappearance</uri> is a GTK theme and icon configurator used with LXDE. "
+"It provides a nice graphical interface for setting the theme and icons, "
+"while depending on very few extra libraries."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):705
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-themes/gtk-chtheme\">GTK-"
+"ChTheme</uri> is a simple application allowing for easier switching of GTK "
+"themes and your font. Currently, it does not allow for the switching of icon "
+"themes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):711
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-themes/gtk-theme-switch"
+"\">GTK-theme-switch</uri> is another simple application that lets you change "
+"your GTK theme."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):721
+msgid "Miscellaneous"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):725
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/app-admin/conky\">Conky</uri> "
+"is a lightweight system monitor that can display over 250 objects, including "
+"date and time, CPU usage, memory usage, IMAP/POP3 email, top processes, "
+"hardware sensor data, and even info from your music player. It is highly "
+"customisable both in appearance and data display. We also have a <uri link="
+"\"/doc/en/conky-howto.xml\">Conky configuration guide</uri> available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):733
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/app-editors/leafpad"
+"\">Leafpad</uri> is a simple text editor. It is very lightweight, but "
+"includes features like codeset options, and the ability to undo/redo without "
+"limits."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):739
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/media-gfx/feh\">feh</uri> is "
+"a simple image viewer that runs from the terminal, but it also has many "
+"other features. It can display a slideshow of images, create an index print, "
+"dynamically zoom, and set the desktop background (detailed instructions "
+"above)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):746
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/media-gfx/gpicview"
+"\">GPicView</uri> is a GUI-based image viewer. Though it has more "
+"dependencies than <c>feh</c>, it is incredibly quick to load and run."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):752
+msgid ""
+"<uri link=\"http://packages.gentoo.org/package/x11-misc/slim\">SLiM</uri> is "
+"the Simple Login Manager, which allows you to login to your Openbox session "
+"via a graphical interface instead of the terminal. It has very few "
+"dependencies, and supports many themes, but should not be used on machines "
+"that require remote logins."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):766
+msgid "Openbox inside desktop environments"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):768
+msgid "LXDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):771
+msgid ""
+"If installing each component of a working environment sounds like a little "
+"<e>too</e> much customisation, but you still want the flexibility of "
+"Openbox, you may want to look into a desktop environment that uses Openbox "
+"as its default window manager. That environment is <uri link=\"http://www."
+"lxde.org/\">LXDE</uri>, the Lightweight X Desktop Environment. Designed to "
+"require even fewer system resources than Xfce, it is built around Openbox."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):783
+msgid "Openbox inside GNOME"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):786
+msgid ""
+"If you already have a GNOME environment installed, you may just want to "
+"replace the Metacity window manager with Openbox. Fortunately, this is quite "
+"a simple task! You will need to fire up your favourite editor, open your "
+"<path>~/.xinitrc</path> file, and put the following command inside it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):793
+msgid "Adding an Openbox-GNOME session to your .xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):793
+#, no-wrap
+msgid ""
+"\n"
+"exec openbox-gnome-session\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):797
+msgid ""
+"If you use GDM or another graphical login manager, you will see a new "
+"\"GNOME/Openbox\" option in your session menu. You can simply select that "
+"option instead of manually editing your <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):806
+msgid "Openbox inside KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):809
+msgid ""
+"Say you have KDE installed and like it, but you want more flexibility with "
+"your window management than KWin offers. You can use Openbox as your window "
+"manager inside of KDE by simply editing your <path>~/.xinitrc</path> file, "
+"and replacing your current exec command with the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):816
+msgid "Adding an Openbox-KDE session to your .xinitrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):816
+#, no-wrap
+msgid ""
+"\n"
+"exec openbox-kde-session\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):820
+msgid ""
+"Now when you issue <c>startx</c> you will see KDE, but instead of KWin, you "
+"will have the customisability of the Openbox window manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):825
+msgid ""
+"If you use KDM or another graphic login manager, you will see a new \"KDE/"
+"Openbox\" option in your session menu. You can simply select that option "
+"instead of manually editing your <path>~/.xinitrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):831
+msgid ""
+"This method of using Openbox with KDE has been tested with the KDE 3.x "
+"releases. While it seems highly likely that it will work with the KDE 4.x "
+"series, it has not been thoroughly tested as of yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):840
+msgid "Openbox inside Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):843
+msgid ""
+"If you use Xfce4 and would like to replace xfwm4 with Openbox, you will need "
+"to go about it a little differently than with KDE or GNOME. First, you need "
+"to start your normal Xfce session, and open up a terminal. From the "
+"terminal, issue the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):850
+msgid "Killing xfwm4 and replacing it with Openbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):850
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>killall xfwm4 ; openbox &amp; exit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):854
+msgid ""
+"Second, you need to exit out of your Xfce session, and make sure to tick the "
+"checkbox that says \"Save session for future login.\" This will keep Openbox "
+"as your default window manager. Third, you will notice that you can't logout "
+"properly when using the default menu action. To fix this problem, open up "
+"your <path>menu.xml</path>, and locate this line:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):862
+msgid "Finding the exit action in menu.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):862
+#, no-wrap
+msgid ""
+"\n"
+"&lt;item label=\"Exit\"&gt;\n"
+"     &lt;action name=\"Exit\"/&gt;\n"
+"&lt;/item&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):868
+msgid "Change it to this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre:caption):872
+msgid "Replacing the exit action in menu.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(pre):872
+#, no-wrap
+msgid ""
+"\n"
+"&lt;item label=\"Exit\"&gt;\n"
+"  &lt;action name=\"Execute\"&gt;\n"
+"    &lt;command&gt;xfce4-session-logout&lt;/command&gt;\n"
+"  &lt;/action&gt;\n"
+"&lt;/item&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(note):880
+msgid ""
+"With Xfce4, the root-menu provided by Xfdesktop will be used instead of the "
+"Openbox root-menu."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):890
+msgid "Further documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(title):892
+msgid "External resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(p):895
+msgid ""
+"While this document will easily take you through the inital installation and "
+"customisation of Openbox, it is by no means the only reference on the topic. "
+"There are several other resources that will aid you in creating your perfect "
+"Openbox setup. Some of them are listed below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):903
+msgid ""
+"On <uri link=\"http://openbox.org/\">The Official Openbox website</uri> you "
+"will find more detailed information regarding theming, creating menus "
+"(including pipe menus), autostart scripting, and much more. This site also "
+"has information regarding new releases, upgrades, and instructions on how "
+"you can contribute to development."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):910
+msgid ""
+"The <uri link=\"http://urukrama.wordpress.com/openbox-guide/\">Urukrama's "
+"Guide to Openbox</uri> blog contains a plethora of information about "
+"switching GTK+ themes, setting up keybindings, desktop effects, and other "
+"programs to use in conjunction with Openbox. Though the tutorial was "
+"originally written for use with Ubuntu, everything is applicable to Gentoo "
+"(and other Linux distributions for that matter)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(li):918
+msgid ""
+"<uri link=\"http://www.box-look.org/\">Box-Look</uri> provides numerous "
+"themes, icons, wallpapers, fonts, and tools to be used with Openbox (as well "
+"as the other *box window managers like Fluxbox, Blackbox, PekWM, etc.)"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//openbox.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/openrc-migration.xml.po b/doc/gettext/ru/openrc-migration.xml.po
new file mode 100644
index 0000000..35043d1
--- /dev/null
+++ b/doc/gettext/ru/openrc-migration.xml.po
@@ -0,0 +1,560 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(guide:link):5
+msgid "/doc/en/openrc-migration.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):6
+msgid "Baselayout and OpenRC Migration Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(mail:link):9
+msgid "cardoe"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(author:title):14
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(mail:link):15
+msgid "uberlord"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(abstract):18
+msgid ""
+"This guide shows you how to migrate from baselayout-1 to baselayout-2 and "
+"OpenRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(version):27
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(date):28
+msgid "2010-07-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):31
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):33
+msgid "What's baselayout?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):36
+msgid ""
+"Baselayout provides a basic set of files that are necessary for all systems "
+"to function properly, such as <path>/etc/hosts</path>. It also provides the "
+"basic filesystem layout used by Gentoo (i.e. <path>/etc</path>, <path>/var</"
+"path>, <path>/usr</path>, <path>/home</path> directories)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):46
+msgid "What's OpenRC?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):49
+msgid ""
+"OpenRC is a dependency-based rc system that works with whatever init is "
+"provided by the system, normally <path>/sbin/init</path>. However, it is "
+"<e>not</e> a replacement for <path>/sbin/init</path>. The default init used "
+"by Gentoo Linux is <c>sys-apps/sysvinit</c>, while Gentoo/FreeBSD uses the "
+"FreeBSD init provided by <c>sys-freebsd/freebsd-sbin</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):60
+msgid "So why migrate?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):63
+msgid ""
+"Originally Gentoo's rc system was built into baselayout 1 and written "
+"entirely in bash. This led to several limitations. For example, certain "
+"system calls need to be accessed during boot and this required C-based "
+"callouts to be added. These callouts were each statically linked, causing "
+"the rc system to bloat over time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):70
+msgid ""
+"Additionally, as Gentoo expanded to other platforms like Gentoo/FreeBSD and "
+"Gentoo Embedded, it became impossible to require a bash-based rc system. "
+"This led to a development of baselayout 2, which is written in C and only "
+"requires a POSIX-compliant shell. During the development of baselayout 2, it "
+"was determined that it was a better fit if baselayout merely provided the "
+"base files and filesystem layout for Gentoo and the rc system was broken off "
+"into its own package. Thus we have OpenRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):80
+msgid ""
+"OpenRC is primarily developed by <uri link=\"http://roy.marples.name/openrc"
+"\">Roy Marples</uri> and supports all current Gentoo variations (i.e. Gentoo "
+"Linux, Gentoo/FreeBSD, Gentoo Embedded, and Gentoo Vserver) and other "
+"platforms such as FreeBSD and NetBSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):92
+msgid "Migration to OpenRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):96
+msgid ""
+"Migration to OpenRC is fairly straightforward; it will be pulled in as part "
+"of your regular upgrade process by your package manager. The most important "
+"step actually comes after you install the new <c>&gt;=sys-apps/baselayout-2</"
+"c> and <c>sys-apps/openrc</c> packages. It is <e>critical</e> that you run "
+"<c>dispatch-conf</c> and ensure your <path>/etc</path> is up to date before "
+"rebooting. <brite>Failure to do so will result in an unbootable system</"
+"brite> and will require the use of the Gentoo LiveCD to perform the steps "
+"below to repair your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):107
+msgid ""
+"Once you've finished updating your config files, there are a few things to "
+"verify prior to rebooting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):116
+msgid "/etc/conf.d/rc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):119
+msgid ""
+"<path>/etc/conf.d/rc</path> has been deprecated and any settings you have in "
+"there will need to be migrated to the appropriate settings in <path>/etc/rc."
+"conf</path>. Please read through <path>/etc/rc.conf</path> and <path>/etc/"
+"conf.d/rc</path> and migrate the settings. Once you are complete, delete "
+"<path>/etc/conf.d/rc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):130
+msgid "Kernel modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):133
+msgid ""
+"Normally, when you want certain kernel modules automatically loaded at boot, "
+"you place them into <path>/etc/modules.autoload.d/kernel-2.6</path> along "
+"with any parameters you wanted to pass to them. In baselayout-2, this file "
+"is not used anymore. Instead, autoloaded modules and module parameters are "
+"placed in one file, <path>/etc/conf.d/modules</path>, no matter the kernel "
+"version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):141
+msgid "An example old style configuration would be:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):145
+msgid "/etc/modules.autoload.d/kernel-2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):145
+#, no-wrap
+msgid ""
+"\n"
+"ivtv\n"
+"cx88_dvb video_br=2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):150
+msgid "Converting the above example would result in the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):154
+msgid "/etc/conf.d/modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):154
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Modules autoloaded at boot</comment>\n"
+"modules_2_6=\"ivtv cx88_dvb\"\n"
+"<comment># Module parameters</comment>\n"
+"module_cx88_dvb_args_2_6=\"video_br=2\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):161
+msgid ""
+"In the above examples, the modules and their parameters would only be passed "
+"to 2.6.x series kernels. The new configuration allows for fine grained "
+"control over the modules and parameters based on kernel version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):167
+msgid "An in-depth example would be:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):171
+msgid "detailed example of /etc/conf.d/modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):171
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Always load ochi1394 and ieee1394, no matter the kernel version</comment>\n"
+"modules=\"ohci1394 ieee1394\"\n"
+"<comment># Only load tun and usbserial for 2.6.x series kernels</comment>\n"
+"modules_2_6=\"tun usbserial\"\n"
+"<comment># Only load cx88_dvb for 2.6.23 kernels</comment>\n"
+"modules_2_6_23=\"cx88_dvb\"\n"
+"<comment># Only load ivtv for 2.6.23-gentoo-r5</comment>\n"
+"modules_2_6_23_gentoo_r5=\"ivtv\"\n"
+"\n"
+"<comment># For 2.6.23-gentoo-r5, pass video_br=2 to cx88_dvb</comment>\n"
+"module_cx88_dvb_args_2_6_23_gentoo_r5=\"video_br=2\"\n"
+"<comment># For 2.6.x series kernels, always pass vendor and product</comment>\n"
+"module_usbserial_args_2_6=\"vendor=0x1410 product=0x2110\"\n"
+"<comment># Always pass debug to ieee1394</comment>\n"
+"module_ieee1394_args=\"debug\" \n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(impo):189
+msgid ""
+"The <b>module*</b> variables are not cumulative. The more version-specific "
+"variables will override the more general variables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(note):194
+msgid "Please note the difference between <b>module_</b> and <b>modules_</b>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):201
+msgid "Boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):204
+msgid ""
+"The <c>boot</c> runlevel performs several important steps for every machine. "
+"For example, making sure your root filesystem is mounted read/write, that "
+"your filesystems are checked for errors, that your mountpoints are "
+"available, and that the <path>/proc</path> pseudo-filesystem is started at "
+"boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):211
+msgid ""
+"With OpenRC, volume management services for your block storage devices are "
+"no longer run automatically at boot. This includes lvm, raid, swap, device-"
+"mapper (dm), dm-crypt, evms, and the like. You must ensure the appropriate "
+"initscript for these services is in the <c>boot</c> runlevel, otherwise it's "
+"possible that your system will not boot!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):219
+msgid ""
+"While the OpenRC ebuild will attempt to do this migration for you, you "
+"should verify that it migrated all the volume management services properly:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):224
+msgid "Display all services in boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):224
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls -l /etc/runlevels/boot/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):228
+msgid ""
+"If you don't see root, procfs, mtab, swap, and fsck in the above listing, "
+"perform the following to add them to the <c>boot</c> runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):233
+msgid "Adding critical services to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):233
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add root boot</i>\n"
+"# <i>rc-update add procfs boot</i>\n"
+"# <i>rc-update add mtab boot</i>\n"
+"# <i>rc-update add fsck boot</i>\n"
+"# <i>rc-update add swap boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):241
+msgid ""
+"If you know you use mdraid and lvm but do not see them above, you would run "
+"the following to add initscripts to the <c>boot</c> runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):246
+msgid "Adding mdraid and lvm to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):246
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add mdraid boot</i>\n"
+"# <i>rc-update add lvm boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):254
+msgid "Udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):257
+msgid ""
+"OpenRC no longer starts <c>udev</c> by default, but it does need to be "
+"present in the <c>sysinit</c> runlevel to be started. The OpenRC ebuild "
+"should detect if <c>udev</c> was previously enabled and add it to the "
+"<c>sysinit</c> runlevel. However, to be safe, check if <c>udev</c> is "
+"present:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):264
+msgid "Verifying udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):264
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls -l /etc/runlevels/sysinit</i>\n"
+"lrwxrwxrwx 1 root root 14 2009-01-29 08:00 /etc/runlevels/sysinit/udev -&gt; \\\n"
+"/etc/init.d/udev\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):270
+msgid "If <c>udev</c> is not listed, add it to the correct runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):274
+msgid "Adding udev to the sysinit runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):274
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add udev sysinit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):281
+msgid "Network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):284
+msgid ""
+"Due to baselayout and OpenRC being broken into two different packages, your "
+"net.eth0 initscript may disappear during the upgrade process. To replace "
+"this initscript please perform the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):290
+msgid "Adding back missing net.eth0 script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):290
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/init.d</i>\n"
+"# <i>ln -s net.lo net.eth0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):295
+msgid ""
+"If you are missing any other network initscripts, follow the instructions "
+"above to re-add them. Simply replace <c>eth0</c> with the name of your "
+"network device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):301
+msgid ""
+"Also, <path>/etc/conf.d/net</path> no longer uses bash-style arrays for "
+"configuration. Please review <path>/usr/share/doc/openrc-&lt;version&gt;/net."
+"example</path> for configuration instructions. Conversion should be "
+"relatively straight-forward, for example a static IP assignment would change "
+"as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):309
+msgid "Old /etc/conf.d/net style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):309
+#, no-wrap
+msgid ""
+"\n"
+"config_eth0=( \"192.168.1.37 netmask 255.255.255.0 brd 192.168.1.255\" )\n"
+"routes_eth0=( \"default via 192.168.1.100\" )\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):314
+msgid "New /etc/conf.d/net style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):314
+#, no-wrap
+msgid ""
+"\n"
+"config_eth0=\"192.168.1.37 netmask 255.255.255.0 brd 192.168.1.255\"\n"
+"routes_eth0=\"default via 192.168.1.100\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):322
+msgid "Clock"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):325
+msgid ""
+"Clock settings have been renamed from <path>/etc/conf.d/clock</path> to your "
+"system's native tool for adjusting the clock. This means on Linux it will be "
+"<path>/etc/conf.d/hwclock</path> and on FreeBSD it will be <path>/etc/conf.d/"
+"adjkerntz</path>. Systems without a working real time clock (RTC) chip "
+"should use <path>/etc/init.d/swclock</path>, which sets the system time "
+"based on the mtime of a file which is created at system shutdown. The "
+"initscripts in <path>/etc/init.d/</path> have also been renamed accordingly, "
+"so make sure the appropriate script for your system has been added to the "
+"boot runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):337
+msgid ""
+"Additionally, the <c>TIMEZONE</c> variable is no longer in this file. Its "
+"contents are instead found in the <path>/etc/timezone</path> file. If it "
+"doesn't exist, you will of course have to create it with your timezone. "
+"Please review both of these files to ensure their correctness."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):344
+msgid ""
+"The proper value for this file is the path relative to your timezone from "
+"<path>/usr/share/zoneinfo</path>. For example, for someone living on the "
+"east coast of the United States, the following would be a correct setting:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):350
+msgid "/etc/timezone"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):350
+#, no-wrap
+msgid ""
+"\n"
+"America/New_York\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):357
+msgid "XSESSION"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):360
+msgid ""
+"The XSESSION variable is no longer found in <path>/etc/rc.conf</path>. "
+"Instead, you can set the XSESSION variable per-user in <path>~/.bashrc</"
+"path> (or equivalent), or system-wide in <path>/etc/env.d/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):366
+msgid "Here's an example of setting XSESSION for the whole system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):370
+msgid "Setting XSESSION system-wide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):370
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo 'XSESSION=\"Xfce4\"' &gt; /etc/env.d/90xsession</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(impo):374
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(impo):394
+msgid ""
+"You must run <c>env-update</c> after creating a file in <path>/etc/env.d</"
+"path>, and then logout and login for it to take effect. If you set the "
+"variable in <path>~/.bashrc</path>, you can re-source the file with "
+"<c>source ~/.bashrc</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):384
+msgid "EDITOR and PAGER"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):387
+msgid ""
+"The EDITOR variable is no longer found in <path>/etc/rc.conf</path>. Both "
+"EDITOR and PAGER are set by default in <path>/etc/profile</path>. You should "
+"change this as needed in your <path>~/.bashrc</path> (or equivalent) file or "
+"create <path>/etc/env.d/99editor</path> and set the system default there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):404
+msgid "Boot log"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):407
+msgid ""
+"Previously, you could log the boot process by using <c>app-admin/"
+"showconsole</c>. However, OpenRC now handles all logging internally, so "
+"there's no need for the hacks that <c>showconsole</c> employed. You can "
+"safely unmerge <c>showconsole</c>. To continue logging boot messages, just "
+"set the appropriate variable in <path>/etc/rc.conf</path>. Logs will appear "
+"in <path>/var/log/rc.log</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre:caption):416
+msgid "Enabling boot logging in /etc/rc.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(pre):416
+#, no-wrap
+msgid ""
+"\n"
+"rc_logger=\"YES\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(title):423
+msgid "Finishing up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(p):426
+msgid ""
+"Once you've finished updating your config files and initscripts, the last "
+"thing to do is <b>reboot</b>. This is necessary because system state "
+"information is not preserved during the upgrade, so you'll need to provide "
+"it with a fresh boot."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//openrc-migration.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/overview.xml.po b/doc/gettext/ru/overview.xml.po
new file mode 100644
index 0000000..05f94e1
--- /dev/null
+++ b/doc/gettext/ru/overview.xml.po
@@ -0,0 +1,36 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(version):10
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(title):12
+msgid "Documentation Development Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(title):19
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(p):22
+msgid ""
+"On this page you'll find an overview of all available documentation files, "
+"important bugs, etc."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//overview.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/pda-guide.xml.po b/doc/gettext/ru/pda-guide.xml.po
new file mode 100644
index 0000000..05a630e
--- /dev/null
+++ b/doc/gettext/ru/pda-guide.xml.po
@@ -0,0 +1,444 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(guide:link):5
+msgid "/doc/en/pda-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):6
+msgid "Gentoo PDA Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(mail:link):12
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(mail):12
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(abstract):15
+msgid ""
+"Nowadays, personal digital assistants, or PDAs, are quite popular. Not only "
+"do they provide more features than before, they are also easy to handle, "
+"even by people who aren't that computer literate. But how can you "
+"synchronise these PDAs with your Gentoo Linux installation if they are "
+"almost all running Windows Mobile?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(version):27
+msgid "1.0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(date):28
+msgid "2007-11-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):31
+msgid "Setting up PDA Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):33
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):147
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):36
+msgid ""
+"PDAs are everywhere. They are an evolution of the paper journals and address "
+"books and have become very feature-rich: addresses and telephone numbers, "
+"pictures and movies, small spreadsheets or documents, calender entries, ... "
+"anything is possible with PDAs. And thanks to wireless technology, PDAs can "
+"manipulate or receive data from various devices (like GPS devices or other "
+"PDAs) or join the world-wide Internet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):45
+msgid ""
+"However, most PDAs run a propriatary operating system and might not be easy "
+"to synchronise with your computer if you are not running software of the "
+"same vendor. Luckily, the free software community has made serious efforts "
+"in reverse engineering access to the PDAs and some companies have even "
+"opened their specification to connect with the PDA. This guide will cover "
+"accessing and synchronizing PDAs with your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):57
+msgid "Kernel Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):60
+msgid ""
+"The first thing we need to do is get the kernel to recognize our device. "
+"Open up the kernel configuration (for instance, through <c>make menuconfig</"
+"c>) and add support for your PDA. If your device uses USB to connect to a "
+"computer you will most likely find support for it under <e>Device Drivers -"
+"&gt; USB support -&gt; USB Serial Converter support</e>. For instance, iPAQ "
+"users (and many others) can use the <e>USB PocketPC PDA Driver</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):69
+msgid "Kernel Driver Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):69
+#, no-wrap
+msgid ""
+"\n"
+"&lt;M&gt; USB Serial Converter support\n"
+"[ ]   USB Serial Console device support (EXPERIMENTAL)\n"
+"[ ]   USB Generic Serial Driver\n"
+"&lt; &gt;   USB Belkin and Peracom Single Port Serial Driver\n"
+"&lt; &gt;   USB ConnectTech WhiteHEAT Serial Driver\n"
+"&lt; &gt;   USB Digi International AccelePort USB Serial Driver\n"
+"&lt; &gt;   USB Cypress M8 USB Serial Driver\n"
+"&lt; &gt;   USB Empeg empeg-car Mark I/II Driver\n"
+"&lt; &gt;   USB FTDI Single Port Serial Driver (EXPERIMENTAL)\n"
+"&lt; &gt;   USB Handspring Visor / Palm m50x / Sony Clie Driver\n"
+"&lt;M&gt;   USB PocketPC PDA Driver\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):83
+msgid ""
+"You might wonder why it is called a <e>Serial Converter</e>. This is because "
+"you are going to use USB (technology) to talk with your device, even though "
+"the device itself is accessed using a serial protocol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):89
+msgid "You will also need asynchronous PPP support:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):93
+msgid "Kernel Driver Setup for Async PPP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):93
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"  Network device support ---&gt;\n"
+"    &lt;M&gt; PPP (point-to-point protocol) support\n"
+"      &lt;M&gt; PPP support for async serial ports\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):100
+msgid ""
+"Rebuild the kernel and its modules. If you only had to modify a module, you "
+"can install the modules and continue. Otherwise, set up the new kernel in "
+"your boot loader and reboot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):109
+msgid "Detecting Your PDA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):112
+msgid ""
+"Ok, now that we have the kernel module setup, let's go ahead and get some "
+"information. Plug in your device and take a look at your modules list if you "
+"have build support for the device as a kernel module:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):118
+msgid "Checking if your PDA is detected"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):118
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lsmod</i>\n"
+"Module                  Size  Used by\n"
+"ipaq                   30736  0\n"
+"usbserial              25120  1 ipaq\n"
+"<comment>(...)</comment>\n"
+"\n"
+"# <i>dmesg | grep Pocket</i>\n"
+"drivers/usb/serial/usb-serial.c: USB Serial support registered for PocketPC PDA\n"
+"drivers/usb/serial/ipaq.c: USB PocketPC PDA driver v0.5\n"
+"ipaq 3-2:1.0: PocketPC PDA converter detected\n"
+"usb 3-2: PocketPC PDA converter now attached to ttyUSB0\n"
+"\n"
+"# <i>ls -la /dev/ttyUSB0</i>\n"
+"crw-rw---- 1 root uucp 188, 0 Sep 27 19:21 /dev/ttyUSB0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):135
+msgid ""
+"As we can see, the device has been detected and is now accessible through "
+"<path>/dev/ttyUSB0</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):145
+msgid "Using SynCE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):150
+msgid ""
+"<uri link=\"http://www.synce.org\">SynCE</uri> is the tool you can use to "
+"connect to and work with Windows Mobile and Windows CE powered devices. The "
+"tool connects, through the device set up earlier, to the device and allows "
+"applications to synchronise appointments, addresses and more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):157
+msgid ""
+"A list of devices supported through SynCE can be found on the <uri link="
+"\"http://www.synce.org\">SynCE website</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):162
+msgid ""
+"SynCE is not available through a stable ebuild though, so before installing "
+"it, you will first need to mark them in <path>/etc/portage/package.keywords</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):167
+msgid "List of packages to list in package.keywords"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):167
+#, no-wrap
+msgid ""
+"\n"
+"app-pda/synce\n"
+"app-pda/synce-software-manager\n"
+"app-pda/synce-librapi2\n"
+"app-pda/synce-libsynce\n"
+"app-pda/synce-multisync_plugin\n"
+"app-pda/synce-rra\n"
+"dev-libs/libmimedir\n"
+"app-pda/synce-dccm\n"
+"app-pda/synce-trayicon\n"
+"app-pda/orange\n"
+"app-pda/dynamite\n"
+"app-pda/synce-kde\n"
+"app-pda/synce-gnomevfs\n"
+"app-pda/synce-serial\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):184
+msgid ""
+"Then, install the <c>app-pda/synce</c> and <c>net-dialup/ppp</c> packages to "
+"obtain the necessary tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):192
+msgid "Configuring the PDA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):195
+msgid ""
+"The next task is to configure the serial device we found earlier (<path>/dev/"
+"ttyUSB0</path> in our example) to be used with SynCE:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):200
+msgid "Configuring the serial device for SynCE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):200
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>synce-serial-config ttyUSB0</i>\n"
+"\n"
+"You can now run synce-serial-start to start a serial connection.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):206
+msgid ""
+"This step only has to be performed once: it stored the necessary PPP-related "
+"information inside <path>/etc/ppp/peers/synce-device</path> which is read by "
+"PPP when it is called by <c>synce-serial-start</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):215
+msgid "Accessing The Device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):218
+msgid ""
+"Now, log on as the user who will be using the PDA and run the <c>vdccm</c> "
+"command. This tool is the connection manager for SynCE through which "
+"programs connect to the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):224
+msgid "Launching the connection manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):224
+#, no-wrap
+msgid ""
+"\n"
+"~$ <i>vdccm</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):228
+msgid ""
+"As root again, run <c>synce-serial-start</c> which will connect to the "
+"device. With some PDAs, you will notice this on the PDA itself through a "
+"synchronisation symbol or any other event."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):234
+msgid "Running synce-serial-start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):234
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>synce-serial-start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):238
+msgid ""
+"In some cases, the first attempts fail but this isn't shown immediately. You "
+"can rerun the command a few times until the command replies that a serial "
+"connection is already started. To verify that the connection is done, check "
+"if a ppp interface (like ppp0) is created and has an IP address attached to "
+"it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):245
+msgid ""
+"When <path>ppp0</path> is started, the configuration starts the <path>/etc/"
+"init.d/net.ppp0</path> init script which is configured through <path>/etc/"
+"conf.d/net.ppp0</path>, so you definitely want to take a look at this "
+"configuration file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):255
+msgid "File Navigation and Manipulation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):258
+msgid ""
+"The SynCE project provides a number of programs to communicate with the PDA "
+"and exchange files. The tools have similar namings as on a regular Unix "
+"system but with a <c>p</c> prepended to it: <c>pcp</c>, <c>pls</c>, <c>pmv</"
+"c>, <c>prm</c>, <c>pmkdir</c>, <c>prmdir</c>. Other tools are specific for "
+"PDAs, like <c>prun</c> to launch a program, <c>synce-install-cab</c> to "
+"install a CAB file or <c>pstatus</c> to display information about the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):267
+msgid ""
+"Beware though, the behavior of the tools is not all that intuïtive. For "
+"instance, the <c>pls</c> tool shows the contents of the <path>My Documents</"
+"path> directory whereas the <c>pcp</c> tool starts from the <path>My Device</"
+"path> location. As an example, we'll upload a file to the <path>My "
+"Documents</path> folder:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre:caption):275
+msgid "Uploading a file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(pre):275
+#, no-wrap
+msgid ""
+"\n"
+"~$ <i>pls</i>\n"
+"Directory               Tue 01 Jan 2002 01:00:00 PM CET  Business/\n"
+"Directory               Tue 01 Jan 2002 01:00:00 PM CET  Personal/\n"
+"Directory               Tue 01 Jan 2002 01:00:00 PM CET  Templates/\n"
+"~$ <i>pcp music.mp3 :\"My Documents/music.mp3\"</i>\n"
+"File copy of 3852416 bytes took 0 minutes and 38 seconds, that's 101379 bytes/s.\n"
+"~$ <i>pls</i>\n"
+"Archive        3852416  Wed 02 Jan 2002 07:05:06 PM CET  music.mp3\n"
+"Directory               Tue 01 Jan 2002 01:00:00 PM CET  Business/\n"
+"Directory               Tue 01 Jan 2002 01:00:00 PM CET  Personal/\n"
+"Directory               Tue 01 Jan 2002 01:00:00 PM CET  Templates/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):292
+msgid "SynCE for KDE Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):295
+msgid ""
+"The <uri link=\"http://synce.sourceforge.net/synce/kde/\">SynCE for KDE "
+"Project</uri> aims to support PDAs within KDE by facilitating file exchange, "
+"synchronisation and installation and even provide mirroring capabilities so "
+"you can control your PDA from within KDE."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):303
+msgid ""
+"The <c>raki</c> tool is SynCE's PocketPC management tool for KDE. The first "
+"time you launch it, it asks whether you use <c>dccm</c> or <c>vdccm</c>. "
+"Once you selected the connection manager you use (in our example it would be "
+"<c>vdccm</c>) your KDE session (or any environment which supports KDE "
+"applets) will now have a PDA applet from which you can browse and "
+"synchronise your PDA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):311
+msgid ""
+"However, KDE integration for PDAs is better maintained through KPilot..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):320
+msgid "All-In-One Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(title):322
+msgid "KPilot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(note):325
+msgid ""
+"The author did not get KPilot to run well on his iPAQ as it timed out before "
+"the connection was made. If anyone knows a possible solution to this, please "
+"report this at <uri link=\"https://bugs.gentoo.org/XXXXXX\">bug XXXXXX</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):331
+msgid ""
+"The <c>kde-base/kpilot</c> application provides synchronisation support from "
+"the PDA with Kontact (KDE) or Evolution (GNOME). Its setup is quite easy: "
+"install the package and launch it. The first time you run it, it will ask "
+"you to identify your PDA, either by passing on the device name or having "
+"KPilot auto-detect the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(p):339
+msgid ""
+"Once configured, you can quickly synchronise tasks, data, addresses and "
+"messages between your PDA and Kontact, the KDE PIM manager."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//pda-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/portage-utils.xml.po b/doc/gettext/ru/portage-utils.xml.po
new file mode 100644
index 0000000..5896814
--- /dev/null
+++ b/doc/gettext/ru/portage-utils.xml.po
@@ -0,0 +1,357 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(guide:link):5
+msgid "/doc/en/portage-utils.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):7
+msgid "Portage-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail:link):10
+msgid "rane@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail):10
+msgid "Łukasz Damentko"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(author:title):12
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(author:title):15
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail:link):13
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail):13
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail:link):16
+msgid "vanquirius@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(mail):16
+msgid "Marcelo Góes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(abstract):19
+msgid ""
+"This guide covers some common uses of portage-utils, a set of fast Portage "
+"helper applications written in C."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(version):28
+msgid "1.3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(date):29
+msgid "2007-05-23"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):32
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):36
+msgid ""
+"<c>portage-utils</c> is a collection of very fast utilities written in C, "
+"which are meant to offer a faster but more limited alternative to their "
+"<c>gentoolkit</c> counterparts. Please note that <c>portage-utils</c> is not "
+"meant to replace <c>gentoolkit</c>. Its utilities are much more efficient "
+"than the equivalent ones from <c>gentoolkit</c> and might be better suited "
+"to be used in scripts that need to call Portage repeatedly, but <c>portage-"
+"utils</c> does not offer the same functionalities. It does not consider "
+"eclasses at all and does not provide tools like <c>revdep-rebuild</c> and "
+"<c>glsa-check</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):47
+msgid ""
+"More information about <c>gentoolkit</c> can be found in the <uri link=\"/"
+"doc/en/gentoolkit.xml\">Gentoolkit</uri> guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):52
+msgid ""
+"You can view the complete list of applications in <c>portage-utils</c> by "
+"typing <c>man q</c> or <c>q --help</c>. Please read the man page for each "
+"utility described, as this guide is only meant to be a short reference for "
+"the most useful functions and does not include all the information about "
+"each application."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):60
+msgid "The first step of using <c>portage-utils</c> is to install the package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):64
+msgid "Installing portage-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):64
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge portage-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):73
+msgid "Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):75
+msgid "How to find a package to which a file belongs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):78
+msgid "<c>qfile</c> finds the package to which a file belongs:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):82
+msgid "Finding the package to which a file belongs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):82
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>qfile /etc/fonts/fonts.conf</i>\n"
+"media-libs/fontconfig (/etc/fonts/fonts.conf)\n"
+"$ <i>qfile /usr/share/keymaps/atari/atari-uk-falcon.map.gz</i>\n"
+"sys-apps/kbd (/usr/share/keymaps/atari/atari-uk-falcon.map.gz)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):92
+msgid "Verifying package integrity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):95
+msgid ""
+"If you want to check MD5 sums or mtimes of the files installed by some "
+"package, you can do it using the <c>qcheck</c> application:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):100
+msgid "Checking package integrity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):100
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>qcheck portage-utils</i>\n"
+"Checking app-portage/portage-utils-0.1.13 ...\n"
+"  * 36 out of 36 files are good\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):106
+msgid ""
+"Of course, all the files which were changed after installation will be "
+"reported here. If the application reports configuration files which you have "
+"manually edited after installation, there's nothing to worry about."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):115
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):125
+msgid "Listing packages which depend on some package"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):118
+msgid ""
+"Of course there's also an application which allows you to list all the "
+"packages which depend on some package. This is done using <c>qdepends</c>. "
+"Use the <c>-a</c> flag to show all the DEPEND, RDEPEND, and PDEPEND "
+"information for a package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):125
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>qdepends -a pygtk</i>\n"
+" * DEPEND\n"
+"dev-python/pygtk-2.8.2: &gt;=dev-lang/python-2.3 &gt;=x11-libs/gtk+-2.8.0\n"
+"&gt;=dev-libs/glib-2.8.0 &gt;=x11-libs/pango-1.10.0 &gt;=dev-libs/atk-1.8.0\n"
+"&gt;=gnome-base/libglade-2.5.0 &gt;=dev-python/pycairo-0.9.0 dev-python/numeric\n"
+"virtual/opengl dev-python/pyopengl &gt;=x11-libs/gtkglarea-1.99\n"
+"&gt;=dev-util/pkgconfig-0.9 sys-devel/patch\n"
+" * RDEPEND\n"
+"dev-python/pygtk-2.8.2: &gt;=dev-lang/python-2.3 &gt;=x11-libs/gtk+-2.8.0\n"
+"&gt;=dev-libs/glib-2.8.0 &gt;=x11-libs/pango-1.10.0 &gt;=dev-libs/atk-1.8.0\n"
+"&gt;=gnome-base/libglade-2.5.0 &gt;=dev-python/pycairo-0.9.0 dev-python/numeric\n"
+"virtual/opengl dev-python/pyopengl &gt;=x11-libs/gtkglarea-1.99\n"
+" * PDEPEND\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):144
+msgid "Listing files that belong to an ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):147
+msgid "<c>qlist</c> gives you a list of all files that belong to an ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):151
+msgid "Listing files which belong to an ebuild file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):151
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>qlist vim</i>\n"
+"/usr/bin/gvim\n"
+"/usr/bin/gvimdiff\n"
+"/usr/bin/evim\n"
+"/usr/bin/eview\n"
+"/usr/bin/gview\n"
+"/usr/bin/rgvim\n"
+"[...]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):165
+msgid "Looking for packages that use some USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):168
+msgid ""
+"This is done with <c>quse</c>, which must be run as root. It may take some "
+"time to first create/update the ebuild cache."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):173
+msgid "Looking for packages with the 'firefox' USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):173
+#, no-wrap
+msgid ""
+"\n"
+"# <i>quse firefox</i>\n"
+"app-office/openoffice/openoffice-2.0.2_rc1.ebuild binfilter curl eds firefox gnome gtk java kde ldap xml2\n"
+"dev-haskell/gtk2hs/gtk2hs-0.9.10.ebuild doc glade gnome firefox\n"
+"dev-java/swt/swt-3.1-r1.ebuild accessibility cairo firefox gnome\n"
+"[...]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):184
+msgid "Finding package sizes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):187
+msgid "This is done with <c>qsize</c> application and is as simple as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):191
+msgid "Finding package size"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):191
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>qsize vim</i>\n"
+"app-editors/gvim-6.4: 10 files, 7 non-files, 2327.516 KB\n"
+"app-editors/vim-6.4: 6 files, 2 non-files, 2058.14 KB\n"
+"app-editors/vim-core-6.4: 1024 files, 68 non-files, 10950.984 KB\n"
+"[...]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):202
+msgid "Searching the Portage tree"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):205
+msgid ""
+"One of the most powerful tools of <c>portage-utils</c> is <c>qsearch</c>. "
+"This tool allows you to search your Portage tree much faster than default "
+"<c>emerge -s</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):211
+msgid "Here are some examples of its usage:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):215
+msgid "Using qsearch to search the tree"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):215
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(I forgot the name of the package with my favorite fonts)</comment>\n"
+"$ <i>qsearch terminus</i>\n"
+"media-fonts/terminus-font A clean fixed font for the console and X11\n"
+"\n"
+"<comment>(I want to thank the guy who made them. What's his homepage?)</comment>\n"
+"$ <i>qsearch -H terminus</i>\n"
+"media-fonts/terminus-font http://www.is-vn.bg/hamster/jimmy-en.html\n"
+"\n"
+"<comment>(I need a jabber client and I need it now)</comment>\n"
+"$ <i>qsearch -S \"jabber client\"</i>\n"
+"app-emacs/emacs-jabber A Jabber client for Emacs.\n"
+"net-im/gajim Jabber client written in PyGTK\n"
+"net-im/gnome-jabber Gnome Jabber Client\n"
+"net-im/gossip Lightweight Jabber client for GNOME\n"
+"net-im/imcom Python commandline Jabber Client\n"
+"net-im/psi QT 3.x Jabber Client, with Licq-like interface\n"
+"net-im/tkabber Featureful Jabber client for tcl/tk.\n"
+"x11-themes/psi-themes Iconsets for Psi, a QT 3.x Jabber Client\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(title):239
+msgid "Extracting information from emerge logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(p):242
+msgid ""
+"There is also a tool that allows you to extract useful information from your "
+"<path>emerge.log</path> file. It's called <c>qlop</c> and it can be useful "
+"when you want to estimate package compilation times or compare with your "
+"friends whose computer compiles faster. It also allows you to check what's "
+"compiling at the moment and how long it will take - which is handy when "
+"you're working in the console and don't have any other means to check it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre:caption):251
+msgid "Reading emerge logs with qlop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(pre):251
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(I'm starting to emerge perl and I want an estimate on how long it usually takes)</comment>\n"
+"$ <i>qlop -tH perl</i>\n"
+"perl: 7 minutes, 52 seconds for 4 merges\n"
+"<comment>(Now let's see what's emerging at the moment)</comment>\n"
+"$ <i>qlop -c</i>\n"
+"* perl-5.8.8-r23\n"
+"    started: Mon May 21 12:41:11 2007\n"
+"    elapsed: 19 seconds\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//portage-utils.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/postgres-howto.xml.po b/doc/gettext/ru/postgres-howto.xml.po
new file mode 100644
index 0000000..4a5d6a5
--- /dev/null
+++ b/doc/gettext/ru/postgres-howto.xml.po
@@ -0,0 +1,1014 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(guide:link):5
+msgid "/doc/en/postgres-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):6
+msgid "PostgreSQL Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(mail:link):12
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(mail):12
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(abstract):15
+msgid ""
+"This guide is meant to show the basic setup of PostgreSQL. The setup "
+"described here should be sufficient enough to use for basic web "
+"appplications, and any other program that provides PostgreSQL support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(version):25
+msgid "1.2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(date):26
+msgid "2007-04-25"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):29
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):31
+msgid "PostgreSQL introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):34
+msgid ""
+"When talking to most developers about the different database solutions to "
+"use, two major databases will usually form the answer. One would be "
+"<c>MySQL</c>, and the other is what this document will refer to, "
+"<c>PostgreSQL</c>. The advantages of one over the other is a somewhat long "
+"winded debate, however it is just to say that PostgreSQL has had a more firm "
+"grasp on true relational database structure than MySQL. Most of the standard "
+"features such as <b>FOREIGN KEY</b> was only just added in MySQL 5. However, "
+"whatever the case may be, this document assumes that you have selected "
+"PostgreSQL as the database to use. The first place to start is the "
+"<c>emerge</c> process. In the next section, the installation process through "
+"emerge will be described, as well as the basic configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):51
+msgid "PostgreSQL installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):54
+msgid ""
+"To begin, we must first <c>emerge</c> the PostgreSQL package. To do so, run "
+"the following code to first ensure that the options for it are properly set:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):59
+msgid "Checking the PostgreSQL build options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):59
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -pv postgresql</i>\n"
+"\n"
+"These are the packages that I would merge, in order:\n"
+"\n"
+"Calculating dependencies ...done!\n"
+"[ebuild  N    ] dev-db/postgresql-8.0.4  -doc -kerberos +nls +pam +perl -pg-intdatetime +python +readline (-selinux) +ssl -tcl +xml +zlib 0 kB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):68
+msgid "Here's a list of what the different build options indicate:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):74
+msgid "USE Flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):75
+msgid "Meaning"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):78
+msgid "doc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):79
+msgid ""
+"This USE flag enables or disables the installation of documentation outside "
+"of the standard man pages. The one good time to disable this option is if "
+"you are low on space, or you have alternate methods of getting a hold of the "
+"documentation (online, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):87
+msgid "kerberos"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):88
+msgid ""
+"When connecting to the database, with this option enabled, the admin has the "
+"option of using <c>kerberos</c> to authenticate their users/services to the "
+"database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):95
+msgid "nls"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):96
+msgid ""
+"If this option is enabled, PostgreSQL can utilize translated strings for non-"
+"English speaking users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):102
+msgid "pam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):103
+msgid ""
+"If this option is enabled, and the admin configures the PostgreSQL "
+"configuration file properly, users/services will be able to login to a "
+"PostgreSQL database using <c>PAM</c> (Pluggable Authentication Module)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):110
+msgid "perl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):111
+msgid ""
+"If this option is enabled, <c>perl</c> bindings for PostgreSQL will be built."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):117
+msgid "pg-intdatetime"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):118
+msgid ""
+"If this option is enabled, PostgreSQL will support 64 bit integer date types."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):124
+msgid "python"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):125
+msgid ""
+"If this option is enabled, PostgreSQL will be built with <c>python</c> "
+"bindings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):131
+msgid "readline"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):132
+msgid ""
+"If this option is enabled, PostgreSQL will support <c>readline</c> style "
+"command line editing. This includes command history and isearch."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):138
+msgid "selinux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):139
+msgid ""
+"If this option is enabled, an <c>selinux</c> policy for PostgreSQL will be "
+"installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):145
+msgid "ssl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):146
+msgid ""
+"If this option is enabled, PostgreSQL will utilize the <c>OpenSSL</c> "
+"library to encrypt traffic between PostgreSQL clients and servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):152
+msgid "tcl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):153
+msgid "If this option is enabled, PostgreSQL will build <c>tcl</c> bindings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):158
+msgid "xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):159
+msgid ""
+"If this option is enabled, <c>XPATH</c> style xml support will be built. "
+"More information on using xml support with PostgreSQL can be found on: <uri "
+"link=\"http://www.throwingbeans.org/postgresql_and_xml.html\"> PostgreSQL "
+"and XML</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):167
+msgid "zlib"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):168
+msgid ""
+"This isn't really used by PostgreSQL itself, but by <c>pg_dump</c> to "
+"compress the dumps it produces."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):175
+msgid ""
+"Once you've customized PostgreSQL to meet your specific needs, go ahead and "
+"start the <c>emerge</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):180
+msgid "Emerge-ing PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):180
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge postgresql</i>\n"
+"<comment>(Output shortened)</comment>\n"
+"&gt;&gt;&gt; /usr/lib/libecpg.so.5 -&gt; libecpg.so.5.0\n"
+"&gt;&gt;&gt; /usr/bin/postmaster -&gt; postgres\n"
+" * Make sure the postgres user in /etc/passwd has an account setup with /bin/bash as the shell\n"
+" *\n"
+" * Execute the following command\n"
+" * emerge --config =postgresql-8.0.4\n"
+" * to setup the initial database environment.\n"
+" *\n"
+"&gt;&gt;&gt; Regenerating /etc/ld.so.cache...\n"
+"&gt;&gt;&gt; dev-db/postgresql-8.0.4 merged.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):195
+msgid ""
+"As shown by the einfo output, there is some post setup that must be done. "
+"The next chapter will look at the actual configuration of PostgreSQL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):204
+msgid "PostgreSQL configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):206
+msgid "Setting up the initial database environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):209
+msgid ""
+"As noted in the earlier <c>emerge</c> output, the initial database "
+"environment must be setup. However, before this is done, one thing needs to "
+"be considered. Unlike, say MySQL, PostgreSQL's \"root\" password is the "
+"password of the actual user. However, only the user is created by the ebuild "
+"<e>not</e> the password. So before we can begin, the password must be set "
+"for the postgres user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):217
+msgid "Setting the password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):217
+#, no-wrap
+msgid ""
+"\n"
+"# <i>passwd postgres</i>\n"
+"New UNIX password:\n"
+"Retype new UNIX password:\n"
+"passwd: password updated successfully\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):224
+msgid ""
+"Now that this is set up, the creation of the initial database environment "
+"can occur:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):229
+msgid "Configuring the database environment with emerge --config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):229
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --config =postgresql-8.0.4</i>\n"
+"\n"
+"\n"
+"Configuring pkg...\n"
+"\n"
+" * Creating the data directory ...\n"
+" * Initializing the database ...\n"
+"The files belonging to this database system will be owned by user \"postgres\".\n"
+"This user must also own the server process.\n"
+"\n"
+"The database cluster will be initialized with locale C.\n"
+"\n"
+"fixing permissions on existing directory /var/lib/postgresql/data ... ok\n"
+"creating directory /var/lib/postgresql/data/global ... ok\n"
+"creating directory /var/lib/postgresql/data/pg_xlog ... ok\n"
+"creating directory /var/lib/postgresql/data/pg_xlog/archive_status ... ok\n"
+"creating directory /var/lib/postgresql/data/pg_clog ... ok\n"
+"creating directory /var/lib/postgresql/data/pg_subtrans ... ok\n"
+"creating directory /var/lib/postgresql/data/base ... ok\n"
+"creating directory /var/lib/postgresql/data/base/1 ... ok\n"
+"creating directory /var/lib/postgresql/data/pg_tblspc ... ok\n"
+"selecting default max_connections ... 100\n"
+"selecting default shared_buffers ... 1000\n"
+"creating configuration files ... ok\n"
+"creating template1 database in /var/lib/postgresql/data/base/1 ... ok\n"
+"initializing pg_shadow ... ok\n"
+"enabling unlimited row size for system tables ... ok\n"
+"initializing pg_depend ... ok\n"
+"creating system views ... ok\n"
+"loading pg_description ... ok\n"
+"creating conversions ... ok\n"
+"setting privileges on built-in objects ... ok\n"
+"creating information schema ... ok\n"
+"vacuuming database template1 ... ok\n"
+"copying template1 to template0 ... ok\n"
+"\n"
+"WARNING: enabling \"trust\" authentication for local connections\n"
+"You can change this by editing pg_hba.conf or using the -A option the\n"
+"next time you run initdb.\n"
+"\n"
+"Success. You can now start the database server using:\n"
+"\n"
+"    /usr/bin/postmaster -D /var/lib/postgresql/data\n"
+"or\n"
+"    /usr/bin/pg_ctl -D /var/lib/postgresql/data -l logfile start\n"
+"\n"
+" *\n"
+" * You can use /etc/init.d/postgresql script to run PostgreSQL instead of pg_ctl.\n"
+" *\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):281
+msgid ""
+"Now the initial database environment is setup. The next section will look at "
+"verifying the install and setting up users to access the database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):289
+msgid "PostgreSQL database setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):292
+msgid ""
+"Now that PostgreSQL is setup, it's a good idea at this point to verify the "
+"installation. First, make sure the service starts up ok:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):297
+msgid "Starting up the PostgreSQL service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):297
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/postgresql start</i>\n"
+"* Starting PostgreSQL ...                                          [ ok ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):302
+msgid ""
+"Once this is verified working, it's also a good idea to add it to the "
+"default runlevel so it starts at boot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):307
+msgid "Adding to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):307
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add postgresql default</i>\n"
+"* postgresql added to runlevel default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):312
+msgid ""
+"Now that the service has started, it's time to try setting up a test "
+"database. To start out, let's create a test database by using the "
+"<c>createdb</c> command. We'll also pass along the <c>-U</c> option to set "
+"the user (it defaults to the current user name if you don't), and the <c>-W</"
+"c> option to request the password we created earlier. Finally we give it the "
+"name of the database we want to create:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):321
+msgid "Creating a database with createdb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):321
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>createdb -U postgres -W test</i>\n"
+"Password:\n"
+"CREATE DATABASE\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):327
+msgid ""
+"The database was successfully created, and we can confirm that the database "
+"can run basic tasks. We'll go ahead and drop this database (remove it) with "
+"the <c>dropdb</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):333
+msgid "Dropping a database with dropdb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):333
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>dropdb -U postgres -W test</i>\n"
+"Password:\n"
+"DROP DATABASE\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):339
+msgid ""
+"Right now, only the postgres user can run commands. Obviously this is not "
+"the sort of setup one would like in a multi-user environment. The next "
+"section will look at working with user accounts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):348
+msgid "Setting up database user accounts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):351
+msgid ""
+"As mentioned earlier, having to login as the postgres user is somewhat "
+"undesirable in a mult-user environment. In most cases there will be various "
+"users and services accessing the server, and each have different permission "
+"requirements. So, to handle this, the <c>createuser</c> command can be used. "
+"This command is an alternative to running a few SQL queries, and is a lot "
+"more flexible from an admin standpoint. We'll go ahead and create two users, "
+"a 'superuser' that can add other users and administer the db, and a standard "
+"user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):361
+msgid "Setting up the superuser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):361
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(replace chris with the username you'd like to use)</comment>\n"
+"$ <i>createuser -a -d -P -E -U postgres -W chris</i>\n"
+"Enter password for new user:\n"
+"Enter it again:\n"
+"Password:\n"
+"CREATE USER\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):370
+msgid ""
+"There, we've created the superuser. The command line option <c>-a</c> "
+"specifies that this user can add other users. <c>-d</c> means that this user "
+"can create databases. <c>-P</c> let's you enter a password for the user and "
+"<c>-E</c> will encrypt it for security purposes. Now then, we'll test this "
+"new user's permissions out by setting up our standard user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):378
+msgid "Setting up the standard user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):378
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(replace chris with the username you've just created)</comment>\n"
+"$ <i>createuser -A -D -P -E -U chris -W testuser</i>\n"
+"Enter password for new user:\n"
+"Enter it again:\n"
+"Password:\n"
+"CREATE USER\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):387
+msgid ""
+"Success! Our new user was created using the previously created superuser. "
+"The <c>-A</c> and <c>-D</c> options do the opposite of <c>-a</c> and <c>-d</"
+"c>, and instead deny the user the ability to create other users and "
+"databases. Now that there are users to work with, the next chapter will look "
+"at using the new database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):399
+msgid "Using PostgreSQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):401
+msgid "Setting up permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):404
+msgid ""
+"Now there is a user that can create databases and add other users, and the "
+"main postgres user that can do anything. The user created earlier can "
+"currently login to the server, and that's about it. In general, users need "
+"to be able to insert data and retrieve data, and sometimes any other number "
+"of tasks. So, for this new user to be able to do anything, they must be "
+"setup with the proper permissions. This can easily be done by passing the "
+"<c>-O</c> parameter to <c>createdb</c>. We'll start by making a new "
+"database, <b>MyDB</b> with our superuser that will be owned by the previous "
+"testuser:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):415
+msgid "Creating the MyDB database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):415
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>createdb -O testuser -U chris -W MyDB</i>\n"
+"Password:\n"
+"CREATE DATABASE\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):421
+msgid ""
+"Alright, now we have a new MyDB database, and a testuser that can access it. "
+"To test this out, we'll login as the testuser to the new MyDB database. "
+"We'll do this with the <c>psql</c> program. This program is what's used to "
+"connect to the PostgreSQL database from command line. So connect to the new "
+"database like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):429
+msgid "Logging into the MyDB database as the testuser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):429
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>psql -U testuser -W MyDB</i>\n"
+"Password:\n"
+"Welcome to psql 8.0.4, the PostgreSQL interactive terminal.\n"
+"\n"
+"Type:  \\copyright for distribution terms\n"
+"       \\h for help with SQL commands\n"
+"       \\? for help with psql commands\n"
+"       \\g or terminate with semicolon to execute query\n"
+"       \\q to quit\n"
+"\n"
+"MyDB=&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):443
+msgid ""
+"So, the testuser is now logged into the database, and can begin to initiate "
+"some commands. To get a feel for using PostgreSQL, the next section will "
+"take a look at some of the basic commands in navigating the <c>psql</c> "
+"client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):452
+msgid "Basic PostgreSQL commands and creating a table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):455
+msgid ""
+"For those who are used to MySQL, this is somewhat of a definite read. This "
+"is where PostgreSQL may get somewhat unique with regards to running "
+"commands. To start, here is a list of some commands that will be discussed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):463
+msgid "Command"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):464
+msgid "Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(th):465
+msgid "MySQL Equivalent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):468
+msgid "\\c[onnect] [DBNAME|- [USER]]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):469
+msgid "Connects to another database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):470
+msgid "USE DATABASE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):473
+msgid "\\q"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):474
+msgid "Quit the <c>psql</c> client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):475
+msgid "quit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):478
+msgid "\\i FILE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):479
+msgid "Run commands from <c>FILE</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):480
+msgid "source FILE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):483
+msgid "\\o [FILE]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):484
+msgid "Send query results to <c>FILE</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):485
+msgid "INTO OUTFILE, but outputs everything (not just SELECTS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):488
+msgid "\\d [NAME]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):489
+msgid "Describe a database or table (as well as other items)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):490
+msgid "DESC(RIBE)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):493
+msgid "\\db [PATTERN]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):494
+msgid ""
+"List available tables that match <c>PATTERN</c> (all if no pattern is given)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(ti):498
+msgid "SHOW TABLES"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):502
+msgid ""
+"With the exception of <c>\\c[onnect]</c>, all the commands shown will be "
+"used later on in the section. So right now the database is empty. That said, "
+"we need to insert some data. The first step to inserting data, however, is "
+"to put it in a table. Right now there are no tables in the database, so we "
+"need to create one. This is done with the <c>CREATE TABLE</c> command. We'll "
+"make a table of items. They will contain a Product ID, Description, and "
+"price:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):511
+msgid "Creating the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):511
+#, no-wrap
+msgid ""
+"\n"
+"MyDB=&gt; CREATE TABLE products (\n"
+"MyDB(&gt;   product_id SERIAL,\n"
+"MyDB(&gt;   description TEXT,\n"
+"MyDB(&gt;   price DECIMAL\n"
+"MyDB(&gt; );\n"
+"NOTICE:  CREATE TABLE will create implicit sequence \"products_product_id_seq\"\n"
+"for serial column \"products.product_id\"\n"
+"CREATE TABLE\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):522
+msgid ""
+"You can ignore the NOTICE, it's perfectly harmless. Looking at the last line "
+"of the function, <c>CREATE TABLE</c> seems to indicate that the command has "
+"succeeded. However, let's go ahead and verify that the table was indeed "
+"successfully created with the <c>\\d</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):529
+msgid "Looking at the newly created table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):529
+#, no-wrap
+msgid ""
+"\n"
+"MyDB=&gt; <i>\\d products</i>\n"
+"                                 Table \"public.products\"\n"
+"   Column    |  Type   |                            Modifiers\n"
+"-------------+---------+------------------------------------------------------------------\n"
+" product_id  | integer | not null default nextval('public.products_product_id_seq'::text)\n"
+" description | text    |\n"
+" price       | numeric |\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):539
+msgid ""
+"Indeed the table was successfully created. Now that the table is created, it "
+"needs to be populated with data. The next section will look at populating "
+"the database with data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):548
+msgid "Inserting data into the database"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):551
+msgid ""
+"This section will look at the two ways of populating the newly created table "
+"with data. First let's look at the most basic command, <c>INSERT</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):556
+msgid "INSERT syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):556
+#, no-wrap
+msgid ""
+"\n"
+"INSERT INTO [tablename] (column1,column2,column3) VALUES(value1,value2,value3)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):560
+msgid ""
+"<c>tablename</c> contains the name of the table to insert the data into. "
+"(column1,column2,column3) lets you specify the specific columns to insert "
+"the values into. VALUES(value1,value2,value3) is the listing of values. The "
+"values are inserted into the same order as the columns (column1 gets value1, "
+"column2 gets value2, column3 gets value3). These counts <e>must</e> be the "
+"same. So let's go ahead and insert an item into the table:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(impo):569
+msgid ""
+"From working with databases for a long time, I personally recommend "
+"specifying <c>INSERT</c> statements exactly as above. Developers often make "
+"the mistake of using <c>INSERT INTO</c> without specifying columns. This is "
+"unproductive, as if a new column gets added to the database, it will cause "
+"in error if the value to column count is not the same. You should <e>always</"
+"e> specify the columns unless you're 300% sure you'll never add a column."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):578
+msgid "Inserting data into the table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):578
+#, no-wrap
+msgid ""
+"\n"
+"MyDB=&gt; <i>INSERT INTO products (description,price) VALUES('A test product', 12.00);</i>\n"
+"INSERT 17273 1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):583
+msgid ""
+"The last line needs a bit of explaining. The return of an insert command is "
+"an OID (Object Identifier) and the number of rows inserted. OID's are a bit "
+"beyond the scope of this guide, and the <uri link=\"http://www.postgresql."
+"org/docs/8.1/static/datatype-oid.html\">PostgreSQL manual</uri> has some "
+"good information on it. Now, for a situation where you have 20,000 products, "
+"these insert statements can be a little tedious. However, not all is lost. "
+"The <c>COPY</c> command can be used to insert data into a table from a file "
+"or stdin. In this example, let's assume that you have a csv (comma separated "
+"values) file, which contains the product id, description, and price. The "
+"file looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):596
+msgid "products.csv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):596
+#, no-wrap
+msgid ""
+"\n"
+"2,meat,6.79\n"
+"3,soup,0.69\n"
+"4,soda,1.79\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):602
+msgid "Now we'll use the <c>COPY</c> command to populate our data:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(impo):606
+msgid ""
+"The <c>COPY FROM STDIN</c> command is used because only the postgres user "
+"can insert data from a file (for obvious security reasons)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):611
+msgid "Using COPY to populate the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):611
+#, no-wrap
+msgid ""
+"\n"
+"MyDB=&gt; <i>COPY products FROM STDIN WITH DELIMITER AS ',';</i>\n"
+"Enter data to be copied followed by a newline.\n"
+"End with a backslash and a period on a line by itself.\n"
+"&gt;&gt; <i>2,meat,6.79</i>\n"
+"&gt;&gt; <i>3,soup,0.69</i>\n"
+"&gt;&gt; <i>4,soda,1.79</i>\n"
+"&gt;&gt; <i>\\.</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):621
+msgid ""
+"Unfortunately, this line doesn't return the same status information as the "
+"<c>INSERT INTO</c> statement. How do we know the data was inserted? The next "
+"section will look at running queries to check our data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):630
+msgid "Using PostgreSQL queries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):633
+msgid ""
+"This section will look at using the <c>SELECT</c> statement to view data in "
+"our tables. The basic <c>SELECT</c> format looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):638
+msgid "SELECT syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):638
+#, no-wrap
+msgid ""
+"\n"
+"SELECT (column1,column2|*) FROM (table) [WHERE (conditionals)]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):642
+msgid ""
+"There are two ways to select columns. The first is using <c>*</c> to select "
+"all columns, and the second is to specify a list of specific columns you "
+"wish to see. The second is quite handy when you want to find a specific "
+"column in a rather large list of them. Let's start out with using <c>SELECT</"
+"c> with <c>*</c> to specify all columns:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):650
+msgid "Viewing the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):650
+#, no-wrap
+msgid ""
+"\n"
+"MyDB=&gt; <i>SELECT * FROM products;</i>\n"
+" product_id |  description   | price\n"
+"------------+----------------+-------\n"
+"          1 | A test product | 12.00\n"
+"          2 | meat           |  6.79\n"
+"          3 | soup           |  0.69\n"
+"          4 | soda           |  1.79\n"
+"(4 rows)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):661
+msgid ""
+"As shown here, all the data we inserted earlier is indeed in the table. Now "
+"let's say we only want to see the description and the price, and don't care "
+"about the product id. In this case we'll use the column specific SELECT form:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):667
+msgid "Viewing specific columns from the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):667
+#, no-wrap
+msgid ""
+"\n"
+"MyDB=&gt; <i>SELECT description,price FROM products;</i>\n"
+"  description   | price\n"
+"----------------+-------\n"
+" A test product | 12.00\n"
+" meat           |  6.79\n"
+" soup           |  0.69\n"
+" soda           |  1.79\n"
+"(4 rows)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):678
+msgid ""
+"Now only the product and price is shown, letting us focus on only the "
+"important data. Now let's say that we want to see only the items that are "
+"greater than $2.00. Here's where the <c>WHERE</c> clause comes in handy:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre:caption):684
+msgid "Viewing specific rows from the products table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(pre):684
+#, no-wrap
+msgid ""
+"\n"
+"MyDB=&gt; <i>SELECT description,price FROM products WHERE price &gt; 2.00;</i>\n"
+"  description   | price\n"
+"----------------+-------\n"
+" A test product | 12.00\n"
+" meat           |  6.79\n"
+"(2 rows)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):693
+msgid ""
+"Now a listing of products over $2.00 is displayed, focusing the data even "
+"more. These forms of querying for information are very powerful, and can "
+"help create extremely useful reports."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(title):702
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(p):705
+msgid ""
+"This concludes the PostgreSQL Guide. A big thanks goes to Masatomo Nakano, "
+"the previous Gentoo PostgreSQL maintainer for his help in answering my "
+"questions. Any suggestions on this guide should be sent to "
+"<mail>chriswhite@gentoo.org</mail>. For more extensive documentation, see "
+"the <uri link=\"http://www.postgresql.org\">PostgreSQL website</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//postgres-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/power-management-guide.xml.po b/doc/gettext/ru/power-management-guide.xml.po
new file mode 100644
index 0000000..902f3b7
--- /dev/null
+++ b/doc/gettext/ru/power-management-guide.xml.po
@@ -0,0 +1,2221 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):6
+msgid "Power Management Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):9
+msgid "earthwings@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):9
+msgid "Dennis Nienhüser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):12
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):12
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):18
+msgid ""
+"Power Management is the key to extend battery run time on mobile systems "
+"like laptops. This guide assists you setting it up on your laptop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):27
+msgid "1.47"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):28
+msgid "2010-07-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):35
+msgid ""
+"Capacity and lifetime of laptop batteries have improved much in the last "
+"years. Nevertheless modern processors consume much more energy than older "
+"ones and each laptop generation introduces more devices hungry for energy. "
+"That's why Power Management is more important than ever. Increasing battery "
+"run time doesn't necessarily mean buying another battery. Much can be "
+"achieved applying intelligent Power Management policies."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):47
+msgid "A Quick Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):50
+msgid ""
+"Please notice that this guide describes Power Management for <e>laptops</e>. "
+"While some sections might also suite for <e>servers</e>, others do not and "
+"may even cause harm. Please do not apply anything from this guide to a "
+"server unless you really know what you are doing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):57
+msgid ""
+"As this guide has become rather long, here's a short overview helping you to "
+"find your way through it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):62
+msgid ""
+"The <uri link=\"#doc_chap2\">Prerequisites</uri> chapter talks about some "
+"requirements that should be met before any of the following device "
+"individual sections will work. This includes BIOS settings, kernel "
+"configuration and some simplifications in user land. The following three "
+"chapters focus on devices that typically consume most energy - processor, "
+"display and hard drive. Each can be configured seperately. <uri link="
+"\"#doc_chap3\">CPU Power Management</uri> shows how to adjust the "
+"processor's frequency to save a maximum of energy without losing too much "
+"performance. A few different tricks prevent your hard drive from working "
+"unnecessarily often in <uri link=\"#doc_chap5\">Disk Power Management</uri> "
+"(decreasing noise level as a nice side effect). Some notes on graphics "
+"cards, Wireless LAN and USB finish the device section in <uri link="
+"\"#doc_chap6\">Power Management For Other Devices</uri> while another "
+"chapter is dedicated to the (rather experimental) <uri link="
+"\"#doc_chap7\">sleep states</uri>. Last not least <uri link="
+"\"#doc_chap8\">Troubleshooting</uri> lists common pitfalls."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):83
+msgid "Power Budget For Each Component"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:link):87
+msgid "/images/energy-budget.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:short):87
+msgid "Which component consumes how much energy?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:caption):87
+msgid "Power budget for each component"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):89
+msgid ""
+"Nearly every component can operate in different states - off, sleep, idle, "
+"active to name a few - consuming a different amount of energy. Major parts "
+"are consumed by the LCD display, CPU, chipset and hard drives. Often one is "
+"able to activate OS-independent Power Management in the BIOS, but an "
+"intelligent setup in the operating system adapting to different situations "
+"can achieve much more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):102
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):106
+msgid ""
+"Before discussing the details of making individual devices Power Management "
+"aware, make sure certain requirements are met. After controlling BIOS "
+"settings, some kernel options want to be enabled - these are in short ACPI, "
+"sleep states and CPU frequency scaling. As power saving most of the time "
+"comes along with performance loss or increased latency, it should only be "
+"enabled when running on batteries. That's where a new runlevel <e>battery</"
+"e> comes in handy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):118
+msgid "The BIOS Part"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):121
+msgid ""
+"First have a look into your BIOS Power Management settings. The best way is "
+"to combine BIOS and operating system policies, but for the moment it's "
+"better to disable most of the BIOS part. This makes sure it doesn't "
+"interfere with your policies. Don't forget to re-check BIOS settings after "
+"you configured everything else."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):132
+msgid "Setting USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):135
+msgid ""
+"Please check that the <c>acpi</c> USE flag is set in <path>/etc/make.conf</"
+"path>. Other USE flags that might be interesting for your system are <c>apm</"
+"c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>, <c>pmu</c>. See <path>/"
+"usr/portage/profiles/use*.desc</path> for details. If you forgot to set one "
+"of these flags, you can recompile affected packages using the <c>--newuse</"
+"c> flag in <c>emerge</c>, see <c>man emerge</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):147
+msgid "Configuring The Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):150
+msgid ""
+"ACPI (Advanced Configuration and Power Interface) support in the kernel is "
+"still work in progress. Using a recent kernel will make sure you'll get the "
+"most out of it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):156
+msgid ""
+"There are different kernel sources in Portage. I'd recommend using <c>gentoo-"
+"sources</c> or <c>tuxonice-sources</c>. The latter contains patches for "
+"TuxOnIce, see the chapter about <uri link=\"#doc_chap7\">sleep states</uri> "
+"for more details. When configuring the kernel, activate at least these "
+"options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):163
+msgid "Minimum kernel setup for Power Management (Kernel 2.6)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):163
+#, no-wrap
+msgid ""
+"\n"
+"Power management and ACPI options ---&gt;\n"
+"[*] Power Management support\n"
+"  [ ] Software Suspend\n"
+"\n"
+"  ACPI( Advanced Configuration and Power Interface ) Support ---&gt;\n"
+"    [ ]   Deprecated /proc/acpi/ files\n"
+"    [*]   AC Adapter\n"
+"    [*]   Battery\n"
+"    &lt;M&gt;   Button\n"
+"    &lt;M&gt;   Video\n"
+"    [ ]   Generic Hotkey\n"
+"    &lt;M&gt;   Fan\n"
+"    &lt;M&gt;   Processor\n"
+"    &lt;M&gt;     Thermal Zone\n"
+"    &lt; &gt;   ASUS/Medion Laptop Extras\n"
+"    &lt; &gt;   IBM ThinkPad Laptop Extras\n"
+"    &lt; &gt;   Toshiba Laptop Extras\n"
+"    (0)   Disable ACPI for systems before Jan 1st this year\n"
+"    [ ]   Debug Statements\n"
+"    [*]   Power Management Timer Support\n"
+"    &lt; &gt;   ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)\n"
+"\n"
+"  CPU Frequency Scaling ---&gt;\n"
+"    [*] CPU Frequency scaling\n"
+"    [ ]   Enable CPUfreq debugging\n"
+"    &lt; &gt;   CPU frequency translation statistics\n"
+"    [ ]     CPU frequency translation statistics details\n"
+"          Default CPUFreq governor (userspace)\n"
+"    &lt;*&gt;   'performance' governor\n"
+"    &lt;*&gt;   'powersave' governor\n"
+"    &lt;*&gt;   'ondemand' cpufreq policy governor\n"
+"    &lt;*&gt;   'conservative' cpufreq governor\n"
+"    &lt;*&gt;   CPU frequency table helpers\n"
+"    &lt;M&gt; ACPI Processor P-States driver\n"
+"    &lt;*&gt; <i>CPUFreq driver for your processor</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):201
+msgid ""
+"Decide yourself whether you want to enable Software Suspend, and Sleep "
+"States (see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba "
+"laptop, enable the appropriate section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):207
+msgid ""
+"The kernel has to know how to enable CPU frequency scaling on your "
+"processor. As each type of CPU has a different interface, you've got to "
+"choose the right driver for your processor. Be careful here - enabling "
+"<c>Intel Pentium 4 clock modulation</c> on a Pentium M system will lead to "
+"strange results for example. Consult the kernel documentation if you're "
+"unsure which one to take."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):215
+msgid ""
+"Compile your kernel, make sure the right modules get loaded at startup and "
+"boot into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</"
+"c> to get the acpi daemon. This one informs you about events like switching "
+"from AC to battery or closing the lid. Make sure the modules are loaded if "
+"you didn't compile them into the kernel and start acpid by executing <c>/etc/"
+"init.d/acpid start</c>. Run <c>rc-update add acpid default</c> to load it on "
+"startup. You'll soon see how to use it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):225
+msgid "Installing acpid"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):225
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge sys-power/acpid</i>\n"
+"# <i>/etc/init.d/acpid start</i>\n"
+"# <i>rc-update add acpid default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):234
+msgid "Creating A \"battery\" Runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):237
+msgid ""
+"The default policy will be to enable Power Management only when needed - "
+"running on batteries. To make the switch between AC and battery convenient, "
+"create a runlevel <c>battery</c> that holds all the scripts starting and "
+"stopping Power Management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):244
+msgid ""
+"You can safely skip this section if you don't like the idea of having "
+"another runlevel. However, skipping this step will make the rest a bit "
+"trickier to set up. The next sections assume a runlevel <c>battery</c> "
+"exists."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):250
+msgid "Creating a battery runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):250
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/runlevels</i>\n"
+"# <i>cp -a default battery</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):255
+msgid ""
+"Finished. Your new runlevel <c>battery</c> contains everything like "
+"<c>default</c>, but there is no automatic switch between both yet. Time to "
+"change it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):264
+msgid "Reacting On ACPI Events"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):267
+msgid ""
+"Typical ACPI events are closing the lid, changing the power source or "
+"pressing the sleep button. An important event is changing the power source, "
+"which should cause a runlevel switch. A small script will take care of it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):273
+msgid ""
+"First you need a script which changes the runlevel to <c>default</c> "
+"respectively <c>battery</c> depending on the power source. The script uses "
+"the <c>on_ac_power</c> command from <c>sys-power/pm-utils</c> - make sure "
+"the package is installed on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):280
+msgid "Installing pm-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):280
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge pm-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):284
+msgid ""
+"You are now able to determine the power source by executing <c>on_ac_power "
+"&amp;&amp; echo AC available || echo Running on batteries</c> in a shell. "
+"The script below is responsible for changing runlevels. Save it as <path>/"
+"etc/acpi/actions/pmg_switch_runlevel.sh</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):291
+msgid "/etc/acpi/actions/pmg_switch_runlevel.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):291
+#, no-wrap
+msgid ""
+"\n"
+"#!/bin/bash\n"
+"\n"
+"<comment># BEGIN configuration</comment>\n"
+"RUNLEVEL_AC=\"default\"\n"
+"RUNLEVEL_BATTERY=\"battery\"\n"
+"<comment># END configuration</comment>\n"
+"\n"
+"\n"
+"if [ ! -d \"/etc/runlevels/${RUNLEVEL_AC}\" ]\n"
+"then\n"
+"    logger \"${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting.\"\n"
+"    exit 1\n"
+"fi\n"
+"\n"
+"if [ ! -d \"/etc/runlevels/${RUNLEVEL_BATTERY}\" ]\n"
+"then\n"
+"    logger \"${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting.\"\n"
+"    exit 1\n"
+"fi\n"
+"\n"
+"if on_ac_power\n"
+"then\n"
+"    if [[ \"$(&lt;/var/lib/init.d/softlevel)\" != \"${RUNLEVEL_AC}\" ]]\n"
+"    then\n"
+"        logger \"Switching to ${RUNLEVEL_AC} runlevel\"\n"
+"         /sbin/rc ${RUNLEVEL_AC}\n"
+"    fi\n"
+"elif [[ \"$(&lt;/var/lib/init.d/softlevel)\" != \"${RUNLEVEL_BATTERY}\" ]]\n"
+"then\n"
+"    logger \"Switching to ${RUNLEVEL_BATTERY} runlevel\"\n"
+"    /sbin/rc ${RUNLEVEL_BATTERY}\n"
+"fi\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):326
+msgid ""
+"Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> "
+"to make the script executable. The last thing that needs to be done is "
+"calling the script whenever the power source changes. That's done by "
+"catching ACPI events with the help of <c>acpid</c>. First you need to know "
+"which events are generated when the power source changes. The events are "
+"called <c>ac_adapter</c> and <c>battery</c> on most laptops, but it might be "
+"different on yours."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):336
+msgid "Determining ACPI events for changing the power source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):336
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tail -f /var/log/messages | grep \"ACPI event\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):340
+msgid ""
+"Run the command above and pull the power cable. You should see something "
+"like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):345
+msgid "Sample output for power source changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):345
+#, no-wrap
+msgid ""
+"\n"
+"[Tue Sep 20 17:39:06 2005] ACPI event \"ac_adapter AC 00000080 00000000\"\n"
+"[Tue Sep 20 17:39:06 2005] ACPI event \"battery BAT0 00000080 00000001\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):350
+msgid ""
+"The interesting part is the quoted string after <c>ACPI event</c>. It will "
+"be matched by the event line in the files you are going to create below. "
+"Don't worry if your system generates multiple events or always the same. As "
+"long as any event is generated, runlevel changing will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):357
+msgid "/etc/acpi/events/pmg_ac_adapter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):357
+#, no-wrap
+msgid ""
+"\n"
+"<comment># replace \"ac_adapter\" below with the event generated on your laptop</comment>\n"
+"<comment># For example, ac_adapter.* will match ac_adapter AC 00000080 00000000</comment>\n"
+"event=ac_adapter.*\n"
+"action=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):364
+msgid "/etc/acpi/events/pmg_battery"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):364
+#, no-wrap
+msgid ""
+"\n"
+"<comment># replace \"battery\" below with the event generated on your laptop</comment>\n"
+"<comment># For example, battery.* will match battery BAT0 00000080 00000001</comment>\n"
+"event=battery.*\n"
+"action=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):371
+msgid "Finally acpid has to be restarted to recognize the changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):375
+msgid "Finishing runlevel switching with acpid"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):375
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/acpid restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):379
+msgid ""
+"Give it a try: Plug AC in and out and watch syslog for the \"Switching to AC "
+"mode\" or \"Switching to battery mode\" messages. See the <uri link="
+"\"#doc_chap8\">Troubleshooting section</uri> if the script is not able to "
+"detect the power source correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):386
+msgid ""
+"Due to the nature of the event mechanism, your laptop will boot into "
+"runlevel <c>default</c> regardless of the AC/battery state. This is fine "
+"when running from AC, but we'd like to boot into the battery runlevel "
+"otherwise. One solution would be to add another entry to the boot loader "
+"with the parameter <c>softlevel=battery</c>, but it's likely to forget "
+"choosing it. A better way is faking an ACPI event in the end of the boot "
+"process and letting <path>pmg_switch_runlevel.sh</path> script decide "
+"whether a runlevel change is necessary. Open <path>/etc/conf.d/local.start</"
+"path> in your favourite editor and add these lines:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):398
+msgid "Runlevel adjustment at boot time by editing local.start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):398
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Fake acpi event to switch runlevel if running on batteries</comment>\n"
+"/etc/acpi/actions/pmg_switch_runlevel.sh \"battery/battery\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):403
+msgid ""
+"Prepared like this you can activate Power Management policies for individual "
+"devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):413
+msgid "CPU Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):417
+msgid ""
+"Mobile processors can operate at different frequencies. Some allow changing "
+"voltage as well. Most of the time your CPU doesn't need to run at full speed "
+"and scaling it down will save much energy - often without any performance "
+"decrease."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):427
+msgid "Some Technical Terms"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):430
+msgid ""
+"CPU frequency scaling brings up some technical terms that might be unknown "
+"to you. Here's a quick introduction."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):435
+msgid ""
+"First of all, the kernel has to be able to change the processor's frequency. "
+"The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU. "
+"Thus it's important to choose the right one in your kernel. You should "
+"already have done it above. Once the kernel knows how to change frequencies, "
+"it has to know which frequency it should set. This is done according to the "
+"<b>policy</b> which consists of a <b>CPUfreq policy</b> and a <b>governor</"
+"b>. A CPUfreq policy are just two numbers which define a range the frequency "
+"has to stay between - minimal and maximal frequency. The governor now "
+"decides which of the available frequencies in between minimal and maximal "
+"frequency to choose. For example, the <b>powersave governor</b> always "
+"chooses the lowest frequency available, the <b>performance governor</b> the "
+"highest one. The <b>userspace governor</b> makes no decision but chooses "
+"whatever the user (or a program in userspace) wants - which means it reads "
+"the frequency from <path>/sys/devices/system/cpu/cpu0/cpufreq/"
+"scaling_setspeed</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):452
+msgid ""
+"This doesn't sound like dynamic frequency changes yet and in fact it isn't. "
+"Dynamics however can be accomplished with various approaches. For example, "
+"the <b>ondemand governor</b> makes its decisions depending on the current "
+"CPU load. The same is done by various userland tools like <c>cpudyn</c>, "
+"<c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to "
+"enable or disable dynamic frequency changes depending on power source."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):464
+msgid "Setting The Frequency"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):467
+msgid ""
+"Decreasing CPU speed and voltage has two advantages: On the one hand less "
+"energy is consumed, on the other hand there is thermal improvement as your "
+"system doesn't get as hot as running on full speed. The main disadvantage is "
+"obviously the loss of performance. Decreasing processor speed is a trade off "
+"between performance loss and energy saving."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):475
+msgid ""
+"Not every laptop supports frequency scaling. If unsure, have a look at the "
+"list of supported processors in the <uri link="
+"\"#doc_chap8\">Troubleshooting</uri> section to verify yours is supported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):481
+msgid ""
+"It's time to test whether CPU frequency changing works. Let's install "
+"another tool: <c>sys-power/cpufrequtils</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):486
+msgid "Checking CPU frequency"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):486
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge cpufrequtils</i>\n"
+"# <i>cpufreq-info</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):491
+msgid "Here is an example output:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):495
+msgid "Sample output from cpufreq-info"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):495
+#, no-wrap
+msgid ""
+"\n"
+"cpufrequtils 0.3: cpufreq-info (C) Dominik Brodowski 2004\n"
+"Report errors and bugs to linux@brodo.de, please.\n"
+"analyzing CPU 0:\n"
+"  driver: centrino\n"
+"  CPUs which need to switch frequency at the same time: 0\n"
+"  hardware limits: 600 MHz - 1.40 GHz\n"
+"  available frequency steps: 600 MHz, 800 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz\n"
+"  available cpufreq governors: conservative, ondemand, powersave, userspace, performance\n"
+"  current policy: frequency should be within 924 MHz and 1.40 GHz.\n"
+"    The governor \"performance\" may decide which speed to use\n"
+"    within this range.\n"
+"  current CPU frequency is 1.40 GHz.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):510
+msgid ""
+"Now play around with <c>cpufreq-set</c> to make sure frequency switching "
+"works. Run <c>cpufreq-set -g ondemand</c> for example to activate the "
+"ondemand governor and verify the change with <c>cpufreq-info</c>. If it "
+"doesn't work as expected, you might find help in the <uri link="
+"\"#doc_chap8\">Troubleshooting section</uri> in the end of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):518
+msgid ""
+"<c>cpufrequtils</c> can operate in an automatic mode (when you use the "
+"<b>ondemand</b> governor), you can also switch to the <b>userspace</b> "
+"governor if you want to manually set a specific speed. You can also "
+"statically set your CPU to its highest or lowest frequency by using the "
+"<b>performance</b> and <b>powersave</b> governors, respectively."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):526
+msgid "Changing CPU speeds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):526
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Set the highest available frequency)</comment>\n"
+"# <i>cpufreq-set -g performance</i>\n"
+"<comment>(Set the lowest available frequency)</comment>\n"
+"# <i>cpufreq-set -g powersave</i>\n"
+"<comment>(Set a specific frequency)</comment>\n"
+"# <i>cpufreq-set -g userspace</i>\n"
+"# <i>cpufreq-set -f 2.00ghz</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):539
+msgid "Other CPU Speed Utilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):542
+msgid ""
+"While <c>cpufrequtils</c> may be the best all-around program, there are some "
+"other choices available in Portage. The following table gives a quick "
+"overview of available CPU speed utilities. It's roughly separated in three "
+"categories <b>kernel</b> for approaches that only need kernel support, "
+"<b>daemon</b> for programs that run in the background and <b>graphical</b> "
+"for programs that provide a GUI for easy configuration and changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):553
+msgid "Name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):554
+msgid "Category"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):555
+msgid "Switch decision"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):556
+msgid "Kernel governors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):557
+msgid "Further governors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):558
+msgid "Comments"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):561
+msgid "'ondemand' governor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):562
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):576
+msgid "Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):563
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):577
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):592
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):618
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):642
+msgid "CPU load"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):564
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):565
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):578
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):579
+msgid "N.A."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):566
+msgid ""
+"Chooses maximal frequency on CPU load and slowly steps down when the CPU is "
+"idle. Further tuning through files in <path>/sys/devices/system/cpu/cpu0/"
+"cpufreq/ondemand/</path>. Still requires userland tools (programs, scripts) "
+"if governor switching or similar is desired."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):575
+msgid "'conservative' governor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):580
+msgid ""
+"Unlike the ondemand governor, conversative doesn't jump to maximum frequency "
+"when CPU load is high, but increases the frequency step by step. Further "
+"tuning through files in <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/"
+"</path>. Still requires userland tools (programs, scripts) if governor "
+"switching or similar is desired."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):590
+msgid "http://mnm.uib.es/~gallir/cpudyn/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):590
+msgid "cpudyn"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):591
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):602
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):617
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):630
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):641
+msgid "Daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):593
+msgid "Performance, powersave"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):594
+msgid "Dynamic"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):595
+msgid ""
+"Also supports disk standby - notice however that <e>laptop mode</e> in most "
+"cases will do a better job."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):601
+msgid "http://sourceforge.net/projects/cpufreqd/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):601
+msgid "cpufreqd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):603
+msgid "Battery state, CPU load, temperature, running programs and more"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):604
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):666
+msgid "All available"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):605
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):619
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):632
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):643
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):654
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):655
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):656
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):667
+msgid "None"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):606
+msgid ""
+"Sophisticated (but somewhat complicated) setup. Extendible through plugins "
+"like sensor monitoring (lm_sensors) or coordinating some NVidia based "
+"graphics card memory and core. Cpufreqd is SMP aware and can optionally be "
+"controlled manually at runtime."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):615
+msgid "http://www.deater.net/john/powernowd.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):615
+msgid "powernowd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):620
+msgid "Passive, sine, aggressive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):621
+msgid "Supports SMP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):628
+msgid "http://projects.simpledesigns.com.pl/project/ncpufreqd/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):628
+msgid "ncpufreqd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):631
+msgid "Temperature"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):633
+msgid "Powersave, performance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):634
+msgid ""
+"Toggles the used governor between performance and powersave depending on "
+"system temperature. Very useful on laptops with notorious heat problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):640
+msgid "http://www.goop.org/~jeremy/speedfreq/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):640
+msgid "speedfreq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):644
+msgid "Dynamic, powersave, performance, fixed speed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):645
+msgid ""
+"Easy to configure with a nice client/server interface. Requires a 2.6 "
+"kernel. Unmaintained, broken and thus removed from Portage. Please switch to "
+"cpufreqd if you're still using it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):652
+msgid "http://cpuspeedy.sourceforge.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):652
+msgid "gtk-cpuspeedy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):653
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):664
+msgid "Graphical"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):657
+msgid ""
+"Gnome application, a graphical tool to set CPU frequency manually. It does "
+"not offer any automation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):663
+msgid "klaptopdaemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):665
+msgid "Battery state"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):668
+msgid "KDE only, 'ondemand' governor required for dynamic frequency scaling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):674
+msgid ""
+"While adjusting the frequency to the current load looks simple at a first "
+"glance, it's not such a trivial task. A bad algorithm can cause switching "
+"between two frequencies all the time or wasting energy when setting "
+"frequency to an unnecessary high level."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):681
+msgid "Which one to choose? If you have no idea about it, try <c>cpufreqd</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):685
+msgid "Installing cpufreqd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):685
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge cpufreqd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):689
+msgid ""
+"<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</"
+"path>. The default one that ships with cpufreqd may look a bit confusing. I "
+"recommend replacing it with the one from former Gentoo developer Henrik Brix "
+"Andersen (see below). Please notice that you need cpufreqd-2.0.0 or later. "
+"Earlier versions have a different syntax for the config file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):697
+msgid "/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):697
+#, no-wrap
+msgid ""
+"\n"
+"[General]\n"
+"pidfile=/var/run/cpufreqd.pid\n"
+"poll_interval=3\n"
+"enable_plugins=acpi_ac, acpi_battery\n"
+"enable_remote=1\n"
+"remote_group=wheel\n"
+"verbosity=5\n"
+"[/General]\n"
+"\n"
+"[Profile]\n"
+"name=ondemand\n"
+"minfreq=0%\n"
+"maxfreq=100%\n"
+"policy=ondemand\n"
+"[/Profile]\n"
+"\n"
+"[Profile]\n"
+"name=conservative\n"
+"minfreq=0%\n"
+"maxfreq=100%\n"
+"policy=conservative\n"
+"[/Profile]\n"
+"\n"
+"[Profile]\n"
+"name=powersave\n"
+"minfreq=0%\n"
+"maxfreq=100%\n"
+"policy=powersave\n"
+"[/Profile]\n"
+"\n"
+"[Profile]\n"
+"name=performance\n"
+"minfreq=0%\n"
+"maxfreq=100%\n"
+"policy=performance\n"
+"[/Profile]\n"
+"\n"
+"[Rule]\n"
+"name=battery\n"
+"ac=off\n"
+"profile=conservative\n"
+"[/Rule]\n"
+"\n"
+"[Rule]\n"
+"name=battery_low\n"
+"ac=off\n"
+"battery_interval=0-10\n"
+"profile=powersave\n"
+"[/Rule]\n"
+"\n"
+"[Rule]\n"
+"name=ac\n"
+"ac=on\n"
+"profile=ondemand\n"
+"[/Rule]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):755
+msgid ""
+"Now you can start the cpufreqd daemon. Add it to the <c>default</c> and "
+"<c>battery</c> runlevel as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):760
+msgid "Starting cpufreqd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):760
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add cpufreqd default battery</i>\n"
+"# <i>/etc/init.d/cpufreqd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):765
+msgid ""
+"Sometimes it can be desirable to select another policy than the daemon "
+"chooses, for example when battery power is low, but you know that AC will be "
+"available soon. In that case you can turn on cpufreqd's manual mode with "
+"<c>cpufreqd-set manual</c> and select one of your configured policies (as "
+"listed by <c>cpufreqd-get</c>). You can leave manual mode by executing "
+"<c>cpufreqd-set dynamic</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):774
+msgid ""
+"Do not run more than one of the above programs at the same time. It may "
+"cause confusion like switching between two frequencies all the time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):782
+msgid "Verifying the result"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):785
+msgid ""
+"The last thing to check is that your new policies do a good job. An easy way "
+"to do so is monitoring CPU speed while working with your laptop:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):790
+msgid "Monitoring CPU speed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):790
+#, no-wrap
+msgid ""
+"\n"
+"# <i>watch grep \\\"cpu MHz\\\" /proc/cpuinfo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):794
+msgid ""
+"If <path>/proc/cpuinfo</path> doesn't get updated (see <uri link="
+"\"#doc_chap8\">Troubleshooting</uri>), monitor the CPU frequency with <c>sys-"
+"apps/x86info</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):800
+msgid "Alternative CPU speed monitoring"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):800
+#, no-wrap
+msgid ""
+"\n"
+"# <i>watch x86info -mhz</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):804
+msgid ""
+"Depending on your setup, CPU speed should increase on heavy load, decrease "
+"on no activity or just stay at the same level. When using <c>cpufreqd</c> "
+"and verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get "
+"additional information about what's happening reported to <c>syslog</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):816
+msgid "LCD Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):820
+msgid ""
+"As you can see in <uri link=\"#doc_chap1_fig1\">figure 1.1</uri>, the LCD "
+"display consumes the biggest part of energy (might not be the case for non-"
+"mobile CPU's). Thus it's quite important not only to shut the display off "
+"when not needed, but also to reduce it's backlight if possible. Most laptops "
+"offer the possibility to control the backlight dimming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):831
+msgid "Standby settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):834
+msgid ""
+"The first thing to check is the standby/suspend/off timings of the display. "
+"As this depends heavily on your windowmanager, I'll let you figure it out "
+"yourself. Just two common places: Blanking the terminal can be done with "
+"<c>setterm -blank &lt;number-of-minutesM&gt;</c>, <c>setterm -powersave on</"
+"c> and <c>setterm -powerdown &lt;number-of-minutesM&gt;</c>. For X.org, "
+"modify <path>/etc/X11/xorg.conf</path> similar to this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):843
+msgid "LCD suspend settings in X.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):843
+#, no-wrap
+msgid ""
+"\n"
+"Section \"ServerFlags\"\n"
+"  Option  \"blank time\"  \"5\"  <comment># Blank the screen after 5 minutes (Fake)</comment>\n"
+"  Option  \"standby time\"  \"10\"  <comment># Turn off screen after 10 minutes (DPMS)</comment>\n"
+"  Option  \"suspend time\"  \"20\"  <comment># Full suspend after 20 minutes</comment>\n"
+"  Option  \"off time\"  \"30\"  <comment># Turn off after half an hour</comment>\n"
+"  [...]\n"
+"EndSection\n"
+"\n"
+"[...]\n"
+"\n"
+"Section \"Monitor\"\n"
+"  Identifier  [...]\n"
+"  Option  \"DPMS\"\n"
+"  [...]\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):864
+msgid "Backlight dimming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):867
+msgid ""
+"Probably more important is the backlight dimming. If you have access to the "
+"dimming settings via a tool, write a small script that dims the backlight in "
+"battery mode and place it in your <c>battery</c> runlevel. The following "
+"script should work on most IBM Thinkpads and Toshiba laptops. You've got to "
+"enable the appropriate option in your kernel (IBM Thinkpads only). For "
+"Toshiba laptops, install <c>sys-power/acpitool</c> and skip configuration of "
+"<c>thinkpad_acpi</c> (formerly called <c>ibm_acpi</c>) as described below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):877
+msgid ""
+"Support for setting brightness is marked experimental in thinkpad_acpi. It "
+"accesses hardware directly and may cause severe harm to your system. Please "
+"read the <uri link=\"http://ibm-acpi.sourceforge.net/\">thinkpad_acpi "
+"website</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):884
+msgid ""
+"To be able to set the brightness level, the thinkpad_acpi module has to be "
+"loaded with the experimental parameter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):889
+msgid "automatically loading the thinkpad_acpi module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):889
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Please read the warnings above before doing this!)</comment>\n"
+"# <i>echo \"options thinkpad_acpi experimental=1\" &gt;&gt; /etc/modprobe.d/thinkpad_acpi</i>\n"
+"# <i>update-modules</i>\n"
+"# <i>echo thinkpad_acpi &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+"# <i>modprobe thinkpad_acpi</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):897
+msgid ""
+"This should work without error messages and a file <path>/proc/acpi/ibm/"
+"brightness</path> should be created after loading the module. An init script "
+"will take care of choosing the brightness according to the power source."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):904
+msgid "/etc/conf.d/lcd-brightness"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):904
+#, no-wrap
+msgid ""
+"\n"
+"<comment># See /proc/acpi/ibm/brightness for available values</comment>\n"
+"<comment># Please read /usr/src/linux/Documentation/thinkpad-acpi.txt</comment>\n"
+"\n"
+"<comment># brightness level in ac mode. Default is 7.</comment>\n"
+"BRIGHTNESS_AC=7\n"
+"\n"
+"<comment># brightness level in battery mode. Default is 4.</comment>\n"
+"BRIGHTNESS_BATTERY=4\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):915
+msgid "/etc/init.d/lcd-brightness"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):915
+#, no-wrap
+msgid ""
+"\n"
+"#!/sbin/runscript\n"
+"\n"
+"set_brightness() {\n"
+"    if on_ac_power\n"
+"    then\n"
+"        LEVEL=${BRIGHTNESS_AC:-7}\n"
+"    else\n"
+"        LEVEL=${BRIGHTNESS_BATTERY:-4}\n"
+"    fi\n"
+"\n"
+"    if [ -f /proc/acpi/ibm/brightness ]\n"
+"    then\n"
+"        ebegin \"Setting LCD brightness\"\n"
+"        echo \"level ${LEVEL}\" &gt; /proc/acpi/ibm/brightness\n"
+"        eend $?\n"
+"    elif [[ -e /usr/bin/acpitool &amp;&amp; -n $(acpitool -T | grep \"LCD brightness\") ]]\n"
+"    then\n"
+"        ebegin \"Setting LCD brightness\"\n"
+"        acpitool -l $LEVEL &gt;/dev/null || ewarn \"Unable to set lcd brightness\"\n"
+"        eend $?\n"
+"    else\n"
+"        ewarn \"Setting LCD brightness is not supported.\"\n"
+"        ewarn \"For IBM Thinkpads, check that thinkpad_acpi is loaded into the kernel\"\n"
+"        ewarn \"For Toshiba laptops, you've got to install sys-power/acpitool\"\n"
+"    fi\n"
+"}\n"
+"\n"
+"start() {\n"
+"    set_brightness\n"
+"}\n"
+"\n"
+"stop () {\n"
+"    set_brightness\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):952
+msgid ""
+"When done, make sure brightness is adjusted automatically by adding it to "
+"the battery runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):957
+msgid "Enabling automatic brightness adjustment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):957
+#, no-wrap
+msgid ""
+"\n"
+"# <i>chmod +x /etc/init.d/lcd-brightness</i>\n"
+"# <i>rc-update add lcd-brightness battery</i>\n"
+"# <i>rc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):968
+msgid "Disk Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):972
+msgid ""
+"Hard disks consume less energy in sleep mode. Therefore it makes sense to "
+"activate power saving features whenever the hard disk is not used for a "
+"certain amount of time. I'll show you two alternative possibilities to do "
+"it. First, laptop-mode will save most energy due to several measures which "
+"prevent or at least delay write accesses. The drawback is that due to the "
+"delayed write accesses a power outage or kernel crash will be more dangerous "
+"for data loss. If you don't like this, you have to make sure that there are "
+"no processes which write to your hard disk frequently. Afterwards you can "
+"enable power saving features of your hard disk with <c>hdparm</c> as the "
+"second alternative."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):987
+msgid "Increasing idle time - laptop-mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):990
+msgid ""
+"Recent 2.6 kernels include the so-called <c>laptop-mode</c>. When activated, "
+"dirty buffers are written to disk on read calls or after 10 minutes (instead "
+"of 30 seconds). This minimizes the time the hard disk needs to be spun up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):996
+msgid "Automated start of laptop-mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):996
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge laptop-mode-tools</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1000
+msgid ""
+"<c>laptop-mode-tools</c> has its configuration file in <path>/etc/laptop-"
+"mode/laptop-mode.conf</path>. Adjust it the way you like it, it's well "
+"commented. Run <c>rc-update add laptop_mode battery</c> to start it "
+"automatically."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1007
+msgid ""
+"Recent versions (1.11 and later) of laptop-mode-tools include a new tool "
+"<c>lm-profiler</c>. It will monitor your system's disk usage and running "
+"network services and suggests to disable unneeded ones. You can either "
+"disable them through laptop-mode-tools builtin runlevel support (which will "
+"be reverted by Gentoo's <c>/sbin/rc</c>) or use your <c>default</c>/"
+"<c>battery</c> runlevels (recommended)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1016
+msgid "Sample output from running lm-profiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1016
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lm-profiler</i>\n"
+"Profiling session started.\n"
+"Time remaining: 600 seconds\n"
+"[4296896.602000] amarokapp\n"
+"Time remaining: 599 seconds\n"
+"[4296897.714000] sort\n"
+"[4296897.970000] mv\n"
+"Time remaining: 598 seconds\n"
+"Time remaining: 597 seconds\n"
+"[4296900.482000] reiserfs/0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1029
+msgid ""
+"After profiling your system for ten minutes, lm-profiler will present a list "
+"of services which might have caused disk accesses during that time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1034
+msgid "lm-profiler suggests to disable some services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1034
+#, no-wrap
+msgid ""
+"\n"
+"Program:     \"atd\"\n"
+"Reason:      standard recommendation (program may not be running)\n"
+"Init script: /etc/init.d/atd (GUESSED)\n"
+"\n"
+"Do you want to disable this service in battery mode? [y/N]: <i>n</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1042
+msgid ""
+"To disable atd as suggested in the example above, you would run <c>rc-update "
+"del atd battery</c>. Be careful not to disable services that are needed for "
+"your system to run properly - <c>lm-profiler</c> is likely to generate some "
+"false positives. Do not disable a service if you are unsure whether it's "
+"needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1053
+msgid "Limiting Write Accesses"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1056
+msgid ""
+"If you don't want to use laptop-mode, you must take special care to disable "
+"services that write to your disk frequently - <c>syslogd</c> is a good "
+"candidate, for example. You probably don't want to shut it down completely, "
+"but it's possible to modify the config file so that \"unnecessary\" things "
+"don't get logged and thus don't create disk traffic. <c>Cups</c> writes to "
+"disk periodically, so consider shutting it down and only enable it manually "
+"when needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1066
+msgid "Disabling cups in battery mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1066
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update del cupsd battery</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1070
+msgid ""
+"You can also use <c>lm-profiler</c> from laptop-mode-tools (see above) to "
+"find services to disable. Once you eliminated all of them, go on with "
+"configuring hdparm."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1079
+msgid "hdparm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1082
+msgid ""
+"The second possibility is using <c>hdparm</c>. Skip this if you are using "
+"laptop-mode. Otherwise, edit <path>/etc/conf.d/hdparm</path> and add the "
+"following values to your drive entries. This example assumes your hard drive "
+"is called <b>hda</b>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1089
+msgid "Using /etc/conf.d/hdparm for disk standby"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1089
+#, no-wrap
+msgid ""
+"\n"
+"hda_args=\"-q -S12\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1093
+msgid ""
+"This will activate power management for your hard drive. If you ever want to "
+"deactivate power management, you can edit <path>/etc/conf.d/hdparm</path> "
+"and change the values to <c>-q -S0</c>, or just run <c>hdparm -q -S0 /dev/"
+"hda</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1099
+msgid ""
+"See <c>man hdparm</c> for the options. Though you can always start "
+"<c>hdparm</c> manually when you are on battery power by running <c>/etc/init."
+"d/hdparm start</c>, it's much easier to automate its startup and shutdown. "
+"To do so, add <c>hdparm</c> to the battery runlevel so that it will "
+"automatically enable power management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1107
+msgid "Automate disk standby settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1107
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add hdparm battery</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):1111
+msgid ""
+"Be careful with sleep/spin down settings of your hard drive. Setting it to "
+"small values might wear out your drive and lose warranty."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1119
+msgid "Other tricks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1122
+msgid ""
+"Another possibility is to deactivate swap in battery mode. Before writing a "
+"swapon/swapoff switcher, make sure there is enough RAM and swap isn't used "
+"heavily, otherwise you'll be in big problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1128
+msgid ""
+"If you don't want to use laptop-mode, it's still possible to minimize disk "
+"access by mounting certain directories as <c>tmpfs</c> - write accesses are "
+"not stored on a disk, but in main memory and get lost with unmounting. Often "
+"it's useful to mount <path>/tmp</path> like this - you don't have to pay "
+"special attention as it gets cleared on every reboot regardless whether it "
+"was mounted on disk or in RAM. Just make sure you have enough RAM and no "
+"program (like a download client or compress utility) needs extraordinary "
+"much space in <path>/tmp</path>. To activate this, enable tmpfs support in "
+"your kernel and add a line to <path>/etc/fstab</path> like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1140
+msgid "Editing /etc/fstab to make /tmp even more volatile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1140
+#, no-wrap
+msgid ""
+"\n"
+"none  /tmp  tmpfs  size=32m  0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1144
+msgid ""
+"Pay attention to the size parameter and modify it for your system. If you're "
+"unsure, don't try this at all, it can become a performance bottleneck "
+"easily. In case you want to mount <path>/var/log</path> like this, make sure "
+"to merge the log files to disk before unmounting. They are essential. Don't "
+"attempt to mount <path>/var/tmp</path> like this. Portage uses it for "
+"compiling..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1157
+msgid "Power Management For Other Devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1159
+msgid "Graphics Cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1162
+msgid ""
+"In case you own an ATI graphics card supporting PowerPlay (dynamic clock "
+"scaling for the graphics processing unit GPU), you can activate this feature "
+"in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the "
+"<c>DynamicClocks</c> option in the Device section. Please notice that this "
+"feature will lead to crashes on some systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1170
+msgid "Enabling ATI PowerPlay support in X.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1170
+#, no-wrap
+msgid ""
+"\n"
+"Section \"Device\"\n"
+"[...]\n"
+"Option      \"DynamicClocks\" \"on\"\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1180
+msgid "Wireless Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1183
+msgid ""
+"Wireless LAN cards consume quite a bit of energy. Put them in Power "
+"Management mode just like your hard drives."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1188
+msgid ""
+"This script assumes your wireless interface is called <c>wlan0</c>; replace "
+"this with the actual name of your interface."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1193
+msgid ""
+"Add the following option to <path>/etc/conf.d/net</path> to automatically "
+"enable power management for your wireless card:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1198
+msgid "Automated WLAN Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1198
+#, no-wrap
+msgid ""
+"\n"
+"iwconfig_wlan0=\"power on\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1202
+msgid ""
+"See <c>man iwconfig</c> for details and more options like the period between "
+"wakeups or timeout settings. If your driver and access point support "
+"changing the beacon time, this is a good starting point to save even more "
+"energy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1211
+msgid "USB Power Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1214
+msgid ""
+"There are two problems with USB devices regarding energy consumption: First, "
+"devices like USB mice, digital cameras or USB sticks consume energy while "
+"plugged in. You cannot avoid this (nevertheless remove them in case they're "
+"not needed). Second, when there are USB devices plugged in, the USB host "
+"controller periodically accesses the bus which in turn prevents the CPU from "
+"going into sleep mode. The kernel offers an experimental option to enable "
+"suspension of USB devices through driver calls or one of the <path>power/"
+"state</path> files in <path>/sys</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1225
+msgid "Enabling USB suspend support in the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1225
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers\n"
+"  USB support\n"
+"    [*]   Support for Host-side USB\n"
+"      [*]   USB suspend/resume (EXPERIMENTAL)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1237
+msgid "Sleep States: sleep, standby, and suspend to disk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1241
+msgid "ACPI defines different sleep states. The more important ones are"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1246
+msgid "S1 aka Standby"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1247
+msgid "S3 aka Suspend to RAM aka Sleep"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1248
+msgid "S4 aka Suspend to Disk aka Hibernate"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1251
+msgid ""
+"They can be called whenever the system is not in use, but a shutdown is not "
+"wanted due to the long boot time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1259
+msgid "Sleep (S3)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1262
+msgid ""
+"The ACPI support for these sleep states is marked experimental for good "
+"reason. APM sleep states seem to be more stable, however you can't use APM "
+"and ACPI together."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1268
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1362
+msgid "Kernel configuration for the various suspend types"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1268
+#, no-wrap
+msgid ""
+"\n"
+"  Power Management Options ---&gt;\n"
+"    [*]  Power Management support\n"
+"    [*]  Suspend to RAM and standby \n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1274
+msgid ""
+"Once your kernel is properly configured, you can use the <c>hibernate-"
+"script</c> to activate suspend or sleep mode. Let's install that first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1280
+msgid "Installing the hibernate-script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1280
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge hibernate-script</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1284
+msgid ""
+"Some configuration has to be done in <path>/etc/hibernate</path>. The "
+"default package introduces a few configuration files for each sleep state. "
+"Options that are common to all suspend methods are placed in <path>common."
+"conf</path>; make sure this file is properly set up for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1291
+msgid ""
+"To configure sleep, edit <path>sysfs-ram.conf</path> in <path>/etc/"
+"hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup correctly, "
+"but if you need to make further changes to this particular sleep state (or "
+"any other sleep state) you should add them to <path>/etc/hibernate/hibernate."
+"conf</path>. The comments and option names will guide you. If you use nfs or "
+"samba shares over the network, make sure to shutdown the appropriate init "
+"scripts to avoid timeouts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1301
+msgid ""
+"For more information on setting up sleep states, read <c>man hibernate.conf</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1306
+msgid ""
+"Ready? Now is the last chance to backup any data you want to keep after "
+"executing the next command. Notice that you probably have to hit a special "
+"key like <c>Fn</c> to resume from sleep."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1312
+msgid "Calling sleep"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1312
+#, no-wrap
+msgid ""
+"\n"
+"# <i>hibernate-ram</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1316
+msgid ""
+"If you're still reading, it seems to work. You can also setup standby (S1) "
+"in a similar way by editing <path>sysfs-ram.conf</path> and changing "
+"\"UseSysfsPowerState mem\" to \"UseSysfsPowerState standby\". S3 and S4 are "
+"the more interesting sleep states due to greater energy savings however."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1326
+msgid "Hibernate (S4)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1329
+msgid ""
+"This section introduces hibernation, where a snapshot of the running system "
+"is written to disk before powering off. On resume, the snapshot is loaded "
+"and you can go on working at exactly the point you called hibernate before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1335
+msgid ""
+"Don't exchange non hot-pluggable hardware when suspended. Don't attempt to "
+"load a snapshot with a different kernel image than the one it was created "
+"with. Shutdown any NFS or samba server/client before hibernating."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1341
+msgid ""
+"There are two different implementations for S4. The original one is swsusp, "
+"then there is the newer tuxonice (formerly suspend2) with a nicer interface "
+"(including fbsplash support). A <uri link=\"http://tuxonice.net/features."
+"html#compare\">feature comparison</uri> is available at the <uri link="
+"\"http://www.tuxonice.net\">tuxonice homepage</uri>. There used to be "
+"Suspend-to-Disk (pmdisk), a fork of swsusp, but it has been merged back."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1351
+msgid ""
+"TuxOnIce is not included in the mainline kernel yet, therefore you either "
+"have to patch your kernel sources with the patches provided by <uri link="
+"\"http://www.tuxonice.net\">tuxonice.net</uri> or use <c>sys-kernel/tuxonice-"
+"sources</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1358
+msgid "The kernel part for both swusp and TuxOnIce is as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1362
+#, no-wrap
+msgid ""
+"\n"
+"Power Management support ---&gt;\n"
+"  <comment>(hibernate with swsusp)</comment>\n"
+"  [*] Hibernation (aka 'suspend to disk')\n"
+"      <comment>(replace /dev/SWAP with your swap partition)</comment>\n"
+"      (/dev/SWAP)      Default resume partition\n"
+"\n"
+"  <comment>(hibernate with TuxOnIce)</comment>\n"
+"  Enhanced Hibernation (TuxOnIce)\n"
+"    --- Image Storage (you need at least one allocator)\n"
+"    [*]    File Allocator\n"
+"    [*]    Swap Allocator\n"
+"    ---   General Options\n"
+"    [*]    Compression support\n"
+"    [ ]     Allow Keep Image Mode\n"
+"    [*]     Replace swsusp by default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1380
+msgid ""
+"The configuration for swsusp is rather easy. If you didn't store the "
+"location of your swap partition in the kernel config, you can also pass it "
+"as a parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not "
+"possible due to a broken image, use the <c>noresume</c> kernel parameter. "
+"The <c>hibernate-cleanup</c> init script invalidates swsusp images during "
+"the boot process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1389
+msgid "Invalidating swsusp images during the boot process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1389
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1431
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add hibernate-cleanup boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1393
+msgid ""
+"To activate hibernate with swsusp, use the hibernate script and set "
+"<c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/sysfs-disk</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1398
+msgid ""
+"Backup your data before doing this. Run <c>sync</c> before executing one of "
+"the commands to have cached data written to disk. First try it outside of X, "
+"then with X running, but not logged in."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1404
+msgid ""
+"If you experience kernel panics due to uhci or similar, try to compile USB "
+"support as module and unload the modules before sending your laptop to sleep "
+"mode. There are configuration options for this in <path>common.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1410
+msgid "Hibernating with swsusp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1410
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/hibernate/common.conf</i>\n"
+"<comment>(Make sure you have a backup of your data)</comment>\n"
+"# <i>hibernate</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1416
+msgid ""
+"The following section discusses the setup of TuxOnIce including fbsplash "
+"support for a nice graphical progress bar during suspend and resume."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1421
+msgid ""
+"The first part of the configuration is similar to the configuration of "
+"swsusp. In case you didn't store the location of your swap partition in the "
+"kernel config, you have to pass it as a kernel parameter with the "
+"<c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a "
+"broken image, append the <c>noresume</c> parameter. Additionally, the "
+"<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the "
+"boot process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1431
+msgid "Invalidating TuxOnIce images during the boot process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1435
+msgid ""
+"Now edit <path>/etc/hibernate/tuxonice.conf</path>, enable the <c>TuxOnIce</"
+"c> options you need. Do not enable the <c>fbsplash</c> options in <c>common."
+"conf</c> just yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1441
+msgid "Hibernating with TuxOnIce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1441
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/hibernate/tuxonice.conf</i>\n"
+"<comment>(Make sure you have a backup of your data)</comment>\n"
+"# <i>hibernate</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1447
+msgid ""
+"Please configure <c>fbsplash</c> now if you didn't do already. To enable "
+"fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> "
+"package is needed. Additionally, you've got to enable the <c>fbsplash</c> "
+"USE flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1453
+msgid "Installing tuxonice-userui"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1453
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"sys-apps/tuxonice-userui fbsplash\" &gt;&gt; /etc/portage/package.use</i>\n"
+"<comment>(It may be marked ~arch, so first it must be keyworded)</comment>\n"
+"# <i>echo \"sys-apps/tuxonice-userui\" &gt;&gt; /etc/portage/package.keywords</i>\n"
+"# <i>emerge tuxonice-userui</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1460
+msgid ""
+"The ebuild tells you to make a symlink to the theme you want to use. For "
+"example, to use the <c>livecd-2005.1</c> theme, run the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1465
+msgid "Using the livecd-2005.1 theme during hibernation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1465
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ln -sfn /etc/splash/livecd-2005.1 /etc/splash/tuxonice</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1469
+msgid ""
+"If you don't want a black screen in the first part of the resume process, "
+"you have to add the <c>tuxoniceui_fbsplash</c> tool to your initrd image. "
+"Assuming you created the initrd image with <c>splash_geninitramfs</c> and "
+"saved it as <path>/boot/fbsplash-emergence-1024x768</path>, here's how to do "
+"that."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1476
+msgid "Adding tuxoniceui_fbsplash to an initrd image"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1476
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount /boot</i>\n"
+"# <i>mkdir ~/initrd.d</i>\n"
+"# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>\n"
+"# <i>cd ~/initrd.d</i>\n"
+"# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>\n"
+"# <i>rm fbsplash-emergence-1024x768</i>\n"
+"# <i>cp /usr/sbin/tuxoniceui_fbsplash sbin/</i>\n"
+"# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 &gt; /boot/fbsplash-tuxonice-emergence-1024x768</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1487
+msgid ""
+"Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that "
+"your TuxOnIce kernel uses <path>/boot/fbsplash-tuxonice-emergence-1024x768</"
+"path> as initrd image. You can now test a dry run to see if everything is "
+"setup correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1494
+msgid "Test run for fbsplash hibernation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1494
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tuxoniceui_fbsplash -t</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1498
+msgid ""
+"Afterwards open <path>/etc/hibernate/common.conf</path> and activate the "
+"fbsplash options. Execute <c>hibernate</c> and enjoy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1508
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1512
+msgid ""
+"<e>Q:</e> I'm trying to change the CPU frequency, but <path>/sys/devices/"
+"system/cpu/cpu0/cpufreq/scaling_governor</path> does not exist."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1518
+msgid ""
+"<e>A:</e> Make sure your processor supports CPU frequency scaling and you "
+"chose the right CPUFreq driver for your processor. Here is a list of "
+"processors that are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-"
+"SA1100, ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile "
+"K6-3+, AMD mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, "
+"Cyrix Media GXm, Intel mobile PIII and Intel mobile PIII-M on certain "
+"chipsets, Intel Pentium 4, Intel Xeon, Intel Pentium M (Centrino), National "
+"Semiconductors Geode GX, Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, "
+"SuperH SH-3, SH-4, several \"PowerBook\" and \"iBook2\" and various "
+"processors on some ACPI 2.0-compatible systems (only if \"ACPI Processor "
+"Performance States\" are available to the ACPI/BIOS interface)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1531
+msgid ""
+"<e>Q:</e> My laptop supports frequency scaling, but <path>/sys/devices/"
+"system/cpu/cpu0/cpufreq/</path> is empty."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1536
+msgid ""
+"<e>A:</e> Look for ACPI related error messages with <c>dmesg | grep ACPI</"
+"c>. Try to update the BIOS, especially if a broken DSDT is reported. You can "
+"also try to fix it yourself (which is beyond the scope of this guide)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1542
+msgid ""
+"<e>Q:</e> My laptop supports frequency scaling, but according to <path>/proc/"
+"cpuinfo</path> the speed never changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1547
+msgid ""
+"<e>A:</e> Probably you have activated symmetric multiprocessing support "
+"(CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older "
+"kernels had a bug causing this. In that case, run <c>emerge x86info</c>, "
+"update your kernel as asked and check the current frequency with <c>x86info -"
+"mhz</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1554
+msgid ""
+"<e>Q:</e> I can change the CPU frequency, but the range is not as wide as in "
+"another OS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1559
+msgid ""
+"<e>A:</e> You can combine frequency scaling with ACPI throttling to get a "
+"lower minimum frequency. Notice that throttling doesn't save much energy and "
+"is mainly used for thermal management (keeping your laptop cool and quiet). "
+"You can read the current throttling state with <c>cat /proc/acpi/processor/"
+"CPU/throttling</c> and change it with <c>echo -n \"0:x\" &gt; /proc/acpi/"
+"processor/CPU/limit</c>, where x is one of the Tx states listed in <path>/"
+"proc/acpi/processor/CPU/throttling</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1569
+msgid ""
+"<e>Q:</e> When configuring the kernel, powersave, performance and userspace "
+"governors show up, but that ondemand thing is missing. Where do I get it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1574
+msgid ""
+"<e>A:</e> The ondemand governor is only included in recent kernel sources. "
+"Try updating them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1579
+msgid "<e>Q:</e> Battery life time seems to be worse than before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1583
+msgid ""
+"<e>A:</e> Check your BIOS settings. Maybe you forgot to re-enable some of "
+"the settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1588
+msgid ""
+"<e>Q:</e> My battery is charged, but KDE reports there would be 0% left and "
+"immediately shuts down."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1593
+msgid ""
+"<e>A:</e> Check that battery support is compiled into your kernel. If you "
+"use it as a module, make sure the module is loaded."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1598
+msgid ""
+"<e>Q:</e> My system logger reports things like \"logger: ACPI group "
+"battery / action battery is not defined\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1603
+msgid ""
+"<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path> "
+"script that is shipped with acpid. You can safely ignore it. If you like to "
+"get rid of it, you can comment the appropriate line in <path>/etc/acpi/"
+"default.sh</path> as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1610
+msgid "Disabling warnings about unknown acpi events"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1610
+#, no-wrap
+msgid ""
+"\n"
+"        *)      # logger \"ACPI action $action is not defined\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1614
+msgid "<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1618
+msgid ""
+"<e>A:</e> This seems to be a kernel bug. Read on <uri link=\"http://bugme."
+"osdl.org/show_bug.cgi?id=1752\">here</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1623
+msgid ""
+"<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</"
+"path> and now X.org crashes / the screen stays black / my laptop doesn't "
+"shutdown properly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1629
+msgid ""
+"<e>A:</e> This happens on some systems. You have to disable "
+"<c>DynamicClocks</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1634
+msgid ""
+"<e>Q:</e> I want to use TuxOnIce, but it tells me my swap partition is too "
+"small. Resizing is not an option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1639
+msgid ""
+"<e>A:</e> If there is enough free space on your system, you can use the "
+"filewriter instead of the swapwriter. The <c>hibernate-script</c> supports "
+"it as well. More information can be found in <path>/usr/src/linux/"
+"Documentation/power/tuxonice.txt</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1646
+msgid ""
+"<e>Q:</e> I just bought a brand new battery, but it only lasts for some "
+"minutes! What am I doing wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1651
+msgid ""
+"<e>A:</e> First follow your manufacturer's advice on how to charge the "
+"battery correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1656
+msgid "<e>Q:</e> The above didn't help. What should I do then?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1660
+msgid ""
+"<e>A:</e> Some batteries sold as \"new\" are in fact old ones. Try the "
+"following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1664
+msgid "Querying battery state"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1664
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>grep capacity /proc/acpi/battery/BAT0/info</i>\n"
+"design capacity:     47520 mWh\n"
+"last full capacity:  41830 mWh\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1670
+msgid ""
+"If the \"last full capacity\" differs significantly from the design "
+"capacity, your battery is probably broken. Try to claim your warranty."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1675
+msgid "<e>Q:</e> My problem is not listed above. Where should I go next?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1679
+msgid ""
+"<e>A:</e> Don't fear to contact me, <mail link=\"earthwings@gentoo.org"
+"\">Dennis Nienhüser</mail>, directly. The <uri link=\"http://forums.gentoo."
+"org\">Gentoo Forums</uri> are a good place to get help as well. If you "
+"prefer IRC, try the <c>#gentoo-laptop</c><uri link=\"irc://irc.gentoo.org"
+"\">channel</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/prelink-howto.xml.po b/doc/gettext/ru/prelink-howto.xml.po
new file mode 100644
index 0000000..7bda5df
--- /dev/null
+++ b/doc/gettext/ru/prelink-howto.xml.po
@@ -0,0 +1,552 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):6
+msgid "Gentoo Linux Prelink Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):9
+msgid "cretin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail):9
+msgid "Stefan Jones"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(author):11
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):15
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail):15
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):18
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail):18
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):21
+msgid "erwin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail):21
+msgid "Erwin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(abstract):27
+msgid ""
+"This guide tells you how to make use of prelink support in Portage 2.0.46 "
+"and later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(version):34
+msgid "1.18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(date):35
+msgid "2010-01-12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):38
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):40
+msgid "What is Prelink and how can it help me?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):43
+msgid ""
+"Most common applications make use of shared libraries. These shared "
+"libraries need to be loaded into memory at runtime and the various symbol "
+"references need to be resolved. For most small programs this dynamic linking "
+"is very quick. But for programs written in C++ and that have many library "
+"dependencies, the dynamic linking can take a fair amount of time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):51
+msgid ""
+"On most systems, libraries are not changed very often and when a program is "
+"run, the operations taken to link the program are the same every time. "
+"Prelink takes advantage of this by carrying out the linking and storing it "
+"in the executable, in effect prelinking it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):58
+msgid ""
+"Prelinking can cut the startup times of applications. For example, a typical "
+"KDE program's loading time can be cut by as much as 50%. The only "
+"maintenance required is re-running prelink every time a library is upgraded "
+"for a pre-linked executable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(warn):65
+msgid ""
+"Prelink will not work with Hardened Gentoo. This is because both projects "
+"try to change the address space mapping of shared libraries. But prelink "
+"with the -R option randomises library base addresses, providing some degree "
+"of hardened protection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):75
+msgid "Summary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):79
+msgid ""
+"Prelinking is done via a program called, surprisingly, <c>prelink</c>. It "
+"changes the binary to make it start faster."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):83
+msgid ""
+"If an application's dependent libraries change after you have prelinked it, "
+"you need to re-prelink the application, otherwise you lose the speed "
+"advantage. This is to say, everytime you update a package via portage that "
+"updates libraries, they need to be re-prelinked."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):89
+msgid ""
+"The change to the binary is fully reversible. <c>prelink</c> has an undo "
+"function."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):93
+msgid ""
+"Current versions of Portage can handle, via <c>prelink</c>, the changing "
+"MD5sums and mtimes of the binaries."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):97
+msgid ""
+"You do not need to set <c>FEATURES=\"prelink\"</c> in your <path>make.conf</"
+"path> file; Portage will automatically support prelink if it can find the "
+"prelink binary."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):109
+msgid "Setting up Prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):111
+msgid "Installing the Programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):114
+msgid ""
+"First you need to install the <c>prelink</c> tool. The emerge process "
+"automatically verifies that your system can prelink safely."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):119
+msgid "Installing Prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):119
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge prelink</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):123
+msgid ""
+"A number of people get errors in emerging prelink because of the failed "
+"tests. The tests were put in for safety reasons, prelink's behavior is "
+"undefined if you disable them. The emerge errors are usually only dependent "
+"on the core packages; binutils, gcc, and glibc. Try re-emerging those "
+"packages in that order."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(note):131
+msgid ""
+"Tip: If you get an error try compiling and testing <c>prelink</c> yourself "
+"(<c>./configure</c> ; <c>make</c> ; <c>make check</c> ). On a failure you "
+"can view the *.log files in the testsuite directory. They may provide you "
+"with some useful clues."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):138
+msgid ""
+"If you have a set of steps that reproduces the emerge error on another "
+"system please check <uri link=\"http://bugzilla.gentoo.org\">Bugzilla</uri> "
+"and create a bug report if it has not already been reported."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):147
+msgid "Preparing your System"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):150
+msgid ""
+"Also make sure that you do <e>not</e> have -fPIC set in your CFLAGS/"
+"CXXFLAGS. If you do, you will need to rebuild your entire system without."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):158
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):161
+msgid ""
+"Running <c>env-update</c> will generate the <path>/etc/prelink.conf</path> "
+"file that tells <path>prelink</path> which files to prelink."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):166
+msgid "Running env-update"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):166
+#, no-wrap
+msgid ""
+"\n"
+"# <i>env-update</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):170
+msgid ""
+"Unfortunately you cannot prelink files that were compiled by old versions of "
+"binutils. Most of these applications come from pre-compiled, binary only "
+"packages which are installed in <path>/opt</path>. Making the following file "
+"will tell prelink not to attempt to prelink them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):177
+msgid "/etc/env.d/60prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):177
+#, no-wrap
+msgid ""
+"\n"
+"PRELINK_PATH_MASK=\"/opt\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(note):181
+msgid "You can add more or less directories to the colon separated list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):190
+msgid "Prelinking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):192
+msgid "Prelink Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):195
+msgid ""
+"I use the following command to prelink all the binaries in the directories "
+"given by <path>/etc/prelink.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):200
+msgid "Prelinking listed files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):200
+#, no-wrap
+msgid ""
+"\n"
+"# <i>prelink -amR</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(warn):204
+msgid ""
+"It has been observed that if you are low on disk space and you prelink your "
+"entire system then there is a possibility that your binaries may be "
+"truncated. The result being a b0rked system. Use the <c>file</c> or "
+"<c>readelf</c> command to check the state of a binary file. Alternatively, "
+"check the amount of free space on your harddrive ahead of time with <c>df -"
+"h</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(th):214
+msgid "The options explained:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(th):217
+msgid "-a"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(ti):218
+msgid "\"All\": prelinks all the binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(th):221
+msgid "-m"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(ti):222
+msgid ""
+"Conserve the virtual memory space. This is needed if you have a lot of "
+"libraries that need to be prelinked."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(th):228
+msgid "-R"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(ti):229
+msgid ""
+"Random -- randomize the address ordering, this enhances security against "
+"buffer overflows."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(note):236
+msgid "For more options and details see <c>man prelink</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):243
+msgid "Prelink Cron Job"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):246
+msgid ""
+"<c>sys-devel/prelink-20060213</c> and later install a cron job in <path>/etc/"
+"cron.daily/prelink</path>. To enable it, edit the configuration file <path>/"
+"etc/conf.d/prelink</path>. This will run prelink daily in the background, as "
+"needed, saving you running the command manually."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):256
+msgid "Speeding Up KDE After Prelinking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):259
+msgid ""
+"KDE's loading time can be greatly reduced after prelinking. If you inform "
+"KDE that it has been prelinked it will disable the loading of <c>kdeinit</c> "
+"(as it isn't required anymore) which speeds up KDE even more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):265
+msgid ""
+"Set <c>KDE_IS_PRELINKED=1</c> in <path>/etc/env.d/*kdepaths*</path> to "
+"inform KDE about the prelinking."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):273
+msgid "Removing prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):276
+msgid ""
+"If you ever change your mind about prelinking, before you unmerge prelink, "
+"you'll first need to remove the prelink cronjob from <path>/etc/cron.daily</"
+"path> and <path>/etc/conf.d/prelink</path>. Next, you'll have to remove "
+"prelinking from all binaries:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):283
+msgid "Removing prelinking from all binaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):283
+#, no-wrap
+msgid ""
+"\n"
+"# <i>prelink -au</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):287
+msgid "Finally, unmerge the <c>prelink</c> package itself:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):291
+msgid "Unmerging prelink"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):291
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -aC prelink</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):300
+msgid "Known Problems and Fixes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):302
+msgid "\"Cannot prelink against non-PIC shared library\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):305
+msgid ""
+"The cause of this problem is from badly compiled shared libraries that were "
+"compiled without the -fPIC gcc option for all their object files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):310
+msgid "Here are the libraries that haven't been fixed or cannot be fixed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):315
+msgid ""
+"The libraries in the wine package, including winex. Prelinking wouldn't "
+"speed up MS Windows executables anyway."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):319
+msgid ""
+"The library in media-video/mjpegtools, <path>/usr/lib/liblavfile-1.6.so.0</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(li):323
+msgid ""
+"Nvidia OpenGl libraries, <path>/usr/lib/opengl/nvidia/lib/libGL.so.*</path>. "
+"Due to performance reasons they were compiled without PIC support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):330
+msgid ""
+"If your problem library was not listed please report it with, preferably, a "
+"patch to add <c>-fPIC</c> to the relevant CFLAGS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):338
+msgid "When I prelink my system some static binaries don't work anymore"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):341
+msgid ""
+"Where glibc is concerned, there is no such thing as a 100% static binary. If "
+"you statically compile a binary with glibc, it may still depend on other "
+"system files. Below is an explanation by Dick Howell,"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):347
+msgid ""
+"\"I suppose the idea is that everything will be in the downloaded file, so "
+"nothing depends on the local libraries on the target system. Unfortunately "
+"with Linux, and I think anything else using GLIBC, this still isn't quite "
+"true. There's this \"libnss\" (name service switch, some people seem to call "
+"it network security system) which provides functions for accessing various "
+"databases for authentication, network information, and other things. It's "
+"supposed to make application programs independent of the separately "
+"configured actual network environment of the machine. A nice idea, but "
+"changes to GLIBC can lead to problems loading it. And you can't statically "
+"link \"libnss\", since it is configured for each machine individually. The "
+"problem comes, I think, mainly from statically linking other GLIBC "
+"libraries, notably \"libpthread\", \"libm\", and \"libc\", from which come "
+"incompatible calls to \"libnss\" functions.\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):366
+msgid ""
+"Prelink aborts with \"prelink: dso.c:306: fdopen_dso: Assertion `j == k' "
+"failed.\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):370
+msgid ""
+"This a known problem, kindly diagnosed <uri link=\"http://bugs.gentoo.org/"
+"show_bug.cgi?id=13878\">here</uri>. Prelink cannot cope with UPX-compressed "
+"executables. As of prelink-20021213 there is no fix except to hide the "
+"executables while you are prelinking. See the <uri link="
+"\"#doc_chap2_sect2\">Configuration section</uri> above for an easy way to do "
+"this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):382
+msgid "I use grsecurity and it seems that prelinking doesn't work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):385
+msgid ""
+"In order to prelink on a system with grsecurity using a randomized mmap() "
+"base, it is necessary to turn \"randomized mmap() base\" OFF for <path>/lib/"
+"ld-2.3.*.so</path>. This can be done with the <c>chpax</c> utility, but it "
+"must be done when the file is not in use (f.i. boot from a rescue CD)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):396
+msgid ""
+"Prelink fails with error \"prelink: Can't walk directory tree XXXX: Too many "
+"levels of symbolic links\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):402
+msgid ""
+"Your symlinks are nested too deeply. This happens when a symlink points to "
+"itself. For example, <path>/usr/lib/lib -&gt; lib</path> is the most common. "
+"To fix this, you can find the symlink manually or use the utility provided "
+"by the <c>symlinks</c> package:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre:caption):409
+msgid "Fix symlinks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(pre):409
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge symlinks</i>\n"
+"# <i>symlinks -drv /</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):414
+msgid ""
+"More details can be found at <uri link=\"http://bugs.gentoo.org/show_bug.cgi?"
+"id=82117\">Bugzilla</uri> and this <uri link=\"http://forums.gentoo.org/"
+"viewtopic-t-458144-highlight-prelink.html\">forum post</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(title):427
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(p):431
+msgid ""
+"Prelinking can drastically speed up the start up times for a number of large "
+"applications. Support is built into Portage. Prelinking is also safe as you "
+"can always undo the prelinking for any binary if you come across any "
+"problems. Just remember that when you update glibc or other libraries that "
+"you prelinked with, you need to rerun <path>prelink</path>! In short good "
+"luck!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//prelink-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/printing-howto.xml.po b/doc/gettext/ru/printing-howto.xml.po
new file mode 100644
index 0000000..5e2c5c0
--- /dev/null
+++ b/doc/gettext/ru/printing-howto.xml.po
@@ -0,0 +1,1330 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):6
+msgid "Gentoo Printing Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(mail:link):9
+msgid "swift"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(abstract):15
+msgid ""
+"This document covers the installation and maintenance of printers using CUPS "
+"and Samba. It covers local installation and networked installations and "
+"you'll also find instructions on using shared printers from other operating "
+"systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(version):25
+msgid "3.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(date):26
+msgid "2010-03-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):29
+msgid "Printing and Gentoo Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):31
+msgid "Use the Right Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):34
+msgid ""
+"Linux has great support for printers; the right tool for the job is called "
+"CUPS (<uri link=\"http://www.cups.org\">Common Unix Printing System</uri>). "
+"Since the beginning of the project, back in 1999, the installation and "
+"maintenance of CUPS has improved dramatically."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):41
+msgid ""
+"In this document we will cover how to use CUPS to setup a local or networked "
+"printer. We will not go in too much detail since the project has <uri link="
+"\"http://www.cups.org/documentation.php\">great documentation</uri> "
+"available for advanced usage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):53
+msgid "Configure your Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):55
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):544
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):768
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):1000
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):58
+msgid ""
+"When you want to install a printer on your system you need to know how your "
+"printer will be attached to your system. Is it through a local port like LPT "
+"or USB, or is it networked? And if it is, does it use the Internet Printing "
+"Protocol (IPP) or is it through the Microsoft Windows SMB-CIFS protocol "
+"(Microsoft Windows Sharing)?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):66
+msgid ""
+"The next few sections explain what minimal kernel configuration you need. Of "
+"course, this depends on how your printer is going to be attached to your "
+"system, so for your convenience we have separated the instructions:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):73
+msgid "#lpt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):73
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):99
+msgid "Locally Attached Printer (LPT)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):74
+msgid "#usb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):74
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):139
+msgid "Locally Attached Printer (USB)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):75
+msgid "#ipp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):75
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):173
+msgid "Remotely Attached Printer (IPP)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):76
+msgid "#smb-cifs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):76
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):186
+msgid "Remotely Attached Printer (SMB-CIFS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):79
+msgid ""
+"So navigate to <path>/usr/src/linux</path> and run <c>make menuconfig</c> to "
+"enter the kernel configuration. If you used <c>genkernel</c> to configure "
+"your kernel, you should still perform these steps just to make sure nothing "
+"was missed out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):86
+msgid ""
+"In the next configuration examples, we will add the necessary support <e>in</"
+"e> the kernel, not as modules. This is not mandatory; if you want you can "
+"easily use modular support. Don't forget to load the appropriate modules "
+"afterwards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):92
+msgid "Now go to the appropriate section to configure (or check) your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):102
+msgid ""
+"The LPT port is generally used to identify the parallel printer port. You "
+"need to enable parallel port support first, then PC-style parallel port "
+"support (unless you are a SPARC user) after which you enable parallel "
+"printer support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):108
+msgid "Parallel Port Printer Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):108
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers --&gt;\n"
+"  &lt;*&gt; Parallel port support\n"
+"  &lt;*&gt;   PC-style hardware\n"
+"\n"
+"Device Drivers --&gt;\n"
+"  Character Devices --&gt;\n"
+"    &lt;*&gt; Parallel printer support\n"
+"       [*]      IEEE 1284 transfer modes)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(note):119
+msgid ""
+"Some users might need to enable other options in the <c>Parallel port "
+"support</c> section. Check the kernel configuration <c>Help</c> function for "
+"more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):125
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):159
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):200
+msgid ""
+"That's it; quit the kernel configuration and rebuild your kernel. Don't "
+"forget to copy the new kernel image to the <path>/boot</path> location (and "
+"don't forget to mount <path>/boot</path> if needed) and update your boot "
+"loader configuration prior to rebooting your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):132
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):166
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):207
+msgid ""
+"Now continue with <uri link=\"#cups\">Installing and Configuring CUPS</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):142
+msgid "To enable USB printing, you just need USB support in your kernel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):146
+msgid "USB Port Printer Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):146
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers --&gt;\n"
+"  USB Support --&gt;\n"
+"    &lt;*&gt; Support for Host-side USB\n"
+"    <comment>(...)</comment>\n"
+"    --- USB Host Controller Drivers\n"
+"    <comment>(Select the HCD that your system uses. If you do not know which one\n"
+"     to select, run \"lspci -v | grep HCI\" from another terminal)</comment>\n"
+"    &lt;*&gt; EHCI HCD (USB 2.0) support <comment>( or )</comment>\n"
+"    &lt;*&gt; OHCI HCD support           <comment>( or )</comment>\n"
+"    &lt;*&gt; UHCI HCD (most Intel and VIA) support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):176
+msgid ""
+"To be able to connect to a remotely attached printer through the Internet "
+"Printing Protocol your kernel just needs to have networking support. "
+"Assuming your kernel has that already, continue with <uri link=\"#cups"
+"\">Installing and Configuring CUPS</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):189
+msgid "Your kernel must support SMB CIFS:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):193
+msgid "SMB-CIFS Printer Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):193
+#, no-wrap
+msgid ""
+"\n"
+"File systems --&gt;\n"
+"  Network File Systems --&gt;\n"
+"    &lt;*&gt; SMB file system support (to mount Windows shares etc.)\n"
+"    &lt;*&gt; CIFS support (advanced network file system for Samba, Windows and other CIFS compliant servers)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):216
+msgid "Installing and Configuring CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):218
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):221
+msgid ""
+"Installing CUPS with Gentoo is a breeze. CUPS has a few optional features "
+"that might interest you. To enable or disable those features, use the USE "
+"flags associated with them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(th):229
+msgid "USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(th):230
+msgid "Impact on CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):233
+msgid "dbus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):234
+msgid "Adds support for the <c>dbus</c> system message bus."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):237
+msgid "jpeg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):238
+msgid "Adds support for printing JPEG images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):241
+msgid "nls"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):242
+msgid ""
+"Enable National Language Support. With nls in place, CUPS is able to deliver "
+"localized feedback so you can hopefully enjoy CUPS in your native language."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):249
+msgid "pam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):250
+msgid ""
+"If you need print job authentication through the Pluggable Authentication "
+"Modules, this will activate PAM support for CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):256
+msgid "php"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):257
+msgid "Adds support for php scripting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):260
+msgid "png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):261
+msgid "Adds support for printing PNG images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):264
+msgid "ppds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):265
+msgid ""
+"Adds support for automatically generated ppd (printing driver) files. See "
+"<uri link=\"#installing_best\">Installing the Best Driver</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):271
+msgid "samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):272
+msgid ""
+"If you want to be able to share locally attached printers to Windows systems "
+"on your network using the SMB-CIFS protocol, or you want to be able to use "
+"shared printers from Windows systems, you need SAMBA support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):279
+msgid "slp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):280
+msgid ""
+"In a managed environment the printer might be made available as a service to "
+"others. With the Service Location Protocol you can easily find and configure "
+"a service on your system. Enable this USE flag if your printer is available "
+"as a service or should be made available as one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):288
+msgid "ssl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):289
+msgid ""
+"If you want remote authentication and/or privacy, you need support for the "
+"Secure Socket Layer, allowing for encrypted printing sessions. Support for "
+"SSL must be available on all participating systems in your network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):296
+msgid "tiff"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):297
+msgid "Adds support for printing TIFF images."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):300
+msgid "X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):301
+msgid ""
+"Allows you to use your desktop menu to load the CUPS configuration webpage "
+"into your preferred browser."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):308
+msgid ""
+"Check the current USE settings. If you want to deviate from your current USE "
+"settings for CUPS alone, add the appropriate USE flags to <path>/etc/portage/"
+"package.use</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):314
+msgid "USE flag settings for CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):314
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -pv cups</i>\n"
+"[ebuild N     ] net-print/cups-1.2.6  \"X dbus jpeg nls pam png ppds ssl -php -samba -slp -tiff\" 0 kB\n"
+"\n"
+"<comment>(For instance, to enable SAMBA support for CUPS)</comment>\n"
+"# <i>nano -w /etc/portage/package.use</i>\n"
+"net-print/cups samba\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):323
+msgid "If you are happy with the result, have Portage install CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):327
+msgid "Installing CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):327
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge cups</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(impo):331
+msgid ""
+"Any users that need to print should be added to the <c>lp</c> group. Add "
+"them by running (as root) <c>gpasswd -a username lp</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):336
+msgid ""
+"If the printer is attached to your system locally, you need to load CUPS "
+"automatically on start-up. Make sure your printer is attached and powered on "
+"before you start CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):342
+msgid "Automatically starting CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):342
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/cupsd start</i>\n"
+"# <i>rc-update add cupsd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):350
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):353
+msgid ""
+"The default CUPS server configuration in <path>/etc/cups/cupsd.conf</path> "
+"is sufficient for most users. However, several users might need some changes "
+"to the CUPS configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):359
+msgid "In the next sections we cover a few changes that are often needed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):364
+msgid ""
+"In <uri link=\"#remote_usage\">Remote Printer Access</uri> we allow other "
+"systems to use the printer attached to this Linux workstation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):368
+msgid ""
+"In <uri link=\"#remote_admin\">CUPS Remote Administration</uri> we grant "
+"access to the CUPS administration from remote systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):372
+msgid ""
+"In <uri link=\"#windows_pcl\">Enable Support for Windows PCL Drivers</uri> "
+"you configure CUPS to support Windows PCL drivers. This is advised if you "
+"want Windows systems to be able to use a Samba-shared printer as most "
+"Windows drivers are PCL drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):378
+msgid ""
+"In <uri link=\"#setup_remote\">Setting Up a Remote Printer</uri> we "
+"configure this system to use a printer attached to another system (not "
+"Windows share)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):388
+msgid "Remote Printer Access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):391
+msgid ""
+"If you want other systems to use your printer through IPP you need to "
+"explicitly grant access to the printer in <path>/etc/cups/cupsd.conf</path>. "
+"If you want to share your printer using SAMBA, this change is not needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):397
+msgid ""
+"Open up <path>/etc/cups/cupsd.conf</path> in your favorite editor and add in "
+"an <c>Allow</c> line for the system(s) that should be able to reach to your "
+"printer. In the next example, we grant access to the printer from localhost "
+"and from any system whose IP address starts with <c>192.168.0</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):404
+msgid "Allowing remote access to the printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):404
+#, no-wrap
+msgid ""
+"\n"
+"&lt;Location /&gt;\n"
+"  Order allow,deny\n"
+"  <i>Allow localhost</i>\n"
+"  <i>Allow from 192.168.0.*</i>\n"
+"&lt;/Location&gt;\n"
+"\n"
+"<comment>(This broadcasts browsing information to the clients on the network)\n"
+"(This is so that they know the printer is available)</comment>\n"
+"BrowseAddress 192.168.0.*:631\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):416
+msgid ""
+"Also, you will need to specify which port CUPS listens to, so that it will "
+"respond to printing requests from other machines on your network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):421
+msgid "Port configuration in /etc/cups/cupsd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):421
+#, no-wrap
+msgid ""
+"\n"
+"Listen *:631\n"
+"<comment>(Make sure that localhost is commented out)</comment>\n"
+"#Listen localhost:631\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(note):427
+msgid ""
+"If you are still using CUPS 1.1 (which is now deprecated), then you will "
+"need to use a different syntax for remote printing requests:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):432
+msgid "Deprecated CUPS 1.1 configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):432
+#, no-wrap
+msgid ""
+"\n"
+"Port 631\n"
+"<comment>(Make sure the next two lines are commented out)</comment>\n"
+"#Listen 127.0.0.1:631\n"
+"#Listen localhost:631\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):442
+msgid "CUPS Remote Administration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):445
+msgid ""
+"If you are interested in remote administration, you need to grant access "
+"from other systems than just localhost to the CUPS administration. Edit "
+"<path>/etc/cups/cupsd.conf</path> and have it explicitly grant access to the "
+"systems you want. For instance, to grant access to the system with IP "
+"address of 192.168.0.3:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):453
+msgid "Allowing remote access in /etc/cups/cupsd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):453
+#, no-wrap
+msgid ""
+"\n"
+"&lt;Location /admin&gt;\n"
+"<comment>(...)</comment>\n"
+"  Encryption Required\n"
+"  Order allow,deny\n"
+"  <i>Allow localhost</i>\n"
+"  <i>Allow 192.168.0.3</i>\n"
+"&lt;/Location&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):463
+msgid ""
+"Do not forget to restart CUPS after making changes to <path>/etc/cups/cupsd."
+"conf</path> by running <c>/etc/init.d/cupsd restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):471
+msgid "Enable Support for Windows PCL Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):474
+msgid ""
+"PCL drivers send raw data to the print server. To enable raw printing on "
+"CUPS, you need to edit <path>/etc/cups/mime.types</path> and uncomment the "
+"line <c>application/octet-stream</c> if it is not already uncommented. Then "
+"you need to edit <path>/etc/cups/mime.convs</path> and do the same, if it is "
+"not already uncommented."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):482
+msgid "Enable support for raw printing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):482
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vim /etc/cups/mime.types</i>\n"
+"<comment>(Uncomment the line so that the file contains:)</comment>\n"
+"application/octet-stream\n"
+"\n"
+"# <i>vim /etc/cups/mime.convs</i>\n"
+"<comment>(Uncomment the line so that the file contains:)</comment>\n"
+"application/octet-stream     application/vnd.cups-raw    0    -\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):492
+msgid ""
+"Do not forget to restart CUPS after making these changes by running <c>/etc/"
+"init.d/cupsd restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):500
+msgid "Setting Up a Remote Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):503
+msgid ""
+"If the printers are attached to a remote CUPS-powered server you can easily "
+"set up your system to use the remote printer by changing the <path>/etc/cups/"
+"client.conf</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):509
+msgid ""
+"Assuming the printer is attached to a system called <c>printserver.mydomain</"
+"c>, open up <path>/etc/cups/client.conf</path> with your favorite editor and "
+"set the <c>ServerName</c> directive:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):515
+msgid "Editing client.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):515
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vim /etc/cups/client.conf</i>\n"
+"\n"
+"<comment>(Substitute printserver.mydomain with your print server name)</comment>\n"
+"ServerName <i>printserver.mydomain</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):522
+msgid ""
+"The remote system will have a default printer setting which you will be "
+"using. If you want to change the default printer, use <c>lpoptions</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):527
+msgid "Changing the default printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):527
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(First list the available printers)</comment>\n"
+"# <i>lpstat -a</i>\n"
+"hpljet5p accepting requests since Jan 01 00:00\n"
+"hpdjet510 accepting requests since Jan 01 00:00\n"
+"\n"
+"<comment>(Set the HP LaserJet 5P as the default printer)</comment>\n"
+"# <i>lpoptions -d hpljet5p</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):542
+msgid "Configuring a Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):547
+msgid ""
+"If the printer you want to configure is remotely available through a "
+"different print server (running CUPS) you do not need to follow these "
+"instructions. Instead, read <uri link=\"#setup_remote\">Setting Up a Remote "
+"Printer</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):556
+msgid "Detecting the Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):559
+msgid ""
+"If you have a USB printer or your parallel port printer was powered on when "
+"you booted your Linux system, you might be able to retrieve information from "
+"the kernel stating that it has successfully detected your printer. However "
+"this is merely an indication and not a requirement."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):566
+msgid "Retrieving kernel information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):566
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(For a parallel port printer)</comment>\n"
+"$ <i>dmesg | grep -i print</i>\n"
+"parport0: Printer, Hewlett-Packard HP LaserJet 2100 Series\n"
+"\n"
+"<comment>(For a USB printer)</comment>\n"
+"$ <i>lsusb</i>\n"
+"<comment>(...)</comment>\n"
+"Bus 001 Device 007: ID 03f0:1004 Hewlett-Packard DeskJet 970c/970cse\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):580
+msgid "Installing the Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):583
+msgid ""
+"To have the printer installed on your system, fire up your browser and have "
+"it point to <uri link=\"http://localhost:631\">http://localhost:631</uri>. "
+"You will be greeted by the CUPS web interface from which you can perform all "
+"administrative tasks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(note):590
+msgid ""
+"If you use an HTTPS connection to CUPS, the first time you access the "
+"interface it <e>may</e> take a very long time before the site comes up. This "
+"is because the first request triggers the generation of the CUPS SSL "
+"certificates which can be a very time-consuming job."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):597
+msgid ""
+"Go to <e>Administration</e> and enter your root login and password "
+"information at the box. Then, when you have reached the administrative "
+"interface, click on <e>Add Printer</e>. You will be greeted by a new screen "
+"allowing you to enter the following information:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):605
+msgid ""
+"The <e>spooler name</e>, a short but descriptive name used on your system to "
+"identify the printer. This name should not contain spaces or any special "
+"characters. For instance, for the HP LaserJet 5P you could say <c>hpljet5p</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):611
+msgid ""
+"The <e>location</e>, a description where the printer is physically located "
+"(for instance in your room, or in the kitchen right next to your dish "
+"washer, ...). This is to help maintaining several printers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):616
+msgid ""
+"The <e>description</e> in which you should place a full description of the "
+"printer. A common use is the full printer name (like \"HP LaserJet 5P\")."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):622
+msgid ""
+"The next screen asks you for the device where the printer listens to. You "
+"will have the choice of several devices. The next table covers a few "
+"possible devices, but the list is not exhaustive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(th):630
+msgid "Device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(th):631
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):634
+msgid "AppSocket/HP JetDirect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):635
+msgid ""
+"This special device allows for network printers to be accessible through a "
+"HP JetDirect socket. Only specific printers support this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):641
+msgid "Internet Printing Protocol (IPP or HTTP)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):642
+msgid ""
+"Use this to reach your remote printer through the IPP protocol either "
+"directly (IPP) or through HTTP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):648
+msgid "LPD/LPR Host or Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):649
+msgid "Select this if the printer is remote and attached to a LPD/LPR server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):654
+msgid "Parallel Port #1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):655
+msgid ""
+"Select this when the printer is locally attached to your parallel port "
+"(LPT). When the printer is automatically detected its name will be appended "
+"to the device as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):662
+msgid "USB Printer #1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(ti):663
+msgid ""
+"Select this when the printer is locally attached to a USB port. The printer "
+"name should automatically be appended to the device name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):670
+msgid ""
+"If you are installing a remote printer, you will be asked for the URI to the "
+"printer:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):676
+msgid "An LPD printer server requires a <c>lpd://hostname/queue</c> syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):679
+msgid "An HP JetDirect printer requires a <c>socket://hostname</c> syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):682
+msgid ""
+"An IPP printer requires a <c>ipp://hostname/printers/printername</c> or "
+"<c>http://hostname:631/ipp/queue</c> syntax."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):693
+msgid ""
+"Next, select the printer manufacturer in the adjoining screen and the model "
+"type and number in the subsequent one. For many printers you will find "
+"multiple drivers. You can either select one now or search on <uri link="
+"\"http://www.linuxprinting.org/printer_list.cgi\">LinuxPrinting.org's "
+"Printer List</uri> for a good driver. You can change drivers easily later on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):701
+msgid ""
+"Once the driver is selected, CUPS will inform you that the printer has been "
+"added successfully to the system. You can now go to the printer management "
+"page on the administration interface and select <c>Configure Printer</c> to "
+"change the printer settings (resolution, page format, ...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):711
+msgid "Testing and Reconfiguring the Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):714
+msgid ""
+"To verify if the printer is working correctly, go to the printer "
+"administration page, select your printer and click on <c>Print Test Page</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):719
+msgid ""
+"If the printer does not seem to work correctly, click on <c>Modify Printer</"
+"c> to reconfigure the printer. You will be greeted with the same screens as "
+"during the first installation but the defaults will now be your current "
+"configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):726
+msgid ""
+"If you have no idea why your printer does not function, you might get a clue "
+"by looking at <path>/var/log/cups/error_log</path>. In the next example we "
+"find out that there is a permission error, probably due to a wrong <c>Allow</"
+"c> setting in <path>/etc/cups/cupsd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):733
+msgid "Looking for CUPS errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):733
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tail /var/log/cups/error_log</i>\n"
+"<comment>(...)</comment>\n"
+"E [11/Jun/2005:10:23:28 +0200] [Job 102] Unable to get printer status (client-error-forbidden)!\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):742
+msgid "Installing the Best Driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):745
+msgid ""
+"Many printer drivers exist; to find out which one has the best performance "
+"for your printer, visit the <uri link=\"http://www.linuxprinting.org/"
+"printer_list.cgi\">LinuxPrinting Printer List</uri>. Select your brand and "
+"type to find out what driver the site recommends. For instance, for the HP "
+"LaserJet 5P, the site recommends the <c>ljet4</c> driver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):754
+msgid ""
+"Download the PPD file from the site and place it in <path>/usr/share/cups/"
+"model</path>, then run <c>/etc/init.d/cupsd restart</c> as root. This will "
+"make the driver available through the CUPS web interface. Now reconfigure "
+"your printer as described above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):766
+msgid "Using Special Printer Drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):771
+msgid ""
+"Some printers require specific drivers or provide additional features that "
+"are not enabled through the regular configuration process as described "
+"above. This chapter will discuss a selection of printers and how they are "
+"made to work with Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):778
+msgid "The following printers and/or drivers are covered:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):783
+msgid "#gutenprint"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):783
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):791
+msgid "Gutenprint Driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(li):784
+msgid "<uri link=\"#hplip\">HPLIP Driver</uri> (deprecates HPOJ and HPIJS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri:link):785
+msgid "#pnm2ppa"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(uri):785
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):865
+msgid "PNM2PPA Driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):794
+msgid ""
+"The <uri link=\"http://gutenprint.sourceforge.net\">gutenprint</uri> drivers "
+"are high-quality, open source printer drivers for various Canon, Epson, HP, "
+"Lexmark, Sony, Olympus and PCL printers supporting CUPS, ghostscript, The "
+"Gimp and other applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):801
+msgid ""
+"Gentoo's Portage Tree contains an ebuild for the gutenprint drivers. Just "
+"use <c>emerge</c> to install them. Note that the ebuild listens to quite a "
+"few USE flags (such as <c>cups</c> and <c>ppds</c>). You must have enabled "
+"at least these two flags!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):808
+msgid "Installing gutenprint drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):808
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gutenprint</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):812
+msgid ""
+"When the emerge process has finished, the gutenprint drivers will be "
+"available through the CUPS web interface."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):820
+msgid "HPLIP Driver"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):823
+msgid ""
+"The <uri link=\"http://hplipopensource.com/hplip-web/index.html\">HPLIP "
+"Project</uri> uses the hpcups printer driver. It also includes scanner and "
+"fax support and service tools for various multi-purpose peripherals. For "
+"printing support, it is recomended to use the new hpcups driver, which you "
+"can enable with the <c>hpcups</c> USE flag. The old hpijs driver is still "
+"included when you build <c>hplip</c> with the <c>hpijs</c> USE flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):832
+msgid ""
+"The default install enables dynamically generated ppd files at runtime. Some "
+"old printers may still require static ppd files. If you encounter problems "
+"when using <c>hp-setup</c> try enabling the <c>static-ppds</c> USE flag and "
+"rebuilding <c>hplip</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):839
+msgid "Installing the hplip drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):839
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -vp hplip</i>\n"
+"These are the packages that would be merged, in order:\n"
+"\n"
+"Calculating dependencies... done!\n"
+"[ebuild  N    ] net-print/hplip-3.9.12  USE=\"gtk hpcups qt4 -doc -fax -hpijs \n"
+"-libnotify -minimal -new-hpcups -parport -policykit -scanner -snmp -static-ppds\n"
+"-udev-acl\" 20,871 kB \n"
+"\n"
+"Total: 1 package (1 new), Size of downloads: 20,871 kB\n"
+"\n"
+"# <i>emerge hplip</i>\n"
+"<comment>(Make sure your USB printer is plugged into your computer)</comment>\n"
+"# <i>hp-setup</i>\n"
+"# <i>/etc/init.d/cupsd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):856
+msgid ""
+"When the emerge process has finished, the <c>hp-setup</c> tool will attempt "
+"to detect and install the printer drivers for your printer on the system. "
+"Once finished, your printer will be available in the CUPS configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):868
+msgid ""
+"PPA is an HP technology that focuses on sending low-level processing to the "
+"system instead of to the printer which makes the printer cheaper but more "
+"resource consuming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):874
+msgid ""
+"If the <uri link=\"http://www.linuxprinting.org/printer_list.cgi"
+"\">LinuxPrinting</uri> site informs you that the <uri link=\"http://pnm2ppa."
+"sourceforge.net/\">pnm2ppa</uri> driver is your best option, you need to "
+"install the <c>pnm2ppa</c> filter on your system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):882
+msgid "Installing the pnm2ppa filter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):882
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge pnm2ppa</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):886
+msgid ""
+"Once installed, download the PPD file for your printer from the <uri link="
+"\"http://www.linuxprinting.org/printer_list.cgi\">LinuxPrinting</uri> site "
+"and put it in <path>/usr/share/cups/model</path>. Next, configure your "
+"printer using the steps explained above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):898
+msgid "Printing From and To Microsoft Windows"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(note):902
+msgid ""
+"You should read our <uri link=\"/doc/en/quick-samba-howto.xml\">Samba/CUPS "
+"Guide</uri> for more detailed information on setting up CUPS with Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):910
+msgid "Configuring a Windows Client for IPP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):913
+msgid ""
+"Microsoft Windows supports IPP (Windows 9x and ME users need to <uri link="
+"\"http://support.microsoft.com/default.aspx?scid=kb;en-us;294439\">install</"
+"uri> it separately). To install a printer that is attached to your Linux box "
+"on Windows, fire up the <c>Add Printer</c> wizard and select <c>Network "
+"Printer</c>. When you are asked for the URI, use the <c>http://hostname:631/"
+"printers/queue</c> syntax."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):922
+msgid ""
+"Make sure that your systems <uri link=\"#remote_usage\">can reach</uri> your "
+"printer!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):930
+msgid "Configuring a Windows Client for a Samba Shared Printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):933
+msgid ""
+"To share the printer on the SMB-CIFS network, you must have SAMBA installed "
+"and configured correctly. How to do this is beyond the scope of this "
+"document, but we will quickly deal with the configuration of SAMBA for "
+"shared printers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):939
+msgid ""
+"Open <path>/etc/samba/smb.conf</path> with your favorite editor and add a <c>"
+"[printers]</c> section to it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):944
+msgid "Adding a [printers] section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):944
+#, no-wrap
+msgid ""
+"\n"
+"[printers]\n"
+"  comment      = All printers\n"
+"  path         = /var/spool/samba\n"
+"  browseable   = no\n"
+"  guest ok     = no\n"
+"  writable     = no\n"
+"  printable    = yes\n"
+"  public       = yes\n"
+"  printer name = hpljet5p\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):956
+msgid ""
+"Now navigate to the top of the <path>smb.conf</path> file until you are "
+"inside the <c>[global]</c> section. Then locate the <c>printcap name</c> and "
+"<c>printing</c> settings and set each of them to <c>cups</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):962
+msgid "Changing the [global] section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):962
+#, no-wrap
+msgid ""
+"\n"
+"[global]\n"
+"  <comment>(...)</comment>\n"
+"  printcap name = <i>cups</i>\n"
+"  printing      = <i>cups</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):969
+msgid ""
+"Make sure you enabled the <uri link=\"#windows_pcl\">Windows PCL drivers</"
+"uri> support in CUPS. Then, restart the <c>smb</c> service to have the "
+"changes take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):978
+msgid "Configuring a Linux Client for a Windows Print Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):981
+msgid ""
+"First of all, make sure that the printer is shared on your Windows system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):985
+msgid ""
+"Next, in the CUPS web interface, configure your printer as described "
+"previously. You will notice that CUPS has added another driver called "
+"<c>Windows Printer via SAMBA</c>. Select it and use the <c>smb://username:"
+"password@workgroup/server/printername</c> or <c>smb://server/printername</c> "
+"syntax for the URI."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):998
+msgid "Printing-related Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1003
+msgid ""
+"Many tools exist that help you configure a printer, use additional printing "
+"filters, add features to your printing capabilities, etc. This chapter lists "
+"a few of them. The list is not exhaustive and not meant to discuss each tool "
+"in great detail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):1013
+msgid "Gtk-LP - A Gtk-powered Printer Configuration Tool"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1016
+msgid ""
+"With <uri link=\"http://gtklp.sourceforge.net/index.shtml\">Gtk-LP</uri> you "
+"can install, modify and configure your printer from a stand-alone Gtk "
+"application. It uses CUPS and provides all standard CUPS capabilities as "
+"well. Definitely worth checking out if you dislike the CUPS Web interface or "
+"want a stand-alone application for your day-to-day printing routines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1024
+msgid "To install it, emerge <c>gtklp</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):1028
+msgid "Installing Gtk-LP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):1028
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gtklp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):1037
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(title):1039
+msgid "Error: Unable to convert file 0 to printable format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1042
+msgid ""
+"If you are having printing troubles and <path>/var/log/cups/error_log</path> "
+"shows this message:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):1047
+msgid "Error log"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):1047
+#, no-wrap
+msgid ""
+"\n"
+"Unable to convert file 0 to printable format\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1051
+msgid ""
+"You need to re-emerge <c>ghostscript-gpl</c> with the <c>cups</c> USE flag. "
+"You can either add <c>cups</c> to your USE flags in <path>/etc/make.conf</"
+"path>, or you can enable it only for <c>ghostscript-gpl</c> as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):1057
+msgid "Adding cups to ghostscript-gpl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):1057
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"app-text/ghostscript-gpl cups\" &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(p):1061
+msgid ""
+"Then emerge <c>ghostscript-gpl</c>. When it has finished compiling, be sure "
+"to restart <c>cupsd</c> afterward:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre:caption):1066
+msgid "Restarting cupsd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(pre):1066
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/cupsd restart</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//printing-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/qmail-howto.xml.po b/doc/gettext/ru/qmail-howto.xml.po
new file mode 100644
index 0000000..dd85347
--- /dev/null
+++ b/doc/gettext/ru/qmail-howto.xml.po
@@ -0,0 +1,881 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(guide:link):5
+msgid "/doc/en/qmail-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):7
+msgid "netqmail/vpopmail Virtual Mail Hosting System Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(mail:link):10
+msgid "vapier@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(mail):10
+msgid "Mike Frysinger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(abstract):13
+msgid ""
+"This document details how to create a mail hosting system based upon "
+"netqmail, vpopmail, courier-imap, mysql, and horde's imp."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(version):20
+msgid "1.15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(date):21
+msgid "2007-10-11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):28
+msgid ""
+"Whether you're providing e-mail for just system daemons, a single server, a "
+"domain, or for many virtual domains, netqmail can easily be setup to handle "
+"your needs. This guide will help you setup netqmail for all of these "
+"scenarios with a focus on remote access and encrypted communications the "
+"whole way through."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):35
+msgid ""
+"Specifically, the packages this guide will help you with are netqmail, "
+"courier-imap, vpopmail, and horde/imp. These core packages will also bring "
+"in daemontools, ucspi-tcp, mysql, apache, and mod_php. netqmail provides the "
+"core mta functions, courier-imap provides remote retrieval services, "
+"vpopmail provides virtual domain management, and horde/imp provides webmail "
+"access."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):43
+msgid ""
+"Before emerging anything, you will need the following USE variables enabled. "
+"If you've already emerged any of these packages, you may have to re-emerge "
+"them. <c>USE=\"maildir ssl imap mysql\"</c>. Additionally, if you want to "
+"use horde/imp for your webmail then you will need <c>USE=\"nls\"</c> before "
+"emerging mod_php."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(note):51
+msgid ""
+"This guide is written in steps. If at anytime you feel your setup is "
+"'complete', you do not need to continue."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):56
+msgid ""
+"The last step of course is to commit yourself to the netqmail system. There "
+"are many other packages with which you could build your e-mail system. Now "
+"is the time to research and decide that netqmail is for you. We have another "
+"<uri link=\"virt-mail-howto.xml\">lovely guide</uri> centered around <uri "
+"link=\"http://www.postfix.org/\">Postfix</uri>, or you could look into <uri "
+"link=\"http://www.exim.org/\">exim</uri>. It's up to you to choose the best "
+"solution for yourself; it is up to us to show you how to use netqmail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):71
+msgid "netqmail (talking to myself)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):75
+msgid "Emerge netqmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):75
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge mail-mta/netqmail</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):79
+msgid ""
+"This guide is designed around netqmail-1.05-r4 or later. Will it work with "
+"earlier versions? Maybe. Should you upgrade? Yes, if you want to be sure "
+"this guide will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(warn):85
+msgid ""
+"If you get a message like <c>the virtual/mta package conflicts with another "
+"package</c> then you need to make sure to unmerge the other MTA on your "
+"system. To figure out what package that is, just run <c>emerge netqmail -p</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):91
+msgid ""
+"Emerging netqmail will also emerge ucspi-tcp and daemontools. You can read "
+"up on <uri link=\"http://cr.yp.to/ucspi-tcp.html\">ucspi-tcp</uri> and on "
+"<uri link=\"http://cr.yp.to/daemontools.html\">daemontools</uri> if you "
+"like. Basically, daemontools is responsible for managing netqmail as a "
+"service while ucspi-tcp is responsible for managing the incoming TCP "
+"connections to the netqmail service."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):100
+msgid "First we have a few post-install configuration steps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):104
+msgid "Out-of-the-box setup for netqmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):104
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Customize to fit your personal information)</comment>\n"
+"# <i>nano /var/qmail/control/servercert.cnf</i>\n"
+"# <i>emerge --config netqmail</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):110
+msgid ""
+"The design of netqmail has been completely around the focus of security. To "
+"this end, e-mail is never sent to the user 'root'. So now you have to select "
+"a user on your machine to receive mail that would normally be destined for "
+"'root'. From now on in this guide, I will refer to that user as I have it in "
+"my setup, 'vapier'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):118
+msgid "Setting up non-root account for mail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):118
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /var/qmail/alias</i>\n"
+"# <i>echo vapier &gt; .qmail-root</i>\n"
+"# <i>echo vapier &gt; .qmail-postmaster</i>\n"
+"# <i>echo vapier &gt; .qmail-mailer-daemon</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):125
+msgid "Now we want to get the netqmail delivery service up and running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):129
+msgid "Start netqmail delivery service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):129
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add svscan default</i>\n"
+"# <i>/etc/init.d/svscan start</i>\n"
+"# <i>cd /service</i>\n"
+"# <i>ln -s /var/qmail/supervise/qmail-send qmail-send</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):136
+msgid ""
+"We want to make sure netqmail is working correctly, so here's a quick test."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):140
+msgid "Test delivery service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):140
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ssh vapier@localhost</i>\n"
+"# <i>maildirmake .maildir</i>\n"
+"# <i>qmail-inject root &lt;&lt; EOF\n"
+"test root e-mail!\n"
+"EOF</i>\n"
+"# <i>qmail-inject postmaster &lt;&lt; EOF\n"
+"test postmaster e-mail!\n"
+"EOF</i>\n"
+"# <i>qmail-inject vapier &lt;&lt; EOF\n"
+"test vapier e-mail!\n"
+"EOF</i>\n"
+"# <i>mutt</i>\n"
+"<comment>(You should now have 3 e-mails in your inbox)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):156
+msgid ""
+"And that's all! Now you have a mail system that will handle mail for your "
+"local machine and the system daemons/users who utilize it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(warn):161
+msgid ""
+"If you don't receive any mail or you see weird errors in the log files "
+"(check <path>/var/log/qmail/</path>) involving 'localhost.localhost', then "
+"that means your domain/dns information is not setup properly. By default, "
+"netqmail utilizes the output of <c>hostname --fqdn</c>. If, on your machine, "
+"this returns 'localhost', then check your <path>/etc/conf.d/hostname</path>, "
+"<path>/etc/hosts</path>, and your dns to make sure everything is correct. "
+"Once you have, edit the configuration files in <path>/var/qmail/control/</"
+"path>. Use the example setups that follow if you need some more help."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):172
+msgid "Example /var/qmail/control/ files for a 2nd level domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):172
+#, no-wrap
+msgid ""
+"\n"
+"# <i>hostname --fqdn</i>\n"
+"wh0rd.org\n"
+"# <i>cat me</i>\n"
+"wh0rd.org\n"
+"# <i>cat defaultdomain</i>\n"
+"wh0rd.org\n"
+"# <i>cat plusdomain</i>\n"
+"wh0rd.org\n"
+"# <i>cat locals</i>\n"
+"wh0rd.org\n"
+"# <i>cat rcpthosts</i>\n"
+"wh0rd.org\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):187
+msgid "Example /var/qmail/control/ files for a 3rd level domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):187
+#, no-wrap
+msgid ""
+"\n"
+"# <i>hostname --fqdn</i>\n"
+"mail.wh0rd.org\n"
+"# <i>cat me</i>\n"
+"mail.wh0rd.org\n"
+"# <i>cat defaultdomain</i>\n"
+"wh0rd.org\n"
+"# <i>cat plusdomain</i>\n"
+"wh0rd.org\n"
+"# <i>cat locals</i>\n"
+"mail.wh0rd.org\n"
+"# <i>cat rcpthosts</i>\n"
+"mail.wh0rd.org\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):207
+msgid "vpopmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):211
+msgid "Emerge vpopmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):211
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vpopmail</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):215
+msgid ""
+"This guide is designed around vpopmail-5.4.6 or later. Will it work with "
+"earlier versions? Maybe. Should you upgrade? Yes, if you want to be sure "
+"this guide will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):221
+msgid ""
+"vpopmail takes a little bit more effort to setup than the previous packages. "
+"Since vpopmail runs off of mysql, we'll have to make sure that it's up and "
+"running first. Then we can setup the vpopmail database and move on. Before "
+"you do this step, you should make sure you've already emerged and setup "
+"mysql properly. Note that the password I will use for the vpopmail database "
+"is 'vpoppw', you however should pick a different one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):230
+msgid "Setting up vpopmail in mysql"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):230
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add mysql default</i>\n"
+"<comment>If you just emerged mysql for the first time, make sure you run\n"
+"the <i>ebuild &lt;mysql.ebuild&gt; config</i> command and follow the\n"
+"directions before starting the mysql server.</comment>\n"
+"# <i>/etc/init.d/mysql start</i>\n"
+"# <i>nano /etc/vpopmail.conf</i>\n"
+"<comment>(Change the password from 'secret' to 'vpoppw')</comment>\n"
+"# <i>mysql -p &lt;&lt; EOF\n"
+"create database vpopmail;\n"
+"use mysql;\n"
+"grant select, insert, update, delete, create, drop on vpopmail.* to vpopmail@localhost identified by 'vpoppw';\n"
+"flush privileges;\n"
+"EOF</i>\n"
+"<comment>(The following steps may or may not be needed, but we run them just to be sure)</comment>\n"
+"# <i>chown root:vpopmail /etc/vpopmail.conf</i>\n"
+"# <i>chmod 640 /etc/vpopmail.conf</i>\n"
+"# <i>chown root:vpopmail /var/vpopmail/bin/vchkpw</i>\n"
+"# <i>chmod 4711 /var/vpopmail/bin/vchkpw</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(warn):251
+msgid ""
+"If you experience permission problems with mysql/vpopmail, you may want to "
+"try restarting mysql. Just run <c>/etc/init.d/mysql restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):256
+msgid ""
+"At this point in time, vpopmail is ready to roll. In this guide, we will be "
+"providing virtual hosting for the domain 'wh0rd.org'. This means we need to "
+"tell vpopmail about this domain we want it to host for us. We'll also "
+"quickly add an user account for 'vapier' while we're here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):263
+msgid "Adding a domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):263
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(You only have to do this if the <i>vadddomain</i> step below results in \"command not found\")</comment>\n"
+"# <i>source /etc/profile</i>\n"
+"\n"
+"<comment>(While debugging vpopmail, you may want to consult the logs)</comment>\n"
+"# <i>mysql -u vpopmail -p</i>\n"
+"mysql&gt; <i>select * from vpopmail.vlog;</i>\n"
+"\n"
+"# <i>vadddomain wh0rd.org postpass</i>\n"
+"<comment>(Now quickly verify the domain is setup properly)</comment>\n"
+"# <i>printf \"postmaster@wh0rd.org\\0postpass\\0blah\\0\" | vchkpw `which id` 3&lt;&amp;0</i>\n"
+"uid=89(vpopmail) gid=89(vpopmail) groups=0(root)\n"
+"<comment>(If you don't see something similar to above, then permissions somewhere are incorrect)</comment>\n"
+"# <i>vadduser vapier@wh0rd.org vappw</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):279
+msgid ""
+"Every domain that vpopmail creates comes with a 'postmaster' account. Here "
+"we told vpopmail that the password for the postmaster account is 'postpass'. "
+"Before vpopmail can be truly useful, we'll need to be able to receive mail "
+"via courier and send mail via netqmail and SMTP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):291
+msgid "Courier POP/IMAP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):295
+msgid "Emerge courier-imap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):295
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge net-mail/courier-imap</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):299
+msgid ""
+"You must emerge courier-imap after vpopmail. That way the authvchkpw module "
+"will be built."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):304
+msgid ""
+"This guide is designed around net-mail/courier-imap-3.0.7 or later. Will it "
+"work with earlier versions? Maybe. Should you upgrade? Yes, if you want to "
+"be sure this guide will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):310
+msgid ""
+"Now for the common post-install configuration steps. These steps are only "
+"needed if you wish to run SSL encrypted communications (which you should !). "
+"Otherwise you can skip to the last two steps in the two following code "
+"listings, removing the '-ssl' from the init script name each time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):317
+msgid "Out-of-the-box setup for POP3/SSL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):317
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/courier/authlib/authdaemonrc</i>\n"
+"<comment>(Set the authmodulelist variable to only contain \"authvchkpw\")</comment>\n"
+"# <i>cd /etc/courier-imap</i>\n"
+"# <i>nano pop3d.cnf</i>\n"
+"<comment>(Edit the [ req_dn ] section)</comment>\n"
+"# <i>mkpop3dcert</i>\n"
+"# <i>rc-update add courier-pop3d-ssl default</i>\n"
+"# <i>/etc/init.d/courier-pop3d-ssl start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):328
+msgid "Out-of-the-box setup for IMAP/SSL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):328
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/courier-imap</i>\n"
+"# <i>nano imapd.cnf</i>\n"
+"<comment>(Edit the [ req_dn ] section)</comment>\n"
+"# <i>mkimapdcert</i>\n"
+"# <i>rc-update add courier-imapd-ssl default</i>\n"
+"# <i>/etc/init.d/courier-imapd-ssl start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):337
+msgid ""
+"Your mail client should now be able to login to the host running courier and "
+"retrieve mail for the virtual host. In my case, I am now able to login with "
+"the username 'vapier@wh0rd.org' and password 'vappw'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):348
+msgid "netqmail (talking to the world)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):352
+msgid ""
+"Let's get SMTP up and running while making sure we don't create another spam "
+"hole for people to abuse."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):357
+msgid "Start netqmail SMTP service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):357
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /var/qmail/control/</i>\n"
+"# <i>nano conf-smtpd</i>\n"
+"<comment>(Uncomment the SMTP-AUTH variables and set QMAIL_SMTP_CHECKPASSWORD to /var/vpopmail/bin/vchkpw)</comment>\n"
+"# <i>nano servercert.cnf</i>\n"
+"<comment>(Edit the [ req_dn ] section)</comment>\n"
+"# <i>mkservercert</i>\n"
+"# <i>cd /service</i>\n"
+"# <i>ln -s /var/qmail/supervise/qmail-smtpd qmail-smtpd</i>\n"
+"# <i>/etc/init.d/svscan restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):369
+msgid ""
+"Assuming you haven't tweaked the netqmail control files at all, netqmail "
+"will now accept mail for the wh0rd.org virtual domain and for users of the "
+"local machine. Furthermore, netqmail will relay mail for anyone who sends "
+"via 127.0.0.1 and for anyone who is able to authenticate with vpopmail. When "
+"you setup your mail client to send mail, make sure you select options like "
+"'Server requires authentication'. In my case, I set the user as "
+"'vapier@wh0rd.org' and my password as 'vappw'. The last detail is to make "
+"sure you tell your mail client to use SSL/TLS for SMTP communication. "
+"netqmail will not let you authenticate if the session is not encrypted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):386
+msgid "Horde / IMP Webmail Client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):390
+msgid ""
+"Although there are plenty of webmail clients out there (and you're free to "
+"use any of them), I prefer the <uri link=\"http://www.horde.org/imp/\">IMP "
+"Webmail Client</uri> that is part of the Horde framework. The biggest reason "
+"is that Horde can simply provide Webmail access, or you can easily add other "
+"components to handle Address Books, Calendars, Tasks, etc... If this hasn't "
+"convinced you yet, then perhaps you need to read up on <uri link=\"http://"
+"www.horde.org/\">Horde</uri> for yourself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):400
+msgid "On to the good stuff! We need to emerge IMP now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):404
+msgid "Emerge IMP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):404
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge horde-imp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):408
+msgid ""
+"This guide is based around horde-2.2.x and horde-imp-3.2.x. The CVS versions "
+"(and thus the next major release) will probably have very different "
+"configuration settings. Also note that php-5.x will probably break horde-2.x."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):414
+msgid ""
+"Horde currently isn't the easiest to setup unless you know exactly what to "
+"do. Fortunately for you, I know exactly what to do, thus you will too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):419
+msgid "Out-of-the-box setup for Horde"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):419
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /var/www/localhost/htdocs/horde/config/</i>\n"
+"# <i>for f in *.dist ; do mv ${f} ${f/.dist} ; done</i>\n"
+"# <i>nano horde.php</i>\n"
+"<comment>(Under 'Horde Authentication':)</comment>\n"
+"$conf['auth']['driver'] = 'imap';\n"
+"$conf['auth']['params']['dsn'] = '{localhost:993/imap/ssl/novalidate-cert}';\n"
+"\n"
+"<comment>(Under 'Horde Logging':)</comment>\n"
+"$conf['log']['name'] = '/var/log/apache2/horde.log';\n"
+"\n"
+"<comment>(Under 'Problem Reporting':)</comment>\n"
+"$conf['problems']['enabled'] = true;\n"
+"$conf['problems']['email'] = 'webmaster@wh0rd.org';\n"
+"\n"
+"# <i>nano registry.php</i>\n"
+"<comment>(Under 'Handlers':)</comment>\n"
+"$this-&gt;registry['auth']['login'] = 'imp';\n"
+"$this-&gt;registry['auth']['logout'] = 'imp';\n"
+"\n"
+"<comment>(Under 'Application registry':)\n"
+"Set the 'status' element of applications['imp'] from 'inactive' to 'active'</comment>\n"
+"\n"
+"# <i>touch /var/log/apache2/horde.log</i>\n"
+"# <i>chown apache:apache /var/log/apache2/horde.log</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(note):446
+msgid ""
+"You'll may want to change the 'webmaster' e-mail account to something else. "
+"If you wish to use that e-mail address, then remember you'll have to add "
+"that user via vpopmail (or see below about qmailadmin)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):452
+msgid "Now we setup IMP real quick."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):456
+msgid "Out-of-the-box setup for IMP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):456
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /var/www/localhost/htdocs/horde/imp/config/</i>\n"
+"# <i>for f in *.dist ; do mv ${f} ${f/.dist} ; done</i>\n"
+"# <i>nano servers.php</i>\n"
+"\n"
+"<comment>(Edit the $servers['imap'] array:)</comment>\n"
+"$servers['imap'] = array(\n"
+"  'name' =&gt; 'wh0rd.org',\n"
+"  'server' =&gt; 'localhost',\n"
+"  'protocol' =&gt; 'imap/ssl/novalidate-cert',\n"
+"  'port' =&gt; 993,\n"
+"  'folders' =&gt; '',\n"
+"  'namespace' =&gt; 'INBOX.',\n"
+"  'maildomain' =&gt; 'wh0rd.org',\n"
+"  'smtphost' =&gt; 'localhost',\n"
+"  'realm' =&gt; '',\n"
+"  'preferred' =&gt; ''\n"
+");\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):476
+msgid "Finally, we bring up apache so we can start using webmail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):480
+msgid "Running apache"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):480
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/apache2</i>\n"
+"<comment>(Uncomment APACHE2_OPTS=\"-D SSL -D PHP5\")</comment>\n"
+"# <i>rc-update add apache2 default</i>\n"
+"# <i>/etc/init.d/apache2 start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(warn):487
+msgid ""
+"You should really look into forcing https on users of horde. This isn't a "
+"trivial issue, but you should look into it for the sake of security."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):492
+msgid ""
+"To test out the new IMP setup, launch a web browser and visit <uri>http://"
+"localhost/horde/</uri> (or change localhost with the server you're setting "
+"this up on). You should see the Horde welcome page where you can login. "
+"Again, in my setup, I simply login with 'vapier@wh0rd.org' and 'vappw' as my "
+"username and password."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):500
+msgid ""
+"At this point, Horde and IMP are all setup. You should, however, go back "
+"through the config directories and tweak each to your heart's content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):510
+msgid "Extra packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):512
+msgid "qmailadmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):515
+msgid ""
+"The first package I would suggest you look into is <uri link=\"http://www."
+"inter7.com/qmailadmin.html\">qmailadmin</uri>. It's a web based interface "
+"for managing virtual domains. Simply <c>emerge net-mail/qmailadmin</c> and "
+"then point your webbrowser to <uri>http://localhost/cgi-bin/qmailadmin</uri> "
+"in order to use it. Makes life a lot easier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):527
+msgid "qmHandle"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):530
+msgid ""
+"If you run into problems with netqmail queues and have a hard time debugging "
+"the situation, you may want to look into <uri link=\"http://qmhandle."
+"sourceforge.net/\">qmHandle</uri>. It's a simple perl program which allows "
+"you to view and manage the netqmail message queue. Again, all you need to do "
+"is <c>emerge net-mail/qmhandle</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):541
+msgid "horde add ons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):544
+msgid ""
+"I would highly recommend looking into the many other Horde applications. The "
+"<uri link=\"http://www.horde.org/turba/\">Turba</uri>, <uri link=\"http://"
+"www.horde.org/kronolith/\">Kronolith</uri>, and <uri link=\"http://www.horde."
+"org/nag/\">Nag</uri> applications complement IMP very well for instance. "
+"Their configuration is similar to that of IMP, so you should have no trouble "
+"setting them up. Just remember to edit registry.php in the horde config "
+"directory so the new applications show up at the bottom of the horde website."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):558
+msgid "ucspi-tcp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):561
+msgid ""
+"netqmail utilizes ucspi-tcp to handle the incoming connections for netqmail. "
+"If you wish to customize these filtering rules, then see the configuration "
+"files in <path>/etc/tcprules.d/</path> (older versions put files in <path>/"
+"etc</path>). There you'll find two files for each service, the configuration "
+"file (i.e. tcp.qmail-smtp) and the compiled version of this file that ucspi-"
+"tcp uses (i.e. tcp.qmail-smtp.cdb). Whenever you update the configuration "
+"file, you'll have to rebuild the binary version of it. Just run <c>tcprules "
+"tcp.qmail-smtp.cdb tcp.qmail-smtp.tmp &lt; tcp.qmail-smtp</c>. Every time a "
+"connection is made to the netqmail service, the compiled rules file is re-"
+"read, so there's no need to restart the service."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):577
+msgid "qmail-scanner"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):580
+msgid ""
+"If you wish to do content filtering on your mail server (spam and virus), "
+"then you'll need to use a different queuing program than the default one. "
+"One good program for doing so is <uri link=\"http://qmail-scanner."
+"sourceforge.net/\">qmail-scanner</uri>. Just <c>emerge qmail-scanner</c> and "
+"edit the <path>/etc/tcprules.d/tcp.qmail-smtp</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):589
+msgid ""
+"The build process of qmail-scanner is quite ugly. In order to support "
+"packages, they must already be on your system. This means you will have to "
+"emerge SpamAssassin and/or Clam AntiVirus before you emerge qmail-scanner. "
+"See the relevant following sections for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):596
+msgid "Changing the queuer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):596
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/tcprules.d/</i>\n"
+"# <i>nano tcp.qmail-smtp</i>\n"
+"<comment>(Add QMAILQUEUE=\"/var/qmail/bin/qmail-scanner-queue\" to the catchall allow rule)</comment>\n"
+"# <i>tcprules tcp.qmail-smtp.cdb tcp.qmail-smtp.tmp &lt; tcp.qmail-smtp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):603
+msgid ""
+"See the following sections for setting up spam and virus filtering. You may "
+"want to set a few custom options by editing <path>/var/qmail/bin/qmail-"
+"scanner-queue.pl</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):612
+msgid "SpamAssassin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):615
+msgid ""
+"One of the best Open Source spam filters out there is <uri link=\"http://www."
+"spamassassin.org/\">SpamAssassin</uri>. Just <c>emerge mail-filter/"
+"spamassassin</c> to install. The package comes in two flavors, a command "
+"line version and a client/server version. For servers that will be handling "
+"a small amount of mail, running with the command line version is OK, but for "
+"anyone whose server will be handling appreciative loads should utilize the "
+"client/server version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):625
+msgid "Out-of-the-box setup for SpamAssassin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):625
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/mail/spamassassin/local.cf</i>\n"
+"<comment>(At the bare minimum, add these options:)</comment>\n"
+"required_hits 6\n"
+"skip_rbl_checks 1\n"
+"\n"
+"# <i>rc-update add spamd default</i>\n"
+"# <i>/etc/init.d/spamd start</i>\n"
+"# <i>nano /var/qmail/bin/qmail-scanner-queue.pl</i>\n"
+"<comment>(Make sure the $spamc_binary variable is set to '/usr/bin/spamc'.)</comment>\n"
+"<comment>(If it is set to '', then see the note below.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):638
+msgid ""
+"If you did not have SpamAssassin on your system before you emerged qmail-"
+"scanner, you will have to re-emerge qmail-scanner now. Its build process is "
+"pretty ugly and will only add in features for packages it detects on the "
+"system at build time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):645
+msgid ""
+"At this point, incoming mail should be sent through qmail-scanner which will "
+"run it through SpamAssassin for you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):653
+msgid "Clam AntiVirus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):656
+msgid ""
+"Like SpamAssassin, <uri link=\"http://www.clamav.net/\">Clam AntiVirus</uri> "
+"comes in two flavors. I'll give you a quick run down on how to quickly setup "
+"the client/server version. First, just <c>emerge app-antivirus/clamav</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre:caption):662
+msgid "Out-of-the-box setup for Clam AntiVirus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(pre):662
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano /etc/conf.d/clamd</i>\n"
+"<comment>(Set START_CLAMD=yes)</comment>\n"
+"# <i>nano /etc/clamav.conf</i>\n"
+"<comment>(Setup stuff the way you want it)</comment>\n"
+"# <i>rc-update add clamd default</i>\n"
+"# <i>/etc/init.d/clamd start</i>\n"
+"# <i>nano /var/qmail/bin/qmail-scanner-queue.pl</i>\n"
+"<comment>(Make sure the $clamscan_binary variable is set to '/usr/bin/clamscan'.)</comment>\n"
+"<comment>(If it is set to '', then see the note below.)</comment>\n"
+"# <i>nano /var/qmail/control/conf-common</i>\n"
+"<comment>(If ClamAV reports memory problems try rasing the softlimit)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(impo):676
+msgid ""
+"If you did not have Clam AntiVirus on your system before you emerged qmail-"
+"scanner, you will have to re-emerge qmail-scanner now. Its build process is "
+"pretty ugly and will only add in features for packages it detects on the "
+"system at build time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):683
+msgid ""
+"At this point, incoming mail should be sent through qmail-scanner which will "
+"run it through Clam AntiVirus for you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(title):693
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(p):697
+msgid ""
+"I have no final notes other than if you experience any troubles with the "
+"guide, please contact <mail link=\"vapier@gentoo.org\">me</mail> or file a "
+"bug with <uri link=\"http://bugs.gentoo.org/\">Gentoo's Bugtracking Website</"
+"uri>. If you have some interesting bits you think would enhance this guide, "
+"by all means send it my way for inclusion. I love netqmail and would gladly "
+"add stuff that could possibly enhance a user's experience with the mta."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//qmail-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/quick-samba-howto.xml.po b/doc/gettext/ru/quick-samba-howto.xml.po
new file mode 100644
index 0000000..5f35a76
--- /dev/null
+++ b/doc/gettext/ru/quick-samba-howto.xml.po
@@ -0,0 +1,1264 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(guide:link):5
+msgid "/doc/en/quick-samba-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):7
+msgid "Gentoo Samba3/CUPS HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(author:title):9
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(author:title):12
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(author):9
+msgid "Andreas \"daff\" Ntaflos"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(mail:link):13
+msgid "joshua@sungentoo.homeunix.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(mail):13
+msgid "Joshua Preston"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(author:title):15
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(mail:link):16
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(mail):16
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(abstract):19
+msgid ""
+"Setup, install and configure a Samba server under Gentoo that shares files "
+"and printers without the need to install drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(version):28
+msgid "1.26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(date):29
+msgid "2009-01-25"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):32
+msgid "Introduction to this HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):34
+msgid "Purpose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):37
+msgid ""
+"This HOWTO is designed to help you move a network from many different "
+"clients speaking different languages, to many different machines that speak "
+"a common language. The ultimate goal is to help differing architectures and "
+"technologies, come together in a productive, happily coexisting environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):44
+msgid ""
+"Following the directions outlined in this HOWTO should give you an excellent "
+"step towards a peaceful cohabitation between Windows, and virtually all "
+"known variations of *nix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):50
+msgid ""
+"This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended "
+"to explore the functionality and power of the Gentoo system, portage and the "
+"flexibility of USE flags. Like so many other projects, it was quickly "
+"discovered what was missing in the Gentoo realm: there weren't any Samba "
+"HOWTOs catered for Gentoo users. These users are more demanding than most; "
+"they require performance, flexibility and customization. This does not "
+"however imply that this HOWTO was not intended for other distributions; "
+"rather that it was designed to work with a highly customized version of "
+"Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):61
+msgid ""
+"This HOWTO will describe how to share files and printers between Windows PCs "
+"and *nix PCs. It will also show you how to mount and manipulate shares."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):66
+msgid ""
+"There are a few topics that will be mentioned, but are out of the scope of "
+"this HOWTO. These will be noted as they are presented."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):71
+msgid ""
+"This HOWTO is based on a compilation and merge of an excellent HOWTO "
+"provided in the <uri link=\"http://forums.gentoo.org\">Gentoo forums</uri> "
+"by Andreas \"daff\" Ntaflos and the collected knowledge of Joshua Preston. "
+"The link to this discussion is provided below for your reference:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri:link):80
+msgid "http://forums.gentoo.org/viewtopic.php?t=110931"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):80
+msgid "HOWTO CUPS+Samba: printing from Windows &amp; Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):88
+msgid "Before you use this guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):91
+msgid ""
+"There are a several other guides for setting up CUPS and/or Samba, please "
+"read them as well, as they may tell you things left out of this HOWTO "
+"(intentional or otherwise). One such document is the very useful and well "
+"written <uri link=\"/doc/en/printing-howto.xml\">Gentoo Printing Guide</"
+"uri>, as configuration issues and specific printer setup is not discussed "
+"here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):102
+msgid "Brief Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):105
+msgid ""
+"After presenting the various USE flags, the following list will outline all "
+"of the topics covered as they are presented:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):113
+msgid "Install and configure Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):114
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):121
+msgid "Install and configure CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):115
+msgid "Adding the printer to CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):116
+msgid "Adding the PS drivers for the Windows clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):111
+msgid "On the Samba server: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):122
+msgid "Configuring a default printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):123
+msgid "Mounting a Windows or Samba share"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):119
+msgid "On the Unix clients: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):128
+msgid "Configuring the printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):129
+msgid "Accessing Samba shares"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):126
+msgid "On the Windows Clients: <placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):137
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):140
+msgid "We will need the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):145
+msgid "net-fs/samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):146
+msgid "net-print/cups (built with the <c>ppds</c> USE flag)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):147
+msgid "net-print/hplip (if you have an HP printer)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):148
+msgid "A kernel of sorts (2.6)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):149
+msgid "A printer (PS or non-PS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):150
+msgid ""
+"A working network (home/office/etc) consisting of more than one machine)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):155
+msgid ""
+"The main package we use here is <c>net-fs/samba</c>, however, you will need "
+"a kernel with CIFS support enabled in order to mount a Samba or Windows "
+"share from another computer. CUPS will be emerged if it is not already."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):166
+msgid "Getting acquainted with Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):168
+msgid "The USE Flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):171
+msgid ""
+"Before emerging anything, take a look at some of the various USE flags "
+"available to Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):176
+msgid "Samba uses the following USE Variables:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):176
+#, no-wrap
+msgid ""
+"\n"
+"kerberos acl cups ldap pam readline python winbind\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):180
+msgid ""
+"Depending on the network topology and the specific requirements of the "
+"server, the USE flags outlined below will define what to include or exclude "
+"from the emerging of Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(th):189
+msgid "Description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):193
+msgid ""
+"Include support for Kerberos. The server will need this if it is intended to "
+"join an existing domain or Active Directory. See the note below for more "
+"information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):201
+msgid ""
+"Enables Access Control Lists. The ACL support in Samba uses a patched ext2/"
+"ext3, or SGI's XFS in order to function properly as it extends more detailed "
+"access to files or directories; much more so than typical *nix GID/UID "
+"schemas."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):210
+msgid ""
+"This enables support for the Common Unix Printing System. This provides an "
+"interface allowing local CUPS printers to be shared to other systems in the "
+"network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):218
+msgid ""
+"Enables the Lightweight Directory Access Protocol (LDAP). If Samba is "
+"expected to use Active Directory, this option must be used. This would be "
+"used in the event Samba needs to login to or provide login to a Domain/"
+"Active Directory Server. The kerberos USE flag is needed for proper "
+"functioning of this option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):228
+msgid ""
+"Include support for pluggable authentication modules (PAM). This provides "
+"the ability to authenticate users on the Samba Server, which is required if "
+"users have to login to your server. The kerberos USE flag is recommended "
+"along with this option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):237
+msgid ""
+"Link Samba against libreadline. This is highly recommended and should "
+"probably not be disabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):244
+msgid ""
+"Python bindings API. Provides an API that will allow Python to interface "
+"with Samba."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(ti):251
+msgid ""
+"Winbind allows for a unified logon within a Samba environment. It uses a "
+"Unix implementation of Windows RPC calls, PAM and the name service switch "
+"(supported by the c library) to enable Windows NT domain users to appear and "
+"work as Unix users on a Unix system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):260
+msgid ""
+"A couple of things worth mentioning about the USE flags and different Samba "
+"functions include:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):266
+msgid ""
+"ACLs on ext2/3 are implemented through extended attributes (EAs). EA and ACL "
+"kernel options for ext2 and/or ext3 will need to be enabled (depending on "
+"which file system is being used - both can be enabled)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):275
+msgid "http://www.bluelightning.org/linux/samba_acl_howto/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):276
+msgid "http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):271
+msgid ""
+"While Active Directory, ACL, and PDC functions are out of the intended scope "
+"of this HOWTO, you may find these links as helpful to your cause: "
+"<placeholder-1/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):286
+msgid "Server Software Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):288
+msgid "Emerging Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):291
+msgid ""
+"First of all: be sure that all your hostnames resolve correctly. Either have "
+"a working domain name system running on your network or appropriate entries "
+"in your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if "
+"hostnames don't point to the correct machines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):298
+msgid ""
+"Hopefully now you can make an assessment of what you'll actually need in "
+"order to use Samba with your particular setup. The setup used for this HOWTO "
+"is:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):304
+msgid "cups"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):305
+msgid "readline"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):306
+msgid "pam"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):309
+msgid ""
+"To optimize performance, size and the time of the build, the USE flags are "
+"specifically included or excluded."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):314
+msgid ""
+"First, add <c>ppds</c> to your USE flags to make sure that when CUPS is "
+"built, it has proper foomatic support:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):319
+msgid "Adding ppds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):319
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"net-print/cups ppds\" &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):323
+msgid "Now, emerge Samba:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):327
+msgid "Emerge Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):327
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"net-fs/samba readline cups pam\" &gt;&gt; /etc/portage/package.use</i>\n"
+"# <i>emerge net-fs/samba</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):332
+msgid "This will emerge Samba and CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):339
+msgid "Emerging net-print/hplip"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):342
+msgid "You only need to emerge this if you use an HP printer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):346
+msgid "Emerge hplip"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):346
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge net-print/hplip</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):355
+msgid "Server Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):357
+msgid "Configuring Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):360
+msgid ""
+"The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is "
+"divided in sections indicated by [sectionname]. Comments are either # or ;. "
+"A sample <path>smb.conf</path> is included below with comments and "
+"suggestions for modifications. If more details are required, see the man "
+"page for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, "
+"the Samba Web site or any of the numerous Samba books available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):369
+msgid "A Sample /etc/samba/smb.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):369
+#, no-wrap
+msgid ""
+"\n"
+"[global]\n"
+"<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>\n"
+"workgroup = <comment>MYWORKGROUPNAME</comment>\n"
+"<comment># Of course this has no REAL purpose other than letting\n"
+"# everyone knows it's not Windows!\n"
+"# %v prints the version of Samba we are using.</comment>\n"
+"server string = Samba Server %v\n"
+"<comment># We are going to use cups, so we are going to put it in here ;-)</comment>\n"
+"printcap name = cups\n"
+"printing = cups\n"
+"load printers = yes\n"
+"<comment># We want a log file and we do not want it to get bigger than 50kb.</comment>\n"
+"log file = /var/log/samba/log.%m\n"
+"max log size = 50\n"
+"<comment># We are going to set some options for our interfaces...</comment>\n"
+"socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192\n"
+"<comment># This is a good idea, what we are doing is binding the\n"
+"# samba server to our local network.\n"
+"# For example, if eth0 is our local network device</comment>\n"
+"interfaces = lo <i>eth0</i>\n"
+"bind interfaces only = yes\n"
+"<comment># Now we are going to specify who we allow, we are afterall\n"
+"# very security conscience, since this configuration does\n"
+"# not use passwords!</comment>\n"
+"hosts allow = 127.0.0.1 <i>192.168.1.0/24</i>\n"
+"hosts deny = 0.0.0.0/0\n"
+"<comment># Other options for this are USER, DOMAIN, ADS, and SERVER\n"
+"# The default is user</comment>\n"
+"security = share\n"
+"<comment># No passwords, so we're going to use a guest account!</comment>\n"
+"guest ok = yes\n"
+"\n"
+"<comment># Now we setup our print drivers information!</comment>\n"
+"[print$]\n"
+"comment = Printer Drivers\n"
+"path = /etc/samba/printer <comment># this path holds the driver structure</comment>\n"
+"guest ok = yes\n"
+"browseable = yes\n"
+"read only = yes\n"
+"<comment># Modify this to \"username,root\" if you don't want root to\n"
+"# be the only printer admin)</comment>\n"
+"write list = <i>root</i>\n"
+"\n"
+"<comment># Now we'll setup a printer to share, while the name is arbitrary\n"
+"# it should be consistent throughout Samba and CUPS!</comment>\n"
+"[HPDeskJet930C]\n"
+"comment = HP DeskJet 930C Network Printer\n"
+"printable = yes\n"
+"path = /var/spool/samba\n"
+"public = yes\n"
+"guest ok = yes\n"
+"<comment># Modify this to \"username,root\" if you don't want root to\n"
+"# be the only printer admin)</comment>\n"
+"printer admin = <i>root</i>\n"
+"\n"
+"<comment># Now we setup our printers share. This should be\n"
+"# browseable, printable, public.</comment>\n"
+"[printers]\n"
+"comment = All Printers\n"
+"browseable = no\n"
+"printable = yes\n"
+"writable = no\n"
+"public = yes\n"
+"guest ok = yes\n"
+"path = /var/spool/samba\n"
+"<comment># Modify this to \"username,root\" if you don't want root to\n"
+"# be the only printer admin)</comment>\n"
+"printer admin = <i>root</i>\n"
+"\n"
+"<comment># We create a new share that we can read/write to from anywhere\n"
+"# This is kind of like a public temp share, anyone can do what\n"
+"# they want here.</comment>\n"
+"[public]\n"
+"comment = Public Files\n"
+"browseable = yes\n"
+"public = yes\n"
+"create mode = 0766\n"
+"guest ok = yes\n"
+"path = /home/samba/public\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(warn):451
+msgid ""
+"If you like to use Samba's guest account to do anything concerning printing "
+"from Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</"
+"c> section. The guest account seems to cause problems when running "
+"<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. "
+"See below, too, when we talk about <c>cupsaddsmb</c> and the problems that "
+"can arise. Use a dedicated printer user, like <c>printeruser</c> or "
+"<c>printer</c> or <c>printme</c> or whatever. It doesn't hurt and it will "
+"certainly protect you from a lot of problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):462
+msgid ""
+"Now create the directories required for the minimum configuration of Samba "
+"to share the installed printer throughout the network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):467
+msgid "Create the directories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):467
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /etc/samba/printer</i>\n"
+"# <i>mkdir /var/spool/samba</i>\n"
+"# <i>mkdir /home/samba/public</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):473
+msgid ""
+"At least one Samba user is required in order to install the printer drivers "
+"and to allow users to connect to the printer. Users must exist in the "
+"system's <path>/etc/passwd</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):479
+msgid "Creating the users"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):479
+#, no-wrap
+msgid ""
+"\n"
+"# <i>smbpasswd -a root</i>\n"
+"\n"
+"<comment>(If another user is to be a printer admin)</comment>\n"
+"# <i>smbpasswd -a username</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):486
+msgid ""
+"The Samba passwords need not be the same as the system passwords in <path>/"
+"etc/passwd</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):491
+msgid ""
+"You will also need to update <path>/etc/nsswitch.conf</path> so that Windows "
+"systems can be found easily using NetBIOS:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):496
+msgid "Editing /etc/nsswitch.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):496
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/nsswitch.conf</i>\n"
+"<comment>(Edit the hosts: line)</comment>\n"
+"hosts: files dns <i>wins</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):505
+msgid "Configuring CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):508
+msgid ""
+"This is a little more complicated. CUPS' main config file is <path>/etc/cups/"
+"cupsd.conf</path>. It's structure is similar to Apache's <path>httpd.conf</"
+"path> file, so many you may find it familiar. Outlined in the example are "
+"the directives that need to be changed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):515
+msgid "/etc/cups/cupsd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):515
+#, no-wrap
+msgid ""
+"\n"
+"ServerName <i>PrintServer</i>          <comment># your printserver name</comment>\n"
+"ServerAdmin <i>root@PrintServer</i>    <comment># the person for printer-related hate-mail, e.g. you</comment>\n"
+"\n"
+"AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>\n"
+"ErrorLog  /var/log/cups/error_log  <comment># doesn't really need changing either</comment>\n"
+"\n"
+"LogLevel  debug <comment># only while installing and testing, should later be\n"
+"                # changed to 'info'</comment>\n"
+"\n"
+"MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,\n"
+"               # there seemed to be a bug in CUPS' controlling of the web interface,\n"
+"               # making CUPS think a denial of service attack was in progress when\n"
+"               # I tried to configure a printer with the web interface. weird.</comment>\n"
+"\n"
+"BrowseAddress @IF(<i>eth0</i>) <comment># Change this to your internal net interface</comment>\n"
+"\n"
+"&lt;Location /&gt;\n"
+"Order Deny,Allow\n"
+"Deny From All\n"
+"Allow From <i>192.168.1.*</i>  <comment># the addresses of your internel network\n"
+"                        # e.g. 192.168.1.* will allow connections from any host on\n"
+"                        # the 192.168.1.0 network. change to whatever suits you</comment>\n"
+"&lt;/Location&gt;\n"
+"\n"
+"&lt;Location /admin&gt;\n"
+"AuthType Basic\n"
+"AuthClass System\n"
+"Allow From <i>192.168.1.*</i>  <comment># same as above, allow any host on the\n"
+"                        # 192.168.1.0 network to connect and do\n"
+"                        # administrative tasks after authenticating</comment>\n"
+"Order Deny,Allow\n"
+"Deny From All\n"
+"&lt;/Location&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):551
+msgid ""
+"Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. The changes "
+"to <path>mime.convs</path> and <path>mime.types</path> are needed to make "
+"CUPS print Microsoft Office document files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):557
+msgid "/etc/cups/mime.convs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):557
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(The following line is found near the end of the file. Uncomment it)</comment>\n"
+"application/octet-stream        application/vnd.cups-raw        0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):562
+msgid "Edit <path>/etc/cups/mime.types</path> to uncomment some lines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):566
+msgid "/etc/cups/mime.types"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):566
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(The following line is found near the end of the file. Uncomment it)</comment>\n"
+"application/octet-stream\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):571
+msgid "CUPS needs to be started on boot, and started immediately."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):575
+msgid "Setting up the CUPS service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):575
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(To start CUPS on boot)</comment>\n"
+"# <i>rc-update add cupsd default</i>\n"
+"<comment>(To start or restart CUPS now)</comment>\n"
+"# <i>/etc/init.d/cupsd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):585
+msgid "Installing a printer for and with CUPS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):588
+msgid ""
+"First, go to <uri link=\"http://linuxprinting.org\">LinuxPrinting.Org</uri> "
+"to find and download the correct PPD file for your printer and CUPS. To do "
+"so, click the link Printer Listings to the left. Select your printers "
+"manufacturer and the model in the pulldown menu, e.g. HP and DeskJet 930C. "
+"Click \"Show\". On the page coming up click the \"recommended driver\" link "
+"after reading the various notes and information. Then fetch the PPD file "
+"from the next page, again after reading the notes and introductions there. "
+"You may have to select your printers manufacturer and model again. Reading "
+"the <uri link=\"http://www.linuxprinting.org/cups-doc.html\">CUPS quickstart "
+"guide</uri> is also very helpful when working with CUPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):601
+msgid ""
+"Now you have a PPD file for your printer to work with CUPS. Place it in "
+"<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was "
+"named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the "
+"printer. This can be done via the CUPS web interface or via command line. "
+"The web interface is found at <path>http://PrintServer:631</path> once CUPS "
+"is running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):609
+msgid "Install the printer via command line"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):609
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>\n"
+"# <i>/etc/init.d/cupsd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):614
+msgid ""
+"Remember to adjust to what you have. Be sure to have the name (<c>-p</c> "
+"argument) right (the name you set above during the Samba configuration!) and "
+"to put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or "
+"whatever device you are using for your printer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):621
+msgid ""
+"You should now be able to access the printer from the web interface and be "
+"able to print a test page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):629
+msgid "Installing the Windows printer drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):632
+msgid ""
+"Now that the printer should be working it is time to install the drivers for "
+"the Windows clients to work. Samba 2.2 introduced this functionality. "
+"Browsing to the print server in the Network Neighbourhood, right-clicking on "
+"the printershare and selecting \"connect\" downloads the appropriate drivers "
+"automagically to the connecting client, avoiding the hassle of manually "
+"installing printer drivers locally."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):641
+msgid ""
+"There are two sets of printer drivers for this. First, the Adobe PS drivers "
+"which can be obtained from <uri link=\"http://www.adobe.com/support/"
+"downloads/main.html\">Adobe</uri> (PostScript printer drivers). Second, "
+"there are the CUPS PS drivers, to be obtained by emerging <c>net-print/cups-"
+"windows</c>. Note that it may still be marked ~arch, so you may need to add "
+"it to <path>/etc/portage/package.keywords</path>. There doesn't seem to be a "
+"difference between the functionality of the two, but the Adobe PS drivers "
+"need to be extracted on a Windows System since it's a Windows binary. Also "
+"the whole procedure of finding and copying the correct files is a bit more "
+"hassle. The CUPS drivers support some options the Adobe drivers don't."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):655
+msgid "This HOWTO uses the CUPS drivers for Windows. Install them as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):659
+msgid "Install the drivers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):659
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av cups-windows</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):663
+msgid ""
+"Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS "
+"distribution. Be sure to read its manpage (<c>man cupsaddsmb</c>), as it "
+"will tell you which Windows drivers you'll need to copy to the proper CUPS "
+"directory. Once you've copied the drivers, restart CUPS by running <c>/etc/"
+"init.d/cupsd restart</c>. Next, run <c>cupsaddsmb</c> as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):671
+msgid "Run cupsaddsmb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):671
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>\n"
+"<comment>(Instead of HPDeskJet930C you could also specify \"-a\", which will\n"
+"\"export all known printers\".)</comment>\n"
+"# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(warn):678
+msgid ""
+"The execution of this command often causes the most trouble. Read through "
+"the <uri link=\"http://forums.gentoo.org/viewtopic.php?t=110931\">posts in "
+"this thread</uri> for some troubleshooting tips."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):684
+msgid "Here are common errors that may happen:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):689
+msgid ""
+"The hostname given as a parameter for <c>-h</c> and <c>-H</c> "
+"(<c>PrintServer</c>) often does not resolve correctly and doesn't identify "
+"the print server for CUPS/Samba interaction. If an error like: <b>Warning: "
+"No PPD file for printer \"CUPS_PRINTER_NAME\" - skipping!</b> occurs, the "
+"first thing you should do is substitute <c>PrintServer</c> with "
+"<c>localhost</c> and try it again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):697
+msgid ""
+"The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message "
+"is quite common, but can be triggered by many problems. It's unfortunately "
+"not very helpful. One thing to try is to temporarily set <c>security = user</"
+"c> in your <path>smb.conf</path>. After/if the installation completes "
+"successfully, you should set it back to share, or whatever it was set to "
+"before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):707
+msgid ""
+"This should install the correct driver directory structure under <path>/etc/"
+"samba/printer</path>. That would be <path>/etc/samba/printer/W32X86/2/</"
+"path>. The files contained should be the 3 driver files and the PPD file, "
+"renamed to <path>YourPrinterName.ppd</path> (the name which you gave the "
+"printer when installing it (see above)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):715
+msgid ""
+"Pending no errors or other complications, your drivers are now installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):722
+msgid "Finalizing our setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):725
+msgid "Lastly, setup our directories."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):729
+msgid "Final changes needed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):729
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /home/samba</i>\n"
+"# <i>mkdir /home/samba/public</i>\n"
+"# <i>chmod 755 /home/samba</i>\n"
+"# <i>chmod 755 /home/samba/public</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):739
+msgid "Testing our Samba configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):742
+msgid ""
+"We will want to test our configuration file to ensure that it is formatted "
+"properly and all of our options have at least the correct syntax. To do this "
+"we run <c>testparm</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):748
+msgid "Running the testparm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):748
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(By default, testparm checks /etc/samba/smb.conf)</comment>\n"
+"# <i>/usr/bin/testparm</i>\n"
+"Load smb config files from /etc/samba/smb.conf\n"
+"Processing section \"[printers]\"\n"
+"Global parameter guest account found in service section!\n"
+"Processing section \"[public]\"\n"
+"Global parameter guest account found in service section!\n"
+"Loaded services file OK.\n"
+"Server role: ROLE_STANDALONE\n"
+"Press enter to see a dump of your service definitions\n"
+" ...\n"
+" ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):766
+msgid "Starting the Samba service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):769
+msgid "Now configure Samba to start at bootup; then go ahead and start it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):773
+msgid "Setting up the Samba service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):773
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add samba default</i>\n"
+"# <i>/etc/init.d/samba start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):781
+msgid "Checking our services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):784
+msgid ""
+"It would probably be prudent to check our logs at this time also. We will "
+"also want to take a peak at our Samba shares using <c>smbclient</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):789
+msgid "Checking the shares with smbclient"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):789
+#, no-wrap
+msgid ""
+"\n"
+"# <i>smbclient -L localhost</i>\n"
+"Password:\n"
+"<comment>(You should see a BIG list of services here.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):800
+msgid "Configuration of the Clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):802
+msgid "Printer configuration of *nix based clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):805
+msgid ""
+"Despite the variation or distribution, the only thing needed is CUPS. Do the "
+"equivalent on any other UNIX/Linux/BSD client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):810
+msgid "Configuring a Gentoo system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):810
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge cups</i>\n"
+"# <i>nano -w /etc/cups/client.conf</i>\n"
+"ServerName <i>PrintServer</i>      <comment># your printserver name</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):816
+msgid "That should be it. Nothing else will be needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):820
+msgid ""
+"If you use only one printer, it will be your default printer. If your print "
+"server manages several printers, your administrator will have defined a "
+"default printer on the server. If you want to define a different default "
+"printer for yourself, use the <c>lpoptions</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):827
+msgid "Setting your default printer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):827
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(List available printers)</comment>\n"
+"# <i>lpstat -a</i>\n"
+"<comment>(Sample output, yours will differ)</comment>\n"
+"HPDeskJet930C accepting requests since Jan 01 00:00\n"
+"laser accepting requests since Jan 01 00:00\n"
+"<comment>(Define HPDeskJet930C as your default printer)</comment>\n"
+"# <i>lpoptions -d HPDeskJet930C</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):837
+msgid "Printing in *nix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):837
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Specify the printer to be used)</comment>\n"
+"# <i>lp -d HPDeskJet930C anything.txt</i>\n"
+"<comment>(Use your default printer)</comment>\n"
+"# <i>lp foobar.whatever.ps</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):844
+msgid ""
+"Just point your web browser to <c>http://printserver:631</c> on the client "
+"if you want to manage your printers and their jobs with a nice web "
+"interface. Replace <c>printserver</c> with the name of the <e>machine</e> "
+"that acts as your print server, not the name you gave to the cups print "
+"server if you used different names."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):855
+msgid "Mounting a Windows or Samba share in GNU/Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(note):858
+msgid ""
+"Don't forget to install <c>net-fs/mount-cifs</c> or <c>net-fs/samba</c> on "
+"the client(s) that will be accessing the shares."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):863
+msgid ""
+"Now is time to configure our kernel to support CIFS. Since I'm assuming "
+"we've all compiled at least one kernel, we'll need to make sure we have all "
+"the right options selected in our kernel. For simplicity's sake, make it a "
+"module for ease of use. It is the author's opinion that kernel modules are a "
+"good thing and should be used whenever possible."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):871
+msgid "Kernel support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):871
+#, no-wrap
+msgid ""
+"\n"
+"CONFIG_CIFS=m\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):875
+msgid "Then make the module/install it; insert it with:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):879
+msgid "Loading the kernel module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):879
+#, no-wrap
+msgid ""
+"\n"
+"# <i>modprobe cifs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):883
+msgid ""
+"Once the module is loaded, mounting a Windows or Samba share is possible. "
+"Use <c>mount</c> to accomplish this, as detailed below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre:caption):888
+msgid "Mounting a Windows/Samba share"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(pre):888
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(The syntax for mounting a Windows/Samba share is:\n"
+"  mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point\n"
+"If we are not using passwords or a password is not needed)</comment>\n"
+"\n"
+"# <i>mount -t cifs //PrintServer/public /mnt/public</i>\n"
+"\n"
+"<comment>(If a password is needed)</comment>\n"
+"# <i>mount -t cifs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):899
+msgid ""
+"After you mount the share, you would access it as if it were a local drive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):906
+msgid "Printer Configuration for Windows NT/2000/XP clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):909
+msgid ""
+"That's just a bit of point-and-click. Browse to <path>\\\\PrintServer</path> "
+"and right click on the printer (HPDeskJet930C) and click connect. This will "
+"download the drivers to the Windows client and now every application (such "
+"as Word or Acrobat) will offer HPDeskJet930C as an available printer to "
+"print to. :-)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):921
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):923
+msgid "A Fond Farewell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):926
+msgid ""
+"That should be it. You should now have a successful printing enviroment that "
+"is friendly to both Windows and *nix as well as a working share!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):936
+msgid "Links and Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):938
+msgid "Links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):941
+msgid ""
+"These are some links that may help you in setting up, configuration and "
+"troubleshooting your installation:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri:link):947
+msgid "http://www.cups.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):947
+msgid "CUPS Homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):948
+msgid ""
+"<uri link=\"http://www.samba.org/\">Samba Homepage</uri>, especially the "
+"<uri link=\"http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-"
+"printing.html\">chapter on Samba/CUPS configuration</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri:link):953
+msgid "http://linuxprinting.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):953
+msgid "LinuxPrinting dot Org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(li):954
+msgid ""
+"<uri link=\"http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/\">Kurt "
+"Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e> "
+"and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and "
+"Samba, and generally printing support on networks. A really interesting "
+"read, with lots and lots of details.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri:link):961
+msgid "http://www.freebsddiary.org/cups.php"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(uri):961
+msgid "FreeBSD Diary's CUPS Topic"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(title):967
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(p):970
+msgid ""
+"See <uri link=\"http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-"
+"HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37\">this page</uri> "
+"from Kurt Pfeifle's \"Printing Support in Samba 3.0\" manual. Lots of useful "
+"tips there! Be sure to look this one up first, before posting questions and "
+"problems! Maybe the solution you're looking for is right there."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//quick-samba-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/rsync.xml.po b/doc/gettext/ru/rsync.xml.po
new file mode 100644
index 0000000..8b305d8
--- /dev/null
+++ b/doc/gettext/ru/rsync.xml.po
@@ -0,0 +1,626 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(guide:link):5
+msgid "/doc/en/rsync.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):6
+msgid "Gentoo Linux rsync Mirrors Policy and Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail:link):9
+msgid "mirror-admin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail):9
+msgid "Gentoo Mirror Administrators"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail:link):12
+msgid "klausman-gentoo@schwarzvogel.de"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail):12
+msgid "Tobias Klausmann"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail:link):15
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(mail):15
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(abstract):18
+msgid ""
+"This document explains how to set up a official rsync mirror and your own "
+"local mirror."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(version):27
+msgid "3.9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(date):28
+msgid "2010-06-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):31
+msgid "Preliminaries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):33
+msgid "Terms, names and all that"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):36
+msgid ""
+"This guide is intended for people who would like to set up an rsync mirror "
+"of their own. It caters not only to those who want to run an official rsync "
+"mirror but also those wanting to run private mirrors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):42
+msgid ""
+"There are three kinds of Gentoo rsync mirrors: main rotation mirrors, "
+"community mirrors and private mirrors. Main rotation mirrors are maintained "
+"by the Gentoo infrastructure team. They handle the bulk of the Gentoo rsync "
+"traffic. The community mirrors are run by volunteers from the Gentoo "
+"community. Private mirrors are mirrors run by individuals which are closed "
+"off to the public and meant to cut traffic costs and latency for an "
+"organization or individual."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):51
+msgid ""
+"At this time, we have enough community mirrors and are actively seeking "
+"additional main rotation mirrors. Hardware specifications for main rotation "
+"servers include:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):58
+msgid ""
+"Minimum of a 2GHz Pentium 4 processor (64-bit with at least 2 cores "
+"preferred)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):59
+msgid "Minimum of 2GB RAM (3GB - 4GB is ideal)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):60
+msgid "15GB of disk space (IDE/SATA is fine)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):63
+msgid ""
+"You would maintain physical possession ownership of the hardware, and keep "
+"it online in your own colocation space. Average bandwidth consumption for "
+"each main rotation mirror is currently ~10Mbit/sec (around 2.6 TiB per "
+"month). As the number of main rotation mirrors increases, this number should "
+"decrease accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):71
+msgid ""
+"If you would like to donate your machine, please email the <mail link="
+"\"mirror-admin@gentoo.org\">Mirror Admins</mail> with the pertinent "
+"information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):82
+msgid "Setting up your own local rsync mirror"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):84
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):240
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):87
+msgid ""
+"Many users run Gentoo on several machines and need to sync the portage trees "
+"on all of them. Using public mirrors is simply a waste of bandwidth at both "
+"ends. Syncing only one machine against a public mirror and all others "
+"against that computer would save resources on Gentoo mirrors and save users' "
+"bandwidth."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):94
+msgid ""
+"The same holds true for organizations who would like to control the rsync "
+"mirror their servers and workstations sync against. Of course, they usually "
+"also want to save on bandwidth and traffic costs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):100
+msgid ""
+"All you need to do is select which machine is going to be your own local "
+"rsync mirror and set it up. You should choose a computer that can handle the "
+"CPU and disk load that an rsync operation requires. Your local mirror also "
+"needs to be available whenever any of your other computers syncs its portage "
+"tree. Besides, it should have a static IP address or a name that always "
+"resolves to your server. Configuring a DHCP and/or a DNS server is beyond "
+"the scope of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):110
+msgid ""
+"Note that these instructions assume your private rsync mirror is a Gentoo "
+"machine. If you intend to run it on a different distribution, the guide for "
+"setting up a community mirror might be more helpful. Just don't sync the "
+"mirror every half hour but once or twice a day."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):120
+msgid "Setting up the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):123
+msgid ""
+"There is no extra package to install as the required software is already on "
+"your computer. Setting up your own local rsync mirror is just a matter of "
+"configuring the <c>rsyncd</c> daemon to make your <path>/usr/portage</path> "
+"directory available for syncing. Create the following <path>/etc/rsyncd."
+"conf</path> configuration file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):131
+msgid "Sample /etc/rsyncd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):131
+#, no-wrap
+msgid ""
+"\n"
+"pid file = /var/run/rsyncd.pid\n"
+"max connections = 5\n"
+"use chroot = yes\n"
+"uid = nobody\n"
+"gid = nobody\n"
+"<comment># Optional: restrict access to your Gentoo boxes</comment>\n"
+"hosts allow = 192.168.0.1 192.168.0.2 192.168.1.0/24\n"
+"hosts deny  = *\n"
+"\n"
+"[gentoo-portage]\n"
+"path=/usr/portage\n"
+"comment=Gentoo Portage\n"
+"exclude=distfiles/ packages/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):147
+msgid ""
+"You do not need to use the <c>hosts allow</c> and <c>hosts deny</c> options. "
+"By default, all clients will be allowed to connect. The order in which you "
+"write the options is not relevant. The server will always check the <c>hosts "
+"allow</c> option first and grant the connection if the connecting host "
+"matches any of the listed patterns. The server will then check the <c>hosts "
+"deny</c> option and refuse the connection if any match is found. Any host "
+"that does not match anything will be granted a connection. Please read the "
+"man page (<c>man rsyncd.conf</c>) for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):158
+msgid ""
+"Now, start your rsync daemon with the following command as the root user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):162
+msgid "Starting the rsync daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):162
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Start the daemon now)</comment>\n"
+"# <i>/etc/init.d/rsyncd start</i>\n"
+"<comment>(Add the daemon to your default runlevel)</comment>\n"
+"# <i>rc-update add rsyncd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):169
+msgid ""
+"Let's test your rsync mirror. You do not need to try from another machine "
+"but it would be a good idea to do so. If your server is not known by name "
+"from all your computers, you can use its IP address instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):175
+msgid "Testing your mirror"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):175
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(You may use the server name or its IP)</comment>\n"
+"# <i>rsync 192.168.0.1::</i>\n"
+"gentoo-portage     Gentoo Portage\n"
+"# <i>rsync your_server_name::gentoo-portage</i>\n"
+"<comment>(You should see the content of /usr/portage on your mirror)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):183
+msgid ""
+"Your rsync mirror is now set up. Keep running <c>emerge --sync</c> as you "
+"have done so far to keep your server up-to-date. If you use cron or similar "
+"facilities to sync regularly, remember to keep it down to a sensible "
+"frequency like once or twice a day."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(note):190
+msgid ""
+"Please note that most public mirror administrators consider syncing more "
+"than once or twice a day an abuse. Some if not most of them will ban your IP "
+"from their server if you start abusing their machines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):199
+msgid "Configuring your clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):202
+msgid ""
+"Now, make your other computers use your own local rsync mirror instead of a "
+"public one. Edit your <path>/etc/make.conf</path> and make the <c>SYNC</c> "
+"variable point to your server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):208
+msgid "Define SYNC in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):208
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Use your server IP address)</comment>\n"
+"SYNC=\"rsync://<i>192.168.0.1</i>/gentoo-portage\"\n"
+"<comment>(Or use your server name)</comment>\n"
+"SYNC=\"rsync://<i>your_server_name</i>/gentoo-portage\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):215
+msgid ""
+"You can check that your computer has been properly set up by syncing against "
+"your own local mirror for the first time:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):220
+msgid "Checking and syncing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):220
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Check that the SYNC variable has been setup)</comment>\n"
+"# <i>emerge --info|grep SYNC</i>\n"
+"SYNC=\"rsync://your_server_name/gentoo-portage\"\n"
+"<comment>(Sync against your local mirror)</comment>\n"
+"# <i>emerge --sync</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):228
+msgid ""
+"That's it! All your computers will now use your local rsync mirror whenever "
+"you run <c>emerge --sync</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):238
+msgid "Setting up a community rsync server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(note):243
+msgid ""
+"You can find sample configuration and script files in the gentoo-rsync-"
+"mirror package. Just do <c>emerge gentoo-rsync-mirror</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):248
+msgid ""
+"Right now, mirroring our Portage tree requires around 600Mb, so it isn't "
+"space intensive; having at least 1Gb free should allow for growing room. "
+"Setting up a Portage tree mirror is simple -- first, ensure that your mirror "
+"has rsync installed. Then, set up your <path>rsyncd.conf</path> file to look "
+"something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):256
+msgid "rsyncd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):256
+#, no-wrap
+msgid ""
+"\n"
+"uid = nobody\n"
+"gid = nobody\n"
+"use chroot = yes\n"
+"max connections = 15\n"
+"pid file = /var/run/rsyncd.pid\n"
+"motd file = /etc/rsync/rsyncd.motd\n"
+"log file = /var/log/rsync.log\n"
+"transfer logging = yes\n"
+"log format = %t %a %m %f %b\n"
+"syslog facility = local3\n"
+"timeout = 300\n"
+"\n"
+"[gentoo-portage]\n"
+"#modern versions of portage use this entry\n"
+"path = /gentoo/rsync\n"
+"comment = Gentoo Linux Portage tree mirror\n"
+"exclude = distfiles\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):276
+msgid ""
+"You can pick your own locations for most of the files, of course. What's "
+"important is the section name (<c>[gentoo-portage]</c>). This is the "
+"location that rsync clients will try to sync from."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):282
+msgid ""
+"For security reasons, the use of a chrooted environment is required! This "
+"has implications for the logged timestamps -- see the FAQ below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):287
+msgid ""
+"Now, you need to mirror the Gentoo Linux Portage tree. You can use the "
+"script below to do so. Again, you'll probably want to change some of the "
+"file locations to suit your needs -- in particular, they should match those "
+"of your <path>rsyncd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):294
+msgid "rsync-gentoo-portage.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):294
+#, no-wrap
+msgid ""
+"\n"
+"#!/bin/bash\n"
+"\n"
+"RSYNC=\"/usr/bin/rsync\"\n"
+"OPTS=\"--quiet --recursive --links --perms --times -D --delete --timeout=300\"\n"
+"#Uncomment the following line only if you have been granted access to masterportage.gentoo.org\n"
+"#SRC=\"rsync://masterportage.gentoo.org/gentoo-portage\"\n"
+"#If you are waiting for access to our master mirror, select one of our mirrors to mirror from:\n"
+"SRC=\"rsync://rsync.de.gentoo.org/gentoo-portage\"\n"
+"DST=\"/space/gentoo/rsync/\"\n"
+"\n"
+"echo \"Started update at\" `date` &gt;&gt; $0.log 2&gt;&amp;1\n"
+"logger -t rsync \"re-rsyncing the gentoo-portage tree\"\n"
+"${RSYNC} ${OPTS} ${SRC} ${DST} &gt;&gt; $0.log 2&gt;&amp;1\n"
+"\n"
+"echo \"End: \"`date` &gt;&gt; $0.log 2&gt;&amp;1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):312
+msgid ""
+"Your <path>rsyncd.motd</path> should contain your IP address and other "
+"relevant information about your mirror, such as information about the host "
+"providing the Portage mirror and an administrative contact. You can now test "
+"your server as outlined in the <uri link=\"#local\">Setting up your own "
+"local rsync mirror</uri> chapter above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):320
+msgid ""
+"After you have been approved as an official rsync mirror, your host will be "
+"aliased with a name of the form: <path>rsync[num].[country code].gentoo.org</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):331
+msgid "Short FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):333
+msgid "Q: Who should I contact regarding rsync issues and maintenance?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):336
+msgid ""
+"A: Visit <uri link=\"http://bugs.gentoo.org\">Gentoo Bugzilla</uri> and fill "
+"out a bug on the product \"Mirrors\", component \"Server Problem\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):345
+msgid "Q: How can I check the freshness of an official rsync server?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):348
+msgid ""
+"The Gentoo infrastructure team monitors all community rsync servers for "
+"freshness. You can see the results on the <uri link=\"http://mirrorstats."
+"gentoo.org/rsync\">corresponding web page</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):357
+msgid ""
+"Q: I run a private rsync mirror for my company. Can I still access "
+"masterportage.gentoo.org?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):362
+msgid ""
+"A: Because our resources are limited, we need to ensure we allocate them in "
+"such a way as to provide the maximum amount of benefit to our users. As "
+"such, we limit connections to our master rsync and distfile mirrors to "
+"public mirrors only. Users are welcome to use our regular mirror system to "
+"establish a private rsync mirror, though they are asked to follow certain "
+"basic <uri link=\"/news/en/gwn/20030505-newsletter."
+"xml#doc_chap1_sect3\">rsync etiquette guidelines</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):375
+msgid "Q: Is it important that I sync my mirror twice an hour?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):378
+msgid ""
+"A: Yes it is important. You do not need to perform the syncs at exactly :00 "
+"and :30 but the syncs should take place in each of the following two windows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):384
+msgid ":00 to :10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):385
+msgid ":30 to :40"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):388
+msgid ""
+"Additionally, please make sure that your syncs are exactly 30 minutes apart. "
+"So, if you schedule the first sync of each hour for :08, please schedule the "
+"second sync of the hour for :38."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):397
+msgid ""
+"Q: Where should I sync my rsync mirror before I become an official Gentoo "
+"mirror?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):401
+msgid "For European-based rsync mirror: sync to rsync.de.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):402
+msgid "For US-based rsync mirror: sync to rsync.us.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(li):403
+msgid "For all others: sync to rsync.us.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):410
+msgid "Q: How do I find the mirror nearest to me?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):413
+msgid ""
+"A: <c>netselect</c> was designed to do this for you. If you haven't already "
+"run <c>emerge netselect</c> then do it. Then run: <c>netselect rsync.gentoo."
+"org</c>. After a minute or so netselect will print an IP address. Take this "
+"address and use it as the only parameter for rsync with two colons appended "
+"to it. e.g.: <c>rsync 1.2.3.4::</c>. You should be able to find out which "
+"mirror that is from the banner message. Update your <path>/etc/make.conf</"
+"path> accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):426
+msgid "Q: Can I use compression when syncing against masterportage.gentoo.org?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):429
+msgid ""
+"A: No. Compression utilizes too many resources on the server, so we have "
+"forcibly disabled it on <path>masterportage.gentoo.org</path>. Please <e>do "
+"not</e> attempt to use compression when syncing against this server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):438
+msgid ""
+"Q: I'm seeing a lot of old and probably dead rsync processes, how can I get "
+"rid of them?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):442
+msgid ""
+"This command will help you to kill old rsync processes that sometimes lie "
+"around due to connection problems. It's important to kill those because they "
+"count as valid connections for the 'max connections' option. You may run "
+"this command via crontab every hour, it will search and kill rsync processes "
+"older than one hour."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):450
+msgid "Kill old rsync processes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):450
+#, no-wrap
+msgid ""
+"\n"
+"/bin/kill -9 `/bin/ps --no-headers -Crsync -o etime,user,pid,command|/bin/grep nobody | \\\n"
+"             /bin/grep \"[0-9]\\{2\\}:[0-9]\\{2\\}:\" |/bin/awk '{print $3}'`\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(title):458
+msgid ""
+"Q: There are many users who connect to my rsync server very frequently, "
+"sometimes even causing a DoS to my mirror, is there any way to prevent this?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):463
+msgid ""
+"In some cases, there are a few inconsiderate users who abuse the rsync "
+"mirror system by syncing more than 1-2 times per day. In the most extreme "
+"cases, users schedule cron jobs to sync every 15 minutes or so. This often "
+"leads to a Denial of Service attack by continually occupying an rsync slot "
+"that could have otherwise gone to another user. To try and prevent this, you "
+"may use the <uri link=\"/proj/en/infrastructure/mirrors/rsyncd.conf_pl.txt"
+"\">this perl script</uri> which will scan your rsync log files, pick out IP "
+"addresses that have already connected more than <c>N</c> times that day and "
+"dynamically create a <path>rsyncd.conf</path> file, including the offending "
+"IP addresses in the 'hosts deny' directive. The following line controls what "
+"<c>N</c> equals (in this case 4):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre:caption):477
+msgid "Define maximum number of connections per IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(pre):477
+#, no-wrap
+msgid ""
+"\n"
+"@badhosts=grep {$hash{$_}&gt;4} keys %hash;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(p):481
+msgid ""
+"If you use this script, please remember to rotate your rsync log files daily "
+"and modify the script to match the location of your <path>rsyncd.conf</path> "
+"file. This script is tested on Gentoo Linux, but should work suitably on "
+"other arches that support both rsync and perl."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//rsync.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/shoutcast-config.xml.po b/doc/gettext/ru/shoutcast-config.xml.po
new file mode 100644
index 0000000..f9a0e71
--- /dev/null
+++ b/doc/gettext/ru/shoutcast-config.xml.po
@@ -0,0 +1,1453 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):5
+msgid "Streaming Radio With SHOUTcast"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(mail:link):8
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(mail):8
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(author:title):10
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(mail:link):11
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(mail):11
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(abstract):14
+msgid ""
+"This guide will walk through the steps needed to setup a streaming radio "
+"server with SHOUTcast Server and SHOUTcast Trans."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(version):23
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(date):24
+msgid "2006-11-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):27
+msgid "Setting up SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):29
+msgid "Installing the files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):32
+msgid ""
+"The SHOUTcast Server can be found in media-sound/SHOUTcast-server-bin. You "
+"can install it with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):37
+msgid "Emerging SHOUTcast"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):37
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge shoutcast-server-bin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):41
+msgid ""
+"The SHOUTcast Server will now be installed. The next step is configuring "
+"your new SHOUTcast Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):49
+msgid "Configuring SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):52
+msgid ""
+"Now that SHOUTcast Server is installed, it must be configured. The "
+"configuration file can be found in <path>/etc/shoutcast/sc_serv.conf</path>. "
+"Let's begin with the configuration. Make sure you are root, and open the "
+"configuration file with your favorite editor. I choose vi for this example. "
+"Now I'll bring up the file with vi:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):60
+msgid "Opening the configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):60
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vi /etc/shoutcast/sc_serv.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):64
+msgid ""
+"This will bring up the SHOUTcast Server configuration file for viewing. From "
+"there you will see the configuration file and the different options that you "
+"can set. Let's take a look on how to setup these particular options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):73
+msgid "Mandatory Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):76
+msgid "Setting the user limit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):76
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; MaxUser.  The maximum number of simultaneous listeners allowed.\n"
+"; Compute a reasonable value for your available upstream bandwidth (i.e. if\n"
+"; you have 256kbps upload DSL, and want to broadcast at 24kbps, you would\n"
+"; choose 256kbps/24kbps=10 maximum listeners.)  Setting this value higher\n"
+"; only wastes RAM and screws up your broadcast when more people connect\n"
+"; than you can support.</comment>\n"
+"MaxUser=10\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):86
+msgid ""
+"This is where the maximum number of users is set. As the caption states, it "
+"is foolish to setup 100 users on a 256kbps upload (This is what I have set, "
+"as my upload is about that). If you're running SHOUTcast Server to serve a "
+"LAN, you can probably set this MUCH higher (to the 100 mentioned easily). "
+"Please remember to not abuse whatever bandwidth you are using though. "
+"Bandwidth comes at quite a high price to ISPs and some will cut your "
+"account, fine you high costs to makeup, or both."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):96
+msgid "Setting the password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):96
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Password.  While SHOUTcast never asks a listener for a password, a\n"
+"; password is required to broadcast through the server, and to perform\n"
+"; administration via the web interface to this server.  This server should\n"
+"; consist of only letters and numbers, and is the same server your broadcaster\n"
+"; will need to enter in the SHOUTcast Source Plug-in for Winamp.  THIS VALUE\n"
+"; CANNOT BE BLANK.</comment>\n"
+"Password=a_hard_to_crack_password\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):106
+msgid ""
+"Here is where you setup the password. The password itself is clear text. For "
+"security purposes, I STRONGLY recommend that you don't use passwords that "
+"are used to access critical system components or other sensitive "
+"information. Make this as random as possible, with a combination of letters "
+"and numbers. This password will be what SHOUTcast Trans (or any other "
+"content provider) will use to connect and provide streaming content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):115
+msgid "Setting up your listening port"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):115
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; PortBase. This is the port number your server will run on.  The\n"
+"; value, and the value + 1 must be available.  If you get a fatal error when\n"
+"; the DNAS is setting up a socket on startup, make sure nothing else on the\n"
+"; machine is running on the same port (telnet localhost port number -- if you\n"
+"; get connection refused then you're clear to use that port).  Ports less than 1024\n"
+"; may require root privileges on *nix machines.  The default port is 8000.</comment>\n"
+"PortBase=8000\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):125
+msgid ""
+"This value sets up what port users will connect to on your SHOUTcast Server. "
+"The default is 8000, as it is what most mp3 server capable programs will "
+"default to (Audacious, winamp, etc.). As it states, if you wish to use a "
+"port less than 1024, you will need to be root. However, I strongly urge "
+"against using any port lower than 1024 for your SHOUTcast Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):133
+msgid "Setting up logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):133
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; LogFile: file to use for logging. Can be '/dev/null' or 'none'\n"
+"; or empty to turn off logging. The default is ./sc_serv.log\n"
+"; on *nix systems or sc_serv_dir\\sc_serv.log on win32.\n"
+"; Note: on win32 systems if no path is specified the location is\n"
+"; in the same directory as the executable, on *nix systems it is in the\n"
+"; current directory.</comment>\n"
+"LogFile=/var/log/SHOUTcast.log\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):143
+msgid ""
+"This sets the location of the SHOUTcast server log file. The ebuild has it "
+"set to /dev/null, so you will need to change it in order to get a real log. "
+"I have it setup in the basic /var/log location. You can have it log to "
+"wherever you need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):150
+msgid "Enabling real time stats"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):150
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; RealTime displays a status line that is updated every second\n"
+"; with the latest information on the current stream (*nix and win32\n"
+"; console systems only)</comment>\n"
+"RealTime=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):157
+msgid ""
+"This displays information on the current song to stdout every second. This "
+"is disabled by the ebuild so that the SHOUTcast daemon can run as silently "
+"as possible. Set this to 1 if you want these updates each second. However, I "
+"recommend you use the status page instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):164
+msgid "Enabling real time logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):164
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; ScreenLog controls whether logging is printed to the screen or not\n"
+"; on *nix and win32 console systems. It is useful to disable this when\n"
+"; running servers in background without their own terminals. Default is 1</comment>\n"
+"ScreenLog=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):171
+msgid ""
+"This is disabled by default in the ebuild to make the daemon run as silently "
+"as possible. This will log any events (connects, disconnects, etc) to stdout "
+"as they happen in real time. However, because the log file does the same "
+"thing, I recommend using it instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):178
+msgid "Setting the last number of songs displayed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):178
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; ShowLastSongs specifies how many songs to list in the /played.html\n"
+"; page.  The default is 10.  Acceptable entries are 1 to 20.</comment>\n"
+"ShowLastSongs=10\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):184
+msgid ""
+"Just as it states, this value will set how many of the most recently played /"
+"played.html will display. If you put more than 20, you should probably "
+"consider more coffee."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):190
+msgid "Setting up filesystem modification logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):198
+msgid ""
+"This setting enables or disables logging for directory modifications by the "
+"DNAS (Distributed Network Audio Server), or SHOUTcast for short. Recommended "
+"for those who wish to have the most secure logging possible. Basic home/"
+"casual users probably don't need this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):205
+msgid "Enabling http request logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):217
+msgid ""
+"This specifies whether or not you want to log hits to the HTTP server that "
+"SHOUTcast provides. Once again, recommended for those who wish the most "
+"secure logging possible, but not recommended for home/casual users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):223
+msgid "Enabling W3C Logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):223
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; W3CEnable turns on W3C Logging.  W3C logs contain httpd-like accounts\n"
+"; of every track played for every listener, including byte counts those listeners\n"
+"; took.  This data can be parsed with tools like Analog and WebTrends, or given\n"
+"; to third parties like Arbitron and Measurecast for their reporting systems.\n"
+"; Default is Yes (enabled).</comment>\n"
+"W3CEnable=Yes\n"
+"\n"
+"<comment>; W3CLog describes the name of the log file for W3C logging.  Default log file is\n"
+"; sc_w3c.log, in the same directory wherever the DNAS gets started from.</comment>\n"
+"W3CLog=/dev/null\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):236
+msgid ""
+"The first option enables W3C logging. This type of logging can be easily "
+"parsed by the programs listed. This is highly recommended for those who wish "
+"to have the most in depth statistics possible. The second option specifies "
+"where to store the W3C log. This is set to /dev/null by the ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):246
+msgid "Network Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):249
+msgid "Setting the source IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):249
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; SrcIP, the interface to listen for source connections on (or to make relay\n"
+"; connections on if relaying). Can and usually will be ANY or 127.0.0.1\n"
+"; (Making it 127.0.0.1 will keep other machines from being able to\n"
+"; broadcast using your SHOUTcast Server )</comment>\n"
+"SrcIP=ANY\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):257
+msgid ""
+"The SrcIP variable sets what IP streaming content is coming from. This can "
+"be another server (relaying), localhost (regular), or any other IP that your "
+"interface supports. Setting to localhost prevents any other server from "
+"using your SHOUTcast Server as a broadcast source. The default is ANY and "
+"will cause your SHOUTcast Server to source from any IP. Security wise, it is "
+"better to set this to something specific."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):266
+msgid "Setting the destination IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):266
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; DestIP, IP to listen for clients on (and to contact yp.SHOUTcast.com)\n"
+"; can and usually will be be ANY. If your machine has multiple IP addresses,\n"
+"; set this to the one you want it to be accessed by.</comment>\n"
+"DestIP=ANY\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):273
+msgid ""
+"This determines which IP on your interface you will allow users to connect "
+"to. This can be localhost (if you're anti-social and wish only to stream to "
+"yourself), a private IP (for instance, 192.168.0.101, for hosting to a local "
+"network), or your external IP (for instance, 209.204.249.201, for streaming "
+"to a WAN, but not a LAN). In most cases, you can reach your own stream by "
+"using 127.0.0.1 instead of what is listed here. ANY lets your SHOUTcast "
+"Server bind to all IP addresses on all available interfaces."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):283
+msgid "Setting proxy/yp.SHOUTcast.com port"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):283
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Yport, port to connect to yp.SHOUTcast.com on. For people behind caching\n"
+"; web proxies, change this to the alternate port (666 is what it might be,\n"
+"; check www.SHOUTcast.com if you have problems). Otherwise, leave this at 80.\n"
+"; We're actively working on re-opening port 666, but as of release the only\n"
+"; working port is port 80.</comment>\n"
+"Yport=80\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):292
+msgid ""
+"This has 2 functions. First is the port to connect to yp.SHOUTcast.com with. "
+"yp.SHOUTcast.com is nullsoft's page for public servers so users know where "
+"to listen in on. Users can search for your station from this page. The "
+"secondary use is for web proxies. Set this to the port you use for proxy "
+"connects, and set DestIP to your proxy for streaming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):300
+msgid "Setting up reverse DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):300
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; NameLookups.  Specify 1 to perform reverse DNS on connections.\n"
+"; This option may increase the time it takes to connect to your\n"
+"; server if your DNS server is slow.  Default is 0 (off).</comment>\n"
+"NameLookups=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):307
+msgid ""
+"This option specifies whether or not you want to perform reverse DNS lookups "
+"on clients. This would take an IP address and try to find out the "
+"corresponding host name. Use this for logging purposes to create a more "
+"detailed report."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):313
+msgid "Setting up relaying"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):322
+msgid ""
+"This specifies that you are acting as a relay server. Relay servers are "
+"often used to take a low bandwidth connection that can only stream to one "
+"client, and use its own higher bandwidth to serve to more clients. RelayPort "
+"specifies the port and IP address of the SHOUTcast Server you wish to relay "
+"for. Comment this out if you don't plan on using your server as a relay."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):333
+msgid "Server Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):336
+msgid "Setting the admin password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):348
+msgid ""
+"Setting this will create a broadcaster and administrator. The broadcaster "
+"can log in with Password, and view connections. However, should the person "
+"want to kick/ban/administer the server, they must have the Admin password. "
+"This option creates more specific roles for your server. This is recommended "
+"for instances where the system administrator is not the same person as the "
+"broadcaster."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):357
+msgid "Setting up auto user disconnect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):357
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; AutoDumpUsers controls whether listeners are disconnected if the source\n"
+"; stream disconnects. The default is 0.</comment>\n"
+"AutoDumpUsers=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):363
+msgid ""
+"This specifies whether or not users are kicked out if the stream disconnects "
+"for any reason. This is set to 0, so that clients will either timeout "
+"themselves, or keep trying to buffer a stream. Use this if you expect short "
+"interruptions at any time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):370
+msgid "Setting up the source timeout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):370
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; AutoDumpSourceTime specifies how long, in seconds, the source stream is\n"
+"; allowed to be idle before the server disconnects it. 0 will let the source\n"
+"; stream idle indefinitely before disconnecting. The default is 30.</comment>\n"
+"AutoDumpSourceTime=30\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):377
+msgid ""
+"This specifies when the SHOUTcast Server should give up waiting for a source "
+"(mainly a relay server) to stream content from. Anywhere from 30 to 60 "
+"should be a reasonable value for this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):383
+msgid "Setting up the content directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):383
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; ContentDir specifies the directory location on disk of where to stream\n"
+"; on-demand content from. Subdirectories are supported as of DNAS 1.8.2.\n"
+"; Default is ./content/, meaning a directory named content in the same directory\n"
+"; as where sc_serv was invoked from.</comment>\n"
+"ContentDir=/opt/SHOUTcast/content/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):391
+msgid ""
+"The ContentDir specifies where to put on demand content. For example, if you "
+"wish to stream an announcement to employees, you could use this for that "
+"purpose. The SHOUTcast Server ebuild sets this to <path>/opt/SHOUTcast/"
+"content</path> for you. To use this, put an mp3 in the content directory, "
+"then point your browser to <c>http://example.com:[port]/content/mp3name.pls</"
+"c>. SHOUTcast Server will automatically create a streaming media compatible "
+"play list for the mp3, and stream it on demand. Use this as an alternative "
+"to SHOUTcast Trans for streaming media source."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):403
+msgid "Setting up an intro file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):414
+msgid ""
+"This allows you to configure an intro file. Every time users connect, "
+"they'll hear this file played. As it states, the stream bit rate and the "
+"intro song bit rate must match, or else things will break. You can, however, "
+"put something such as intro128.mp3 and intro64.mp3, and it will play "
+"intro128.mp3 to users connecting to a 128kbps stream, and intro64.mp3 for "
+"users connecting at 64kbps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):423
+msgid "Setting up a back file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):436
+msgid ""
+"This is the same as above, but will be played when the stream source ends, "
+"instead of when users disconnect. This will only work if AutoDumpUsers is "
+"set to 0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):442
+msgid "Setting up a title format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):442
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; TitleFormat specifies a format string for what title is sent to the listener.\n"
+"; For example, a string of 'Justin Radio' forces the title 'Justin Radio' even\n"
+"; when the source changes the title. You can use up to one '%s' in the string\n"
+"; which lets you contain the title from the source. For example, if your\n"
+"; TitleFormat is 'Justin Radio: %s', and the source plug-in's title is\n"
+"; 'Billy plays the blues', then the net title is\n"
+"; 'Justin Radio: Billy plays the blues'. Note: only works on non-relay servers.\n"
+"; The default is no format string.</comment>\n"
+"TitleFormat=Chris Gentoo Beats: %s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):454
+msgid ""
+"This sets up a non-variable title for your SHOUTcast server. Use this if "
+"your source stream differs from your SHOUTcast Server's name. This will NOT "
+"work with relay servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):460
+msgid "Setting up a URL format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):467
+msgid ""
+"This is the same as TitleFormat except that the URL listed above is used "
+"instead of the source stream's URL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):472
+msgid "Setting up the public status of a source stream"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):472
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; PublicServer can be always, never, or default (the default, heh)\n"
+"; Any setting other than default will override the public status\n"
+"; of the source plug-in or of a SHOUTcast Server that is being relayed.</comment>\n"
+"PublicServer=default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):479
+msgid ""
+"This specifies whether or not you want to be listed as a public server even "
+"if your relay server/source plug-in is listed as such."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):484
+msgid "Allowing relaying"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):484
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; AllowRelay determines whether or not other SHOUTcast Servers will be\n"
+"; permitted to relay this server.  The default is Yes.</comment>\n"
+"AllowRelay=Yes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):490
+msgid ""
+"AllowRelay determines if other servers are allowed to relay your content. If "
+"you don't think you'll ever relay at all, set this to No."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):495
+msgid "Allowing relays to publically display the source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):495
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; AllowPublicRelay, when set to No, will tell any relaying servers not\n"
+"; to list the server in the SHOUTcast directory (non-public), provided\n"
+"; the relaying server's Public flag is set to default.  The default is\n"
+"; Yes.</comment>\n"
+"AllowPublicRelay=Yes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):503
+msgid ""
+"AllowPublicRelay specifies whether or not you wish to be listed in the "
+"SHOUTcastpublic directory if the server you're relaying to is already "
+"listed. Note that PublicServer can override this setting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):509
+msgid "Setting MetaInterval"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):509
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; MetaInterval specifies how often, in bytes, meta data sent.\n"
+"; You should really leave this at the default of 32768, but the option is\n"
+"; provided anyway.</comment>\n"
+"MetaInterval=32768\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):516
+msgid "Just leave this as is."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):523
+msgid "Access Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):526
+msgid "Setting the max listener time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):534
+msgid ""
+"I'm not to sure why you'd need this one. Basically, if a user is on for too "
+"many minutes, disconnect them. Only thing I can think of is to kick idlers "
+"off, or people you think should be doing other things than listening to your "
+"stream. Value is measured in minutes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):541
+msgid "Setting up the ban file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):549
+msgid ""
+"This is the filename for the list of clients that are banned from your "
+"server. The default is sc_serv.ban, but you can use whatever name you so "
+"desire with this setting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):555
+msgid "Setting the Rip list"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):567
+msgid ""
+"As grim as it sounds, Rip actually stands for \"Reserved IP\". Use this for "
+"your friends or other people you consider more important than random users. "
+"If you are currently streaming to the max number of users possible, and one "
+"of your rip members tries to get on, it will kick the longest listening "
+"person from the server to get them on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):575
+msgid "Setup if Rip only users can access your server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):585
+msgid ""
+"This allows for only Rip members to connect to your SHOUTcast Server. You "
+"can either use this for private radio streams, or to make it so that only "
+"certain relays will be able to access your stream."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):594
+msgid "Mass Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):597
+msgid "Setting Unique variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):612
+msgid ""
+"Basically, if you're running lots of SHOUTcast Servers, it would be a dire "
+"pain to change all the log/ban/etc. files to something unique for every "
+"configuration. Instead, you can set Unique to something, and $ will be "
+"replaced with whatever Unique is set to. For example, if one file had "
+"Unique=Jazz and another had Unique=Rock, then Log=/var/log/$.log would "
+"produce /var/log/Jazz.log on one configuration file and /var/log/Rock.log on "
+"another configuration file. Much easier when dealing with multiple SHOUTcast "
+"Servers on similar configurations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):623
+msgid "Setting up common configure variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):636
+msgid ""
+"If you're running multiple SHOUTcast Servers and wish to utilize similar "
+"configuration variables without setting them all for each configuration "
+"file, you can set this to point to a file that contains settings that are "
+"similar between multiple configurations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):646
+msgid "Optimization Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):649
+msgid "Setup number of CPU's utilized"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):662
+msgid ""
+"On multiple CPU systems, use this setting to force the SHOUTcast Server to "
+"utilize CpuCount # of processors. The default to assign one thread to each "
+"processor, and have listeners across all the threads. If you set this lower "
+"than your total processor count, this will leave processors free to do other "
+"things."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):670
+msgid "Setup data submission gap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):686
+msgid ""
+"The SHOUTcast Server will use the sleep value in determining the gap between "
+"sending data. The higher the value, the longer the gap, the lower the value, "
+"the shorter the gap and the more CPU usage SHOUTcast Server will take up. On "
+"slower systems, as it states, you might want to lower this so that the "
+"SHOUTcast Servers sends data more and more frequently to users. Best to "
+"leave as is."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):695
+msgid "Setup XML output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):702
+msgid ""
+"Probably don't need to worry about this setting to much unless you use "
+"custom XML parsers to create custom statistics for you server. If the XML "
+"parser cannot handle whitespace and line feeds in XML, set this to Yes, and "
+"all should work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):712
+msgid "Configuration Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):715
+msgid ""
+"Your SHOUTcast Server should now be configured. For businesses that are "
+"using SHOUTcast, I recommend turning on WC3 logging, as it can be easily "
+"parsed, and used for creating custom statistics. You should also enable the "
+"AdministratorPassword. You might also wish to enable some of the mass "
+"configuration options if you're creating multiple SHOUTcast Servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):723
+msgid ""
+"With the configuration setup, we'll now work on getting SHOUTcast up and "
+"running. We'll start with simple on demand streaming for a simple startup, "
+"then work on SHOUTcast Trans later (as it is somewhat more involved)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):734
+msgid "Getting started with SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):736
+msgid "Setting up on demand streaming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):739
+msgid ""
+"On demand streaming, as shown in the configuration chapter, automatically "
+"sets up on demand play lists for mp3 files in the content directory. The "
+"SHOUTcast server ebuild has a directory setup in /opt/SHOUTcast/content for "
+"all your on demand mp3's. Let's get started by creating a simple on demand "
+"streaming mp3."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):746
+msgid ""
+"First we'll need to get an mp3 from somewhere and put it in the content "
+"directory. We'll take this sample.mp3 file from an /Mp3 directory I have "
+"created."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):752
+msgid "Copying an mp3 to the content directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):752
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp sample.mp3 /opt/SHOUTcast/content/</i>\n"
+"# <i>cd /opt/SHOUTcast/content/</i>\n"
+"# <i>ls</i>\n"
+"sample.mp3\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):759
+msgid ""
+"OK, so the file is copied over now. Now we'll need to startup our SHOUTcast "
+"Server so the file can be accessed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):764
+msgid "Starting up the SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):764
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/shoutcast start</i>\n"
+" * Starting Shoutcast Server...\n"
+"*******************************************************************************\n"
+"** SHOUTcast Distributed Network Audio Server\n"
+"** Copyright (C) 1998-2004 Nullsoft, Inc.  All Rights Reserved.\n"
+"** Use \"sc_serv filename.ini\" to specify an ini file.\n"
+"*******************************************************************************\n"
+"                                                                         [ ok ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):775
+msgid ""
+"The little banner is there to make sure that nothing dies right away (i.e. "
+"so you know your server actually started). Your SHOUTcast Server is now "
+"started! Because of the nature of on demand content, you will ONLY be able "
+"to access it from a browser. MPlayer or anything else won't be able to "
+"stream it as is. I use kmplayer in order to access the stream directly from "
+"my browser. You can see the result on the next image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(figure:caption):785
+msgid "On Demand Content"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(figure:short):785
+msgid "OnDemandContent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(figure:link):785
+msgid "/images/docs/shoutcast-OnDemandContent.jpg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):787
+msgid ""
+"Some people have Audacious setup to handle their audio mime types, so your "
+"browser may spawn Audacious up in order to play the resulting streaming "
+"content. Now that you are able to work with on demand content, we'll now "
+"work on using SHOUTcast Trans to create a true streaming radio server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):799
+msgid "Setting up SHOUTcast Trans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):801
+msgid "SHOUTcast Trans introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):804
+msgid ""
+"SHOUTcast Trans stands for SHOUTcast Trans(coder), as it is able to "
+"transcode mp3's to lower or higher bit rates. SHOUTcast Trans works by "
+"streaming mp3's from a play list specified in the configuration file. We'll "
+"begin to setup the configuration for SHOUTcast Trans, so that we can have a "
+"real to goodness streaming radio station. We'll begin by opening the "
+"configuration file for SHOUTcast Trans, which just so happens to be located "
+"in /etc/shoutcast/sc_trans.conf."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):814
+msgid "Opening the SHOUTcast Trans configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):814
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(First install SHOUTcast Trans)</comment>\n"
+"# <i>emerge shoutcast-trans-bin</i>\n"
+"<comment>(Next open the SHOUTcast Trans configuration file)</comment>\n"
+"# <i>vi /etc/shoutcast/sc_trans.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):821
+msgid ""
+"Now that we have the SHOUTcast Trans configuration file open, we'll begin to "
+"setup the streaming source."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):829
+msgid "Configuring SHOUTcast Trans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):832
+msgid "Setting up the playlist"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):832
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; PlaylistFile (required EVEN IF RELAYING) - play list file (to create, use\n"
+"; find /path/to/mp3/directory -type f -name \"*.mp3\" &gt; playlist_filename.lst</comment>\n"
+"PlaylistFile=/opt/SHOUTcast/playlists/playlist.lst\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):838
+msgid ""
+"This setting tells SHOUTcast where to find its streaming media content from. "
+"This setting requires an existing file, so let's go ahead and create a play "
+"list. I'll create one real quick from my /Mp3 directory referred to earlier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):845
+msgid "Creating the playlist"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):845
+#, no-wrap
+msgid ""
+"\n"
+"# <i>find /Mp3 -type f -name \"*.mp3\" &gt; /opt/SHOUTcast/playlists/playlist.lst</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):849
+msgid ""
+"Now that the play list is setup, we point the configuration file to it, and "
+"SHOUTcast Trans will now know what files to stream."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):854
+msgid "Setting the server IP and port"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):854
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Serverip/ServerPort are the target server to send to</comment>\n"
+"Serverip=127.0.0.1\n"
+"ServerPort=8000\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):860
+msgid ""
+"This setting decides where to send the streaming content. In this guide, it "
+"will be the SHOUTcast Server's IP and port that you setup previously (DestIP "
+"and PortBase)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):866
+msgid "Setting the SHOUTcast Server password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):866
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Password is the password on the sc_serv you're sending to.</comment>\n"
+"Password=password_you_setup_in_sc_serv.conf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):871
+msgid ""
+"The is the same password that you setup in the SHOUTcast Server "
+"configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):875
+msgid "Setting up your stream information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):875
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; StreamTitle/URL/Genre define the data that appears on the directory and in the\n"
+"; stream info.</comment>\n"
+"StreamTitle=Chris Gentoo Beats\n"
+"StreamURL=http://www.gentoo.org\n"
+"Genre=JPOP Electronica And More!\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):883
+msgid ""
+"This sets up the title of your stream (i.e. Radio One), the URL (i.e. http://"
+"www.radio-one.com), and the Genre (i.e. Electronica Trance Tribal)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):888
+msgid "Setting up your logfile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):888
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Logfile optionally denotes a text file to log sc_Trans to.  a kill -HUP\n"
+"; will force a close and re-open of this file (but will also cease logging to\n"
+"; the console)</comment>\n"
+"LogFile=/var/log/sc_Trans.log\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):895
+msgid ""
+"This will point to the log file for SHOUTcast Trans. All your logging goes "
+"here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):900
+msgid "Setting up shuffling"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):900
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Shuffle the play list</comment>\n"
+"Shuffle=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):905
+msgid ""
+"Decide on whether or not you want your play list to play random songs from "
+"your list each time. Most will set this to 1. If you're going to be "
+"accepting song requests, set this to 0 and I'll explain how to do that later "
+"on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):911
+msgid "Setting up the stream"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):911
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Bitrate/SampleRate/Channels recommended values:\n"
+"; 8kbps 8000/11025/1\n"
+"; 16kbps 16000/11025/1\n"
+"; 24kbps 24000/22050/1\n"
+"; 32kbps 32000/22050/1\n"
+"; 64kbps mono 64000/44100/1\n"
+"; 64kbps stereo 64000/22050/2\n"
+"; 96kbps stereo 96000/44100/2\n"
+"; 128kbps stereo 128000/44100/2</comment>\n"
+"Bitrate=128000\n"
+"SampleRate=44100\n"
+"Channels=2\n"
+"<comment>; Quality is from 1-10. 1 is best, 10 is fastest.</comment>\n"
+"Quality=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):928
+msgid ""
+"Bitrate sets up the bit rate for your stream. This can be from 8000 (8kbps) "
+"to 128000 (128kbps). SampleRate sets the sampling rate of the stream. This "
+"can be anything from 11025 (11025kHz) to 44100 (44100kHz). Channels sets how "
+"many channels your stream will broadcast. This can be anything from 1 (mono) "
+"to 2 (stereo). Quality sets the stream quality. This is somewhat still "
+"controlled by the Bitrate/SampleRate/Channels. This is where you deal with "
+"how compressed the stream is. 1 gives you best quality, 10 gives you the "
+"best speed. Keep your connection in mind when you set these values! Use the "
+"guide given in order to figure out what your mp3's should be streamed at."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):940
+msgid "Setting up crossfading"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):940
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Mode=0 for none, 1 for 100/100-&gt;100/0, 2 for 0/100-&gt;100/0</comment>\n"
+"CrossfadeMode=1\n"
+"<comment>; Length is ms.</comment>\n"
+"CrossfadeLength=8000\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):947
+msgid ""
+"This sets up song cross fading. Setting this to 0 will disable cross fading. "
+"If you set it to 1, Song 1 will fade out and Song 2 will fade in. If you set "
+"it to 2, Song 1 will fade in and Song 2 will fade out. The length is how "
+"long in ms the cross fade occurs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):954
+msgid "Enabling ID3 usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):954
+#, no-wrap
+msgid ""
+"\n"
+"UseID3=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):958
+msgid ""
+"This decides whether or not you wish to use the ID3 tag for information "
+"about the mp3."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):963
+msgid "Setting up public status"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):963
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Public determines whether or not this station will show up in the directory</comment>\n"
+"Public=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):968
+msgid ""
+"This sets up whether or not streams should be publicly listed when relaying "
+"to a server. Remember PublicServer in sc_serv.conf can over-ride this!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):973
+msgid "Setting up user interaction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):973
+#, no-wrap
+msgid ""
+"\n"
+"<comment>; Put stuff here for user interaction (AOL IM, ICQ, IRC)</comment>\n"
+"AIM=AIMHandle\n"
+"ICQ=\n"
+"IRC=SHOUTcast\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):980
+msgid ""
+"This sets up the information on how to reach you (the DJ). You can setup AIM "
+"or ICQ channels for song requests/anything. You can setup your own IRC "
+"channel as well, so that you can interact with multiple users at once."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):989
+msgid "SHOUTcast Trans Setup Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):992
+msgid ""
+"Your SHOUTcast Trans is now ready to stream to your SHOUTcast Server! We'll "
+"now get started on streaming your mp3's."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1002
+msgid "Getting Started With SHOUTcast Trans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1004
+msgid "Starting up SHOUTcast Trans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1007
+msgid ""
+"As I most often use SHOUTcast Trans with SHOUTcast Server, I tend to startup "
+"SHOUTcast Trans, which in turns starts up SHOUTcast for you (much easier). "
+"So we'll go ahead and get SHOUTcast Trans started."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1013
+msgid "Starting up SHOUTcast Trans and SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1013
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/shoutcast_trans start</i>\n"
+" * Starting Shoutcast Server...\n"
+"*******************************************************************************\n"
+"** SHOUTcast Distributed Network Audio Server\n"
+"** Copyright (C) 1998-2004 Nullsoft, Inc.  All Rights Reserved.\n"
+"** Use \"sc_serv filename.ini\" to specify an ini file.\n"
+"*******************************************************************************\n"
+"                                                  [ ok ]\n"
+"* Starting Shoutcast Trans...                     [ ok ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1028
+msgid "Listening to the SHOUTcast Trans stream"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1031
+msgid ""
+"Now that SHOUTcast Trans is started, we'll start listening to the stream. I "
+"use MPlayer in this example to play the stream."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1036
+msgid "Listening to your stream"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1036
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mplayer -cache 1024 http://127.0.0.1:8000/</i>\n"
+"...\n"
+"Playing http://127.0.0.1:8000/.\n"
+"Connecting to server 127.0.0.1[127.0.0.1]:8000 ...\n"
+"Name   : Chris Gentoo Beats\n"
+"Genre  : JPOP Electronica And More!\n"
+"Website: http://www.gentoo.org\n"
+"Public : no\n"
+"Bitrate: 128kbit/s\n"
+"Cache size set to 1024 KBytes\n"
+"Connected to server: 127.0.0.1\n"
+"Cache fill:  9.38% (98304 bytes)    Audio file detected.\n"
+"==========================================================================\n"
+"Opening audio decoder: [mp3lib] MPEG layer-2, layer-3\n"
+"MP3lib: init layer2 and 3 finished, tables done\n"
+"mpg123: Can't rewind stream by 156 bits!\n"
+"AUDIO: 44100 Hz, 2 ch, 16 bit (0x10), ratio: 16000-&gt;176400 (128.0 kbit)\n"
+"Selected audio codec: [mp3] afm:mp3lib (mp3lib MPEG layer-2, layer-3)\n"
+"==========================================================================\n"
+"Checking audio filter chain for 44100Hz/2ch/16bit -&gt; 44100Hz/2ch/16bit...\n"
+"AF_pre: af format: 2 bps, 2 ch, 44100 hz, little endian signed int\n"
+"AF_pre: 44100Hz 2ch Signed 16-bit (Little-Endian)\n"
+"AO: [oss] 44100Hz 2ch Signed 16-bit (Little-Endian) (2 bps)\n"
+"Building audio filter chain for 44100Hz/2ch/16bit -&gt; 44100Hz/2ch/16bit...\n"
+"Video: no video\n"
+"Starting playback...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1065
+msgid ""
+"This was somewhat clipped. The -cache variable was put in to over-ride my "
+"somewhat larger buffering settings. And voilà! You're now listening to "
+"streaming media! In the next chapter, we'll show you how to do a little bit "
+"more with your SHOUTcast Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1077
+msgid "Advanced SHOUTcast Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1079
+msgid "Business Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1082
+msgid "Businesses can use SHOUTcast in a number of ways:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(li):1087
+msgid ""
+"Use on demand content streaming to make more interesting daily announcements."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(li):1091
+msgid ""
+"Have streaming public announcements available as they happen, let your "
+"clients know what's going on, on the spot! Then archive them as on demand "
+"content streaming for future reference."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(li):1096
+msgid ""
+"Do interviews as streaming media and archive them as on demand content "
+"streaming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1102
+msgid ""
+"There are more possibilities on how to utilize SHOUTcast Server for "
+"businesses. Use live streaming media instead of boring old text!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1110
+msgid "DJ-ing with SHOUTcast"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1113
+msgid ""
+"SHOUTcast Server is one of the most popular servers for both new and veteran "
+"DJs alike. For those just starting, there are a few ways to increase the "
+"user experience of your SHOUTcast Server. Having an intro song is very key. "
+"It gives the users an idea of what your station is all about. Be sure to "
+"include this! Post your server on yp.SHOUTcast.com (described in the "
+"SHOUTcast Server configuration section) so that everyone knows where you "
+"are. One of the most unique things is to be able to take requests. To set up "
+"requesting, first turn Shuffle off in sc_Trans.conf. Have about, I'd say, 10 "
+"or so songs ready to get you started. Then start requesting song requests in "
+"the middle. When someone requests a song, simple add it to the end of your "
+"play list, and then you can use this script here to control what SHOUTcast "
+"Trans does with your play list:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1128
+msgid "djcontrol"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1128
+#, no-wrap
+msgid ""
+"\n"
+"<comment>#!/bin/bash</comment>\n"
+"\n"
+"case \"$1\" in\n"
+"  \"reload\")\n"
+"    kill -s USR1 `cat /var/run/SHOUTcast_Trans.pid`\n"
+"    ;;\n"
+"  \"next\")\n"
+"    kill -s WINCH `cat /var/run/SHOUTcast_Trans.pid`\n"
+"    ;;\n"
+"  *)\n"
+"    echo \"Invalid command\"\n"
+"    ;;\n"
+"esac\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1144
+msgid ""
+"When you've added the song to the play list, you need to tell SHOUTcast "
+"Trans that your play list has changed with the new request entry."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1149
+msgid "Reloading the playlist"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1149
+#, no-wrap
+msgid ""
+"\n"
+"# <i>djcontrol reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1153
+msgid ""
+"You should now let the users know after what song the requests will start. "
+"Or if you want, you can keep skipping with:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1158
+msgid "Skipping through the playlist"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1158
+#, no-wrap
+msgid ""
+"\n"
+"# <i>djcontrol next</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1162
+msgid ""
+"Be careful not to skip too much, as there is no previous control. Once you "
+"hit their song, the requesting begins. I'd get about 5 or so requests before "
+"you start requesting. This way you don't run all the way back to the "
+"beginning. If you start to lack in requests and expect that your request "
+"hour is over with, then simply copy your next session's play list over the "
+"requests play list and reload the play list. Once the current song is over, "
+"it will go back to the new play list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1175
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1178
+msgid ""
+"That ends it for the SHOUTcast Server and SHOUTcast Trans tutorial. I hope "
+"you benefited from the information here and please email me any comments or "
+"suggestions for this page! Enjoy your new streaming SHOUTcast Server!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/source_mirrors.xml.po b/doc/gettext/ru/source_mirrors.xml.po
new file mode 100644
index 0000000..3e1120b
--- /dev/null
+++ b/doc/gettext/ru/source_mirrors.xml.po
@@ -0,0 +1,341 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(guide:link):5
+msgid "/doc/en/source_mirrors.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):7
+msgid "Gentoo Linux Source Mirrors Policy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):10
+msgid "klieber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):10
+msgid "Kurt Lieber"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):12
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):15
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):18
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):21
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):24
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):13
+msgid "cshields@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):13
+msgid "Corey Shields"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):16
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):16
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):19
+msgid "jforman@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):19
+msgid "Jeffrey Forman"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):22
+msgid "robbat2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):22
+msgid "Robin H. Johnson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):25
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):25
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(abstract):28
+msgid "This document explains the requirements for source mirrors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(version):35
+msgid "1.13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(date):36
+msgid "2010-04-28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):39
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):41
+msgid "Minimum Bandwidth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):44
+msgid ""
+"To properly host a source mirror, you should have a minimum of 5Mbps "
+"upstream bandwidth. ADSL and cable connections do not generally make "
+"adequate connections for distfile hosts due to their limited upstream "
+"performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):53
+msgid "Minimum Disk Space"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):56
+msgid ""
+"The space requirements depend on whether you choose to run a \"Full\" mirror "
+"or a \"Distfiles only\" mirror. Full mirrors require 210 GB of disk space. "
+"Distfiles only mirrors require 120 GB of space."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):65
+msgid "Minimum User Count"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):68
+msgid ""
+"We ask that you support a minimum of 15 and preferrably 30 or more "
+"concurrent user connections."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):76
+msgid "Update Frequency"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):79
+msgid ""
+"All mirrors must be synchronized every four hours, starting at midnight in "
+"your local time zone. This helps distribute the load out over a period of "
+"time, rather than having all mirrors synchronize at the same time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):88
+msgid "Mirror Needs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):91
+msgid ""
+"Your mirror may not be added immediately to our listing and given access to "
+"the private distribution point. We add mirrors on an as-needed basis so as "
+"not to clutter up the listing, and to provide an adequate amount of high "
+"speed mirrors. You are more than welcome to peek in <uri link=\"irc://irc."
+"gentoo.org/gentoo-mirrors\">#gentoo-mirrors</uri> on IRC and chat up to see "
+"the status of your mirror being added to our official network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):105
+msgid "Implementation details"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):109
+msgid "For new source mirror requests, the procedure will be as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):113
+msgid ""
+"Set up your server to rsync with ftp.ussg.iu.edu::gentoo-distfiles. Once you "
+"have a complete mirror of that server, please file a bug report on <uri link="
+"\"http://bugs.gentoo.org/enter_bug.cgi?product=Mirrors\">bugs.gentoo.org</"
+"uri> under the <c>Mirrors</c> category stating that you have a new mirror "
+"and wish it to be added to the list of official mirrors. Please specify "
+"whether you wish to be a \"Full\" mirror or \"Distfiles only\" mirror. "
+"Distfiles only mirrors will be designated as such on the website."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):123
+msgid ""
+"Full mirrors must carry the following directories (plus any directories that "
+"get added in the future):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):129
+msgid "/releases (45-55G)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):130
+msgid "/experimental (20-30G)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):131
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):141
+msgid "/distfiles (110G)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):132
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):142
+msgid "/snapshots (600M)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):133
+msgid "/grp (0M, obsolete)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):136
+msgid "Distfiles only mirrors need to carry the following directories:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):145
+msgid ""
+"We will then verify that the mirror exists and we can connect to it "
+"properly. Then, in the next 2 weeks, we will determine if your mirror is "
+"syncing correctly and in accordance with this policy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):151
+msgid ""
+"If all steps went smoothly, we will then add you to our list of <uri link=\"/"
+"main/en/mirrors2.xml\">download mirrors</uri> on the main web site. We will "
+"also send you the login information for our private master distfile mirror "
+"which is only available to official Gentoo Linux source mirrors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):158
+msgid ""
+"Additionally, you, the mirror admin, will be requested to subscribe to the "
+"gentoo-mirrors mailing list (low traffic) so that you can follow all issues "
+"associated with source mirrors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(note):164
+msgid ""
+"Thanks for helping out Gentoo Linux users and developers! :) For any mirror "
+"administration issues or problems, please contact <mail link=\"mirror-"
+"admin@gentoo.org\">mirror-admin@gentoo.org</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(warn):170
+msgid ""
+"Do NOT email mirror-admin@gentoo.org for mirror requests, please file a bug. "
+"It makes mirror tracking easier on us."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):180
+msgid "Short FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):182
+msgid ""
+"Q: Who should I contact regarding new mirrors or to get my mirror added to "
+"the Gentoo web site?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):188
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):198
+msgid ""
+"A: Please file a bug on bugs.gentoo.org under the <c>Mirrors</c> category."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):195
+msgid "Q: Who should I contact regarding mirror issues and maintenance?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):205
+msgid ""
+"Q: I run a private source mirror for my company. Can I still access the "
+"private master source mirror?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):211
+msgid ""
+"A: Because our resources are limited, we need to ensure we allocate them in "
+"such a way to provide the maximum amount of benefit to our users. As such, "
+"we limit connections to our master rsync and distfile mirrors to public "
+"mirrors only. Users are welcome to use our regular mirror system to "
+"establish a private source mirror."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):222
+msgid "Q: How do I find the mirror nearest to me?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):225
+msgid ""
+"A: mirrorselect was designed to do this for you. If you haven't already run "
+"<c>emerge mirrorselect</c>, then please do so. Then run: <c>mirrorselect</"
+"c>. An ncurses-based menu will display allowing you to select a mirror close "
+"to you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):235
+msgid "Q: I don't have that much disk space. Can I mirror part of the sources?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):240
+msgid ""
+"A: Yes, if you are unable to mirror our full sources, you can elect to "
+"mirror the following two directories only:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):246
+msgid "/distfiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):247
+msgid "/snapshots"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):250
+msgid ""
+"These two directories will require approximately 50GB of space and you will "
+"be listed on our site as a distfiles-only mirror."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):258
+msgid ""
+"Q: Do I have to turn on Directory Indexing for directories served up via "
+"HTTP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):263
+msgid ""
+"A: Directory Indexing is required for the /releases and /experimental "
+"directories, but can be turned off for all other directories (including /"
+"distfiles) if you wish."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):273
+msgid "Q: Do I have to mirror historical? I mean, it is old releases."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):276
+msgid ""
+"A: Of course not, it is quite a bit of data. In your rsync command, add "
+"<path>--exclude=/releases/historical</path> to your rsync options. This will "
+"exclude historical and save you quite a bit of space."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/sudo-guide.xml.po b/doc/gettext/ru/sudo-guide.xml.po
new file mode 100644
index 0000000..04cdc70
--- /dev/null
+++ b/doc/gettext/ru/sudo-guide.xml.po
@@ -0,0 +1,616 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(guide:link):7
+msgid "/doc/en/sudo-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):8
+msgid "Gentoo Sudo(ers) Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(mail:link):11
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(mail):11
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(abstract):14
+msgid ""
+"When you want some people to perform certain administrative steps on your "
+"system without granting them total root access, using sudo is your best "
+"option. With sudo you can control who can do what. This guide offers you a "
+"small introduction to this wonderful tool."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(version):25
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(date):26
+msgid "2006-07-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):29
+msgid "About Sudo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):31
+msgid "Granting Permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):34
+msgid ""
+"The <c>app-admin/sudo</c> package allows the system administrator to grant "
+"permission to other users to execute one or more applications they would "
+"normally have no right to. Unlike using the <e>setuid</e> bit on these "
+"applications <c>sudo</c> gives a more fine-grained control on <e>who</e> can "
+"execute a certain command and <e>when</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):42
+msgid ""
+"With <c>sudo</c> you can make a clear list <e>who</e> can execute a certain "
+"application. If you would set the setuid bit, any user would be able to run "
+"this application (or any user of a certain group, depending on the "
+"permissions used). You can (and probably even should) require the user to "
+"provide a password when he wants to execute the application and you can even "
+"fine-tune the permissions based on the user's location: logged on from the "
+"system itself or through SSH from a remote site."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):55
+msgid "Logging Activity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):58
+msgid ""
+"One additional advantage of <c>sudo</c> is that it can log any attempt "
+"(successful or not) to run an application. This is very useful if you want "
+"to track who made that one fatal mistake that took you 10 hours to fix :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):67
+msgid "Configuring Sudo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):70
+msgid ""
+"The <c>sudo</c> configuration is managed by the <path>/etc/sudoers</path> "
+"file. This file should never be edited through <c>nano&nbsp;/etc/sudoers</c> "
+"or <c>vim&nbsp;/etc/sudoers</c> or any other editor you might like. When you "
+"want to alter this file, you should use <c>visudo</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):77
+msgid ""
+"This tool makes sure that no two system administrators are editing this file "
+"at the same time, preserves the permissions on the file and performs some "
+"syntax checking to make sure you make no fatal mistakes in the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):86
+msgid "About this Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):89
+msgid ""
+"This guide is meant as a quick introduction. The <c>sudo</c> package is a "
+"lot more powerful than what is described in this guide. It has special "
+"features for editing files as a different user (<c>sudoedit</c>), running "
+"from within a script (so it can background, read the password from standard "
+"in instead of the keyboard, ...), etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):97
+msgid ""
+"Please read the <c>sudo</c> and <c>sudoers</c> manual pages for more "
+"information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):107
+msgid "Sudoers Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):109
+msgid "Basic Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):112
+msgid ""
+"The most difficult part of <c>sudo</c> is the <path>/etc/sudoers</path> "
+"syntax. The basic syntax is like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):117
+msgid "Basic /etc/sudoers syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):117
+#, no-wrap
+msgid ""
+"\n"
+"user  host = commands\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):121
+msgid ""
+"This syntax tells <c>sudo</c> that the user, identified by <e>user</e> and "
+"logged on through the system <e>host</e> can execute any of the commands "
+"listed in <e>commands</e> as the root user. A more real-life example might "
+"make this more clear: allow the user <e>swift</e> to execute <c>emerge</c> "
+"if he is logged on from the system (not through SSH):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):129
+msgid "Live /etc/sudoers examples"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):129
+#, no-wrap
+msgid ""
+"\n"
+"swift  localhost = /usr/bin/emerge\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):133
+msgid ""
+"A <brite>big warning</brite> is in place though: do not allow a user to run "
+"an application that can allow people to elevate privileges. For instance, "
+"allowing users to execute <c>emerge</c> as root can indeed grant them full "
+"root access to the system because <c>emerge</c> can be manipulated to change "
+"the live file system to the user's advantage. If you do not trust your "
+"<c>sudo</c> users, don't grant them any rights."
+msgstr ""
+
+#. Wrappers are no real advantage here either, see #71750
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):146
+msgid ""
+"The user name can also be substituted with a group name - in this case you "
+"should start the group name with a <c>%</c> sign. For instance, to allow any "
+"one in the <c>wheel</c> group to execute <c>emerge</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):152
+msgid "Allowing the wheel group members to execute emerge"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):152
+#, no-wrap
+msgid ""
+"\n"
+"%wheel  localhost = /usr/bin/emerge\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):156
+msgid ""
+"You can extend the line to allow for several commands (instead of making a "
+"single entry for each command). For instance, to allow the same user to not "
+"only run <c>emerge</c> but also <c>ebuild</c> and <c>emerge-webrsync</c> as "
+"root:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):162
+msgid "Multiple commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):162
+#, no-wrap
+msgid ""
+"\n"
+"swift  localhost = /usr/bin/emerge, /usr/bin/ebuild, /usr/sbin/emerge-webrsync\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):166
+msgid ""
+"You can also specify a precise command and not only the tool itself. This is "
+"useful to restrict the use of a certain tool to a specified set of command "
+"options. The <c>sudo</c> tool allows shell-style wildcards (AKA meta or glob "
+"characters) to be used in pathnames as well as command line arguments in the "
+"sudoers file. Note that these are <e>not</e> regular expressions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):174
+msgid "Let us put this to the test:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):178
+msgid "Attempt to update the system using sudo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):178
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>sudo emerge -uDN world</i>\n"
+"\n"
+"We trust you have received the usual lecture from the local System\n"
+"Administrator. It usually boils down to these three things:\n"
+"\n"
+"    #1) Respect the privacy of others.\n"
+"    #2) Think before you type.\n"
+"    #3) With great power comes great responsibility.\n"
+"\n"
+"Password: <comment>(Enter the user password, not root!)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):191
+msgid ""
+"The password that <c>sudo</c> requires is the user's own password. This is "
+"to make sure that no terminal that you accidentally left open to others is "
+"abused for malicious purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):197
+msgid ""
+"You should know that <c>sudo</c> does not alter the <c>${PATH}</c> variable: "
+"any command you place after <c>sudo</c> is treated from <e>your</e> "
+"environment. If you want the user to run a tool in for instance <path>/sbin</"
+"path> he should provide the full path to <c>sudo</c>, like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):204
+msgid "Using the full path to a tool"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):204
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>sudo /usr/sbin/emerge-webrsync</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):211
+msgid "Using Aliases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):214
+msgid ""
+"In larger environments having to enter all users over and over again (or "
+"hosts, or commands) can be a daunting task. To ease the administration of "
+"<path>/etc/sudoers</path> you can define <e>aliases</e>. The format to "
+"declare aliases is quite simple:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):221
+msgid "Declaring aliases in /etc/sudoers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):221
+#, no-wrap
+msgid ""
+"\n"
+"Host_Alias hostalias = hostname1, hostname2, ...\n"
+"User_Alias useralias = user1, user2, ...\n"
+"Cmnd_Alias cmndalias = command1, command2, ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):227
+msgid ""
+"One alias that always works, for any position, is the <c>ALL</c> alias (to "
+"make a good distinction between aliases and non-aliases it is recommended to "
+"use capital letters for aliases). As you might undoubtedly have guessed, the "
+"<c>ALL</c> alias is an alias to all possible settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):234
+msgid ""
+"A sample use of the <c>ALL</c> alias to allow <e>any</e> user to execute the "
+"<c>shutdown</c> command if he is logged on locally is:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):239
+msgid "Allowing any user to execute shutdown"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):239
+#, no-wrap
+msgid ""
+"\n"
+"ALL  localhost = /sbin/shutdown\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):243
+msgid ""
+"Another example is to allow the user <c>swift</c> to execute the <c>emerge</"
+"c> command as root, regardless of where he is logged in from:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):248
+msgid "Allowing a user to run an application regardless of his location"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):248
+#, no-wrap
+msgid ""
+"\n"
+"swift   ALL = /usr/bin/emerge\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):252
+msgid ""
+"More interesting is to define a set of users who can run software "
+"administrative applications (such as <c>emerge</c> and <c>ebuild</c>) on the "
+"system and a group of administrators who can change the password of any "
+"user, except root!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):258
+msgid "Using aliases for users and commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):258
+#, no-wrap
+msgid ""
+"\n"
+"User_Alias  <i>SOFTWAREMAINTAINERS</i> = swift, john, danny\n"
+"User_Alias  <i>PASSWORDMAINTAINERS</i> = swift, sysop\n"
+"Cmnd_Alias  <i>SOFTWARECOMMANDS</i>    = /usr/bin/emerge, /usr/bin/ebuild\n"
+"Cmnd_Alias  <i>PASSWORDCOMMANDS</i>    = /usr/bin/passwd [a-zA-Z0-9_-]*, !/usr/bin/passwd root\n"
+"\n"
+"<i>SOFTWAREMAINTAINERS</i>  localhost = <i>SOFTWARECOMMANDS</i>\n"
+"<i>PASSWORDMAINTAINERS</i>  localhost = <i>PASSWORDCOMMANDS</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):271
+msgid "Non-Root Execution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):274
+msgid ""
+"It is also possible to have a user run an application as a different, non-"
+"root user. This can be very interesting if you run applications as a "
+"different user (for instance <c>apache</c> for the web server) and want to "
+"allow certain users to perform administrative steps as that user (like "
+"killing zombie processes)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):281
+msgid ""
+"Inside <path>/etc/sudoers</path> you list the user(s) in between <c>(</"
+"c>&nbsp;and&nbsp;<c>)</c> before the command listing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):286
+msgid "Non-root execution syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):286
+#, no-wrap
+msgid ""
+"\n"
+"users  hosts = (run-as) commands\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):290
+msgid ""
+"For instance, to allow <c>swift</c> to run the <c>kill</c> tool as the "
+"<c>apache</c> or <c>gorg</c> user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):295
+msgid "Non-root execution example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):295
+#, no-wrap
+msgid ""
+"\n"
+"Cmnd_Alias KILL = /bin/kill, /usr/bin/pkill\n"
+"\n"
+"swift   ALL = (apache, gorg) KILL\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):301
+msgid ""
+"With this set, the user can run <c>sudo&nbsp;-u</c> to select the user he "
+"wants to run the application as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):306
+msgid "Running pkill as the apache user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):306
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>sudo -u apache pkill apache</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):310
+msgid ""
+"You can set an alias for the user to run an application as using the "
+"<c>Runas_Alias</c> directive. Its use is identical to the other <c>_Alias</"
+"c> directives we have seen before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):319
+msgid "Passwords and Default Settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):322
+msgid ""
+"By default, <c>sudo</c> asks the user to identify himself using his own "
+"password. Once a password is entered, <c>sudo</c> remembers it for 5 "
+"minutes, allowing the user to focus on his tasks and not repeatedly re-"
+"entering his password."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):329
+msgid ""
+"Of course, this behavior can be changed: you can set the <c>Defaults:</c> "
+"directive in <path>/etc/sudoers</path> to change the default behavior for a "
+"user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):335
+msgid "For instance, to change the default 5 minutes to 0 (never remember):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):339
+msgid "Changing the timeout value"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):339
+#, no-wrap
+msgid ""
+"\n"
+"Defaults:swift  timestamp_timeout=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):343
+msgid ""
+"A setting of <c>-1</c> would remember the password indefinitely (until the "
+"system reboots)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):348
+msgid ""
+"A different setting would be to require the password of the user that the "
+"command should be run as and not the users' personal password. This is "
+"accomplished using <c>runaspw</c>. In the following example we also set the "
+"number of retries (how many times the user can re-enter a password before "
+"<c>sudo</c> fails) to <c>2</c> instead of the default 3:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):356
+msgid "Requiring the root password instead of the user's password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):356
+#, no-wrap
+msgid ""
+"\n"
+"Defaults:john   runaspw, passwd_tries=2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):360
+msgid ""
+"Another interesting feature is to keep the <c>DISPLAY</c> variable set so "
+"that you can execute graphical tools:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):365
+msgid "Keeping the DISPLAY variable alive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):365
+#, no-wrap
+msgid ""
+"\n"
+"Defaults:john env_keep=DISPLAY\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):369
+msgid ""
+"You can change dozens of default settings using the <c>Defaults:</c> "
+"directive. Fire up the <c>sudo</c> manual page and search for <c>Defaults</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):374
+msgid ""
+"If you however want to allow a user to run a certain set of commands without "
+"providing any password whatsoever, you need to start the commands with "
+"<c>NOPASSWD:</c>, like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):380
+msgid "Allowing emerge to be ran as root without asking for a password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):380
+#, no-wrap
+msgid ""
+"\n"
+"swift     localhost = NOPASSWD: /usr/bin/emerge\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):389
+msgid "Using Sudo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):391
+msgid "Listing Privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):394
+msgid "To inform yourself what your capabilities are, run <c>sudo&nbsp;-l</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):398
+msgid "Listing capabilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):398
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>sudo -l</i>\n"
+"User swift may run the following commands on this host:\n"
+"    (root)   /usr/libexec/xfsm-shutdown-helper\n"
+"    (root)   /usr/bin/emerge\n"
+"    (root)   /usr/bin/passwd [a-zA-Z0-9_-]*\n"
+"    (root)   !/usr/bin/passwd root\n"
+"    (apache) /usr/bin/pkill\n"
+"    (apache) /bin/kill\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):409
+msgid ""
+"If you have any command in <path>/etc/sudoers</path> that does not require "
+"you to enter a password, it will not require a password to list the entries "
+"either. Otherwise you might be asked for your password if it isn't "
+"remembered."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):418
+msgid "Prolonging the Password Timeout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):421
+msgid ""
+"By default, if a user has entered his password to authenticate himself to "
+"<c>sudo</c>, it is remembered for 5 minutes. If the user wants to prolong "
+"this period, he can run <c>sudo&nbsp;-v</c> to reset the time stamp so that "
+"it will take another 5 minutes before <c>sudo</c> asks for the password "
+"again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):428
+msgid "Prolonging the password timeout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):428
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>sudo -v</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):432
+msgid "The inverse is to kill the time stamp using <c>sudo&nbsp;-k</c>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/test.xml.po b/doc/gettext/ru/test.xml.po
new file mode 100644
index 0000000..446823e
--- /dev/null
+++ b/doc/gettext/ru/test.xml.po
@@ -0,0 +1,84 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(title):6
+msgid "Testfile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(mail:link):9
+msgid "pylon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(mail):9
+msgid "Lars Weiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(abstract):15
+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//test.xml(version):22
+msgid "1.84"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(date):23
+msgid "2008-12-03"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(title):26
+msgid "Sample Chapter 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(title):28
+msgid "Sample Section 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(p):31
+msgid "Some text. Some more text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(title):39
+msgid "Sample Section 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(p):42
+msgid "<b>Some bold text</b> and <e>emphasised</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(p):46
+msgid "Testing gentoo-doc-cvs mailing list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(p):49
+msgid "Testing gentoo-commits mailing list as well."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/udev-guide.xml.po b/doc/gettext/ru/udev-guide.xml.po
new file mode 100644
index 0000000..5446b31
--- /dev/null
+++ b/doc/gettext/ru/udev-guide.xml.po
@@ -0,0 +1,696 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):6
+msgid "Gentoo udev Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(author:title):11
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail:link):12
+msgid "greg_g@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail):12
+msgid "Gregorio Guidi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(abstract):18
+msgid ""
+"This document explains what udev is and how you can use udev to fit your "
+"needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(version):26
+msgid "6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(date):27
+msgid "2010-05-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):30
+msgid "What is udev?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):32
+msgid "The /dev Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):35
+msgid ""
+"When Linux-users talk about the hardware on their system in the vicinity of "
+"people who believe Linux is some sort of virus or brand of coffee, the use "
+"of \"slash dev slash foo\" will return a strange look for sure. But for the "
+"fortunate user (and that includes you) using <path>/dev/hda1</path> is just "
+"a fast way of explaining that we are talking about the primary master IDE, "
+"first partition. Or aren't we?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):44
+msgid ""
+"We all know what a device file is. Some even know why device files have "
+"special numbers when we take a closer look at them when we issue <c>ls -l</"
+"c> in <path>/dev</path>. But what we always take for granted is that the "
+"primary master IDE disk is referred to as <path>/dev/hda</path>. You might "
+"not see it this way, but this is a flaw by design."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):52
+msgid ""
+"Think about hotpluggable devices like USB, IEEE1394, hot-swappable PCI, ... "
+"What is the first device? And for how long? What will the other devices be "
+"named when the first one disappears? How will that affect ongoing "
+"transactions? Wouldn't it be fun that a printing job is suddenly moved from "
+"your supernew laserprinter to your almost-dead matrix printer because your "
+"mom decided to pull the plug of the laserprinter which happened to be the "
+"first printer?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):61
+msgid ""
+"Enter <e>udev</e>. The goals of the udev project are both interesting and "
+"needed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):67
+msgid "Runs in userspace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):68
+msgid "Dynamically creates/removes device files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):69
+msgid "Provides consistent naming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):70
+msgid "Provides a user-space API"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):73
+msgid ""
+"To provide these features, udev is developed in three separate projects: "
+"<e>namedev</e>, <e>libsysfs</e> and, of course, <e>udev</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):81
+msgid "namedev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):84
+msgid ""
+"Namedev allows you to define the device naming separately from the udev "
+"program. This allows for flexible naming policies and naming schemes "
+"developed by separate entities. This device naming subsystem provides a "
+"standard interface that udev can use."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):91
+msgid ""
+"Currently only a single naming scheme is provided by namedev; the one "
+"provided by LANANA, used by the majority of Linux systems currently and "
+"therefore very suitable for the majority of Linux users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):97
+msgid ""
+"Namedev uses a 5-step procedure to find out the name of a given device. If "
+"the device name is found in one of the given steps, that name is used. The "
+"steps are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):104
+msgid "label or serial number"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):105
+msgid "bus device number"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):106
+msgid "bus topology"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):107
+msgid "statically given name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):108
+msgid "kernel provided name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):111
+msgid ""
+"The <e>label or serial number</e> step checks if the device has a unique "
+"identifier. For instance USB devices have a unique USB serial number; SCSI "
+"devices have a unique UUID. If namedev finds a match between this unique "
+"number and a given configuration file, the name provided in the "
+"configuration file is used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):119
+msgid ""
+"The <e>bus device number</e> step checks the device bus number. For non-hot-"
+"swappable environments this procedure is sufficient to identify a hardware "
+"device. For instance PCI bus numbers rarely change in the lifetime of a "
+"system. Again, if namedev finds a match between this position and a given "
+"configuration file, the name provided in that configuration file is used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):128
+msgid ""
+"Likewise the <e>bus topology</e> is a rather static way of defining devices "
+"as long as the user doesn't switch devices. When the position of the device "
+"matches a given setting provided by the user, the accompanying name is used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):134
+msgid ""
+"The fourth step, <e>statically given name</e>, is a simple string "
+"replacement. When the kernel name (the default name) matches a given "
+"replacement string, the substitute name will be used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):140
+msgid ""
+"The final step (<e>kernel provided name</e>) is a catch-all: this one takes "
+"the default name provided by the kernel. In the majority of cases this is "
+"sufficient as it matches the device naming used on current Linux systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):149
+msgid "libsysfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):152
+msgid ""
+"udev interacts with the kernel through the sysfs pseudo filesystem. The "
+"libsysfs project provides a common API to access the information given by "
+"the sysfs filesystem in a generic way. This allows for querying all kinds of "
+"hardware without having to make assumptions on the kind of hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):162
+msgid "udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):165
+msgid ""
+"Every time the kernel gets an event in the device structure, it asks udev to "
+"take a look. udev follows the rules in the <path>/etc/udev/rules.d/</path> "
+"directory. udev then uses the information given by the kernel to perform the "
+"necessary actions on the <path>/dev</path> structure (creating or deleting "
+"device files)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):178
+msgid "Using udev on Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):180
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):183
+msgid ""
+"udev is meant to be used in combination with a 2.6 kernel (like <c>gentoo-"
+"sources</c> with the default 2007.0 profile). If you're using such a kernel "
+"then you just have to make sure that you have a recent <c>sys-apps/"
+"baselayout</c> version. That's all you need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):190
+msgid "Installing udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):190
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge udev</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):194
+msgid "Kernelwise, be sure to activate the following options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):198
+msgid "Required kernel options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):198
+#, no-wrap
+msgid ""
+"\n"
+"File systems ---&gt;\n"
+"    [*] Inotify file change notification support\n"
+"    [*]   Inotify support for userspace\n"
+"  Pseudo filesystems ---&gt;\n"
+"    [*] /proc file system support\n"
+"    [*] Virtual memory file system support (former shm fs)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):207
+msgid ""
+"If you use <c>genkernel</c>, you don't need to do anything special. "
+"Genkernel sets up udev by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):215
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):218
+msgid ""
+"If you want to use the udev settings Gentoo provides to make your life "
+"comfortable, then read no more. Gentoo will use udev but keep a static "
+"<path>/dev</path> so that you will never have any missing device nodes. The "
+"Gentoo init scripts won't run the devfsd daemon and will deactivate devfs "
+"when you boot up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):226
+msgid ""
+"But if you are a die-hard and want to run a udev-only, unmodified system as "
+"is intended by the udev development (including the difficulties of missing "
+"device nodes because udev doesn't support them yet), by all means, read on :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):232
+msgid ""
+"We'll deactivate the rules that save the device file nodes: edit the "
+"<c>RC_DEVICE_TARBALL</c> variable in <path>/etc/conf.d/rc</path> and set it "
+"to <c>no</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):238
+msgid "/etc/conf.d/rc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):238
+#, no-wrap
+msgid ""
+"\n"
+"RC_DEVICE_TARBALL=\"no\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):242
+msgid ""
+"If you have included devfs support in your kernel, you can deactivate it in "
+"the bootloader configuration: add <c>gentoo=nodevfs</c> as a kernel "
+"parameter. If you want to use devfs and deactivate udev, add "
+"<c>gentoo=noudev</c> as kernel parameter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):254
+msgid "Known Issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):256
+msgid "Missing device node files at boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):259
+msgid ""
+"If you can't boot successfully because you get an error about <path>/dev/"
+"null</path> not found, or because the initial console is missing, the "
+"problem is that you lack some device files that must be available <e>before</"
+"e><path>/dev</path> is mounted and handled by udev. This is common on Gentoo "
+"machines installed from old media."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):267
+msgid ""
+"If you run <c>sys-apps/baselayout-1.8.12</c> or later, this problem is "
+"alleviated since the boot process should still manage to complete. However, "
+"to get rid of those annoying warnings, you should create the missing device "
+"nodes as described below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):274
+msgid ""
+"To see which devices nodes are present before the <path>/dev</path> "
+"filesystem is mounted, run the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):279
+msgid "Listing device nodes available at boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):279
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir test</i>\n"
+"# <i>mount --bind / test</i>\n"
+"# <i>cd test/dev</i>\n"
+"# <i>ls</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):286
+msgid ""
+"The devices needed for a successful boot are <path>/dev/null</path> and "
+"<path>/dev/console</path>. If they didn't show up in the previous test, you "
+"have to create them manually. Issue the following commands in the <path>test/"
+"dev/</path> directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):293
+msgid "Creating necessary device node files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):293
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mknod -m 660 console c 5 1</i>\n"
+"# <i>mknod -m 660 null c 1 3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):298
+msgid ""
+"When you're finished, don't forget to unmount the <path>test/</path> "
+"directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):302
+msgid "Unmounting the test/ directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):302
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd ../..</i>\n"
+"# <i>umount test</i>\n"
+"# <i>rmdir test</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):311
+msgid "udev and nvidia"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):314
+msgid ""
+"If you use the proprietary driver from nVidia and the X server fails to "
+"start on a udev-only system, then make sure you have:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):320
+msgid ""
+"the <c>nvidia</c> module listed in <path>/etc/modules.autoload.d/kernel-2.6</"
+"path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):324
+msgid ""
+"a version of baselayout equal to or greater than <c>sys-apps/"
+"baselayout-1.8.12</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):333
+msgid "No Consistent Naming between DevFS and udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):336
+msgid ""
+"Even though our intention is to have a consistent naming scheme between both "
+"dynamical device management solutions, sometimes naming differences do occur."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):341
+msgid ""
+"One reported clash is with a HP Smart Array 5i RAID controller (more "
+"precisely the <c>cciss</c> kernel module). With udev, the devices are named "
+"<path>/dev/cciss/cXdYpZ</path> with X, Y and Z regular numbers. With devfs, "
+"the devices are <path>/dev/hostX/targetY/partZ</path> or symlinked from "
+"<path>/dev/cciss/cXdY</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):349
+msgid ""
+"If this is the case, don't forget to update your <path>/etc/fstab</path> and "
+"bootloader configuration files accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):354
+msgid ""
+"The same happens with all-round symlinks that used to exist in <path>/dev</"
+"path>, such as <path>/dev/mouse</path>, which <c>udev</c> doesn't create "
+"anymore. Be certain to check your X configuration file and see if the Device "
+"rule for your mouse points to an existing device file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):361
+msgid ""
+"Another issue is the difference in naming of terminals between devfs and "
+"udev. While devfs calls its terminals <c>tty</c>, udev calls them <c>vc</c> "
+"and <c>tty</c>. This could lead to a problem in case you are restricting "
+"root logins from consoles using <path>/etc/securetty</path>. You will need "
+"to make sure that both <c>tty1</c> and <c>vc/1</c> are listed in <path>/etc/"
+"securetty</path> to ensure that root can login using the console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):373
+msgid "Block device renaming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):376
+msgid ""
+"Recent versions of udev (104 and up) along with newer kernel versions "
+"(2.6.19 and up) may change your disc device names, due to a change in the "
+"kernel's libata implementation. A CD-RW device at <path>/dev/hdc</path> may "
+"be changed to <path>/dev/sr0</path>. While this is not normally a problem, "
+"it may cause issues for some applications that are hardcoded to look for "
+"devices at other locations. For example, <c>media-sound/rip</c> expects to "
+"find discs at <path>/dev/cdrom</path>, which becomes a problem if you use a "
+"newer kernel and udev renames your device to <path>/dev/cdrom1</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):387
+msgid ""
+"To work around these issues, you must edit <path>/etc/udev/rules.d/70-"
+"persistent-cd.rules</path> and assign the correct name to the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):393
+msgid ""
+"For more information on writing udev rules, be sure to read Daniel Drake's "
+"<uri link=\"http://www.reactivated.net/udevrules.php\">guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):401
+msgid "Network device renaming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):404
+msgid ""
+"Sometimes unplugging and replugging a network device (like a USB WiFi card) "
+"can rename your net device each time, incrementing the number by one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):409
+msgid ""
+"When this happens, you'll see it become <c>wlan0</c>, <c>wlan1</c>, "
+"<c>wlan2</c>, etc. This is because udev is adding additional rules to its "
+"rules file, instead of reloading the existing rules. Since udev watches its "
+"rules directory via inotify, you need inotify support in your kernel config:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):416
+msgid "Enabling inotify support in the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):416
+#, no-wrap
+msgid ""
+"\n"
+"File systems ---&gt;\n"
+"    [*] Inotify file change notification support\n"
+"    [*]   Inotify support for userspace\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):422
+msgid "Now udev will retain proper names for your network devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):429
+msgid "udev loads modules in an unpredictable order"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):432
+msgid ""
+"Sometimes udev loads modules in an undesired, unpredictable, or seemingly "
+"random order. This is especially common for systems that have multiple "
+"devices of the same type, as well as multimedia devices. This can affect the "
+"assigned numbers of devices; for example, sound cards may sometimes swap "
+"numbers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):439
+msgid ""
+"There are a few solutions to fix device numbers and/or module load order. "
+"Ideally, you can just use module parameters to specify your desired device "
+"number. Some modules, such as ALSA, include the \"index\" parameter. Modules "
+"that use the index parameter can be adjusted as shown. This example is for a "
+"system with two sound cards. The card with an index of 0 is designated as "
+"the first card. Once the parameters are changed, the module config files "
+"must be updated."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):448
+msgid "Specifying module parameters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):448
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"option snd-ice1724 index=0\" &gt;&gt; /etc/modprobe.d/alsa.conf</i>\n"
+"# <i>echo \"option snd-ymfpci index=1\" &gt;&gt; /etc/modprobe.d/alsa.conf</i>\n"
+"# <i>update-modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):454
+msgid ""
+"The above example is the preferred solution, but not all modules support "
+"parameters such as index. For these modules, you'll have to force the "
+"correct module load order. First, you must stop udev from autoloading the "
+"modules by blacklisting them. Be sure to use the exact name of the module "
+"being loaded. For PCI devices, you'll need to use the module names obtained "
+"from the output of <c>pcimodules</c>, available in the <c>pciutils</c> "
+"package. The following example uses DVB modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):464
+msgid "Blacklisting modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):464
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"blacklist b2c2-flexcop-pci\" &gt;&gt; /etc/modprobe.d/dvb</i>\n"
+"# <i>echo \"blacklist budget\" &gt;&gt; /etc/modprobe.d/dvb</i>\n"
+"# <i>update-modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):470
+msgid ""
+"Next, load the modules in the correct order. Add them to <path>/etc/modules."
+"autoload.d/kernel-2.6</path><e>in the exact order you want them loaded</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):476
+msgid "Loading modules in the correct order"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):476
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"budget\" &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+"# <i>echo \"b2c2-flexcop-pci\" &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):484
+msgid "Other issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):487
+msgid ""
+"If device nodes are not created when a module is loaded from <path>/etc/"
+"modules.autoload.d/kernel-2.6</path> but they appear when you load the "
+"module manually with modprobe then you should try upgrading to <c>sys-apps/"
+"baselayout-1.8.12</c> or later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):494
+msgid ""
+"Support for the framebuffer devices (<path>/dev/fb/*</path>) comes with the "
+"kernel starting from version 2.6.6-rc2."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):499
+msgid ""
+"For kernels older than 2.6.4 you have to explicitly include support for the "
+"<path>/dev/pts</path> filesystem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):504
+msgid "Enabling the /dev/pts filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):504
+#, no-wrap
+msgid ""
+"\n"
+"File systems ---&gt;\n"
+"  Pseudo filesystems ---&gt;\n"
+"    [*] /dev/pts file system for Unix98 PTYs\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):515
+msgid "Resources &amp; Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):519
+msgid ""
+"The udev talk on the Linux Symposium (Ottawa, Ontario Canada - 2003) given "
+"by Greg Kroah-Hartman (IBM Corporation) provided a solid understanding on "
+"the udev application."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):525
+msgid ""
+"<uri link=\"http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer."
+"html\">Decibel's UDEV Primer</uri> is an in-depth document about udev and "
+"Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):530
+msgid ""
+"<uri link=\"http://www.reactivated.net/udevrules.php\">Writing udev rules</"
+"uri> by fellow Gentoo developer Daniel Drake is an excellent document to "
+"learn how to customize your udev installation."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/uml.xml.po b/doc/gettext/ru/uml.xml.po
new file mode 100644
index 0000000..10b50ea
--- /dev/null
+++ b/doc/gettext/ru/uml.xml.po
@@ -0,0 +1,681 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(guide:link):6
+msgid "/doc/en/uml.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):7
+msgid "Gentoo Linux Developer's guide to system testing with User-Mode Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(author:title):9
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(author:title):12
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(author:title):15
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(author:title):18
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail:link):10
+msgid "g2boojum@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail):10
+msgid "Grant Goodyear"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(author):12
+msgid "John Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail:link):16
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail):16
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail:link):19
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail):19
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(abstract):22
+msgid ""
+"This guide shows Gentoo Linux developers how to set up and use user-mode "
+"linux for testing potentially system-breaking changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(version):31
+msgid "0.16"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(date):32
+msgid "2008-03-01"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):35
+msgid "Obtaining User-Mode Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(impo):39
+msgid ""
+"Before you can use user-mode Linux, you <e>must</e> be using a non-NPTL "
+"profile, and you must be using &lt;<c>glibc</c>-2.4. Follow the instructions "
+"for <uri link=\"/doc/en/gentoo-upgrading.xml#instructions\">changing "
+"profiles</uri>. You will need to run <c>emerge -e world</c> after switching "
+"to a non-NPTL profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):47
+msgid ""
+"As the user-mode Linux website (<uri>http://user-mode-linux.sourceforge.net</"
+"uri>) states, user-modeL linux allows a user to \"run Linux inside itself\". "
+"Specifically, user-mode linux provides a virtual machine on which a user can "
+"\"[r]un buggy software, experiment with new Linux kernels or distributions, "
+"and poke around in the internals of Linux, all without risking your main "
+"Linux setup.\" Experimental changes to Gentoo core packages such as <e>sys-"
+"apps/baselayout</e> or <e>sys-libs/glibc</e> have the potential to break the "
+"system and render it unbootable; with user-mode Linux we can test these "
+"changes without having to worry about breaking the live system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):60
+msgid ""
+"Most 2.6 kernels have UML support. Although you can use your current kernel "
+"sources, it might be wiser to keep the UML kernel tree(s) separate. After "
+"all, you'll be building a new kernel with a different configuration and you "
+"might want to have heterogenous systems on your main Linux system (several "
+"different UML kernels)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):68
+msgid ""
+"So download a nice kernel tree (like the vanilla one from <uri link=\"http://"
+"www.kernel.org\">kernel.org</uri>) and extract it to some local development "
+"location."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):74
+msgid ""
+"Next, configure this UML kernel as you would do for any other system, but "
+"append <e>ARCH=um</e> so that the kernel build software knows that the "
+"kernel is meant to run as a guest process on the main system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):80
+msgid "Building the UML kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):80
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /srv/aegis/src/uml-linux</i>\n"
+"# <i>make menuconfig <comment>ARCH=um</comment></i>\n"
+"# <i>make linux <comment>ARCH=um</comment></i>\n"
+"# <i>cp linux /usr/local/bin/linux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(warn):87
+msgid "The <e>ARCH=um</e> fragment is <e>extremely</e> important!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):91
+msgid ""
+"On a default Gentoo system, <path>/usr/local/bin</path> is in your <c>$PATH</"
+"c>. If it isn't, you should find a definition of <c>PATH</c> in the <path>/"
+"etc/profile</path> and fix it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):97
+msgid "Verifying $PATH"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):97
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>echo $PATH | grep /usr/local/bin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):101
+msgid "Sample definition of $PATH in /etc/profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):101
+#, no-wrap
+msgid ""
+"\n"
+"PATH=\"/usr/local/bin:/usr/bin:/bin:${PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):105
+msgid ""
+"Don't forget to run <c>source /etc/profile</c> for the change to take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):109
+msgid ""
+"For the user-mode Linux kernel to properly boot a Gentoo system the kernel "
+"needs to be configured to <e>not</e> automatically mount <path>/dev</path> "
+"(devfs) by default. Also, you will almost certainly want to make sure that "
+"you have <e>tmpfs</e> (the \"Virtual Memory Filesystem\") compiled in, since "
+"by default the Gentoo Linux bootscripts store their information in a small "
+"tmpfs partition. (The binary kernels available from the user-mode website do "
+"automatically mount <path>/dev</path>, and they don't have tmpfs compiled "
+"in; don't bother with them)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):121
+msgid ""
+"I highly recommend reading the user-mode linux documentation, but the basic "
+"idea is that running the <path>/usr/local/bin/linux</path> program boots the "
+"user-mode kernel and tries to bring up the system stored in the file "
+"<path>root_fs</path> that should be located in the current working directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):129
+msgid "It won't hurt to also install the user-mode Linux tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):133
+msgid "Installing UML tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):133
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge sys-apps/usermode-utilities</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):137
+msgid ""
+"These tools facilitate networking (among other things) between the user-mode "
+"Linux virtual system and the host Linux system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):147
+msgid "Creating root_fs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):149
+msgid "Making the Gentoo chroot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):152
+msgid ""
+"The <path>root_fs</path> file needed for user-mode linux is a single file "
+"that contains an entire Gentoo Linux filesystem. To generate this file you "
+"will need to have Loopback device support enabled in the host (non-user-"
+"mode) kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):159
+msgid ""
+"Generating the <path>root_fs</path> file itself will be our last step. First "
+"we will generate a Gentoo filesystem in an ordinary chroot. We need the "
+"stage tarball available, which could be downloaded separately, extracted "
+"from an Installation CD, or extracted from an Installation CD .iso."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):167
+msgid "Mounting an Installation CD .iso"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):167
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /mnt/loop</i>\n"
+"# <i>mount -o loop /path/to/install-&lt;TAB&gt;.iso /mnt/loop</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):172
+msgid ""
+"Setting up the chroot is essentially identical to an ordinary Gentoo Linux "
+"build."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):177
+msgid "Creating the Gentoo chroot mount"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):177
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /mnt/gentoo</i>\n"
+"# <i>cd /mnt/gentoo</i>\n"
+"# <i>tar xvjpf /path/to/stage&lt;TAB&gt;.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):183
+msgid "Go ahead and unmount the .iso. You don't need it anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):187
+msgid ""
+"Build the system in the usual fashion: chroot into <path>/mnt/gentoo</path> "
+"and follow the Gentoo installation instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):192
+msgid ""
+"Add any additional packages you desire. Feel free to give your virtual "
+"Gentoo system a hostname, if you so desire. In <path>/etc/fstab</path> you "
+"will want <path>/dev/ROOT</path> to be <path>/dev/ubda</path>, with a fs "
+"type of either ext2, ext3, or reiserfs. Set <path>/dev/SWAP</path> to be "
+"<path>/dev/ubdb</path>, and comment out <path>/dev/BOOT</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):200
+msgid "At this point, remember to set your root password."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):204
+msgid "Setting root password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):204
+#, no-wrap
+msgid ""
+"\n"
+"# <i>passwd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):208
+msgid ""
+"Now we need to make some changes to the boot scripts. Remove consolefont and "
+"keymaps from the boot runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):213
+msgid "Removing unneeded initscripts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):213
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update del consolefont boot</i>\n"
+"# <i>rc-update del keymaps boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):218
+msgid ""
+"Exit the chroot, unmount all of the bind mounts, tar up the new Gentoo "
+"distro, and clean up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):223
+msgid "Finalising the installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):223
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /mnt/gentoo</i>\n"
+"# <i>tar cvjpf ~/gentoo.tbz2 *</i>\n"
+"# <i>cd</i>\n"
+"# <i>rm -rf /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):233
+msgid "Making root_fs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):236
+msgid ""
+"Our Gentoo chroot is nearly 300 MB in size, so <path>root_fs</path> needs to "
+"be at least that size. We'll choose 0.5 GB as a reasonable size."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):242
+msgid "Creating UML files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):242
+#, no-wrap
+msgid ""
+"\n"
+"# <i>dd if=/dev/zero of=root_fs seek=500 count=1 bs=1M</i>\n"
+"# <i>mke2fs -F root_fs</i>\n"
+"# <i>mount -o loop root_fs /mnt/loop</i>\n"
+"# <i>tar xvjpf gentoo.tbz2 -C /mnt/loop</i>\n"
+"# <i>umount /mnt/loop</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):250
+msgid "It would also be nice to have a 0.5 GB swap partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):254
+msgid "Create swap partition"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):254
+#, no-wrap
+msgid ""
+"\n"
+"# <i>dd if=/dev/zero of=swap_fs seek=500 count=1 bs=1M</i>\n"
+"# <i>mkswap -f swap_fs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):259
+msgid "Now see if it works!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):263
+msgid "Start UML kernel thread"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):263
+#, no-wrap
+msgid ""
+"\n"
+"# <i>linux ubd0=root_fs ubd1=swap_fs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):267
+msgid ""
+"User-mode Linux uses xterms for the virtual consoles that are run at boot "
+"time, so you need to make sure that the terminal from which you run user-"
+"mode Linux has $DISPLAY properly set (along with proper xhost/xauth "
+"permissions)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):274
+msgid ""
+"With any luck you should be able to log into your user-mode Linux Gentoo "
+"system. The only thing keeping this user-mode Linux version of Gentoo from "
+"being fully functional is networking from the virtual machine to the host."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(note):281
+msgid ""
+"If you receive \"No space left on device\" errors, you may need to allocate "
+"more memory to your user mode system by appending <c>mem=xxxMB</c> to the "
+"end of the kernel thread line. For example: <c>linux ubd0=root_fs "
+"ubd1=swap_fs mem=128MB</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):293
+msgid "Networking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):295
+msgid "Using an Existing Network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):298
+msgid ""
+"Make sure that the host kernel has the following settings compiled as "
+"modules:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):302
+msgid "Host kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):302
+#, no-wrap
+msgid ""
+"\n"
+"Networking --&gt;\n"
+"  IP: Netfilter Configuration --&gt;\n"
+"    IP tables support --&gt;\n"
+"      Full NAT --&gt;\n"
+"        &lt;M&gt; MASQUERADE target support \n"
+"    \n"
+"    Network Device Support --&gt; \n"
+"      &lt;M&gt; TUN/TAP Support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):313
+msgid "Run the following commands on the <e>host</e> machine:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):317
+msgid "Setup networking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):317
+#, no-wrap
+msgid ""
+"\n"
+"# <i>modprobe tun</i>\n"
+"<comment>(If you receive a FATAL error here, try deleting /dev/net/tun and retry)</comment>\n"
+"# <i>modprobe iptable_nat</i>\n"
+"# <i>iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE</i>\n"
+"# <i>echo 1 &gt; /proc/sys/net/ipv4/ip_forward</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):325
+msgid ""
+"The iptables line sets up IP Masquerading between the private network that "
+"our user-mode system will be on and the internet (reachable via <c>eth0</c> "
+"in our case). The echo line then turns on packet forwarding between the "
+"private network and the interface that the default gateway is on (eth0 for "
+"us)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):333
+msgid ""
+"Now we bring up the user-mode system and see if networking is functional."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):338
+msgid "Get UML up and running"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):338
+#, no-wrap
+msgid ""
+"\n"
+"# <i>linux ubd0=root_fs ubd1=swap_fs eth0=tuntap,,,192.168.0.254</i>\n"
+"<comment>(login to user-mode system)</comment>\n"
+"# <i>ifconfig eth0 192.168.0.1 up</i>\n"
+"# <i>ping -c 2 192.168.0.254</i>\n"
+"PING 192.168.0.254 (192.168.0.254): 56 octets data\n"
+"64 octets from 192.168.0.254: icmp_seq=0 ttl=255 time=0.8 ms\n"
+"64 octets from 192.168.0.254: icmp_seq=1 ttl=255 time=0.6 ms\n"
+"\n"
+"--- 192.168.0.254 ping statistics ---\n"
+"2 packets transmitted, 2 packets received, 0% packet loss\n"
+"round-trip min/avg/max = 0.6/0.7/0.8 ms\n"
+"# <i>route add default gw 192.168.0.254</i>\n"
+"# <i>netstat -rn</i>\n"
+"Kernel IP routing table\n"
+"Destination  Gateway        Genmask        Flags MSS Window irtt Iface\n"
+"192.168.0.0  0.0.0.0        255.255.255.0  U      40 0         0 eth0\n"
+"0.0.0.0      192.168.0.254  0.0.0.0        UG     40 0         0 eth0\n"
+"# <i>scp user@192.168.0.254:/etc/resolv.conf /etc/resolv.conf</i> <comment>(if needed)</comment>\n"
+"# <i>ping -c 2 www.gentoo.org</i>\n"
+"PING www.gentoo.org (207.170.82.202): 56 octets data\n"
+"64 octets from 207.170.82.202: icmp_seq=0 ttl=240 time=119.6 ms\n"
+"64 octets from 207.170.82.202: icmp_seq=1 ttl=240 time=92.0 ms\n"
+"\n"
+"--- www.gentoo.org ping statistics ---\n"
+"2 packets transmitted, 2 packets received, 0% packet loss\n"
+"round-trip min/avg/max = 92.0/105.8/119.6 ms\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):367
+msgid ""
+"On the user-mode system we assign the user-mode eth0 interface the private "
+"IP address 192.168.0.1 and bring up the interface. The host has private IP "
+"address 192.168.0.254, and we ping it to make sure that our networking is, "
+"indeed, up. The route line adds a default gateway, namely our host, we use "
+"scp to retrieve a working <path>/etc/resolv.conf</path> (if necessary), and "
+"we ping www.gentoo.org to make sure that name resolution (and general access "
+"to the internet) is working from our user-mode system. Now the user-mode "
+"system can <c>emerge</c> at will!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):382
+msgid "Using a Virtual Network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):385
+msgid ""
+"Before you get all too excited, this is not a virtual private network. It is "
+"a network that is only accessible by the UML instances. The <c>usermode-"
+"utilities</c> package provides a tool called <c>uml_switch</c> which defines "
+"the end points of the switch."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):392
+msgid "Activating end points of a UML switch"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):392
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(If the switch information should stay in the foreground:)</comment>\n"
+"$ <i>uml_switch -unix ~/tmp/switch.sock</i>\n"
+"\n"
+"<comment>(If it should be backgrounded:)</comment>\n"
+"$ <i>uml_switch -unix ~/tmp/switch.sock &amp;&gt; ~/tmp/switch.log &amp;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):400
+msgid ""
+"To start the UML instances on the switch, run the next command. Your "
+"(virtual) network interface will be connected to the <c>uml_switch</c> "
+"process and will be using the given MAC address."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):406
+msgid "Running first UML instance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):406
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>linux ubd0=first_rootfs ubd1=first_swapfs eth0=daemon,10:00:01:02:00:00,,~/tmp/switch.sock</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):410
+msgid ""
+"You can still connect the system to the existing network, or have a second "
+"process attached to both the virtual one and the existing one:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):415
+msgid "Running second UML instance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):415
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>linux ubd0=second_rootfs ubd1=second_swapfs eth0=daemon,10:00:01:02:00:01,,~/tmp/switch.sock \\\n"
+"  eth1=tuntap,,,192.168.1.43</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):420
+msgid ""
+"More information about the tuntap setting can be found in the previous "
+"section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):428
+msgid "Testing the .iso"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):432
+msgid ""
+"Perhaps the true ideal of Gentoo Linux testing would be to boot the .iso "
+"with user-mode Linux and do the complete Gentoo install from within the user-"
+"mode Linux virtual system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):438
+msgid ""
+"Booting the .iso, or actually the initrd from the .iso, is pretty "
+"straightforward."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):443
+msgid "Booting the ISO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):443
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount -o loop /path/to/install-&lt;TAB&gt;.iso /mnt/loop</i>\n"
+"# <i>cp /mnt/loop/isolinux/gentoo.igz .</i>\n"
+"# <i>linux load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=22000 \\</i>\n"
+"&gt; <i>initrd=rescue.gz root=/dev/ram0 ubd0=root_fs ubd1=swap_fs \\</i>\n"
+"&gt; <i>ubd2=/dev/cdroms/cdrom0 eth0=tuntap,,,192.168.0.254</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):451
+msgid ""
+"Now you can follow the Gentoo install doc essentially verbatim, although "
+"you'll need to know that the root filesystem will be <path>/dev/ubd/0</"
+"path>, the swap \"partition\" will be <path>/dev/ubd/1</path>, and the CD "
+"rom will be <path>/dev/ubd/2</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):464
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri:link):470
+msgid "http://edeca.net/articles/bridging/index.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri):470
+msgid "Bridging with UML"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri:link):474
+msgid "http://user-mode-linux.sourceforge.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri):474
+msgid "UML Homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri:link):477
+msgid "http://www.theshore.net/~caker/uml/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri):477
+msgid "Caker's UML Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri:link):480
+msgid "http://sourceforge.net/mailarchive/forum.php?forum_id=3647"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri):480
+msgid "UML Mailinglist archives"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/usb-guide.xml.po b/doc/gettext/ru/usb-guide.xml.po
new file mode 100644
index 0000000..d94878f
--- /dev/null
+++ b/doc/gettext/ru/usb-guide.xml.po
@@ -0,0 +1,631 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(guide:link):5
+msgid "/doc/en/usb-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):6
+msgid "Gentoo Linux USB Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(mail:link):9
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(mail):9
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(abstract):12
+msgid ""
+"This document helps a user setup USB on a Gentoo system and configure "
+"various USB devices as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(version):21
+msgid "1.15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(date):22
+msgid "2009-11-29"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):25
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):27
+msgid "What is USB?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):30
+msgid ""
+"USB stands for Universal Serial Bus and is basically an external interface "
+"standard that enables communication between the computer and various other "
+"peripherals. Some of the most commonly used USB devices today are keyboards, "
+"mice, pen drives, digital cameras, external CD &amp; DVD writers, printers "
+"etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):37
+msgid ""
+"There are currently two versions of USB in use, i.e. USB 1.1 and USB 2.0. "
+"Since USB has always been backward compatible with its previous versions, "
+"USB 2.0 is backwards compatible with USB 1.1. The latest USB devices are "
+"typically USB 2.0 compatible. USB 2.0 supports a maximum data transmission "
+"speed of 480 Mbps or 60 MBps and this is the major difference between the "
+"two standards. Another advantage with USB is that the devices are all <e>hot-"
+"pluggable</e>, which means that you do not have to restart your system in "
+"order for you to be able to use these devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):51
+msgid "A Technical Perspective"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):54
+msgid ""
+"Before we go onto the exact configuration options in the kernel, it would be "
+"apt to look at USB in a little more detail. If you're in a hurry or want to "
+"skip this section, please go to <uri link=\"#kernel\">Kernel Configuration</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):61
+msgid ""
+"A USB system has a host controller, hubs, a <e>root hub</e> amongst others "
+"and can support up to 127 USB devices including the hubs. The host "
+"controller is nothing but the hardware interface between the USB device and "
+"the operating system. There are a couple of HCI (Host Controller Interface) "
+"in use today and they are the OHCI (Open HCI) by Compaq, UHCI (Universal "
+"HCI) and EHCI (Enhanced HCI), both from Intel. The OHCI/UHCI are the two "
+"industry standard USB 1.1 interfaces whereas the EHCI is for USB 2.0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):71
+msgid ""
+"The hardware vendor provides an interface for the programmer that allows the "
+"system to interact with the hardware and this is called the HCD or Host "
+"Controller Device. It is through this HCD that the device interacts with the "
+"system software. The following diagram should make things easier to "
+"comprehend."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):78
+msgid "General USB Architecture"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):78
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Software consists of other components as well like the device driver, but\n"
+"for the sake of simplicity, they are not shown)</comment>\n"
+"\n"
+"    + ----  Hardware  ----   + ----  Software  ---- +\n"
+"    |                        |                      |\n"
+"    | [USB Dev] -+-&gt; {EHCI} -+---&gt;  ( EHCD )        |\n"
+"    |            |           |                      |  User\n"
+"    |            `-&gt; {UHCI} -+---&gt;  ( UHCD )        |\n"
+"    |                        |                      |\n"
+"    + ----  Hardware  ----   + ----  Software  ---- +\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):91
+msgid ""
+"A USB device can either use a custom driver or use one already present in "
+"the system and this is based on the concept of a device <e>class</e>. This "
+"means that if a device belongs to a certain <e>class</e>, then other devices "
+"belonging to the same <e>class</e> can make use of the same device driver. "
+"Some of these <e>classes</e> are the USB HID (Human Interface Devices) class "
+"which covers input devices like keyboards and mice, the USB Mass Storage "
+"devices class which covers devices like pen drives, digital cameras, audio "
+"players etc and the USB CDC (Communication Devices Class) which essentially "
+"covers USB modems and similar devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):106
+msgid "What's on your machine?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):109
+msgid ""
+"It is very simple to find out whether your machine has USB 2.0 support or "
+"not. We make use of the <c>lspci</c> command for this purpose."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):114
+msgid ""
+"The <c>lspci</c> tool is a part of the <c>sys-apps/pciutils</c> package. If "
+"you do not have this installed, please <c>emerge pciutils</c>. Please note "
+"that you have to be root while running the <c>lspci</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):120
+msgid "Various lspci outputs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):120
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(In system that is USB 1.1 compliant, note the UHCI only)</comment>\n"
+"\n"
+"# <i>lspci -v | grep USB</i>\n"
+"0000:00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])\n"
+"\n"
+"<comment>(A system that is USB 2.0 compliant, note the EHCI and UHCI)</comment>\n"
+"\n"
+"00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 01) (prog-if 00 [UHCI])\n"
+"00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 01) (prog-if 00 [UHCI])\n"
+"00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 01) (prog-if 00 [UHCI])\n"
+"00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 01) (prog-if 20 [EHCI])\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):134
+msgid ""
+"So using the <c>lspci</c> command, we can find out if the system supports "
+"USB 2.0. This is useful as we will be enabling the corresponding options in "
+"the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):145
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):147
+msgid "Getting the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):150
+msgid ""
+"First emerge the kernel sources of your choice. Here we'll use the <c>gentoo-"
+"sources</c>. For more information on the various kernel sources available on "
+"Portage, please look up the <uri link=\"/doc/en/gentoo-kernel.xml\">Gentoo "
+"Linux Kernel Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):157
+msgid "Getting the kernel sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):157
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gentoo-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):161
+msgid "Now, lets get on with the task of configuring the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):165
+msgid "Heading over to the source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):165
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):170
+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//usb-guide.xml(title):178
+msgid "Config options for the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):181
+msgid ""
+"Now we will look at some of the options we will have to enable in the kernel "
+"to ensure proper USB support for our devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):186
+msgid ""
+"Examples in this document will show configuration options for basic USB "
+"support as well as those needed commonly, for example a USB mass storage "
+"device (most cameras and USB pen drives). If you have a specific USB device "
+"that needs to be configured, please look up your device's manual or search "
+"online to see if that device has support built-in into the kernel or custom "
+"drivers that you can use. Please note that for the sake of ease, all "
+"examples have the options compiled into the kernel. If you would like to "
+"have a modular kernel, ensure that you note down the various modules and "
+"adjust your config files accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):198
+msgid "make menuconfig options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):198
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+"  SCSI device support  ---&gt;\n"
+"\n"
+"<comment>(Although SCSI will be enabled automatically when selecting USB Mass Storage,\n"
+"we need to enable disk support.)</comment>\n"
+"---   SCSI support type (disk, tape, CD-ROM)\n"
+"&lt;*&gt;   SCSI disk support\n"
+"\n"
+"<comment>(Then move back a level and go into USB support)</comment>\n"
+"USB support  ---&gt;\n"
+"\n"
+"<comment>(This is the root hub and is required for USB support.\n"
+"If you'd like to compile this as a module, it will be called usbcore.)</comment>\n"
+"&lt;*&gt; Support for Host-side USB\n"
+"\n"
+"<comment>(Select at least one of the HCDs. If you are unsure, picking all is fine.)</comment>\n"
+"--- USB Host Controller Drivers\n"
+"&lt;*&gt; EHCI HCD (USB 2.0) support\n"
+"&lt; &gt; OHCI HCD support\n"
+"&lt;*&gt; UHCI HCD (most Intel and VIA) support\n"
+"\n"
+"<comment>(Moving a little further down, we come to CDC and mass storage.)</comment>\n"
+"&lt; &gt; USB Modem (CDC ACM) support\n"
+"&lt;*&gt; USB Printer support\n"
+"&lt;*&gt; USB Mass Storage support\n"
+"\n"
+"<comment>(If you have a USB Network Card like the RTL8150, you'll need this)</comment>\n"
+"USB Network Adapters  ---&gt;\n"
+"    &lt;*&gt; USB RTL8150 based ethernet device support (EXPERIMENTAL)\n"
+"\n"
+"<comment>(If you have a serial to USB converter like the Prolific 2303, you'll need this)</comment>\n"
+"USB Serial Converter support  ---&gt;\n"
+"    &lt;*&gt; USB Serial Converter support\n"
+"    &lt;*&gt; USB Prolific 2303 Single Port Serial Driver (NEW)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):235
+msgid ""
+"If you have a USB keyboard, mouse, joystick, or any other input device, you "
+"need to enable HID support. Go back one level to \"Device drivers\" and "
+"enable HID support as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):241
+msgid "Enabling HID support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):241
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"  [*] HID Devices  ---&gt;\n"
+"    &lt;*&gt;   USB Human Interface Device (full HID) support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):247
+msgid ""
+"Now that your options are set, you can (re)compile the kernel and USB "
+"support should be functional once you reboot into the new kernel. You can "
+"now proceed to <uri link=\"#postkern\">Seeing USB at work</uri> and see if "
+"everything is working as it should."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):259
+msgid "Seeing USB at work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):261
+msgid "dmesg is your friend!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):264
+msgid ""
+"The time has finally come to play with those USB devices :) So let's get "
+"started. In this chapter, we'll see how the system responds to various USB "
+"devices. We'll start by plugging in a USB 512 MB Memory Stick/Pen Drive. You "
+"could use some other similar mass storage device. We will primarily use "
+"<c>dmesg</c> to see what is happening and how the system responds to the "
+"device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):273
+msgid ""
+"<c>dmesg</c> will generally give a lot of output up front before coming to "
+"the info we need, as it reads the kernel ring buffer that has all the boot "
+"up messages as well. The output in the following examples have only the "
+"relevant portion(s) and extra spaces in between to enable better "
+"readability. If needed please use a <c>dmesg | more</c> or <c>dmesg | less</"
+"c> to see the output better in your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):282
+msgid "dmesg output for Memory Stick"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):282
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Plug in Memory Stick into available USB port and then..)</comment>\n"
+"# <i>dmesg | less</i>\n"
+"\n"
+"<comment>(The device is picked up as a USB 1.1 and allocated an address.\n"
+"Also says what HCD it is using.)</comment>\n"
+"usb 1-1: new full speed USB device using uhci_hcd and address 2\n"
+"\n"
+"<comment>(SCSI emulation automatically kicks in)</comment>\n"
+"scsi0 : SCSI emulation for USB Mass Storage devices\n"
+"usb-storage: device found at 2\n"
+"\n"
+"<comment>(Now the device information including model number is retrieved)</comment>\n"
+"usb-storage: waiting for device to settle before scanning\n"
+"  Vendor: JetFlash  Model: TS512MJF2A        Rev: 1.00\n"
+"  Type:   Direct-Access                      ANSI SCSI revision: 02\n"
+"SCSI device sda: 1003600 512-byte hdwr sectors (514 MB)\n"
+"\n"
+"<comment>(The write-protect sense is EXPERIMENTAL code in the later kernels)</comment>\n"
+"sda: Write Protect is off\n"
+"sda: Mode Sense: 0b 00 00 08\n"
+"sda: assuming drive cache: write through\n"
+"SCSI device sda: 1003600 512-byte hdwr sectors (514 MB)\n"
+"/dev/scsi/host0/bus0/target0/lun0: p1\n"
+"Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0\n"
+"Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0\n"
+"usb-storage: device scan complete\n"
+"<comment>(At this point, the device is generally accessible by mounting /dev/sda1)</comment>\n"
+"\n"
+"<comment>(When the device is disconnected, the system acknowledges the same)</comment>\n"
+"usb 1-1: USB disconnect, address 2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):315
+msgid ""
+"Once the device is connected and mounted, you can access it like a normal "
+"hard disk. Usual operations like <c>cp</c>, <c>mv</c>, <c>rm</c>, etc work "
+"fine. You could also create a filesystem on the USB stick/format it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):321
+msgid "Accessing the Memory Stick"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):321
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount /dev/sda1 /mnt/usb</i>\n"
+"# <i>df -h</i>\n"
+"Filesystem            Size  Used Avail Use% Mounted on\n"
+"/dev/hda8             9.4G  7.5G  1.9G  80% /\n"
+"/dev/hda9              11G  8.1G  2.4G  78% /usr\n"
+"none                  189M     0  189M   0% /dev/shm\n"
+"/dev/sda1             490M   34M  457M   7% /mnt/usb\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):331
+msgid ""
+"Digital cameras can be accessed the same way as memory sticks. I have a "
+"Nikon Coolpix 5200 and this is the way I access it. Cameras these days "
+"usually have two modes to transfer pictures; USB mass storage and PTP "
+"(Picture Transfer Protocol). The camera is set to USB mass storage mode and "
+"hence the procedure is exactly the same as that of accessing a memory stick "
+"because of which I have not explained in detail about it. Please note that "
+"this may NOT work in all cases and with all digital cameras that have USB "
+"support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):341
+msgid ""
+"How would a USB mouse show up in case you had one? It will show up as an HID "
+"device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):346
+msgid "USB Optical Mouse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):346
+#, no-wrap
+msgid ""
+"\n"
+"# <i>dmesg | grep USB</i>\n"
+"drivers/usb/input/hid-core.c: v2.0:USB HID core driver\n"
+"usb 1-1: new low speed USB device using address 2\n"
+"input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:07.2-1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):353
+msgid ""
+"Another nifty command you can use to see the status of your USB ports is "
+"<c>lsusb</c>. This is part of <c>sys-apps/usbutils</c> and will be covered "
+"in the next chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):364
+msgid "Userspace USB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):366
+msgid "Nifty tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):369
+msgid ""
+"So far we've seen how much support exists on the kernel/system side for USB "
+"on Linux. Now we'll take a peek into what kind of support is provided by "
+"Gentoo for USB in the userspace."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):375
+msgid ""
+"One of the most useful tools around is <c>lsusb</c>. This lists all the usb "
+"devices connected to the system. Installing it is a breeze."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):380
+msgid "Installing usbutils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):380
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge usbutils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):384
+msgid ""
+"Once installed, you can just run <c>lsusb</c> to get simple info on the USB "
+"devices attached to the machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):389
+msgid "You have to be root in most cases to run <c>lsusb</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(warn):393
+msgid ""
+"<c>lsusb</c> reads the information for the USB devices from <path>/proc/bus/"
+"usb</path>. If you have not enabled that in your kernel, chances are that "
+"<c>lsusb</c> may not work at all. Please ensure you have <path>/proc</path> "
+"filesystem support enabled in your kernel and that <c>usbfs</c> is mounted "
+"at <path>/proc/bus/usb</path> (which should happen automatically)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):402
+msgid "lsusb at work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):402
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lsusb</i>\n"
+"<comment>(This is the 512 MB Memory Stick from Transcend)</comment>\n"
+"Bus 001 Device 003: ID 0c76:0005 JMTek, LLC. USBdisk\n"
+"<comment>(This is the Optical Mouse)</comment>\n"
+"Bus 001 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse\n"
+"<comment>(This is the root hub)</comment>\n"
+"Bus 001 Device 001: ID 0000:0000\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):412
+msgid ""
+"If you are one of those types who love to see lots of information, you have "
+"the option of running <c>lsusb -v</c>. Try that and see the amount of info "
+"it gives out. Another good option is that <c>lsusb</c> dumps the current "
+"physical USB hierarchy as a tree and thus makes it easier to understand the "
+"exact device map. The command is <c>lsusb -t</c>. For example,"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):420
+msgid "lsusb showing USB hierarchy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):420
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lsusb -t</i>\n"
+"Bus#  1\n"
+"`-Dev#   1 Vendor 0x0000 Product 0x0000\n"
+"  |-Dev#   2 Vendor 0x046d Product 0xc00e\n"
+"  `-Dev#   3 Vendor 0x0c76 Product 0x0005\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):428
+msgid ""
+"You can easily correlate the outputs of <c>lsusb</c> and <c>lsusb -t</c>, "
+"which helps debugging as well as understanding how USB works."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):438
+msgid "And thanks to..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):440
+msgid "References"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):443
+msgid ""
+"A good number of online documents helped me during the development of this "
+"document and there are some that are highly technical but truly interesting. "
+"I thought they all deserve some credit, so here we go!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):450
+msgid "http://www.usb.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):450
+msgid "The Official USB Website"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):451
+msgid "http://www.usb.org/about/faq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):451
+msgid "The USB FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):454
+msgid "http://h18000.www1.hp.com/productinfo/development/openhci.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):454
+msgid "Compaq's OHCI Standard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):458
+msgid "http://developer.intel.com/technology/usb/uhci11d.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):458
+msgid "Intel's UHCI Standard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):462
+msgid "http://www.intel.com/technology/usb/ehcispec.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):462
+msgid "Intel's EHCI Standard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):470
+msgid "Other Interesting Links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):474
+msgid "/doc/en/liveusb.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):474
+msgid "Gentoo Linux LiveUSB HOWTO"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/utf-8.xml.po b/doc/gettext/ru/utf-8.xml.po
new file mode 100644
index 0000000..322aac5
--- /dev/null
+++ b/doc/gettext/ru/utf-8.xml.po
@@ -0,0 +1,1116 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):6
+msgid "Using UTF-8 with Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail:link):9
+msgid "slarti@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail):9
+msgid "Thomas Martin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(author:title):11
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail:link):12
+msgid "devil@gentoo.org.ua"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail):12
+msgid "Alexander Simonov"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail:link):15
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail):15
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail:link):18
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(abstract):21
+msgid ""
+"This guide shows you how to set up and use the UTF-8 Unicode character set "
+"with your Gentoo Linux system, after explaining the benefits of Unicode and "
+"more specifically UTF-8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(version):31
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(date):32
+msgid "2010-09-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):35
+msgid "Character Encodings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):37
+msgid "What is a Character Encoding?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):40
+msgid ""
+"Computers do not understand text themselves. Instead, every character is "
+"represented by a number. Traditionally, each set of numbers used to "
+"represent alphabets and characters (known as a coding system, encoding or "
+"character set) was limited in size due to limitations in computer hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):50
+msgid "The History of Character Encodings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):53
+msgid ""
+"The most common (or at least the most widely accepted) character set is "
+"<b>ASCII</b> (American Standard Code for Information Interchange). It is "
+"widely held that ASCII is the most successful software standard ever. Modern "
+"ASCII was standardised in 1986 (ANSI X3.4, RFC 20, ISO/IEC 646:1991, ECMA-6) "
+"by the American National Standards Institute."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):61
+msgid ""
+"ASCII is strictly seven-bit, meaning that it uses bit patterns representable "
+"with seven binary digits, which provides a range of 0 to 127 in decimal. "
+"These include 32 non-visible control characters, most between 0 and 31, with "
+"the final control character, DEL or delete at 127. Characters 32 to 126 are "
+"visible characters: a space, punctuation marks, Latin letters and numbers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):69
+msgid ""
+"The eighth bit in ASCII was originally used as a parity bit for error "
+"checking. If this is not desired, it is left as 0. This means that, with "
+"ASCII, each character is represented by a single byte."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):75
+msgid ""
+"Although ASCII was enough for communication in modern English, in other "
+"European languages that include accented characters, things were not so "
+"easy. The ISO 8859 standards were developed to meet these needs. They were "
+"backwards compatible with ASCII, but instead of leaving the eighth bit "
+"blank, they used it to allow another 127 characters in each encoding. ISO "
+"8859's limitations soon came to light, and there are currently 15 variants "
+"of the ISO 8859 standard (8859-1 through to 8859-15). Outside of the ASCII-"
+"compatible byte range of these character sets, there is often conflict "
+"between the letters represented by each byte. To complicate interoperability "
+"between character encodings further, Windows-1252 is used in some versions "
+"of Microsoft Windows instead for Western European languages. This is a "
+"superset of ISO 8859-1, however it is different in several ways. These sets "
+"do all retain ASCII compatibility, however."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):91
+msgid ""
+"The necessary development of completely different single-byte encodings for "
+"non-Latin alphabets, such as EUC (Extended Unix Coding) which is used for "
+"Japanese and Korean (and to a lesser extent Chinese) created more confusion, "
+"while other operating systems still used different character sets for the "
+"same languages, for example, Shift-JIS and ISO-2022-JP. Users wishing to "
+"view cyrillic glyphs had to choose between KOI8-R for Russian and Bulgarian "
+"or KOI8-U for Ukrainian, as well as all the other cyrillic encodings such as "
+"the unsuccessful ISO 8859-5, and the common Windows-1251 set. All of these "
+"character sets broke most compatibility with ASCII (although KOI8 encodings "
+"place cyrillic characters in Latin order, so in case the eighth bit is "
+"stripped, text is still decipherable on an ASCII terminal through case-"
+"reversed transliteration.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):106
+msgid ""
+"This has led to confusion, and also to an almost total inability for "
+"multilingual communication, especially across different alphabets. Enter "
+"Unicode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):115
+msgid "What is Unicode?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):118
+msgid ""
+"Unicode throws away the traditional single-byte limit of character sets. It "
+"uses 17 \"planes\" of 65,536 code points to describe a maximum of 1,114,112 "
+"characters. As the first plane, aka. \"Basic Multilingual Plane\" or BMP, "
+"contains almost everything you will ever use, many have made the wrong "
+"assumption that Unicode was a 16-bit character set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):126
+msgid ""
+"Unicode has been mapped in many different ways, but the two most common are "
+"<b>UTF</b> (Unicode Transformation Format) and <b>UCS</b> (Universal "
+"Character Set). A number after UTF indicates the number of bits in one unit, "
+"while the number after UCS indicates the number of bytes. UTF-8 has become "
+"the most widespread means for the interchange of Unicode text as a result of "
+"its eight-bit clean nature, and it is the subject of this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):138
+msgid "UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):141
+msgid ""
+"UTF-8 is a variable-length character encoding, which in this instance means "
+"that it uses 1 to 4 bytes per symbol. So, the first UTF-8 byte is used for "
+"encoding ASCII, giving the character set full backwards compatibility with "
+"ASCII. UTF-8 means that ASCII and Latin characters are interchangeable with "
+"little increase in the size of the data, because only the first bit is used. "
+"Users of Eastern alphabets such as Japanese, who have been assigned a higher "
+"byte range are unhappy, as this results in as much as a 50% redundancy in "
+"their data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):155
+msgid "What UTF-8 Can Do for You"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):158
+msgid ""
+"UTF-8 allows you to work in a standards-compliant and internationally "
+"accepted multilingual environment, with a comparatively low data redundancy. "
+"UTF-8 is the preferred way for transmitting non-ASCII characters over the "
+"Internet, through Email, IRC or almost any other medium. Despite this, many "
+"people regard UTF-8 in online communication as abusive. It is always best to "
+"be aware of the attitude towards UTF-8 in a specific channel, mailing list "
+"or Usenet group before using <e>non-ASCII</e> UTF-8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):173
+msgid "Setting up UTF-8 with Gentoo Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):175
+msgid "Finding or Creating UTF-8 Locales"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):178
+msgid ""
+"Now that you understand the principles behind Unicode, you're ready to start "
+"using UTF-8 with your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):183
+msgid ""
+"The preliminary requirement for UTF-8 is to have a version of glibc "
+"installed that has national language support. The recommend means to do this "
+"is the <path>/etc/locale.gen</path> file. It is beyond the scope of this "
+"document to explain the usage of this file though. It is explained in the "
+"<uri link=\"/doc/en/guide-localization.xml#doc_chap3_sect3\">Gentoo "
+"Localization Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):192
+msgid ""
+"Next, we'll need to decide whether a UTF-8 locale is already available for "
+"our language, or whether we need to create one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):197
+msgid "Checking for an existing UTF-8 locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):197
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace \"en_GB\" with your desired locale setting)</comment>\n"
+"# <i>locale -a | grep 'en_GB'</i>\n"
+"en_GB\n"
+"en_GB.UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):204
+msgid ""
+"From the output of this command line, we need to take the result with a "
+"suffix similar to <c>.UTF-8</c>. If there is no result with a suffix similar "
+"to <c>.UTF-8</c>, we need to create a UTF-8 compatible locale."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):210
+msgid ""
+"Only execute the following code listing if you do not have a UTF-8 locale "
+"available for your language."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):215
+msgid "Creating a UTF-8 locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):215
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace \"en_GB\" with your desired locale setting)</comment>\n"
+"# <i>localedef -i en_GB -f UTF-8 en_GB.UTF-8</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):220
+msgid ""
+"Another way to include a UTF-8 locale is to add it to the <path>/etc/locale."
+"gen</path> file and generate necessary locales with <c>locale-gen</c> "
+"command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):226
+msgid "Line in /etc/locale.gen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):226
+#, no-wrap
+msgid ""
+"\n"
+"en_GB.UTF-8 UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):233
+msgid "Setting the Locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):236
+msgid ""
+"There is one environment variable that needs to be set in order to use our "
+"new UTF-8 locales: <c>LC_CTYPE</c> (or optionally <c>LANG</c>, if you want "
+"to change the system language as well). There are also many different ways "
+"to set it; some people prefer to only have a UTF-8 environment for a "
+"specific user, in which case they set them in their <path>~/.profile</path> "
+"(if you use <c>/bin/sh</c>), <path>~/.bash_profile</path> or <path>~/."
+"bashrc</path> (if you use <c>/bin/bash</c>). More details and best practices "
+"can be found in our <uri link=\"/doc/en/guide-localization.xml"
+"\">Localization Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):247
+msgid ""
+"Others prefer to set the locale globally. One specific circumstance where "
+"the author particularly recommends doing this is when <path>/etc/init.d/xdm</"
+"path> is in use, because this init script starts the display manager and "
+"desktop before any of the aforementioned shell startup files are sourced, "
+"and so before any of the variables are in the environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):256
+msgid ""
+"Setting the locale globally should be done using <path>/etc/env.d/02locale</"
+"path>. The file should look something like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):262
+msgid "Demonstration /etc/env.d/02locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):262
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(As always, change \"en_GB.UTF-8\" to your locale)</comment>\n"
+"LANG=\"en_GB.UTF-8\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):267
+msgid ""
+"You can also substitute <c>LC_CTYPE</c> for <c>LANG</c>. For more "
+"information on the categories affected by using <c>LC_CTYPE</c>, please read "
+"the <uri link=\"http://www.gnu.org/software/libc/manual/html_node/Locale-"
+"Categories.html#Locale-Categories\">GNU locale page</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):274
+msgid "Next, the environment must be updated with the change."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):278
+msgid "Updating the environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):278
+#, no-wrap
+msgid ""
+"\n"
+"# <i>env-update</i>\n"
+"&gt;&gt;&gt; Regenerating /etc/ld.so.cache...\n"
+" * Caching service dependencies ...\n"
+"# <i>source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):285
+msgid ""
+"Now, run <c>locale</c> with no arguments to see if we have the correct "
+"variables in our environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):290
+msgid "Checking if our new locale is in the environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):290
+#, no-wrap
+msgid ""
+"\n"
+"# <i>locale</i>\n"
+"LANG=en_GB.UTF-8\n"
+"LC_CTYPE=\"en_GB.UTF-8\"\n"
+"LC_NUMERIC=\"en_GB.UTF-8\"\n"
+"LC_TIME=\"en_GB.UTF-8\"\n"
+"LC_COLLATE=\"en_GB.UTF-8\"\n"
+"LC_MONETARY=\"en_GB.UTF-8\"\n"
+"LC_MESSAGES=\"en_GB.UTF-8\"\n"
+"LC_PAPER=\"en_GB.UTF-8\"\n"
+"LC_NAME=\"en_GB.UTF-8\"\n"
+"LC_ADDRESS=\"en_GB.UTF-8\"\n"
+"LC_TELEPHONE=\"en_GB.UTF-8\"\n"
+"LC_MEASUREMENT=\"en_GB.UTF-8\"\n"
+"LC_IDENTIFICATION=\"en_GB.UTF-8\"\n"
+"LC_ALL=\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):308
+msgid ""
+"That's everything. You are now using UTF-8 locales, and the next hurdle is "
+"the configuration of the applications you use from day to day."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):318
+msgid "Application Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):322
+msgid ""
+"When Unicode first started gaining momentum in the software world, multibyte "
+"character sets were not well suited to languages like C, in which many of "
+"the day-to-day programs people use are written. Even today, some programs "
+"are not able to handle UTF-8 properly. Fortunately, most are!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):332
+msgid "Filenames, NTFS, and FAT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):335
+msgid ""
+"There are several NLS options in the Linux kernel configuration menu, but it "
+"is important to not become confused! For the most part, the only thing you "
+"need to do is to build UTF-8 NLS support into your kernel, and change the "
+"default NLS option to utf8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):342
+msgid "Kernel configuration steps for UTF-8 NLS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):342
+#, no-wrap
+msgid ""
+"\n"
+"File Systems --&gt;\n"
+"  Native Language Support --&gt;\n"
+"    (utf8) Default NLS Option\n"
+"    &lt;*&gt; NLS UTF8\n"
+"    <comment>(Also &lt;*&gt; other character sets that are in use in\n"
+"    your FAT filesystems or Joilet CD-ROMs.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):351
+msgid ""
+"If you plan on mounting NTFS partitions, you may need to specify an <c>nls=</"
+"c> option with mount. If you plan on mounting FAT partitions, you may need "
+"to specify a <c>codepage=</c> option with mount. Optionally, you can also "
+"set a default codepage for FAT in the kernel configuration. Note that the "
+"<c>codepage</c> option with mount will override the kernel settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):359
+msgid "FAT settings in kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):359
+#, no-wrap
+msgid ""
+"\n"
+"File Systems --&gt;\n"
+"  DOS/FAT/NT Filesystems  --&gt;\n"
+"    (437) Default codepage for fat\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):365
+msgid ""
+"You should avoid setting <c>Default iocharset for fat</c> to UTF-8, as it is "
+"not recommended. Instead, you may want to pass the option utf8=true when "
+"mounting your FAT partitions. For further information, see <c>man mount</c> "
+"and the kernel documentation at <path>/usr/src/linux/Documentation/"
+"filesystems/vfat.txt</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):373
+msgid ""
+"For changing the encoding of filenames, <c>app-text/convmv</c> can be used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):377
+msgid "Example usage of convmv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):377
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --ask app-text/convmv</i>\n"
+"<comment>(Command format)</comment>\n"
+"# <i>convmv -f &lt;current-encoding&gt; -t utf-8 &lt;filename&gt;</i>\n"
+"<comment>(Substitute iso-8859-1 with the charset you are converting\n"
+"from)</comment>\n"
+"# <i>convmv -f iso-8859-1 -t utf-8 filename</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):386
+msgid ""
+"For changing the <e>contents</e> of files, use the <c>iconv</c> utility, "
+"bundled with <c>glibc</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):391
+msgid "Example usage of iconv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):391
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(substitute iso-8859-1 with the charset you are converting from)</comment>\n"
+"<comment>(Check the output is sane)</comment>\n"
+"# <i>iconv -f iso-8859-1 -t utf-8 filename</i>\n"
+"<comment>(Convert a file, you must create another file)</comment>\n"
+"# <i>iconv -f iso-8859-1 -t utf-8 filename &gt; newfile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):399
+msgid "<c>app-text/recode</c> can also be used for this purpose."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):406
+msgid "The System Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(impo):409
+msgid "You need &gt;=sys-apps/baselayout-1.11.9 for Unicode on the console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):413
+msgid ""
+"To enable UTF-8 on the console, you should edit <path>/etc/rc.conf</path> "
+"and set <c>UNICODE=\"yes\"</c>, and also read the comments in that file -- "
+"it is important to have a font that has a good range of characters if you "
+"plan on making the most of Unicode. For this to work, make sure you have "
+"properly created a Unicode locale as explained in <uri link="
+"\"#doc_chap1\">Chapter 1</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):422
+msgid ""
+"The <c>KEYMAP</c> variable, set in <path>/etc/conf.d/keymaps</path>, should "
+"have a Unicode keymap specified."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):427
+msgid "Example /etc/conf.d/keymaps snippet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):427
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Change \"uk\" to your local layout)</comment>\n"
+"KEYMAP=\"uk\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):435
+msgid "Ncurses and Slang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):438
+msgid ""
+"Ignore any mention of Slang in this section if you do not have it installed "
+"or do not use it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):443
+msgid ""
+"It is wise to add <c>unicode</c> to your global USE flags in <path>/etc/make."
+"conf</path>, and then to remerge <c>sys-libs/ncurses</c> and <c>sys-libs/"
+"slang</c> if appropriate. Portage will do this automatically when you update "
+"your system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):450
+msgid "Updating your system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):450
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --update --deep --newuse world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):454
+msgid ""
+"We also need to rebuild packages that link to these, now the USE changes "
+"have been applied. The tool we use (<c>revdep-rebuild</c>) is part of the "
+"<c>gentoolkit</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):460
+msgid "Rebuilding of programs that link to ncurses or slang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):460
+#, no-wrap
+msgid ""
+"\n"
+"# <i>revdep-rebuild --soname libncurses.so.5</i>\n"
+"# <i>revdep-rebuild --soname libslang.so.1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):468
+msgid "KDE, GNOME and Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):471
+msgid ""
+"All of the major desktop environments have full Unicode support, and will "
+"require no further setup than what has already been covered in this guide. "
+"This is because the underlying graphical toolkits (Qt or GTK+2) are UTF-8 "
+"aware. Subsequently, all applications running on top of these toolkits "
+"should be UTF-8-aware out of the box."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):479
+msgid ""
+"The exceptions to this rule come in Xlib and GTK+1. GTK+1 requires a "
+"iso-10646-1 FontSpec in the ~/.gtkrc, for example <c>-misc-fixed-*-*-*-*-*-*-"
+"*-*-*-*-iso10646-1</c>. Also, applications using Xlib or Xaw will need to be "
+"given a similar FontSpec, otherwise they will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):487
+msgid ""
+"If you have a version of the gnome1 control center around, use that instead. "
+"Pick any iso10646-1 font from there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):492
+msgid "Example ~/.gtkrc (for GTK+1) that defines a Unicode compatible font"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):492
+#, no-wrap
+msgid ""
+"\n"
+"style \"user-font\"\n"
+"{\n"
+"    fontset=\"-misc-fixed-*-*-*-*-*-*-*-*-*-*-iso10646-1\"\n"
+"}\n"
+"widget_class \"*\" style \"user-font\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):500
+msgid ""
+"If an application has support for both a Qt and GTK+2 GUI, the GTK+2 GUI "
+"will generally give better results with Unicode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):508
+msgid "X11 and Fonts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):511
+msgid ""
+"TrueType fonts have support for Unicode, and most of the fonts that ship "
+"with Xorg have impressive character support, although, obviously, not every "
+"single glyph available in Unicode has been created for that font. To build "
+"fonts (including the Bitstream Vera set) with support for East Asian letters "
+"with X, make sure you have the <c>cjk</c> USE flag set. Many other "
+"applications utilise this flag, so it may be worthwhile to add it as a "
+"permanent USE flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):520
+msgid "Also, several font packages in Portage are Unicode aware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):524
+msgid "Optional: Install some more Unicode-aware fonts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):524
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge terminus-font intlfonts freefonts corefonts</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):531
+msgid "Window Managers and Terminal Emulators"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):534
+msgid ""
+"Window managers not built on GTK or Qt generally have very good Unicode "
+"support, as they often use the Xft library for handling fonts. If your "
+"window manager does not use Xft for fonts, you can still use the FontSpec "
+"mentioned in the previous section as a Unicode font."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):541
+msgid ""
+"Terminal emulators that use Xft and support Unicode are harder to come by. "
+"Aside from Konsole and gnome-terminal, the best options in Portage are "
+"<c>x11-terms/rxvt-unicode</c>, <c>x11-terms/terminal</c>, <c>gnustep-apps/"
+"terminal</c>, <c>x11-terms/mlterm</c>, or plain <c>x11-terms/xterm</c> when "
+"built with the <c>unicode</c> USE flag and invoked as <c>uxterm</c>. <c>app-"
+"misc/screen</c> supports UTF-8 too, when invoked as <c>screen -U</c> or the "
+"following is put into the <path>~/.screenrc</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):551
+msgid "~/.screenrc for UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):551
+#, no-wrap
+msgid ""
+"\n"
+"defutf8 on\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):558
+msgid "Vim, Emacs, Xemacs and Nano"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):561
+msgid ""
+"Vim provides full UTF-8 support, and also has builtin detection of UTF-8 "
+"files. For further information in Vim, use <c>:help mbyte.txt</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):566
+msgid ""
+"Emacs 22.x and higher has full UTF-8 support as well. Xemacs 22.x does not "
+"support combining characters yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):571
+msgid ""
+"Lower versions of Emacs and/or Xemacs might require you to install <c>app-"
+"emacs/mule-ucs</c> and/or <c>app-xemacs/mule-ucs</c> and add the following "
+"code to your <path>~/.emacs</path> to have support for CJK languages in "
+"UTF-8:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):578
+msgid "Emacs CJK UTF-8 support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):578
+#, no-wrap
+msgid ""
+"\n"
+"(require 'un-define)\n"
+"(require 'jisx0213)\n"
+"(set-language-environment \"Japanese\")\n"
+"(set-default-coding-systems 'utf-8)\n"
+"(set-terminal-coding-system 'utf-8)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):586
+msgid "Nano has provided full UTF-8 support since version 1.3.6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):593
+msgid "Shells"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):596
+msgid ""
+"Currently, <c>bash</c> provides full Unicode support through the GNU "
+"readline library. Z Shell (<c>zsh</c>) offers Unicode support with the "
+"<c>unicode</c> USE flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):602
+msgid ""
+"The C shell, <c>tcsh</c> and <c>ksh</c> do not provide UTF-8 support at all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):609
+msgid "Irssi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):612
+msgid ""
+"Irssi has complete UTF-8 support, although it does require a user to set an "
+"option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):617
+msgid "Enabling UTF-8 in Irssi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):617
+#, no-wrap
+msgid ""
+"\n"
+"/set term_charset UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):621
+msgid ""
+"For channels where non-ASCII characters are often exchanged in non-UTF-8 "
+"charsets, the <c>/recode</c> command may be used to convert the characters. "
+"Type <c>/help recode</c> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):630
+msgid "Mutt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):633
+msgid ""
+"The Mutt mail user agent has very good Unicode support. To use UTF-8 with "
+"Mutt, you don't need to put anything in your configuration files. Mutt will "
+"work under unicode enviroment without modification if all your configuration "
+"files (signature included) are UTF-8 encoded."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):640
+msgid ""
+"You may still see '?' in mail you read with Mutt. This is a result of people "
+"using a mail client which does not indicate the used charset. You can't do "
+"much about this than to ask them to configure their client correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):646
+msgid ""
+"Further information is available from the <uri link=\"http://wiki.mutt.org/"
+"index.cgi?MuttFaq/Charset\">Mutt Wiki</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):654
+msgid "Man"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):657
+msgid ""
+"Man pages are an integral part of any Linux machine. To ensure that any "
+"unicode in your man pages render correctly, edit <path>/etc/man.conf</path> "
+"and replace a line as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):663
+msgid "man.conf changes for Unicode support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):663
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(This is the old line)</comment>\n"
+"NROFF           /usr/bin/nroff -Tascii -c -mandoc\n"
+"<comment>(Replace the one above with this)</comment>\n"
+"NROFF           /usr/bin/nroff -mandoc -c\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):673
+msgid "elinks and links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):676
+msgid ""
+"These are commonly used text-based browsers, and we shall see how we can "
+"enable UTF-8 support on them. On <c>elinks</c> and <c>links</c>, there are "
+"two ways to go about this, one using the Setup option from within the "
+"browser or editing the config file. To set the option through the browser, "
+"open a site with <c>elinks</c> or <c>links</c> and then <c>Alt+S</c> to "
+"enter the Setup Menu then select Terminal options, or press <c>T</c>. Scroll "
+"down and select the last option <c>UTF-8 I/O</c> by pressing Enter. Then "
+"Save and exit the menu. On <c>links</c> you may have to do a repeat <c>Alt"
+"+S</c> and then press <c>S</c> to save. The config file option, is shown "
+"below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):688
+msgid "Enabling UTF-8 for elinks/links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):688
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(For elinks, edit /etc/elinks/elinks.conf or ~/.elinks/elinks.conf and\n"
+"add the following line)</comment>\n"
+"set terminal.linux.utf_8_io = 1\n"
+"\n"
+"<comment>(For links, edit ~/.links/links.cfg and add the following\n"
+"line)</comment>\n"
+"terminal \"xterm\" 0 1 0 us-ascii utf-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):701
+msgid "Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):704
+msgid ""
+"Samba is a software suite which implements the SMB (Server Message Block) "
+"protocol for UNIX systems such as Macs, Linux and FreeBSD. The protocol is "
+"also sometimes referred to as the Common Internet File System (CIFS). Samba "
+"also includes the NetBIOS system - used for file sharing over windows "
+"networks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):711
+msgid "Enabling UTF-8 for Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):711
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Edit /etc/samba/smb.conf and add the following under the [global] section)</comment>\n"
+"dos charset = 1255\n"
+"unix charset = UTF-8\n"
+"display charset = UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):721
+msgid "Testing it all out"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):724
+msgid ""
+"There are numerous UTF-8 test websites around. <c>net-www/w3m</c>, <c>net-"
+"www/links</c>, <c>net-www/elinks</c>, <c>net-www/lynx</c> and all Mozilla "
+"based browsers (including Firefox) support UTF-8. Konqueror and Opera have "
+"full UTF-8 support too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):731
+msgid ""
+"When using one of the text-only web browsers, make absolutely sure you are "
+"using a Unicode-aware terminal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):736
+msgid ""
+"If you see certain characters displayed as boxes with letters or numbers "
+"inside, this means that your font does not have a character for the symbol "
+"or glyph that the UTF-8 wants. Instead, it displays a box with the hex code "
+"of the UTF-8 symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):745
+msgid "http://www.w3.org/2001/06/utf-8-test/UTF-8-demo.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):745
+msgid "A W3C UTF-8 Test Page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):749
+msgid "http://titus.uni-frankfurt.de/indexe.htm?/unicode/unitest.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):749
+msgid "A UTF-8 test page provided by the University of Frankfurt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):757
+msgid "Input Methods"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):760
+msgid ""
+"<e>Dead keys</e> may be used to input characters in X that are not included "
+"on your keyboard. These work by pressing your right Alt key (or in some "
+"countries, AltGr) and an optional key from the non-alphabetical section of "
+"the keyboard to the left of the return key at once, releasing them, and then "
+"pressing a letter. The dead key should modify it. Input can be further "
+"modified by using the Shift key at the same time as pressing the AltGr and "
+"modifier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):769
+msgid ""
+"To enable dead keys in X, you need a layout that supports it. Most European "
+"layouts already have dead keys with the default variant. However, this is "
+"not true of North American layouts. Although there is a degree of "
+"inconsistency between layouts, the easiest solution seems to be to use a "
+"layout in the form \"en_US\" rather than \"us\", for example. The layout is "
+"set in <path>/etc/X11/xorg.conf</path> like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):778
+msgid "/etc/X11/xorg.conf snippet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):778
+#, no-wrap
+msgid ""
+"\n"
+"Section \"InputDevice\"\n"
+"    Identifier \"Keyboard0\"\n"
+"    Driver     \"kbd\"\n"
+"    Option     \"XkbLayout\" \"en_US\" <comment># Rather than just \"us\"</comment>\n"
+"    <comment>(Other Xkb options here)</comment>\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):787
+msgid ""
+"The preceding change only needs to be applied if you are using a North "
+"American layout, or another layout where dead keys do not seem to be "
+"working. European users should have working dead keys as is."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):793
+msgid ""
+"This change will come into effect when your X server is restarted. To apply "
+"the change now, use the <c>setxkbmap</c> tool, for example, <c>setxkbmap "
+"en_US</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):798
+msgid ""
+"It is probably easiest to describe dead keys with examples. Although the "
+"results are locale dependent, the concepts should remain the same regardless "
+"of locale. The examples contain UTF-8, so to view them you need to either "
+"tell your browser to view the page as UTF-8, or have a UTF-8 locale already "
+"configured."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):806
+msgid ""
+"When I press AltGr and [ at once, release them, and then press a, 'ä' is "
+"produced. When I press AltGr and [ at once, and then press e, 'ë' is "
+"produced. When I press AltGr and ; at once, 'á' is produced, and when I "
+"press AltGr and ; at once, release them, and then press e, 'é' is produced."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):813
+msgid ""
+"By pressing AltGr, Shift and [ at once, releasing them, and then pressing a, "
+"a Scandinavian 'å' is produced. Similarly, when I press AltGr, Shift and "
+"[ at once, release <e>only</e> the [, and then press it again, '˚' is "
+"produced. Although it looks like one, this (U+02DA) is not the same as a "
+"degree symbol (U+00B0). This works for other accents produced by dead keys — "
+"AltGr and [, releasing only the [, then pressing it again makes '¨'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):822
+msgid ""
+"AltGr can be used with alphabetical keys alone. For example, AltGr and m, a "
+"Greek lower-case letter mu is produced: 'µ'. AltGr and s produce a scharfes "
+"s or esszet: 'ß'. As many European users would expect (because it is marked "
+"on their keyboard), AltGr and 4 (or E depending on the keyboard layout) "
+"produces a Euro sign, '€'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):833
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):838
+msgid "http://en.wikipedia.org/wiki/Unicode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):838
+msgid "The Wikipedia entry for Unicode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):842
+msgid "http://en.wikipedia.org/wiki/UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):842
+msgid "The Wikipedia entry for UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):845
+msgid "http://www.unicode.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):845
+msgid "Unicode.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):846
+msgid "http://www.utf-8.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):846
+msgid "UTF-8.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):847
+msgid "http://www.ietf.org/rfc/rfc3629.txt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):847
+msgid "RFC 3629"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):848
+msgid "http://www.ietf.org/rfc/rfc2277.txt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):848
+msgid "RFC 2277"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):851
+msgid "http://www.tbray.org/ongoing/When/200x/2003/04/26/UTF"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):851
+msgid "Characters vs. Bytes"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/vdr-guide.xml.po b/doc/gettext/ru/vdr-guide.xml.po
new file mode 100644
index 0000000..ae207a3
--- /dev/null
+++ b/doc/gettext/ru/vdr-guide.xml.po
@@ -0,0 +1,937 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(guide:link):5
+msgid "/doc/en/vdr-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):6
+msgid "Gentoo Linux VDR Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(author:title):14
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail:link):9
+msgid "ng@zcat.de"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail):9
+msgid "Norman Golisz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail:link):12
+msgid "diox@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail):12
+msgid "Dimitry Bradt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail:link):15
+msgid "zzam@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail):15
+msgid "Matthias Schwarzott"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail:link):18
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail):18
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(abstract):21
+msgid "This guide shows you how to prepare Gentoo Linux for DVB and VDR."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(version):29
+msgid "1.8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(date):30
+msgid "2008-09-28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):33
+msgid "General information to DVB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):35
+msgid "What is DVB?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):38
+msgid ""
+"<e>DVB</e> stands for <e>Digital Video Broadcasting</e>. DVB describes "
+"methods to transfer digital data of TV, radio, interactive services like "
+"MHP, EPG and teletext. Through data compression with MPEG-2, or H.264 for "
+"HDTV, it's possible to transfer several channels on the same frequency. The "
+"more data compression, the more channels can be transferred, but you pay it "
+"with quality loss."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):47
+msgid ""
+"DVB can be transferred in several ways. The trailing letter identifies the "
+"method of transfer, e.g. DVB-<e>T</e> for terrestrial transmission. There "
+"are several more types:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):54
+msgid "DVB-S for transmission over satellites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):55
+msgid "DVB-C for transmission over cable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):56
+msgid "DVB-H for transmission to mobile devices (terrestrial)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):57
+msgid "DVB-IPI for transmission over IP based networks, e.g. internet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):58
+msgid ""
+"DVB-RC(S/C/T) return channel for the transmission of data services, e.g. "
+"broadband internet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):68
+msgid "Types and requirement of DVB cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):71
+msgid ""
+"Besides the different methods available to receive a DVB stream, the cards "
+"are classified by their type of produced output. There are cards with a "
+"decoder implemented which offer direct access to the stream by the device "
+"<path>/dev/video</path>. These cards are <e>full featured cards</e>. Other "
+"cards have no own decoder implemented and require a software decoder on the "
+"computer and are <e>budget cards</e>. This implies higher system "
+"requirements. Your computer's CPU should run at at least 600 MHz, and have "
+"at least 256MB of RAM. <uri link=\"http://linuxtv.org/wiki/index.php/"
+"DVB_Card_Vendors\">This list</uri> is useful for identifying your card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):88
+msgid "Preparing the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):90
+msgid "Configuring the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):93
+msgid ""
+"First, we must ensure that your kernel supports DVB and your DVB device. "
+"Since kernel version 2.6 the necessary drivers are included. Check your "
+"kernel configuration and make sure the following options are selected as a "
+"static driver or as modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):100
+msgid "Required kernel options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):100
+#, no-wrap
+msgid ""
+"\n"
+"Input Device Support ---&gt;\n"
+"* Event Interface\n"
+"Device Drivers ---&gt;\n"
+"Multimedia Devices ---&gt;\n"
+"Digital Video Broadcasting Devices ---&gt;\n"
+"    [*] DVB For Linux\n"
+"     *  DVB Core Support\n"
+"   M  [Your driver]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):111
+msgid ""
+"Additionally we have to select the proper driver for your hardware. To find "
+"out the right module for your card, we mark every driver as module. If you "
+"have a PCI card, install <c>pciutils</c> if you haven't already. If you want "
+"built-in drivers or you don't own a PCI card, skip this step and continue "
+"with <uri link=\"#kernel_output\">Checking the kernel output</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):119
+msgid "Installing pciutils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):119
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge pciutils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):123
+msgid ""
+"After booting the new kernel, we run <c>pcimodules</c> to list the required "
+"modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):128
+msgid "Listing the required modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):128
+#, no-wrap
+msgid ""
+"\n"
+"# <i>pcimodules</i>\n"
+"ohci-hcd\n"
+"ehci-hcd\n"
+"sis900\n"
+"snd-emu10k1\n"
+"b2c2-flexcop-pci\n"
+"nvidia\n"
+"nvidiafb\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):139
+msgid ""
+"In this case we have to load the module <c>b2c2-flexcop-pci</c>. We add the "
+"name to <path>/etc/modules.autoload.d/kernel-2.6</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):144
+msgid "Adding the module name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):144
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo b2c2-flexcop-pci &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):152
+msgid "Checking the kernel output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):155
+msgid ""
+"It's recommended to mark every driver as module, so that you can add the "
+"required module dynamically, especially if you don't know the module name. "
+"If you already know the module name, select the driver as a built-in driver. "
+"Compile the kernel, install the modules and boot it. You can check if your "
+"kernel has successfully detected your card by using <c>dmesg</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):163
+msgid "Checking kernel output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):163
+#, no-wrap
+msgid ""
+"\n"
+"# <i>dmesg | grep DVB</i>\n"
+"<comment>(If you own a TerraTec Cinergy T2, your output might look like this:)</comment>\n"
+"DVB: registering new adaptor (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver).\n"
+"input: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control as /class/input/input2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):175
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):183
+msgid "Installing VDR"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):179
+msgid "To install VDR, we just emerge it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):183
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vdr</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):187
+msgid ""
+"Now continue with <uri link=\"#inst_ir_remote\">Installing the Remote "
+"Control</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):196
+msgid "Installing the Remote Control"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):200
+msgid ""
+"There are at least two ways to control VDR via an infrared remote control. "
+"If your TV card has an onboard IR receiver you can use <c>vdr-remote</c>. "
+"Otherwise, you most likely need to use LIRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):209
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):216
+msgid "Installing vdr-remote"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):212
+msgid "We first install the plugin via emerge:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):216
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vdr-remote</i>\n"
+"# <i>eselect vdr-plugin enable remote</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):221
+msgid ""
+"When using the remote plugin for the IR port on your DVB card everything "
+"should be fine with the default config. It automatically uses the input "
+"device which has \"dvb\" in its name. For more advanced uses take a look at "
+"<path>/etc/conf.d/vdr.remote</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):228
+msgid "Now, continue with <uri link=\"#video-out\">Video Output Methods</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):235
+msgid "Alternative: installing LIRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):238
+msgid ""
+"If your card can be remotely controlled (but you cannot or do not want to "
+"use <c>vdr-remote</c>), you may wish to configure LIRC. LIRC interprets the "
+"pressed keys and returns a name for each one. A program that supports LIRC "
+"waits for key events and runs the action configured in the config file, "
+"mostly stored in the config directory of the executing program (e.g. "
+"<c>mplayer</c> loads the file <path>~/.mplayer/lircrc</path>). Before we "
+"install LIRC, you have to add <c>lirc</c> to your USE flags and add an "
+"additional entry to <path>/etc/make.conf</path>: <c>LIRC_DEVICES</c>. Use "
+"<uri link=\"http://www.lirc.org/html/table.html\">this list</uri> to find "
+"the proper arguments for the option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):251
+msgid "Installing LIRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):251
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/make.conf</i>\n"
+"<comment>(Replace \"devinput\" with the proper driver)</comment>\n"
+"LIRC_DEVICES=\"devinput\"\n"
+"USE=\"lirc\"\n"
+"# <i>emerge lirc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):259
+msgid ""
+"At first we have to define each key code with a name. Most supported remote "
+"controls are configured already, take a look at the <uri link=\"http://lirc."
+"sourceforge.net/remotes/\">remote list</uri>. Download the required file and "
+"save it as <path>/etc/lircd.conf</path>. Now we have to find out where to "
+"access your remote control. Run the following command to get a list of the "
+"current input devices (make sure your device is running)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):268
+msgid "List of current input devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):268
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cat /proc/bus/input/devices</i>\n"
+"I: Bus=0000 Vendor=0000 Product=0000 Version=0000\n"
+"N: Name=\"TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control\"\n"
+"P: Phys=usb-0000:00:1d.7-1/input0\n"
+"S: Sysfs=/class/input/input2\n"
+"H: Handlers=kbd event1\n"
+"B: EV=100003\n"
+"B: KEY=108fc210 2043 0 0 0 0 8000 2080 1 9e1680 0 0 ffc\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):279
+msgid ""
+"In this case we have the Terratec Cinergy T2 device plugged in, so we can "
+"access the device over <path>/dev/input/event1</path>. Replace <c>event1</c> "
+"with the matching device in your output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):285
+msgid ""
+"<c>lircd</c> needs to know the device to use. Add the following line to "
+"<path>/etc/conf.d/lircd</path>. Remember to replace <c>devinput</c> with the "
+"name of your driver and <c>event1</c> with the actual device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):291
+msgid "Adding options to lircd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):291
+#, no-wrap
+msgid ""
+"\n"
+"LIRCD_OPTS=\"-H devinput -d /dev/input/event1\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):295
+msgid "It's time to start <c>lircd</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):299
+msgid "Starting lircd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):299
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/lircd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):303
+msgid ""
+"Now it should be possible to watch <c>lircd</c> capturing and decoding key "
+"presses. Just run the command <c>irw</c>. Stop it by pressing Ctrl+C when "
+"you have enough."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):309
+msgid "Testing LIRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):309
+#, no-wrap
+msgid ""
+"\n"
+"# <i>irw</i>\n"
+"0000000000001aa2 00 Exit Technisat_TTS35AI.conf\n"
+"0000000000001a8d 00 Mute Technisat_TTS35AI.conf\n"
+"0000000000000a97 00 OK Technisat_TTS35AI.conf\n"
+"0000000000000a97 01 OK Technisat_TTS35AI.conf\n"
+"0000000000000a92 00 Menu Technisat_TTS35AI.conf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):318
+msgid ""
+"Next, add it to the default runlevel so that it starts automatically at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):322
+msgid "Adding lircd to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):322
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add lircd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):326
+msgid ""
+"To be able to use your remote control, you must enable LIRC support in VDR. "
+"Add the following line to <path>/etc/conf.d/vdr</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):331
+msgid "Enabling support for LIRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):331
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/conf.d/vdr</i>\n"
+"IR_CTRL=\"lirc\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):341
+msgid "Video Output Methods"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):345
+msgid ""
+"You now need to decide on one (and only one!) of the following video output "
+"devices which show the picture and the overlayed On Screen Display (OSD)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):353
+msgid "Hardware decoding: full-featured DVB cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):356
+msgid ""
+"Users of these expensive cards need not install anything else, so you may "
+"continue with <uri link=\"#channel_list\">configuring your channel list</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):364
+msgid "Hardware decoding: DXR3/Hollywood+ cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):367
+msgid "To use a DXR3 card for VDR output we need the <c>vdr-dxr3</c> plugin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):371
+msgid "Installing the plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):371
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vdr-dxr3</i>\n"
+"# <i>echo em8300 &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):376
+msgid ""
+"The em8300 module need some configuration that depends on the exact revision "
+"of that card."
+msgstr ""
+
+#. <p>
+#. Because we (the authors) don't own a card that uses the dxr3config, we decided
+#. to skip this part till we have one at our disposal.
+#. </p>
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):388
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):411
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):451
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):515
+msgid ""
+"Continue with <uri link=\"#channel_list\">configuring your channel list</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):395
+msgid "Hardware decoding: PVR350 cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):398
+msgid ""
+"As PVR350 cards have an onboard MPEG-Decoder chip we want to make use of "
+"that. We need to install the <c>vdr-pvr350</c> plugin. If <c>ivtv-driver</c> "
+"is not yet installed emerge will automatically install it for you. To have "
+"the ivtv module loaded at boot we add it to <path>/etc/modules.autoload.d/"
+"kernel-2.6</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):406
+msgid "Installing PVR350-Plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):406
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vdr-pvr350</i>\n"
+"# <i>echo ivtv &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):418
+msgid "Software decoding: vdr-softdevice"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):421
+msgid ""
+"To install it, we have to emerge <c>vdr-softdevice</c>. Don't forget to "
+"enable the plugin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):426
+msgid "Installing the softdevice plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):426
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vdr-softdevice</i>\n"
+"# <i>eselect vdr-plugin enable softdevice</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):431
+msgid ""
+"To select the proper video and audio output, edit <path>/etc/conf.d/vdr."
+"softdevice</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):436
+msgid ""
+"For now, we will only describe the shm (\"shared memory\") method. This is "
+"already enabled in the installed config file (Setting SOFTDEVICE_VIDEO_OUT). "
+"Later you need to start <c>ShmClient</c> to get a window showing the picture."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):442
+msgid ""
+"If you do not want to think about a separate keyboard layout for controlling "
+"VDR, there are remote configuration files available at Matthias Schwarzott's "
+"<uri link=\"http://dev.gentoo.org/~zzam/vdr_remote_conf/\">devspace</uri>. "
+"There are files for softdevice/shm and xineliboutput (more coming). You will "
+"need the relevant file to <path>/etc/vdr/remote.conf</path> and run <c>chown "
+"vdr:vdr</c> on the file to get it working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):458
+msgid "Software decoding: vdr-xineliboutput"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):461
+msgid ""
+"Some people prefer to use <c>vdr-xineliboutput</c>, because it can also work "
+"remotely. We'll now teach you how to configure <c>vdr-xineliboutput</c> on "
+"your host and client. First, the host setup:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):467
+msgid "Installing vdr-xineliboutput"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):467
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vdr-xineliboutput</i>\n"
+"# <i>eselect vdr-plugin enable xineliboutput</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):472
+msgid ""
+"Adding command line options at this point is crucial for xineliboutput to "
+"work. For more options, see <c>vdr --help</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):477
+msgid "Adding command line options to /etc/conf.d/vdr.xineliboutput"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):477
+#, no-wrap
+msgid ""
+"\n"
+"_EXTRAOPTS=\"--local=none --remote=37890\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):481
+msgid ""
+"The next step is to edit <path>/etc/vdr/svdrphosts.conf</path>. This file "
+"describes a number of host addresses that are allowed to connect to the "
+"SVDRP port of the video disk recorder running on the host system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):487
+msgid "Editing /etc/vdr/svdrphosts.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):487
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(The proper syntax is: IP-Address[/Netmask])</comment>\n"
+"127.0.0.1             <comment>(always accept localhost)</comment>\n"
+"192.168.1.0/24        <comment>(any host on the local net)</comment>\n"
+"#204.152.189.113      <comment>(a specific host)</comment>\n"
+"#0.0.0.0/0            <comment>(any host on any net - USE THIS WITH CARE!)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):495
+msgid ""
+"If you only want to use <c>vdr-xineliboutput</c> to view the picture on the "
+"same computer as the one running VDR you can continue with <uri link="
+"\"#channel_list\">configuring your channel list</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):501
+msgid ""
+"Otherwise, you now simply <c>emerge media-plugins/vdr-xineliboutput</c> on "
+"your client:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):506
+msgid "Client setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):506
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vdr-xineliboutput</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):510
+msgid ""
+"Later (after having started VDR) you will use the command <c>vdr-sxfe xvdr://"
+"hostname</c> to connect to VDR and view its picture and OSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):519
+msgid ""
+"There is also a plugin which just simulates the existance of a real output "
+"device (<c>vdr-dummydevice</c>) for some fancy uses like record-only "
+"servers, but that is more advanced than a normal VDR setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):530
+msgid "Creating a Channel List"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):534
+msgid ""
+"To make VDR really useful you need to create an appropriate channel list. "
+"There is more than one way to get a working list of channels (besides "
+"downloading one). The channel list installed by default is for DVB-S "
+"reception on Astra on 19.2°E."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):544
+msgid "Using dvbscan from linuxtv-dvb-apps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):547
+msgid "Installing linuxtv-dvb-apps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):547
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge linuxtv-dvb-apps</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):551
+msgid ""
+"Find the correct frequency list for your region and type of reception. These "
+"files are stored under <path>/usr/share/dvb/scan</path>. For reception with "
+"DVB-T in Germany, Region Nuernberg you need to use <path>/usr/share/dvb/scan/"
+"dvb-t/de-Nuernberg</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):558
+msgid "Scanning with dvbscan"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):558
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>dvbscan -o vdr /usr/share/dvb/scan/dvb-t/de-Nuernberg &gt; /etc/vdr/channels.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):565
+msgid "Using vdr-reelchannelscan"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):568
+msgid "First, delete the contents of the existing channel list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):572
+msgid "Cleaning old channel-list"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):572
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm /etc/vdr/channels.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):576
+msgid "Installing and activating vdr-reelchannelscan"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):576
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge vdr-reelchannelscan</i>\n"
+"# <i>eselect vdr-plugin enable reelchannelscan</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):584
+msgid "Channels for systems using vdr-analogtv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):587
+msgid ""
+"You'll probably want to configure your channels at this point. The VDR "
+"project provides you with some examples which can be found at <path>/usr/"
+"share/doc/vdr-analogtv-$version/examples/</path>, as long as you've "
+"installed &gt;=<c>media-plugins/vdr-analogtv-1.0.00-r1</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):599
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):629
+msgid "Starting VDR"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):603
+msgid ""
+"After having all basic software parts ready on the system you need to "
+"configure VDR with its OSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):608
+msgid ""
+"If you use a hardware decoder for picture output you should switch on the "
+"connected TV now. If you use software output the client for this must be "
+"started after VDR."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):614
+msgid ""
+"First, you should learn your key definitions; that is, connecting keys on "
+"your remote control to VDR's internal commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):619
+msgid ""
+"Just in case you need to edit the keyboard configuration, or (more likely) "
+"want to delete it to go back to learning the keys: VDR stores its key-"
+"definitions in <path>/etc/vdr/remote.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):625
+msgid "We begin with starting VDR:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):629
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/vdr start</i>\n"
+"* Preparing start of vdr:\n"
+"*   config files ...                                        [ ok ]\n"
+"*   Waiting for prerequisites (devices nodes etc.) ...      [ ok ]\n"
+"* Starting vdr ...                                          [ ok ]\n"
+"* First start of vdr: No check for running vdr possible\n"
+"* until control device (remote/keyboard) keys are learnt!\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):639
+msgid ""
+"Users of software decoders should now start the client program that opens "
+"the window to show the TV picture and the OSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):644
+msgid "Activating the software decoder for the client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):644
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(For users of vdr-softdevice)</comment>\n"
+"# <i>ShmClient</i>\n"
+"<comment>(For users of vdr-xineliboutput)</comment>\n"
+"# <i>vdr-sxfe xvdr://hostname</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):651
+msgid "The most useful keys for VDR are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):655
+msgid "Cursor keys (Left/Right/Up/Down)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):656
+msgid "Menu/Exit/Ok"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):657
+msgid "Colors (Red/Green/Yellow/Blue)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):658
+msgid "Number keys (0-9)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(impo):661
+msgid ""
+"If you don't have many keys, make sure to assign these. (Some remotes have "
+"Play/Pause/etc. on the same keys as the colors, so use them for the colors)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):666
+msgid ""
+"Now that the basic installation is over, you need to configure VDR. Switch "
+"to your output screen and follow the on-screen instructions. VDR asks you to "
+"press various keys on your remote control to learn the correct key codes. If "
+"you don't own a remote control, you can use your keyboard."
+msgstr ""
+
+#. <p>
+#. TODO: Add a configuration howto for remote controls etc.
+#. </p>
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):677
+msgid ""
+"Now you can add the VDR initscript to the default runlevel to get it started "
+"every time your computer boots up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):682
+msgid "Adding vdr to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):682
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add vdr default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):691
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):695
+msgid ""
+"If you need any help, you can always ask someone in <uri link=\"irc://irc."
+"gentoo.org/gentoo-vdr\">#gentoo-vdr</uri>, or look around on our <uri link="
+"\"http://forums.gentoo.org/\">forums</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/vi-guide.xml.po b/doc/gettext/ru/vi-guide.xml.po
new file mode 100644
index 0000000..782c7bc
--- /dev/null
+++ b/doc/gettext/ru/vi-guide.xml.po
@@ -0,0 +1,834 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(guide:link):5
+msgid "/doc/en/vi-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):6
+msgid "Learning vi -- the \"cheatsheet\" technique"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(author:title):7
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail:link):8
+msgid "drobbins@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail):8
+msgid "Daniel Robbins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail:link):11
+msgid "stocke2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail):11
+msgid "Eric Stockbridge"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(author:title):13
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail:link):14
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail):14
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(abstract):17
+msgid ""
+"This guide will teach you how to use vi, using a cheat sheet method to "
+"accelerate the learning process. This will be the first guide for vi, "
+"catering to beginners."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(version):23
+msgid "1.1.7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(date):24
+msgid "2005-07-21"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):27
+msgid "Getting Started"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):29
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):32
+msgid ""
+"This tutorial will show you how to use vi, a powerful visual editor. Using a "
+"special accelerated <e>cheat sheet</e> method, this tutorial is designed to "
+"make you a proficient vi user without requiring a huge time commitment. In "
+"this vi tutorial, you'll learn how to move around, edit text, use insert "
+"mode, copy and paste text, and use important vim extensions like visual mode "
+"and multi-window editing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):41
+msgid ""
+"If you either don't know or aren't comfortable using vi, then you owe it to "
+"yourself to take this tutorial and get up to speed with one of the most "
+"popular and powerful Linux/UNIX visual editing programs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):50
+msgid "About the guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):53
+msgid ""
+"There's one thing in particular that makes it difficult to learn vi -- vi "
+"has lots of commands. In order to use vi effectively, you need to memorize "
+"quite a few. This can take a long time, and one of the goals of this "
+"tutorial is not to take up a lot of your time. So, initially, we have a "
+"challenge -- how exactly do I help you to memorize lots of commands in a "
+"short period of time?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):62
+msgid ""
+"To tackle this challenge, as we proceed through this tutorial, we're going "
+"to gradually put together a vi cheat sheet. This sheet will contain all the "
+"important vi commands. After you've completed this tutorial, you'll be able "
+"to refer to this cheat sheet if you forget a particular command. Over time, "
+"as you memorize commands, you'll gradually become less and less dependent on "
+"the cheat sheet. By using the cheat-sheet technique, you'll be able to learn "
+"how to use vi faster than ever possible before!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):76
+msgid "The learning process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):79
+msgid ""
+"In this guide, I'm going to use several techniques to help you learn. First, "
+"I'm going to describe how a particular command works, as you'd expect. Then, "
+"I'm going to ask you to try to use the command in vi (for practice), and "
+"then I'm going to ask you to transcribe the command to the cheat sheet (for "
+"later reference.) If you want to learn vi quickly, it's important that you "
+"perform all these steps. Trying out a command in vi and transcribing the "
+"command onto your cheat sheet will help you to memorize the command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):93
+msgid "Introducing vim"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):96
+msgid ""
+"There are many versions of vi, and I'm going to be showing you how to use a "
+"version of vi called <c>vim</c>. vim is very popular and has a number of "
+"extensions that make vi a lot nicer (whenever I demonstrate a vim-specific "
+"command, I'll make a note of it.) If you need to install vim, you can get it "
+"from <uri link=\"http://www.vim.org/\">www.vim.org</uri>. In addition to an "
+"enhanced command-line vi, vim also comes with <c>gvim</c>, a nice graphical "
+"editor which can be configured to use the excellent GTK+ gui library. Here's "
+"a gvim screenshot from my system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):108
+msgid "/images/vishot.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):108
+msgid "screenshot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):108
+msgid "VIM screenshot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):110
+msgid ""
+"If you're a vi newbie, try to get gvim running on your system. Using vi from "
+"a gui can make things a bit easier for beginners."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):120
+msgid "First Steps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):122
+msgid "Pick a file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):125
+msgid ""
+"Before using vi to edit files, you need to know how to use vi to move around "
+"in a file. vi has a lot of movement commands, and we're going to take a look "
+"at many of them. For this part of the tutorial, find an unimportant text "
+"file and load it into vi by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(pre:caption):132
+msgid "Loading a file into vi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(pre):132
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>vi myfile.txt</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):136
+msgid ""
+"If you have vim installed, type <c>vim myfile.txt</c>. If you'd prefer to "
+"use gvim, type <c>gvim myfile.txt</c>. <path>myfile.txt</path> should be the "
+"name of a text file on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):145
+msgid "Inside vi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):148
+msgid ""
+"After vi loads, you should see a part of the text file you loaded on your "
+"screen. Congratulations -- you're in vi! Unlike many editors, when vi starts "
+"up, it is in a special mode called <e>command mode</e>. This means that if "
+"you press <c>l</c>on the keyboard, instead of inserting an <c>l</c> into the "
+"file at the current cursor position, the cursor will move one character to "
+"the right instead. In command mode, the characters on your keyboard are used "
+"to send commands to vi rather than insert literal characters into the text. "
+"One of the most essential types of commands are movement commands; let's "
+"take a look at some."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):166
+msgid "Moving around"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):168
+msgid "Moving in vi, part 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):171
+msgid ""
+"When in command mode, you can use the <c>h</c>,<c>j</c>,<c>k</c> and <c>l</"
+"c> keys to move the cursor left, down, up and right respectively. If you're "
+"using a modern version of vi, you can also use the arrow keys for this "
+"purpose. The <c>h</c>,<c>j</c>,<c>k</c> and <c>l</c> keys are handy because "
+"once you're comfortable with them, you'll be able to move around in the file "
+"without moving your fingers from the home keyboard row. Try using <c>h</c>,"
+"<c>j</c>,<c>k</c> and <c>l</c> (and the arrow keys) to move around in the "
+"text file. Try using <c>h</c> until you get to the beginning of a line. "
+"Notice that vi doesn't allow you to \"wrap around\" to the previous line by "
+"hitting <c>h</c> while you're on the first character. Likewise, you can't "
+"\"wrap around\" to the next line by hitting <c>l</c> at the end of a line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):190
+msgid "Moving in vi, part 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):193
+msgid ""
+"vi offers special shortcuts for jumping to the beginning or end of the "
+"current line. You can press <c>0</c> (zero) to jump to the first character "
+"of a line, and <c>$</c> to jump to the last character of the line. Try 'em "
+"and see. Since vi has so many handy movement commands, it makes a great "
+"\"pager\" (like the more or less commands.) Using vi as a pager will also "
+"help you to learn all the movement commands very quickly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):203
+msgid ""
+"You can also use <c>&lt;CTR&gt;F</c> and <c>&lt;CTR&gt;B</c> to move "
+"forwards and backwards a page at a time. Modern versions of vi (like vim) "
+"will also allow you to use the <c>PGUP</c> and <c>PGDOWN</c> keys for this "
+"purpose."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):213
+msgid "Word moves, part 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):216
+msgid ""
+"vi also allows you to move to the left or right by word increments. To move "
+"to the <e>first</e> character of the next word, press <c>w</c>. To move to "
+"the <e>last</e> character of the next word, press <c>e</c>. To move to the "
+"first character of the <e>previous</e> word, press <c>b</c>. Test 'em out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):227
+msgid "Word moves, part 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):230
+msgid ""
+"After playing around with the word movement commands, you may have noticed "
+"that vi considers words like <c>foo-bar-oni</c> as five separate words! This "
+"is because by default, vi delimits words by spaces <e>or</e> punctuation. "
+"<c>foo-bar-oni</c> is therefore considered five words: <c>foo</c>, <c>-</c>, "
+"<c>bar</c>, <c>-</c> and <c>oni</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):238
+msgid ""
+"Sometimes, this is what you want, and sometimes it isn't. Fortunately, vi "
+"also understands the concept of a \"bigword\". vi delimits bigwords by "
+"<e>spaces or newlines only</e>. This means that while <c>foo-bar-oni</c> is "
+"considered five vi words, it's considered only one vi bigword."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):249
+msgid "Word moves, part 3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):252
+msgid ""
+"To jump around to the next and previous bigword, you can use a "
+"<e>capitalized</e> word move command. Use <c>W</c> to jump to the first "
+"character of the next bigword, <c>E</c> to jump to the last character of the "
+"next bigword, and <c>B</c> to jump to the first character of the previous "
+"bigword. Test 'em out, and compare the matching word and bigword movement "
+"commands until you understand their differences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):265
+msgid "Bigger moves"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):268
+msgid ""
+"We just have a few more commands to cover before it's time to start puting "
+"together our cheat sheet. You can use the <c>(</c> and <c>)</c> characters "
+"to move to the beginning of the previous and next sentence. In addition, you "
+"can hit <c>{</c> or <c>}</c> to jump to the beginning of the current "
+"paragraph, and the beginning of the next. Test 'em out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):282
+msgid "Quitting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):286
+msgid ""
+"We've covered the basic movement commands, but there are another couple of "
+"commands that you need to know. Typing <c>:q</c> will quit vi. If this "
+"doesn't work, then you probably accidentally modified the file in some way. "
+"To tell vi to quit, throwing away any changes, type <c>:q!</c>. You should "
+"now be at the command prompt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):294
+msgid ""
+"In vi, any command that begins with a <c>:</c> is said to be an <e>ex-mode</"
+"e> command. This is because vi has a built-in non-visual editor called "
+"<e>ex</e>. It can be used similarly to sed to perform line-based editing "
+"operations. In addition, it can also be used to quit, as we've just seen. If "
+"you ever hit the <c>Q</c> key while in command mode, you'll be transported "
+"to ex mode. If this ever happens to you, you'll be confronted with a : "
+"prompt, and hitting enter will scroll the entire screen upwards. To get back "
+"to good 'ol vi mode, simply type vi and hit enter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):311
+msgid "The Cheat Sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):313
+msgid "The beginnings of the cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):316
+msgid ""
+"We've covered a lot of commands, and it's time to transcribe them to our "
+"cheat sheet. For the cheat sheet, you'll need a US letter or A4 sized piece "
+"of paper (we're going to pack a lot of info onto this sheet!) Here's a "
+"picture of my cheat sheet after I've transcribed all the commands that we've "
+"covered so far. Try to follow my layout if possible so that we can fit "
+"everything on one sheet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):326
+msgid "/images/vicheat-first.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):326
+msgid "First part of the cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):326
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):597
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):708
+msgid "Cheat Sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):331
+msgid "Miscellaneous vi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):334
+msgid ""
+"Let's continue our rapid command-covering pace. In command-mode, you can "
+"jump to a particularline by typing <c>G</c>. To jump to the first line of a "
+"file, type <c>1G</c>. Note that <c>G</c> is capitalized."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):340
+msgid ""
+"If you want to jump to the next occurence of a particular text pattern, type "
+"<c>/&lt;regexp&gt;</c> and hit <c>enter</c>. Replace &lt;regexp&gt; with the "
+"regular expression you're looking for. If you don't know how to use regular "
+"expressions, don't fret -- typing <c>/foo</c> will move to the next "
+"occurence of <e>foo</e>. The only thing you'll need to watch out for is when "
+"you want to refer to the literal <c>^</c>, <c>.</c>, <c>$</c> or <c>\\</c> "
+"characters. Prefix these characters with a backslash (<c>\\</c>), and you'll "
+"be set. For example, <c>/foo\\.gif</c> will search for the next occurence of "
+"\"foo.gif\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):353
+msgid ""
+"To repeat the search forwards, hit <c>n</c>. To repeat the search backwards, "
+"type <c>N</c>. As always, test these commands out in your very own vi "
+"editor. You can also type <c>//</c> to repeat the last search."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):365
+msgid "Saving and Editing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):367
+msgid "Save and save as..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):370
+msgid ""
+"We've covered how you can use the <e>ex</e> command <c>:q</c> to quit from "
+"vi. If you want to save your changes, type <c>:w</c>. If you want to save "
+"your changes to another file, type <c>:w filename.txt</c> to save as "
+"<e>filename.txt</e>. If you want to save and quit, type <c>:x</c> or <c>:wq</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):378
+msgid ""
+"In vim (and other advanced vi editors, like elvis)<c>:w</c>, you can have "
+"multiple buffers open at once. To open a file into a new window, type <c>:sp "
+"filename.txt</c>. <path>filename.txt</path> will appear open for editing in "
+"a new split window. To switch between windows, type <c>&lt;CTR&gt;w&lt;"
+"CTR&gt;w</c> (control-w twice). Any <c>:q</c>, <c>:q!</c>, <c>:w</c> and <c>:"
+"x</c> commands that you enter will only be applied to the currently-active "
+"window."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):391
+msgid "Simple edits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):394
+msgid ""
+"Now, it's time to start learning some of the simple editing commands. The "
+"commands that we'll cover here are considered <e>simple</e> because the "
+"commands keep you in command mode. The more complex editing commands "
+"automatically put you into insert mode -- a mode that allows you to enter "
+"literal data from the keyboard. We'll cover those in a bit."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):402
+msgid ""
+"For now, try moving over some characters and hitting <c>x</c> repeatedly. "
+"You'll see that <c>x</c> will delete the current character under the cursor. "
+"Now, move to the middle of the paragraph somewhere in your text file, and "
+"hit <c>J</c> (capitalized). You'll see that the <c>J</c> command tells vi to "
+"join the next line to the end of the current line. Now, move over a "
+"character and hit <c>r</c>, and then type in a new character; you'll see "
+"that the original character has been replaced. Finally, move to any line in "
+"the file and type <c>dd</c>. You'll see that <c>dd</c> deletes the current "
+"line of text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):418
+msgid "Repeating and deleting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):421
+msgid ""
+"You can repeat any editing command by hitting the <c>.</c> key. If you "
+"experiment, you'll see that typing <c>dd...</c> will delete 4 lines, and "
+"<c>J......</c> will join four lines. As usual, vi provides with another "
+"handy shortcut."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):428
+msgid ""
+"To delete text, you can also use the <c>d</c> command combined with any "
+"movement command. For example, <c>dw</c> will delete from the current "
+"position to the beginning of the next word; <c>d)</c> will delete up until "
+"the end of the next sentence, and <c>d}</c> will delete the remainder of the "
+"paragraph. Experiment with the <c>d</c> command and the other editing "
+"commands until you're comfortable with them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):441
+msgid "Undo!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):444
+msgid ""
+"Now that we're experimenting with deletion, it would be a good time to learn "
+"how to undo any changes. By pressing <c>u</c>, the original version of vi "
+"allowed you to undo the last edit only. However, modern versions of vi like "
+"vim will allow you to repeatedly press <c>u</c> to continue to undo changes "
+"to your file. Try combining some <c>d</c> and <c>u</c> commands together."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):456
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):588
+msgid "Updating the cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):459
+msgid ""
+"Time to update the cheat sheet! After adding all the commands we've covered "
+"so far, your cheat sheet should look like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):465
+msgid "/images/vicheat-edit.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):465
+msgid "Cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):465
+msgid "Cheat sheet with editing commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):472
+msgid "Insert mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):476
+msgid ""
+"So far, we've covered how to move around in vi, perform file i/o, and "
+"perform basic editing operations. However, I still haven't shown you how to "
+"actually type in free-form text! This was intentional, because vi's insert "
+"mode is a bit complicated at first. However, after you become comfortable "
+"with insert mode, its complexity (and flexibility) will become an asset."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):485
+msgid ""
+"In vi <e>insert mode</e>, you'll be able to enter text directly to the "
+"screen just like you can in many other visual editors. Once you've entered "
+"your modifications, you can hit escape to return to <e>command mode</e>. You "
+"can enter insert mode by pressing <c>i</c> or <c>a</c>. If you press <c>i</"
+"c>, your text will be <e>inserted</e> before the current character, and if "
+"you hit <c>a</c>, your text will be <e>appended</e> after the current "
+"character. Remember, after you enter your text, hit <c>&lt;ESC&gt;</c> to "
+"return to command mode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):499
+msgid "Benefits of insert mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):502
+msgid ""
+"Go ahead and try using the <c>a</c> and <c>i</c> commands. Hit either <c>a</"
+"c> or <c>i</c>, type some text, and then hit escape to get back to command "
+"mode. After hitting <c>a</c> or <c>i</c>, try hitting <c>&lt;ENTER&gt;</c>, "
+"and see what happens. Try using the arrow keys and the <c>&lt;DEL&gt;</c> "
+"key to get a feel for how insert mode works. By using the arrow keys and "
+"<c>&lt;DEL&gt;</c> key, you can perform significant editing steps without "
+"repeatedly entering and leaving insert mode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):516
+msgid "Insert options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):519
+msgid ""
+"Here are some other handy ways to enter insert mode. Press <c>A</c> "
+"(captial) to begin appending to the <e>end</e> of the current line, "
+"regardless of your current position on the line. Likewise, press <c>I</c> "
+"(capital) to begin inserting text at the <e>beginning</e> of the current "
+"line. Press <c>o</c> to create a new blank line below the current line into "
+"which you can insert text, and press <c>O</c> (capital) to create a new line "
+"above the current line. To replace the entire current line with a new line, "
+"press <c>cc</c>. To replace everything from the current position to the end "
+"of the line, type <c>c$</c>. To replace everything from the current position "
+"to the beginning of the line, type <c>c0</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):533
+msgid ""
+"In addition to performing a special operation, every one of these commands "
+"will put you into insert mode. After typing in your text, hit <c>&lt;ESC&gt;"
+"</c> to return to command mode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):542
+msgid "Changing text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):545
+msgid ""
+"We've used the <c>c</c> (change) command a little bit so far when we typed "
+"<c>cc</c>, <c>c0</c> and <c>c$</c>. <c>cc</c> is a special form of the "
+"change command, similar to <c>dd</c>. the <c>c0</c> and <c>c$</c> commands "
+"are examples of using the change command in combination with a movement "
+"command. In this form, <c>c</c> works similarly to <c>d</c>, except that it "
+"leaves you in insert mode so that you can enter replacement text for the "
+"deleted region. Try combining some movement commands with <c>c</c> and test "
+"them out on your file (hint: <c>cW</c>, <c>ce</c>, <c>c(</c> .)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):562
+msgid "Compound Commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):566
+msgid ""
+"vi <e>really</e> becomes powerful when you start using compound (\"combo\") "
+"commands, like <c>d{</c> and <c>cw</c>. In addition to these commands, you "
+"can also combine a number with any movement command, such as <c>3w</c>, "
+"which will tell vi to jump three words to the right. Here are some more "
+"movement \"combo\" command examples: <c>12b</c>, <c>4j</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):575
+msgid ""
+"vi, in addition to allowing (number)(movement command) combinations, also "
+"allows <c>d</c> or <c>c</c> to be combined with a number or movement "
+"command. So, <c>d3w</c> will delete the next three words, <c>d2j</c> will "
+"delete the current and next two lines, etc. Test out some <c>c</c> and <c>d</"
+"c> combo moves to get a feel for how powerful and concise vi editing can be. "
+"Once these commands are second-nature, you'll be able to edit files at "
+"blazing speed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):591
+msgid "Time to update the cheat sheet again. Here's what it looks like so far:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):597
+msgid "/images/vicheat-compound.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):597
+msgid "Cheat sheet with compound commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):602
+msgid "Productivity features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):605
+msgid ""
+"So far, we've covered how to move, save and quit, perform simple edits and "
+"deletions, and use insert mode. With everything listed on the cheat sheet so "
+"far, you should be able to use vi to perform almost any task."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):612
+msgid ""
+"However, vi also has many more powerful commands. In this section, you'll "
+"learn how to <e>cut</e>, <e>copy</e> and <e>paste</e>, <e>search</e> and "
+"<e>replace</e>, and use <e>autoindent</e> features. These commands will help "
+"make vi more fun and productive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):622
+msgid "Visual mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):625
+msgid ""
+"The best way to cut and paste is to use <e>visual mode</e>, a special mode "
+"that has been added to modern versions of vi, like vim and elvis. You can "
+"think of visual mode as a \"highlight text\" mode. Once the text is "
+"highlighted, it can be copied or deleted, and then pasted. If you are using "
+"gvim, you can highlight by simply dragging the left mouse button over a "
+"particular region:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):635
+msgid "/images/vihighlight.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):635
+msgid "Highlighted text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):635
+msgid "VIM with highlighted text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):637
+msgid ""
+"In addition, you can also enter visual mode by hitting <c>v</c> (this may be "
+"your only option if you are using vi from the console.) Then, by moving the "
+"cursor using movement commands (typically the arrow keys), you'll be able to "
+"highlight a region of text. Once highlighted, we are ready to cut or copy "
+"the text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):645
+msgid ""
+"If you're copying the text, hit <c>y</c> (which stands for \"yank\"). If "
+"you're cutting the text, hit <c>d</c>. You'll be placed back in command "
+"mode. Now, move to the position where you'd like to insert the cut or copied "
+"text, and hit <c>P</c> to insert before the cursor, or <c>p</c> to insert "
+"after the cursor. Voila, the cut/copy and paste is complete! Test out "
+"several copy/cut and paste operations before advancing to the next section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):658
+msgid "Replacing text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):661
+msgid ""
+"To replace patterns of text, we use <e>ex</e> mode. If you'd like to replace "
+"the first pattern that appears on the current line, type <c>:s/&lt;"
+"regexp&gt;/&lt;replacement&gt;/</c> and hit <c>&lt;ENTER&gt;</c>, where &lt;"
+"regexp&gt; is the pattern you'd like to match and &lt;replacement&gt; is the "
+"replacement string. To replace all matches on the current line, type <c>:s/"
+"&lt;regexp&gt;/&lt;replacement&gt;/g</c> and hit enter. To replace every "
+"occurence of this pattern in your file (normally what you want), type <c>:%s/"
+"&lt;regexp&gt;/&lt;replacement&gt;/g</c>. If you'd like to do a global "
+"replace, but have vi prompt you for each change, type <c>:%s/&lt;regexp&gt;/"
+"&lt;replacement&gt;/gc</c> (stands for \"confirm\") and hit <c>&lt;ENTER&gt;"
+"</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):679
+msgid "Indentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):682
+msgid ""
+"vi supports autoindentation, for when you are editing source code. Most "
+"modern versions of vi (like vim) will auto-enable autoindent mode when you "
+"are editing a source file (like a .c file, for example). When autoindent is "
+"enabled, you can use <c>&lt;CTR&gt;d</c> (control-d) to move one indent "
+"level to the left, and <c>&lt;CTR&gt;t</c> (control-t) to move one indent "
+"level to the right. If autoindent wasn't enabled automatically, you can "
+"manually enable it by typing in the <e>ex</e> command <c>:set autoindent</"
+"c>. You can also tell vi to set the tab size to your favorite setting by "
+"using the <c>:set tabstop</c> command; <c>:set tabstop=4</c> is quite "
+"popular."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):698
+msgid "Our final cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):701
+msgid ""
+"Well, we've reached the end of the vi tutorial! After adding all the "
+"advanced editing commands to your cheat sheet, it should look like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):708
+msgid "/images/vicheat-final.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):708
+msgid "Final cheet sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):710
+msgid ""
+"Keep your cheat sheet handy, and begin using vi to edit files and compose "
+"emails. Refer to the cheat sheet when needed; you'll find that within the "
+"week, you'll have nearly all the commands memorized and your vi productivity "
+"will shoot through the roof!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):717
+msgid ""
+"If you want to use vi as your default editor make the following change to "
+"<path>/etc/rc.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(pre:caption):722
+msgid "Setting vi as the default editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(pre):722
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Set EDITOR to your preferred editor.)</comment>\n"
+"#EDITOR=\"/bin/nano\"\n"
+"EDITOR=\"/usr/bin/vim\"\n"
+"#EDITOR=\"/usr/bin/emacs\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):732
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):735
+msgid ""
+"Here are some resources you may find helpful as you continue to learn more "
+"about vi:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(li):741
+msgid ""
+"<uri link=\"http://www.thomer.com/thomer/vi/vi.html\">The vi Lovers Home "
+"Page</uri>, an excellent resource for all things vi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(li):745
+msgid ""
+"<uri link=\"http://www.vim.org/\">The vim homepage</uri> is the place to go "
+"for all your vim needs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(li):749
+msgid ""
+"If you're looking for a good, old-fashioned book, <uri link=\"http://www."
+"oreilly.com/catalog/vi6/\">Learning the vi Editor, 6th Edition</uri> would "
+"be an excellent choice. Contains good coverage of vi and vi clones."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):760
+msgid "About this document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):763
+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//vi-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/virt-mail-howto.xml.po b/doc/gettext/ru/virt-mail-howto.xml.po
new file mode 100644
index 0000000..1cbb553
--- /dev/null
+++ b/doc/gettext/ru/virt-mail-howto.xml.po
@@ -0,0 +1,1589 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):6
+msgid "Virtual Mailhosting System with Postfix Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):9
+msgid "antifa@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):9
+msgid "Ken Nowack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):12
+msgid "ezra@revoltltd.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):12
+msgid "Ezra Gorman"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):15
+msgid "klasikahl@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):15
+msgid "Zack Gilburd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):18
+msgid "seather@scygro.za.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):18
+msgid "Scygro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):21
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):21
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(abstract):27
+msgid ""
+"This document details how to create a virtual mailhosting system based upon "
+"postfix, mysql, courier-imap, and cyrus-sasl."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(version):32
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(date):33
+msgid "2010-10-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):36
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1021
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):40
+msgid ""
+"For most Gentoo users, a simple mail client and fetchmail will do. However, "
+"if you're hosting a domain with your system, you'll need a full blown MTA "
+"(Mail Transfer Agent). And if you're hosting multiple domains, then you'll "
+"definitely need something more robust to handle all of the email for your "
+"users. This system was designed to be an elegant solution to that problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):48
+msgid ""
+"A virtual mail system needs to be able to handle email for numerous domains "
+"with multiple users over a variety of interfaces. This presents some issues "
+"that must be dealt with. For instance, what if you have two users on "
+"different domains that want the same user name? If you are providing imap "
+"access and smtp-auth, how do combine the various authentication daemons into "
+"a single system? How do you provide security for the numerous components "
+"that comprise the system? How do you manage it all?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):58
+msgid ""
+"This howto will show you how to set up with a mail system capable of "
+"handling mail for as many domains as your hardware can handle, supports "
+"virtual mail users that don't require shell accounts, has domain specific "
+"user names, can authenticate web, imap, smtp, and pop3 clients against a "
+"single database, utilizes ssl for transport layer security, has a web "
+"interface, can handle mailing lists for any domain on the machine, and is "
+"controlled by a nice, central and easy mysql database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):68
+msgid ""
+"There are quite a variety of ways to go about setting up a virtual "
+"mailhosting system. With so may options, another may be the best choice for "
+"your specific needs. Consider investigating <uri>http://www.qmail.org/</uri> "
+"and <uri>http://www.exim.org/</uri> to explore your options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):75
+msgid ""
+"The following packages are used in this setup: apache, courier-imap, courier-"
+"authlib postfix, mod_php, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, "
+"and mailman."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):81
+msgid ""
+"Make sure to turn on the following USE variables in <path>/etc/make.conf</"
+"path> before compiling the packages: <c>USE=\"mysql imap libwww maildir sasl "
+"ssl\"</c>. Otherwise you will most likely have to recompile things to get "
+"the support you need for all the protocols. Further, it's a good idea to "
+"turn off any other mail and network variables, like ipv6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(impo):89
+msgid ""
+"You need a domain name to run a public mail server, or at least an MX record "
+"for a domain. Ideally you would have control of at least two domains to take "
+"advantage of your new virtual domain functionality."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(impo):95
+msgid ""
+"Make sure <path>/etc/conf.d/hostname</path> is set to the right hostname for "
+"your mail server. You can apply any changes you make to this file by running "
+"<c>/etc/init.d/hostname restart</c>. Verify your hostname is set correctly "
+"with <c>hostname</c>. Also verify that there are no conflicting entries in "
+"<path>/etc/hosts</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(note):103
+msgid ""
+"It is recommended that you read this entire document and familiarize "
+"yourself with all the steps before attempting the install. If you run into "
+"problems with any of the steps, check the troubleshooting guide at the end "
+"of this document. Also, not all the referenced packages are necessary, this "
+"set up is very flexible. For instance, if you do not desire a web interface, "
+"feel free to skip the squirrelmail section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):117
+msgid "Postfix Basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):121
+msgid "Install postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):121
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge postfix</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(warn):125
+msgid ""
+"Verify that you have not installed any other MTA, such as ssmtp, exim, or "
+"netqmail, or you will surely have BIG problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):130
+msgid ""
+"After postfix is installed, it's time to configure it. Change the following "
+"options in <path>/etc/postfix/main.cf</path>. Remember to replace <c>"
+"$variables</c> with your own names."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):136
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):327
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):783
+msgid "/etc/postfix/main.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):136
+#, no-wrap
+msgid ""
+"\n"
+"myhostname = $host.domain.name\n"
+"mydomain = $domain.name\n"
+"inet_interfaces = all\n"
+"mydestination = $myhostname, localhost.$mydomain $mydomain\n"
+"mynetworks = my.ip.net.work/24, 127.0.0.0/8\n"
+"home_mailbox = .maildir/\n"
+"local_destination_concurrency_limit = 2\n"
+"default_destination_concurrency_limit = 10\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):147
+msgid ""
+"Next change the following in <path>/etc/postfix/master.cf</path>. This will "
+"turn on verbose output for debugging:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):152
+msgid "/etc/postfix/master.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):152
+#, no-wrap
+msgid ""
+"\n"
+"# service type  private unpriv  chroot  wakeup  maxproc command + args\n"
+"#               (yes)   (yes)   (yes)   (never) (50)\n"
+"#\n"
+"==========================================================================\n"
+"<comment>(Just add the \"-v\" after the smtpd in the following line)</comment>\n"
+"smtp      inet  n       -       n       -       -       smtpd -v\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):161
+msgid ""
+"Next, edit <path>/etc/mail/aliases</path> to add your local aliases. There "
+"should at least be an alias for root like: <c>root: your@email.address</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):166
+msgid "Starting postfix for the first time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):166
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/usr/bin/newaliases</i>\n"
+"<comment>(This will install the new aliases. You only need to do this\n"
+"when you update or install aliases.)</comment>\n"
+"\n"
+"# <i>/etc/init.d/postfix start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):174
+msgid ""
+"Now that postfix is running, fire up your favorite console mail client and "
+"send yourself an email. I use <c>mutt</c> for all my console mail. Verify "
+"that postfix is delivering mail to local users, once that's done, we're on "
+"to the next step."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(note):181
+msgid ""
+"I strongly recommend that you verify this basic postfix setup is functioning "
+"before you progress to the next step of the howto."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):191
+msgid "Courier-imap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):195
+msgid "Install courier-imap and courier-authlib"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):195
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge courier-imap courier-authlib</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):199
+msgid "Courier-imap configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):199
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/courier-imap</i>\n"
+"<comment>(If you want to use the ssl capabilities of courier-imap or pop3,\n"
+"you'll need to create certs for this purpose.\n"
+"This step is recommended. If you do not want to use ssl, skip this step.)</comment>\n"
+"\n"
+"# <i>nano -w pop3d.cnf</i>\n"
+"# <i>nano -w imapd.cnf</i>\n"
+"<comment>(Change the C, ST, L, CN, and email parameters to match your server.)</comment>\n"
+"\n"
+"# <i>mkpop3dcert</i>\n"
+"# <i>mkimapdcert</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):213
+msgid "Start the courier services you need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):213
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/courier-imapd start</i>\n"
+"# <i>/etc/init.d/courier-imapd-ssl start</i>\n"
+"# <i>/etc/init.d/courier-pop3d start</i>\n"
+"# <i>/etc/init.d/courier-pop3d-ssl start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):220
+msgid ""
+"Start up your favorite mail client and verify that all connections you've "
+"started work for receiving and sending mail. Of course, you won't be able to "
+"log on to any of the services because authentication hasn't been configured "
+"yet, but it is wise to check if the connections themselves work or not."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):227
+msgid ""
+"Now that the basics work, we're going to do a whole bunch of stuff at once "
+"to get the rest of the system running. Again, please verify that what we've "
+"installed already works before progressing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):238
+msgid "Cyrus-sasl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):242
+msgid ""
+"Next we're going to install cyrus-sasl. Sasl is going to play the role of "
+"actually passing your auth variables to courier-auth, which will in turn "
+"pass that information to mysql for authentication of smtp users. For this "
+"howto, we'll not even try to verify that sasl is working until mysql is set "
+"up and contains a test user. Which is fine since we'll be authenticating "
+"against mysql in the end anyway."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):251
+msgid "Configuring and installing the cyrus-sasl ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):251
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge cyrus-sasl</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):255
+msgid "Next, edit <path>/etc/sasl2/smtpd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):259
+msgid "Starting sasl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):259
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/sasl2/smtpd.conf</i>\n"
+"mech_list: PLAIN LOGIN\n"
+"pwcheck_method: saslauthd\n"
+"# <i>nano -w /etc/conf.d/saslauthd</i>\n"
+"SASLAUTHD_OPTS=\"${SASLAUTH_MECH} -a rimap -r\"\n"
+"SASLAUTHD_OPTS=\"${SASLAUTHD_OPTS} -O localhost\"\n"
+"# <i>/etc/init.d/saslauthd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):274
+msgid "SSL Certs for Postfix and Apache"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):278
+msgid ""
+"Next we're going to make a set of ssl certificates for postfix and apache."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):282
+msgid "Making ssl certicates"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):282
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/ssl/</i>\n"
+"# <i>nano -w openssl.cnf</i>\n"
+"\n"
+"<comment>Change the following default values for your domain:</comment>\n"
+"countryName_default\n"
+"stateOrProvinceName_default\n"
+"localityName_default\n"
+"0.organizationName_default\n"
+"commonName_default\n"
+"emailAddress_default.\n"
+"\n"
+"<comment>(If the variables are not already present, just add them in a sensible place.)</comment>\n"
+"\n"
+"# <i>cd misc</i>\n"
+"# <i>./CA.pl -newreq-nodes</i>\n"
+"# <i>./CA.pl -newca</i>\n"
+"# <i>./CA.pl -sign</i>\n"
+"# <i>cp newcert.pem /etc/postfix</i>\n"
+"# <i>cp newkey.pem /etc/postfix</i>\n"
+"# <i>cp demoCA/cacert.pem /etc/postfix</i>\n"
+"<comment>(Now we do the same thing for apache.)</comment>\n"
+"\n"
+"# <i>openssl req -new &gt; new.cert.csr</i>\n"
+"# <i>openssl rsa -in privkey.pem -out new.cert.key</i>\n"
+"# <i>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</i>\n"
+"<comment>(Just leave the resulting certificates here for now.\n"
+"We'll install them after Apache is installed.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):317
+msgid "Adding SSL and SASL support to Postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):321
+msgid ""
+"Now edit the postfix config's to make it aware of your new sasl and ssl "
+"capabilities. Add the following parameters to the end of the file where they "
+"will be easy to find."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):327
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/main.cf</i>\n"
+"\n"
+"smtpd_sasl_auth_enable = yes\n"
+"smtpd_sasl2_auth_enable = yes\n"
+"smtpd_sasl_security_options = noanonymous\n"
+"broken_sasl_auth_clients = yes\n"
+"smtpd_sasl_local_domain =\n"
+"\n"
+"<comment>(The broken_sasl_auth_clients option and the login auth method\n"
+"are for outlook and outlook express only and are undocumented.\n"
+"Isn't having to hack software for stupid, broken, M$ BS great?\n"
+"smtpd_sasl_local_domain appends a domain name to clients using\n"
+"smtp-auth. Make sure it's blank or your user names will get\n"
+"mangled by postfix and be unable to auth.)</comment>\n"
+"\n"
+"smtpd_recipient_restrictions =\n"
+"  permit_sasl_authenticated,\n"
+"  permit_mynetworks,\n"
+"  reject_unauth_destination\n"
+"\n"
+"<comment>(The next two options enable outgoing encryption.)</comment>\n"
+"smtp_use_tls = yes\n"
+"smtp_tls_note_starttls_offer = yes\n"
+"smtpd_use_tls = yes\n"
+"#smtpd_tls_auth_only = yes\n"
+"smtpd_tls_key_file = /etc/postfix/newkey.pem\n"
+"smtpd_tls_cert_file = /etc/postfix/newcert.pem\n"
+"smtpd_tls_CAfile = /etc/postfix/cacert.pem\n"
+"smtpd_tls_loglevel = 3\n"
+"smtpd_tls_received_header = yes\n"
+"smtpd_tls_session_cache_timeout = 3600s\n"
+"tls_random_source = dev:/dev/urandom\n"
+"\n"
+"<comment>(smtpd_tls_auth_only is commented out to ease testing the system.\n"
+"You can turn this on later if you desire.)</comment>\n"
+"\n"
+"# <i>postfix reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):367
+msgid ""
+"Now we're going to verify that the config's we added were picked up by "
+"postfix. For this we are going to use <c>telnet</c> (provided by for "
+"instance <c>net-misc/netkit-telnetd</c>) although you can also use <c>nc</c> "
+"(provided by <c>net-analyzer/netcat</c>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):374
+msgid "Verifying sasl and tls support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):374
+#, no-wrap
+msgid ""
+"\n"
+"# <i>telnet localhost 25</i>\n"
+"\n"
+"Trying 127.0.0.1...\n"
+"Connected to localhost.\n"
+"Escape character is '^]'.\n"
+"220 mail.domain.com ESMTP Postfix\n"
+"<i>EHLO domain.com</i>\n"
+"250-mail.domain.com\n"
+"250-PIPELINING\n"
+"250-SIZE 10240000\n"
+"250-VRFY\n"
+"250-ETRN\n"
+"250-STARTTLS\n"
+"250-AUTH LOGIN PLAIN\n"
+"250-AUTH=LOGIN PLAIN\n"
+"250-XVERP\n"
+"250 8BITMIME\n"
+"<i>^]</i>\n"
+"telnet&gt; <i>quit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):396
+msgid ""
+"Verify that the above AUTH and STARTTLS lines now appear in your postfix "
+"install. As I said before, as it stands now AUTH will not work. that's "
+"because sasl will try to auth against it's sasldb, instead of the shadow "
+"file for some unknown reason, which we have not set up. So we're going to "
+"just plow through and set up mysql to hold all of our auth and virtual "
+"domain information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):409
+msgid "The vmail user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):413
+msgid ""
+"Before we set up our virtual mailhosting environment, we create a functional "
+"user under which the virtual mailboxes will be hosted. For clarity's sake we "
+"will call this <e>vmail</e>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):419
+msgid "Adding the vmail user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):419
+#, no-wrap
+msgid ""
+"\n"
+"# <i>useradd -d /home/vmail -s /bin/false -m vmail</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):423
+msgid ""
+"So now you've set up the vmail account. You can create multiple accounts if "
+"you want (to keep some structure in your set of virtual mail accounts). The "
+"user id, group id and home dirs are referenced in the MySQL tables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):429
+msgid ""
+"Next to the user account we also need to create the location where the "
+"mailboxes will reside:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):434
+msgid "Creating mailboxes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):434
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir -p /home/vmail/virt-domain.com/foo</i>\n"
+"# <i>chown -R vmail:vmail /home/vmail/virt-domain.com</i>\n"
+"# <i>maildirmake /home/vmail/virt-domain.com/foo/.maildir</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):445
+msgid "MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):449
+msgid ""
+"Next we're going to install and configure MySQL. You'll need the <uri link="
+"\"http://www.gentoo.org/doc/en/files/genericmailsql.sql\">genericmailsql."
+"sql</uri> dumpfile for this step."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):455
+msgid "Installing and configuring MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):455
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge mysql</i>\n"
+"\n"
+"# <i>/usr/bin/mysql_install_db</i>\n"
+"<comment>(After this command runs follow the onscreen directions\n"
+"for adding a root password with mysql, otherwise your db will\n"
+"be wide open.)</comment>\n"
+"\n"
+"# <i>/etc/init.d/mysql start</i>\n"
+"# <i>mysqladmin -u root -p create mailsql</i>\n"
+"# <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i>\n"
+"# <i>mysql -u root -p mysql</i>\n"
+"mysql&gt; <i>GRANT SELECT,INSERT,UPDATE,DELETE</i>\n"
+"  -&gt;     <i>ON mailsql.*</i>\n"
+"  -&gt;     <i>TO mailsql@localhost</i>\n"
+"  -&gt;     <i>IDENTIFIED BY '$password';</i>\n"
+"Query OK, 0 rows affected (0.02 sec)\n"
+"\n"
+"mysql&gt; <i>FLUSH PRIVILEGES;</i>\n"
+"Query OK, 0 rows affected (0.00 sec)\n"
+"\n"
+"mysql&gt; <i>quit</i>\n"
+"<comment>(Verify that the new mailsql user can connect to the mysql server.)</comment>\n"
+"\n"
+"# <i>mysql -u mailsql -p mailsql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):482
+msgid ""
+"Your new database has default values and tables set up for two domains. The "
+"following tables are included:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):488
+msgid "alias - local email alias and mailman alias information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):489
+msgid "relocated - relocated user email address maps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):490
+msgid ""
+"transport - default mail transport information for all domains you are "
+"hosting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):494
+msgid "users - all user account information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):495
+msgid "virtual - virtual domain email alias maps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):498
+msgid "alias table sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):498
+#, no-wrap
+msgid ""
+"\n"
+"id   alias      destination\n"
+"1    root       foo@bar.com\n"
+"2    postmaster foo@bar.com\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):504
+msgid "user table sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):504
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Line wrapped for clarity.)</comment>\n"
+"id email            clear     name     uid     gid     homedir     \\\n"
+"  maildir                                quota  postfix\n"
+"10 foo@virt-domain.com $password realname virtid  virtid  /home/vmail \\\n"
+"  /home/vmail/virt-domain.com/foo/.maildir/        y\n"
+"13 foo@bar.com      $password realname localid localid /home/foo   \\\n"
+"  /home/foo/.maildir/                           y\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):514
+msgid ""
+"The values of the <c>virtid</c> uid and gid should be those of the <c>vmail</"
+"c> user and group."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):519
+msgid "transport table sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):519
+#, no-wrap
+msgid ""
+"\n"
+"id   domain          destination\n"
+"1    bar.com         local:\n"
+"2    virt-domain.com virtual:\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):525
+msgid "virtual table sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):525
+#, no-wrap
+msgid ""
+"\n"
+"id   email                destination\n"
+"3    root@virt-domain.com other@email.address\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):535
+msgid "Apache and phpMyAdmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):539
+msgid ""
+"Next we'll set up apache and add an interface to interact with the database "
+"more easily."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):544
+msgid "Setting up apache and phpmyadmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):544
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge apache phpmyadmin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):548
+msgid ""
+"There are plenty of guides out there about how to set up apache with php, "
+"including guides provided by the <uri link=\"/proj/en/php/\">Gentoo PHP "
+"Project</uri>. There are also numerous posts on <uri>http://forums.gentoo."
+"org</uri> detailing how to solve problems with the installation. So, that "
+"said, we're not going to cover it here. Set up the apache and php installs, "
+"then continue with this howto. Now, a word for the wise: .htaccess the "
+"directory that you put phpmyadmin in. If you do not do this, search engine "
+"spiders will come along and index the page which in turn will mean that "
+"anyone will be able to find your phpmyadmin page via google and in turn be "
+"able to come change your database however they want which is <e>BAD!</e> "
+"There are many howtos on this including: <uri>http://www.csoft.net/docs/"
+"micro/htaccess.html.en</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):563
+msgid ""
+"Now we're going to install the Apache certificates we made previously. The "
+"Apache-SSL directives that you need to use the resulting cert are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):569
+msgid "SSLCertificateFile /path/to/certs/new.cert.cert"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):570
+msgid "SSLCertificateKeyFile /path/to/certs/new.cert.key"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):573
+msgid "Install Apache SSL certificates"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):573
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp /etc/ssl/misc/new.cert.cert /etc/apache2/ssl/</i>\n"
+"# <i>cp /etc/ssl/misc/new.cert.key /etc/apache2/ssl/</i>\n"
+"# <i>cd /etc/apache2/vhosts.d</i>\n"
+"<comment>(Check if you have an ssl-vhost template already.\n"
+" Copy that one instead of the default_vhost if that is the case)</comment>\n"
+"# <i>cp 00_default_vhost.conf ssl-vhost.conf</i>\n"
+"# <i>nano -w ssl-vhost.conf</i>\n"
+"\n"
+"<comment>(Change the following parameters)</comment>\n"
+"NameVirtualHost host.domain.name:443\n"
+"\n"
+"&lt;VirtualHost host.domain.name:443&gt;\n"
+"  ServerName host.domain.name\n"
+"  ServerAdmin your@email.address\n"
+"\n"
+"  DocumentRoot \"/var/www/localhost/htdocs/phpmyadmin\";\n"
+"  &lt;Directory \"/var/www/localhost/htdocs/phpmyadmin\"&gt;\n"
+"    ...\n"
+"  &lt;/Directory&gt;\n"
+"\n"
+"  SSLCertificateFile /etc/apache2/ssl/new.cert.cert\n"
+"  SSLCertificateKeyFile /etc/apache2/ssl/new.cert.key\n"
+"  SSLEngine on\n"
+"  ...\n"
+"&lt;/VirtualHost&gt;\n"
+"\n"
+"# <i>nano -w /etc/conf.d/apache2</i>\n"
+"<comment>(Add -D SSL -D PHP5 to the APACHE2_OPTS)</comment>\n"
+"\n"
+"# <i>/etc/init.d/apache2 restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):606
+msgid "Next, configure phpMyAdmin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):610
+msgid "Configuring phpMyAdmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):610
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /var/www/localhost/htdocs/phpmyadmin</i>\n"
+"# <i>cp config.sample.inc.php config.inc.php</i>\n"
+"# <i>nano -w config.inc.php</i>\n"
+"<comment>(Change the following parameters.)</comment>\n"
+"$cfg['blowfish_secret'] = 'someverysecretpassphraze';\n"
+"\n"
+"$cfg['Servers'][$i]['host'] = 'localhost';          // MySQL hostname\n"
+"$cfg['Servers'][$i]['controluser'] = 'mailsql';     // MySQL control user settings\n"
+"                                                    // (this user must have read-only\n"
+"$cfg['Servers'][$i]['controlpass'] = '$password';   // access to the \"mysql/user\"\n"
+"                                                    // and \"mysql/db\" tables)\n"
+"$cfg['Servers'][$i]['user'] = 'mailsql';            // MySQL user\n"
+"$cfg['Servers'][$i]['password'] = '$password';      // MySQL password\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):626
+msgid ""
+"Now enter the phpmyadmin page and browse the tables. You'll want to add in "
+"your local aliases, edit your user table to add a test user, and change your "
+"transport table to add information about your domains. The default values "
+"supplied with the dumpfile should be a sufficient guide to what values need "
+"to go where. Make sure that if you put information in the database that it "
+"is accurate. For instance, make sure the local user's home dir exists and "
+"that the correct uid/gid values are in place. The maildirs should be created "
+"automatically by postfix when the user receives their first email. So, in "
+"general, it's a good idea to send a \"Welcome\" mail to a new user after you "
+"setup their account to make sure the .maildir gets created."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):644
+msgid "Configuring MySQL Authentication and vhosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):648
+msgid ""
+"Next we'll reconfigure our authentication to use the mailsql database in "
+"courier-imap and postfix. In all of the following examples, replace <c>"
+"$password</c> with the password you set for the mailsql mysql user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):654
+msgid "Configuring authentication"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):654
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/courier/authlib/authdaemonrc</i>\n"
+"authmodulelist=\"authmysql authpam\"\n"
+"\n"
+"# <i>nano -w /etc/courier/authlib/authmysqlrc</i>\n"
+"MYSQL_SERVER            localhost\n"
+"MYSQL_USERNAME       mailsql\n"
+"MYSQL_PASSWORD      $password\n"
+"MYSQL_DATABASE          mailsql\n"
+"MYSQL_USER_TABLE        users\n"
+"<comment>(Make sure the following line is commented out since we're storing plaintext.)</comment>\n"
+"#MYSQL_CRYPT_PWFIELD    crypt\n"
+"MYSQL_CLEAR_PWFIELD     clear\n"
+"MYSQL_UID_FIELD         uid\n"
+"MYSQL_GID_FIELD         gid\n"
+"MYSQL_LOGIN_FIELD       email\n"
+"MYSQL_HOME_FIELD        homedir\n"
+"MYSQL_NAME_FIELD        name\n"
+"MYSQL_MAILDIR_FIELD     maildir\n"
+"\n"
+"# <i>/etc/init.d/courier-authlib restart</i>\n"
+"# <i>/etc/init.d/saslauthd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):678
+msgid ""
+"We're almost there, I promise! Next, set up the rest of the necessary "
+"configs for postfix to interract with the database for all its other "
+"transport needs. Remember to replace each value with the name of your own "
+"user, user id, password, alias, email address, and so on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):685
+msgid "/etc/postfix/mysql-aliases.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):685
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/mysql-aliases.cf</i>\n"
+"# mysql-aliases.cf\n"
+"\n"
+"user         = mailsql\n"
+"password     = $password\n"
+"dbname       = mailsql\n"
+"table        = alias\n"
+"select_field = destination\n"
+"where_field  = alias\n"
+"hosts        = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):698
+msgid "/etc/postfix/mysql-relocated.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):698
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/mysql-relocated.cf</i>\n"
+"# mysql-relocated.cf\n"
+"\n"
+"user         = mailsql\n"
+"password     = $password\n"
+"dbname       = mailsql\n"
+"table        = relocated\n"
+"select_field = destination\n"
+"where_field  = email\n"
+"hosts        = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):711
+msgid "/etc/postfix/mysql-transport.cf (optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):711
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/mysql-transport.cf</i>\n"
+"# mysql-transport.cf\n"
+"\n"
+"user         = mailsql\n"
+"password     = $password\n"
+"dbname       = mailsql\n"
+"table        = transport\n"
+"select_field = destination\n"
+"where_field  = domain\n"
+"hosts        = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):724
+msgid "/etc/postfix/mysql-virtual-gid.cf (optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):724
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i>\n"
+"# mysql-virtual-gid.cf\n"
+"\n"
+"user            = mailsql\n"
+"password        = $password\n"
+"dbname          = mailsql\n"
+"table           = users\n"
+"select_field    = gid\n"
+"where_field     = email\n"
+"additional_conditions = and postfix = 'y'\n"
+"hosts           = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):738
+msgid "/etc/postfix/mysql-virtual-maps.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):738
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i>\n"
+"# mysql-virtual-maps.cf\n"
+"\n"
+"user            = mailsql\n"
+"password        = $password\n"
+"dbname          = mailsql\n"
+"table           = users\n"
+"select_field    = maildir\n"
+"where_field     = email\n"
+"additional_conditions = and postfix = 'y'\n"
+"hosts           = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):752
+msgid "/etc/postfix/mysql-virtual-uid.cf (optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):752
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i>\n"
+"# mysql-virtual-uid.cf\n"
+"\n"
+"user            = mailsql\n"
+"password        = $password\n"
+"dbname          = mailsql\n"
+"table           = users\n"
+"select_field    = uid\n"
+"where_field     = email\n"
+"additional_conditions = and postfix = 'y'\n"
+"hosts           = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):766
+msgid "/etc/postfix/mysql-virtual.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):766
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/mysql-virtual.cf</i>\n"
+"# mysql-virtual.cf\n"
+"\n"
+"user         = mailsql\n"
+"password     = $password\n"
+"dbname       = mailsql\n"
+"table        = virtual\n"
+"select_field = destination\n"
+"where_field  = email\n"
+"hosts        = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):779
+msgid "Lastly, edit <path>/etc/postfix/main.cf</path> one more time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):783
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/main.cf</i>\n"
+"<comment>(Ensure that there are no other alias_maps definitions)</comment>\n"
+"alias_maps = mysql:/etc/postfix/mysql-aliases.cf\n"
+"relocated_maps = mysql:/etc/postfix/mysql-relocated.cf\n"
+"\n"
+"local_transport = local\n"
+"local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname\n"
+"\n"
+"virtual_transport = virtual\n"
+"<comment>(The domains listed by the mydestination should not be listed in\n"
+" the virtual_mailbox_domains parameter)</comment>\n"
+"virtual_mailbox_domains = virt-domain.com, $other-virtual-domain.com\n"
+"\n"
+"virtual_minimum_uid = 1000\n"
+"<comment>(Substitute $vmail-gid with the GID of the vmail group)</comment>\n"
+"virtual_gid_maps = static:$vmail-gid\n"
+"virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf\n"
+"virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf\n"
+"<comment>(Substitute $vmail-uid with the UID of the vmail user)</comment>\n"
+"virtual_uid_maps = static:$vmail-uid\n"
+"virtual_mailbox_base = /\n"
+"#virtual_mailbox_limit =\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):808
+msgid ""
+"For security reasons you should change the permissions of the various <path>/"
+"etc/mail/mysql-*.cf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):813
+msgid "Changing file permission"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):813
+#, no-wrap
+msgid ""
+"\n"
+"# <i>chmod 640 /etc/postfix/mysql-*.cf</i>\n"
+"# <i>chgrp postfix /etc/postfix/mysql-*.cf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):818
+msgid ""
+"As of Postfix 2.0.x, there were a number of significant changes over the 1.1."
+"x release. Notably the transport, virtual-gid, and virtual-uid tables are no "
+"longer necessary. The tables are still included if you wish to use them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(note):824
+msgid ""
+"It is recommended that you read VIRTUAL_README included with the postfix "
+"docs for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):829
+msgid "Make postfix reload its tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):829
+#, no-wrap
+msgid ""
+"\n"
+"# <i>postfix reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):833
+msgid ""
+"Now, if all went well, you should have a functioning mailhost. Users should "
+"be able to authenticate against the sql database, using their full email "
+"address, for pop3, imap, and smtp. I would highly suggest that you verify "
+"that everything is working at this point. If you run into problems (with as "
+"many things as this setup has going on, it's likely that you will) check the "
+"troubleshooting section of this howto."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):847
+msgid "Squirrelmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):851
+msgid "Install squirrelmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):851
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge squirrelmail</i>\n"
+"<comment>(Install squirrelmail to localhost so that it's accessed by http://localhost/mail)\n"
+"(Substitute 1.4.3a-r2 with the version you use)</comment>\n"
+"\n"
+"# <i>webapp-config -I -h localhost -d /mail squirrelmail 1.4.3a-r2</i>\n"
+"# <i>cd /var/www/localhost/htdocs/mail/config</i>\n"
+"# <i>perl ./conf.pl</i>\n"
+"<comment>(Change your Organization, Server, and Folder settings for squirrelmail.\n"
+"Now you should be able to login to squirrelmail, again - with your full email address,\n"
+"and use your new webmail setup.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):869
+msgid "Mailman"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):873
+msgid ""
+"Last step: mailman. The new version of mailman has very nice virtual domain "
+"support, which is why I use it, not to mention it's really a great package. "
+"To get this package installed and working correctly for virtual domains is "
+"going to require a bit of hacking. I really recommend reading all of the "
+"mailman documentation, including README.POSTFIX.gz, to understand what's "
+"being done here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):882
+msgid "Install mailman"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):882
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge mailman</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):886
+msgid "Setting defaults: Mailman/Defaults.py"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):886
+#, no-wrap
+msgid ""
+"\n"
+"# <i> nano -w /usr/local/mailman/Mailman/Defaults.py</i>\n"
+"<comment>(Change the values below to reflect your primary domain, virtuals will be set next.)</comment>\n"
+"DEFAULT_EMAIL_HOST = 'domain.com'\n"
+"DEFAULT_URL_HOST = 'www.domain.com'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):893
+msgid "mailman config: mm_cfg.py"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):893
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /usr/local/mailman/Mailman/mm_cfg.py</i>\n"
+"MTA = \"Postfix\"\n"
+"POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com']\n"
+"add_virtualhost('www.virt.domain.com', 'virt.domain.com')\n"
+"add_virtualhost('www.virt.domain2.com', 'virt.domain2.com')\n"
+"<comment>(This is required for your virtual domains for mailman to function.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):902
+msgid "And last but not least"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):902
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Once that's finished, add your first list.)</comment>\n"
+"\n"
+"# <i>su mailman</i>\n"
+"# <i>cd ~</i>\n"
+"# <i>./bin/newlist --urlhost='www.virt-domain.com' --emailhost='virt-domain.com' test</i>\n"
+"Enter the email of the person running the list: <i>your@email.address</i>\n"
+"Initial test password:\n"
+"Hit enter to continue with test owner notification...\n"
+"<comment>(Virtual domain lists may also be specified with\n"
+"list@domain.com style list names.)</comment>\n"
+"# <i>./bin/genaliases</i>\n"
+"<comment>(Now that your aliases have been generated,\n"
+"verify that they were added successfully.)</comment>\n"
+"\n"
+"# <i>nano -w data/aliases</i>\n"
+"# STANZA START: test\n"
+"# CREATED:\n"
+"test:             \"|/usr/local/mailman/mail/mailman post test\"\n"
+"test-admin:       \"|/usr/local/mailman/mail/mailman admin test\"\n"
+"test-bounces:     \"|/usr/local/mailman/mail/mailman bounces test\"\n"
+"test-confirm:     \"|/usr/local/mailman/mail/mailman confirm test\"\n"
+"test-join:        \"|/usr/local/mailman/mail/mailman join test\"\n"
+"test-leave:       \"|/usr/local/mailman/mail/mailman leave test\"\n"
+"test-owner:       \"|/usr/local/mailman/mail/mailman owner test\"\n"
+"test-request:     \"|/usr/local/mailman/mail/mailman request test\"\n"
+"test-subscribe:   \"|/usr/local/mailman/mail/mailman subscribe test\"\n"
+"test-unsubscribe: \"|/usr/local/mailman/mail/mailman unsubscribe test\"\n"
+"# STANZA END: test\n"
+"\n"
+"<comment>(Create the required mailman list)</comment>\n"
+"# <i>./bin/newlist mailman</i>\n"
+"# <i>./bin/genaliases</i>\n"
+"\n"
+"<comment>(Return to the root user)</comment>\n"
+"# <i>exit</i>\n"
+"\n"
+"# <i>/etc/init.d/mailman start</i>\n"
+"# <i>rc-update add mailman default</i>\n"
+"<comment>(To start mailman at once and on every reboot.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):944
+msgid "Adding mailman alias support to postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):944
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/main.cf</i>\n"
+"owner_request_special = no\n"
+"recipient_delimiter = +\n"
+"<comment>(Read README.POSTFIX.gz for details on this.)</comment>\n"
+"\n"
+"alias_maps     =\n"
+"  hash:/usr/local/mailman/data/aliases,\n"
+"  mysql:/etc/postfix/mysql-aliases.cf\n"
+"\n"
+"virtual_alias_maps =\n"
+"  hash:/usr/local/mailman/data/virtual-mailman,\n"
+"  mysql:/etc/postfix/mysql-virtual.cf\n"
+"<comment>(This adds mailman alias file support to postfix\n"
+"You may of course use the mysql tables for this,\n"
+"but I hate doing that by hand. Also, if you are not\n"
+"using virtual domains, adding the virtual alias maps\n"
+"to postfix may cause problems, be warned.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):964
+msgid ""
+"You should now be able to setup mailing lists for any domain on your box. "
+"Last note on this, make sure you run all mailman commands as the user "
+"mailman (<c>su mailman</c>) or else the permissions will be wrong and you'll "
+"have to fix them. Read the mailman doc's for more information on setting up "
+"and managing mailman lists."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):977
+msgid "Content Filtering and Anti-Virus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):981
+msgid ""
+"For content filtering and Anti-Virus, please consult our <uri link=\"/doc/en/"
+"mailfilter-guide.xml\">mail filtering gateway guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):991
+msgid "Wrap Up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):995
+msgid ""
+"Ok, you're all set, edit <path>/etc/postfix/master.cf</path> and turn off "
+"verbose mode for production use. You'll probably also want to add the "
+"services to your startup routine to make sure everything comes back up on a "
+"reboot. Make sure to add all the services you're using - apache, mysql, "
+"saslauthd, postfix, courier-imapd, courier-imapd-ssl, courier-pop3d, and "
+"courier-pop3d-ssl are all up to your decision on what access you want to "
+"provide. I generally have all the services enabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1005
+msgid "Wrap up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1005
+#, no-wrap
+msgid ""
+"\n"
+"# <i>postfix reload</i>\n"
+"# <i>rc-update add $service default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(e):1011
+msgid "Have fun!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1019
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1024
+msgid ""
+"Troubleshooting: This is a short troubleshooting guide for the set up we've "
+"detailed how to install here. It is not exhaustive, but meant as a place to "
+"get you started in figuring out problems. With a complicated setup such as "
+"this, it's imperative that you narrow down the problem to the particular "
+"component that is malfunctioning. In general I do that by following a few "
+"steps. Start from the base of the system and work your way up, ruling out "
+"components that work along the way until you discover which component is "
+"having the problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1037
+msgid "Step 1: Check your config files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1040
+msgid ""
+"Typos are killers, especially when dealing with authentication systems. Scan "
+"your config's and mailsql database for typo's. You can debug all you want, "
+"but if you're not passing the right information back and forth to your mail "
+"system, it's not going to work. If you make a change to a config file for a "
+"service, make sure you restart that service so that the config change gets "
+"picked up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1048
+msgid "How to restart a service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1048
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/service restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1055
+msgid "Step 2: Are all the necessary services actually running?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1058
+msgid ""
+"If it's not running, start it up. It's awful hard to debug a service that "
+"isn't running. Sometimes a service will act like it's started but still not "
+"function. Sometimes, when a bad config is used, or a bad transmission comes "
+"into a mail component, the service will hang and keep the port from being "
+"used by another process. Sometimes you can detect this with netstat. Or, if "
+"you've been at it awhile, just take a break and reboot your box in the "
+"meantime. That will clear out any hung services. Then you can come back "
+"fresh and try it again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1068
+msgid "Checking the status of a service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1068
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/$service status</i>\n"
+"# <i>netstat -a | grep $service (or $port)</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1076
+msgid "Step 3: Are all the service using the current config's?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1079
+msgid ""
+"If you've recently made a change to a config file, restart that service to "
+"make sure it's using the current version. Some of the components will dump "
+"their current config's to you, like postfix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1085
+msgid "Some services can dump their current config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1085
+#, no-wrap
+msgid ""
+"\n"
+"# <i>apache2ctl fullstatus</i> (needs lynx installed)\n"
+"# <i>apache2ctl configtest</i> (checks config sanity)\n"
+"# <i>postconf -n</i> (will tell you exactly what param's postfix is using)\n"
+"# <i>/etc/init.d/$service restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1095
+msgid "Step 4: Check the logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1098
+msgid ""
+"Repeat after me, logs are my friend. My next troubleshooting stop is always "
+"the logs. Sometimes it's helpful to try a failed operation again then check "
+"the logs so that the error message is right at the bottom (or top depending "
+"on your logger) instead of buried in there somewhere. See if there is any "
+"information in your log that can help you diagnose the problem, or at the "
+"very least, figure out which component is having the problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1107
+msgid "Checking the logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1107
+#, no-wrap
+msgid ""
+"\n"
+"# <i>kill -USR1 `ps -C metalog -o pid=`</i>(to turn off metalog buffering)\n"
+"# <i>nano -w /var/log/mail/current</i>\n"
+"# <i>cat /var/log/mysql/mysql.log</i>\n"
+"# <i>tail /var/log/apache2/error_log</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1114
+msgid ""
+"You may also find the debug_peer parameters in main.cf helpful. Setting "
+"these will increase log output over just verbose mode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1119
+msgid "adding debug_peer support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1119
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/postfix/main.cf</i>\n"
+"debug_peer_level = 5\n"
+"debug_peer_list = $host.domain.name\n"
+"<comment>(Uncomment one of the suggested debugger\n"
+"commands as well.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1130
+msgid "Step 5: Talk to the service itself"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1133
+msgid ""
+"SMTP, IMAP, and POP3 all respond to telnet sessions. As we've seen earlier "
+"when we verified postfix's config. Sometimes it's helpful to open a telnet "
+"session to the service itself and see what's happening."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1139
+msgid "Connect to a service with telnet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1139
+#, no-wrap
+msgid ""
+"\n"
+"# <i>telnet localhost $port</i>\n"
+"<comment>(SMTP is 25, IMAP is 143, POP3 is 110. You should receive at least an OK string,\n"
+"letting you know that the service is running and ready to respond to requests.)</comment>\n"
+"\n"
+"Trying 127.0.0.1...\n"
+"Connected to localhost.\n"
+"Escape character is '^]'.\n"
+"* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1153
+msgid ""
+"Step 6: Sometimes only the big guns will give you the information you need: "
+"strace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1156
+msgid ""
+"You should have this installed anyway. This is an invaluable tool for "
+"debugging software. You can start commands from the command line with strace "
+"and watch all the system calls as they happen. It often dumps a huge amount "
+"of information, so you'll either need to watch it realtime as you retry a "
+"failed transaction with the mail system, or dump the output to a file for "
+"review."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1164
+msgid "Using strace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1164
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge strace</i>\n"
+"# <i>strace $command</i>\n"
+"# <i>strace -p `ps -C $service -o pid=`</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1173
+msgid "Step 7: Research"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1176
+msgid ""
+"Once you have the information, if you can diagnose and fix the problem, "
+"great! If not, you'll probably need to go digging on the net for information "
+"that will help you fix it. Here's a list of sites you can check to see if "
+"your error has already been resolved. There's also a really good howto on "
+"setting up smtp-auth which contains some great debugging ideas."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1185
+msgid "<uri>http://forums.gentoo.org/</uri> - Great forums for gentoo users"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1186
+msgid ""
+"<uri>http://bugs.gentoo.org/</uri> - Bugs database for gentoo - great place "
+"to look for specific errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1190
+msgid "<uri>http://postfix.state-of-mind.de/</uri> - smtp-auth howto"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1191
+msgid ""
+"<uri>http://marc.theaimsgroup.com/?l=postfix-users</uri> - Postfix mailing "
+"lists - searchable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1195
+msgid ""
+"<uri>http://sourceforge.net/mailarchive/forum.php?forum_id=6705</uri> - "
+"Courier-imap mailing list archives - not searchable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1199
+msgid ""
+"<uri>http://www.google.com/</uri> - If all else fails, there's always "
+"google, which has never failed me"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1203
+msgid ""
+"I also spend a lot of time on <uri link=\"irc://irc.gentoo.org/gentoo"
+"\">#gentoo</uri>. IRC is a great place to go for help."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/vpnc-howto.xml.po b/doc/gettext/ru/vpnc-howto.xml.po
new file mode 100644
index 0000000..cb6c688
--- /dev/null
+++ b/doc/gettext/ru/vpnc-howto.xml.po
@@ -0,0 +1,1175 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):6
+msgid "Gentoo vpnc HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):9
+msgid "dhaskew@earthlink.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail):9
+msgid "David H. Askew"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):17
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):12
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail):12
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):15
+msgid "fauli@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail):15
+msgid "Christian Faulhammer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):18
+msgid "fischer@unix-ag.uni-kl.de"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail):18
+msgid "Thomas Fischer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):21
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(abstract):24
+msgid ""
+"This document details how to connect your workstation to a Cisco VPN "
+"concentrator utilizing vpnc to manage the connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(version):33
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(date):34
+msgid "2010-07-29"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):37
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):41
+msgid ""
+"If you're reading this, then you likely need to connect to your office "
+"network from home or during travel. Many companies utilize Cisco 3000 VPN "
+"concentrators for their VPN needs, and I am willing to bet that most Linux "
+"newbies think that they are forced to use Windows to connect to them. Well, "
+"this document informs you that connecting to a Cisco VPN is very possible "
+"and will hopefully enable you to setup a working tunnel using your Gentoo "
+"workstation or laptop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):53
+msgid "What this document is"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):57
+msgid "A guide to the basic workings of <c>vpnc</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):58
+msgid "A discussion of DNS and routing issues that relate to VPNs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):59
+msgid "Examples of managing VPN sessions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):60
+msgid "Useful tips and tricks (hopefully)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):66
+msgid "What this document is not"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):70
+msgid "An in-depth guide to VPN/encryption technologies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):71
+msgid "A feature by feature explanation of <c>vpnc</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):77
+msgid "Assumptions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):80
+msgid "The assumptions made at this point are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):85
+msgid "You have Gentoo installed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):86
+msgid "You have Internet access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):87
+msgid "You want to connect to a Cisco 3000 VPN concentrator"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):88
+msgid "You know how to configure, build, and install a new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):96
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):100
+msgid ""
+"In order for Linux to be able to open a VPN connection <e>Universal TUN/TAP "
+"device driver support</e> must be enabled in the kernel. What is it and why "
+"do you need it? Below is a relatively straight forward explanation from the "
+"kernel configuration dialog:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):107
+msgid "CONFIG_TUN"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):107
+#, no-wrap
+msgid ""
+"\n"
+"TUN/TAP provides packet reception and transmission for user space\n"
+"programs. It can be viewed as a simple Point-to-Point or Ethernet\n"
+"device, which instead of receiving packets from a physical media,\n"
+"receives them from user space program and instead of sending packets\n"
+"via physical media writes them to the user space program.\n"
+"\n"
+"When a program opens /dev/net/tun, driver creates and registers\n"
+"corresponding net device tunX or tapX. After a program closed above\n"
+"devices, driver will automatically delete tunXX or tapXX device and\n"
+"all routes corresponding to it.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):120
+msgid ""
+"You can verify yourself if your kernel has TUN/TAP support with the "
+"following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):125
+msgid "Checking the kernel config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):125
+#, no-wrap
+msgid ""
+"\n"
+"# <i> grep \"TUN\" /usr/src/linux/.config</i>\n"
+"CONFIG_INET_TUNNEL=m\n"
+"# CONFIG_INET6_TUNNEL is not set\n"
+"# CONFIG_IPV6_TUNNEL is not set\n"
+"<comment>(TUN/TAP enabled as a module)</comment>\n"
+"CONFIG_TUN=m\n"
+"# CONFIG_8139TOO_TUNE_TWISTER is not set\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):135
+msgid ""
+"As you can see above, <c>CONFIG_TUN=m</c> is compiled as a module. If it is "
+"disabled in your setup, enable it in your kernel of choice, rebuild, "
+"install, reboot and return to this document before continuing with the next "
+"steps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):141
+msgid "Configuration location in the kernel configuration dialog"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):141
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers  ---&gt;\n"
+"  Network device support  ---&gt;\n"
+"    [*] Universal TUN/TAP device driver support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):147
+msgid ""
+"If you built TUN/TAP support directly into the kernel, you should see "
+"information from <c>dmesg</c> output like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):152
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):174
+msgid "Checking dmesg output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):152
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):174
+#, no-wrap
+msgid ""
+"\n"
+"# <i>dmesg | grep TUN</i>\n"
+"Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):157
+msgid ""
+"If you build TUN/TAP support as a module, you first must load the <c>tun</c> "
+"module:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):162
+msgid "Load tun module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):162
+#, no-wrap
+msgid ""
+"\n"
+"# <i>modprobe tun</i>\n"
+"# <i>lsmod</i>\n"
+"Module                  Size  Used by\n"
+"tun                     7296  0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):169
+msgid ""
+"Now that the <c>tun</c> module is loaded, check <c>dmesg</c> output. You "
+"should see something like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):184
+msgid "Install Needed Software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):188
+msgid ""
+"Now that you have a working kernel setup, you need to install <c>net-misc/"
+"vpnc</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):193
+msgid "Installing vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):193
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av net-misc/vpnc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):202
+msgid "Example Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):206
+msgid ""
+"In order to make the following sections more clear, we need an example setup "
+"to work from. For the purposes of this exercise, we will assume that you "
+"have a home network of several computers. All computers are on the "
+"192.168.0.0 / 255.255.255.0 network. The LAN in question is run by a Gentoo "
+"box using an iptables firewall, DHCP, caching DNS, etc ... and it "
+"masquerades the LAN behind the public IP address it receives from an ISP. "
+"You also have a workstation on the LAN from which you want to be able to VPN "
+"into your office with."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):216
+msgid "Our example workstation configuration looks like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):220
+msgid "Our workstation configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):220
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Name server configuration)</comment>\n"
+"# <i>cat /etc/resolv.conf</i>\n"
+"nameserver      192.168.0.1\n"
+"\n"
+"<comment>(Network configuration)</comment>\n"
+"# <i>cat /etc/hosts</i>\n"
+"127.0.0.1       desktop localhost\n"
+"192.168.0.1     router\n"
+"192.168.2.2     mediacenter\n"
+"\n"
+"<comment>(Interface configuration)</comment>\n"
+"# <i>ifconfig -a</i>\n"
+"eth0      Link encap:Ethernet  HWaddr 00:11:2F:8D:08:08\n"
+"          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0\n"
+"          inet6 addr: fe80::211:2fff:fe8d:808/64 Scope:Link\n"
+"          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1\n"
+"          RX packets:3657889 errors:0 dropped:0 overruns:0 frame:0\n"
+"          TX packets:2305893 errors:0 dropped:0 overruns:0 carrier:0\n"
+"          collisions:0 txqueuelen:1000\n"
+"          RX bytes:2193722103 (2092.0 Mb)  TX bytes:1415104432 (1349.5 Mb)\n"
+"          Interrupt:185 Memory:fac00000-0\n"
+"\n"
+"lo        Link encap:Local Loopback\n"
+"          inet addr:127.0.0.1  Mask:255.0.0.0\n"
+"          inet6 addr: ::1/128 Scope:Host\n"
+"          UP LOOPBACK RUNNING  MTU:16436  Metric:1\n"
+"          RX packets:35510 errors:0 dropped:0 overruns:0 frame:0\n"
+"          TX packets:35510 errors:0 dropped:0 overruns:0 carrier:0\n"
+"          collisions:0 txqueuelen:0\n"
+"          RX bytes:16023838 (15.2 Mb)  TX bytes:16023838 (15.2 Mb)\n"
+"\n"
+"<comment>(Routing information)</comment>\n"
+"# <i>netstat -r</i>\n"
+"Kernel IP routing table\n"
+"Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface\n"
+"192.168.0.0     *               255.255.255.0   U         0 0          0 eth0\n"
+"loopback        desktop         255.0.0.0       UG        0 0          0 lo\n"
+"default         router          0.0.0.0         UG        0 0          0 eth0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):266
+msgid "Configuring vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):270
+msgid ""
+"Now that you have <c>vpnc</c> installed and we have an example to work from, "
+"let's discuss the basics of setting up <c>vpnc</c>. The configuration file "
+"for <c>vpnc</c> connection settings can be located in a couple places, "
+"depending on how many profiles you want to setup. By default, <c>vpnc</c> "
+"looks first for <path>/etc/vpnc/default.conf</path> for its connection "
+"settings. If it doesn't find that file, then it looks for <path>/etc/vpnc."
+"conf</path>. This setup will only address a single profile example and will "
+"use the configuration file location <path>/etc/vpnc.conf</path>. Make sure "
+"you do <e>not</e> have a <path>/etc/vpnc/default.conf</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):282
+msgid "Example /etc/vpnc.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):282
+#, no-wrap
+msgid ""
+"\n"
+"IPSec gateway vpngateway.domain.org\n"
+"IPSec ID group_id\n"
+"IPSec secret group_password\n"
+"Xauth username network_signon\n"
+"Xauth password network_password\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):290
+msgid ""
+"The configuration file example above should be modified to reflect the "
+"appropriate values for your setup. The gateway option <c>vpngateway.domain."
+"org</c> can be a fully qualified domain name or an IP address. The ID and "
+"secret options should be given to you by a network administrator. If you "
+"cannot obtain this information but you currently have a working setup on a "
+"Windows box which utilizes the official Cisco VPN client, then all you have "
+"to do is export your profile. The user name and password options are for "
+"your normal network sign-on, such as a Windows NT domain account."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):302
+msgid ""
+"If you are forced to export your profile from a Windows machine, then what "
+"you will likely have is a file ending in <path>.pcf</path>. This file will "
+"have all the information you need. Below is an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):308
+msgid "Example profile.pcf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):308
+#, no-wrap
+msgid ""
+"\n"
+"[main]\n"
+"Description=\n"
+"Host=VPNGATEWAY.DOMAIN.ORG\n"
+"AuthType=1\n"
+"GroupName=group_id\n"
+"GroupPwd=\n"
+"enc_GroupPwd=F3256220AA200A1D532556024F4F314B0388D48B0FBF2DB12\n"
+"EnableISPConnect=0\n"
+"ISPConnectType=0\n"
+"ISPConnect=FOOBAR\n"
+"ISPCommand=\n"
+"Username=\n"
+"SaveUserPassword=0\n"
+"UserPassword=\n"
+"enc_UserPassword=\n"
+"NTDomain=\n"
+"EnableBackup=0\n"
+"BackupServer=\n"
+"EnableMSLogon=1\n"
+"MSLogonType=0\n"
+"EnableNat=1\n"
+"TunnelingMode=0\n"
+"TcpTunnelingPort=10000\n"
+"CertStore=0\n"
+"CertName=\n"
+"CertPath=\n"
+"CertSubjectName=\n"
+"CertSerialHash=00000000000000000000000000000000\n"
+"SendCertChain=0\n"
+"VerifyCertDN=\n"
+"DHGroup=2\n"
+"ForceKeepAlives=0\n"
+"PeerTimeout=90\n"
+"EnableLocalLAN=0\n"
+"EnableSplitDNS=1\n"
+"ForceNetLogin=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):347
+msgid ""
+"In the above example, we can see entries for <c>Host</c>, <c>GroupName</c> "
+"and <c>enc_GroupPwd</c>. Your <c>Username</c> and <c>UserPassword</c> may or "
+"may not be exported depending on the setup. To generate a working vpnc "
+"configuration out of it, you can use <c>pcf2vpnc</c>, included with vpnc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):354
+msgid ""
+"You can decrypt the password with the help from the <c>cisco-decrypt</c> "
+"program, shipped with the latest vpnc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):362
+msgid "Testing your setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):365
+msgid ""
+"Now that you have a configuration in place, it's time to test your setup. To "
+"start <c>vpnc</c> you do the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):370
+msgid "Example vpnc usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):370
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vpnc</i>\n"
+"Enter password for username@vpngateway.domain.org:\n"
+"VPNC started in background (pid: 14788)...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):376
+msgid ""
+"As you can see from the above command output, once you type <c>vpnc</c> (as "
+"root), you are prompted for your password. After entering your password, "
+"which will not be echoed back to you, the <c>vpnc</c> process will "
+"automatically become a background process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):383
+msgid ""
+"If you specified the <c>Xauth password</c> option in your <c>vpnc</c> config "
+"file, then you will not be prompted for your password at <c>vpnc</c> "
+"startup. Additionally, if <c>vpnc</c> needs some extra options not specified "
+"in the configuration file, or if you have forgotten something, don't worry, "
+"it will ask you for it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):391
+msgid "Sample interface configuration changes made by vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):391
+#, no-wrap
+msgid ""
+"\n"
+"# <i> ifconfig -a</i>\n"
+"eth1      Link encap:Ethernet  HWaddr 00:11:2F:8D:08:08\n"
+"          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0\n"
+"          inet6 addr: fe80::211:2fff:fe8d:808/64 Scope:Link\n"
+"          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1\n"
+"          RX packets:2101119 errors:0 dropped:0 overruns:0 frame:0\n"
+"          TX packets:1577559 errors:0 dropped:0 overruns:0 carrier:0\n"
+"          collisions:0 txqueuelen:1000\n"
+"          RX bytes:1757862627 (1676.4 Mb)  TX bytes:732200131 (698.2 Mb)\n"
+"          Interrupt:177 Memory:faa00000-0\n"
+"\n"
+"sit0      Link encap:IPv6-in-IPv4\n"
+"          NOARP  MTU:1480  Metric:1\n"
+"          RX packets:0 errors:0 dropped:0 overruns:0 frame:0\n"
+"          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0\n"
+"          collisions:0 txqueuelen:0\n"
+"          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)\n"
+"\n"
+"tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00\n"
+"          inet addr:192.168.160.42  P-t-P:192.168.160.42  Mask:255.255.255.255\n"
+"          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1412  Metric:1\n"
+"          RX packets:1 errors:0 dropped:0 overruns:0 frame:0\n"
+"          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0\n"
+"          collisions:0 txqueuelen:500\n"
+"          RX bytes:60 (60.0 b)  TX bytes:616 (616.0 b)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):419
+msgid "Sample routing modifications made by vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):419
+#, no-wrap
+msgid ""
+"\n"
+"# <i>netstat -r</i>\n"
+"Kernel IP routing table\n"
+"Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface\n"
+"vpn01.domain.or router          255.255.255.255 UGH    1500 0          0 eth1\n"
+"192.168.0.0     *               255.255.255.0   U         0 0          0 eth1\n"
+"loopback        desktop         255.0.0.0       UG        0 0          0 lo\n"
+"default         *               0.0.0.0         U         0 0          0 tun0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):429
+msgid ""
+"As you can see from the above command output(s), <c>vpnc</c> has done the "
+"following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):435
+msgid ""
+"Created the tun0 network interface, a virtual interface to handle the "
+"traffic across your VPN tunnel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):439
+msgid "Obtained the IP address for the tun0 device from your VPN provider"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):440
+msgid "Set the default route to your VPN gateway"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):443
+msgid ""
+"At this point, your workstation is capable of communicating with hosts via "
+"the VPN. Because <c>vpnc</c> sets your default route to your VPN gateway, "
+"all network traffic will travel across the VPN, even if it destined for the "
+"Internet or elsewhere not specifically specified by additional routes. For "
+"some, this basic type of connection may be satisfactory, but for most, "
+"additional steps need to be taken."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):452
+msgid "Additional things you might want to have:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):457
+msgid "DNS for the VPN"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):458
+msgid ""
+"A routing setup that will only send traffic destined for the VPN down the "
+"virtual tunnel. This way, you can browse the Internet while connected to the "
+"VPN, without your personal web/p2p etc. traffic going across the tunnel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):464
+msgid ""
+"A script to manage all this, because <c>vpnc</c> just doesn't do enough by "
+"default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):470
+msgid ""
+"When you are ready to end the VPN session, execute <c>vpnc-disconnect</c>. "
+"An example is shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):475
+msgid ""
+"Don't disconnect yet, because we have additional things to test. The example "
+"below is just for informational purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):480
+msgid "vpnc-disconnect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):480
+#, no-wrap
+msgid ""
+"\n"
+"# <i>vpnc-disconnect</i>\n"
+"Terminating vpnc daemon (pid: 26250)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):490
+msgid "Set up DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):494
+msgid ""
+"Unfortunately, <c>vpnc</c> doesn't handle the setup and management of DNS "
+"for your newly established tunnel. The user is left to decide how DNS should "
+"be handled. You could just overwrite <path>/etc/resolv.conf</path> when you "
+"connect, but that would utilize your VPN DNS for all DNS queries regardless "
+"of whether or not the traffic is destined for your VPN tunnel. This is a "
+"very functional solution and if you simply need to connect to the tunnel, do "
+"your work, and then disconnect, read no further. But, if you want to be able "
+"to leave your tunnel connected for lengthy periods of time and don't want "
+"your work DNS servers handling requests for your personal traffic, read on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):506
+msgid ""
+"The ideal setup would allow you to separate your DNS queries into two "
+"categories: VPN-related and other. Under this setup, all VPN-related DNS "
+"queries would be answered by DNS servers located at the other end of your "
+"VPN tunnel and all other queries would continue to be answered by local or "
+"ISP supplied DNS servers. This is the setup that will be demonstrated here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):514
+msgid ""
+"We will consider VPN-related DNS queries to be any query belonging to the "
+"example.org domain, such as host1.example.org or server1.example.org."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):519
+msgid ""
+"So how do you set things up, so that only requests made to hosts on the "
+"example.org domain get sent to VPN supplied DNS servers? Well, you're going "
+"to need to install a local DNS server, but don't worry, it's much easier "
+"than you think. There are several software packages that can handle the type "
+"of setup we desire, but for the purposes of this demonstration, <c>dnsmasq</"
+"c> will be utilized. Let's emerge it now:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):528
+msgid ""
+"This DNS server software will not be available to the network, and will only "
+"answer requests from localhost, <c>127.0.0.1</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):533
+msgid "Install dnsmasq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):533
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge dnsmasq</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):537
+msgid ""
+"Now you need to add an option to your <c>dnsmasq</c> startup options. Edit "
+"the following option to suit your needs. Substitute .example.org with the "
+"appropriate domain and the IP address with a valid DNS server that belongs "
+"to the VPN tunnel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):544
+msgid "/etc/conf.d/dnsmasq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):544
+#, no-wrap
+msgid ""
+"\n"
+"Config file for /etc/init.d/dnsmasq\n"
+"\n"
+"# See the dnsmasq(8) man page for possible options to put here.\n"
+"DNSMASQ_OPTS=\"-S /.example.org/192.168.125.10\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):551
+msgid ""
+"Next, make sure that the first entry in <path>/etc/resolv.conf</path> is "
+"your local host <c>127.0.0.1</c>, followed by the location of the backup DNS "
+"servers that should handle the DNS traffic in case dnsmasq fails to start, "
+"or if it needs to forward a DNS query it doesn't currently have in its "
+"cache. An example <path>/etc/resolv.conf</path> is shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):559
+msgid "/etc/resolv.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):559
+#, no-wrap
+msgid ""
+"\n"
+"nameserver 127.0.0.1\n"
+"nameserver 192.168.0.1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):564
+msgid ""
+"Now that you have setup a rule for your VPN tunnel DNS, you need to start "
+"<c>dnsmasq</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):569
+msgid "Starting up dnsmasq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):569
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/dnsmasq start</i>\n"
+"# <i>rc-update add dnsmasq default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):579
+msgid "Configuring the routing table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):583
+msgid ""
+"The ideal scenario would be if only the traffic destined for VPN tunnel "
+"would travel across the link. At this point, you have a VPN tunnel setup and "
+"all traffic will travel across the tunnel, unless you specify additional "
+"routes. In order to fix this situation you need to know what networks are "
+"available to you on your VPN. The easiest way to find out the needed "
+"information is to ask a network administrator, but sometimes they are "
+"reluctant to answer such questions. If your local network admin won't "
+"provide the needed information, some trial and error experiments will be "
+"required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):594
+msgid ""
+"When the VPN tunnel was started, <c>vpnc</c> set the default route to the "
+"tunnel. So you must set your default route back to normal, so that things "
+"work as expected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):600
+msgid "Resetting your default route"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):600
+#, no-wrap
+msgid ""
+"\n"
+"# <i>route add default gw 192.168.0.1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):604
+msgid ""
+"Earlier, when DNS services were being configured for your VPN, you specified "
+"a DNS server to handle your example.org domain. You need to add a route for "
+"the 192.168.125.0 subnet so that DNS queries will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):610
+msgid "Adding a route for dns"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):610
+#, no-wrap
+msgid ""
+"\n"
+"# <i>route add -net 192.168.125.0 netmask 255.255.255.0 dev tun0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):614
+msgid ""
+"At this point, you should add any additional routes for known networks (such "
+"as for the subnet 192.168.160.0, which includes the IP address received by "
+"the TUN/TAP virtual device). If your friendly network administrator gave you "
+"the required info, great. Otherwise, you might need to ping hosts you will "
+"be connecting to frequently, to give yourself an idea about what your "
+"routing table should look like."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):623
+msgid ""
+"Due to your setup, when using VPN network services by name, you must specify "
+"the fully qualified domain name, for instance: webserver1.example.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):628
+msgid "Ping example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):628
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ping intranet1.example.org</i>\n"
+"PING intranet1.example.org (172.25.230.29) 56(84) bytes of data.\n"
+"\n"
+"\n"
+"--- intranet1.example.org ping statistics ---\n"
+"18 packets transmitted, 0 received, 100% packet loss, time 16997ms\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):637
+msgid ""
+"As you can see from the above example, the ping probes to <c>intranet1."
+"example.org</c> were unsuccessful. So we need to add a route for that subnet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):643
+msgid "another route command example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):643
+#, no-wrap
+msgid ""
+"\n"
+"# <i>route add -net 172.25.230.0 netmask 255.255.255.0 dev tun0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):647
+msgid ""
+"A few ping and route commands later, you should be well on your way to a "
+"well working routing table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):657
+msgid "Manage the connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):659
+msgid "Calling vpnc when needed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):662
+msgid ""
+"Next is an example script to manage the VPN connection. You could execute it "
+"(as root) from an xterm to start a connection to your VPN. Then all you have "
+"to do is press return to disconnect the VPN. Obviously you will need to "
+"modify this for your setup, remembering to add all the additional routes "
+"that you may need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):670
+msgid "Example session management script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):670
+#, no-wrap
+msgid ""
+"\n"
+"#!/bin/bash\n"
+"\n"
+"source /sbin/functions.sh\n"
+"\n"
+"ebegin \"Connecting to the VPN\"\n"
+"vpnc\n"
+"eend\n"
+"\n"
+"ebegin \"Modifying the routing table\"\n"
+"route add default gw 192.168.0.1\n"
+"route add -net 172.25.230.0 netmask 255.255.255.0 dev tun0\n"
+"route add -net 192.168.160.0 netmask 255.255.255.0 dev tun0\n"
+"route add -net 192.168.125.0 netmask 255.255.255.0 dev tun0\n"
+"eend\n"
+"\n"
+"einfo \"Press any key to disconnect ...\"\n"
+"\n"
+"read $disconnect\n"
+"\n"
+"ebegin \"Disconnecting from the VPN\"\n"
+"vpnc-disconnect\n"
+"eend\n"
+"ebegin \"Reconfiguring the default routing table\"\n"
+"route add default gw 192.168.0.1\n"
+"eend\n"
+"\n"
+"einfo \"VPN should now be disconnected\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):703
+msgid "Start vpnc on boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):706
+msgid ""
+"Version 0.4.0-r1 of vpnc contains an init script (<path>/etc/init.d/vpnc</"
+"path>) which can handle multiple configurations. The default script looks "
+"for <path>/etc/vpnc/vpnc.conf</path>, but as many configurations as can be "
+"imagined are possible. Before and after shutdown and start-up custom-made "
+"scripts can be executed that are connected by their name to the "
+"corresponding init script (since version 0.5.1-r1). Their names end in "
+"<path>-preup.sh</path>, <path>-postup.sh</path>, <path>-predown.sh</path> "
+"and <path>-postdown.sh</path>, stored in the <path>/etc/init.d/scripts.d/</"
+"path> directory. The general naming scheme is sketched in the following "
+"table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(th):720
+msgid "init script name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(th):721
+msgid "needed configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(th):722
+msgid "preup script name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):725
+msgid "/etc/init.d/vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):726
+msgid "/etc/vpnc/vpnc.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):727
+msgid "/etc/vpnc/scripts.d/vpnc-preup.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):730
+msgid "/etc/init.d/vpnc.work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):731
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):840
+msgid "/etc/vpnc/work.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):732
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):823
+msgid "/etc/vpnc/scripts.d/work-preup.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):736
+msgid ""
+"Add vpnc to default runlevel with the following commands (in this case for "
+"the standard configuration). Don't forget to add the tun module (if you have "
+"built it that way) to the kernels autoload mechanism at startup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):742
+msgid "Adding vpnc to startup scripts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):742
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add vpnc default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):746
+msgid ""
+"If you don't want to save your password in the configuration file, you can "
+"tell the init script to show all output and prompts on standard output by "
+"editing <path>/etc/conf.d/vpnc</path>. Set the variable <c>VPNCOUTPUT</c> to "
+"yes or no, where its default is to not display screen output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):753
+msgid ""
+"The init scripts don't handle DNS separation, but you can use the custom "
+"scripts to achieve that. See <uri link=\"#tipsscript\">Tips and Tricks</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):763
+msgid "Tips and Tricks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):765
+msgid "Graphical remote access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):768
+msgid ""
+"If you are looking for a Linux application that supports RDP (Remote Desktop "
+"Protocol) then give <c>grdesktop</c> a try. It's a GUI app written in GTK+ "
+"that fits in well with a Gnome desktop, but doesn't require it. If you don't "
+"want the GUI configuration dialogs that grdesktop provides, then just "
+"install <c>rdesktop</c>. Ultimately, grdesktop is just a frontend for "
+"rdesktop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):776
+msgid ""
+"If you are a KDE user, you might want to try <c>kvpnc</c>. It a appears to "
+"be a very mature VPN management GUI."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):781
+msgid ""
+"If you need to connect to a Windows machine which doesn't have a DNS entry, "
+"and you know the address of an available WINS server, you can use a tool "
+"called <c>nmblookup</c> to query the WINS server for the host name of the "
+"machine you want to connect to. Unfortunately, you have to install <c>samba</"
+"c> to get it, but if you are going to be working with boxes running Windows "
+"you might as well want to install samba, because it includes several other "
+"useful tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):790
+msgid "Installing samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):790
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av samba</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):794
+msgid ""
+"When you have samba and its tools installed, test <c>nmblookup</c> by asking "
+"the WINS server at IP address 192.168.125.11 about a host named wintelbox1."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):799
+msgid "nmblookup example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):799
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nmblookup -U 192.168.125.11 -R 'wintelbox1'</i>\n"
+"querying wintelbox1 on 192.168.125.11\n"
+"172.25.230.76 wintelbox1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):808
+msgid "Custom scripts on boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):811
+msgid ""
+"The custom-made scripts for the <path>init.d</path> file can be used to "
+"setup a user-defined routing for the vpnc connection. The examples below "
+"show how to setup the routing table so that only connections to 123.234.x.x "
+"are routed over the VPN and all other connections use the default gateway. "
+"The example uses work-preup.sh to save the current default gateway before "
+"starting vpnc (which resets the default gateway using the VPN connection). "
+"Once vpnc has been started, <path>work-postup.sh</path> deletes this new "
+"default gateway, restores the old default gateway and sets the route for all "
+"connections to 123.234.x.x to use the vpnc connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):823
+#, no-wrap
+msgid ""
+"\n"
+"#!/bin/sh\n"
+"route -n | grep -E '^0.0.0.0 ' | cut -c 17-32 &gt;/var/tmp/defaultgw\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):828
+msgid "/etc/vpnc/scripts.d/work-postup.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):828
+#, no-wrap
+msgid ""
+"\n"
+"#!/bin/sh\n"
+"route del -net 0.0.0.0 netmask 0.0.0.0 dev tun1\n"
+"route add default gw $(cat /var/tmp/defaultgw)\n"
+"route add -net 123.234.0.0 netmask 255.255.0.0 dev tun1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):835
+msgid ""
+"The example scripts assume that the vpnc connection uses tun1 as tun device. "
+"You can set the device name in the connection's configuration file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):840
+#, no-wrap
+msgid ""
+"\n"
+"Interface name tun1\n"
+"IPSec gateway vpn.mywork.com\n"
+"Pidfile /var/run/vpnc.work.pid\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):851
+msgid "Useful Links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri:link):857
+msgid "http://www.unix-ag.uni-kl.de/~massar/vpnc/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri):857
+msgid "vpnc homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri:link):860
+msgid "http://home.gna.org/kvpnc/en/index.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri):860
+msgid "kvpnc homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri:link):863
+msgid "http://www.nongnu.org/grdesktop/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri):863
+msgid "grdesktop homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):872
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):876
+msgid ""
+"Hopefully by now you have been able to connect to your VPN of choice and are "
+"well on your way to remote office work. Feel free to file a bug at <uri link="
+"\"http://bugs.gentoo.org\">bugs.gentoo.org</uri> should you find a mistake "
+"or wish to make an addition or recommendation regarding this document."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/vserver-howto.xml.po b/doc/gettext/ru/vserver-howto.xml.po
new file mode 100644
index 0000000..937427a
--- /dev/null
+++ b/doc/gettext/ru/vserver-howto.xml.po
@@ -0,0 +1,78 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(guide:link):5
+msgid "/doc/en/vserver-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(guide:redirect):5
+msgid "/proj/en/vps/vserver-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(title):6
+msgid "Gentoo Linux-VServer Howto"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(mail:link):9
+msgid "hollow@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(mail):9
+msgid "Benedikt Boehm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(mail:link):12
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(mail):12
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(abstract):15
+msgid ""
+"In this Howto you will learn to setup a basic virtual server using the Linux-"
+"VServer Technology"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(version):24
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(date):25
+msgid "2006-10-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(title):28
+msgid "Moved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(p):32
+msgid ""
+"This document has been moved to a <uri link=\"/proj/en/vps/vserver-howto.xml"
+"\">new location</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/xen-guide.xml.po b/doc/gettext/ru/xen-guide.xml.po
new file mode 100644
index 0000000..26de987
--- /dev/null
+++ b/doc/gettext/ru/xen-guide.xml.po
@@ -0,0 +1,733 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):7
+msgid "Configuring Gentoo with Xen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(mail:link):10
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(mail):10
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(abstract):13
+msgid "This guide describes how to start using Xen on your Gentoo system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(version):21
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(date):22
+msgid "2010-05-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):25
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):56
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):391
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):29
+msgid ""
+"The <uri link=\"http://www.xensource.com/\">Xen</uri> technology allows you "
+"to run multiple operating systems on a single physical system, govern "
+"resource consumption and even migrate domains (which are the virtual "
+"environments in which a guest operating system runs) from one Xen-powered "
+"system to another. Xen requires the host operating system to support Xen "
+"(which, in this case, will be a Linux kernel) but guest operating systems "
+"can run unmodified <e>if</e> your hardware supports Intel Virtualization "
+"Technology (VT-x) or AMD Virtualization Technology (SVM). Otherwise your "
+"guest operating systems must also support Xen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):40
+msgid ""
+"This guide will talk you through the configuration steps necessary to get "
+"Xen up and running on Gentoo Linux. We will not discuss Xen itself (the Xen "
+"project has <uri link=\"http://www.cl.cam.ac.uk/research/srg/netos/xen/"
+"readmes/user\">decent documentation</uri> available) nor will we talk about "
+"specialized setups that might be very interesting for Xen setups but are not "
+"Xen-related (like exporting Portage through NFS, booting Linux using PXE, "
+"etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):54
+msgid "Preparing Domain0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):59
+msgid ""
+"<e>Domain0</e> is the primary domain under Xen, hosting the host operating "
+"system which governs all other domains. In this chapter we will prepare an "
+"existing Gentoo installation to become the host operating system in this "
+"domain and build the Xen-powered kernel so that Gentoo is ready to host "
+"other Xen domains."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):70
+msgid "Rebuilding the Gentoo Installation ?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):73
+msgid ""
+"A dramatic change that might be necessary is to rebuild the entire Gentoo "
+"installation with a different <c>CFLAGS</c> setting. Guest operating systems "
+"running under Xen might otherwise see major performance degradation. If you, "
+"however, are planning on checking out Xen rather than installing it for "
+"production use and are not terribly fond of rebuilding all programs, you can "
+"skip this step. In this case you will notice performance degradation but you "
+"will still be able to use Xen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(impo):83
+msgid ""
+"It is advised that, if you change your <c>CFLAGS</c> and build your system "
+"with a gcc lower than version 4, you do not have <c>-Os</c> set as it has "
+"been reported to produce broken code."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):89
+msgid "Editing the CFLAGS and rebuild the Gentoo installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):89
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>nano -w /etc/make.conf</i>\n"
+"<comment>(Add -mno-tls-direct-seg-refs)</comment>\n"
+"CFLAGS=\"-O2 -march=pentium4 -pipe <i>-mno-tls-direct-seg-refs</i>\"\n"
+"\n"
+"~# <i>emerge -e world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):97
+msgid ""
+"If you boot your system using an initial ramdisk (initrd) you need to "
+"rebuild the initrd as well (which is best done by running all steps you "
+"would do when you rebuild your kernel)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):106
+msgid "Installing Xen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):109
+msgid ""
+"Xen actually contains many components, so you'll need to install a couple of "
+"packages. Because it is still <uri link=\"/doc/en/handbook/handbook-x86.xml?"
+"part=3&amp;chap=3#doc_chap2\">~arch masked</uri> you first need to unmask it "
+"by adding the necessary lines to <path>/etc/portage/package.keywords</path> "
+"and then install them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):117
+msgid "Unmasking and Installing Xen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):117
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>nano -w /etc/portage/package.keywords</i>\n"
+"app-emulation/xen\n"
+"app-emulation/xen-tools\n"
+"sys-kernel/xen-sources\n"
+"\n"
+"~# <i>emerge xen xen-tools xen-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):131
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):213
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):266
+msgid "Building the Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):134
+msgid ""
+"Next we'll build the Linux kernel with Xen support. This kernel, whose "
+"sources are available at <path>/usr/src/linux-2.6.x.z-xen</path>, will be "
+"our main running kernel (i.e. the one running domain 0). In the <c>XEN</c> "
+"section you'll find drivers for all kinds of input/output, each driver "
+"having a <e>backend</e> and <e>frontend</e> implementation available. For "
+"the domain 0 kernel you need to select the <e>backend</e> implementation: "
+"these are used by the other domains (who use the <e>frontend</e> drivers) to "
+"communicate directly with the hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):145
+msgid ""
+"Of course, don't forget to select <c>Xen-compatible</c> at <c>Processor type "
+"and features</c>. If you're wondering about networking: each interface in a "
+"domain has a point-to-point link to an interface on domain 0 (called "
+"<path>vifX.Y</path> where X is the domain number and Y the Yth interface of "
+"that domain), so you can configure your network the way you want (bridging, "
+"NAT, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):154
+msgid "Enabling Xen Support for i386 Kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):154
+#, no-wrap
+msgid ""
+"\n"
+"Processor type and features  ---&gt;\n"
+"      Subarchitecture Type (Xen-compatible)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):159
+msgid "Enabling Xen Support for x86_64 Kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):159
+#, no-wrap
+msgid ""
+"\n"
+"Processor type and features  ---&gt;\n"
+"      Subarchitecture Type (PC-compatible)\n"
+"  [*] Enable Xen compatible kernel\n"
+"  [*] Support for hot-pluggable CPUs\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):166
+msgid "Domain-0 Kernel Config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):166
+#, no-wrap
+msgid ""
+"\n"
+"Bus options (PCI etc.)  ---&gt;\n"
+"  [*] PCI support\n"
+"  [ ]   Xen PCI Frontend Debugging\n"
+"\n"
+"Networking  ---&gt;\n"
+"  Networking options  ---&gt;\n"
+"    &lt;*&gt; 802.1d Ethernet Bridging\n"
+"    <comment>Only required by bridged networking.</comment>\n"
+"\n"
+"XEN  ---&gt;\n"
+"  [*] Privileged Guest (domain 0)\n"
+"  &lt;*&gt; Backend driver support\n"
+"  &lt;*&gt;   Block-device backend driver\n"
+"  &lt;*&gt;   Network-device backend driver\n"
+"  &lt;*&gt;   PCI-device backend driver\n"
+"           PCI Backend Mode (Virtual PCI) ---&gt;\n"
+"  [*] Scrub memory before freeing it to Xen\n"
+"  [*] Disable serial port drivers\n"
+"      Xen version compatibility (3.0.4 and later)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):188
+msgid "Domain-U Kernel Config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):188
+#, no-wrap
+msgid ""
+"\n"
+"Bus options (PCI etc.)  ---&gt;\n"
+"  [ ] PCI support\n"
+"\n"
+"Device Drivers  ---&gt;\n"
+"  SCSI device support  ---&gt;\n"
+"    &lt; &gt; SCSI device support\n"
+"    <comment>Disabling SCSI support frees up the /dev/sd* device names\n"
+"    for use as Xen virtual block devices.</comment>\n"
+"\n"
+"XEN  ---&gt;\n"
+"  [ ] Privileged Guest (domain 0)\n"
+"  &lt;*&gt; Block-device frontend driver\n"
+"  &lt;*&gt; Network-device frontend driver\n"
+"  [*] Scrub memory before freeing it to Xen\n"
+"  [*] Disable serial port drivers\n"
+"      Xen version compatibility (3.0.4 and later)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):207
+msgid ""
+"A nice hint is to have the kernel make process store its intermediate object "
+"files elsewhere so that you can reuse the same kernel tree to build "
+"different configurations:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):213
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>mkdir -p ~/build/dom0 ~/build/domU</i>\n"
+"~# <i>make O=~/build/dom0 menuconfig</i>\n"
+"<comment>(Configure the kernel)</comment>\n"
+"~# <i>make O=~/build/dom0 &amp;&amp; make O=~/build/dom0 modules_install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):220
+msgid ""
+"Once the kernel is built you'll find the kernel image immediately in the "
+"build directory (not inside <path>arch/</path> or any other directory) "
+"called <path>vmlinuz</path>. Copy it to <path>/boot</path> and then "
+"configure your bootloader to use the Xen hypervisor (one of the components "
+"installed previously) which is stored as <path>/boot/xen.gz</path>. In the "
+"bootloader configuration, add your newly built kernel as the kernel that Xen "
+"should boot. For instance, for GRUB:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):230
+msgid "GRUB Configuration for Xen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):230
+#, no-wrap
+msgid ""
+"\n"
+"title Xen 3.0 / Gentoo Linux 2.6.x.y\n"
+"root (hd0,0)\n"
+"kernel /boot/xen.gz\n"
+"module /boot/kernel-2.6.x.y-xen0 root=/dev/hda3\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):237
+msgid ""
+"Now reboot your system into Xen. Once you are booted, you need to load the "
+"Xen daemon:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):242
+msgid "Loading the Xen daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):242
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>/etc/init.d/xend start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):246
+msgid ""
+"Now check if you can do whatever you normally do on your system. If this is "
+"the case, you can edit your bootloader configuration to always boot into Xen "
+"and add the Xen deamon to the default runlevel so that it is started "
+"automatically next time you boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(note):253
+msgid ""
+"If you wish to start guest domains automatically on boot add <c>xendomains</"
+"c> to the default runlevel as well and create a symlink in <path>/etc/xen/"
+"auto/</path> to the Xen configuration files for the domains you wish to "
+"start."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):264
+msgid "Creating an Unpriviledged Domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):269
+msgid ""
+"Go to the Xen-powered Linux kernel source and update the configuration. It "
+"is wise to keep as many topics as possible similar to the main kernel except "
+"the <c>XEN</c> settings where drivers should now have their <e>frontend</e> "
+"implementation selected instead of the <e>backend</e>. Then build the kernel "
+"and place the resulting <path>vmlinuz</path> file where you want (we assume "
+"this is <path>/mnt/data/xen/kernel</path>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):278
+msgid "Building the guest kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):278
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>make O=~/build/domU</i>\n"
+"~# <i>cp ~/build/domU/vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):283
+msgid ""
+"It is also possible to create a single kernel image for both the "
+"administrative domain and the unpriviledged domain. More information about "
+"this can be found in the Xen user manual."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):292
+msgid "Creating the Domain Disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):295
+msgid ""
+"For best performance, it is best to dedicate a partition (or logical volume) "
+"to a domain rather than a file based filesystem. However, if you are going "
+"to use Xen primarily for tests using a file based filesystem does have its "
+"advantages (especially regarding maintenance)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):302
+msgid ""
+"You can create a file based filesystem using <c>dd</c> and <c>mke2fs</c> (or "
+"any other file system creation tool). For instance, to create a 2Gbyte ext3 "
+"filesystem:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):308
+msgid "Creating a file based filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):308
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>dd if=/dev/zero of=/mnt/data/xen/disks/ext3root.img bs=1M count=2048</i>\n"
+"~# <i>mke2fs -j /mnt/data/xen/disks/ext3root.img</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):316
+msgid "Configuring a Domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):319
+msgid ""
+"Next we create a Xen configuration file for a domain. You can store these "
+"configuration files where you want, for instance at <path>/mnt/data/xen/"
+"configs</path>. As an example, we create a configuration file for a small "
+"Gentoo environment which uses the disk image we created previously:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):327
+msgid "Creating a domain configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):327
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n"
+"\n"
+"kernel = \"/mnt/data/xen/kernel/kernel-2.6.x.y-xen\"\n"
+"memory = 512\n"
+"name   = \"gentoo\"\n"
+"<comment>(Map the disk image to the virtual /dev/sda1)</comment>\n"
+"disk   = ['file:/mnt/data/xen/disks/ext3root.img,sda1,w']\n"
+"root   = \"/dev/sda1 ro\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):338
+msgid ""
+"If you are using a block device (such as an lvm volume or partition) for the "
+"disk use 'phy:' instead of 'file:' and leave off /dev. For example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):343
+msgid "Using a block device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):343
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(LVM Volume)</comment>\n"
+"disk = [ 'phy:lvm/xen-guest-root,sda1,w' ]\n"
+"\n"
+"<comment>(Physical Partition)</comment>\n"
+"disk = [ 'phy:sdb6,sda1,w' ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):351
+msgid "You can find example configuration files in <path>/etc/xen</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):358
+msgid "Launching the New Domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):361
+msgid ""
+"Now we're all set and we can launch the new domain. If the disk image "
+"contained an operating system, we could just create and attach the domain "
+"using the <c>xm</c> command (Xen manager):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):367
+msgid "Creating and starting a new domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):367
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>xm create /mnt/data/xen/configs/gentoo -c</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):371
+msgid ""
+"The domain would be booted inside the terminal in which you executed the "
+"command. However, in our case, the disk image is empty so the domain won't "
+"boot up in anything useful. To fix this, you can loop-mount the image and "
+"install Gentoo as you're used to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):378
+msgid ""
+"If you want to disconnect from the domain, press <path>Ctrl+]</path>. You "
+"can always reconnect to the domains' console using <c>xm console gentoo</c>. "
+"However, there is only one console per domain, so only use it when you can't "
+"access the domain otherwise (for instance, through SSH)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):389
+msgid "Networking on Unpriviledged Domains"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):394
+msgid ""
+"Xen supports at least two ways of configuring your (virtual) network: "
+"<e>routed</e> and <e>bridged</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):399
+msgid ""
+"When selecting the <e>routed</e> approach, the interface inside your "
+"unpriviledged domain is connected to the virtual interface on your "
+"administrative domain. On your administrative domain (domain 0), the virtual "
+"interface is linked together with <path>eth0</path>. The interface inside "
+"your unpriviledged domain should have an IP address on the same network as "
+"the interface on the administrative domain. Any communication to that IP "
+"address can only occur from the administrative domain, unless you set up "
+"specific routing rules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):410
+msgid ""
+"When selecting the <e>bridged</e> approach, your default network interface "
+"on the administrative domain becomes a bridge which accepts connections to "
+"the virtual domains as well as to the IP address your administrative domain "
+"has."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):419
+msgid "Regular Routed Interfaces"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):422
+msgid ""
+"Before you set up the interface on your unpriviledged domain, make sure that "
+"Xen's <path>netloop</path> and <path>netbk</path> drivers are loaded. A "
+"quick hint: if you have <path>netloop</path> as a module, load it with "
+"<c>nloopbacks=0</c> so that it doesn't create pointless interfaces to the "
+"loopback device. Then, edit your domain configuration file and add a <c>vif</"
+"c> instruction to it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):431
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):487
+msgid "Configuring a virtual interface"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):431
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n"
+"\n"
+"<comment>(Add the vif instruction)</comment>\n"
+"vif    = [ 'ip=192.168.1.101, vifname=veth1' ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):438
+msgid ""
+"In the above example, the interface will be created for the unpriviledged "
+"domain (in which it will be called <path>eth0</path>) and Xen will ensure "
+"that address 192.168.1.101 will be reachable from the administrative domain "
+"through interface <path>veth1</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):445
+msgid ""
+"This doesn't mean that the virtual <path>eth0</path> interface will "
+"automatically have IP 192.168.1.101 assigned to it, but rather that, if you "
+"don't give it that IP, it will not be connected with the administrative "
+"domain and thus cannot be reached."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):452
+msgid ""
+"Now edit <path>/etc/xen/xend-config.sxp</path> as follows to select routed "
+"network configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):457
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):499
+msgid "Editing xend-config.sxp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):457
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>nano -w /etc/xen/xend-config.sxp</i>\n"
+"\n"
+"<comment>(Comment out the following lines)</comment>\n"
+"<i>#</i>(network-script network-bridge)\n"
+"<i>#</i>(vif-script vif-bridge)\n"
+"\n"
+"<comment>(Enable the following lines)</comment>\n"
+"(network-script network-route)\n"
+"(vif-script vif-route)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):472
+msgid "Bridged Interfaces"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):475
+msgid ""
+"Unlike the routed interfaces you now need to load the <path>netloop</path> "
+"driver with <c>nloopbacks=1</c> (or higher) as the additional loopback "
+"devices are used to create the bridge. For the other modules you still need "
+"the <path>netbk</path> module as well as briding functionality "
+"(<path>bridge</path> module if build as such)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):483
+msgid "Now edit your virtual domain and add the <c>vif</c> construct:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):487
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n"
+"\n"
+"<comment>(Add the vif instruction)</comment>\n"
+"vif    = [ 'ip=192.168.1.101, vifname=veth0' ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):494
+msgid ""
+"Next edit <path>/etc/xen/xend-config.sxp</path> as follows to select bridged "
+"network configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):499
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>nano -w /etc/xen/xend-config.sxp</i>\n"
+"\n"
+"<comment>(Enable the following lines)</comment>\n"
+"(network-script network-bridge)\n"
+"(vif-script vif-bridge)\n"
+"\n"
+"<comment>(Comment out the following lines if not done already)</comment>\n"
+"<i>#</i> (network-script network-route)\n"
+"<i>#</i> (vif-script vif-route)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):511
+msgid ""
+"By default, the bridge will contain whatever interface is configured to be "
+"the default interface (the device that is listed under the default route "
+"through <c>ip route list</c>). If you want to alter this behavior, edit the "
+"<path>xend-config.sxp</path> as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):518
+msgid "Editing xend-config.sxp to change bridge configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):518
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>nano -w /etc/xen/xend-config.sxp</i>\n"
+"\n"
+"<comment>(Edit the network-script line)</comment>\n"
+"(network-script <i>'</i>network-bridge <i>netdev=eth0 bridge=xenbr0 vifnum=0'</i>)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):525
+msgid ""
+"Once the configuration is done, restart the <c>xend</c> init script to have "
+"Xen build the bridge:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):530
+msgid "Restarting the xend daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):530
+#, no-wrap
+msgid ""
+"\n"
+"~# <i>/etc/init.d/xend restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):538
+msgid "Further Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):540
+msgid "Xen Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):545
+msgid "http://tx.downloads.xensource.com/downloads/docs/user/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):545
+msgid "Xen Users' Manual"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):549
+msgid "http://xen.xensource.com/documentation.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):549
+msgid "Xen Community Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):553
+msgid "http://wiki.xensource.com/xenwiki/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):553
+msgid "Xen Wiki"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):560
+msgid "Xen Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(li):564
+msgid ""
+"<uri link=\"http://virt-manager.et.redhat.com/\">app-emulation/virt-manager</"
+"uri> is a graphical tool for administering virtual machines"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/xfce-config.xml.po b/doc/gettext/ru/xfce-config.xml.po
new file mode 100644
index 0000000..b33dbb7
--- /dev/null
+++ b/doc/gettext/ru/xfce-config.xml.po
@@ -0,0 +1,768 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):6
+msgid "The Xfce Configuration Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(mail:link):9
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(abstract):12
+msgid ""
+"This guide provides an extensive introduction to Xfce, a fast, lightweight, "
+"full-featured desktop environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(version):21
+msgid "1.28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(date):22
+msgid "2010-08-31"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):25
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):27
+msgid "The Xfce desktop environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):30
+msgid ""
+"<uri link=\"http://www.xfce.org\">Xfce</uri> is a fast, lightweight desktop "
+"environment for Unix-like operating systems. It is designed for "
+"productivity, and is quite configurable while still adhering to the <uri "
+"link=\"http://www.freedesktop.org\">Freedesktop</uri> specifications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):37
+msgid ""
+"Unlike heavier desktop environments, such as <uri link=\"http://www.gnome.org"
+"\">Gnome</uri> and <uri link=\"http://www.kde.org\">KDE</uri>, Xfce uses far "
+"fewer system resources. Additionally, it offers greater modularity and fewer "
+"dependencies; it takes up less space on your hard disk and takes less time "
+"to install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):45
+msgid ""
+"This guide will not only show you how to install and configure a minimal "
+"Xfce environment, but will also explore options to create a full-featured "
+"desktop in keeping with the Xfce philosophy: light, fast, and modular."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):56
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):100
+msgid "Installing Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):58
+msgid "The basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):61
+msgid ""
+"First, make sure you've configured Xorg as shown in the <uri link=\"/doc/en/"
+"xorg-config.xml\">X Server Configuration Howto</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):66
+msgid ""
+"Next, double-check your USE flags in <path>/etc/make.conf</path>; you'll "
+"probably at least want <c>USE=\"-gnome -kde -minimal -qt4 branding dbus hal "
+"jpeg lock session startup-notification thunar X\"</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):72
+msgid ""
+"There's also another variable you can set in <path>/etc/make.conf</path> "
+"called XFCE_PLUGINS. This variable controls additional Xfce plugins for the "
+"panel. You can enable all of the plugins by adding <c>XFCE_PLUGINS="
+"\"brightness menu trash</c> to <path>/etc/make.conf</path>. Here's a brief "
+"summary of the plugins:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dt):81
+msgid "brightness"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dd):82
+msgid ""
+"Lets you add a screen brightness applet to your panel, once you have "
+"installed <c>xfce4-power-manager</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dt):86
+msgid "menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dd):87
+msgid "Lets you add a program menu to your panel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dt):88
+msgid "trash"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dd):89
+msgid ""
+"Lets you add a Trash can to the panel. The Trash allows you to quickly "
+"delete files or recover them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):95
+msgid ""
+"Now that you've set your <c>USE</c> and <c>XFCE_PLUGINS</c> variables in "
+"<path>/etc/make.conf</path>, it's time to install Xfce."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):100
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -avt xfce4-meta</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):104
+msgid ""
+"Next, add your regular user(s) to the <c>plugdev</c>, <c>cdrom</c>, <c>cdrw</"
+"c>, and <c>usb</c> groups, so that they can take full advantage of <c>hal</"
+"c> and be able to mount and use devices such as cameras, optical drives, and "
+"USB sticks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):110
+msgid "Adding users to the hardware groups"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):110
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace username with your actual user)</comment>\n"
+"# <i>for x in plugdev cdrom cdrw usb ; do gpasswd -a username $x ; done</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):115
+msgid "Next, update your environment variables:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):119
+msgid "Updating environment variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):119
+#, no-wrap
+msgid ""
+"\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):123
+msgid "Now start up <c>hald</c> and add it to the default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):127
+msgid "Starting hald"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):127
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/hald start</i>\n"
+"# <i>rc-update add hald default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):132
+msgid ""
+"You'll also need a graphical terminal so that you can continue working with "
+"your new desktop environment. <c>x11-terms/terminal</c> is a good choice, as "
+"it's made specifically for Xfce. Install Terminal as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):138
+msgid "Installing Terminal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):138
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge x11-terms/terminal</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):147
+msgid "Configuring Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):149
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):174
+msgid "Starting Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):152
+msgid ""
+"Now that Xfce is now installed, we'll configure it to be the default desktop "
+"environment when we issue the <c>startx</c> command. Exit your root shell "
+"and log on as a regular user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):158
+msgid "Setting Xfce as the default desktop environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):158
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>echo \"exec startxfce4\" &gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(note):162
+msgid ""
+"If you have ConsoleKit installed, your <path>~/.xinitrc</path> should "
+"instead contain <c>exec ck-launch-session startxfce4</c>. Otherwise, some of "
+"your applications may stop working. You'll also need to add consolekit to "
+"the default runlevel by running the following command as root: <c>rc-update "
+"add consolekit default</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):170
+msgid "Now start your graphical environment by typing <c>startx</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):174
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>startx</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):178
+msgid ""
+"Congratulations, and welcome to your new Xfce desktop environment. Go ahead, "
+"explore it a bit. Then continue reading to learn how you can configure Xfce "
+"to suit your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):187
+msgid "Program access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):190
+msgid ""
+"You might notice right-clicking on the desktop shows you the menu of all "
+"your applications. It's useful, but your desktop can easily be completely "
+"obscured by open windows, making it hard to to launch a new program. So, one "
+"of the first things you may wish to do is give yourself a handy application "
+"menu on your panel. Right click on this panel, and choose \"Add New Item\". "
+"Scroll through the list of choices and select \"Xfce Menu\". You can choose "
+"where you want it to be displayed on your panel. When clicked, it displays "
+"the application/preferences menu, providing a nicely categorized list of "
+"your installed programs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):204
+msgid "Sessions &amp; startup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):207
+msgid ""
+"If you've installed (or plan to install) popular Gnome or KDE applications "
+"such as <c>k3b</c>, <c>nautilus</c>, <c>kmail</c>, <c>evolution</c>, etc. "
+"then you should make sure that Xfce launches the appropriate services for "
+"these at startup. Navigate to Menu --&gt; Settings --&gt; Sessions &amp; "
+"Startup. On the \"Advanced\" tab, select the appropriate checkbox. This "
+"might slightly increase Xfce startup times, but it decreases load times for "
+"KDE and Gnome applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):216
+msgid ""
+"Xfce has the ability to save your session settings and running programs from "
+"the \"General\" tab in the Sessions &amp; Startup menu. They can be "
+"automatically saved when you logout, or Xfce can ask you each time. This "
+"feature is particularly useful for undoing configuration mistakes. "
+"Accidentally killed a panel? Just select \"No\" when prompted to save your "
+"current session, and the next time you start Xfce, your old desktop is "
+"restored. Want to automatically launch your open webbrowser, terminal, and "
+"email client the next time you login? Just save your session before logging "
+"out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):227
+msgid ""
+"You've now got a basic working environment installed and configured. But if "
+"you're interested in doing more, then continue reading!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):237
+msgid "Additional Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):239
+msgid "Panel plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):242
+msgid ""
+"In this chapter, we'll discuss some useful plugins and applications for "
+"everyday use within Xfce."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):247
+msgid ""
+"There are many plugins for the panel available in Portage; see for yourself "
+"with <c>emerge --search xfce</c>. Though for the most part their names are "
+"self-explanatory, a few deserve extra attention, as they are quite helpful. "
+"To use them, simply <c>emerge</c> them. They'll be added to the list of "
+"available items in the \"Add New Items\" menu shown when you right-click on "
+"the panel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):256
+msgid ""
+"<c>xfce4-battery-plugin</c> is perfect for laptop users. It displays battery "
+"percentage, time remaining, power source (AC or battery), fan status, "
+"warnings, and can even be configured to execute commands at certain power "
+"levels. This feature can be used to put the laptop into hibernate mode when "
+"the battery is almost exhausted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):263
+msgid ""
+"<c>xfce4-verve-plugin</c> is a small command line embedded into the panel. "
+"It's quicker than opening up another terminal when you want to run a command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):268
+msgid ""
+"<c>xfce4-mount-plugin</c> gives you a handy method of mounting devices "
+"listed in <path>/etc/fstab</path> just by clicking your mouse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):272
+msgid ""
+"<c>xfce4-sensors-plugin</c> lets you monitor your hardware sensors, such as "
+"CPU temperature, fan RPM, hard drive temp, motherboard voltage, and more"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):278
+msgid ""
+"If you can't find what you're looking for in the plugins specifically made "
+"for Xfce, try searching through the list of Gnome panel applets! That's "
+"right, by first emerging <c>xfce4-xfapplet-plugin</c>, you can install and "
+"run any applet made for Gnome."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):288
+msgid "Useful programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):291
+msgid ""
+"We should now <c>emerge</c> some useful applications and utilities: <c>xfce4-"
+"mixer</c>, <c>xfprint</c>, <c>xfce4-taskmanager</c>, <c>xfwm4-themes</c>, "
+"<c>orage</c>, <c>mousepad</c>, <c>xfce4-power-manager</c>, <c>x11-terms/"
+"terminal</c>, and <c>thunar</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):298
+msgid ""
+"<c>xfce4-mixer</c> is a volume control for your sound card. It can also be "
+"run as a panel applet, giving you fast access to playback volume. "
+"<c>xfprint</c> provides easy printer management and job control; it's a must "
+"if you intend to do any printing from your desktop. <c>xfce4-taskmanager</c> "
+"displays a list of all running programs, and the CPU and memory consumption "
+"each one takes up. By right-clicking an item, you can kill a misbehaving "
+"application, pause and restart it, or even alter its runtime priority, which "
+"lets you fine-tune how much of a demand it puts on your system's resources."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):309
+msgid ""
+"<c>xfwm4-themes</c> adds several window manager themes. You may want to add "
+"a more full-coverage icon theme such as <c>tango-icon-theme</c> just to "
+"round out your desktop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):315
+msgid ""
+"<c>orage</c> is a simple, handy calendar. <c>mousepad</c> is a barebones "
+"text editor that starts up extremely quickly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):320
+msgid ""
+"<c>xfce4-power-manager</c> is an application to monitor and manage power "
+"usage. This is especially important for laptops! The power manager allows "
+"you to adjust screen brightness, choose maximum performance or battery-"
+"saving modes, and setup hibernate, suspend, and shutdown actions when the "
+"lid is shut or buttons are pressed. You can set <uri link=\"http://goodies."
+"xfce.org/projects/applications/xfce4-power-manager\">xfce4-power-manager</"
+"uri> to warn you when your battery reaches certain levels, or even turn off "
+"your machine. The application comes with a couple of helpful panel plugins "
+"to display battery/charging status, and a brightness control."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):332
+msgid ""
+"<c>x11-terms/terminal</c> is an X11 terminal emulator, far more configurable "
+"and useful than the barebones <c>xterm</c>. <c>terminal</c> supports Unicode "
+"text, color schemes, pseudo-transparency and hardware-accelerated "
+"transparency via Xfce's built-in compositor, all out-of-the-box. Just make "
+"sure that the default action on the terminal launcher of your panel runs "
+"<path>/usr/bin/Terminal</path> instead of <path>xterm</path>. Right-click "
+"the launcher and choose \"Properties\" to change the command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):342
+msgid ""
+"<c>thunar</c> is Xfce's default graphical file manager. It's fast yet quite "
+"powerful, can support several plugins for even more functionality; just "
+"install them with <c>emerge</c>. Let's take a look:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):349
+msgid ""
+"<c>thunar-archive-plugin</c> lets you create and extract archive files using "
+"the right-click menu. It provides a handy <uri link=\"http://www.foo-"
+"projects.org/~benny/projects/thunar-archive-plugin\">front-end</uri> for "
+"graphical archiving applications such as <c>xarchiver</c>, <c>squeeze</c>, "
+"and <c>file-roller</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):356
+msgid ""
+"<c>thunar-media-tags-plugin</c> lets you intelligently rename multiple media "
+"files at once, and lets you <uri link=\"http://thunar.xfce.org/pwiki/"
+"projects/thunar-media-tags-plugin\">edit</uri> their information tags, such "
+"as id3 and ogg tags."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):362
+msgid ""
+"<c>thunar-thumbnailers</c> lets you <uri link=\"http://goodies.xfce.org/"
+"projects/thunar-plugins/thunar-thumbnailers\">preview</uri> certain types of "
+"files from within Thunar, such as images and fonts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):367
+msgid ""
+"<c>thunar-volman</c> automatically <uri link=\"http://foo-projects.org/"
+"~benny/projects/thunar-volman/\">manages</uri> removable media and drives."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):374
+msgid ""
+"Next, let's see about adding some useful but lightweight desktop "
+"applications, in keeping with Xfce's philosophy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):379
+msgid ""
+"Though <c>mousepad</c> is nice enough as a basic text editor, if you need a "
+"full-featured word processor but don't want the bloat of OpenOffice, try "
+"emerging <c>abiword</c>. <uri link=\"http://www.abisource.com\">AbiWord</"
+"uri> is lighter, faster, and is completely interoperable with industry-"
+"standard document types. It can also be further extended with <c>abiword-"
+"plugins</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):387
+msgid ""
+"Need a nice email client/newsreader that isn't as demanding as "
+"<c>thunderbird</c> or <c>evolution</c>? Try emerging <c>claws-mail</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):392
+msgid ""
+"For your internet chat needs, <c>irssi</c> is an excellent, tiny, incredibly "
+"configurable IRC client that runs in your terminal. If you prefer a compact "
+"all-in-one client that handles nearly all chat protocols, you may want to "
+"<c>emerge pidgin</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):399
+msgid ""
+"If you need movie and music players, look no further than <c>mplayer</c> and "
+"<uri link=\"/proj/en/desktop/sound/decibel.xml\">decibel-audio-player</uri>. "
+"They can play most every media format available quite nicely."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):405
+msgid ""
+"Finally, you'll need a webbrowser. Nearly all graphical webbrowsers require "
+"more resources than most of your other desktop applications. Still, "
+"<c>firefox</c> (or <c>firefox-bin</c>) is always a good choice. "
+"Alternatively, you may find <c>opera</c> to be quite fast. However, "
+"<c>opera</c> is not available on as many processor architectures as "
+"<c>firefox</c>, and it has more dependencies unless you override them with a "
+"few USE flags."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):414
+msgid "Adding a webbrowser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):414
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Installing Mozilla Firefox)</comment>\n"
+"# <i>emerge firefox</i>\n"
+"<comment>(Installing Opera)</comment>\n"
+"# <i>echo \"www-client/opera gtk -kde\" &gt;&gt; /etc/portage/package.use</i>\n"
+"# <i>emerge opera</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):422
+msgid ""
+"Now that we've explored some good suggestions for rounding out your desktop "
+"applications, let's see what else we can do to enhance your Xfce experience."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):430
+msgid "Graphical login"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):433
+msgid ""
+"Remember when we added <c>startxfce4</c> to our <path>~/.xinitrc</path>? All "
+"you have to do to get into your desktop is type <c>startx</c> after logging "
+"in. This is fine if you prefer a completely text-based boot and login, but "
+"let's use a display manager that will automatically start Xfce after booting "
+"(so that you can login graphically)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):441
+msgid "First, let's make sure Xfce loads at boot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):445
+msgid "Adding xdm to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):445
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add xdm default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):449
+msgid ""
+"We aren't quite finished yet. We have to pick a display manager and set the "
+"appropriate variable. Though there are a few choices available in Portage, "
+"for this guide, we'll stick with <uri link=\"http://slim.berlios.de\">SLiM</"
+"uri>, the Simple Login Manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):456
+msgid ""
+"<c>slim</c> is speedy and lightweight, with minimal dependencies. Perfect "
+"for Xfce!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):461
+msgid "Installing SLiM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):461
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -avt slim</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(note):465
+msgid ""
+"The <c>branding</c> USE flag will pull in the <c>slim-themes</c> package, "
+"which will give you an assortment of login themes, including a Gentoo Linux "
+"theme."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):470
+msgid "Then edit the DISPLAYMANAGER variable in <path>/etc/conf.d/xdm</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):474
+msgid "Editing /etc/conf.d/xdm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):474
+#, no-wrap
+msgid ""
+"\n"
+"DISPLAYMANAGER=\"slim\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):478
+msgid ""
+"SLiM can automatically start your Xfce session if you add <c>XSESSION="
+"\"Xfce4\"</c> to <path>/etc/env.d/90xsession</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):483
+msgid "Setting XSESSION"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):483
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo XSESSION=\\\"Xfce4\\\" &gt; /etc/env.d/90xsession</i>\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):491
+msgid "Beautifying your desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):494
+msgid ""
+"A little customization of your desktop's appearance can go a long way. Xfce "
+"has all the options you'd expect from a modern desktop environment, font "
+"antialiasing settings, color schemes, dozens of window decorations, themes, "
+"and more. If these aren't enough, it's easy to install third-party themes, "
+"icon sets, mouse cursor themes, and wallpapers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):502
+msgid ""
+"A selection of nice Gentoo wallpapers in a variety of resolutions are hosted "
+"on the <uri link=\"/main/en/graphics.xml\">Gentoo website</uri>. If you're "
+"looking for icon sets and complete Xfce themes, <uri link=\"http://www.xfce-"
+"look.org/\">Xfce-Look</uri> has a huge collection. The important thing to "
+"remember about any third-party eyecandy you download is that it will usually "
+"first need to be unpacked and then installed to the proper directory. Icon "
+"sets go in <path>/usr/share/icons/</path>, and themes go to <path>/usr/share/"
+"themes/</path>; use these directories when you want all users to be able to "
+"access themes and icon sets. Individual users can install themes and icon "
+"sets to <path>~/.themes/</path> and <path>~/.icons/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):515
+msgid ""
+"If you installed SLiM as your display manager, there are lots of themes in "
+"the <c>slim-themes</c> package available in Portage. Also, be sure to check "
+"the SLiM <uri link=\"http://slim.berlios.de/themes01.php\">themes page</uri> "
+"for more themes. Creating your own SLiM theme is fairly easy; just read the "
+"<uri link=\"http://slim.berlios.de/themes_howto.php\">Themes HowTo</uri>. "
+"Gentoo also ships a <c>slim-themes</c> package that you can <c>emerge</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):524
+msgid ""
+"Finally, Xfce has its own built-in compositor to manage window transparency. "
+"This option can be found in Menu --&gt; Settings --&gt; Window Manager. For "
+"best performance, you will need to be running a graphics card with drivers "
+"that support hardware-accelerated rendering. Make sure you emerged <c>xfwm4</"
+"c> with the <c>xcomposite</c> USE flag. Next, you will need to enable "
+"compositing in <path>/etc/X11/xorg.conf</path> by adding the following "
+"section:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):533
+msgid "Enabling composite in xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):533
+#, no-wrap
+msgid ""
+"\n"
+"Section \"Extensions\"\n"
+"    Option  \"Composite\"  \"Enable\"\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):539
+msgid ""
+"This is the bare minimum configuration required for Xfce and Xorg-X11. "
+"However, setting up hardware-accelerated rendering depends on your "
+"individual graphics card, and is beyond the scope of this guide. Please see "
+"the other guides in the <uri link=\"/doc/en/index.xml?catid=desktop"
+"\">Desktop Documentation Resources</uri> list to learn about configuring "
+"hardware-accelerated rendering for your graphics card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):548
+msgid ""
+"Once you've finished setting up a beautiful Xfce desktop, the next thing to "
+"do is take a picture of it to share with other folks! Just install <c>xfce4-"
+"screenshooter</c> and post your pictures somewhere for all to admire."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):559
+msgid "Summary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):563
+msgid ""
+"Congratulations on making it this far! You've installed and configured a "
+"speedy desktop environment with a solid suite of applications for your "
+"computing needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):572
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):575
+msgid ""
+"Need additional help on configuring and using Xfce? Need more lightweight "
+"application suggestions? Try checking out:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(uri:link):581
+msgid "http://forums.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(uri):581
+msgid "The Gentoo forums"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):582
+msgid "#xfce on irc.freenode.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):583
+msgid ""
+"The installed help files and other documentation provided by Xfce: <path>/"
+"usr/share/xfce4/doc/C/index.html</path>. Just point your browser at it and "
+"start reading. There are even a lot of \"hidden\" configuration options "
+"detailed in the help files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(uri:link):589
+msgid "http://www.xfce.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(uri):589
+msgid "Xfce's home page"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/xml-guide.xml.po b/doc/gettext/ru/xml-guide.xml.po
new file mode 100644
index 0000000..8f866c9
--- /dev/null
+++ b/doc/gettext/ru/xml-guide.xml.po
@@ -0,0 +1,1484 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):6
+msgid "Gentoo GuideXML Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):14
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):9
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):12
+msgid "drobbins@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail):12
+msgid "Daniel Robbins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author):14
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):18
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail):18
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):21
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail):21
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(abstract):27
+msgid ""
+"This guide shows you how to compose web documentation using the new "
+"lightweight Gentoo GuideXML syntax. This syntax is the official format for "
+"Gentoo documentation, and this document itself was created using GuideXML. "
+"This guide assumes a basic working knowledge of XML and HTML."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(version):38
+msgid "10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(date):39
+msgid "2009-02-27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):42
+msgid "GuideXML basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):44
+msgid "GuideXML design goals"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):47
+msgid ""
+"The guideXML syntax is lightweight yet expressive, so that it is easy to "
+"learn yet also provides all the features we need for the creation of web "
+"documentation. The number of tags is kept to a minimum -- just those we "
+"need. This makes it easy to transform guide into other formats, such as "
+"DocBook XML/SGML or web-ready HTML."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):55
+msgid ""
+"The goal is to make it easy to <e>create</e> and <e>transform</e> guideXML "
+"documents."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):63
+msgid "Further Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):66
+msgid ""
+"If you are planning on contributing documentation to Gentoo, or you want to "
+"test GuideXML, please read our <uri link=\"/proj/en/gdp/doc/doc-tipsntricks."
+"xml\">Doc Tips 'n' Tricks</uri> guide which contains tips and tricks for "
+"documentation development."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):73
+msgid ""
+"You may want to look at the <uri link=\"?passthru=1\">XML source</uri> of "
+"this document while you read it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):83
+msgid "GuideXML"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):85
+msgid "Basic structure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):88
+msgid ""
+"Let's start learning the GuideXML syntax. We'll start with the the initial "
+"tags used in a GuideXML document:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):93
+msgid "The initial part of a guide XML document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):93
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
+"&lt;!DOCTYPE guide SYSTEM \"/dtd/guide.dtd\"&gt;\n"
+"&lt;!-- $Header$ --&gt;\n"
+"\n"
+"&lt;guide link=\"<i>/doc/en/guide.xml</i>\" lang=\"<i>en</i>\"&gt;\n"
+"&lt;title&gt;<i>Gentoo Documentation Guide</i>&lt;/title&gt;\n"
+"\n"
+"&lt;author title=\"<i>Author</i>\"&gt;\n"
+"  &lt;mail link=\"<i>yourname@gentoo.org</i>\"&gt;<i>Your Name</i>&lt;/mail&gt;\n"
+"&lt;/author&gt;\n"
+"\n"
+"&lt;abstract&gt;\n"
+"<i>This guide shows you how to compose web documentation using\n"
+"our new lightweight Gentoo GuideXML syntax.  This syntax is the official\n"
+"format for Gentoo web documentation, and this document itself was created\n"
+"using GuideXML.</i>\n"
+"&lt;/abstract&gt;\n"
+"\n"
+"&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt;\n"
+"&lt;!-- See http://creativecommons.org/licenses/by-sa/2.5 --&gt;\n"
+"&lt;license/&gt;\n"
+"\n"
+"&lt;version&gt;<i>1.0</i>&lt;/version&gt;\n"
+"&lt;date&gt;<i>2004-12-25</i>&lt;/date&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):120
+msgid ""
+"On the first lines, we see the requisite tag that identifies this as an XML "
+"document and specifies its DTD. The <c>&lt;!-- $Header$ --&gt;</c> line will "
+"be automatically modified by the CVS server and helps to track revisions. "
+"Next, there's a <c>&lt;guide&gt;</c> tag -- the entire guide document is "
+"enclosed within a <c>&lt;guide&gt; &lt;/guide&gt;</c> pair. <br/> The "
+"<c>link</c> attribute is optional and should preferably contain the absolute "
+"path to the document relatively to the document root even though the file "
+"name alone will work. It is only used to generate a link to a printer-"
+"friendly version of your document and check whether a translation is up-to-"
+"date. Our XSL back-engine passes the actual path to our XSL stylesheet. The "
+"link attribute is only used as a fall-back value in case the XML is "
+"processed by other means. <br/> The <c>lang</c> attribute should be used to "
+"specify the language code of your document. It is used to format the date "
+"and insert strings like \"<e>Note</e>\", \"<e>Content</e>\", etc. in the "
+"specified language. The default is English."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):140
+msgid ""
+"Next, there's a <c>&lt;title&gt;</c> tag, used to set the title for the "
+"entire guide document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):145
+msgid ""
+"Then, we come to the <c>&lt;author&gt;</c> tags, which contain information "
+"about the various authors of the document. Each <c>&lt;author&gt;</c> tag "
+"allows for an optional <c>title</c> element, used to specify the author's "
+"relationship to the document (author, co-author, editor, etc.). In this "
+"particular example, the authors' names are enclosed in another tag -- a "
+"<c>&lt;mail&gt;</c> tag, used to specify an email address for this "
+"particular person. The <c>&lt;mail&gt;</c> tag is optional and can be "
+"omitted, and at least one <c>&lt;author&gt;</c> element is required per "
+"guide document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):156
+msgid ""
+"Next, we come to the <c>&lt;abstract&gt;</c>, <c>&lt;version&gt;</c> and "
+"<c>&lt;date&gt;</c> tags, used to specify a summary of the document, the "
+"current version number, and the current version date (in YYYY-MM-DD format) "
+"respectively. Dates that are invalid or not in the YYYY-MM-DD format will "
+"appear verbatim in the rendered document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):164
+msgid ""
+"This sums up the tags that should appear at the beginning of a guide "
+"document. Besides the <c>&lt;title&gt;</c> and <c>&lt;mail&gt;</c> tags, "
+"these tags shouldn't appear anywhere else except immediately inside the "
+"<c>&lt;guide&gt;</c> tag, and for consistency it's recommended (but not "
+"required) that these tags appear before the content of the document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):172
+msgid ""
+"Finally we have the <c>&lt;license/&gt;</c> tag, used to publish the "
+"document under the <uri link=\"http://creativecommons.org/licenses/by-sa/2.5/"
+"\">Creative Commons - Attribution / Share Alike</uri> license as required by "
+"the <uri link=\"/proj/en/gdp/doc/doc-policy.xml\">Documentation Policy</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):182
+msgid "Chapters and sections"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):185
+msgid ""
+"Once the initial tags have been specified, you're ready to start adding the "
+"structural elements of the document. Guide documents are divided into "
+"chapters, and each chapter can hold one or more sections. Every chapter and "
+"section has a title. Here's an example chapter with a single section, "
+"consisting of a paragraph. If you append this XML to the XML in the <uri "
+"link=\"#doc_chap2_pre1\">previous excerpt</uri> and append a <c>&lt;/"
+"guide&gt;</c> to the end of the file, you'll have a valid (if minimal) guide "
+"document:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):196
+msgid "Minimal guide example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):196
+#, no-wrap
+msgid ""
+"\n"
+"&lt;chapter&gt;\n"
+"&lt;title&gt;<i>This is my chapter</i>&lt;/title&gt;\n"
+"&lt;section&gt;\n"
+"&lt;title&gt;<i>This is section one of my chapter</i>&lt;/title&gt;\n"
+"&lt;body&gt;\n"
+"\n"
+"&lt;p&gt;\n"
+"<i>This is the actual text content of my section.</i>\n"
+"&lt;/p&gt;\n"
+"\n"
+"&lt;/body&gt;\n"
+"&lt;/section&gt;\n"
+"&lt;/chapter&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):212
+msgid ""
+"Above, I set the chapter title by adding a child <c>&lt;title&gt;</c> "
+"element to the <c>&lt;chapter&gt;</c> element. Then, I created a section by "
+"adding a <c>&lt;section&gt;</c> element. If you look inside the <c>&lt;"
+"section&gt;</c> element, you'll see that it has two child elements -- a "
+"<c>&lt;title&gt;</c> and a <c>&lt;body&gt;</c>. While the <c>&lt;title&gt;</"
+"c> is nothing new, the <c>&lt;body&gt;</c> is -- it contains the actual text "
+"content of this particular section. We'll look at the tags that are allowed "
+"inside a <c>&lt;body&gt;</c> element in a bit."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(note):223
+msgid ""
+"A <c>&lt;guide&gt;</c> element must contain at least one <c>&lt;chapter&gt;</"
+"c> elements, a <c>&lt;chapter&gt;</c> must contain at least one <c>&lt;"
+"section&gt;</c> elements and a <c>&lt;section&gt;</c> element must contain "
+"at least one <c>&lt;body&gt;</c> element."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):233
+msgid "An example &lt;body&gt;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):236
+msgid ""
+"Now, it's time to learn how to mark up actual content. Here's the XML code "
+"for an example <c>&lt;body&gt;</c> element:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):241
+msgid "Example of a body element"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):241
+#, no-wrap
+msgid ""
+"\n"
+"&lt;p&gt;\n"
+"This is a paragraph.  &lt;path&gt;/etc/passwd&lt;/path&gt; is a file.\n"
+"&lt;uri&gt;http://forums.gentoo.org&lt;/uri&gt; is my favorite website.\n"
+"Type &lt;c&gt;ls&lt;/c&gt; if you feel like it.  I &lt;e&gt;really&lt;/e&gt; want to go to sleep now.\n"
+"&lt;/p&gt;\n"
+"\n"
+"&lt;pre caption=\"Code Sample\"&gt;\n"
+"This is text output or code.\n"
+"# &lt;i&gt;this is user input&lt;/i&gt;\n"
+"\n"
+"Make HTML/XML easier to read by using selective emphasis:\n"
+"&lt;foo&gt;&lt;i&gt;bar&lt;/i&gt;&lt;/foo&gt;\n"
+"\n"
+"&lt;comment&gt;(This is how to insert a comment into a code block)&lt;/comment&gt;\n"
+"&lt;/pre&gt;\n"
+"\n"
+"&lt;note&gt;\n"
+"This is a note.\n"
+"&lt;/note&gt;\n"
+"\n"
+"&lt;warn&gt;\n"
+"This is a warning.\n"
+"&lt;/warn&gt;\n"
+"\n"
+"&lt;impo&gt;\n"
+"This is important.\n"
+"&lt;/impo&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):271
+msgid "Now, here's how the <c>&lt;body&gt;</c> element above is rendered:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):275
+msgid ""
+"This is a paragraph. <path>/etc/passwd</path> is a file. <uri>http://forums."
+"gentoo.org</uri> is my favorite web site. Type <c>ls</c> if you feel like "
+"it. I <e>really</e> want to go to sleep now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):281
+msgid "Code Sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):281
+#, no-wrap
+msgid ""
+"\n"
+"This is text output or code.\n"
+"# <i>this is user input</i>\n"
+"\n"
+"Make HTML/XML easier to read by using selective emphasis:\n"
+"&lt;foo&gt;<i>bar</i>&lt;/foo&gt;\n"
+"\n"
+"<comment>(This is how to insert a comment into a code block)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(note):291
+msgid "This is a note."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(warn):295
+msgid "This is a warning."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(impo):299
+msgid "This is important."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):306
+msgid "The &lt;body&gt; tags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):309
+msgid ""
+"We introduced a lot of new tags in the previous section -- here's what you "
+"need to know. The <c>&lt;p&gt;</c> (paragraph), <c>&lt;pre&gt;</c> (code "
+"block), <c>&lt;note&gt;</c>, <c>&lt;warn&gt;</c> (warning) and <c>&lt;"
+"impo&gt;</c> (important) tags all can contain one or more lines of text. "
+"Besides the <c>&lt;table&gt;</c>, <c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c> and "
+"<c>&lt;dl&gt;</c> elements (which we'll cover in just a bit), these are the "
+"only tags that should appear immediately inside a <c>&lt;body&gt;</c> "
+"element. Another thing -- these tags <e>should not</e> be stacked -- in "
+"other words, don't put a <c>&lt;note&gt;</c> element inside a <c>&lt;p&gt;</"
+"c> element. As you might guess, the <c>&lt;pre&gt;</c> element preserves its "
+"whitespace exactly, making it well-suited for code excerpts. You must name "
+"the <c>&lt;pre&gt;</c> tag with a <c>caption</c> attribute:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):324
+msgid "Named <pre/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):324
+#, no-wrap
+msgid ""
+"\n"
+"&lt;pre caption=\"Output of uptime\"&gt;\n"
+"# &lt;i&gt;uptime&lt;/i&gt;\n"
+"16:50:47 up 164 days,  2:06,  5 users,  load average: 0.23, 0.20, 0.25\n"
+"&lt;/pre&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):334
+msgid "Epigraphs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):337
+msgid ""
+"Delegates from the original 13 states formed the Contented Congress. Thomas "
+"Jefferson, a Virgin, and Benjamin Franklin were two singers of the "
+"Declaration of Independence. Franklin discovered electricity by rubbing two "
+"cats backwards and declared, \"A horse divided against itself cannot stand."
+"\" Franklin died in 1790 and is still dead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):345
+msgid ""
+"Epigraphs are sometimes used at the beginning of chapters to illustrate what "
+"is to follow. It is simply a paragraph with a <c>by</c> attribute that "
+"contains the signature."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):351
+msgid "Short epigraph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):351
+#, no-wrap
+msgid ""
+"\n"
+"&lt;p by=\"Anonymous student\"&gt;\n"
+"Delegates from the original 13 states formed the...\n"
+"&lt;/p&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):360
+msgid ""
+"&lt;path&gt;, &lt;c&gt;, &lt;b&gt;, &lt;e&gt;, &lt;sub&gt; and &lt;sup&gt;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):365
+msgid ""
+"The <c>&lt;path&gt;</c>, <c>&lt;c&gt;</c>, <c>&lt;b&gt;</c>, <c>&lt;e&gt;</"
+"c>, <c>&lt;sub&gt;</c> and <c>&lt;sup&gt;</c> elements can be used inside "
+"any child <c>&lt;body&gt;</c> tag, except for <c>&lt;pre&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):371
+msgid ""
+"The <c>&lt;path&gt;</c> element is used to mark text that refers to an <e>on-"
+"disk file</e> -- either an <e>absolute or relative path</e>, or a <e>simple "
+"filename</e>. This element is generally rendered with a mono spaced font to "
+"offset it from the standard paragraph type."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):378
+msgid ""
+"The <c>&lt;c&gt;</c> element is used to mark up a <e>command</e> or <e>user "
+"input</e>. Think of <c>&lt;c&gt;</c> as a way to alert the reader to "
+"something that they can type in that will perform some kind of action. For "
+"example, all the XML tags displayed in this document are enclosed in a "
+"<c>&lt;c&gt;</c> element because they represent something that the user "
+"could type in that is not a path. By using <c>&lt;c&gt;</c> elements, you'll "
+"help your readers quickly identify commands that they need to type in. Also, "
+"because <c>&lt;c&gt;</c> elements are already offset from regular text, "
+"<e>it is rarely necessary to surround user input with double-quotes</e>. For "
+"example, don't refer to a \"<c>&lt;c&gt;</c>\" element like I did in this "
+"sentence. Avoiding the use of unnecessary double-quotes makes a document "
+"more readable -- and adorable!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):393
+msgid ""
+"As you might have guessed, <c>&lt;b&gt;</c> is used to <b>boldface</b> some "
+"text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):398
+msgid ""
+"<c>&lt;e&gt;</c> is used to apply emphasis to a word or phrase; for example: "
+"I <e>really</e> should use semicolons more often. As you can see, this text "
+"is offset from the regular paragraph type for emphasis. This helps to give "
+"your prose more <e>punch</e>!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):405
+msgid ""
+"The <c>&lt;sub&gt;</c> and <c>&lt;sup&gt;</c> elements are used to specify "
+"<sub>subscript</sub> and <sup>superscript</sup>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):413
+msgid "Code samples and colour-coding"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):416
+msgid ""
+"To improve the readability of code samples, the following tags are allowed "
+"inside <c>&lt;pre&gt;</c> blocks:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):423
+msgid "Distinguishes user input from displayed text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):425
+msgid "Comments relevant to the action(s) that appear after the comment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):427
+msgid "Denotes a keyword in the language used in the code sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):430
+msgid "Used for an identifier"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):433
+msgid "Used for a constant"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):436
+msgid "Used for a statement"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):439
+msgid "Used for a variable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(note):443
+msgid ""
+"Remember that all leading and trailing spaces, and line breaks in <c>&lt;"
+"pre&gt;</c> blocks will appear in the displayed html page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):448
+msgid "Sample colour-coded <c>&lt;pre&gt;</c> block:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):452
+msgid "My first ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):452
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Copyright 1999-2009 <b>Gentoo Foundation</b>\n"
+"# Distributed under the terms of the GNU General Public License v2\n"
+"# $Header: $</comment>\n"
+"\n"
+"<ident>DESCRIPTION</ident>=<const>\"Exuberant ctags generates tags files for quick source navigation\"</const>\n"
+"<ident>HOMEPAGE</ident>=<const>\"http://ctags.sourceforge.net\"</const>\n"
+"<ident>SRC_URI</ident>=<const>\"mirror://sourceforge/ctags/<var>${P}</var>.tar.gz\"</const>\n"
+"\n"
+"<ident>LICENSE</ident>=<const>\"GPL-2\"</const>\n"
+"<ident>SLOT</ident>=<const>\"0\"</const>\n"
+"<ident>KEYWORDS</ident>=<const>\"~mips ~sparc ~x86\"</const>\n"
+"<ident>IUSE</ident>=<const>\"\"</const>\n"
+"\n"
+"<stmt>src_compile()</stmt> {\n"
+"    <keyword>econf</keyword> --with-posix-regex\n"
+"    <keyword>emake</keyword> || <keyword>die</keyword> <const>\"emake failed\"</const>\n"
+"}\n"
+"\n"
+"<stmt>src_install()</stmt> {\n"
+"    <keyword>make</keyword> <ident>DESTDIR</ident>=\"<var>${D}</var>\" install || <keyword>die</keyword> <const>\"install failed\"</const>\n"
+"\n"
+"    <keyword>dodoc</keyword> FAQ NEWS README\n"
+"    <keyword>dohtml</keyword> EXTENDING.html ctags.html\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):482
+msgid "&lt;mail&gt; and &lt;uri&gt;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):485
+msgid ""
+"We've taken a look at the <c>&lt;mail&gt;</c> tag earlier; it's used to link "
+"some text with a particular email address, and takes the form <c>&lt;mail "
+"link=\"foo.bar@example.com\"&gt;Mr. Foo Bar&lt;/mail&gt;</c>. If you want to "
+"display the email address, you can use <c>&lt;mail&gt;foo.bar@example."
+"com&lt;/mail&gt;</c>, this would be displayed as <mail>foo.bar@example.com</"
+"mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):493
+msgid ""
+"Shorter forms make it easier to use names and emails of Gentoo developers. "
+"Both <c>&lt;mail&gt;neysx&lt;/mail&gt;</c> and <c>&lt;mail link=\"neysx\"/"
+"&gt;</c> would appear as <mail>neysx</mail>. If you want to use a Gentoo "
+"dev's email with a different content than his full name, use the second form "
+"with some content. For instance, use a dev's first name: <c>&lt;mail link="
+"\"neysx\"&gt;Xavier&lt;/mail&gt;</c> appears as <mail link=\"neysx\">Xavier</"
+"mail>. <br/> This is particularly useful when you want to name a developer "
+"whose name contains \"funny\" characters that you can't type."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):506
+msgid ""
+"The <c>&lt;uri&gt;</c> tag is used to point to files/locations on the "
+"Internet. It has two forms -- the first can be used when you want to have "
+"the actual URI displayed in the body text, such as this link to <uri>http://"
+"forums.gentoo.org/</uri>. To create this link, I typed <c>&lt;uri&gt;http://"
+"forums.gentoo.org/&lt;/uri&gt;</c>. The alternate form is when you want to "
+"associate a URI with some other text -- for example, <uri link=\"http://"
+"forums.gentoo.org/\">the Gentoo Forums</uri>. To create <e>this</e> link, I "
+"typed <c>&lt;uri link=\"http://forums.gentoo.org/\"&gt;the Gentoo Forums&lt;/"
+"uri&gt;</c>. You don't need to write <c>http://www.gentoo.org/</c> to link "
+"to other parts of the Gentoo web site. For instance, a link to the <uri link="
+"\"/doc/en/\">documentation main index</uri> should be simply <c>&lt;uri link="
+"\"/doc/en/index.xml\"&gt;documentation main index&lt;/uri&gt;</c>. You can "
+"even omit <c>index.xml</c> when you link to a directory index, e.g. <c>&lt;"
+"uri link=\"/doc/en/\"&gt;documentation main index&lt;/uri&gt;</c>. Leaving "
+"the trailing slash saves an extra HTTP request."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):524
+msgid ""
+"You should not use a <c>&lt;uri&gt;</c> tag with a <c>link</c> attribute "
+"that starts with <c>mailto:</c>. In this case, use a <c>&lt;mail&gt;</c> tag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):529
+msgid ""
+"Please avoid the <uri link=\"http://en.wikipedia.org/wiki/Click_here\">click "
+"here syndrome</uri> as recommended by the <uri link=\"http://www.w3.org/QA/"
+"Tips/noClickHere\">W3C</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):538
+msgid "Figures"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):541
+msgid ""
+"Here's how to insert a figure into a document -- <c>&lt;figure link=\"mygfx."
+"png\" short=\"my picture\" caption=\"my favorite picture of all time\"/&gt;</"
+"c>. The <c>link</c> attribute points to the actual graphic image, the "
+"<c>short</c> attribute specifies a short description (currently used for the "
+"image's HTML <c>alt</c> attribute), and a caption. Not too difficult :) We "
+"also support the standard HTML-style &lt;img src=\"foo.gif\"/&gt; tag for "
+"adding images without captions, borders, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):554
+msgid "Tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):557
+msgid ""
+"GuideXML supports a simplified table syntax similar to that of HTML. To "
+"start a table, use a <c>&lt;table&gt;</c> tag. Start a row with a <c>&lt;"
+"tr&gt;</c> tag. However, for inserting actual table data, we <e>don't</e> "
+"support the HTML &lt;td&gt; tag; instead, use the <c>&lt;th&gt;</c> if you "
+"are inserting a header, and <c>&lt;ti&gt;</c> if you are inserting a normal "
+"informational block. You can use a <c>&lt;th&gt;</c> anywhere you can use a "
+"<c>&lt;ti&gt;</c> -- there's no requirement that <c>&lt;th&gt;</c> elements "
+"appear only in the first row."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):568
+msgid ""
+"Besides, both table headers (<c>&lt;th&gt;</c>) and table items (<c>&lt;"
+"ti&gt;</c>) accept the <c>colspan</c> and <c>rowspan</c> attributes to span "
+"their content across rows, columns or both."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):574
+msgid ""
+"Furthermore, table cells (<c>&lt;ti&gt;</c> &amp; <c>&lt;th&gt;</c>) can be "
+"right-aligned, left-aligned or centered with the <c>align</c> attribute."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(th):581
+msgid "This title spans 4 columns"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(th):584
+msgid "This title spans 6 rows"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):585
+msgid "Item A1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):586
+msgid "Item A2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):587
+msgid "Item A3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):590
+msgid "Item B1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(th):591
+msgid "Blocky 2x2 title"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):594
+msgid "Item C1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):597
+msgid "Item D1..D3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):600
+msgid "Item E1..F1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):601
+msgid "Item E2..E3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):604
+msgid "Item F2..F3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):611
+msgid "Lists"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):614
+msgid ""
+"To create ordered or unordered lists, simply use the XHTML-style <c>&lt;"
+"ol&gt;</c>, <c>&lt;ul&gt;</c> and <c>&lt;li&gt;</c> tags. Lists may only "
+"appear inside the <c>&lt;body&gt;</c> and <c>&lt;li&gt;</c> tags which means "
+"that you can have lists inside lists. Don't forget that you are writing XML "
+"and that you must close all tags including list items unlike in HTML."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):622
+msgid ""
+"Definition lists (<c>&lt;dl&gt;</c>) are also supported. Please note that "
+"neither the definition term tag (<c>&lt;dt&gt;</c>) nor the definition data "
+"tag (<c>&lt;dd&gt;</c>) accept any other block level tag such as paragraphs "
+"or admonitions. A definition list comprises:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):631
+msgid "A <b>D</b>efinition <b>L</b>ist Tag containing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):633
+msgid "Pairs of <b>D</b>efinition <b>T</b>erm Tags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):635
+msgid "and <b>D</b>efinition <b>D</b>ata Tags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):638
+msgid ""
+"The following list copied from <uri link=\"http://www.w3.org/TR/REC-html40/"
+"struct/lists.html\">w3.org</uri> shows that a definition list can contain "
+"ordered and unordered lists. It may not contain another definition list "
+"though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):649
+msgid "100 g. flour"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):650
+msgid "10 g. sugar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):651
+msgid "1 cup water"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):652
+msgid "2 eggs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):653
+msgid "salt, pepper"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):659
+msgid "Mix dry ingredients thoroughly"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):660
+msgid "Pour in wet ingredients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):661
+msgid "Mix for 10 minutes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):662
+msgid "Bake for one hour at 300 degrees"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):666
+msgid "The recipe may be improved by adding raisins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):672
+msgid "Intra-document references"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):675
+msgid ""
+"GuideXML makes it really easy to reference other parts of the document using "
+"hyperlinks. You can create a link pointing to <uri link="
+"\"#doc_chap1\">Chapter One</uri> by typing <c>&lt;uri link=\"#doc_chap1\"&gt;"
+"Chapter One&lt;/uri&gt;</c>. To point to <uri link="
+"\"#doc_chap1_sect2\">section two of Chapter One</uri>, type <c>&lt;uri link="
+"\"#doc_chap1_sect2\"&gt;section two of Chapter One&lt;/uri&gt;</c>. To refer "
+"to figure 3 in chapter 1, type <c>&lt;uri link=\"#doc_chap1_fig3\"&gt;figure "
+"1.3&lt;/uri&gt;</c>. Or, to refer to <uri link=\"#doc_chap2_pre2\">code "
+"listing 2 in chapter 2</uri>, type <c>&lt;uri link=\"#doc_chap2_pre2\"&gt;"
+"code listing 2.2&lt;/uri&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):687
+msgid ""
+"However, some guides change often and using such \"counting\" can lead to "
+"broken links. In order to cope with this, you can define a name for a <c>&lt;"
+"chapter&gt;</c>, <c>&lt;section&gt;</c> or a <c>&lt;tr&gt;</c> by using the "
+"<c>id</c> attribute, and then point to that attribute, like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):694
+msgid "Using the id attribute"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):694
+#, no-wrap
+msgid ""
+"\n"
+"&lt;chapter id=\"foo\"&gt;\n"
+"&lt;title&gt;This is foo!&lt;/title&gt;\n"
+"...\n"
+"&lt;p&gt;\n"
+"More information can be found in the &lt;uri link=\"#foo\"&gt;foo chapter&lt;/uri&gt;\n"
+"&lt;/p&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):706
+msgid "Disclaimers and obsolete documents"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):709
+msgid ""
+"A <c>disclaimer</c> attribute can be applied to guides and handbooks to "
+"display a predefined disclaimer at the top of the document. The available "
+"disclaimers are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):716
+msgid ""
+"<b>articles</b> is used for <uri link=\"/doc/en/articles/\">republished "
+"articles</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):720
+msgid ""
+"<b>draft</b> is used to indicate a document is still being worked on and "
+"should not be considered official"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):724
+msgid ""
+"<b>oldbook</b> is used on old handbooks to indicate they are not maintained "
+"anymore"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):728
+msgid "<b>obsolete</b> is used to mark a document as obsolete."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):731
+msgid ""
+"When marking a document as obsolete, you might want to add a link to a new "
+"version. The <c>redirect</c> attribute does just that. The user might be "
+"automatically redirected to the new page but you should not rely on that "
+"behaviour."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):738
+msgid "Disclaimer sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):738
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
+"&lt;!DOCTYPE guide SYSTEM \"/dtd/guide.dtd\"&gt;\n"
+"&lt;!-- $Header$ --&gt;\n"
+"\n"
+"&lt;guide disclaimer=\"obsolete\" redirect=\"/doc/en/handbook/handbook-x86.xml\"&gt;\n"
+"&lt;title&gt;Gentoo x86 Installation Guide&lt;/title&gt;\n"
+"\n"
+"&lt;author title=\"Author\"&gt;\n"
+"...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):753
+msgid "FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):756
+msgid ""
+"FAQ documents need to start with a list of questions with links to their "
+"answers. Creating such a list is both time-consuming and error-prone. The "
+"list can be created automatically if you use a <c>faqindex</c> element as "
+"the first chapter of your document. This element has the same structure as a "
+"<c>chapter</c> to allow some introductory text. The structure of the "
+"document is expected to be split into chapters (at least one chapter) "
+"containing sections, each section containing one question specified in its "
+"<c>title</c> element with the answer in its <c>body</c>. The FAQ index will "
+"appear as one section per chapter and one link per question."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):768
+msgid ""
+"A quick look at a <uri link=\"/doc/en/faq.xml\">FAQ</uri> and <uri link=\"/"
+"doc/en/faq.xml?passthru=1\">its source</uri> should make the above obvious."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):779
+msgid "Handbook Format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):781
+msgid "Guide vs Book"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):784
+msgid ""
+"For high-volume documentation, such as the <uri link=\"/doc/en/handbook/"
+"handbook-x86.xml?part=1\">Installation Instructions</uri>, a broader format "
+"was needed. We designed a GuideXML-compatible enhancement that allows us to "
+"write modular and multi-page documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):794
+msgid "Main File"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):797
+msgid ""
+"The first change is the need for a \"master\" document. This document "
+"contains no real content, but links to the individual documentation modules. "
+"The syntax doesn't differ much from GuideXML:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):803
+msgid "Example book usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):803
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version='1.0' encoding='UTF-8'?&gt;\n"
+"&lt;!DOCTYPE book SYSTEM \"/dtd/book.dtd\"&gt;\n"
+"&lt;!-- $Header$ --&gt;\n"
+"\n"
+"&lt;<i>book</i>&gt;\n"
+"&lt;title&gt;Example Book Usage&lt;/title&gt;\n"
+"\n"
+"&lt;author...&gt;\n"
+"  ...\n"
+"&lt;/author&gt;\n"
+"\n"
+"&lt;abstract&gt;\n"
+"  ...\n"
+"&lt;/abstract&gt;\n"
+"\n"
+"&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt;\n"
+"&lt;!-- See http://creativecommons.org/licenses/by-sa/2.5 --&gt;\n"
+"&lt;license/&gt;\n"
+"\n"
+"&lt;version&gt;...&lt;/version&gt;\n"
+"&lt;date&gt;...&lt;/date&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):827
+msgid ""
+"So far no real differences (except for the <c>&lt;book&gt;</c> instead of "
+"<c>&lt;guide&gt;</c> tag). Instead of starting with the individual <c>&lt;"
+"chapter&gt;</c>s, you define a <c>&lt;part&gt;</c>, which is the equivalent "
+"of a separate part in a book:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):834
+msgid "Defining a part"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):834
+#, no-wrap
+msgid ""
+"\n"
+"&lt;part&gt;\n"
+"&lt;title&gt;Part One&lt;/title&gt;\n"
+"&lt;abstract&gt;\n"
+"  ...\n"
+"&lt;/abstract&gt;\n"
+"\n"
+"<comment>(Defining the several chapters)</comment>\n"
+"&lt;/part&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):845
+msgid ""
+"Each part is accompanied by a <c>&lt;title&gt;</c> and an <c>&lt;abstract&gt;"
+"</c> which gives a small introduction to the part."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):850
+msgid ""
+"Inside each part, you define the individual <c>&lt;chapter&gt;</c>s. Each "
+"chapter <e>must</e> be a separate document. As a result it is no surprise "
+"that a special tag (<c>&lt;include&gt;</c>) is added to allow including the "
+"separate document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):857
+msgid "Defining a chapter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):857
+#, no-wrap
+msgid ""
+"\n"
+"&lt;chapter&gt;\n"
+"&lt;title&gt;Chapter One&lt;/title&gt;\n"
+"\n"
+"  &lt;include href=\"path/to/chapter-one.xml\"/&gt;\n"
+"\n"
+"&lt;/chapter&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):869
+msgid "Designing the Individual Chapters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):872
+msgid "The content of an individual chapter is structured as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):876
+msgid "Chapter Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):876
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version='1.0' encoding='UTF-8'?&gt;\n"
+"&lt;!DOCTYPE sections SYSTEM \"/dtd/book.dtd\"&gt;\n"
+"&lt;!-- $Header$ --&gt;\n"
+"\n"
+"&lt;!--  The content of this document is licensed under the CC-BY-SA license --&gt;\n"
+"&lt;!--  See http://creativecommons.org/licenses/by-sa/2.5 --&gt;\n"
+"\n"
+"&lt;sections&gt;\n"
+"\n"
+"&lt;abstract&gt;\n"
+"  This is a small explanation on chapter one.\n"
+"&lt;/abstract&gt;\n"
+"\n"
+"&lt;version&gt;...&lt;/version&gt;\n"
+"&lt;date&gt;...&lt;/date&gt;\n"
+"\n"
+"<comment>(Define the several &lt;section&gt; and &lt;subsection&gt;)</comment>\n"
+"\n"
+"&lt;/sections&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):898
+msgid ""
+"Inside each chapter you can define <c>&lt;section&gt;</c>s (equivalent of "
+"<c>&lt;chapter&gt;</c> in a Guide) and <c>&lt;subsection&gt;</c>s "
+"(equivalent of <c>&lt;section&gt;</c> in a Guide)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):904
+msgid ""
+"Each individual chapter should have its own date and version elements. The "
+"latest date of all chapters and master document will be displayed when a "
+"user browses through all parts of the book."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):915
+msgid "Advanced Handbook Features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):917
+msgid "Global Values"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):920
+msgid ""
+"Sometimes, the same values are repeated many times in several parts of a "
+"handbook. Global search and replace operations tend to forget some or "
+"introduce unwanted changes. Besides, it can be useful to define different "
+"values to be used in shared chapters depending on which handbook includes "
+"the chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):927
+msgid ""
+"Global values can be defined in a handbook master file and used in all "
+"included chapters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):932
+msgid ""
+"To define global values, add a <c>&lt;values&gt;</c> element to the handbook "
+"master file. Each value is then defined in a <c>&lt;key&gt;</c> element "
+"whose <c>id</c> attribute identifies the value, i.e. it is the name of your "
+"variable. The content of the <c>&lt;key&gt;</c> is its value."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):939
+msgid "The following example defines three values in a handbook master file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):943
+msgid "Define values in a handbook"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):943
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version='1.0' encoding='UTF-8'?&gt;\n"
+"&lt;!DOCTYPE book SYSTEM \"/dtd/book.dtd\"&gt;\n"
+"&lt;!-- $Header$ --&gt;\n"
+"\n"
+"&lt;book&gt;\n"
+"&lt;title&gt;Example Book Usage&lt;/title&gt;\n"
+"\n"
+"<i>&lt;values&gt;\n"
+" &lt;key id=\"arch\"&gt;x86&lt;/key&gt;\n"
+" &lt;key id=\"min-cd-name\"&gt;install-x86-minimal-2007.0-r1.iso&lt;/key&gt;\n"
+" &lt;key id=\"min-cd-size\"&gt;57&lt;/key&gt;\n"
+"&lt;/values&gt;</i>\n"
+"\n"
+"&lt;author...&gt;\n"
+"  ...\n"
+"&lt;/author&gt;\n"
+"\n"
+"...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):964
+msgid ""
+"The defined values can then be used throughout the handbook with the in-line "
+"<c>&lt;keyval id=\"key_id\"/&gt;</c> element. Specify the name of the key in "
+"its <c>id</c> attribute, e.g. &lt;keyval id=\"min-cd-name\"/&gt; would be "
+"replaced by \"install-x86-minimal-2007.0-r1.iso\" in our example."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):971
+msgid "Using defined values"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):971
+#, no-wrap
+msgid ""
+"\n"
+"&lt;p&gt;\n"
+"The Minimal Installation CD is called &lt;c&gt;<i>&lt;keyval id=\"min-cd-name\"/&gt;</i>&lt;/c&gt;\n"
+"and takes up only <i>&lt;keyval id=\"min-cd-size\"/&gt;</i> MB of diskspace. You can use this\n"
+"Installation CD to install Gentoo, but &lt;e&gt;only&lt;/e&gt; with a working Internet\n"
+"connection.\n"
+"&lt;/p&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):980
+msgid ""
+"To make life easier on our translators, only use actual values, i.e. content "
+"that does not need to be translated. For instance, we defined the <c>min-cd-"
+"size</c> value to <c>57</c> and not <c>57 MB</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):989
+msgid "Conditional Elements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):992
+msgid ""
+"Chapters that are shared by several handbooks such as our <uri link=\"/doc/"
+"en/handbook/\">Installation Handbooks</uri> often have small differences "
+"depending on which handbook includes them. Instead of adding content that is "
+"irrelevant to some handbooks, authors can add a condition to the following "
+"elements: <c>&lt;section&gt;</c>, <c>&lt;subsection&gt;</c>, <c>&lt;body&gt;"
+"</c>, <c>&lt;note&gt;</c>, <c>&lt;impo&gt;</c>, <c>&lt;warn&gt;</c>, <c>&lt;"
+"pre&gt;</c>, <c>&lt;p&gt;</c>, <c>&lt;table&gt;</c>, <c>&lt;tr&gt;</c>, "
+"<c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c> and <c>&lt;li&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1004
+msgid ""
+"The condition must be an <uri link=\"http://en.wikipedia.org/wiki/XPath"
+"\">XPATH</uri> expression that will be evaluated when transforming the XML. "
+"If it evaluates to <c>true</c>, the element is processed, if not, it is "
+"ignored. The condition is specified in a <c>test</c> attribute."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1012
+msgid ""
+"The following example uses the <c>arch</c> value that is defined in each "
+"handbook master file to condition some content:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1017
+msgid "Using conditional elements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1017
+#, no-wrap
+msgid ""
+"\n"
+"&lt;body test=\"contains('AMD64 x86',func:keyval('arch'))\"&gt;\n"
+"\n"
+"&lt;p&gt;\n"
+"This paragraph applies to both x86 and AMD64 architectures.\n"
+"&lt;/p&gt;\n"
+"\n"
+"&lt;p test=\"func:keyval('arch')='x86'\"&gt;\n"
+"This paragraph only applies to the x86 architecture.\n"
+"&lt;/p&gt;\n"
+"\n"
+"&lt;p test=\"func:keyval('arch')='AMD64'\"&gt;\n"
+"This paragraph only applies to the AMD64 architecture.\n"
+"&lt;/p&gt;\n"
+"\n"
+"&lt;p test=\"func:keyval('arch')='PPC'\"&gt;\n"
+"This paragraph will never be seen!\n"
+"The whole body is skipped because of the first condition.\n"
+"&lt;/p&gt;\n"
+"\n"
+"&lt;/body&gt;\n"
+"\n"
+"&lt;body test=\"contains('AMD64 PPC64',func:keyval('arch'))\"&gt;\n"
+"\n"
+"&lt;p&gt;\n"
+"This paragraph applies to the AMD64, PPC64 <comment>and PPC</comment> architectures because\n"
+"the 'AMD64 PPC64' string does contain 'PPC'.\n"
+"&lt;/p&gt;\n"
+"\n"
+"&lt;note test=\"func:keyval('arch')='AMD64' or func:keyval('arch')='PPC64'\"&gt;\n"
+"This note only applies to the AMD64 and PPC64 architectures.\n"
+"&lt;/note&gt;\n"
+"\n"
+"&lt;/body&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1058
+msgid "Coding Style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1060
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1063
+msgid ""
+"Since all Gentoo Documentation is a joint effort and several people will "
+"most likely change existing documentation, a coding style is needed. A "
+"coding style contains two sections. The first one is regarding internal "
+"coding - how the XML-tags are placed. The second one is regarding the "
+"content - how not to confuse the reader."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1071
+msgid "Both sections are described next."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1078
+msgid "Internal Coding Style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1081
+msgid ""
+"<b>Newlines</b> must be placed immediately after <e>every</e> GuideXML-tag "
+"(both opening as closing), except for: <c>&lt;version&gt;</c>, <c>&lt;"
+"date&gt;</c>, <c>&lt;title&gt;</c>, <c>&lt;th&gt;</c>, <c>&lt;ti&gt;</c>, "
+"<c>&lt;li&gt;</c>, <c>&lt;i&gt;</c>, <c>&lt;e&gt;</c>, <c>&lt;uri&gt;</c>, "
+"<c>&lt;path&gt;</c>, <c>&lt;b&gt;</c>, <c>&lt;c&gt;</c>, <c>&lt;comment&gt;</"
+"c>, <c>&lt;mail&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1091
+msgid ""
+"<b>Blank lines</b> must be placed immediately after <e>every</e><c>&lt;"
+"body&gt;</c> (opening tag only) and before <e>every</e><c>&lt;chapter&gt;</"
+"c>, <c>&lt;p&gt;</c>, <c>&lt;table&gt;</c>, <c>&lt;author&gt;</c> (set), "
+"<c>&lt;pre&gt;</c>, <c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c>, <c>&lt;warn&gt;</"
+"c>, <c>&lt;note&gt;</c> and <c>&lt;impo&gt;</c> (opening tags only)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1100
+msgid ""
+"<b>Word-wrapping</b> must be applied at 80 characters except inside <c>&lt;"
+"pre&gt;</c>. You may only deviate from this rule when there is no other "
+"choice (for instance when a URL exceeds the maximum amount of characters). "
+"The editor must then wrap whenever the first whitespace occurs. You should "
+"try to keep the <e>rendered</e> content of <c>&lt;pre&gt;</c> elements "
+"within 80 columns to help console users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1109
+msgid ""
+"<b>Indentation</b> may not be used, except with the XML-constructs of which "
+"the parent XML-tags are <c>&lt;tr&gt;</c> (from <c>&lt;table&gt;</c>), "
+"<c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c>, <c>&lt;dl&gt;</c>, and <c>&lt;"
+"author&gt;</c>. If indentation is used, it <e>must</e> be two spaces for "
+"each indentation. That means <e>no tabs</e> and <e>not</e> more spaces. "
+"Besides, tabs are not allowed in GuideXML documents."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1118
+msgid ""
+"In case word-wrapping happens in <c>&lt;ti&gt;</c>, <c>&lt;th&gt;</c>, "
+"<c>&lt;li&gt;</c> or <c>&lt;dd&gt;</c> constructs, indentation must be used "
+"for the content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1124
+msgid "An example for indentation is:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1128
+msgid "Indentation Example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1128
+#, no-wrap
+msgid ""
+"\n"
+"&lt;table&gt;\n"
+"&lt;tr&gt;\n"
+"  &lt;th&gt;Foo&lt;/th&gt;\n"
+"  &lt;th&gt;Bar&lt;/th&gt;\n"
+"&lt;/tr&gt;\n"
+"&lt;tr&gt;\n"
+"  &lt;ti&gt;This is an example for indentation&lt;/ti&gt;\n"
+"  &lt;ti&gt;\n"
+"    In case text cannot be shown within an 80-character wide line, you\n"
+"    must use indentation if the parent tag allows it\n"
+"  &lt;/ti&gt;\n"
+"&lt;/tr&gt;\n"
+"&lt;/table&gt;\n"
+"\n"
+"&lt;ul&gt;\n"
+"  &lt;li&gt;First option&lt;/li&gt;\n"
+"  &lt;li&gt;Second option&lt;/li&gt;\n"
+"&lt;/ul&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1149
+msgid ""
+"<b>Attributes</b> may not have spaces in between the attribute, the \"=\" "
+"mark, and the attribute value. As an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1154
+msgid "Attributes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1154
+#, no-wrap
+msgid ""
+"\n"
+"<comment>Wrong  :</comment>     &lt;pre caption = \"Attributes\"&gt;\n"
+"<comment>Correct:</comment>     &lt;pre caption=\"Attributes\"&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1162
+msgid "External Coding Style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1165
+msgid ""
+"Inside tables (<c>&lt;table&gt;</c>) and listings (<c>&lt;ul&gt;</c>, <c>&lt;"
+"ol&gt;</c>) and <c>&lt;dl&gt;</c>, periods (\".\") should not be used unless "
+"multiple sentences are used. In that case, every sentence should end with a "
+"period (or other reading marks)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1172
+msgid ""
+"Every sentence, including those inside tables and listings, should start "
+"with a capital letter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1177
+msgid "Periods and capital letters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1177
+#, no-wrap
+msgid ""
+"\n"
+"&lt;ul&gt;\n"
+"  &lt;li&gt;No period&lt;/li&gt;\n"
+"  &lt;li&gt;With period. Multiple sentences, remember?&lt;/li&gt;\n"
+"&lt;/ul&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1184
+msgid "Code Listings should <e>always</e> have a <c>caption</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1188
+msgid ""
+"Try to use <c>&lt;uri&gt;</c> with the <c>link</c> attribute as much as "
+"possible. In other words, the <uri link=\"http://forums.gentoo.org\">Gentoo "
+"Forums</uri> is preferred over <uri>http://forums.gentoo.org</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1194
+msgid ""
+"When you comment something inside a <c>&lt;pre&gt;</c> construct, use <c>&lt;"
+"comment&gt;</c> and parentheses or the comment marker for the language that "
+"is being used (<c>#</c> for bash scripts and many other things, <c>//</c> "
+"for C code, etc.) Also place the comment <e>before</e> the subject of the "
+"comment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1202
+msgid "Comment example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1202
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Substitute \"john\" with your user name)</comment>\n"
+"# <i>id john</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1212
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1214
+msgid "Start writing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1217
+msgid ""
+"GuideXML has been specially designed to be \"lean and mean\" so that "
+"developers can spend more time writing documentation and less time learning "
+"the actual XML syntax. Hopefully, this will allow developers who aren't "
+"unusually \"doc-savvy\" to start writing quality Gentoo documentation. You "
+"might be interested in our <uri link=\"/proj/en/gdp/doc/doc-tipsntricks.xml"
+"\">Documentation Development Tips &amp; Tricks</uri>. If you'd like to help "
+"(or have any questions about GuideXML), please post a message to the <uri "
+"link=\"/main/en/lists.xml\">gentoo-doc mailing list</uri> stating what you'd "
+"like to tackle. Have fun!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/xorg-config.xml.po b/doc/gettext/ru/xorg-config.xml.po
new file mode 100644
index 0000000..a9612d5
--- /dev/null
+++ b/doc/gettext/ru/xorg-config.xml.po
@@ -0,0 +1,982 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):6
+msgid "The X Server Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(mail:link):9
+msgid "swift"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(abstract):15
+msgid ""
+"Xorg is the X Window server which allows users to have a graphical "
+"environment at their fingertips. This HOWTO explains what Xorg is, how to "
+"install it and what the various configuration options are."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(version):25
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(date):26
+msgid "2010-10-12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):29
+msgid "What is the X Window Server?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):31
+msgid "Graphical vs Command-Line"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):34
+msgid ""
+"The average user may be frightened at the thought of having to type in "
+"commands. Why wouldn't he be able to point and click his way through the "
+"freedom provided by Gentoo (and Linux in general)? Well, of course you are "
+"able to do this! Linux offers a wide variety of flashy user interfaces and "
+"environments which you can install on top of your existing installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):42
+msgid ""
+"This is one of the biggest surprises new users come across: a graphical user "
+"interface is nothing more than an application which runs on your system. It "
+"is <e>not</e> part of the Linux kernel or any other internals of the system. "
+"It is a powerful tool that fully enables the graphical abilities of your "
+"workstation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):49
+msgid ""
+"As standards are important, a standard for drawing and moving windows on a "
+"screen, interacting with the user through mouse, keyboard and other basic, "
+"yet important aspects has been created and named the <e>X Window System</e>, "
+"commonly abbreviated as <e>X11</e> or just <e>X</e>. It is used on Unix, "
+"Linux and Unix-like operating systems throughout the world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):57
+msgid ""
+"The application that provides Linux users with the ability to run graphical "
+"user interfaces and that uses the X11 standard is Xorg-X11, a fork of the "
+"XFree86 project. XFree86 has decided to use a license that might not be "
+"compatible with the GPL license; the use of Xorg is therefore recommended. "
+"The official Portage tree does not provide an XFree86 package anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):68
+msgid "The X.org Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):71
+msgid ""
+"The <uri link=\"http://www.x.org\">X.org</uri> project created and maintains "
+"a freely redistributable, open-source implementation of the X11 system. It "
+"is an open source X11-based desktop infrastructure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):77
+msgid ""
+"Xorg provides an interface between your hardware and the graphical software "
+"you want to run. Besides that, Xorg is also fully network-aware, meaning you "
+"are able to run an application on one system while viewing it on a different "
+"one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):89
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):315
+msgid "Installing Xorg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):93
+msgid ""
+"Before you can install Xorg, you need to prepare your system for it. First, "
+"we'll set up the kernel to support input devices and video cards. Then we'll "
+"prepare <path>/etc/make.conf</path> so that the right drivers and Xorg "
+"packages are built and installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):103
+msgid "Input driver support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):106
+msgid ""
+"By default, Xorg uses <c>evdev</c>, a generic input driver. You'll need to "
+"activate support for <c>evdev</c> by making a change to your kernel "
+"configuration. Read the <uri link=\"/doc/en/kernel-config.xml\">Kernel "
+"Configuration Guide</uri> if you don't know how to setup your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):113
+msgid "Enabling evdev in the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):113
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"  Input device support ---&gt;\n"
+"  &lt;*&gt;  Event interface\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):122
+msgid "Kernel modesetting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):125
+msgid ""
+"Modern open-source video drivers rely on kernel modesetting (KMS). KMS "
+"provides an improved graphical boot with less flickering, faster user "
+"switching, a built-in framebuffer console, seamless switching from the "
+"console to Xorg, and other features. KMS conflicts with legacy framebuffer "
+"drivers, which must remain <b>disabled</b> in your kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):133
+msgid ""
+"First, prepare your kernel for KMS. You need to do this step regardless of "
+"which Xorg video driver you're using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):138
+msgid "Configuring framebuffers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):138
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"  Graphics support ---&gt;\n"
+"    Support for frame buffer devices ---&gt;\n"
+"    <comment>(Disable all drivers, including VGA, Intel, nVidia, and ATI)</comment>\n"
+"\n"
+"    <comment>(Further down, enable basic console support. KMS uses this.)</comment>\n"
+"    Console display driver support ---&gt;\n"
+"      &lt;*&gt;  Framebuffer Console Support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):149
+msgid ""
+"Next, configure your kernel to use the proper KMS driver for your video "
+"card. Intel, nVidia, and ATI are the most common cards, so follow code "
+"listing for your card below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):155
+msgid "For Intel cards:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):159
+msgid "Intel settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):159
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+"  Graphics support ---&gt;\n"
+"    /dev/agpgart (AGP Support) ---&gt;\n"
+"    &lt;*&gt;  Intel 440LX/BX/GX, I8xx and E7x05 chipset support\n"
+"    Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---&gt;\n"
+"    &lt;*&gt;  Intel 830M, 845G, 852GM, 855GM, 865G (i915 driver)\n"
+"         i915 driver\n"
+"    [*]    Enable modesetting on intel by default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):170
+msgid "For nVidia cards:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):174
+msgid "nVidia settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):174
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Enable DRM)</comment>\n"
+"Device Drivers ---&gt;\n"
+"  Graphics support ---&gt;\n"
+"  &lt;*&gt;  Direct Rendering Manager ---&gt;\n"
+"\n"
+"<comment>(Nouveau is currently in the Staging drivers section)</comment>\n"
+"Device Drivers ---&gt;\n"
+"  Staging drivers ---&gt;\n"
+"  [ ]  Exclude Staging drivers from being built\n"
+"  &lt;*&gt;    Nouveau (nVidia) cards\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):187
+msgid ""
+"For newer ATI cards (<uri link=\"/doc/en/ati-faq.xml\">RadeonHD 2000 and up</"
+"uri>), you will need to emerge <c>radeon-ucode</c>. Once you have installed "
+"<c>radeon-ucode</c>, configure your kernel as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):193
+msgid "ATI settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):193
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Setup the kernel to use the radeon-ucode firmware)</comment>\n"
+"Device Drivers ---&gt;\n"
+"  Generic Driver Options ---&gt;\n"
+"  [*]  Include in-kernel firmware blobs in kernel binary\n"
+"  <comment># RadeonHD 2000, 3000, and 4000 series cards:</comment>\n"
+"  (radeon/R600_rlc.bin radeon/R700_rlc.bin) External firmware blobs\n"
+"  <comment># RadeonHD 5000, a.k.a Evergreen, and newer cards:</comment>\n"
+"  (radeon/CEDAR_me.bin radeon/CEDAR_pfp.bin radeon/CEDAR_rlc.bin\n"
+"   radeon/CYPRESS_me.bin radeon/CYPRESS_pfp.bin radeon/CYPRESS_rlc.bin\n"
+"   radeon/JUNIPER_me.bin radeon/JUNIPER_pfp.bin radeon/JUNIPER_rlc.bin\n"
+"   radeon/REDWOOD_me.bin radeon/REDWOOD_pfp.bin \n"
+"   radeon/REDWOOD_rlc.bin) External firmware blobs\n"
+"   (/lib/firmware/) Firmware blobs root directory\n"
+"\n"
+"<comment>(Enable Radeon KMS support)</comment>\n"
+"Device Drivers ---&gt;\n"
+"  Graphics support ---&gt;\n"
+"  &lt;*&gt;  Direct Rendering Manager ---&gt;\n"
+"  &lt;*&gt;    ATI Radeon\n"
+"  [*]      Enable modesetting on radeon by default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):216
+msgid ""
+"Old Radeon cards (X1900 series and older) don't need the <c>radeon-ucode</c> "
+"package or any firmware configuration. Just enable the Direct Rendering "
+"Manager and ATI Radeon modesetting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):222
+msgid ""
+"Now that you're done setting up KMS, continue with preparing <path>/etc/make."
+"conf</path> in the next section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):230
+msgid "make.conf configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):233
+msgid ""
+"Now that your kernel is prepared, you have to configure two important "
+"variables in the <path>/etc/make.conf</path> file before you can install "
+"Xorg."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):238
+msgid ""
+"The first variable is <c>VIDEO_CARDS</c>. This is used to set the video "
+"drivers that you intend to use and is usually based on the kind of video "
+"card you have. The most common settings are <c>nouveau</c> for nVidia cards "
+"or <c>radeon</c> for ATI cards. Both have actively developed, well-supported "
+"open-source drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):246
+msgid ""
+"You may also try the proprietary drivers from nVidia and ATI, <c>nvidia</c> "
+"and <c>fglrx</c> respectively. However, setting up the proprietary drivers "
+"is beyond the scope of this guide. Please read the <uri link=\"/doc/en/"
+"nvidia-guide.xml\">Gentoo Linux nVidia Guide</uri> and <uri link=\"/doc/en/"
+"ati-faq.xml\">Gentoo Linux ATI FAQ</uri>. If you don't know which drivers "
+"you should choose, refer to these guides for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):255
+msgid ""
+"The <c>intel</c> driver may be used for desktops or laptops with common "
+"Intel integrated graphics chipsets."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):260
+msgid ""
+"<c>VIDEO_CARDS</c> may contain more than one driver, each separated with a "
+"space."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):265
+msgid ""
+"The second variable is <c>INPUT_DEVICES</c> and is used to determine which "
+"drivers are to be built for input devices. In most cases setting it to "
+"<c>evdev</c> should work just fine. If you use alternative input devices, "
+"such as a Synaptics touchpad for a laptop, be sure to add it to "
+"<c>INPUT_DEVICES</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):273
+msgid ""
+"Now you should decide which drivers you will use and add necessary settings "
+"to the <path>/etc/make.conf</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):278
+msgid "Sample make.conf entries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):278
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(For mouse, keyboard, and Synaptics touchpad support)</comment>\n"
+"INPUT_DEVICES=\"evdev synaptics\"\n"
+"<comment>(For nVidia cards)</comment>\n"
+"VIDEO_CARDS=\"nouveau\"\n"
+"<comment>(OR, for ATI Radeon cards)</comment>\n"
+"VIDEO_CARDS=\"radeon\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):287
+msgid ""
+"If the suggested settings don't work for you, you should run <c>emerge -pv "
+"xorg-drivers</c>, check all the options available and choose those which "
+"apply to your system. This example is for a system with a keyboard, mouse, "
+"Synaptics touchpad, and a Radeon video card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):294
+msgid "Displaying all the driver options available"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):294
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -pv xorg-drivers</i>\n"
+"\n"
+"These are the packages that would be merged, in order:\n"
+"\n"
+"Calculating dependencies... done!\n"
+"[ebuild   R   ]  x11-base/xorg-drivers-1.8  INPUT_DEVICES=\"evdev synaptics\n"
+"-acecad -aiptek -elographics% -fpit% -joystick -keyboard -mouse -penmount -tslib\n"
+"-virtualbox -vmmouse -void -wacom\"\n"
+"VIDEO_CARDS=\"radeon -apm -ark -ast -chips -cirrus -dummy -epson -fbdev -fglrx\n"
+"(-geode) -glint -i128 (-i740) (-impact) -intel -mach64 -mga -neomagic (-newport)\n"
+"-nouveau -nv -nvidia -r128 -radeonhd -rendition -s3 -s3virge -savage\n"
+"-siliconmotion -sis -sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb)\n"
+"(-sunleo) (-suntcx) -tdfx -tga -trident -tseng -v4l -vesa -via -virtualbox\n"
+"-vmware (-voodoo) (-xgi)\" 0 kB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):311
+msgid ""
+"After setting all the necessary variables you can install the Xorg package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):315
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge xorg-server</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):319
+msgid ""
+"You could install the <c>xorg-x11</c> metapackage instead of the more "
+"lightweight <c>xorg-server</c>. Functionally, <c>xorg-x11</c> and <c>xorg-"
+"server</c> are the same. However, <c>xorg-x11</c> brings in many more "
+"packages that you probably don't need, such as a huge assortment of fonts in "
+"many different languages. They're not necessary for a working desktop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):327
+msgid ""
+"When the installation is finished, you will need to re-initialise some "
+"environment variables before you continue. Just run <c>env-update</c> "
+"followed by <c>source /etc/profile</c> and you're all set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):333
+msgid "Re-initialising the environment variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):333
+#, no-wrap
+msgid ""
+"\n"
+"# <i>env-update</i>\n"
+"# <i>source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):338
+msgid ""
+"Now it's time to start the Hardware Abstraction Layer (HAL) daemon and set "
+"it to automatically start each time you boot. This is necessary to get a "
+"working X environment, otherwise your input devices won't be detected and "
+"you'll probably just get a blank screen. We'll cover HAL more in the <uri "
+"link=\"#using_hal\">next section</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):346
+msgid "Starting HAL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):346
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/hald start</i>\n"
+"# <i>rc-update add hald default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):356
+msgid "Configuring Xorg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):358
+msgid "Using HAL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):361
+msgid ""
+"The X server is designed to work out-of-the-box, with no need to manually "
+"edit Xorg's configuration files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):366
+msgid ""
+"You should first try <uri link=\"#using_startx\">starting X</uri> without "
+"creating <path>/etc/X11/xorg.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):371
+msgid ""
+"If Xorg won't start (if there's something wrong with the screen, or with "
+"your keyboard/mouse), then you can try fixing problems by using the right "
+"configuration files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):377
+msgid ""
+"By default, Xorg uses HAL (Hardware Abstraction Layer) to detect and "
+"configure devices such as keyboards and mice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):382
+msgid ""
+"HAL comes with many premade device rules, also called policies. These policy "
+"files are available in <path>/usr/share/hal/fdi/policy/</path>. Just find a "
+"few that suit your needs most closely and copy them to <path>/etc/hal/fdi/"
+"policy/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(impo):389
+msgid ""
+"Do not edit the files in <path>/usr/share/hal/fdi/</path>! Just copy the "
+"ones you need, and edit them once they're placed in the proper <path>/etc</"
+"path> location."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):395
+msgid ""
+"For example, to get a basic working keyboard/mouse combination, you could "
+"copy the following files to <path>/etc/hal/fdi/policy/</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):400
+msgid "Using HAL policy files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):400
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp /usr/share/hal/fdi/policy/10osvendor/10-input-policy.fdi /etc/hal/fdi/policy</i>\n"
+"# <i>cp /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi /etc/hal/fdi/policy</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):405
+msgid ""
+"There are several other HAL policies in <path>/usr/share/hal/fdi/</path> "
+"that may interest you, such as laptop configurations, storage device "
+"handling, power management, and more. Just copy any of the policies to "
+"<path>/etc/hal/fdi/policy/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(impo):412
+msgid ""
+"Remember, <e>every</e> time you finish making changes to HAL policy files, "
+"you need to restart the HAL daemon by running <c>/etc/init.d/hald restart</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):417
+msgid ""
+"You can edit the policy files in <path>/etc/hal/fdi/policy</path> to your "
+"liking. You may want to make a few tweaks or to expose additional "
+"functionality. Let's go through an example of tweaking a HAL policy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):423
+msgid ""
+"One very convenient trick is to kill the X server entirely by pressing Ctrl-"
+"Alt-Backspace. This is useful when your X server is malfunctioning, frozen, "
+"etc. It's not as extreme as rebooting the whole machine with Ctrl-Alt-Del."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):429
+msgid ""
+"Recent X server versions disabled this key combination by default. However, "
+"you can reenable it by copying <path>10-x11-input.fdi</path> to <path>/etc/"
+"hal/fdi/policy</path> and editing it. You'll need to add just one line to "
+"the appropriate section, as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):436
+msgid "Editing 10-x11-input.fdi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):436
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Open the file in your preferred editor)</comment>\n"
+"# <i>nano -w /etc/hal/fdi/policy/10-x11-input.fdi</i>\n"
+"<comment>(Find the \"input.keys\" section)</comment>\n"
+"&lt;match key=\"info.capabilities\" contains=\"input.keys\"&gt;\n"
+"<comment>(Add the \"terminate\" merge string as shown)</comment>\n"
+"&lt;match key=\"info.capabilities\" contains=\"input.keys\"&gt;\n"
+"      &lt;merge key=\"input.x11_driver\" type=\"string\"&gt;keyboard&lt;/merge&gt;\n"
+"      <i>&lt;merge key=\"input.xkb.options\" type=\"string\"&gt;terminate:ctrl_alt_bksp&lt;/merge&gt;</i>\n"
+"      &lt;match key=\"/org/freedesktop/Hal/devices/computer:system.kernel.name\"\n"
+"             string=\"Linux\"&gt;\n"
+"        &lt;merge key=\"input.x11_driver\" type=\"string\"&gt;evdev&lt;merge&gt;\n"
+"      &lt;/match&gt;\n"
+"    &lt;/match&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):452
+msgid ""
+"Once you're done, run <c>/etc/init.d/hald restart</c> so that HAL picks up "
+"your changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):457
+msgid ""
+"There, now you have a handy way of killing an unresponsive X server. This is "
+"useful when programs have frozen your display entirely, or when configuring "
+"and tweaking your Xorg environment. Be careful when killing your desktop "
+"with this key combination -- most programs really don't like it when you end "
+"them this way, and you may lose some (or all) of what you were working on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):465
+msgid ""
+"Hopefully just working with the HAL policy files results in a working X "
+"desktop. If Xorg still won't start, or there's some other problem, then "
+"you'll need to manually configure <path>xorg.conf</path> as shown in the "
+"next section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):474
+msgid "The xorg.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):477
+msgid ""
+"Configuring <path>xorg.conf</path> should be seen as a \"last resort\" "
+"option. It really desirable to run without one if possible, and to do all "
+"your configuration via HAL policy files. If you still can't get a working "
+"configuration, then read on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):484
+msgid ""
+"The configuration file of Xorg is called <path>xorg.conf</path> and it "
+"resides in <path>/etc/X11</path>. Xorg provides an example configuration as "
+"<path>/etc/X11/xorg.conf.example</path> which you can use to create your own "
+"configuration. It is heavily commented, but if you are in need of more "
+"documentation regarding the syntax, don't hesitate to read the man page:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):492
+msgid "Reading the xorg.conf man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):492
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>man 5 xorg.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):499
+msgid "Automatic Generation of xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):502
+msgid ""
+"Xorg itself is able to guess most parameters for you. In most cases, you "
+"will only have to change some lines to get the resolution you want up and "
+"running. If you are interested in more in-depth tweaking, be sure to check "
+"the resources at the end of this chapter. But first, let us generate a "
+"(hopefully working) Xorg configuration file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):510
+msgid "Generating an xorg.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):510
+#, no-wrap
+msgid ""
+"\n"
+"# <i>Xorg -configure</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):514
+msgid ""
+"Be sure to read the last lines printed on your screen when Xorg has finished "
+"probing your hardware. If it tells you it failed at some point, you're "
+"forced to manually write an <path>xorg.conf</path> file. Assuming that it "
+"didn't fail, it will have told you that it has written <path>/root/xorg.conf."
+"new</path> ready for you to test. So let's test. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):522
+msgid "Testing the xorg.conf.new file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):522
+#, no-wrap
+msgid ""
+"\n"
+"# <i>X -retro -config /root/xorg.conf.new</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):526
+msgid ""
+"If all goes well, you should see a simple black and white pattern. Verify if "
+"your mouse works correctly and if the resolution is good. You might not be "
+"able to deduce the exact resolution, but you should be able to see if it's "
+"too low. You can exit any time by pressing Ctrl-Alt-Backspace."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):536
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):545
+msgid "Copying over xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):539
+msgid ""
+"Let us copy over the <path>xorg.conf.new</path> to <path>/etc/X11/xorg.conf</"
+"path> now, so we won't have to continuously run <c>X -config</c> -- typing "
+"just <c>startx</c> is easier. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):545
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp /root/xorg.conf.new /etc/X11/xorg.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):552
+msgid "Using startx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):555
+msgid ""
+"Now try <c>startx</c> to start up your X server. <c>startx</c> is a script "
+"that executes an <e>X session</e>, that is, it starts the X server and some "
+"graphical applications on top of it. It decides which applications to run "
+"using the following logic:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(li):563
+msgid ""
+"If a file named <path>.xinitrc</path> exists in the home directory, it will "
+"execute the commands listed there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(li):567
+msgid ""
+"Otherwise, it will read the value of the XSESSION variable and will execute "
+"one of the sessions available in <path>/etc/X11/Sessions/</path> "
+"accordingly. You can set the value of XSESSION in <path>/etc/env."
+"d/90xsession</path> to make it a default for all the users on the system. "
+"For example, as root, run <c>echo XSESSION=\"Xfce4\" &gt; /etc/env."
+"d/90xsession</c>. This will create the <path>90xsession</path> file and set "
+"the default X session to <uri link=\"/doc/en/xfce-config.xml\">Xfce</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):579
+msgid "Starting X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):579
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>startx</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):583
+msgid ""
+"You can kill the X session by using the Ctrl-Alt-Backspace key combination. "
+"This will, however, make X exit disgracefully -- something that you might "
+"not always want."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):589
+msgid ""
+"If you haven't yet installed a window manager, all you'll see is a black "
+"screen. Since this can also be a sign that something's wrong, you may want "
+"to emerge <c>twm</c> and <c>xterm</c><e>only to test X</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):595
+msgid ""
+"Once those two programs are installed, run <c>startx</c> again. A few xterm "
+"windows should appear, making it easier to verify that X is working "
+"correctly. Once you're satisfied with the results, run <c>emerge --unmerge "
+"twm xterm</c> as root to get rid of the testing packages. You won't need "
+"them once you've setup a proper desktop environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):608
+msgid "Tweaking X settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):610
+msgid "Setting your Resolution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):613
+msgid ""
+"If you feel that the screen resolution is wrong, you will need to check two "
+"sections in your <path>xorg.conf</path> configuration. First of all, you "
+"have the <e>Screen</e> section which lists the resolutions, if any that your "
+"X server will run at. By default, this section might not list any "
+"resolutions at all. If this is the case, Xorg will estimate the resolutions "
+"based on the information in the second section, <e>Monitor</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):622
+msgid ""
+"What happens is that Xorg checks the settings of <c>HorizSync</c> and "
+"<c>VertRefresh</c> in the <e>Monitor</e> section to compute valid "
+"resolutions. For now, leave these settings as-is. Only when the changes to "
+"the <e>Screen</e> section (which we will describe in a minute) don't work, "
+"then you will need to look up the specs for your monitor and fill in the "
+"correct values."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(warn):630
+msgid ""
+"Do <b>not</b> \"just\" change the values of these two monitor related "
+"variables without consulting the technical specifications of your monitor. "
+"Setting incorrect values lead to out-of-sync errors at best and smoked up "
+"screens at worst."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):637
+msgid ""
+"Now let us change the resolution. In the next example from <path>/etc/X11/"
+"xorg.conf</path> we add the <c>PreferredMode</c> line so that our X server "
+"starts at 1440x900 by default. Don't mind the given strings -- they are "
+"examples and will most likely differ from the settings on your system. "
+"However, the <c>Option</c> in the <c>Device</c> section must match the name "
+"of your monitor (<c>DVI-0</c>), which can be obtained by running <c>xrandr</"
+"c>. You'll need to <c>emerge xrandr</c> just long enough to get this "
+"information. The argument after the monitor name (in the <c>Device</c> "
+"section) must match the <c>Identifier</c> in the <c>Monitor</c> section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):649
+msgid "Changing the Monitor section in /etc/X11/xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):649
+#, no-wrap
+msgid ""
+"\n"
+"Section \"Device\"\n"
+"  Identifier  \"RadeonHD 4550\"\n"
+"  Option      \"Monitor-DVI-0\" \"DVI screen\"\n"
+"EndSection\n"
+"Section \"Monitor\"\n"
+"  Identifier  \"DVI screen\"\n"
+"  Option      \"PreferredMode\" \"1440x900\"\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):660
+msgid "Run X (<c>startx</c>) to discover it uses the resolution you want."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):667
+msgid "Multiple monitors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):670
+msgid ""
+"You can configure more than one monitor in <path>/etc/X11/xorg.conf</path>. "
+"All you have to do is give each monitor an identifer, then list its physical "
+"position, such as \"RightOf\" or \"Above\" another monitor. The following "
+"example shows how to configure a DVI and a VGA monitor, with the VGA monitor "
+"as the right-hand screen:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):678
+msgid "Configuring multiple monitors in xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):678
+#, no-wrap
+msgid ""
+"\n"
+"Section \"Device\"\n"
+"  Identifier \"RadeonHD 4550\"\n"
+"  Option     \"Monitor-DVI-0\" \"DVI screen\"\n"
+"  Option     \"Monitor-VGA-0\" \"VGA screen\"\n"
+"EndSection\n"
+"\n"
+"Section \"Monitor\"\n"
+"  Identifier \"DVI screen\"\n"
+"EndSection\n"
+"\n"
+"Section \"Monitor\"\n"
+"  Identifier \"VGA screen\"\n"
+"  Option     \"RightOf\" \"DVI screen\"\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):698
+msgid "Configuring your keyboard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):701
+msgid ""
+"To setup X to use an international keyboard, you can copy the content of "
+"<path>/usr/share/doc/hal-*/*/use-estonian-layout.fdi.bz2</path> to <path>/"
+"etc/hal/fdi/policy/10-xinput-configuration.fdi</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):707
+msgid "Using an existing config file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):707
+#, no-wrap
+msgid ""
+"\n"
+"# <i>bzcat /usr/share/doc/hal-*/*/use-estonian-layout.fdi.bz2 &gt; /etc/hal/fdi/policy/10-xinput-configuration.fdi</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):711
+msgid ""
+"Now you can just edit <path>10-xinput-configuration.fdi</path> and change "
+"the Estonian keyboard layout (<c>ee</c>) to your own, such as Great Britain "
+"(<b>gb</b>) or Polish (<b>pl</b>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):717
+msgid ""
+"When you're finished, run <c>/etc/init.d/hald restart</c> as root to make "
+"sure that HAL picks up your configuration file changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):725
+msgid "Finishing up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):728
+msgid ""
+"Run <c>startx</c> and be happy about the result. Congratulations, you now "
+"(hopefully) have a working Xorg on your system. The next step is to install "
+"a useful window manager or desktop environment such as KDE, GNOME, or Xfce, "
+"but that's not part of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):740
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):742
+msgid "Creating and Tweaking xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):745
+msgid ""
+"First of all, <c>man xorg.conf</c> and <c>man evdev</c> provide quick yet "
+"complete references about the syntax used by these configuration files. Be "
+"sure to have them open on a terminal near you when you edit your "
+"configuration files!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):752
+msgid ""
+"Also, be sure to look at <path>/etc/X11/xorg.conf.example</path>; you may "
+"wish to copy this and use it as a foundation for writing your own <path>xorg."
+"conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):758
+msgid ""
+"You may find the X.org <uri link=\"http://www.x.org/wiki/FAQ\">FAQ</uri> "
+"provided on their website, in addition to their other documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):763
+msgid ""
+"There are also many online resources on editing <path>xorg.conf</path>. We "
+"only list few of them here, be sure to <uri link=\"http://www.google.com"
+"\">Google</uri> for more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):772
+msgid "Other resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):775
+msgid ""
+"More information about installing and configuring various graphical desktop "
+"environments and applications can be found in the <uri link=\"/doc/en/?"
+"catid=desktop\">Gentoo Desktop Documentation Resources</uri> section of our "
+"documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):782
+msgid ""
+"If you're upgrading to <c>xorg-server</c> 1.8 from an earlier version, then "
+"be sure to read the <uri link=\"/proj/en/desktop/x/x11/xorg-server-1.8-"
+"upgrade-guide.xml\">migration guide</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/ru/zsh.xml.po b/doc/gettext/ru/zsh.xml.po
new file mode 100644
index 0000000..945ba10
--- /dev/null
+++ b/doc/gettext/ru/zsh.xml.po
@@ -0,0 +1,659 @@
+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:46+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: ru\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
+"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(guide:link):5
+msgid "/doc/en/zsh.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):6
+msgid "zsh Configuration and Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail:link):9
+msgid "hekonsek@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail):9
+msgid "Henryk Konsek"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail:link):12
+msgid "morritt.andrew@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail):12
+msgid "Andrew Morritt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail:link):15
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail):15
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail:link):18
+msgid "welp@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail):18
+msgid "Peter Weller"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(abstract):21
+msgid ""
+"This guide shows how to install and configure zsh quickly. After reading "
+"this document you will be able use many zsh features such as advanced tab-"
+"completion, command correction and prompt management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(version):31
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(date):32
+msgid "2006-10-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):35
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):37
+msgid "Installing zsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):40
+msgid ""
+"To install <c>zsh</c> under Gentoo, we need to emerge the <c>app-shells/zsh</"
+"c> (zsh itself) and <c>app-shells/zsh-completion</c> (zsh completion "
+"scripts) packages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):46
+msgid "Emerging zsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):46
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge zsh zsh-completion</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):53
+msgid "Entering zsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):56
+msgid ""
+"When you start <c>zsh</c> for the first time, you get the following message. "
+"You can skip this menu as we will create an init file later in this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):61
+msgid "Skipping the initial config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):61
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>zsh</i>\n"
+"This is the Z Shell configuration function for new users, zsh-newuser-install.\n"
+"You are seeing this message because you have no zsh startup files\n"
+"(the files .zshenv, .zprofile, .zshrc, .zlogin in the directory\n"
+"~).  This function can help you with a few settings that should\n"
+"make your use of the shell easier.\n"
+"\n"
+"You can:\n"
+"\n"
+"(q)  Quit and do nothing.  The function will be run again next time.\n"
+"\n"
+"(0)  Exit, creating the file ~/.zshrc containing just a comment.\n"
+"     That will prevent this function being run again.\n"
+"\n"
+"(1)  Continue to the main menu.\n"
+"\n"
+"--- Type one of the keys in parentheses --- <i>q</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):86
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):88
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):91
+msgid ""
+"To start zsh for a single session, run <c>zsh</c>. For a more permanent "
+"solution, please refer to the chapter on <uri link=\"#savingsettings"
+"\">Saving settings</uri>. After the installation, <c>zsh</c> seems to be "
+"very simple and rather limited in the area of functionality. To change this, "
+"several configuration changes need to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):102
+msgid "Advanced Tab-completion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):105
+msgid ""
+"To enable the famous <c>zsh</c> tab-completion system, you need to run the "
+"following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):110
+msgid "Enabling completion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):110
+#, no-wrap
+msgid ""
+"\n"
+"% <i>autoload -U compinit</i>\n"
+"% <i>compinit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):115
+msgid ""
+"Default completion style is quite plain and ugly. If you want to improve its "
+"appearance, enter the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):120
+msgid "Completion style improvements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):120
+#, no-wrap
+msgid ""
+"\n"
+"% <i>zstyle ':completion:*:descriptions' format '%U%B%d%b%u'</i>\n"
+"% <i>zstyle ':completion:*:warnings' format '%BSorry, no matches for: %d%b'</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):128
+msgid "Command correction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):131
+msgid ""
+"It is also a good idea to enable the auto-correction of the commands typed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):135
+msgid "Enabling correction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):135
+#, no-wrap
+msgid ""
+"\n"
+"% <i>setopt correctall</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):142
+msgid "Prompts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):145
+msgid ""
+"The prompt may seem quite boring however, but we can fix it easily in "
+"several steps. First, we need to initialize advanced prompt support:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):150
+msgid "Enabling advanced prompts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):150
+#, no-wrap
+msgid ""
+"\n"
+"% <i>autoload -U promptinit</i>\n"
+"% <i>promptinit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):155
+msgid ""
+"Available prompts samples may be printed via the <c>prompt -p</c> command. "
+"Now we can activate our favorite one:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):160
+msgid "Choosing a sample prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):160
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace gentoo with the prompt of your choice)</comment>\n"
+"% <i>prompt gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(note):165
+msgid ""
+"If you're playing around with the different prompts, and you don't want to "
+"see a sample of every one, you can use <c>prompt -l</c> to list the prompts "
+"available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):171
+msgid ""
+"Another option is to create your own prompt. To do this you will need to set "
+"the PS1 environment variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):176
+msgid "A simple custom prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):176
+#, no-wrap
+msgid ""
+"\n"
+"% <i>export PS1=\"[Test Prompt] &gt; \"</i>\n"
+"[Test Prompt] &gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):181
+msgid ""
+"While it is good to be able to create a custom text prompt, zsh also "
+"provides many escape sequences that allow system information to be inserted "
+"into the prompt. Some of the escape sequences available are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(th):189
+msgid "Sequence"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(th):190
+msgid "Printed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):193
+msgid "%T"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):194
+msgid "System time (HH:MM)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):197
+msgid "%*"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):198
+msgid "System time (HH:MM:SS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):201
+msgid "%D"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):202
+msgid "System date (YY-MM-DD)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):205
+msgid "%n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):206
+msgid "Your username"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):209
+msgid "%B - %b"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):210
+msgid "Begin - end bold print"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):213
+msgid "%U - %u"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):214
+msgid "Begin - end underlining"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):217
+msgid "%d"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):218
+msgid "Your current working directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):221
+msgid "%~"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):222
+msgid "Your current working directory, relative to ~"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):225
+msgid "%M"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):226
+msgid "The computer's hostname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):229
+msgid "%m"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):230
+msgid "The computer's hostname (truncated before the first period)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):233
+msgid "%l"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):234
+msgid "Your current tty"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):238
+msgid ""
+"These escape sequences may simply be inserted into the environment variable, "
+"PS1, and zsh will parse them automatically."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):243
+msgid "A more complex prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):243
+#, no-wrap
+msgid ""
+"\n"
+"% <i>export PS1=\"[%* - %D] %d %% \"</i>\n"
+"[08:44:23 - 06-02-18] /home/username %\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):251
+msgid "History"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):254
+msgid ""
+"Unfortunately, the default zsh configuration in Gentoo does not include "
+"command history support. As working with a shell without history is very "
+"frustrating, we should enter the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):260
+msgid "Basic history configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):260
+#, no-wrap
+msgid ""
+"\n"
+"% <i>export HISTSIZE=2000</i>\n"
+"% <i>export HISTFILE=\"$HOME/.history\"</i>\n"
+"\n"
+"<comment>(History won't be saved without the following command)</comment>\n"
+"% <i>export SAVEHIST=$HISTSIZE</i>\n"
+msgstr ""
+
+#. does not work
+#. <p>
+#. It is very comfortable to search commands in history using the up/down arrow
+#. keys, especially after typing the few first letters of the desired command.
+#. </p>
+#.
+#. <p>
+#. To enable this feature, enter the following commands:
+#. </p>
+#.
+#. <pre caption="Setting context searching">
+#. % <i>bindkey `tput kcuu1` history-beginning-search-backward >/dev/null 2>&amp;1</i>
+#. % <i>bindkey `tput kcud1` history-beginning-search-forward >/dev/null 2>&amp;1 </i>
+#. </pre>
+#.
+#. <p>
+#. To try the above feature, try the following commands:
+#. </p>
+#.
+#. TODO: use commands that *are* in the history, i.e. commands from above samples
+#.
+#. <pre caption="History searching based on the first letters of the commands">
+#. <comment>(Do not press Enter after typing)</comment>
+#. % <i>vim /etc/</i>
+#. <comment>(Now press up arrow key)</comment>
+#. % <i>vim /etc/fstab</i>
+#. <comment>(Press up arrow key once again)</comment>
+#. % <i>vim /etc/X11/xorg.conf</i>
+#. </pre>
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):299
+msgid ""
+"To prevent history from recording duplicated entries (such as <c>ls -l</c> "
+"entered many times during single shell session), you can set the "
+"<c>hist_ignore_all_dups</c> option:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):305
+msgid "Setting ignoring of duplicates"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):305
+#, no-wrap
+msgid ""
+"\n"
+"% <i>setopt hist_ignore_all_dups</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):309
+msgid ""
+"A useful trick to prevent particular entries from being recorded into a "
+"history by preceding them with at least one space."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):314
+msgid "Preventing particular entry from being recorded"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):314
+#, no-wrap
+msgid ""
+"\n"
+"% <i>setopt hist_ignore_space</i>\n"
+"\n"
+"<comment>(This command won't be recorded. Note the extra space before it.)</comment>\n"
+"% <i> cat /proc/cpuinfo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):324
+msgid "Miscellaneous settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):327
+msgid ""
+"You can set the <c>autocd</c> option if you want to avoid tedious typing of "
+"<c>cd</c> command while changing current directory (for example <c>/etc</c> "
+"instead of <c>cd /etc</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):333
+msgid "Setting autocd option"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):333
+#, no-wrap
+msgid ""
+"\n"
+"% <i>setopt autocd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):337
+msgid ""
+"If standard bash-like globbing does not satisfy you, <c>extendedglob</c> "
+"option may be set to enable extended globbing (one similar to regular "
+"expressions)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):343
+msgid "Setting extended globbing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):343
+#, no-wrap
+msgid ""
+"\n"
+"% <i>setopt extendedglob</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):347
+msgid ""
+"When option above is set, you are able to use extended globbing queries such "
+"as <c>cp ^*.(tar|bz2|gz)</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):357
+msgid "Saving settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):359
+msgid "Saving zsh settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):362
+msgid ""
+"Once we have customized <c>zsh</c> the way we like it, it is a good idea to "
+"save these options as the <c>zsh</c> defaults for the system. One possible "
+"way to achieve this is to write our settings in the <path>/etc/zsh/zshrc</"
+"path> script. Alternatively, we could make them the defaults for our account "
+"only be editing <path>~/.zshrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):370
+msgid "An example zshrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):370
+#, no-wrap
+msgid ""
+"\n"
+"#!/bin/zsh\n"
+"\n"
+"# completion\n"
+"autoload -U compinit\n"
+"compinit\n"
+"\n"
+"# correction\n"
+"setopt correctall\n"
+"\n"
+"# prompt\n"
+"autoload -U promptinit\n"
+"promptinit\n"
+"prompt gentoo\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):391
+msgid "Making zsh default shell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):393
+msgid "Option for users with root privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):396
+msgid "We can change shell for given user with <c>usermod</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):400
+msgid "Switching to zsh permanently using usermod"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):400
+#, no-wrap
+msgid ""
+"\n"
+"# <i>usermod -s /bin/zsh userlogin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):407
+msgid "Alternative for non-root users"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):410
+msgid ""
+"If your system administrator (despite gentle requests, that is) refuses to "
+"set the shell to zsh for you, you can set <c>bash</c> to execute <c>zsh</c> "
+"on startup, all you need to do is make a slight modification to your "
+"<path>~/.bashrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):417
+msgid "Sample ~/.bashrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):417
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Add the following to your ~/.bashrc)</comment>\n"
+"exec zsh\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):422
+msgid ""
+"Another method of changing shells is to use the <c>chsh</c> command (a "
+"utility used to change a user's login shell). A normal user may only change "
+"the login shell for his own account. As root, you can change the login shell "
+"of any user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):428
+msgid "Switching to zsh permanently using chsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):428
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace \"username\" with your own username)</comment>\n"
+"$ <i>chsh -s /bin/zsh username</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/shoutcast-config.xml.pot b/doc/gettext/shoutcast-config.xml.pot
new file mode 100644
index 0000000..f7e8517
--- /dev/null
+++ b/doc/gettext/shoutcast-config.xml.pot
@@ -0,0 +1,902 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):5
+msgid "Streaming Radio With SHOUTcast"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(mail:link):8
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(mail):8
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(author:title):10
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(mail:link):11
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(mail):11
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(abstract):14
+msgid "This guide will walk through the steps needed to setup a streaming radio server with SHOUTcast Server and SHOUTcast Trans."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(version):23
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(date):24
+msgid "2006-11-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):27
+msgid "Setting up SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):29
+msgid "Installing the files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):32
+msgid "The SHOUTcast Server can be found in media-sound/SHOUTcast-server-bin. You can install it with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):37
+msgid "Emerging SHOUTcast"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):37
+#, no-wrap
+msgid "\n# <i>emerge shoutcast-server-bin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):41
+msgid "The SHOUTcast Server will now be installed. The next step is configuring your new SHOUTcast Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):49
+msgid "Configuring SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):52
+msgid "Now that SHOUTcast Server is installed, it must be configured. The configuration file can be found in <path>/etc/shoutcast/sc_serv.conf</path>. Let's begin with the configuration. Make sure you are root, and open the configuration file with your favorite editor. I choose vi for this example. Now I'll bring up the file with vi:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):60
+msgid "Opening the configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):60
+#, no-wrap
+msgid "\n# <i>vi /etc/shoutcast/sc_serv.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):64
+msgid "This will bring up the SHOUTcast Server configuration file for viewing. From there you will see the configuration file and the different options that you can set. Let's take a look on how to setup these particular options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):73
+msgid "Mandatory Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):76
+msgid "Setting the user limit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):76
+#, no-wrap
+msgid "\n<comment>; MaxUser.  The maximum number of simultaneous listeners allowed.\n; Compute a reasonable value for your available upstream bandwidth (i.e. if\n; you have 256kbps upload DSL, and want to broadcast at 24kbps, you would\n; choose 256kbps/24kbps=10 maximum listeners.)  Setting this value higher\n; only wastes RAM and screws up your broadcast when more people connect\n; than you can support.</comment>\nMaxUser=10\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):86
+msgid "This is where the maximum number of users is set. As the caption states, it is foolish to setup 100 users on a 256kbps upload (This is what I have set, as my upload is about that). If you're running SHOUTcast Server to serve a LAN, you can probably set this MUCH higher (to the 100 mentioned easily). Please remember to not abuse whatever bandwidth you are using though. Bandwidth comes at quite a high price to ISPs and some will cut your account, fine you high costs to makeup, or both."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):96
+msgid "Setting the password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):96
+#, no-wrap
+msgid "\n<comment>; Password.  While SHOUTcast never asks a listener for a password, a\n; password is required to broadcast through the server, and to perform\n; administration via the web interface to this server.  This server should\n; consist of only letters and numbers, and is the same server your broadcaster\n; will need to enter in the SHOUTcast Source Plug-in for Winamp.  THIS VALUE\n; CANNOT BE BLANK.</comment>\nPassword=a_hard_to_crack_password\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):106
+msgid "Here is where you setup the password. The password itself is clear text. For security purposes, I STRONGLY recommend that you don't use passwords that are used to access critical system components or other sensitive information. Make this as random as possible, with a combination of letters and numbers. This password will be what SHOUTcast Trans (or any other content provider) will use to connect and provide streaming content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):115
+msgid "Setting up your listening port"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):115
+#, no-wrap
+msgid "\n<comment>; PortBase. This is the port number your server will run on.  The\n; value, and the value + 1 must be available.  If you get a fatal error when\n; the DNAS is setting up a socket on startup, make sure nothing else on the\n; machine is running on the same port (telnet localhost port number -- if you\n; get connection refused then you're clear to use that port).  Ports less than 1024\n; may require root privileges on *nix machines.  The default port is 8000.</comment>\nPortBase=8000\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):125
+msgid "This value sets up what port users will connect to on your SHOUTcast Server. The default is 8000, as it is what most mp3 server capable programs will default to (Audacious, winamp, etc.). As it states, if you wish to use a port less than 1024, you will need to be root. However, I strongly urge against using any port lower than 1024 for your SHOUTcast Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):133
+msgid "Setting up logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):133
+#, no-wrap
+msgid "\n<comment>; LogFile: file to use for logging. Can be '/dev/null' or 'none'\n; or empty to turn off logging. The default is ./sc_serv.log\n; on *nix systems or sc_serv_dir\\sc_serv.log on win32.\n; Note: on win32 systems if no path is specified the location is\n; in the same directory as the executable, on *nix systems it is in the\n; current directory.</comment>\nLogFile=/var/log/SHOUTcast.log\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):143
+msgid "This sets the location of the SHOUTcast server log file. The ebuild has it set to /dev/null, so you will need to change it in order to get a real log. I have it setup in the basic /var/log location. You can have it log to wherever you need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):150
+msgid "Enabling real time stats"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):150
+#, no-wrap
+msgid "\n<comment>; RealTime displays a status line that is updated every second\n; with the latest information on the current stream (*nix and win32\n; console systems only)</comment>\nRealTime=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):157
+msgid "This displays information on the current song to stdout every second. This is disabled by the ebuild so that the SHOUTcast daemon can run as silently as possible. Set this to 1 if you want these updates each second. However, I recommend you use the status page instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):164
+msgid "Enabling real time logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):164
+#, no-wrap
+msgid "\n<comment>; ScreenLog controls whether logging is printed to the screen or not\n; on *nix and win32 console systems. It is useful to disable this when\n; running servers in background without their own terminals. Default is 1</comment>\nScreenLog=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):171
+msgid "This is disabled by default in the ebuild to make the daemon run as silently as possible. This will log any events (connects, disconnects, etc) to stdout as they happen in real time. However, because the log file does the same thing, I recommend using it instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):178
+msgid "Setting the last number of songs displayed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):178
+#, no-wrap
+msgid "\n<comment>; ShowLastSongs specifies how many songs to list in the /played.html\n; page.  The default is 10.  Acceptable entries are 1 to 20.</comment>\nShowLastSongs=10\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):184
+msgid "Just as it states, this value will set how many of the most recently played /played.html will display. If you put more than 20, you should probably consider more coffee."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):190
+msgid "Setting up filesystem modification logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):198
+msgid "This setting enables or disables logging for directory modifications by the DNAS (Distributed Network Audio Server), or SHOUTcast for short. Recommended for those who wish to have the most secure logging possible. Basic home/casual users probably don't need this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):205
+msgid "Enabling http request logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):217
+msgid "This specifies whether or not you want to log hits to the HTTP server that SHOUTcast provides. Once again, recommended for those who wish the most secure logging possible, but not recommended for home/casual users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):223
+msgid "Enabling W3C Logging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):223
+#, no-wrap
+msgid "\n<comment>; W3CEnable turns on W3C Logging.  W3C logs contain httpd-like accounts\n; of every track played for every listener, including byte counts those listeners\n; took.  This data can be parsed with tools like Analog and WebTrends, or given\n; to third parties like Arbitron and Measurecast for their reporting systems.\n; Default is Yes (enabled).</comment>\nW3CEnable=Yes\n\n<comment>; W3CLog describes the name of the log file for W3C logging.  Default log file is\n; sc_w3c.log, in the same directory wherever the DNAS gets started from.</comment>\nW3CLog=/dev/null\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):236
+msgid "The first option enables W3C logging. This type of logging can be easily parsed by the programs listed. This is highly recommended for those who wish to have the most in depth statistics possible. The second option specifies where to store the W3C log. This is set to /dev/null by the ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):246
+msgid "Network Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):249
+msgid "Setting the source IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):249
+#, no-wrap
+msgid "\n<comment>; SrcIP, the interface to listen for source connections on (or to make relay\n; connections on if relaying). Can and usually will be ANY or 127.0.0.1\n; (Making it 127.0.0.1 will keep other machines from being able to\n; broadcast using your SHOUTcast Server )</comment>\nSrcIP=ANY\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):257
+msgid "The SrcIP variable sets what IP streaming content is coming from. This can be another server (relaying), localhost (regular), or any other IP that your interface supports. Setting to localhost prevents any other server from using your SHOUTcast Server as a broadcast source. The default is ANY and will cause your SHOUTcast Server to source from any IP. Security wise, it is better to set this to something specific."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):266
+msgid "Setting the destination IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):266
+#, no-wrap
+msgid "\n<comment>; DestIP, IP to listen for clients on (and to contact yp.SHOUTcast.com)\n; can and usually will be be ANY. If your machine has multiple IP addresses,\n; set this to the one you want it to be accessed by.</comment>\nDestIP=ANY\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):273
+msgid "This determines which IP on your interface you will allow users to connect to. This can be localhost (if you're anti-social and wish only to stream to yourself), a private IP (for instance, 192.168.0.101, for hosting to a local network), or your external IP (for instance, 209.204.249.201, for streaming to a WAN, but not a LAN). In most cases, you can reach your own stream by using 127.0.0.1 instead of what is listed here. ANY lets your SHOUTcast Server bind to all IP addresses on all available interfaces."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):283
+msgid "Setting proxy/yp.SHOUTcast.com port"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):283
+#, no-wrap
+msgid "\n<comment>; Yport, port to connect to yp.SHOUTcast.com on. For people behind caching\n; web proxies, change this to the alternate port (666 is what it might be,\n; check www.SHOUTcast.com if you have problems). Otherwise, leave this at 80.\n; We're actively working on re-opening port 666, but as of release the only\n; working port is port 80.</comment>\nYport=80\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):292
+msgid "This has 2 functions. First is the port to connect to yp.SHOUTcast.com with. yp.SHOUTcast.com is nullsoft's page for public servers so users know where to listen in on. Users can search for your station from this page. The secondary use is for web proxies. Set this to the port you use for proxy connects, and set DestIP to your proxy for streaming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):300
+msgid "Setting up reverse DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):300
+#, no-wrap
+msgid "\n<comment>; NameLookups.  Specify 1 to perform reverse DNS on connections.\n; This option may increase the time it takes to connect to your\n; server if your DNS server is slow.  Default is 0 (off).</comment>\nNameLookups=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):307
+msgid "This option specifies whether or not you want to perform reverse DNS lookups on clients. This would take an IP address and try to find out the corresponding host name. Use this for logging purposes to create a more detailed report."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):313
+msgid "Setting up relaying"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):322
+msgid "This specifies that you are acting as a relay server. Relay servers are often used to take a low bandwidth connection that can only stream to one client, and use its own higher bandwidth to serve to more clients. RelayPort specifies the port and IP address of the SHOUTcast Server you wish to relay for. Comment this out if you don't plan on using your server as a relay."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):333
+msgid "Server Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):336
+msgid "Setting the admin password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):348
+msgid "Setting this will create a broadcaster and administrator. The broadcaster can log in with Password, and view connections. However, should the person want to kick/ban/administer the server, they must have the Admin password. This option creates more specific roles for your server. This is recommended for instances where the system administrator is not the same person as the broadcaster."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):357
+msgid "Setting up auto user disconnect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):357
+#, no-wrap
+msgid "\n<comment>; AutoDumpUsers controls whether listeners are disconnected if the source\n; stream disconnects. The default is 0.</comment>\nAutoDumpUsers=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):363
+msgid "This specifies whether or not users are kicked out if the stream disconnects for any reason. This is set to 0, so that clients will either timeout themselves, or keep trying to buffer a stream. Use this if you expect short interruptions at any time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):370
+msgid "Setting up the source timeout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):370
+#, no-wrap
+msgid "\n<comment>; AutoDumpSourceTime specifies how long, in seconds, the source stream is\n; allowed to be idle before the server disconnects it. 0 will let the source\n; stream idle indefinitely before disconnecting. The default is 30.</comment>\nAutoDumpSourceTime=30\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):377
+msgid "This specifies when the SHOUTcast Server should give up waiting for a source (mainly a relay server) to stream content from. Anywhere from 30 to 60 should be a reasonable value for this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):383
+msgid "Setting up the content directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):383
+#, no-wrap
+msgid "\n<comment>; ContentDir specifies the directory location on disk of where to stream\n; on-demand content from. Subdirectories are supported as of DNAS 1.8.2.\n; Default is ./content/, meaning a directory named content in the same directory\n; as where sc_serv was invoked from.</comment>\nContentDir=/opt/SHOUTcast/content/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):391
+msgid "The ContentDir specifies where to put on demand content. For example, if you wish to stream an announcement to employees, you could use this for that purpose. The SHOUTcast Server ebuild sets this to <path>/opt/SHOUTcast/content</path> for you. To use this, put an mp3 in the content directory, then point your browser to <c>http://example.com:[port]/content/mp3name.pls</c>. SHOUTcast Server will automatically create a streaming media compatible play list for the mp3, and stream it on demand. Use this as an alternative to SHOUTcast Trans for streaming media source."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):403
+msgid "Setting up an intro file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):414
+msgid "This allows you to configure an intro file. Every time users connect, they'll hear this file played. As it states, the stream bit rate and the intro song bit rate must match, or else things will break. You can, however, put something such as intro128.mp3 and intro64.mp3, and it will play intro128.mp3 to users connecting to a 128kbps stream, and intro64.mp3 for users connecting at 64kbps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):423
+msgid "Setting up a back file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):436
+msgid "This is the same as above, but will be played when the stream source ends, instead of when users disconnect. This will only work if AutoDumpUsers is set to 0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):442
+msgid "Setting up a title format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):442
+#, no-wrap
+msgid "\n<comment>; TitleFormat specifies a format string for what title is sent to the listener.\n; For example, a string of 'Justin Radio' forces the title 'Justin Radio' even\n; when the source changes the title. You can use up to one '%s' in the string\n; which lets you contain the title from the source. For example, if your\n; TitleFormat is 'Justin Radio: %s', and the source plug-in's title is\n; 'Billy plays the blues', then the net title is\n; 'Justin Radio: Billy plays the blues'. Note: only works on non-relay servers.\n; The default is no format string.</comment>\nTitleFormat=Chris Gentoo Beats: %s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):454
+msgid "This sets up a non-variable title for your SHOUTcast server. Use this if your source stream differs from your SHOUTcast Server's name. This will NOT work with relay servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):460
+msgid "Setting up a URL format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):467
+msgid "This is the same as TitleFormat except that the URL listed above is used instead of the source stream's URL."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):472
+msgid "Setting up the public status of a source stream"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):472
+#, no-wrap
+msgid "\n<comment>; PublicServer can be always, never, or default (the default, heh)\n; Any setting other than default will override the public status\n; of the source plug-in or of a SHOUTcast Server that is being relayed.</comment>\nPublicServer=default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):479
+msgid "This specifies whether or not you want to be listed as a public server even if your relay server/source plug-in is listed as such."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):484
+msgid "Allowing relaying"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):484
+#, no-wrap
+msgid "\n<comment>; AllowRelay determines whether or not other SHOUTcast Servers will be\n; permitted to relay this server.  The default is Yes.</comment>\nAllowRelay=Yes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):490
+msgid "AllowRelay determines if other servers are allowed to relay your content. If you don't think you'll ever relay at all, set this to No."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):495
+msgid "Allowing relays to publically display the source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):495
+#, no-wrap
+msgid "\n<comment>; AllowPublicRelay, when set to No, will tell any relaying servers not\n; to list the server in the SHOUTcast directory (non-public), provided\n; the relaying server's Public flag is set to default.  The default is\n; Yes.</comment>\nAllowPublicRelay=Yes\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):503
+msgid "AllowPublicRelay specifies whether or not you wish to be listed in the SHOUTcastpublic directory if the server you're relaying to is already listed. Note that PublicServer can override this setting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):509
+msgid "Setting MetaInterval"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):509
+#, no-wrap
+msgid "\n<comment>; MetaInterval specifies how often, in bytes, meta data sent.\n; You should really leave this at the default of 32768, but the option is\n; provided anyway.</comment>\nMetaInterval=32768\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):516
+msgid "Just leave this as is."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):523
+msgid "Access Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):526
+msgid "Setting the max listener time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):534
+msgid "I'm not to sure why you'd need this one. Basically, if a user is on for too many minutes, disconnect them. Only thing I can think of is to kick idlers off, or people you think should be doing other things than listening to your stream. Value is measured in minutes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):541
+msgid "Setting up the ban file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):549
+msgid "This is the filename for the list of clients that are banned from your server. The default is sc_serv.ban, but you can use whatever name you so desire with this setting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):555
+msgid "Setting the Rip list"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):567
+msgid "As grim as it sounds, Rip actually stands for \"Reserved IP\". Use this for your friends or other people you consider more important than random users. If you are currently streaming to the max number of users possible, and one of your rip members tries to get on, it will kick the longest listening person from the server to get them on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):575
+msgid "Setup if Rip only users can access your server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):585
+msgid "This allows for only Rip members to connect to your SHOUTcast Server. You can either use this for private radio streams, or to make it so that only certain relays will be able to access your stream."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):594
+msgid "Mass Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):597
+msgid "Setting Unique variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):612
+msgid "Basically, if you're running lots of SHOUTcast Servers, it would be a dire pain to change all the log/ban/etc. files to something unique for every configuration. Instead, you can set Unique to something, and $ will be replaced with whatever Unique is set to. For example, if one file had Unique=Jazz and another had Unique=Rock, then Log=/var/log/$.log would produce /var/log/Jazz.log on one configuration file and /var/log/Rock.log on another configuration file. Much easier when dealing with multiple SHOUTcast Servers on similar configurations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):623
+msgid "Setting up common configure variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):636
+msgid "If you're running multiple SHOUTcast Servers and wish to utilize similar configuration variables without setting them all for each configuration file, you can set this to point to a file that contains settings that are similar between multiple configurations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):646
+msgid "Optimization Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):649
+msgid "Setup number of CPU's utilized"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):662
+msgid "On multiple CPU systems, use this setting to force the SHOUTcast Server to utilize CpuCount # of processors. The default to assign one thread to each processor, and have listeners across all the threads. If you set this lower than your total processor count, this will leave processors free to do other things."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):670
+msgid "Setup data submission gap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):686
+msgid "The SHOUTcast Server will use the sleep value in determining the gap between sending data. The higher the value, the longer the gap, the lower the value, the shorter the gap and the more CPU usage SHOUTcast Server will take up. On slower systems, as it states, you might want to lower this so that the SHOUTcast Servers sends data more and more frequently to users. Best to leave as is."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):695
+msgid "Setup XML output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):702
+msgid "Probably don't need to worry about this setting to much unless you use custom XML parsers to create custom statistics for you server. If the XML parser cannot handle whitespace and line feeds in XML, set this to Yes, and all should work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):712
+msgid "Configuration Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):715
+msgid "Your SHOUTcast Server should now be configured. For businesses that are using SHOUTcast, I recommend turning on WC3 logging, as it can be easily parsed, and used for creating custom statistics. You should also enable the AdministratorPassword. You might also wish to enable some of the mass configuration options if you're creating multiple SHOUTcast Servers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):723
+msgid "With the configuration setup, we'll now work on getting SHOUTcast up and running. We'll start with simple on demand streaming for a simple startup, then work on SHOUTcast Trans later (as it is somewhat more involved)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):734
+msgid "Getting started with SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):736
+msgid "Setting up on demand streaming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):739
+msgid "On demand streaming, as shown in the configuration chapter, automatically sets up on demand play lists for mp3 files in the content directory. The SHOUTcast server ebuild has a directory setup in /opt/SHOUTcast/content for all your on demand mp3's. Let's get started by creating a simple on demand streaming mp3."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):746
+msgid "First we'll need to get an mp3 from somewhere and put it in the content directory. We'll take this sample.mp3 file from an /Mp3 directory I have created."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):752
+msgid "Copying an mp3 to the content directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):752
+#, no-wrap
+msgid "\n# <i>cp sample.mp3 /opt/SHOUTcast/content/</i>\n# <i>cd /opt/SHOUTcast/content/</i>\n# <i>ls</i>\nsample.mp3\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):759
+msgid "OK, so the file is copied over now. Now we'll need to startup our SHOUTcast Server so the file can be accessed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):764
+msgid "Starting up the SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):764
+#, no-wrap
+msgid "\n# <i>/etc/init.d/shoutcast start</i>\n * Starting Shoutcast Server...\n*******************************************************************************\n** SHOUTcast Distributed Network Audio Server\n** Copyright (C) 1998-2004 Nullsoft, Inc.  All Rights Reserved.\n** Use \"sc_serv filename.ini\" to specify an ini file.\n*******************************************************************************\n                                                                         [ ok ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):775
+msgid "The little banner is there to make sure that nothing dies right away (i.e. so you know your server actually started). Your SHOUTcast Server is now started! Because of the nature of on demand content, you will ONLY be able to access it from a browser. MPlayer or anything else won't be able to stream it as is. I use kmplayer in order to access the stream directly from my browser. You can see the result on the next image."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(figure:caption):785
+msgid "On Demand Content"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(figure:short):785
+msgid "OnDemandContent"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(figure:link):785
+msgid "/images/docs/shoutcast-OnDemandContent.jpg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):787
+msgid "Some people have Audacious setup to handle their audio mime types, so your browser may spawn Audacious up in order to play the resulting streaming content. Now that you are able to work with on demand content, we'll now work on using SHOUTcast Trans to create a true streaming radio server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):799
+msgid "Setting up SHOUTcast Trans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):801
+msgid "SHOUTcast Trans introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):804
+msgid "SHOUTcast Trans stands for SHOUTcast Trans(coder), as it is able to transcode mp3's to lower or higher bit rates. SHOUTcast Trans works by streaming mp3's from a play list specified in the configuration file. We'll begin to setup the configuration for SHOUTcast Trans, so that we can have a real to goodness streaming radio station. We'll begin by opening the configuration file for SHOUTcast Trans, which just so happens to be located in /etc/shoutcast/sc_trans.conf."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):814
+msgid "Opening the SHOUTcast Trans configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):814
+#, no-wrap
+msgid "\n<comment>(First install SHOUTcast Trans)</comment>\n# <i>emerge shoutcast-trans-bin</i>\n<comment>(Next open the SHOUTcast Trans configuration file)</comment>\n# <i>vi /etc/shoutcast/sc_trans.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):821
+msgid "Now that we have the SHOUTcast Trans configuration file open, we'll begin to setup the streaming source."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):829
+msgid "Configuring SHOUTcast Trans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):832
+msgid "Setting up the playlist"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):832
+#, no-wrap
+msgid "\n<comment>; PlaylistFile (required EVEN IF RELAYING) - play list file (to create, use\n; find /path/to/mp3/directory -type f -name \"*.mp3\" &gt; playlist_filename.lst</comment>\nPlaylistFile=/opt/SHOUTcast/playlists/playlist.lst\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):838
+msgid "This setting tells SHOUTcast where to find its streaming media content from. This setting requires an existing file, so let's go ahead and create a play list. I'll create one real quick from my /Mp3 directory referred to earlier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):845
+msgid "Creating the playlist"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):845
+#, no-wrap
+msgid "\n# <i>find /Mp3 -type f -name \"*.mp3\" &gt; /opt/SHOUTcast/playlists/playlist.lst</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):849
+msgid "Now that the play list is setup, we point the configuration file to it, and SHOUTcast Trans will now know what files to stream."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):854
+msgid "Setting the server IP and port"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):854
+#, no-wrap
+msgid "\n<comment>; Serverip/ServerPort are the target server to send to</comment>\nServerip=127.0.0.1\nServerPort=8000\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):860
+msgid "This setting decides where to send the streaming content. In this guide, it will be the SHOUTcast Server's IP and port that you setup previously (DestIP and PortBase)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):866
+msgid "Setting the SHOUTcast Server password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):866
+#, no-wrap
+msgid "\n<comment>; Password is the password on the sc_serv you're sending to.</comment>\nPassword=password_you_setup_in_sc_serv.conf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):871
+msgid "The is the same password that you setup in the SHOUTcast Server configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):875
+msgid "Setting up your stream information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):875
+#, no-wrap
+msgid "\n<comment>; StreamTitle/URL/Genre define the data that appears on the directory and in the\n; stream info.</comment>\nStreamTitle=Chris Gentoo Beats\nStreamURL=http://www.gentoo.org\nGenre=JPOP Electronica And More!\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):883
+msgid "This sets up the title of your stream (i.e. Radio One), the URL (i.e. http://www.radio-one.com), and the Genre (i.e. Electronica Trance Tribal)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):888
+msgid "Setting up your logfile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):888
+#, no-wrap
+msgid "\n<comment>; Logfile optionally denotes a text file to log sc_Trans to.  a kill -HUP\n; will force a close and re-open of this file (but will also cease logging to\n; the console)</comment>\nLogFile=/var/log/sc_Trans.log\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):895
+msgid "This will point to the log file for SHOUTcast Trans. All your logging goes here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):900
+msgid "Setting up shuffling"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):900
+#, no-wrap
+msgid "\n<comment>; Shuffle the play list</comment>\nShuffle=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):905
+msgid "Decide on whether or not you want your play list to play random songs from your list each time. Most will set this to 1. If you're going to be accepting song requests, set this to 0 and I'll explain how to do that later on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):911
+msgid "Setting up the stream"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):911
+#, no-wrap
+msgid "\n<comment>; Bitrate/SampleRate/Channels recommended values:\n; 8kbps 8000/11025/1\n; 16kbps 16000/11025/1\n; 24kbps 24000/22050/1\n; 32kbps 32000/22050/1\n; 64kbps mono 64000/44100/1\n; 64kbps stereo 64000/22050/2\n; 96kbps stereo 96000/44100/2\n; 128kbps stereo 128000/44100/2</comment>\nBitrate=128000\nSampleRate=44100\nChannels=2\n<comment>; Quality is from 1-10. 1 is best, 10 is fastest.</comment>\nQuality=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):928
+msgid "Bitrate sets up the bit rate for your stream. This can be from 8000 (8kbps) to 128000 (128kbps). SampleRate sets the sampling rate of the stream. This can be anything from 11025 (11025kHz) to 44100 (44100kHz). Channels sets how many channels your stream will broadcast. This can be anything from 1 (mono) to 2 (stereo). Quality sets the stream quality. This is somewhat still controlled by the Bitrate/SampleRate/Channels. This is where you deal with how compressed the stream is. 1 gives you best quality, 10 gives you the best speed. Keep your connection in mind when you set these values! Use the guide given in order to figure out what your mp3's should be streamed at."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):940
+msgid "Setting up crossfading"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):940
+#, no-wrap
+msgid "\n<comment>; Mode=0 for none, 1 for 100/100-&gt;100/0, 2 for 0/100-&gt;100/0</comment>\nCrossfadeMode=1\n<comment>; Length is ms.</comment>\nCrossfadeLength=8000\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):947
+msgid "This sets up song cross fading. Setting this to 0 will disable cross fading. If you set it to 1, Song 1 will fade out and Song 2 will fade in. If you set it to 2, Song 1 will fade in and Song 2 will fade out. The length is how long in ms the cross fade occurs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):954
+msgid "Enabling ID3 usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):954
+#, no-wrap
+msgid "\nUseID3=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):958
+msgid "This decides whether or not you wish to use the ID3 tag for information about the mp3."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):963
+msgid "Setting up public status"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):963
+#, no-wrap
+msgid "\n<comment>; Public determines whether or not this station will show up in the directory</comment>\nPublic=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):968
+msgid "This sets up whether or not streams should be publicly listed when relaying to a server. Remember PublicServer in sc_serv.conf can over-ride this!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):973
+msgid "Setting up user interaction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):973
+#, no-wrap
+msgid "\n<comment>; Put stuff here for user interaction (AOL IM, ICQ, IRC)</comment>\nAIM=AIMHandle\nICQ=\nIRC=SHOUTcast\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):980
+msgid "This sets up the information on how to reach you (the DJ). You can setup AIM or ICQ channels for song requests/anything. You can setup your own IRC channel as well, so that you can interact with multiple users at once."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):989
+msgid "SHOUTcast Trans Setup Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):992
+msgid "Your SHOUTcast Trans is now ready to stream to your SHOUTcast Server! We'll now get started on streaming your mp3's."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1002
+msgid "Getting Started With SHOUTcast Trans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1004
+msgid "Starting up SHOUTcast Trans"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1007
+msgid "As I most often use SHOUTcast Trans with SHOUTcast Server, I tend to startup SHOUTcast Trans, which in turns starts up SHOUTcast for you (much easier). So we'll go ahead and get SHOUTcast Trans started."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1013
+msgid "Starting up SHOUTcast Trans and SHOUTcast Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1013
+#, no-wrap
+msgid "\n# <i>/etc/init.d/shoutcast_trans start</i>\n * Starting Shoutcast Server...\n*******************************************************************************\n** SHOUTcast Distributed Network Audio Server\n** Copyright (C) 1998-2004 Nullsoft, Inc.  All Rights Reserved.\n** Use \"sc_serv filename.ini\" to specify an ini file.\n*******************************************************************************\n                                                  [ ok ]\n* Starting Shoutcast Trans...                     [ ok ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1028
+msgid "Listening to the SHOUTcast Trans stream"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1031
+msgid "Now that SHOUTcast Trans is started, we'll start listening to the stream. I use MPlayer in this example to play the stream."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1036
+msgid "Listening to your stream"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1036
+#, no-wrap
+msgid "\n# <i>mplayer -cache 1024 http://127.0.0.1:8000/</i>\n...\nPlaying http://127.0.0.1:8000/.\nConnecting to server 127.0.0.1[127.0.0.1]:8000 ...\nName   : Chris Gentoo Beats\nGenre  : JPOP Electronica And More!\nWebsite: http://www.gentoo.org\nPublic : no\nBitrate: 128kbit/s\nCache size set to 1024 KBytes\nConnected to server: 127.0.0.1\nCache fill:  9.38% (98304 bytes)    Audio file detected.\n==========================================================================\nOpening audio decoder: [mp3lib] MPEG layer-2, layer-3\nMP3lib: init layer2 and 3 finished, tables done\nmpg123: Can't rewind stream by 156 bits!\nAUDIO: 44100 Hz, 2 ch, 16 bit (0x10), ratio: 16000-&gt;176400 (128.0 kbit)\nSelected audio codec: [mp3] afm:mp3lib (mp3lib MPEG layer-2, layer-3)\n==========================================================================\nChecking audio filter chain for 44100Hz/2ch/16bit -&gt; 44100Hz/2ch/16bit...\nAF_pre: af format: 2 bps, 2 ch, 44100 hz, little endian signed int\nAF_pre: 44100Hz 2ch Signed 16-bit (Little-Endian)\nAO: [oss] 44100Hz 2ch Signed 16-bit (Little-Endian) (2 bps)\nBuilding audio filter chain for 44100Hz/2ch/16bit -&gt; 44100Hz/2ch/16bit...\nVideo: no video\nStarting playback...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1065
+msgid "This was somewhat clipped. The -cache variable was put in to over-ride my somewhat larger buffering settings. And voilà! You're now listening to streaming media! In the next chapter, we'll show you how to do a little bit more with your SHOUTcast Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1077
+msgid "Advanced SHOUTcast Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1079
+msgid "Business Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1082
+msgid "Businesses can use SHOUTcast in a number of ways:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(li):1087
+msgid "Use on demand content streaming to make more interesting daily announcements."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(li):1091
+msgid "Have streaming public announcements available as they happen, let your clients know what's going on, on the spot! Then archive them as on demand content streaming for future reference."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(li):1096
+msgid "Do interviews as streaming media and archive them as on demand content streaming."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1102
+msgid "There are more possibilities on how to utilize SHOUTcast Server for businesses. Use live streaming media instead of boring old text!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1110
+msgid "DJ-ing with SHOUTcast"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1113
+msgid "SHOUTcast Server is one of the most popular servers for both new and veteran DJs alike. For those just starting, there are a few ways to increase the user experience of your SHOUTcast Server. Having an intro song is very key. It gives the users an idea of what your station is all about. Be sure to include this! Post your server on yp.SHOUTcast.com (described in the SHOUTcast Server configuration section) so that everyone knows where you are. One of the most unique things is to be able to take requests. To set up requesting, first turn Shuffle off in sc_Trans.conf. Have about, I'd say, 10 or so songs ready to get you started. Then start requesting song requests in the middle. When someone requests a song, simple add it to the end of your play list, and then you can use this script here to control what SHOUTcast Trans does with your play list:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1128
+msgid "djcontrol"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1128
+#, no-wrap
+msgid "\n<comment>#!/bin/bash</comment>\n\ncase \"$1\" in\n  \"reload\")\n    kill -s USR1 `cat /var/run/SHOUTcast_Trans.pid`\n    ;;\n  \"next\")\n    kill -s WINCH `cat /var/run/SHOUTcast_Trans.pid`\n    ;;\n  *)\n    echo \"Invalid command\"\n    ;;\nesac\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1144
+msgid "When you've added the song to the play list, you need to tell SHOUTcast Trans that your play list has changed with the new request entry."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1149
+msgid "Reloading the playlist"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1149
+#, no-wrap
+msgid "\n# <i>djcontrol reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1153
+msgid "You should now let the users know after what song the requests will start. Or if you want, you can keep skipping with:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre:caption):1158
+msgid "Skipping through the playlist"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(pre):1158
+#, no-wrap
+msgid "\n# <i>djcontrol next</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1162
+msgid "Be careful not to skip too much, as there is no previous control. Once you hit their song, the requesting begins. I'd get about 5 or so requests before you start requesting. This way you don't run all the way back to the beginning. If you start to lack in requests and expect that your request hour is over with, then simply copy your next session's play list over the requests play list and reload the play list. Once the current song is over, it will go back to the new play list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(title):1175
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(p):1178
+msgid "That ends it for the SHOUTcast Server and SHOUTcast Trans tutorial. I hope you benefited from the information here and please email me any comments or suggestions for this page! Enjoy your new streaming SHOUTcast Server!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//shoutcast-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/source_mirrors.xml.pot b/doc/gettext/source_mirrors.xml.pot
new file mode 100644
index 0000000..15ddcdd
--- /dev/null
+++ b/doc/gettext/source_mirrors.xml.pot
@@ -0,0 +1,264 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(guide:link):5
+msgid "/doc/en/source_mirrors.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):7
+msgid "Gentoo Linux Source Mirrors Policy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):10
+msgid "klieber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):10
+msgid "Kurt Lieber"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):12 ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):15 ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):18 ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):21 ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(author:title):24
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):13
+msgid "cshields@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):13
+msgid "Corey Shields"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):16
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):16
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):19
+msgid "jforman@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):19
+msgid "Jeffrey Forman"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):22
+msgid "robbat2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):22
+msgid "Robin H. Johnson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail:link):25
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(mail):25
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(abstract):28
+msgid "This document explains the requirements for source mirrors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(version):35
+msgid "1.13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(date):36
+msgid "2010-04-28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):39
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):41
+msgid "Minimum Bandwidth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):44
+msgid "To properly host a source mirror, you should have a minimum of 5Mbps upstream bandwidth. ADSL and cable connections do not generally make adequate connections for distfile hosts due to their limited upstream performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):53
+msgid "Minimum Disk Space"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):56
+msgid "The space requirements depend on whether you choose to run a \"Full\" mirror or a \"Distfiles only\" mirror. Full mirrors require 210 GB of disk space. Distfiles only mirrors require 120 GB of space."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):65
+msgid "Minimum User Count"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):68
+msgid "We ask that you support a minimum of 15 and preferrably 30 or more concurrent user connections."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):76
+msgid "Update Frequency"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):79
+msgid "All mirrors must be synchronized every four hours, starting at midnight in your local time zone. This helps distribute the load out over a period of time, rather than having all mirrors synchronize at the same time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):88
+msgid "Mirror Needs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):91
+msgid "Your mirror may not be added immediately to our listing and given access to the private distribution point. We add mirrors on an as-needed basis so as not to clutter up the listing, and to provide an adequate amount of high speed mirrors. You are more than welcome to peek in <uri link=\"irc://irc.gentoo.org/gentoo-mirrors\">#gentoo-mirrors</uri> on IRC and chat up to see the status of your mirror being added to our official network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):105
+msgid "Implementation details"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):109
+msgid "For new source mirror requests, the procedure will be as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):113
+msgid "Set up your server to rsync with ftp.ussg.iu.edu::gentoo-distfiles. Once you have a complete mirror of that server, please file a bug report on <uri link=\"http://bugs.gentoo.org/enter_bug.cgi?product=Mirrors\">bugs.gentoo.org</uri> under the <c>Mirrors</c> category stating that you have a new mirror and wish it to be added to the list of official mirrors. Please specify whether you wish to be a \"Full\" mirror or \"Distfiles only\" mirror. Distfiles only mirrors will be designated as such on the website."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):123
+msgid "Full mirrors must carry the following directories (plus any directories that get added in the future):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):129
+msgid "/releases (45-55G)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):130
+msgid "/experimental (20-30G)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):131 ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):141
+msgid "/distfiles (110G)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):132 ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):142
+msgid "/snapshots (600M)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):133
+msgid "/grp (0M, obsolete)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):136
+msgid "Distfiles only mirrors need to carry the following directories:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):145
+msgid "We will then verify that the mirror exists and we can connect to it properly. Then, in the next 2 weeks, we will determine if your mirror is syncing correctly and in accordance with this policy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):151
+msgid "If all steps went smoothly, we will then add you to our list of <uri link=\"/main/en/mirrors2.xml\">download mirrors</uri> on the main web site. We will also send you the login information for our private master distfile mirror which is only available to official Gentoo Linux source mirrors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):158
+msgid "Additionally, you, the mirror admin, will be requested to subscribe to the gentoo-mirrors mailing list (low traffic) so that you can follow all issues associated with source mirrors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(note):164
+msgid "Thanks for helping out Gentoo Linux users and developers! :) For any mirror administration issues or problems, please contact <mail link=\"mirror-admin@gentoo.org\">mirror-admin@gentoo.org</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(warn):170
+msgid "Do NOT email mirror-admin@gentoo.org for mirror requests, please file a bug. It makes mirror tracking easier on us."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):180
+msgid "Short FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):182
+msgid "Q: Who should I contact regarding new mirrors or to get my mirror added to the Gentoo web site?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):188 ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):198
+msgid "A: Please file a bug on bugs.gentoo.org under the <c>Mirrors</c> category."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):195
+msgid "Q: Who should I contact regarding mirror issues and maintenance?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):205
+msgid "Q: I run a private source mirror for my company. Can I still access the private master source mirror?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):211
+msgid "A: Because our resources are limited, we need to ensure we allocate them in such a way to provide the maximum amount of benefit to our users. As such, we limit connections to our master rsync and distfile mirrors to public mirrors only. Users are welcome to use our regular mirror system to establish a private source mirror."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):222
+msgid "Q: How do I find the mirror nearest to me?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):225
+msgid "A: mirrorselect was designed to do this for you. If you haven't already run <c>emerge mirrorselect</c>, then please do so. Then run: <c>mirrorselect</c>. An ncurses-based menu will display allowing you to select a mirror close to you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):235
+msgid "Q: I don't have that much disk space. Can I mirror part of the sources?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):240
+msgid "A: Yes, if you are unable to mirror our full sources, you can elect to mirror the following two directories only:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):246
+msgid "/distfiles"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(li):247
+msgid "/snapshots"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):250
+msgid "These two directories will require approximately 50GB of space and you will be listed on our site as a distfiles-only mirror."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):258
+msgid "Q: Do I have to turn on Directory Indexing for directories served up via HTTP?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):263
+msgid "A: Directory Indexing is required for the /releases and /experimental directories, but can be turned off for all other directories (including /distfiles) if you wish."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(title):273
+msgid "Q: Do I have to mirror historical? I mean, it is old releases."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(p):276
+msgid "A: Of course not, it is quite a bit of data. In your rsync command, add <path>--exclude=/releases/historical</path> to your rsync options. This will exclude historical and save you quite a bit of space."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//source_mirrors.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/sudo-guide.xml.pot b/doc/gettext/sudo-guide.xml.pot
new file mode 100644
index 0000000..d051bbc
--- /dev/null
+++ b/doc/gettext/sudo-guide.xml.pot
@@ -0,0 +1,424 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(guide:link):7
+msgid "/doc/en/sudo-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):8
+msgid "Gentoo Sudo(ers) Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(mail:link):11
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(mail):11
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(abstract):14
+msgid "When you want some people to perform certain administrative steps on your system without granting them total root access, using sudo is your best option. With sudo you can control who can do what. This guide offers you a small introduction to this wonderful tool."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(version):25
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(date):26
+msgid "2006-07-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):29
+msgid "About Sudo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):31
+msgid "Granting Permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):34
+msgid "The <c>app-admin/sudo</c> package allows the system administrator to grant permission to other users to execute one or more applications they would normally have no right to. Unlike using the <e>setuid</e> bit on these applications <c>sudo</c> gives a more fine-grained control on <e>who</e> can execute a certain command and <e>when</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):42
+msgid "With <c>sudo</c> you can make a clear list <e>who</e> can execute a certain application. If you would set the setuid bit, any user would be able to run this application (or any user of a certain group, depending on the permissions used). You can (and probably even should) require the user to provide a password when he wants to execute the application and you can even fine-tune the permissions based on the user's location: logged on from the system itself or through SSH from a remote site."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):55
+msgid "Logging Activity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):58
+msgid "One additional advantage of <c>sudo</c> is that it can log any attempt (successful or not) to run an application. This is very useful if you want to track who made that one fatal mistake that took you 10 hours to fix :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):67
+msgid "Configuring Sudo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):70
+msgid "The <c>sudo</c> configuration is managed by the <path>/etc/sudoers</path> file. This file should never be edited through <c>nano&nbsp;/etc/sudoers</c> or <c>vim&nbsp;/etc/sudoers</c> or any other editor you might like. When you want to alter this file, you should use <c>visudo</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):77
+msgid "This tool makes sure that no two system administrators are editing this file at the same time, preserves the permissions on the file and performs some syntax checking to make sure you make no fatal mistakes in the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):86
+msgid "About this Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):89
+msgid "This guide is meant as a quick introduction. The <c>sudo</c> package is a lot more powerful than what is described in this guide. It has special features for editing files as a different user (<c>sudoedit</c>), running from within a script (so it can background, read the password from standard in instead of the keyboard, ...), etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):97
+msgid "Please read the <c>sudo</c> and <c>sudoers</c> manual pages for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):107
+msgid "Sudoers Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):109
+msgid "Basic Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):112
+msgid "The most difficult part of <c>sudo</c> is the <path>/etc/sudoers</path> syntax. The basic syntax is like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):117
+msgid "Basic /etc/sudoers syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):117
+#, no-wrap
+msgid "\nuser  host = commands\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):121
+msgid "This syntax tells <c>sudo</c> that the user, identified by <e>user</e> and logged on through the system <e>host</e> can execute any of the commands listed in <e>commands</e> as the root user. A more real-life example might make this more clear: allow the user <e>swift</e> to execute <c>emerge</c> if he is logged on from the system (not through SSH):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):129
+msgid "Live /etc/sudoers examples"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):129
+#, no-wrap
+msgid "\nswift  localhost = /usr/bin/emerge\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):133
+msgid "A <brite>big warning</brite> is in place though: do not allow a user to run an application that can allow people to elevate privileges. For instance, allowing users to execute <c>emerge</c> as root can indeed grant them full root access to the system because <c>emerge</c> can be manipulated to change the live file system to the user's advantage. If you do not trust your <c>sudo</c> users, don't grant them any rights."
+msgstr ""
+
+#. Wrappers are no real advantage here either, see #71750
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):146
+msgid "The user name can also be substituted with a group name - in this case you should start the group name with a <c>%</c> sign. For instance, to allow any one in the <c>wheel</c> group to execute <c>emerge</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):152
+msgid "Allowing the wheel group members to execute emerge"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):152
+#, no-wrap
+msgid "\n%wheel  localhost = /usr/bin/emerge\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):156
+msgid "You can extend the line to allow for several commands (instead of making a single entry for each command). For instance, to allow the same user to not only run <c>emerge</c> but also <c>ebuild</c> and <c>emerge-webrsync</c> as root:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):162
+msgid "Multiple commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):162
+#, no-wrap
+msgid "\nswift  localhost = /usr/bin/emerge, /usr/bin/ebuild, /usr/sbin/emerge-webrsync\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):166
+msgid "You can also specify a precise command and not only the tool itself. This is useful to restrict the use of a certain tool to a specified set of command options. The <c>sudo</c> tool allows shell-style wildcards (AKA meta or glob characters) to be used in pathnames as well as command line arguments in the sudoers file. Note that these are <e>not</e> regular expressions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):174
+msgid "Let us put this to the test:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):178
+msgid "Attempt to update the system using sudo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):178
+#, no-wrap
+msgid "\n$ <i>sudo emerge -uDN world</i>\n\nWe trust you have received the usual lecture from the local System\nAdministrator. It usually boils down to these three things:\n\n    #1) Respect the privacy of others.\n    #2) Think before you type.\n    #3) With great power comes great responsibility.\n\nPassword: <comment>(Enter the user password, not root!)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):191
+msgid "The password that <c>sudo</c> requires is the user's own password. This is to make sure that no terminal that you accidentally left open to others is abused for malicious purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):197
+msgid "You should know that <c>sudo</c> does not alter the <c>${PATH}</c> variable: any command you place after <c>sudo</c> is treated from <e>your</e> environment. If you want the user to run a tool in for instance <path>/sbin</path> he should provide the full path to <c>sudo</c>, like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):204
+msgid "Using the full path to a tool"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):204
+#, no-wrap
+msgid "\n$ <i>sudo /usr/sbin/emerge-webrsync</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):211
+msgid "Using Aliases"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):214
+msgid "In larger environments having to enter all users over and over again (or hosts, or commands) can be a daunting task. To ease the administration of <path>/etc/sudoers</path> you can define <e>aliases</e>. The format to declare aliases is quite simple:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):221
+msgid "Declaring aliases in /etc/sudoers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):221
+#, no-wrap
+msgid "\nHost_Alias hostalias = hostname1, hostname2, ...\nUser_Alias useralias = user1, user2, ...\nCmnd_Alias cmndalias = command1, command2, ...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):227
+msgid "One alias that always works, for any position, is the <c>ALL</c> alias (to make a good distinction between aliases and non-aliases it is recommended to use capital letters for aliases). As you might undoubtedly have guessed, the <c>ALL</c> alias is an alias to all possible settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):234
+msgid "A sample use of the <c>ALL</c> alias to allow <e>any</e> user to execute the <c>shutdown</c> command if he is logged on locally is:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):239
+msgid "Allowing any user to execute shutdown"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):239
+#, no-wrap
+msgid "\nALL  localhost = /sbin/shutdown\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):243
+msgid "Another example is to allow the user <c>swift</c> to execute the <c>emerge</c> command as root, regardless of where he is logged in from:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):248
+msgid "Allowing a user to run an application regardless of his location"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):248
+#, no-wrap
+msgid "\nswift   ALL = /usr/bin/emerge\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):252
+msgid "More interesting is to define a set of users who can run software administrative applications (such as <c>emerge</c> and <c>ebuild</c>) on the system and a group of administrators who can change the password of any user, except root!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):258
+msgid "Using aliases for users and commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):258
+#, no-wrap
+msgid "\nUser_Alias  <i>SOFTWAREMAINTAINERS</i> = swift, john, danny\nUser_Alias  <i>PASSWORDMAINTAINERS</i> = swift, sysop\nCmnd_Alias  <i>SOFTWARECOMMANDS</i>    = /usr/bin/emerge, /usr/bin/ebuild\nCmnd_Alias  <i>PASSWORDCOMMANDS</i>    = /usr/bin/passwd [a-zA-Z0-9_-]*, !/usr/bin/passwd root\n\n<i>SOFTWAREMAINTAINERS</i>  localhost = <i>SOFTWARECOMMANDS</i>\n<i>PASSWORDMAINTAINERS</i>  localhost = <i>PASSWORDCOMMANDS</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):271
+msgid "Non-Root Execution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):274
+msgid "It is also possible to have a user run an application as a different, non-root user. This can be very interesting if you run applications as a different user (for instance <c>apache</c> for the web server) and want to allow certain users to perform administrative steps as that user (like killing zombie processes)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):281
+msgid "Inside <path>/etc/sudoers</path> you list the user(s) in between <c>(</c>&nbsp;and&nbsp;<c>)</c> before the command listing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):286
+msgid "Non-root execution syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):286
+#, no-wrap
+msgid "\nusers  hosts = (run-as) commands\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):290
+msgid "For instance, to allow <c>swift</c> to run the <c>kill</c> tool as the <c>apache</c> or <c>gorg</c> user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):295
+msgid "Non-root execution example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):295
+#, no-wrap
+msgid "\nCmnd_Alias KILL = /bin/kill, /usr/bin/pkill\n\nswift   ALL = (apache, gorg) KILL\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):301
+msgid "With this set, the user can run <c>sudo&nbsp;-u</c> to select the user he wants to run the application as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):306
+msgid "Running pkill as the apache user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):306
+#, no-wrap
+msgid "\n$ <i>sudo -u apache pkill apache</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):310
+msgid "You can set an alias for the user to run an application as using the <c>Runas_Alias</c> directive. Its use is identical to the other <c>_Alias</c> directives we have seen before."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):319
+msgid "Passwords and Default Settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):322
+msgid "By default, <c>sudo</c> asks the user to identify himself using his own password. Once a password is entered, <c>sudo</c> remembers it for 5 minutes, allowing the user to focus on his tasks and not repeatedly re-entering his password."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):329
+msgid "Of course, this behavior can be changed: you can set the <c>Defaults:</c> directive in <path>/etc/sudoers</path> to change the default behavior for a user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):335
+msgid "For instance, to change the default 5 minutes to 0 (never remember):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):339
+msgid "Changing the timeout value"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):339
+#, no-wrap
+msgid "\nDefaults:swift  timestamp_timeout=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):343
+msgid "A setting of <c>-1</c> would remember the password indefinitely (until the system reboots)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):348
+msgid "A different setting would be to require the password of the user that the command should be run as and not the users' personal password. This is accomplished using <c>runaspw</c>. In the following example we also set the number of retries (how many times the user can re-enter a password before <c>sudo</c> fails) to <c>2</c> instead of the default 3:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):356
+msgid "Requiring the root password instead of the user's password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):356
+#, no-wrap
+msgid "\nDefaults:john   runaspw, passwd_tries=2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):360
+msgid "Another interesting feature is to keep the <c>DISPLAY</c> variable set so that you can execute graphical tools:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):365
+msgid "Keeping the DISPLAY variable alive"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):365
+#, no-wrap
+msgid "\nDefaults:john env_keep=DISPLAY\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):369
+msgid "You can change dozens of default settings using the <c>Defaults:</c> directive. Fire up the <c>sudo</c> manual page and search for <c>Defaults</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):374
+msgid "If you however want to allow a user to run a certain set of commands without providing any password whatsoever, you need to start the commands with <c>NOPASSWD:</c>, like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):380
+msgid "Allowing emerge to be ran as root without asking for a password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):380
+#, no-wrap
+msgid "\nswift     localhost = NOPASSWD: /usr/bin/emerge\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):389
+msgid "Using Sudo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):391
+msgid "Listing Privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):394
+msgid "To inform yourself what your capabilities are, run <c>sudo&nbsp;-l</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):398
+msgid "Listing capabilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):398
+#, no-wrap
+msgid "\n$ <i>sudo -l</i>\nUser swift may run the following commands on this host:\n    (root)   /usr/libexec/xfsm-shutdown-helper\n    (root)   /usr/bin/emerge\n    (root)   /usr/bin/passwd [a-zA-Z0-9_-]*\n    (root)   !/usr/bin/passwd root\n    (apache) /usr/bin/pkill\n    (apache) /bin/kill\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):409
+msgid "If you have any command in <path>/etc/sudoers</path> that does not require you to enter a password, it will not require a password to list the entries either. Otherwise you might be asked for your password if it isn't remembered."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(title):418
+msgid "Prolonging the Password Timeout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):421
+msgid "By default, if a user has entered his password to authenticate himself to <c>sudo</c>, it is remembered for 5 minutes. If the user wants to prolong this period, he can run <c>sudo&nbsp;-v</c> to reset the time stamp so that it will take another 5 minutes before <c>sudo</c> asks for the password again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre:caption):428
+msgid "Prolonging the password timeout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(pre):428
+#, no-wrap
+msgid "\n$ <i>sudo -v</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(p):432
+msgid "The inverse is to kill the time stamp using <c>sudo&nbsp;-k</c>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//sudo-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/test.xml.pot b/doc/gettext/test.xml.pot
new file mode 100644
index 0000000..614378a
--- /dev/null
+++ b/doc/gettext/test.xml.pot
@@ -0,0 +1,80 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(title):6
+msgid "Testfile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(mail:link):9
+msgid "pylon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(mail):9
+msgid "Lars Weiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(abstract):15
+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//test.xml(version):22
+msgid "1.84"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(date):23
+msgid "2008-12-03"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(title):26
+msgid "Sample Chapter 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(title):28
+msgid "Sample Section 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(p):31
+msgid "Some text. Some more text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(title):39
+msgid "Sample Section 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(p):42
+msgid "<b>Some bold text</b> and <e>emphasised</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(p):46
+msgid "Testing gentoo-doc-cvs mailing list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(p):49
+msgid "Testing gentoo-commits mailing list as well."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//test.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/udev-guide.xml.pot b/doc/gettext/udev-guide.xml.pot
new file mode 100644
index 0000000..65d094c
--- /dev/null
+++ b/doc/gettext/udev-guide.xml.pot
@@ -0,0 +1,471 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):6
+msgid "Gentoo udev Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(author:title):11
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail:link):12
+msgid "greg_g@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail):12
+msgid "Gregorio Guidi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(abstract):18
+msgid "This document explains what udev is and how you can use udev to fit your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(version):26
+msgid "6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(date):27
+msgid "2010-05-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):30
+msgid "What is udev?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):32
+msgid "The /dev Directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):35
+msgid "When Linux-users talk about the hardware on their system in the vicinity of people who believe Linux is some sort of virus or brand of coffee, the use of \"slash dev slash foo\" will return a strange look for sure. But for the fortunate user (and that includes you) using <path>/dev/hda1</path> is just a fast way of explaining that we are talking about the primary master IDE, first partition. Or aren't we?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):44
+msgid "We all know what a device file is. Some even know why device files have special numbers when we take a closer look at them when we issue <c>ls -l</c> in <path>/dev</path>. But what we always take for granted is that the primary master IDE disk is referred to as <path>/dev/hda</path>. You might not see it this way, but this is a flaw by design."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):52
+msgid "Think about hotpluggable devices like USB, IEEE1394, hot-swappable PCI, ... What is the first device? And for how long? What will the other devices be named when the first one disappears? How will that affect ongoing transactions? Wouldn't it be fun that a printing job is suddenly moved from your supernew laserprinter to your almost-dead matrix printer because your mom decided to pull the plug of the laserprinter which happened to be the first printer?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):61
+msgid "Enter <e>udev</e>. The goals of the udev project are both interesting and needed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):67
+msgid "Runs in userspace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):68
+msgid "Dynamically creates/removes device files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):69
+msgid "Provides consistent naming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):70
+msgid "Provides a user-space API"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):73
+msgid "To provide these features, udev is developed in three separate projects: <e>namedev</e>, <e>libsysfs</e> and, of course, <e>udev</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):81
+msgid "namedev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):84
+msgid "Namedev allows you to define the device naming separately from the udev program. This allows for flexible naming policies and naming schemes developed by separate entities. This device naming subsystem provides a standard interface that udev can use."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):91
+msgid "Currently only a single naming scheme is provided by namedev; the one provided by LANANA, used by the majority of Linux systems currently and therefore very suitable for the majority of Linux users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):97
+msgid "Namedev uses a 5-step procedure to find out the name of a given device. If the device name is found in one of the given steps, that name is used. The steps are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):104
+msgid "label or serial number"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):105
+msgid "bus device number"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):106
+msgid "bus topology"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):107
+msgid "statically given name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):108
+msgid "kernel provided name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):111
+msgid "The <e>label or serial number</e> step checks if the device has a unique identifier. For instance USB devices have a unique USB serial number; SCSI devices have a unique UUID. If namedev finds a match between this unique number and a given configuration file, the name provided in the configuration file is used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):119
+msgid "The <e>bus device number</e> step checks the device bus number. For non-hot-swappable environments this procedure is sufficient to identify a hardware device. For instance PCI bus numbers rarely change in the lifetime of a system. Again, if namedev finds a match between this position and a given configuration file, the name provided in that configuration file is used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):128
+msgid "Likewise the <e>bus topology</e> is a rather static way of defining devices as long as the user doesn't switch devices. When the position of the device matches a given setting provided by the user, the accompanying name is used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):134
+msgid "The fourth step, <e>statically given name</e>, is a simple string replacement. When the kernel name (the default name) matches a given replacement string, the substitute name will be used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):140
+msgid "The final step (<e>kernel provided name</e>) is a catch-all: this one takes the default name provided by the kernel. In the majority of cases this is sufficient as it matches the device naming used on current Linux systems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):149
+msgid "libsysfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):152
+msgid "udev interacts with the kernel through the sysfs pseudo filesystem. The libsysfs project provides a common API to access the information given by the sysfs filesystem in a generic way. This allows for querying all kinds of hardware without having to make assumptions on the kind of hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):162
+msgid "udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):165
+msgid "Every time the kernel gets an event in the device structure, it asks udev to take a look. udev follows the rules in the <path>/etc/udev/rules.d/</path> directory. udev then uses the information given by the kernel to perform the necessary actions on the <path>/dev</path> structure (creating or deleting device files)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):178
+msgid "Using udev on Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):180
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):183
+msgid "udev is meant to be used in combination with a 2.6 kernel (like <c>gentoo-sources</c> with the default 2007.0 profile). If you're using such a kernel then you just have to make sure that you have a recent <c>sys-apps/baselayout</c> version. That's all you need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):190
+msgid "Installing udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):190
+#, no-wrap
+msgid "\n# <i>emerge udev</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):194
+msgid "Kernelwise, be sure to activate the following options:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):198
+msgid "Required kernel options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):198
+#, no-wrap
+msgid "\nFile systems ---&gt;\n    [*] Inotify file change notification support\n    [*]   Inotify support for userspace\n  Pseudo filesystems ---&gt;\n    [*] /proc file system support\n    [*] Virtual memory file system support (former shm fs)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):207
+msgid "If you use <c>genkernel</c>, you don't need to do anything special. Genkernel sets up udev by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):215
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):218
+msgid "If you want to use the udev settings Gentoo provides to make your life comfortable, then read no more. Gentoo will use udev but keep a static <path>/dev</path> so that you will never have any missing device nodes. The Gentoo init scripts won't run the devfsd daemon and will deactivate devfs when you boot up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):226
+msgid "But if you are a die-hard and want to run a udev-only, unmodified system as is intended by the udev development (including the difficulties of missing device nodes because udev doesn't support them yet), by all means, read on :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):232
+msgid "We'll deactivate the rules that save the device file nodes: edit the <c>RC_DEVICE_TARBALL</c> variable in <path>/etc/conf.d/rc</path> and set it to <c>no</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):238
+msgid "/etc/conf.d/rc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):238
+#, no-wrap
+msgid "\nRC_DEVICE_TARBALL=\"no\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):242
+msgid "If you have included devfs support in your kernel, you can deactivate it in the bootloader configuration: add <c>gentoo=nodevfs</c> as a kernel parameter. If you want to use devfs and deactivate udev, add <c>gentoo=noudev</c> as kernel parameter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):254
+msgid "Known Issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):256
+msgid "Missing device node files at boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):259
+msgid "If you can't boot successfully because you get an error about <path>/dev/null</path> not found, or because the initial console is missing, the problem is that you lack some device files that must be available <e>before</e><path>/dev</path> is mounted and handled by udev. This is common on Gentoo machines installed from old media."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):267
+msgid "If you run <c>sys-apps/baselayout-1.8.12</c> or later, this problem is alleviated since the boot process should still manage to complete. However, to get rid of those annoying warnings, you should create the missing device nodes as described below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):274
+msgid "To see which devices nodes are present before the <path>/dev</path> filesystem is mounted, run the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):279
+msgid "Listing device nodes available at boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):279
+#, no-wrap
+msgid "\n# <i>mkdir test</i>\n# <i>mount --bind / test</i>\n# <i>cd test/dev</i>\n# <i>ls</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):286
+msgid "The devices needed for a successful boot are <path>/dev/null</path> and <path>/dev/console</path>. If they didn't show up in the previous test, you have to create them manually. Issue the following commands in the <path>test/dev/</path> directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):293
+msgid "Creating necessary device node files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):293
+#, no-wrap
+msgid "\n# <i>mknod -m 660 console c 5 1</i>\n# <i>mknod -m 660 null c 1 3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):298
+msgid "When you're finished, don't forget to unmount the <path>test/</path> directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):302
+msgid "Unmounting the test/ directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):302
+#, no-wrap
+msgid "\n# <i>cd ../..</i>\n# <i>umount test</i>\n# <i>rmdir test</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):311
+msgid "udev and nvidia"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):314
+msgid "If you use the proprietary driver from nVidia and the X server fails to start on a udev-only system, then make sure you have:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):320
+msgid "the <c>nvidia</c> module listed in <path>/etc/modules.autoload.d/kernel-2.6</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):324
+msgid "a version of baselayout equal to or greater than <c>sys-apps/baselayout-1.8.12</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):333
+msgid "No Consistent Naming between DevFS and udev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):336
+msgid "Even though our intention is to have a consistent naming scheme between both dynamical device management solutions, sometimes naming differences do occur."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):341
+msgid "One reported clash is with a HP Smart Array 5i RAID controller (more precisely the <c>cciss</c> kernel module). With udev, the devices are named <path>/dev/cciss/cXdYpZ</path> with X, Y and Z regular numbers. With devfs, the devices are <path>/dev/hostX/targetY/partZ</path> or symlinked from <path>/dev/cciss/cXdY</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):349
+msgid "If this is the case, don't forget to update your <path>/etc/fstab</path> and bootloader configuration files accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):354
+msgid "The same happens with all-round symlinks that used to exist in <path>/dev</path>, such as <path>/dev/mouse</path>, which <c>udev</c> doesn't create anymore. Be certain to check your X configuration file and see if the Device rule for your mouse points to an existing device file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):361
+msgid "Another issue is the difference in naming of terminals between devfs and udev. While devfs calls its terminals <c>tty</c>, udev calls them <c>vc</c> and <c>tty</c>. This could lead to a problem in case you are restricting root logins from consoles using <path>/etc/securetty</path>. You will need to make sure that both <c>tty1</c> and <c>vc/1</c> are listed in <path>/etc/securetty</path> to ensure that root can login using the console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):373
+msgid "Block device renaming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):376
+msgid "Recent versions of udev (104 and up) along with newer kernel versions (2.6.19 and up) may change your disc device names, due to a change in the kernel's libata implementation. A CD-RW device at <path>/dev/hdc</path> may be changed to <path>/dev/sr0</path>. While this is not normally a problem, it may cause issues for some applications that are hardcoded to look for devices at other locations. For example, <c>media-sound/rip</c> expects to find discs at <path>/dev/cdrom</path>, which becomes a problem if you use a newer kernel and udev renames your device to <path>/dev/cdrom1</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):387
+msgid "To work around these issues, you must edit <path>/etc/udev/rules.d/70-persistent-cd.rules</path> and assign the correct name to the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):393
+msgid "For more information on writing udev rules, be sure to read Daniel Drake's <uri link=\"http://www.reactivated.net/udevrules.php\">guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):401
+msgid "Network device renaming"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):404
+msgid "Sometimes unplugging and replugging a network device (like a USB WiFi card) can rename your net device each time, incrementing the number by one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):409
+msgid "When this happens, you'll see it become <c>wlan0</c>, <c>wlan1</c>, <c>wlan2</c>, etc. This is because udev is adding additional rules to its rules file, instead of reloading the existing rules. Since udev watches its rules directory via inotify, you need inotify support in your kernel config:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):416
+msgid "Enabling inotify support in the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):416
+#, no-wrap
+msgid "\nFile systems ---&gt;\n    [*] Inotify file change notification support\n    [*]   Inotify support for userspace\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):422
+msgid "Now udev will retain proper names for your network devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):429
+msgid "udev loads modules in an unpredictable order"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):432
+msgid "Sometimes udev loads modules in an undesired, unpredictable, or seemingly random order. This is especially common for systems that have multiple devices of the same type, as well as multimedia devices. This can affect the assigned numbers of devices; for example, sound cards may sometimes swap numbers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):439
+msgid "There are a few solutions to fix device numbers and/or module load order. Ideally, you can just use module parameters to specify your desired device number. Some modules, such as ALSA, include the \"index\" parameter. Modules that use the index parameter can be adjusted as shown. This example is for a system with two sound cards. The card with an index of 0 is designated as the first card. Once the parameters are changed, the module config files must be updated."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):448
+msgid "Specifying module parameters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):448
+#, no-wrap
+msgid "\n# <i>echo \"option snd-ice1724 index=0\" &gt;&gt; /etc/modprobe.d/alsa.conf</i>\n# <i>echo \"option snd-ymfpci index=1\" &gt;&gt; /etc/modprobe.d/alsa.conf</i>\n# <i>update-modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):454
+msgid "The above example is the preferred solution, but not all modules support parameters such as index. For these modules, you'll have to force the correct module load order. First, you must stop udev from autoloading the modules by blacklisting them. Be sure to use the exact name of the module being loaded. For PCI devices, you'll need to use the module names obtained from the output of <c>pcimodules</c>, available in the <c>pciutils</c> package. The following example uses DVB modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):464
+msgid "Blacklisting modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):464
+#, no-wrap
+msgid "\n# <i>echo \"blacklist b2c2-flexcop-pci\" &gt;&gt; /etc/modprobe.d/dvb</i>\n# <i>echo \"blacklist budget\" &gt;&gt; /etc/modprobe.d/dvb</i>\n# <i>update-modules</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):470
+msgid "Next, load the modules in the correct order. Add them to <path>/etc/modules.autoload.d/kernel-2.6</path><e>in the exact order you want them loaded</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):476
+msgid "Loading modules in the correct order"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):476
+#, no-wrap
+msgid "\n# <i>echo \"budget\" &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n# <i>echo \"b2c2-flexcop-pci\" &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):484
+msgid "Other issues"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):487
+msgid "If device nodes are not created when a module is loaded from <path>/etc/modules.autoload.d/kernel-2.6</path> but they appear when you load the module manually with modprobe then you should try upgrading to <c>sys-apps/baselayout-1.8.12</c> or later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):494
+msgid "Support for the framebuffer devices (<path>/dev/fb/*</path>) comes with the kernel starting from version 2.6.6-rc2."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):499
+msgid "For kernels older than 2.6.4 you have to explicitly include support for the <path>/dev/pts</path> filesystem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):504
+msgid "Enabling the /dev/pts filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):504
+#, no-wrap
+msgid "\nFile systems ---&gt;\n  Pseudo filesystems ---&gt;\n    [*] /dev/pts file system for Unix98 PTYs\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):515
+msgid "Resources &amp; Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):519
+msgid "The udev talk on the Linux Symposium (Ottawa, Ontario Canada - 2003) given by Greg Kroah-Hartman (IBM Corporation) provided a solid understanding on the udev application."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):525
+msgid "<uri link=\"http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html\">Decibel's UDEV Primer</uri> is an in-depth document about udev and Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):530
+msgid "<uri link=\"http://www.reactivated.net/udevrules.php\">Writing udev rules</uri> by fellow Gentoo developer Daniel Drake is an excellent document to learn how to customize your udev installation."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/uml.xml.pot b/doc/gettext/uml.xml.pot
new file mode 100644
index 0000000..45b463c
--- /dev/null
+++ b/doc/gettext/uml.xml.pot
@@ -0,0 +1,463 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(guide:link):6
+msgid "/doc/en/uml.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):7
+msgid "Gentoo Linux Developer's guide to system testing with User-Mode Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(author:title):9 ../../gentoo/xml/htdocs/doc/en//uml.xml(author:title):12 ../../gentoo/xml/htdocs/doc/en//uml.xml(author:title):15 ../../gentoo/xml/htdocs/doc/en//uml.xml(author:title):18
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail:link):10
+msgid "g2boojum@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail):10
+msgid "Grant Goodyear"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(author):12
+msgid "John Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail:link):16
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail):16
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail:link):19
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(mail):19
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(abstract):22
+msgid "This guide shows Gentoo Linux developers how to set up and use user-mode linux for testing potentially system-breaking changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(version):31
+msgid "0.16"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(date):32
+msgid "2008-03-01"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):35
+msgid "Obtaining User-Mode Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(impo):39
+msgid "Before you can use user-mode Linux, you <e>must</e> be using a non-NPTL profile, and you must be using &lt;<c>glibc</c>-2.4. Follow the instructions for <uri link=\"/doc/en/gentoo-upgrading.xml#instructions\">changing profiles</uri>. You will need to run <c>emerge -e world</c> after switching to a non-NPTL profile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):47
+msgid "As the user-mode Linux website (<uri>http://user-mode-linux.sourceforge.net</uri>) states, user-modeL linux allows a user to \"run Linux inside itself\". Specifically, user-mode linux provides a virtual machine on which a user can \"[r]un buggy software, experiment with new Linux kernels or distributions, and poke around in the internals of Linux, all without risking your main Linux setup.\" Experimental changes to Gentoo core packages such as <e>sys-apps/baselayout</e> or <e>sys-libs/glibc</e> have the potential to break the system and render it unbootable; with user-mode Linux we can test these changes without having to worry about breaking the live system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):60
+msgid "Most 2.6 kernels have UML support. Although you can use your current kernel sources, it might be wiser to keep the UML kernel tree(s) separate. After all, you'll be building a new kernel with a different configuration and you might want to have heterogenous systems on your main Linux system (several different UML kernels)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):68
+msgid "So download a nice kernel tree (like the vanilla one from <uri link=\"http://www.kernel.org\">kernel.org</uri>) and extract it to some local development location."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):74
+msgid "Next, configure this UML kernel as you would do for any other system, but append <e>ARCH=um</e> so that the kernel build software knows that the kernel is meant to run as a guest process on the main system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):80
+msgid "Building the UML kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):80
+#, no-wrap
+msgid "\n# <i>cd /srv/aegis/src/uml-linux</i>\n# <i>make menuconfig <comment>ARCH=um</comment></i>\n# <i>make linux <comment>ARCH=um</comment></i>\n# <i>cp linux /usr/local/bin/linux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(warn):87
+msgid "The <e>ARCH=um</e> fragment is <e>extremely</e> important!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):91
+msgid "On a default Gentoo system, <path>/usr/local/bin</path> is in your <c>$PATH</c>. If it isn't, you should find a definition of <c>PATH</c> in the <path>/etc/profile</path> and fix it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):97
+msgid "Verifying $PATH"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):97
+#, no-wrap
+msgid "\n$ <i>echo $PATH | grep /usr/local/bin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):101
+msgid "Sample definition of $PATH in /etc/profile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):101
+#, no-wrap
+msgid "\nPATH=\"/usr/local/bin:/usr/bin:/bin:${PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):105
+msgid "Don't forget to run <c>source /etc/profile</c> for the change to take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):109
+msgid "For the user-mode Linux kernel to properly boot a Gentoo system the kernel needs to be configured to <e>not</e> automatically mount <path>/dev</path> (devfs) by default. Also, you will almost certainly want to make sure that you have <e>tmpfs</e> (the \"Virtual Memory Filesystem\") compiled in, since by default the Gentoo Linux bootscripts store their information in a small tmpfs partition. (The binary kernels available from the user-mode website do automatically mount <path>/dev</path>, and they don't have tmpfs compiled in; don't bother with them)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):121
+msgid "I highly recommend reading the user-mode linux documentation, but the basic idea is that running the <path>/usr/local/bin/linux</path> program boots the user-mode kernel and tries to bring up the system stored in the file <path>root_fs</path> that should be located in the current working directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):129
+msgid "It won't hurt to also install the user-mode Linux tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):133
+msgid "Installing UML tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):133
+#, no-wrap
+msgid "\n# <i>emerge sys-apps/usermode-utilities</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):137
+msgid "These tools facilitate networking (among other things) between the user-mode Linux virtual system and the host Linux system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):147
+msgid "Creating root_fs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):149
+msgid "Making the Gentoo chroot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):152
+msgid "The <path>root_fs</path> file needed for user-mode linux is a single file that contains an entire Gentoo Linux filesystem. To generate this file you will need to have Loopback device support enabled in the host (non-user-mode) kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):159
+msgid "Generating the <path>root_fs</path> file itself will be our last step. First we will generate a Gentoo filesystem in an ordinary chroot. We need the stage tarball available, which could be downloaded separately, extracted from an Installation CD, or extracted from an Installation CD .iso."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):167
+msgid "Mounting an Installation CD .iso"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):167
+#, no-wrap
+msgid "\n# <i>mkdir /mnt/loop</i>\n# <i>mount -o loop /path/to/install-&lt;TAB&gt;.iso /mnt/loop</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):172
+msgid "Setting up the chroot is essentially identical to an ordinary Gentoo Linux build."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):177
+msgid "Creating the Gentoo chroot mount"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):177
+#, no-wrap
+msgid "\n# <i>mkdir /mnt/gentoo</i>\n# <i>cd /mnt/gentoo</i>\n# <i>tar xvjpf /path/to/stage&lt;TAB&gt;.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):183
+msgid "Go ahead and unmount the .iso. You don't need it anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):187
+msgid "Build the system in the usual fashion: chroot into <path>/mnt/gentoo</path> and follow the Gentoo installation instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):192
+msgid "Add any additional packages you desire. Feel free to give your virtual Gentoo system a hostname, if you so desire. In <path>/etc/fstab</path> you will want <path>/dev/ROOT</path> to be <path>/dev/ubda</path>, with a fs type of either ext2, ext3, or reiserfs. Set <path>/dev/SWAP</path> to be <path>/dev/ubdb</path>, and comment out <path>/dev/BOOT</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):200
+msgid "At this point, remember to set your root password."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):204
+msgid "Setting root password"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):204
+#, no-wrap
+msgid "\n# <i>passwd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):208
+msgid "Now we need to make some changes to the boot scripts. Remove consolefont and keymaps from the boot runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):213
+msgid "Removing unneeded initscripts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):213
+#, no-wrap
+msgid "\n# <i>rc-update del consolefont boot</i>\n# <i>rc-update del keymaps boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):218
+msgid "Exit the chroot, unmount all of the bind mounts, tar up the new Gentoo distro, and clean up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):223
+msgid "Finalising the installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):223
+#, no-wrap
+msgid "\n# <i>cd /mnt/gentoo</i>\n# <i>tar cvjpf ~/gentoo.tbz2 *</i>\n# <i>cd</i>\n# <i>rm -rf /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):233
+msgid "Making root_fs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):236
+msgid "Our Gentoo chroot is nearly 300 MB in size, so <path>root_fs</path> needs to be at least that size. We'll choose 0.5 GB as a reasonable size."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):242
+msgid "Creating UML files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):242
+#, no-wrap
+msgid "\n# <i>dd if=/dev/zero of=root_fs seek=500 count=1 bs=1M</i>\n# <i>mke2fs -F root_fs</i>\n# <i>mount -o loop root_fs /mnt/loop</i>\n# <i>tar xvjpf gentoo.tbz2 -C /mnt/loop</i>\n# <i>umount /mnt/loop</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):250
+msgid "It would also be nice to have a 0.5 GB swap partition."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):254
+msgid "Create swap partition"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):254
+#, no-wrap
+msgid "\n# <i>dd if=/dev/zero of=swap_fs seek=500 count=1 bs=1M</i>\n# <i>mkswap -f swap_fs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):259
+msgid "Now see if it works!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):263
+msgid "Start UML kernel thread"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):263
+#, no-wrap
+msgid "\n# <i>linux ubd0=root_fs ubd1=swap_fs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):267
+msgid "User-mode Linux uses xterms for the virtual consoles that are run at boot time, so you need to make sure that the terminal from which you run user-mode Linux has $DISPLAY properly set (along with proper xhost/xauth permissions)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):274
+msgid "With any luck you should be able to log into your user-mode Linux Gentoo system. The only thing keeping this user-mode Linux version of Gentoo from being fully functional is networking from the virtual machine to the host."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(note):281
+msgid "If you receive \"No space left on device\" errors, you may need to allocate more memory to your user mode system by appending <c>mem=xxxMB</c> to the end of the kernel thread line. For example: <c>linux ubd0=root_fs ubd1=swap_fs mem=128MB</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):293
+msgid "Networking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):295
+msgid "Using an Existing Network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):298
+msgid "Make sure that the host kernel has the following settings compiled as modules:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):302
+msgid "Host kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):302
+#, no-wrap
+msgid "\nNetworking --&gt;\n  IP: Netfilter Configuration --&gt;\n    IP tables support --&gt;\n      Full NAT --&gt;\n        &lt;M&gt; MASQUERADE target support \n    \n    Network Device Support --&gt; \n      &lt;M&gt; TUN/TAP Support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):313
+msgid "Run the following commands on the <e>host</e> machine:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):317
+msgid "Setup networking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):317
+#, no-wrap
+msgid "\n# <i>modprobe tun</i>\n<comment>(If you receive a FATAL error here, try deleting /dev/net/tun and retry)</comment>\n# <i>modprobe iptable_nat</i>\n# <i>iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE</i>\n# <i>echo 1 &gt; /proc/sys/net/ipv4/ip_forward</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):325
+msgid "The iptables line sets up IP Masquerading between the private network that our user-mode system will be on and the internet (reachable via <c>eth0</c> in our case). The echo line then turns on packet forwarding between the private network and the interface that the default gateway is on (eth0 for us)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):333
+msgid "Now we bring up the user-mode system and see if networking is functional."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):338
+msgid "Get UML up and running"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):338
+#, no-wrap
+msgid "\n# <i>linux ubd0=root_fs ubd1=swap_fs eth0=tuntap,,,192.168.0.254</i>\n<comment>(login to user-mode system)</comment>\n# <i>ifconfig eth0 192.168.0.1 up</i>\n# <i>ping -c 2 192.168.0.254</i>\nPING 192.168.0.254 (192.168.0.254): 56 octets data\n64 octets from 192.168.0.254: icmp_seq=0 ttl=255 time=0.8 ms\n64 octets from 192.168.0.254: icmp_seq=1 ttl=255 time=0.6 ms\n\n--- 192.168.0.254 ping statistics ---\n2 packets transmitted, 2 packets received, 0% packet loss\nround-trip min/avg/max = 0.6/0.7/0.8 ms\n# <i>route add default gw 192.168.0.254</i>\n# <i>netstat -rn</i>\nKernel IP routing table\nDestination  Gateway        Genmask        Flags MSS Window irtt Iface\n192.168.0.0  0.0.0.0        255.255.255.0  U      40 0         0 eth0\n0.0.0.0      192.168.0.254  0.0.0.0        UG     40 0         0 eth0\n# <i>scp user@192.168.0.254:/etc/resolv.conf /etc/resolv.conf</i> <comment>(if needed)</comment>\n# <i>ping -c 2 www.gentoo.org</i>\nPING www.gentoo.org (207.170.82.202): 56 octets data\n64 octets from 207.170.82.202: icmp_seq=0 ttl=240 time=119.6 ms\n64 octets from 207.170.82.202: icmp_seq=1 ttl=240 time=92.0 ms\n\n--- www.gentoo.org ping statistics ---\n2 packets transmitted, 2 packets received, 0% packet loss\nround-trip min/avg/max = 92.0/105.8/119.6 ms\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):367
+msgid "On the user-mode system we assign the user-mode eth0 interface the private IP address 192.168.0.1 and bring up the interface. The host has private IP address 192.168.0.254, and we ping it to make sure that our networking is, indeed, up. The route line adds a default gateway, namely our host, we use scp to retrieve a working <path>/etc/resolv.conf</path> (if necessary), and we ping www.gentoo.org to make sure that name resolution (and general access to the internet) is working from our user-mode system. Now the user-mode system can <c>emerge</c> at will!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):382
+msgid "Using a Virtual Network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):385
+msgid "Before you get all too excited, this is not a virtual private network. It is a network that is only accessible by the UML instances. The <c>usermode-utilities</c> package provides a tool called <c>uml_switch</c> which defines the end points of the switch."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):392
+msgid "Activating end points of a UML switch"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):392
+#, no-wrap
+msgid "\n<comment>(If the switch information should stay in the foreground:)</comment>\n$ <i>uml_switch -unix ~/tmp/switch.sock</i>\n\n<comment>(If it should be backgrounded:)</comment>\n$ <i>uml_switch -unix ~/tmp/switch.sock &amp;&gt; ~/tmp/switch.log &amp;</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):400
+msgid "To start the UML instances on the switch, run the next command. Your (virtual) network interface will be connected to the <c>uml_switch</c> process and will be using the given MAC address."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):406
+msgid "Running first UML instance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):406
+#, no-wrap
+msgid "\n$ <i>linux ubd0=first_rootfs ubd1=first_swapfs eth0=daemon,10:00:01:02:00:00,,~/tmp/switch.sock</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):410
+msgid "You can still connect the system to the existing network, or have a second process attached to both the virtual one and the existing one:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):415
+msgid "Running second UML instance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):415
+#, no-wrap
+msgid "\n$ <i>linux ubd0=second_rootfs ubd1=second_swapfs eth0=daemon,10:00:01:02:00:01,,~/tmp/switch.sock \\\n  eth1=tuntap,,,192.168.1.43</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):420
+msgid "More information about the tuntap setting can be found in the previous section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):428
+msgid "Testing the .iso"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):432
+msgid "Perhaps the true ideal of Gentoo Linux testing would be to boot the .iso with user-mode Linux and do the complete Gentoo install from within the user-mode Linux virtual system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):438
+msgid "Booting the .iso, or actually the initrd from the .iso, is pretty straightforward."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre:caption):443
+msgid "Booting the ISO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(pre):443
+#, no-wrap
+msgid "\n# <i>mount -o loop /path/to/install-&lt;TAB&gt;.iso /mnt/loop</i>\n# <i>cp /mnt/loop/isolinux/gentoo.igz .</i>\n# <i>linux load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=22000 \\</i>\n&gt; <i>initrd=rescue.gz root=/dev/ram0 ubd0=root_fs ubd1=swap_fs \\</i>\n&gt; <i>ubd2=/dev/cdroms/cdrom0 eth0=tuntap,,,192.168.0.254</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(p):451
+msgid "Now you can follow the Gentoo install doc essentially verbatim, although you'll need to know that the root filesystem will be <path>/dev/ubd/0</path>, the swap \"partition\" will be <path>/dev/ubd/1</path>, and the CD rom will be <path>/dev/ubd/2</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(title):464
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri:link):470
+msgid "http://edeca.net/articles/bridging/index.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri):470
+msgid "Bridging with UML"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri:link):474
+msgid "http://user-mode-linux.sourceforge.net/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri):474
+msgid "UML Homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri:link):477
+msgid "http://www.theshore.net/~caker/uml/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri):477
+msgid "Caker's UML Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri:link):480
+msgid "http://sourceforge.net/mailarchive/forum.php?forum_id=3647"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(uri):480
+msgid "UML Mailinglist archives"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//uml.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/usb-guide.xml.pot b/doc/gettext/usb-guide.xml.pot
new file mode 100644
index 0000000..667930e
--- /dev/null
+++ b/doc/gettext/usb-guide.xml.pot
@@ -0,0 +1,380 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(guide:link):5
+msgid "/doc/en/usb-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):6
+msgid "Gentoo Linux USB Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(mail:link):9
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(mail):9
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(abstract):12
+msgid "This document helps a user setup USB on a Gentoo system and configure various USB devices as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(version):21
+msgid "1.15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(date):22
+msgid "2009-11-29"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):25
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):27
+msgid "What is USB?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):30
+msgid "USB stands for Universal Serial Bus and is basically an external interface standard that enables communication between the computer and various other peripherals. Some of the most commonly used USB devices today are keyboards, mice, pen drives, digital cameras, external CD &amp; DVD writers, printers etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):37
+msgid "There are currently two versions of USB in use, i.e. USB 1.1 and USB 2.0. Since USB has always been backward compatible with its previous versions, USB 2.0 is backwards compatible with USB 1.1. The latest USB devices are typically USB 2.0 compatible. USB 2.0 supports a maximum data transmission speed of 480 Mbps or 60 MBps and this is the major difference between the two standards. Another advantage with USB is that the devices are all <e>hot-pluggable</e>, which means that you do not have to restart your system in order for you to be able to use these devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):51
+msgid "A Technical Perspective"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):54
+msgid "Before we go onto the exact configuration options in the kernel, it would be apt to look at USB in a little more detail. If you're in a hurry or want to skip this section, please go to <uri link=\"#kernel\">Kernel Configuration</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):61
+msgid "A USB system has a host controller, hubs, a <e>root hub</e> amongst others and can support up to 127 USB devices including the hubs. The host controller is nothing but the hardware interface between the USB device and the operating system. There are a couple of HCI (Host Controller Interface) in use today and they are the OHCI (Open HCI) by Compaq, UHCI (Universal HCI) and EHCI (Enhanced HCI), both from Intel. The OHCI/UHCI are the two industry standard USB 1.1 interfaces whereas the EHCI is for USB 2.0."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):71
+msgid "The hardware vendor provides an interface for the programmer that allows the system to interact with the hardware and this is called the HCD or Host Controller Device. It is through this HCD that the device interacts with the system software. The following diagram should make things easier to comprehend."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):78
+msgid "General USB Architecture"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):78
+#, no-wrap
+msgid "\n<comment>(Software consists of other components as well like the device driver, but\nfor the sake of simplicity, they are not shown)</comment>\n\n    + ----  Hardware  ----   + ----  Software  ---- +\n    |                        |                      |\n    | [USB Dev] -+-&gt; {EHCI} -+---&gt;  ( EHCD )        |\n    |            |           |                      |  User\n    |            `-&gt; {UHCI} -+---&gt;  ( UHCD )        |\n    |                        |                      |\n    + ----  Hardware  ----   + ----  Software  ---- +\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):91
+msgid "A USB device can either use a custom driver or use one already present in the system and this is based on the concept of a device <e>class</e>. This means that if a device belongs to a certain <e>class</e>, then other devices belonging to the same <e>class</e> can make use of the same device driver. Some of these <e>classes</e> are the USB HID (Human Interface Devices) class which covers input devices like keyboards and mice, the USB Mass Storage devices class which covers devices like pen drives, digital cameras, audio players etc and the USB CDC (Communication Devices Class) which essentially covers USB modems and similar devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):106
+msgid "What's on your machine?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):109
+msgid "It is very simple to find out whether your machine has USB 2.0 support or not. We make use of the <c>lspci</c> command for this purpose."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):114
+msgid "The <c>lspci</c> tool is a part of the <c>sys-apps/pciutils</c> package. If you do not have this installed, please <c>emerge pciutils</c>. Please note that you have to be root while running the <c>lspci</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):120
+msgid "Various lspci outputs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):120
+#, no-wrap
+msgid "\n<comment>(In system that is USB 1.1 compliant, note the UHCI only)</comment>\n\n# <i>lspci -v | grep USB</i>\n0000:00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])\n\n<comment>(A system that is USB 2.0 compliant, note the EHCI and UHCI)</comment>\n\n00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 01) (prog-if 00 [UHCI])\n00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 01) (prog-if 00 [UHCI])\n00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 01) (prog-if 00 [UHCI])\n00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 01) (prog-if 20 [EHCI])\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):134
+msgid "So using the <c>lspci</c> command, we can find out if the system supports USB 2.0. This is useful as we will be enabling the corresponding options in the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):145
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):147
+msgid "Getting the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):150
+msgid "First emerge the kernel sources of your choice. Here we'll use the <c>gentoo-sources</c>. For more information on the various kernel sources available on Portage, please look up the <uri link=\"/doc/en/gentoo-kernel.xml\">Gentoo Linux Kernel Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):157
+msgid "Getting the kernel sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):157
+#, no-wrap
+msgid "\n# <i>emerge gentoo-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):161
+msgid "Now, lets get on with the task of configuring the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):165
+msgid "Heading over to the source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):165
+#, no-wrap
+msgid "\n# <i>cd /usr/src/linux</i>\n# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):170
+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//usb-guide.xml(title):178
+msgid "Config options for the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):181
+msgid "Now we will look at some of the options we will have to enable in the kernel to ensure proper USB support for our devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):186
+msgid "Examples in this document will show configuration options for basic USB support as well as those needed commonly, for example a USB mass storage device (most cameras and USB pen drives). If you have a specific USB device that needs to be configured, please look up your device's manual or search online to see if that device has support built-in into the kernel or custom drivers that you can use. Please note that for the sake of ease, all examples have the options compiled into the kernel. If you would like to have a modular kernel, ensure that you note down the various modules and adjust your config files accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):198
+msgid "make menuconfig options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):198
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n  SCSI device support  ---&gt;\n\n<comment>(Although SCSI will be enabled automatically when selecting USB Mass Storage,\nwe need to enable disk support.)</comment>\n---   SCSI support type (disk, tape, CD-ROM)\n&lt;*&gt;   SCSI disk support\n\n<comment>(Then move back a level and go into USB support)</comment>\nUSB support  ---&gt;\n\n<comment>(This is the root hub and is required for USB support.\nIf you'd like to compile this as a module, it will be called usbcore.)</comment>\n&lt;*&gt; Support for Host-side USB\n\n<comment>(Select at least one of the HCDs. If you are unsure, picking all is fine.)</comment>\n--- USB Host Controller Drivers\n&lt;*&gt; EHCI HCD (USB 2.0) support\n&lt; &gt; OHCI HCD support\n&lt;*&gt; UHCI HCD (most Intel and VIA) support\n\n<comment>(Moving a little further down, we come to CDC and mass storage.)</comment>\n&lt; &gt; USB Modem (CDC ACM) support\n&lt;*&gt; USB Printer support\n&lt;*&gt; USB Mass Storage support\n\n<comment>(If you have a USB Network Card like the RTL8150, you'll need this)</comment>\nUSB Network Adapters  ---&gt;\n    &lt;*&gt; USB RTL8150 based ethernet device support (EXPERIMENTAL)\n\n<comment>(If you have a serial to USB converter like the Prolific 2303, you'll need this)</comment>\nUSB Serial Converter support  ---&gt;\n    &lt;*&gt; USB Serial Converter support\n    &lt;*&gt; USB Prolific 2303 Single Port Serial Driver (NEW)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):235
+msgid "If you have a USB keyboard, mouse, joystick, or any other input device, you need to enable HID support. Go back one level to \"Device drivers\" and enable HID support as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):241
+msgid "Enabling HID support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):241
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\n  [*] HID Devices  ---&gt;\n    &lt;*&gt;   USB Human Interface Device (full HID) support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):247
+msgid "Now that your options are set, you can (re)compile the kernel and USB support should be functional once you reboot into the new kernel. You can now proceed to <uri link=\"#postkern\">Seeing USB at work</uri> and see if everything is working as it should."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):259
+msgid "Seeing USB at work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):261
+msgid "dmesg is your friend!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):264
+msgid "The time has finally come to play with those USB devices :) So let's get started. In this chapter, we'll see how the system responds to various USB devices. We'll start by plugging in a USB 512 MB Memory Stick/Pen Drive. You could use some other similar mass storage device. We will primarily use <c>dmesg</c> to see what is happening and how the system responds to the device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):273
+msgid "<c>dmesg</c> will generally give a lot of output up front before coming to the info we need, as it reads the kernel ring buffer that has all the boot up messages as well. The output in the following examples have only the relevant portion(s) and extra spaces in between to enable better readability. If needed please use a <c>dmesg | more</c> or <c>dmesg | less</c> to see the output better in your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):282
+msgid "dmesg output for Memory Stick"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):282
+#, no-wrap
+msgid "\n<comment>(Plug in Memory Stick into available USB port and then..)</comment>\n# <i>dmesg | less</i>\n\n<comment>(The device is picked up as a USB 1.1 and allocated an address.\nAlso says what HCD it is using.)</comment>\nusb 1-1: new full speed USB device using uhci_hcd and address 2\n\n<comment>(SCSI emulation automatically kicks in)</comment>\nscsi0 : SCSI emulation for USB Mass Storage devices\nusb-storage: device found at 2\n\n<comment>(Now the device information including model number is retrieved)</comment>\nusb-storage: waiting for device to settle before scanning\n  Vendor: JetFlash  Model: TS512MJF2A        Rev: 1.00\n  Type:   Direct-Access                      ANSI SCSI revision: 02\nSCSI device sda: 1003600 512-byte hdwr sectors (514 MB)\n\n<comment>(The write-protect sense is EXPERIMENTAL code in the later kernels)</comment>\nsda: Write Protect is off\nsda: Mode Sense: 0b 00 00 08\nsda: assuming drive cache: write through\nSCSI device sda: 1003600 512-byte hdwr sectors (514 MB)\n/dev/scsi/host0/bus0/target0/lun0: p1\nAttached scsi removable disk sda at scsi0, channel 0, id 0, lun 0\nAttached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0\nusb-storage: device scan complete\n<comment>(At this point, the device is generally accessible by mounting /dev/sda1)</comment>\n\n<comment>(When the device is disconnected, the system acknowledges the same)</comment>\nusb 1-1: USB disconnect, address 2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):315
+msgid "Once the device is connected and mounted, you can access it like a normal hard disk. Usual operations like <c>cp</c>, <c>mv</c>, <c>rm</c>, etc work fine. You could also create a filesystem on the USB stick/format it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):321
+msgid "Accessing the Memory Stick"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):321
+#, no-wrap
+msgid "\n# <i>mount /dev/sda1 /mnt/usb</i>\n# <i>df -h</i>\nFilesystem            Size  Used Avail Use% Mounted on\n/dev/hda8             9.4G  7.5G  1.9G  80% /\n/dev/hda9              11G  8.1G  2.4G  78% /usr\nnone                  189M     0  189M   0% /dev/shm\n/dev/sda1             490M   34M  457M   7% /mnt/usb\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):331
+msgid "Digital cameras can be accessed the same way as memory sticks. I have a Nikon Coolpix 5200 and this is the way I access it. Cameras these days usually have two modes to transfer pictures; USB mass storage and PTP (Picture Transfer Protocol). The camera is set to USB mass storage mode and hence the procedure is exactly the same as that of accessing a memory stick because of which I have not explained in detail about it. Please note that this may NOT work in all cases and with all digital cameras that have USB support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):341
+msgid "How would a USB mouse show up in case you had one? It will show up as an HID device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):346
+msgid "USB Optical Mouse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):346
+#, no-wrap
+msgid "\n# <i>dmesg | grep USB</i>\ndrivers/usb/input/hid-core.c: v2.0:USB HID core driver\nusb 1-1: new low speed USB device using address 2\ninput: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:07.2-1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):353
+msgid "Another nifty command you can use to see the status of your USB ports is <c>lsusb</c>. This is part of <c>sys-apps/usbutils</c> and will be covered in the next chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):364
+msgid "Userspace USB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):366
+msgid "Nifty tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):369
+msgid "So far we've seen how much support exists on the kernel/system side for USB on Linux. Now we'll take a peek into what kind of support is provided by Gentoo for USB in the userspace."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):375
+msgid "One of the most useful tools around is <c>lsusb</c>. This lists all the usb devices connected to the system. Installing it is a breeze."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):380
+msgid "Installing usbutils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):380
+#, no-wrap
+msgid "\n# <i>emerge usbutils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):384
+msgid "Once installed, you can just run <c>lsusb</c> to get simple info on the USB devices attached to the machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(note):389
+msgid "You have to be root in most cases to run <c>lsusb</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(warn):393
+msgid "<c>lsusb</c> reads the information for the USB devices from <path>/proc/bus/usb</path>. If you have not enabled that in your kernel, chances are that <c>lsusb</c> may not work at all. Please ensure you have <path>/proc</path> filesystem support enabled in your kernel and that <c>usbfs</c> is mounted at <path>/proc/bus/usb</path> (which should happen automatically)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):402
+msgid "lsusb at work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):402
+#, no-wrap
+msgid "\n# <i>lsusb</i>\n<comment>(This is the 512 MB Memory Stick from Transcend)</comment>\nBus 001 Device 003: ID 0c76:0005 JMTek, LLC. USBdisk\n<comment>(This is the Optical Mouse)</comment>\nBus 001 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse\n<comment>(This is the root hub)</comment>\nBus 001 Device 001: ID 0000:0000\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):412
+msgid "If you are one of those types who love to see lots of information, you have the option of running <c>lsusb -v</c>. Try that and see the amount of info it gives out. Another good option is that <c>lsusb</c> dumps the current physical USB hierarchy as a tree and thus makes it easier to understand the exact device map. The command is <c>lsusb -t</c>. For example,"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre:caption):420
+msgid "lsusb showing USB hierarchy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(pre):420
+#, no-wrap
+msgid "\n# <i>lsusb -t</i>\nBus#  1\n`-Dev#   1 Vendor 0x0000 Product 0x0000\n  |-Dev#   2 Vendor 0x046d Product 0xc00e\n  `-Dev#   3 Vendor 0x0c76 Product 0x0005\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):428
+msgid "You can easily correlate the outputs of <c>lsusb</c> and <c>lsusb -t</c>, which helps debugging as well as understanding how USB works."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):438
+msgid "And thanks to..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):440
+msgid "References"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(p):443
+msgid "A good number of online documents helped me during the development of this document and there are some that are highly technical but truly interesting. I thought they all deserve some credit, so here we go!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):450
+msgid "http://www.usb.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):450
+msgid "The Official USB Website"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):451
+msgid "http://www.usb.org/about/faq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):451
+msgid "The USB FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):454
+msgid "http://h18000.www1.hp.com/productinfo/development/openhci.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):454
+msgid "Compaq's OHCI Standard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):458
+msgid "http://developer.intel.com/technology/usb/uhci11d.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):458
+msgid "Intel's UHCI Standard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):462
+msgid "http://www.intel.com/technology/usb/ehcispec.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):462
+msgid "Intel's EHCI Standard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(title):470
+msgid "Other Interesting Links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri:link):474
+msgid "/doc/en/liveusb.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(uri):474
+msgid "Gentoo Linux LiveUSB HOWTO"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//usb-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/utf-8.xml.pot b/doc/gettext/utf-8.xml.pot
new file mode 100644
index 0000000..031e2db
--- /dev/null
+++ b/doc/gettext/utf-8.xml.pot
@@ -0,0 +1,726 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):6
+msgid "Using UTF-8 with Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail:link):9
+msgid "slarti@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail):9
+msgid "Thomas Martin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(author:title):11
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail:link):12
+msgid "devil@gentoo.org.ua"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail):12
+msgid "Alexander Simonov"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//utf-8.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail:link):15
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail):15
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(mail:link):18
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(abstract):21
+msgid "This guide shows you how to set up and use the UTF-8 Unicode character set with your Gentoo Linux system, after explaining the benefits of Unicode and more specifically UTF-8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(version):31
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(date):32
+msgid "2010-09-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):35
+msgid "Character Encodings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):37
+msgid "What is a Character Encoding?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):40
+msgid "Computers do not understand text themselves. Instead, every character is represented by a number. Traditionally, each set of numbers used to represent alphabets and characters (known as a coding system, encoding or character set) was limited in size due to limitations in computer hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):50
+msgid "The History of Character Encodings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):53
+msgid "The most common (or at least the most widely accepted) character set is <b>ASCII</b> (American Standard Code for Information Interchange). It is widely held that ASCII is the most successful software standard ever. Modern ASCII was standardised in 1986 (ANSI X3.4, RFC 20, ISO/IEC 646:1991, ECMA-6) by the American National Standards Institute."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):61
+msgid "ASCII is strictly seven-bit, meaning that it uses bit patterns representable with seven binary digits, which provides a range of 0 to 127 in decimal. These include 32 non-visible control characters, most between 0 and 31, with the final control character, DEL or delete at 127. Characters 32 to 126 are visible characters: a space, punctuation marks, Latin letters and numbers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):69
+msgid "The eighth bit in ASCII was originally used as a parity bit for error checking. If this is not desired, it is left as 0. This means that, with ASCII, each character is represented by a single byte."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):75
+msgid "Although ASCII was enough for communication in modern English, in other European languages that include accented characters, things were not so easy. The ISO 8859 standards were developed to meet these needs. They were backwards compatible with ASCII, but instead of leaving the eighth bit blank, they used it to allow another 127 characters in each encoding. ISO 8859's limitations soon came to light, and there are currently 15 variants of the ISO 8859 standard (8859-1 through to 8859-15). Outside of the ASCII-compatible byte range of these character sets, there is often conflict between the letters represented by each byte. To complicate interoperability between character encodings further, Windows-1252 is used in some versions of Microsoft Windows instead for Western European languages. This is a superset of ISO 8859-1, however it is different in several ways. These sets do all retain ASCII compatibility, however."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):91
+msgid "The necessary development of completely different single-byte encodings for non-Latin alphabets, such as EUC (Extended Unix Coding) which is used for Japanese and Korean (and to a lesser extent Chinese) created more confusion, while other operating systems still used different character sets for the same languages, for example, Shift-JIS and ISO-2022-JP. Users wishing to view cyrillic glyphs had to choose between KOI8-R for Russian and Bulgarian or KOI8-U for Ukrainian, as well as all the other cyrillic encodings such as the unsuccessful ISO 8859-5, and the common Windows-1251 set. All of these character sets broke most compatibility with ASCII (although KOI8 encodings place cyrillic characters in Latin order, so in case the eighth bit is stripped, text is still decipherable on an ASCII terminal through case-reversed transliteration.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):106
+msgid "This has led to confusion, and also to an almost total inability for multilingual communication, especially across different alphabets. Enter Unicode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):115
+msgid "What is Unicode?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):118
+msgid "Unicode throws away the traditional single-byte limit of character sets. It uses 17 \"planes\" of 65,536 code points to describe a maximum of 1,114,112 characters. As the first plane, aka. \"Basic Multilingual Plane\" or BMP, contains almost everything you will ever use, many have made the wrong assumption that Unicode was a 16-bit character set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):126
+msgid "Unicode has been mapped in many different ways, but the two most common are <b>UTF</b> (Unicode Transformation Format) and <b>UCS</b> (Universal Character Set). A number after UTF indicates the number of bits in one unit, while the number after UCS indicates the number of bytes. UTF-8 has become the most widespread means for the interchange of Unicode text as a result of its eight-bit clean nature, and it is the subject of this document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):138
+msgid "UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):141
+msgid "UTF-8 is a variable-length character encoding, which in this instance means that it uses 1 to 4 bytes per symbol. So, the first UTF-8 byte is used for encoding ASCII, giving the character set full backwards compatibility with ASCII. UTF-8 means that ASCII and Latin characters are interchangeable with little increase in the size of the data, because only the first bit is used. Users of Eastern alphabets such as Japanese, who have been assigned a higher byte range are unhappy, as this results in as much as a 50% redundancy in their data."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):155
+msgid "What UTF-8 Can Do for You"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):158
+msgid "UTF-8 allows you to work in a standards-compliant and internationally accepted multilingual environment, with a comparatively low data redundancy. UTF-8 is the preferred way for transmitting non-ASCII characters over the Internet, through Email, IRC or almost any other medium. Despite this, many people regard UTF-8 in online communication as abusive. It is always best to be aware of the attitude towards UTF-8 in a specific channel, mailing list or Usenet group before using <e>non-ASCII</e> UTF-8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):173
+msgid "Setting up UTF-8 with Gentoo Linux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):175
+msgid "Finding or Creating UTF-8 Locales"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):178
+msgid "Now that you understand the principles behind Unicode, you're ready to start using UTF-8 with your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):183
+msgid "The preliminary requirement for UTF-8 is to have a version of glibc installed that has national language support. The recommend means to do this is the <path>/etc/locale.gen</path> file. It is beyond the scope of this document to explain the usage of this file though. It is explained in the <uri link=\"/doc/en/guide-localization.xml#doc_chap3_sect3\">Gentoo Localization Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):192
+msgid "Next, we'll need to decide whether a UTF-8 locale is already available for our language, or whether we need to create one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):197
+msgid "Checking for an existing UTF-8 locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):197
+#, no-wrap
+msgid "\n<comment>(Replace \"en_GB\" with your desired locale setting)</comment>\n# <i>locale -a | grep 'en_GB'</i>\nen_GB\nen_GB.UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):204
+msgid "From the output of this command line, we need to take the result with a suffix similar to <c>.UTF-8</c>. If there is no result with a suffix similar to <c>.UTF-8</c>, we need to create a UTF-8 compatible locale."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):210
+msgid "Only execute the following code listing if you do not have a UTF-8 locale available for your language."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):215
+msgid "Creating a UTF-8 locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):215
+#, no-wrap
+msgid "\n<comment>(Replace \"en_GB\" with your desired locale setting)</comment>\n# <i>localedef -i en_GB -f UTF-8 en_GB.UTF-8</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):220
+msgid "Another way to include a UTF-8 locale is to add it to the <path>/etc/locale.gen</path> file and generate necessary locales with <c>locale-gen</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):226
+msgid "Line in /etc/locale.gen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):226
+#, no-wrap
+msgid "\nen_GB.UTF-8 UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):233
+msgid "Setting the Locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):236
+msgid "There is one environment variable that needs to be set in order to use our new UTF-8 locales: <c>LC_CTYPE</c> (or optionally <c>LANG</c>, if you want to change the system language as well). There are also many different ways to set it; some people prefer to only have a UTF-8 environment for a specific user, in which case they set them in their <path>~/.profile</path> (if you use <c>/bin/sh</c>), <path>~/.bash_profile</path> or <path>~/.bashrc</path> (if you use <c>/bin/bash</c>). More details and best practices can be found in our <uri link=\"/doc/en/guide-localization.xml\">Localization Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):247
+msgid "Others prefer to set the locale globally. One specific circumstance where the author particularly recommends doing this is when <path>/etc/init.d/xdm</path> is in use, because this init script starts the display manager and desktop before any of the aforementioned shell startup files are sourced, and so before any of the variables are in the environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):256
+msgid "Setting the locale globally should be done using <path>/etc/env.d/02locale</path>. The file should look something like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):262
+msgid "Demonstration /etc/env.d/02locale"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):262
+#, no-wrap
+msgid "\n<comment>(As always, change \"en_GB.UTF-8\" to your locale)</comment>\nLANG=\"en_GB.UTF-8\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):267
+msgid "You can also substitute <c>LC_CTYPE</c> for <c>LANG</c>. For more information on the categories affected by using <c>LC_CTYPE</c>, please read the <uri link=\"http://www.gnu.org/software/libc/manual/html_node/Locale-Categories.html#Locale-Categories\">GNU locale page</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):274
+msgid "Next, the environment must be updated with the change."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):278
+msgid "Updating the environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):278
+#, no-wrap
+msgid "\n# <i>env-update</i>\n&gt;&gt;&gt; Regenerating /etc/ld.so.cache...\n * Caching service dependencies ...\n# <i>source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):285
+msgid "Now, run <c>locale</c> with no arguments to see if we have the correct variables in our environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):290
+msgid "Checking if our new locale is in the environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):290
+#, no-wrap
+msgid "\n# <i>locale</i>\nLANG=en_GB.UTF-8\nLC_CTYPE=\"en_GB.UTF-8\"\nLC_NUMERIC=\"en_GB.UTF-8\"\nLC_TIME=\"en_GB.UTF-8\"\nLC_COLLATE=\"en_GB.UTF-8\"\nLC_MONETARY=\"en_GB.UTF-8\"\nLC_MESSAGES=\"en_GB.UTF-8\"\nLC_PAPER=\"en_GB.UTF-8\"\nLC_NAME=\"en_GB.UTF-8\"\nLC_ADDRESS=\"en_GB.UTF-8\"\nLC_TELEPHONE=\"en_GB.UTF-8\"\nLC_MEASUREMENT=\"en_GB.UTF-8\"\nLC_IDENTIFICATION=\"en_GB.UTF-8\"\nLC_ALL=\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):308
+msgid "That's everything. You are now using UTF-8 locales, and the next hurdle is the configuration of the applications you use from day to day."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):318
+msgid "Application Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):322
+msgid "When Unicode first started gaining momentum in the software world, multibyte character sets were not well suited to languages like C, in which many of the day-to-day programs people use are written. Even today, some programs are not able to handle UTF-8 properly. Fortunately, most are!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):332
+msgid "Filenames, NTFS, and FAT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):335
+msgid "There are several NLS options in the Linux kernel configuration menu, but it is important to not become confused! For the most part, the only thing you need to do is to build UTF-8 NLS support into your kernel, and change the default NLS option to utf8."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):342
+msgid "Kernel configuration steps for UTF-8 NLS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):342
+#, no-wrap
+msgid "\nFile Systems --&gt;\n  Native Language Support --&gt;\n    (utf8) Default NLS Option\n    &lt;*&gt; NLS UTF8\n    <comment>(Also &lt;*&gt; other character sets that are in use in\n    your FAT filesystems or Joilet CD-ROMs.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):351
+msgid "If you plan on mounting NTFS partitions, you may need to specify an <c>nls=</c> option with mount. If you plan on mounting FAT partitions, you may need to specify a <c>codepage=</c> option with mount. Optionally, you can also set a default codepage for FAT in the kernel configuration. Note that the <c>codepage</c> option with mount will override the kernel settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):359
+msgid "FAT settings in kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):359
+#, no-wrap
+msgid "\nFile Systems --&gt;\n  DOS/FAT/NT Filesystems  --&gt;\n    (437) Default codepage for fat\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):365
+msgid "You should avoid setting <c>Default iocharset for fat</c> to UTF-8, as it is not recommended. Instead, you may want to pass the option utf8=true when mounting your FAT partitions. For further information, see <c>man mount</c> and the kernel documentation at <path>/usr/src/linux/Documentation/filesystems/vfat.txt</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):373
+msgid "For changing the encoding of filenames, <c>app-text/convmv</c> can be used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):377
+msgid "Example usage of convmv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):377
+#, no-wrap
+msgid "\n# <i>emerge --ask app-text/convmv</i>\n<comment>(Command format)</comment>\n# <i>convmv -f &lt;current-encoding&gt; -t utf-8 &lt;filename&gt;</i>\n<comment>(Substitute iso-8859-1 with the charset you are converting\nfrom)</comment>\n# <i>convmv -f iso-8859-1 -t utf-8 filename</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):386
+msgid "For changing the <e>contents</e> of files, use the <c>iconv</c> utility, bundled with <c>glibc</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):391
+msgid "Example usage of iconv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):391
+#, no-wrap
+msgid "\n<comment>(substitute iso-8859-1 with the charset you are converting from)</comment>\n<comment>(Check the output is sane)</comment>\n# <i>iconv -f iso-8859-1 -t utf-8 filename</i>\n<comment>(Convert a file, you must create another file)</comment>\n# <i>iconv -f iso-8859-1 -t utf-8 filename &gt; newfile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):399
+msgid "<c>app-text/recode</c> can also be used for this purpose."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):406
+msgid "The System Console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(impo):409
+msgid "You need &gt;=sys-apps/baselayout-1.11.9 for Unicode on the console."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):413
+msgid "To enable UTF-8 on the console, you should edit <path>/etc/rc.conf</path> and set <c>UNICODE=\"yes\"</c>, and also read the comments in that file -- it is important to have a font that has a good range of characters if you plan on making the most of Unicode. For this to work, make sure you have properly created a Unicode locale as explained in <uri link=\"#doc_chap1\">Chapter 1</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):422
+msgid "The <c>KEYMAP</c> variable, set in <path>/etc/conf.d/keymaps</path>, should have a Unicode keymap specified."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):427
+msgid "Example /etc/conf.d/keymaps snippet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):427
+#, no-wrap
+msgid "\n<comment>(Change \"uk\" to your local layout)</comment>\nKEYMAP=\"uk\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):435
+msgid "Ncurses and Slang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):438
+msgid "Ignore any mention of Slang in this section if you do not have it installed or do not use it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):443
+msgid "It is wise to add <c>unicode</c> to your global USE flags in <path>/etc/make.conf</path>, and then to remerge <c>sys-libs/ncurses</c> and <c>sys-libs/slang</c> if appropriate. Portage will do this automatically when you update your system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):450
+msgid "Updating your system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):450
+#, no-wrap
+msgid "\n# <i>emerge --update --deep --newuse world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):454
+msgid "We also need to rebuild packages that link to these, now the USE changes have been applied. The tool we use (<c>revdep-rebuild</c>) is part of the <c>gentoolkit</c> package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):460
+msgid "Rebuilding of programs that link to ncurses or slang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):460
+#, no-wrap
+msgid "\n# <i>revdep-rebuild --soname libncurses.so.5</i>\n# <i>revdep-rebuild --soname libslang.so.1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):468
+msgid "KDE, GNOME and Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):471
+msgid "All of the major desktop environments have full Unicode support, and will require no further setup than what has already been covered in this guide. This is because the underlying graphical toolkits (Qt or GTK+2) are UTF-8 aware. Subsequently, all applications running on top of these toolkits should be UTF-8-aware out of the box."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):479
+msgid "The exceptions to this rule come in Xlib and GTK+1. GTK+1 requires a iso-10646-1 FontSpec in the ~/.gtkrc, for example <c>-misc-fixed-*-*-*-*-*-*-*-*-*-*-iso10646-1</c>. Also, applications using Xlib or Xaw will need to be given a similar FontSpec, otherwise they will not work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):487
+msgid "If you have a version of the gnome1 control center around, use that instead. Pick any iso10646-1 font from there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):492
+msgid "Example ~/.gtkrc (for GTK+1) that defines a Unicode compatible font"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):492
+#, no-wrap
+msgid "\nstyle \"user-font\"\n{\n    fontset=\"-misc-fixed-*-*-*-*-*-*-*-*-*-*-iso10646-1\"\n}\nwidget_class \"*\" style \"user-font\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):500
+msgid "If an application has support for both a Qt and GTK+2 GUI, the GTK+2 GUI will generally give better results with Unicode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):508
+msgid "X11 and Fonts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):511
+msgid "TrueType fonts have support for Unicode, and most of the fonts that ship with Xorg have impressive character support, although, obviously, not every single glyph available in Unicode has been created for that font. To build fonts (including the Bitstream Vera set) with support for East Asian letters with X, make sure you have the <c>cjk</c> USE flag set. Many other applications utilise this flag, so it may be worthwhile to add it as a permanent USE flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):520
+msgid "Also, several font packages in Portage are Unicode aware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):524
+msgid "Optional: Install some more Unicode-aware fonts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):524
+#, no-wrap
+msgid "\n# <i>emerge terminus-font intlfonts freefonts corefonts</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):531
+msgid "Window Managers and Terminal Emulators"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):534
+msgid "Window managers not built on GTK or Qt generally have very good Unicode support, as they often use the Xft library for handling fonts. If your window manager does not use Xft for fonts, you can still use the FontSpec mentioned in the previous section as a Unicode font."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):541
+msgid "Terminal emulators that use Xft and support Unicode are harder to come by. Aside from Konsole and gnome-terminal, the best options in Portage are <c>x11-terms/rxvt-unicode</c>, <c>x11-terms/terminal</c>, <c>gnustep-apps/terminal</c>, <c>x11-terms/mlterm</c>, or plain <c>x11-terms/xterm</c> when built with the <c>unicode</c> USE flag and invoked as <c>uxterm</c>. <c>app-misc/screen</c> supports UTF-8 too, when invoked as <c>screen -U</c> or the following is put into the <path>~/.screenrc</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):551
+msgid "~/.screenrc for UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):551
+#, no-wrap
+msgid "\ndefutf8 on\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):558
+msgid "Vim, Emacs, Xemacs and Nano"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):561
+msgid "Vim provides full UTF-8 support, and also has builtin detection of UTF-8 files. For further information in Vim, use <c>:help mbyte.txt</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):566
+msgid "Emacs 22.x and higher has full UTF-8 support as well. Xemacs 22.x does not support combining characters yet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):571
+msgid "Lower versions of Emacs and/or Xemacs might require you to install <c>app-emacs/mule-ucs</c> and/or <c>app-xemacs/mule-ucs</c> and add the following code to your <path>~/.emacs</path> to have support for CJK languages in UTF-8:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):578
+msgid "Emacs CJK UTF-8 support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):578
+#, no-wrap
+msgid "\n(require 'un-define)\n(require 'jisx0213)\n(set-language-environment \"Japanese\")\n(set-default-coding-systems 'utf-8)\n(set-terminal-coding-system 'utf-8)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):586
+msgid "Nano has provided full UTF-8 support since version 1.3.6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):593
+msgid "Shells"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):596
+msgid "Currently, <c>bash</c> provides full Unicode support through the GNU readline library. Z Shell (<c>zsh</c>) offers Unicode support with the <c>unicode</c> USE flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):602
+msgid "The C shell, <c>tcsh</c> and <c>ksh</c> do not provide UTF-8 support at all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):609
+msgid "Irssi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):612
+msgid "Irssi has complete UTF-8 support, although it does require a user to set an option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):617
+msgid "Enabling UTF-8 in Irssi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):617
+#, no-wrap
+msgid "\n/set term_charset UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):621
+msgid "For channels where non-ASCII characters are often exchanged in non-UTF-8 charsets, the <c>/recode</c> command may be used to convert the characters. Type <c>/help recode</c> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):630
+msgid "Mutt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):633
+msgid "The Mutt mail user agent has very good Unicode support. To use UTF-8 with Mutt, you don't need to put anything in your configuration files. Mutt will work under unicode enviroment without modification if all your configuration files (signature included) are UTF-8 encoded."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):640
+msgid "You may still see '?' in mail you read with Mutt. This is a result of people using a mail client which does not indicate the used charset. You can't do much about this than to ask them to configure their client correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):646
+msgid "Further information is available from the <uri link=\"http://wiki.mutt.org/index.cgi?MuttFaq/Charset\">Mutt Wiki</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):654
+msgid "Man"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):657
+msgid "Man pages are an integral part of any Linux machine. To ensure that any unicode in your man pages render correctly, edit <path>/etc/man.conf</path> and replace a line as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):663
+msgid "man.conf changes for Unicode support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):663
+#, no-wrap
+msgid "\n<comment>(This is the old line)</comment>\nNROFF           /usr/bin/nroff -Tascii -c -mandoc\n<comment>(Replace the one above with this)</comment>\nNROFF           /usr/bin/nroff -mandoc -c\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):673
+msgid "elinks and links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):676
+msgid "These are commonly used text-based browsers, and we shall see how we can enable UTF-8 support on them. On <c>elinks</c> and <c>links</c>, there are two ways to go about this, one using the Setup option from within the browser or editing the config file. To set the option through the browser, open a site with <c>elinks</c> or <c>links</c> and then <c>Alt+S</c> to enter the Setup Menu then select Terminal options, or press <c>T</c>. Scroll down and select the last option <c>UTF-8 I/O</c> by pressing Enter. Then Save and exit the menu. On <c>links</c> you may have to do a repeat <c>Alt+S</c> and then press <c>S</c> to save. The config file option, is shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):688
+msgid "Enabling UTF-8 for elinks/links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):688
+#, no-wrap
+msgid "\n<comment>(For elinks, edit /etc/elinks/elinks.conf or ~/.elinks/elinks.conf and\nadd the following line)</comment>\nset terminal.linux.utf_8_io = 1\n\n<comment>(For links, edit ~/.links/links.cfg and add the following\nline)</comment>\nterminal \"xterm\" 0 1 0 us-ascii utf-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):701
+msgid "Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):704
+msgid "Samba is a software suite which implements the SMB (Server Message Block) protocol for UNIX systems such as Macs, Linux and FreeBSD. The protocol is also sometimes referred to as the Common Internet File System (CIFS). Samba also includes the NetBIOS system - used for file sharing over windows networks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):711
+msgid "Enabling UTF-8 for Samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):711
+#, no-wrap
+msgid "\n<comment>(Edit /etc/samba/smb.conf and add the following under the [global] section)</comment>\ndos charset = 1255\nunix charset = UTF-8\ndisplay charset = UTF-8\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):721
+msgid "Testing it all out"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):724
+msgid "There are numerous UTF-8 test websites around. <c>net-www/w3m</c>, <c>net-www/links</c>, <c>net-www/elinks</c>, <c>net-www/lynx</c> and all Mozilla based browsers (including Firefox) support UTF-8. Konqueror and Opera have full UTF-8 support too."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):731
+msgid "When using one of the text-only web browsers, make absolutely sure you are using a Unicode-aware terminal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):736
+msgid "If you see certain characters displayed as boxes with letters or numbers inside, this means that your font does not have a character for the symbol or glyph that the UTF-8 wants. Instead, it displays a box with the hex code of the UTF-8 symbol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):745
+msgid "http://www.w3.org/2001/06/utf-8-test/UTF-8-demo.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):745
+msgid "A W3C UTF-8 Test Page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):749
+msgid "http://titus.uni-frankfurt.de/indexe.htm?/unicode/unitest.htm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):749
+msgid "A UTF-8 test page provided by the University of Frankfurt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):757
+msgid "Input Methods"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):760
+msgid "<e>Dead keys</e> may be used to input characters in X that are not included on your keyboard. These work by pressing your right Alt key (or in some countries, AltGr) and an optional key from the non-alphabetical section of the keyboard to the left of the return key at once, releasing them, and then pressing a letter. The dead key should modify it. Input can be further modified by using the Shift key at the same time as pressing the AltGr and modifier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):769
+msgid "To enable dead keys in X, you need a layout that supports it. Most European layouts already have dead keys with the default variant. However, this is not true of North American layouts. Although there is a degree of inconsistency between layouts, the easiest solution seems to be to use a layout in the form \"en_US\" rather than \"us\", for example. The layout is set in <path>/etc/X11/xorg.conf</path> like so:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre:caption):778
+msgid "/etc/X11/xorg.conf snippet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(pre):778
+#, no-wrap
+msgid "\nSection \"InputDevice\"\n    Identifier \"Keyboard0\"\n    Driver     \"kbd\"\n    Option     \"XkbLayout\" \"en_US\" <comment># Rather than just \"us\"</comment>\n    <comment>(Other Xkb options here)</comment>\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(note):787
+msgid "The preceding change only needs to be applied if you are using a North American layout, or another layout where dead keys do not seem to be working. European users should have working dead keys as is."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):793
+msgid "This change will come into effect when your X server is restarted. To apply the change now, use the <c>setxkbmap</c> tool, for example, <c>setxkbmap en_US</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):798
+msgid "It is probably easiest to describe dead keys with examples. Although the results are locale dependent, the concepts should remain the same regardless of locale. The examples contain UTF-8, so to view them you need to either tell your browser to view the page as UTF-8, or have a UTF-8 locale already configured."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):806
+msgid "When I press AltGr and [ at once, release them, and then press a, 'ä' is produced. When I press AltGr and [ at once, and then press e, 'ë' is produced. When I press AltGr and ; at once, 'á' is produced, and when I press AltGr and ; at once, release them, and then press e, 'é' is produced."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):813
+msgid "By pressing AltGr, Shift and [ at once, releasing them, and then pressing a, a Scandinavian 'å' is produced. Similarly, when I press AltGr, Shift and [ at once, release <e>only</e> the [, and then press it again, '˚' is produced. Although it looks like one, this (U+02DA) is not the same as a degree symbol (U+00B0). This works for other accents produced by dead keys — AltGr and [, releasing only the [, then pressing it again makes '¨'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(p):822
+msgid "AltGr can be used with alphabetical keys alone. For example, AltGr and m, a Greek lower-case letter mu is produced: 'µ'. AltGr and s produce a scharfes s or esszet: 'ß'. As many European users would expect (because it is marked on their keyboard), AltGr and 4 (or E depending on the keyboard layout) produces a Euro sign, '€'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(title):833
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):838
+msgid "http://en.wikipedia.org/wiki/Unicode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):838
+msgid "The Wikipedia entry for Unicode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):842
+msgid "http://en.wikipedia.org/wiki/UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):842
+msgid "The Wikipedia entry for UTF-8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):845
+msgid "http://www.unicode.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):845
+msgid "Unicode.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):846
+msgid "http://www.utf-8.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):846
+msgid "UTF-8.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):847
+msgid "http://www.ietf.org/rfc/rfc3629.txt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):847
+msgid "RFC 3629"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):848
+msgid "http://www.ietf.org/rfc/rfc2277.txt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):848
+msgid "RFC 2277"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri:link):851
+msgid "http://www.tbray.org/ongoing/When/200x/2003/04/26/UTF"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(uri):851
+msgid "Characters vs. Bytes"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//utf-8.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/vdr-guide.xml.pot b/doc/gettext/vdr-guide.xml.pot
new file mode 100644
index 0000000..45a62b1
--- /dev/null
+++ b/doc/gettext/vdr-guide.xml.pot
@@ -0,0 +1,663 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(guide:link):5
+msgid "/doc/en/vdr-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):6
+msgid "Gentoo Linux VDR Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(author:title):14
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail:link):9
+msgid "ng@zcat.de"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail):9
+msgid "Norman Golisz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail:link):12
+msgid "diox@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail):12
+msgid "Dimitry Bradt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail:link):15
+msgid "zzam@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail):15
+msgid "Matthias Schwarzott"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail:link):18
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(mail):18
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(abstract):21
+msgid "This guide shows you how to prepare Gentoo Linux for DVB and VDR."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(version):29
+msgid "1.8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(date):30
+msgid "2008-09-28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):33
+msgid "General information to DVB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):35
+msgid "What is DVB?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):38
+msgid "<e>DVB</e> stands for <e>Digital Video Broadcasting</e>. DVB describes methods to transfer digital data of TV, radio, interactive services like MHP, EPG and teletext. Through data compression with MPEG-2, or H.264 for HDTV, it's possible to transfer several channels on the same frequency. The more data compression, the more channels can be transferred, but you pay it with quality loss."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):47
+msgid "DVB can be transferred in several ways. The trailing letter identifies the method of transfer, e.g. DVB-<e>T</e> for terrestrial transmission. There are several more types:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):54
+msgid "DVB-S for transmission over satellites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):55
+msgid "DVB-C for transmission over cable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):56
+msgid "DVB-H for transmission to mobile devices (terrestrial)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):57
+msgid "DVB-IPI for transmission over IP based networks, e.g. internet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):58
+msgid "DVB-RC(S/C/T) return channel for the transmission of data services, e.g. broadband internet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):68
+msgid "Types and requirement of DVB cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):71
+msgid "Besides the different methods available to receive a DVB stream, the cards are classified by their type of produced output. There are cards with a decoder implemented which offer direct access to the stream by the device <path>/dev/video</path>. These cards are <e>full featured cards</e>. Other cards have no own decoder implemented and require a software decoder on the computer and are <e>budget cards</e>. This implies higher system requirements. Your computer's CPU should run at at least 600 MHz, and have at least 256MB of RAM. <uri link=\"http://linuxtv.org/wiki/index.php/DVB_Card_Vendors\">This list</uri> is useful for identifying your card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):88
+msgid "Preparing the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):90
+msgid "Configuring the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):93
+msgid "First, we must ensure that your kernel supports DVB and your DVB device. Since kernel version 2.6 the necessary drivers are included. Check your kernel configuration and make sure the following options are selected as a static driver or as modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):100
+msgid "Required kernel options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):100
+#, no-wrap
+msgid "\nInput Device Support ---&gt;\n* Event Interface\nDevice Drivers ---&gt;\nMultimedia Devices ---&gt;\nDigital Video Broadcasting Devices ---&gt;\n    [*] DVB For Linux\n     *  DVB Core Support\n   M  [Your driver]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):111
+msgid "Additionally we have to select the proper driver for your hardware. To find out the right module for your card, we mark every driver as module. If you have a PCI card, install <c>pciutils</c> if you haven't already. If you want built-in drivers or you don't own a PCI card, skip this step and continue with <uri link=\"#kernel_output\">Checking the kernel output</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):119
+msgid "Installing pciutils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):119
+#, no-wrap
+msgid "\n# <i>emerge pciutils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):123
+msgid "After booting the new kernel, we run <c>pcimodules</c> to list the required modules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):128
+msgid "Listing the required modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):128
+#, no-wrap
+msgid "\n# <i>pcimodules</i>\nohci-hcd\nehci-hcd\nsis900\nsnd-emu10k1\nb2c2-flexcop-pci\nnvidia\nnvidiafb\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):139
+msgid "In this case we have to load the module <c>b2c2-flexcop-pci</c>. We add the name to <path>/etc/modules.autoload.d/kernel-2.6</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):144
+msgid "Adding the module name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):144
+#, no-wrap
+msgid "\n# <i>echo b2c2-flexcop-pci &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):152
+msgid "Checking the kernel output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):155
+msgid "It's recommended to mark every driver as module, so that you can add the required module dynamically, especially if you don't know the module name. If you already know the module name, select the driver as a built-in driver. Compile the kernel, install the modules and boot it. You can check if your kernel has successfully detected your card by using <c>dmesg</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):163
+msgid "Checking kernel output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):163
+#, no-wrap
+msgid "\n# <i>dmesg | grep DVB</i>\n<comment>(If you own a TerraTec Cinergy T2, your output might look like this:)</comment>\nDVB: registering new adaptor (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver).\ninput: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control as /class/input/input2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):175 ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):183
+msgid "Installing VDR"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):179
+msgid "To install VDR, we just emerge it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):183
+#, no-wrap
+msgid "\n# <i>emerge vdr</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):187
+msgid "Now continue with <uri link=\"#inst_ir_remote\">Installing the Remote Control</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):196
+msgid "Installing the Remote Control"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):200
+msgid "There are at least two ways to control VDR via an infrared remote control. If your TV card has an onboard IR receiver you can use <c>vdr-remote</c>. Otherwise, you most likely need to use LIRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):209 ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):216
+msgid "Installing vdr-remote"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):212
+msgid "We first install the plugin via emerge:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):216
+#, no-wrap
+msgid "\n# <i>emerge vdr-remote</i>\n# <i>eselect vdr-plugin enable remote</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):221
+msgid "When using the remote plugin for the IR port on your DVB card everything should be fine with the default config. It automatically uses the input device which has \"dvb\" in its name. For more advanced uses take a look at <path>/etc/conf.d/vdr.remote</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):228
+msgid "Now, continue with <uri link=\"#video-out\">Video Output Methods</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):235
+msgid "Alternative: installing LIRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):238
+msgid "If your card can be remotely controlled (but you cannot or do not want to use <c>vdr-remote</c>), you may wish to configure LIRC. LIRC interprets the pressed keys and returns a name for each one. A program that supports LIRC waits for key events and runs the action configured in the config file, mostly stored in the config directory of the executing program (e.g. <c>mplayer</c> loads the file <path>~/.mplayer/lircrc</path>). Before we install LIRC, you have to add <c>lirc</c> to your USE flags and add an additional entry to <path>/etc/make.conf</path>: <c>LIRC_DEVICES</c>. Use <uri link=\"http://www.lirc.org/html/table.html\">this list</uri> to find the proper arguments for the option."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):251
+msgid "Installing LIRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):251
+#, no-wrap
+msgid "\n# <i>nano -w /etc/make.conf</i>\n<comment>(Replace \"devinput\" with the proper driver)</comment>\nLIRC_DEVICES=\"devinput\"\nUSE=\"lirc\"\n# <i>emerge lirc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):259
+msgid "At first we have to define each key code with a name. Most supported remote controls are configured already, take a look at the <uri link=\"http://lirc.sourceforge.net/remotes/\">remote list</uri>. Download the required file and save it as <path>/etc/lircd.conf</path>. Now we have to find out where to access your remote control. Run the following command to get a list of the current input devices (make sure your device is running)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):268
+msgid "List of current input devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):268
+#, no-wrap
+msgid "\n# <i>cat /proc/bus/input/devices</i>\nI: Bus=0000 Vendor=0000 Product=0000 Version=0000\nN: Name=\"TerraTec/qanu USB2.0 Highspeed DVB-T Receiver remote control\"\nP: Phys=usb-0000:00:1d.7-1/input0\nS: Sysfs=/class/input/input2\nH: Handlers=kbd event1\nB: EV=100003\nB: KEY=108fc210 2043 0 0 0 0 8000 2080 1 9e1680 0 0 ffc\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):279
+msgid "In this case we have the Terratec Cinergy T2 device plugged in, so we can access the device over <path>/dev/input/event1</path>. Replace <c>event1</c> with the matching device in your output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):285
+msgid "<c>lircd</c> needs to know the device to use. Add the following line to <path>/etc/conf.d/lircd</path>. Remember to replace <c>devinput</c> with the name of your driver and <c>event1</c> with the actual device."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):291
+msgid "Adding options to lircd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):291
+#, no-wrap
+msgid "\nLIRCD_OPTS=\"-H devinput -d /dev/input/event1\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):295
+msgid "It's time to start <c>lircd</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):299
+msgid "Starting lircd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):299
+#, no-wrap
+msgid "\n# <i>/etc/init.d/lircd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):303
+msgid "Now it should be possible to watch <c>lircd</c> capturing and decoding key presses. Just run the command <c>irw</c>. Stop it by pressing Ctrl+C when you have enough."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):309
+msgid "Testing LIRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):309
+#, no-wrap
+msgid "\n# <i>irw</i>\n0000000000001aa2 00 Exit Technisat_TTS35AI.conf\n0000000000001a8d 00 Mute Technisat_TTS35AI.conf\n0000000000000a97 00 OK Technisat_TTS35AI.conf\n0000000000000a97 01 OK Technisat_TTS35AI.conf\n0000000000000a92 00 Menu Technisat_TTS35AI.conf\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):318
+msgid "Next, add it to the default runlevel so that it starts automatically at boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):322
+msgid "Adding lircd to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):322
+#, no-wrap
+msgid "\n# <i>rc-update add lircd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):326
+msgid "To be able to use your remote control, you must enable LIRC support in VDR. Add the following line to <path>/etc/conf.d/vdr</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):331
+msgid "Enabling support for LIRC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):331
+#, no-wrap
+msgid "\n# <i>nano -w /etc/conf.d/vdr</i>\nIR_CTRL=\"lirc\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):341
+msgid "Video Output Methods"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):345
+msgid "You now need to decide on one (and only one!) of the following video output devices which show the picture and the overlayed On Screen Display (OSD)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):353
+msgid "Hardware decoding: full-featured DVB cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):356
+msgid "Users of these expensive cards need not install anything else, so you may continue with <uri link=\"#channel_list\">configuring your channel list</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):364
+msgid "Hardware decoding: DXR3/Hollywood+ cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):367
+msgid "To use a DXR3 card for VDR output we need the <c>vdr-dxr3</c> plugin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):371
+msgid "Installing the plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):371
+#, no-wrap
+msgid "\n# <i>emerge vdr-dxr3</i>\n# <i>echo em8300 &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):376
+msgid "The em8300 module need some configuration that depends on the exact revision of that card."
+msgstr ""
+
+#. <p>
+#. Because we (the authors) don't own a card that uses the dxr3config, we decided
+#. to skip this part till we have one at our disposal.
+#. </p>
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):388 ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):411 ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):451 ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):515
+msgid "Continue with <uri link=\"#channel_list\">configuring your channel list</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):395
+msgid "Hardware decoding: PVR350 cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):398
+msgid "As PVR350 cards have an onboard MPEG-Decoder chip we want to make use of that. We need to install the <c>vdr-pvr350</c> plugin. If <c>ivtv-driver</c> is not yet installed emerge will automatically install it for you. To have the ivtv module loaded at boot we add it to <path>/etc/modules.autoload.d/kernel-2.6</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):406
+msgid "Installing PVR350-Plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):406
+#, no-wrap
+msgid "\n# <i>emerge vdr-pvr350</i>\n# <i>echo ivtv &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):418
+msgid "Software decoding: vdr-softdevice"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):421
+msgid "To install it, we have to emerge <c>vdr-softdevice</c>. Don't forget to enable the plugin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):426
+msgid "Installing the softdevice plugin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):426
+#, no-wrap
+msgid "\n# <i>emerge vdr-softdevice</i>\n# <i>eselect vdr-plugin enable softdevice</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):431
+msgid "To select the proper video and audio output, edit <path>/etc/conf.d/vdr.softdevice</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):436
+msgid "For now, we will only describe the shm (\"shared memory\") method. This is already enabled in the installed config file (Setting SOFTDEVICE_VIDEO_OUT). Later you need to start <c>ShmClient</c> to get a window showing the picture."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):442
+msgid "If you do not want to think about a separate keyboard layout for controlling VDR, there are remote configuration files available at Matthias Schwarzott's <uri link=\"http://dev.gentoo.org/~zzam/vdr_remote_conf/\">devspace</uri>. There are files for softdevice/shm and xineliboutput (more coming). You will need the relevant file to <path>/etc/vdr/remote.conf</path> and run <c>chown vdr:vdr</c> on the file to get it working."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):458
+msgid "Software decoding: vdr-xineliboutput"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):461
+msgid "Some people prefer to use <c>vdr-xineliboutput</c>, because it can also work remotely. We'll now teach you how to configure <c>vdr-xineliboutput</c> on your host and client. First, the host setup:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):467
+msgid "Installing vdr-xineliboutput"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):467
+#, no-wrap
+msgid "\n# <i>emerge vdr-xineliboutput</i>\n# <i>eselect vdr-plugin enable xineliboutput</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):472
+msgid "Adding command line options at this point is crucial for xineliboutput to work. For more options, see <c>vdr --help</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):477
+msgid "Adding command line options to /etc/conf.d/vdr.xineliboutput"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):477
+#, no-wrap
+msgid "\n_EXTRAOPTS=\"--local=none --remote=37890\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):481
+msgid "The next step is to edit <path>/etc/vdr/svdrphosts.conf</path>. This file describes a number of host addresses that are allowed to connect to the SVDRP port of the video disk recorder running on the host system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):487
+msgid "Editing /etc/vdr/svdrphosts.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):487
+#, no-wrap
+msgid "\n<comment>(The proper syntax is: IP-Address[/Netmask])</comment>\n127.0.0.1             <comment>(always accept localhost)</comment>\n192.168.1.0/24        <comment>(any host on the local net)</comment>\n#204.152.189.113      <comment>(a specific host)</comment>\n#0.0.0.0/0            <comment>(any host on any net - USE THIS WITH CARE!)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):495
+msgid "If you only want to use <c>vdr-xineliboutput</c> to view the picture on the same computer as the one running VDR you can continue with <uri link=\"#channel_list\">configuring your channel list</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):501
+msgid "Otherwise, you now simply <c>emerge media-plugins/vdr-xineliboutput</c> on your client:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):506
+msgid "Client setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):506
+#, no-wrap
+msgid "\n# <i>emerge vdr-xineliboutput</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):510
+msgid "Later (after having started VDR) you will use the command <c>vdr-sxfe xvdr://hostname</c> to connect to VDR and view its picture and OSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):519
+msgid "There is also a plugin which just simulates the existance of a real output device (<c>vdr-dummydevice</c>) for some fancy uses like record-only servers, but that is more advanced than a normal VDR setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):530
+msgid "Creating a Channel List"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):534
+msgid "To make VDR really useful you need to create an appropriate channel list. There is more than one way to get a working list of channels (besides downloading one). The channel list installed by default is for DVB-S reception on Astra on 19.2°E."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):544
+msgid "Using dvbscan from linuxtv-dvb-apps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):547
+msgid "Installing linuxtv-dvb-apps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):547
+#, no-wrap
+msgid "\n# <i>emerge linuxtv-dvb-apps</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):551
+msgid "Find the correct frequency list for your region and type of reception. These files are stored under <path>/usr/share/dvb/scan</path>. For reception with DVB-T in Germany, Region Nuernberg you need to use <path>/usr/share/dvb/scan/dvb-t/de-Nuernberg</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):558
+msgid "Scanning with dvbscan"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):558
+#, no-wrap
+msgid "\n$ <i>dvbscan -o vdr /usr/share/dvb/scan/dvb-t/de-Nuernberg &gt; /etc/vdr/channels.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):565
+msgid "Using vdr-reelchannelscan"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):568
+msgid "First, delete the contents of the existing channel list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):572
+msgid "Cleaning old channel-list"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):572
+#, no-wrap
+msgid "\n# <i>rm /etc/vdr/channels.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):576
+msgid "Installing and activating vdr-reelchannelscan"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):576
+#, no-wrap
+msgid "\n# <i>emerge vdr-reelchannelscan</i>\n# <i>eselect vdr-plugin enable reelchannelscan</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):584
+msgid "Channels for systems using vdr-analogtv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):587
+msgid "You'll probably want to configure your channels at this point. The VDR project provides you with some examples which can be found at <path>/usr/share/doc/vdr-analogtv-$version/examples/</path>, as long as you've installed &gt;=<c>media-plugins/vdr-analogtv-1.0.00-r1</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):599 ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):629
+msgid "Starting VDR"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):603
+msgid "After having all basic software parts ready on the system you need to configure VDR with its OSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):608
+msgid "If you use a hardware decoder for picture output you should switch on the connected TV now. If you use software output the client for this must be started after VDR."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):614
+msgid "First, you should learn your key definitions; that is, connecting keys on your remote control to VDR's internal commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):619
+msgid "Just in case you need to edit the keyboard configuration, or (more likely) want to delete it to go back to learning the keys: VDR stores its key-definitions in <path>/etc/vdr/remote.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):625
+msgid "We begin with starting VDR:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):629
+#, no-wrap
+msgid "\n# <i>/etc/init.d/vdr start</i>\n* Preparing start of vdr:\n*   config files ...                                        [ ok ]\n*   Waiting for prerequisites (devices nodes etc.) ...      [ ok ]\n* Starting vdr ...                                          [ ok ]\n* First start of vdr: No check for running vdr possible\n* until control device (remote/keyboard) keys are learnt!\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):639
+msgid "Users of software decoders should now start the client program that opens the window to show the TV picture and the OSD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):644
+msgid "Activating the software decoder for the client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):644
+#, no-wrap
+msgid "\n<comment>(For users of vdr-softdevice)</comment>\n# <i>ShmClient</i>\n<comment>(For users of vdr-xineliboutput)</comment>\n# <i>vdr-sxfe xvdr://hostname</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):651
+msgid "The most useful keys for VDR are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):655
+msgid "Cursor keys (Left/Right/Up/Down)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):656
+msgid "Menu/Exit/Ok"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):657
+msgid "Colors (Red/Green/Yellow/Blue)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(li):658
+msgid "Number keys (0-9)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(impo):661
+msgid "If you don't have many keys, make sure to assign these. (Some remotes have Play/Pause/etc. on the same keys as the colors, so use them for the colors)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):666
+msgid "Now that the basic installation is over, you need to configure VDR. Switch to your output screen and follow the on-screen instructions. VDR asks you to press various keys on your remote control to learn the correct key codes. If you don't own a remote control, you can use your keyboard."
+msgstr ""
+
+#. <p>
+#. TODO: Add a configuration howto for remote controls etc.
+#. </p>
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(p):677
+msgid "Now you can add the VDR initscript to the default runlevel to get it started every time your computer boots up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre:caption):682
+msgid "Adding vdr to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(pre):682
+#, no-wrap
+msgid "\n# <i>rc-update add vdr default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(title):691
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(note):695
+msgid "If you need any help, you can always ask someone in <uri link=\"irc://irc.gentoo.org/gentoo-vdr\">#gentoo-vdr</uri>, or look around on our <uri link=\"http://forums.gentoo.org/\">forums</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//vdr-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/vi-guide.xml.pot b/doc/gettext/vi-guide.xml.pot
new file mode 100644
index 0000000..5165da4
--- /dev/null
+++ b/doc/gettext/vi-guide.xml.pot
@@ -0,0 +1,522 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(guide:link):5
+msgid "/doc/en/vi-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):6
+msgid "Learning vi -- the \"cheatsheet\" technique"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(author:title):7 ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail:link):8
+msgid "drobbins@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail):8
+msgid "Daniel Robbins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail:link):11
+msgid "stocke2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail):11
+msgid "Eric Stockbridge"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(author:title):13
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail:link):14
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(mail):14
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(abstract):17
+msgid "This guide will teach you how to use vi, using a cheat sheet method to accelerate the learning process. This will be the first guide for vi, catering to beginners."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(version):23
+msgid "1.1.7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(date):24
+msgid "2005-07-21"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):27
+msgid "Getting Started"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):29
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):32
+msgid "This tutorial will show you how to use vi, a powerful visual editor. Using a special accelerated <e>cheat sheet</e> method, this tutorial is designed to make you a proficient vi user without requiring a huge time commitment. In this vi tutorial, you'll learn how to move around, edit text, use insert mode, copy and paste text, and use important vim extensions like visual mode and multi-window editing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):41
+msgid "If you either don't know or aren't comfortable using vi, then you owe it to yourself to take this tutorial and get up to speed with one of the most popular and powerful Linux/UNIX visual editing programs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):50
+msgid "About the guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):53
+msgid "There's one thing in particular that makes it difficult to learn vi -- vi has lots of commands. In order to use vi effectively, you need to memorize quite a few. This can take a long time, and one of the goals of this tutorial is not to take up a lot of your time. So, initially, we have a challenge -- how exactly do I help you to memorize lots of commands in a short period of time?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):62
+msgid "To tackle this challenge, as we proceed through this tutorial, we're going to gradually put together a vi cheat sheet. This sheet will contain all the important vi commands. After you've completed this tutorial, you'll be able to refer to this cheat sheet if you forget a particular command. Over time, as you memorize commands, you'll gradually become less and less dependent on the cheat sheet. By using the cheat-sheet technique, you'll be able to learn how to use vi faster than ever possible before!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):76
+msgid "The learning process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):79
+msgid "In this guide, I'm going to use several techniques to help you learn. First, I'm going to describe how a particular command works, as you'd expect. Then, I'm going to ask you to try to use the command in vi (for practice), and then I'm going to ask you to transcribe the command to the cheat sheet (for later reference.) If you want to learn vi quickly, it's important that you perform all these steps. Trying out a command in vi and transcribing the command onto your cheat sheet will help you to memorize the command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):93
+msgid "Introducing vim"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):96
+msgid "There are many versions of vi, and I'm going to be showing you how to use a version of vi called <c>vim</c>. vim is very popular and has a number of extensions that make vi a lot nicer (whenever I demonstrate a vim-specific command, I'll make a note of it.) If you need to install vim, you can get it from <uri link=\"http://www.vim.org/\">www.vim.org</uri>. In addition to an enhanced command-line vi, vim also comes with <c>gvim</c>, a nice graphical editor which can be configured to use the excellent GTK+ gui library. Here's a gvim screenshot from my system:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):108
+msgid "/images/vishot.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):108
+msgid "screenshot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):108
+msgid "VIM screenshot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):110
+msgid "If you're a vi newbie, try to get gvim running on your system. Using vi from a gui can make things a bit easier for beginners."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):120
+msgid "First Steps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):122
+msgid "Pick a file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):125
+msgid "Before using vi to edit files, you need to know how to use vi to move around in a file. vi has a lot of movement commands, and we're going to take a look at many of them. For this part of the tutorial, find an unimportant text file and load it into vi by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(pre:caption):132
+msgid "Loading a file into vi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(pre):132
+#, no-wrap
+msgid "\n$ <i>vi myfile.txt</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):136
+msgid "If you have vim installed, type <c>vim myfile.txt</c>. If you'd prefer to use gvim, type <c>gvim myfile.txt</c>. <path>myfile.txt</path> should be the name of a text file on your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):145
+msgid "Inside vi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):148
+msgid "After vi loads, you should see a part of the text file you loaded on your screen. Congratulations -- you're in vi! Unlike many editors, when vi starts up, it is in a special mode called <e>command mode</e>. This means that if you press <c>l</c>on the keyboard, instead of inserting an <c>l</c> into the file at the current cursor position, the cursor will move one character to the right instead. In command mode, the characters on your keyboard are used to send commands to vi rather than insert literal characters into the text. One of the most essential types of commands are movement commands; let's take a look at some."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):166
+msgid "Moving around"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):168
+msgid "Moving in vi, part 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):171
+msgid "When in command mode, you can use the <c>h</c>,<c>j</c>,<c>k</c> and <c>l</c> keys to move the cursor left, down, up and right respectively. If you're using a modern version of vi, you can also use the arrow keys for this purpose. The <c>h</c>,<c>j</c>,<c>k</c> and <c>l</c> keys are handy because once you're comfortable with them, you'll be able to move around in the file without moving your fingers from the home keyboard row. Try using <c>h</c>,<c>j</c>,<c>k</c> and <c>l</c> (and the arrow keys) to move around in the text file. Try using <c>h</c> until you get to the beginning of a line. Notice that vi doesn't allow you to \"wrap around\" to the previous line by hitting <c>h</c> while you're on the first character. Likewise, you can't \"wrap around\" to the next line by hitting <c>l</c> at the end of a line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):190
+msgid "Moving in vi, part 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):193
+msgid "vi offers special shortcuts for jumping to the beginning or end of the current line. You can press <c>0</c> (zero) to jump to the first character of a line, and <c>$</c> to jump to the last character of the line. Try 'em and see. Since vi has so many handy movement commands, it makes a great \"pager\" (like the more or less commands.) Using vi as a pager will also help you to learn all the movement commands very quickly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):203
+msgid "You can also use <c>&lt;CTR&gt;F</c> and <c>&lt;CTR&gt;B</c> to move forwards and backwards a page at a time. Modern versions of vi (like vim) will also allow you to use the <c>PGUP</c> and <c>PGDOWN</c> keys for this purpose."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):213
+msgid "Word moves, part 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):216
+msgid "vi also allows you to move to the left or right by word increments. To move to the <e>first</e> character of the next word, press <c>w</c>. To move to the <e>last</e> character of the next word, press <c>e</c>. To move to the first character of the <e>previous</e> word, press <c>b</c>. Test 'em out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):227
+msgid "Word moves, part 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):230
+msgid "After playing around with the word movement commands, you may have noticed that vi considers words like <c>foo-bar-oni</c> as five separate words! This is because by default, vi delimits words by spaces <e>or</e> punctuation. <c>foo-bar-oni</c> is therefore considered five words: <c>foo</c>, <c>-</c>, <c>bar</c>, <c>-</c> and <c>oni</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):238
+msgid "Sometimes, this is what you want, and sometimes it isn't. Fortunately, vi also understands the concept of a \"bigword\". vi delimits bigwords by <e>spaces or newlines only</e>. This means that while <c>foo-bar-oni</c> is considered five vi words, it's considered only one vi bigword."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):249
+msgid "Word moves, part 3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):252
+msgid "To jump around to the next and previous bigword, you can use a <e>capitalized</e> word move command. Use <c>W</c> to jump to the first character of the next bigword, <c>E</c> to jump to the last character of the next bigword, and <c>B</c> to jump to the first character of the previous bigword. Test 'em out, and compare the matching word and bigword movement commands until you understand their differences."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):265
+msgid "Bigger moves"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):268
+msgid "We just have a few more commands to cover before it's time to start puting together our cheat sheet. You can use the <c>(</c> and <c>)</c> characters to move to the beginning of the previous and next sentence. In addition, you can hit <c>{</c> or <c>}</c> to jump to the beginning of the current paragraph, and the beginning of the next. Test 'em out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):282
+msgid "Quitting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):286
+msgid "We've covered the basic movement commands, but there are another couple of commands that you need to know. Typing <c>:q</c> will quit vi. If this doesn't work, then you probably accidentally modified the file in some way. To tell vi to quit, throwing away any changes, type <c>:q!</c>. You should now be at the command prompt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):294
+msgid "In vi, any command that begins with a <c>:</c> is said to be an <e>ex-mode</e> command. This is because vi has a built-in non-visual editor called <e>ex</e>. It can be used similarly to sed to perform line-based editing operations. In addition, it can also be used to quit, as we've just seen. If you ever hit the <c>Q</c> key while in command mode, you'll be transported to ex mode. If this ever happens to you, you'll be confronted with a : prompt, and hitting enter will scroll the entire screen upwards. To get back to good 'ol vi mode, simply type vi and hit enter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):311
+msgid "The Cheat Sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):313
+msgid "The beginnings of the cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):316
+msgid "We've covered a lot of commands, and it's time to transcribe them to our cheat sheet. For the cheat sheet, you'll need a US letter or A4 sized piece of paper (we're going to pack a lot of info onto this sheet!) Here's a picture of my cheat sheet after I've transcribed all the commands that we've covered so far. Try to follow my layout if possible so that we can fit everything on one sheet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):326
+msgid "/images/vicheat-first.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):326
+msgid "First part of the cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):326 ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):597 ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):708
+msgid "Cheat Sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):331
+msgid "Miscellaneous vi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):334
+msgid "Let's continue our rapid command-covering pace. In command-mode, you can jump to a particularline by typing <c>G</c>. To jump to the first line of a file, type <c>1G</c>. Note that <c>G</c> is capitalized."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):340
+msgid "If you want to jump to the next occurence of a particular text pattern, type <c>/&lt;regexp&gt;</c> and hit <c>enter</c>. Replace &lt;regexp&gt; with the regular expression you're looking for. If you don't know how to use regular expressions, don't fret -- typing <c>/foo</c> will move to the next occurence of <e>foo</e>. The only thing you'll need to watch out for is when you want to refer to the literal <c>^</c>, <c>.</c>, <c>$</c> or <c>\\</c> characters. Prefix these characters with a backslash (<c>\\</c>), and you'll be set. For example, <c>/foo\\.gif</c> will search for the next occurence of \"foo.gif\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):353
+msgid "To repeat the search forwards, hit <c>n</c>. To repeat the search backwards, type <c>N</c>. As always, test these commands out in your very own vi editor. You can also type <c>//</c> to repeat the last search."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):365
+msgid "Saving and Editing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):367
+msgid "Save and save as..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):370
+msgid "We've covered how you can use the <e>ex</e> command <c>:q</c> to quit from vi. If you want to save your changes, type <c>:w</c>. If you want to save your changes to another file, type <c>:w filename.txt</c> to save as <e>filename.txt</e>. If you want to save and quit, type <c>:x</c> or <c>:wq</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):378
+msgid "In vim (and other advanced vi editors, like elvis)<c>:w</c>, you can have multiple buffers open at once. To open a file into a new window, type <c>:sp filename.txt</c>. <path>filename.txt</path> will appear open for editing in a new split window. To switch between windows, type <c>&lt;CTR&gt;w&lt;CTR&gt;w</c> (control-w twice). Any <c>:q</c>, <c>:q!</c>, <c>:w</c> and <c>:x</c> commands that you enter will only be applied to the currently-active window."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):391
+msgid "Simple edits"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):394
+msgid "Now, it's time to start learning some of the simple editing commands. The commands that we'll cover here are considered <e>simple</e> because the commands keep you in command mode. The more complex editing commands automatically put you into insert mode -- a mode that allows you to enter literal data from the keyboard. We'll cover those in a bit."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):402
+msgid "For now, try moving over some characters and hitting <c>x</c> repeatedly. You'll see that <c>x</c> will delete the current character under the cursor. Now, move to the middle of the paragraph somewhere in your text file, and hit <c>J</c> (capitalized). You'll see that the <c>J</c> command tells vi to join the next line to the end of the current line. Now, move over a character and hit <c>r</c>, and then type in a new character; you'll see that the original character has been replaced. Finally, move to any line in the file and type <c>dd</c>. You'll see that <c>dd</c> deletes the current line of text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):418
+msgid "Repeating and deleting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):421
+msgid "You can repeat any editing command by hitting the <c>.</c> key. If you experiment, you'll see that typing <c>dd...</c> will delete 4 lines, and <c>J......</c> will join four lines. As usual, vi provides with another handy shortcut."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):428
+msgid "To delete text, you can also use the <c>d</c> command combined with any movement command. For example, <c>dw</c> will delete from the current position to the beginning of the next word; <c>d)</c> will delete up until the end of the next sentence, and <c>d}</c> will delete the remainder of the paragraph. Experiment with the <c>d</c> command and the other editing commands until you're comfortable with them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):441
+msgid "Undo!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):444
+msgid "Now that we're experimenting with deletion, it would be a good time to learn how to undo any changes. By pressing <c>u</c>, the original version of vi allowed you to undo the last edit only. However, modern versions of vi like vim will allow you to repeatedly press <c>u</c> to continue to undo changes to your file. Try combining some <c>d</c> and <c>u</c> commands together."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):456 ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):588
+msgid "Updating the cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):459
+msgid "Time to update the cheat sheet! After adding all the commands we've covered so far, your cheat sheet should look like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):465
+msgid "/images/vicheat-edit.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):465
+msgid "Cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):465
+msgid "Cheat sheet with editing commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):472
+msgid "Insert mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):476
+msgid "So far, we've covered how to move around in vi, perform file i/o, and perform basic editing operations. However, I still haven't shown you how to actually type in free-form text! This was intentional, because vi's insert mode is a bit complicated at first. However, after you become comfortable with insert mode, its complexity (and flexibility) will become an asset."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):485
+msgid "In vi <e>insert mode</e>, you'll be able to enter text directly to the screen just like you can in many other visual editors. Once you've entered your modifications, you can hit escape to return to <e>command mode</e>. You can enter insert mode by pressing <c>i</c> or <c>a</c>. If you press <c>i</c>, your text will be <e>inserted</e> before the current character, and if you hit <c>a</c>, your text will be <e>appended</e> after the current character. Remember, after you enter your text, hit <c>&lt;ESC&gt;</c> to return to command mode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):499
+msgid "Benefits of insert mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):502
+msgid "Go ahead and try using the <c>a</c> and <c>i</c> commands. Hit either <c>a</c> or <c>i</c>, type some text, and then hit escape to get back to command mode. After hitting <c>a</c> or <c>i</c>, try hitting <c>&lt;ENTER&gt;</c>, and see what happens. Try using the arrow keys and the <c>&lt;DEL&gt;</c> key to get a feel for how insert mode works. By using the arrow keys and <c>&lt;DEL&gt;</c> key, you can perform significant editing steps without repeatedly entering and leaving insert mode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):516
+msgid "Insert options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):519
+msgid "Here are some other handy ways to enter insert mode. Press <c>A</c> (captial) to begin appending to the <e>end</e> of the current line, regardless of your current position on the line. Likewise, press <c>I</c> (capital) to begin inserting text at the <e>beginning</e> of the current line. Press <c>o</c> to create a new blank line below the current line into which you can insert text, and press <c>O</c> (capital) to create a new line above the current line. To replace the entire current line with a new line, press <c>cc</c>. To replace everything from the current position to the end of the line, type <c>c$</c>. To replace everything from the current position to the beginning of the line, type <c>c0</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):533
+msgid "In addition to performing a special operation, every one of these commands will put you into insert mode. After typing in your text, hit <c>&lt;ESC&gt;</c> to return to command mode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):542
+msgid "Changing text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):545
+msgid "We've used the <c>c</c> (change) command a little bit so far when we typed <c>cc</c>, <c>c0</c> and <c>c$</c>. <c>cc</c> is a special form of the change command, similar to <c>dd</c>. the <c>c0</c> and <c>c$</c> commands are examples of using the change command in combination with a movement command. In this form, <c>c</c> works similarly to <c>d</c>, except that it leaves you in insert mode so that you can enter replacement text for the deleted region. Try combining some movement commands with <c>c</c> and test them out on your file (hint: <c>cW</c>, <c>ce</c>, <c>c(</c> .)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):562
+msgid "Compound Commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):566
+msgid "vi <e>really</e> becomes powerful when you start using compound (\"combo\") commands, like <c>d{</c> and <c>cw</c>. In addition to these commands, you can also combine a number with any movement command, such as <c>3w</c>, which will tell vi to jump three words to the right. Here are some more movement \"combo\" command examples: <c>12b</c>, <c>4j</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):575
+msgid "vi, in addition to allowing (number)(movement command) combinations, also allows <c>d</c> or <c>c</c> to be combined with a number or movement command. So, <c>d3w</c> will delete the next three words, <c>d2j</c> will delete the current and next two lines, etc. Test out some <c>c</c> and <c>d</c> combo moves to get a feel for how powerful and concise vi editing can be. Once these commands are second-nature, you'll be able to edit files at blazing speed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):591
+msgid "Time to update the cheat sheet again. Here's what it looks like so far:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):597
+msgid "/images/vicheat-compound.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):597
+msgid "Cheat sheet with compound commands"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):602
+msgid "Productivity features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):605
+msgid "So far, we've covered how to move, save and quit, perform simple edits and deletions, and use insert mode. With everything listed on the cheat sheet so far, you should be able to use vi to perform almost any task."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):612
+msgid "However, vi also has many more powerful commands. In this section, you'll learn how to <e>cut</e>, <e>copy</e> and <e>paste</e>, <e>search</e> and <e>replace</e>, and use <e>autoindent</e> features. These commands will help make vi more fun and productive."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):622
+msgid "Visual mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):625
+msgid "The best way to cut and paste is to use <e>visual mode</e>, a special mode that has been added to modern versions of vi, like vim and elvis. You can think of visual mode as a \"highlight text\" mode. Once the text is highlighted, it can be copied or deleted, and then pasted. If you are using gvim, you can highlight by simply dragging the left mouse button over a particular region:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):635
+msgid "/images/vihighlight.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:short):635
+msgid "Highlighted text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):635
+msgid "VIM with highlighted text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):637
+msgid "In addition, you can also enter visual mode by hitting <c>v</c> (this may be your only option if you are using vi from the console.) Then, by moving the cursor using movement commands (typically the arrow keys), you'll be able to highlight a region of text. Once highlighted, we are ready to cut or copy the text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):645
+msgid "If you're copying the text, hit <c>y</c> (which stands for \"yank\"). If you're cutting the text, hit <c>d</c>. You'll be placed back in command mode. Now, move to the position where you'd like to insert the cut or copied text, and hit <c>P</c> to insert before the cursor, or <c>p</c> to insert after the cursor. Voila, the cut/copy and paste is complete! Test out several copy/cut and paste operations before advancing to the next section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):658
+msgid "Replacing text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):661
+msgid "To replace patterns of text, we use <e>ex</e> mode. If you'd like to replace the first pattern that appears on the current line, type <c>:s/&lt;regexp&gt;/&lt;replacement&gt;/</c> and hit <c>&lt;ENTER&gt;</c>, where &lt;regexp&gt; is the pattern you'd like to match and &lt;replacement&gt; is the replacement string. To replace all matches on the current line, type <c>:s/&lt;regexp&gt;/&lt;replacement&gt;/g</c> and hit enter. To replace every occurence of this pattern in your file (normally what you want), type <c>:%s/&lt;regexp&gt;/&lt;replacement&gt;/g</c>. If you'd like to do a global replace, but have vi prompt you for each change, type <c>:%s/&lt;regexp&gt;/&lt;replacement&gt;/gc</c> (stands for \"confirm\") and hit <c>&lt;ENTER&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):679
+msgid "Indentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):682
+msgid "vi supports autoindentation, for when you are editing source code. Most modern versions of vi (like vim) will auto-enable autoindent mode when you are editing a source file (like a .c file, for example). When autoindent is enabled, you can use <c>&lt;CTR&gt;d</c> (control-d) to move one indent level to the left, and <c>&lt;CTR&gt;t</c> (control-t) to move one indent level to the right. If autoindent wasn't enabled automatically, you can manually enable it by typing in the <e>ex</e> command <c>:set autoindent</c>. You can also tell vi to set the tab size to your favorite setting by using the <c>:set tabstop</c> command; <c>:set tabstop=4</c> is quite popular."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):698
+msgid "Our final cheat sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):701
+msgid "Well, we've reached the end of the vi tutorial! After adding all the advanced editing commands to your cheat sheet, it should look like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:link):708
+msgid "/images/vicheat-final.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(figure:caption):708
+msgid "Final cheet sheet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):710
+msgid "Keep your cheat sheet handy, and begin using vi to edit files and compose emails. Refer to the cheat sheet when needed; you'll find that within the week, you'll have nearly all the commands memorized and your vi productivity will shoot through the roof!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):717
+msgid "If you want to use vi as your default editor make the following change to <path>/etc/rc.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(pre:caption):722
+msgid "Setting vi as the default editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(pre):722
+#, no-wrap
+msgid "\n<comment>(Set EDITOR to your preferred editor.)</comment>\n#EDITOR=\"/bin/nano\"\nEDITOR=\"/usr/bin/vim\"\n#EDITOR=\"/usr/bin/emacs\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):732
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):735
+msgid "Here are some resources you may find helpful as you continue to learn more about vi:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(li):741
+msgid "<uri link=\"http://www.thomer.com/thomer/vi/vi.html\">The vi Lovers Home Page</uri>, an excellent resource for all things vi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(li):745
+msgid "<uri link=\"http://www.vim.org/\">The vim homepage</uri> is the place to go for all your vim needs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(li):749
+msgid "If you're looking for a good, old-fashioned book, <uri link=\"http://www.oreilly.com/catalog/vi6/\">Learning the vi Editor, 6th Edition</uri> would be an excellent choice. Contains good coverage of vi and vi clones."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(title):760
+msgid "About this document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vi-guide.xml(p):763
+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//vi-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/virt-mail-howto.xml.pot b/doc/gettext/virt-mail-howto.xml.pot
new file mode 100644
index 0000000..5a47142
--- /dev/null
+++ b/doc/gettext/virt-mail-howto.xml.pot
@@ -0,0 +1,863 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):6
+msgid "Virtual Mailhosting System with Postfix Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):9
+msgid "antifa@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):9
+msgid "Ken Nowack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):12
+msgid "ezra@revoltltd.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):12
+msgid "Ezra Gorman"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):20 ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):15
+msgid "klasikahl@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):15
+msgid "Zack Gilburd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):18
+msgid "seather@scygro.za.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):18
+msgid "Scygro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):21
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail):21
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(abstract):27
+msgid "This document details how to create a virtual mailhosting system based upon postfix, mysql, courier-imap, and cyrus-sasl."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(version):32
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(date):33
+msgid "2010-10-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):36 ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1021
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):40
+msgid "For most Gentoo users, a simple mail client and fetchmail will do. However, if you're hosting a domain with your system, you'll need a full blown MTA (Mail Transfer Agent). And if you're hosting multiple domains, then you'll definitely need something more robust to handle all of the email for your users. This system was designed to be an elegant solution to that problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):48
+msgid "A virtual mail system needs to be able to handle email for numerous domains with multiple users over a variety of interfaces. This presents some issues that must be dealt with. For instance, what if you have two users on different domains that want the same user name? If you are providing imap access and smtp-auth, how do combine the various authentication daemons into a single system? How do you provide security for the numerous components that comprise the system? How do you manage it all?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):58
+msgid "This howto will show you how to set up with a mail system capable of handling mail for as many domains as your hardware can handle, supports virtual mail users that don't require shell accounts, has domain specific user names, can authenticate web, imap, smtp, and pop3 clients against a single database, utilizes ssl for transport layer security, has a web interface, can handle mailing lists for any domain on the machine, and is controlled by a nice, central and easy mysql database."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):68
+msgid "There are quite a variety of ways to go about setting up a virtual mailhosting system. With so may options, another may be the best choice for your specific needs. Consider investigating <uri>http://www.qmail.org/</uri> and <uri>http://www.exim.org/</uri> to explore your options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):75
+msgid "The following packages are used in this setup: apache, courier-imap, courier-authlib postfix, mod_php, phpmyadmin, squirrelmail, cyrus-sasl, mysql, php, and mailman."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):81
+msgid "Make sure to turn on the following USE variables in <path>/etc/make.conf</path> before compiling the packages: <c>USE=\"mysql imap libwww maildir sasl ssl\"</c>. Otherwise you will most likely have to recompile things to get the support you need for all the protocols. Further, it's a good idea to turn off any other mail and network variables, like ipv6."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(impo):89
+msgid "You need a domain name to run a public mail server, or at least an MX record for a domain. Ideally you would have control of at least two domains to take advantage of your new virtual domain functionality."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(impo):95
+msgid "Make sure <path>/etc/conf.d/hostname</path> is set to the right hostname for your mail server. You can apply any changes you make to this file by running <c>/etc/init.d/hostname restart</c>. Verify your hostname is set correctly with <c>hostname</c>. Also verify that there are no conflicting entries in <path>/etc/hosts</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(note):103
+msgid "It is recommended that you read this entire document and familiarize yourself with all the steps before attempting the install. If you run into problems with any of the steps, check the troubleshooting guide at the end of this document. Also, not all the referenced packages are necessary, this set up is very flexible. For instance, if you do not desire a web interface, feel free to skip the squirrelmail section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):117
+msgid "Postfix Basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):121
+msgid "Install postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):121
+#, no-wrap
+msgid "\n# <i>emerge postfix</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(warn):125
+msgid "Verify that you have not installed any other MTA, such as ssmtp, exim, or netqmail, or you will surely have BIG problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):130
+msgid "After postfix is installed, it's time to configure it. Change the following options in <path>/etc/postfix/main.cf</path>. Remember to replace <c>$variables</c> with your own names."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):136 ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):327 ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):783
+msgid "/etc/postfix/main.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):136
+#, no-wrap
+msgid "\nmyhostname = $host.domain.name\nmydomain = $domain.name\ninet_interfaces = all\nmydestination = $myhostname, localhost.$mydomain $mydomain\nmynetworks = my.ip.net.work/24, 127.0.0.0/8\nhome_mailbox = .maildir/\nlocal_destination_concurrency_limit = 2\ndefault_destination_concurrency_limit = 10\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):147
+msgid "Next change the following in <path>/etc/postfix/master.cf</path>. This will turn on verbose output for debugging:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):152
+msgid "/etc/postfix/master.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):152
+#, no-wrap
+msgid "\n# service type  private unpriv  chroot  wakeup  maxproc command + args\n#               (yes)   (yes)   (yes)   (never) (50)\n#\n==========================================================================\n<comment>(Just add the \"-v\" after the smtpd in the following line)</comment>\nsmtp      inet  n       -       n       -       -       smtpd -v\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):161
+msgid "Next, edit <path>/etc/mail/aliases</path> to add your local aliases. There should at least be an alias for root like: <c>root: your@email.address</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):166
+msgid "Starting postfix for the first time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):166
+#, no-wrap
+msgid "\n# <i>/usr/bin/newaliases</i>\n<comment>(This will install the new aliases. You only need to do this\nwhen you update or install aliases.)</comment>\n\n# <i>/etc/init.d/postfix start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):174
+msgid "Now that postfix is running, fire up your favorite console mail client and send yourself an email. I use <c>mutt</c> for all my console mail. Verify that postfix is delivering mail to local users, once that's done, we're on to the next step."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(note):181
+msgid "I strongly recommend that you verify this basic postfix setup is functioning before you progress to the next step of the howto."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):191
+msgid "Courier-imap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):195
+msgid "Install courier-imap and courier-authlib"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):195
+#, no-wrap
+msgid "\n# <i>emerge courier-imap courier-authlib</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):199
+msgid "Courier-imap configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):199
+#, no-wrap
+msgid "\n# <i>cd /etc/courier-imap</i>\n<comment>(If you want to use the ssl capabilities of courier-imap or pop3,\nyou'll need to create certs for this purpose.\nThis step is recommended. If you do not want to use ssl, skip this step.)</comment>\n\n# <i>nano -w pop3d.cnf</i>\n# <i>nano -w imapd.cnf</i>\n<comment>(Change the C, ST, L, CN, and email parameters to match your server.)</comment>\n\n# <i>mkpop3dcert</i>\n# <i>mkimapdcert</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):213
+msgid "Start the courier services you need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):213
+#, no-wrap
+msgid "\n# <i>/etc/init.d/courier-imapd start</i>\n# <i>/etc/init.d/courier-imapd-ssl start</i>\n# <i>/etc/init.d/courier-pop3d start</i>\n# <i>/etc/init.d/courier-pop3d-ssl start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):220
+msgid "Start up your favorite mail client and verify that all connections you've started work for receiving and sending mail. Of course, you won't be able to log on to any of the services because authentication hasn't been configured yet, but it is wise to check if the connections themselves work or not."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):227
+msgid "Now that the basics work, we're going to do a whole bunch of stuff at once to get the rest of the system running. Again, please verify that what we've installed already works before progressing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):238
+msgid "Cyrus-sasl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):242
+msgid "Next we're going to install cyrus-sasl. Sasl is going to play the role of actually passing your auth variables to courier-auth, which will in turn pass that information to mysql for authentication of smtp users. For this howto, we'll not even try to verify that sasl is working until mysql is set up and contains a test user. Which is fine since we'll be authenticating against mysql in the end anyway."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):251
+msgid "Configuring and installing the cyrus-sasl ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):251
+#, no-wrap
+msgid "\n# <i>emerge cyrus-sasl</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):255
+msgid "Next, edit <path>/etc/sasl2/smtpd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):259
+msgid "Starting sasl"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):259
+#, no-wrap
+msgid "\n# <i>nano -w /etc/sasl2/smtpd.conf</i>\nmech_list: PLAIN LOGIN\npwcheck_method: saslauthd\n# <i>nano -w /etc/conf.d/saslauthd</i>\nSASLAUTHD_OPTS=\"${SASLAUTH_MECH} -a rimap -r\"\nSASLAUTHD_OPTS=\"${SASLAUTHD_OPTS} -O localhost\"\n# <i>/etc/init.d/saslauthd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):274
+msgid "SSL Certs for Postfix and Apache"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):278
+msgid "Next we're going to make a set of ssl certificates for postfix and apache."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):282
+msgid "Making ssl certicates"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):282
+#, no-wrap
+msgid "\n# <i>cd /etc/ssl/</i>\n# <i>nano -w openssl.cnf</i>\n\n<comment>Change the following default values for your domain:</comment>\ncountryName_default\nstateOrProvinceName_default\nlocalityName_default\n0.organizationName_default\ncommonName_default\nemailAddress_default.\n\n<comment>(If the variables are not already present, just add them in a sensible place.)</comment>\n\n# <i>cd misc</i>\n# <i>./CA.pl -newreq-nodes</i>\n# <i>./CA.pl -newca</i>\n# <i>./CA.pl -sign</i>\n# <i>cp newcert.pem /etc/postfix</i>\n# <i>cp newkey.pem /etc/postfix</i>\n# <i>cp demoCA/cacert.pem /etc/postfix</i>\n<comment>(Now we do the same thing for apache.)</comment>\n\n# <i>openssl req -new &gt; new.cert.csr</i>\n# <i>openssl rsa -in privkey.pem -out new.cert.key</i>\n# <i>openssl x509 -in new.cert.csr -out new.cert.cert -req -signkey new.cert.key -days 365</i>\n<comment>(Just leave the resulting certificates here for now.\nWe'll install them after Apache is installed.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):317
+msgid "Adding SSL and SASL support to Postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):321
+msgid "Now edit the postfix config's to make it aware of your new sasl and ssl capabilities. Add the following parameters to the end of the file where they will be easy to find."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):327
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/main.cf</i>\n\nsmtpd_sasl_auth_enable = yes\nsmtpd_sasl2_auth_enable = yes\nsmtpd_sasl_security_options = noanonymous\nbroken_sasl_auth_clients = yes\nsmtpd_sasl_local_domain =\n\n<comment>(The broken_sasl_auth_clients option and the login auth method\nare for outlook and outlook express only and are undocumented.\nIsn't having to hack software for stupid, broken, M$ BS great?\nsmtpd_sasl_local_domain appends a domain name to clients using\nsmtp-auth. Make sure it's blank or your user names will get\nmangled by postfix and be unable to auth.)</comment>\n\nsmtpd_recipient_restrictions =\n  permit_sasl_authenticated,\n  permit_mynetworks,\n  reject_unauth_destination\n\n<comment>(The next two options enable outgoing encryption.)</comment>\nsmtp_use_tls = yes\nsmtp_tls_note_starttls_offer = yes\nsmtpd_use_tls = yes\n#smtpd_tls_auth_only = yes\nsmtpd_tls_key_file = /etc/postfix/newkey.pem\nsmtpd_tls_cert_file = /etc/postfix/newcert.pem\nsmtpd_tls_CAfile = /etc/postfix/cacert.pem\nsmtpd_tls_loglevel = 3\nsmtpd_tls_received_header = yes\nsmtpd_tls_session_cache_timeout = 3600s\ntls_random_source = dev:/dev/urandom\n\n<comment>(smtpd_tls_auth_only is commented out to ease testing the system.\nYou can turn this on later if you desire.)</comment>\n\n# <i>postfix reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):367
+msgid "Now we're going to verify that the config's we added were picked up by postfix. For this we are going to use <c>telnet</c> (provided by for instance <c>net-misc/netkit-telnetd</c>) although you can also use <c>nc</c> (provided by <c>net-analyzer/netcat</c>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):374
+msgid "Verifying sasl and tls support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):374
+#, no-wrap
+msgid "\n# <i>telnet localhost 25</i>\n\nTrying 127.0.0.1...\nConnected to localhost.\nEscape character is '^]'.\n220 mail.domain.com ESMTP Postfix\n<i>EHLO domain.com</i>\n250-mail.domain.com\n250-PIPELINING\n250-SIZE 10240000\n250-VRFY\n250-ETRN\n250-STARTTLS\n250-AUTH LOGIN PLAIN\n250-AUTH=LOGIN PLAIN\n250-XVERP\n250 8BITMIME\n<i>^]</i>\ntelnet&gt; <i>quit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):396
+msgid "Verify that the above AUTH and STARTTLS lines now appear in your postfix install. As I said before, as it stands now AUTH will not work. that's because sasl will try to auth against it's sasldb, instead of the shadow file for some unknown reason, which we have not set up. So we're going to just plow through and set up mysql to hold all of our auth and virtual domain information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):409
+msgid "The vmail user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):413
+msgid "Before we set up our virtual mailhosting environment, we create a functional user under which the virtual mailboxes will be hosted. For clarity's sake we will call this <e>vmail</e>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):419
+msgid "Adding the vmail user"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):419
+#, no-wrap
+msgid "\n# <i>useradd -d /home/vmail -s /bin/false -m vmail</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):423
+msgid "So now you've set up the vmail account. You can create multiple accounts if you want (to keep some structure in your set of virtual mail accounts). The user id, group id and home dirs are referenced in the MySQL tables."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):429
+msgid "Next to the user account we also need to create the location where the mailboxes will reside:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):434
+msgid "Creating mailboxes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):434
+#, no-wrap
+msgid "\n# <i>mkdir -p /home/vmail/virt-domain.com/foo</i>\n# <i>chown -R vmail:vmail /home/vmail/virt-domain.com</i>\n# <i>maildirmake /home/vmail/virt-domain.com/foo/.maildir</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):445
+msgid "MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):449
+msgid "Next we're going to install and configure MySQL. You'll need the <uri link=\"http://www.gentoo.org/doc/en/files/genericmailsql.sql\">genericmailsql.sql</uri> dumpfile for this step."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):455
+msgid "Installing and configuring MySQL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):455
+#, no-wrap
+msgid "\n# <i>emerge mysql</i>\n\n# <i>/usr/bin/mysql_install_db</i>\n<comment>(After this command runs follow the onscreen directions\nfor adding a root password with mysql, otherwise your db will\nbe wide open.)</comment>\n\n# <i>/etc/init.d/mysql start</i>\n# <i>mysqladmin -u root -p create mailsql</i>\n# <i>mysql -u root -p mailsql &lt; genericmailsql.sql</i>\n# <i>mysql -u root -p mysql</i>\nmysql&gt; <i>GRANT SELECT,INSERT,UPDATE,DELETE</i>\n  -&gt;     <i>ON mailsql.*</i>\n  -&gt;     <i>TO mailsql@localhost</i>\n  -&gt;     <i>IDENTIFIED BY '$password';</i>\nQuery OK, 0 rows affected (0.02 sec)\n\nmysql&gt; <i>FLUSH PRIVILEGES;</i>\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql&gt; <i>quit</i>\n<comment>(Verify that the new mailsql user can connect to the mysql server.)</comment>\n\n# <i>mysql -u mailsql -p mailsql</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):482
+msgid "Your new database has default values and tables set up for two domains. The following tables are included:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):488
+msgid "alias - local email alias and mailman alias information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):489
+msgid "relocated - relocated user email address maps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):490
+msgid "transport - default mail transport information for all domains you are hosting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):494
+msgid "users - all user account information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):495
+msgid "virtual - virtual domain email alias maps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):498
+msgid "alias table sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):498
+#, no-wrap
+msgid "\nid   alias      destination\n1    root       foo@bar.com\n2    postmaster foo@bar.com\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):504
+msgid "user table sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):504
+#, no-wrap
+msgid "\n<comment>(Line wrapped for clarity.)</comment>\nid email            clear     name     uid     gid     homedir     \\\n  maildir                                quota  postfix\n10 foo@virt-domain.com $password realname virtid  virtid  /home/vmail \\\n  /home/vmail/virt-domain.com/foo/.maildir/        y\n13 foo@bar.com      $password realname localid localid /home/foo   \\\n  /home/foo/.maildir/                           y\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):514
+msgid "The values of the <c>virtid</c> uid and gid should be those of the <c>vmail</c> user and group."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):519
+msgid "transport table sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):519
+#, no-wrap
+msgid "\nid   domain          destination\n1    bar.com         local:\n2    virt-domain.com virtual:\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):525
+msgid "virtual table sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):525
+#, no-wrap
+msgid "\nid   email                destination\n3    root@virt-domain.com other@email.address\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):535
+msgid "Apache and phpMyAdmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):539
+msgid "Next we'll set up apache and add an interface to interact with the database more easily."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):544
+msgid "Setting up apache and phpmyadmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):544
+#, no-wrap
+msgid "\n# <i>emerge apache phpmyadmin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):548
+msgid "There are plenty of guides out there about how to set up apache with php, including guides provided by the <uri link=\"/proj/en/php/\">Gentoo PHP Project</uri>. There are also numerous posts on <uri>http://forums.gentoo.org</uri> detailing how to solve problems with the installation. So, that said, we're not going to cover it here. Set up the apache and php installs, then continue with this howto. Now, a word for the wise: .htaccess the directory that you put phpmyadmin in. If you do not do this, search engine spiders will come along and index the page which in turn will mean that anyone will be able to find your phpmyadmin page via google and in turn be able to come change your database however they want which is <e>BAD!</e> There are many howtos on this including: <uri>http://www.csoft.net/docs/micro/htaccess.html.en</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):563
+msgid "Now we're going to install the Apache certificates we made previously. The Apache-SSL directives that you need to use the resulting cert are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):569
+msgid "SSLCertificateFile /path/to/certs/new.cert.cert"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):570
+msgid "SSLCertificateKeyFile /path/to/certs/new.cert.key"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):573
+msgid "Install Apache SSL certificates"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):573
+#, no-wrap
+msgid "\n# <i>cp /etc/ssl/misc/new.cert.cert /etc/apache2/ssl/</i>\n# <i>cp /etc/ssl/misc/new.cert.key /etc/apache2/ssl/</i>\n# <i>cd /etc/apache2/vhosts.d</i>\n<comment>(Check if you have an ssl-vhost template already.\n Copy that one instead of the default_vhost if that is the case)</comment>\n# <i>cp 00_default_vhost.conf ssl-vhost.conf</i>\n# <i>nano -w ssl-vhost.conf</i>\n\n<comment>(Change the following parameters)</comment>\nNameVirtualHost host.domain.name:443\n\n&lt;VirtualHost host.domain.name:443&gt;\n  ServerName host.domain.name\n  ServerAdmin your@email.address\n\n  DocumentRoot \"/var/www/localhost/htdocs/phpmyadmin\";\n  &lt;Directory \"/var/www/localhost/htdocs/phpmyadmin\"&gt;\n    ...\n  &lt;/Directory&gt;\n\n  SSLCertificateFile /etc/apache2/ssl/new.cert.cert\n  SSLCertificateKeyFile /etc/apache2/ssl/new.cert.key\n  SSLEngine on\n  ...\n&lt;/VirtualHost&gt;\n\n# <i>nano -w /etc/conf.d/apache2</i>\n<comment>(Add -D SSL -D PHP5 to the APACHE2_OPTS)</comment>\n\n# <i>/etc/init.d/apache2 restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):606
+msgid "Next, configure phpMyAdmin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):610
+msgid "Configuring phpMyAdmin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):610
+#, no-wrap
+msgid "\n# <i>cd /var/www/localhost/htdocs/phpmyadmin</i>\n# <i>cp config.sample.inc.php config.inc.php</i>\n# <i>nano -w config.inc.php</i>\n<comment>(Change the following parameters.)</comment>\n$cfg['blowfish_secret'] = 'someverysecretpassphraze';\n\n$cfg['Servers'][$i]['host'] = 'localhost';          // MySQL hostname\n$cfg['Servers'][$i]['controluser'] = 'mailsql';     // MySQL control user settings\n                                                    // (this user must have read-only\n$cfg['Servers'][$i]['controlpass'] = '$password';   // access to the \"mysql/user\"\n                                                    // and \"mysql/db\" tables)\n$cfg['Servers'][$i]['user'] = 'mailsql';            // MySQL user\n$cfg['Servers'][$i]['password'] = '$password';      // MySQL password\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):626
+msgid "Now enter the phpmyadmin page and browse the tables. You'll want to add in your local aliases, edit your user table to add a test user, and change your transport table to add information about your domains. The default values supplied with the dumpfile should be a sufficient guide to what values need to go where. Make sure that if you put information in the database that it is accurate. For instance, make sure the local user's home dir exists and that the correct uid/gid values are in place. The maildirs should be created automatically by postfix when the user receives their first email. So, in general, it's a good idea to send a \"Welcome\" mail to a new user after you setup their account to make sure the .maildir gets created."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):644
+msgid "Configuring MySQL Authentication and vhosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):648
+msgid "Next we'll reconfigure our authentication to use the mailsql database in courier-imap and postfix. In all of the following examples, replace <c>$password</c> with the password you set for the mailsql mysql user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):654
+msgid "Configuring authentication"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):654
+#, no-wrap
+msgid "\n# <i>nano -w /etc/courier/authlib/authdaemonrc</i>\nauthmodulelist=\"authmysql authpam\"\n\n# <i>nano -w /etc/courier/authlib/authmysqlrc</i>\nMYSQL_SERVER            localhost\nMYSQL_USERNAME       mailsql\nMYSQL_PASSWORD      $password\nMYSQL_DATABASE          mailsql\nMYSQL_USER_TABLE        users\n<comment>(Make sure the following line is commented out since we're storing plaintext.)</comment>\n#MYSQL_CRYPT_PWFIELD    crypt\nMYSQL_CLEAR_PWFIELD     clear\nMYSQL_UID_FIELD         uid\nMYSQL_GID_FIELD         gid\nMYSQL_LOGIN_FIELD       email\nMYSQL_HOME_FIELD        homedir\nMYSQL_NAME_FIELD        name\nMYSQL_MAILDIR_FIELD     maildir\n\n# <i>/etc/init.d/courier-authlib restart</i>\n# <i>/etc/init.d/saslauthd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):678
+msgid "We're almost there, I promise! Next, set up the rest of the necessary configs for postfix to interract with the database for all its other transport needs. Remember to replace each value with the name of your own user, user id, password, alias, email address, and so on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):685
+msgid "/etc/postfix/mysql-aliases.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):685
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/mysql-aliases.cf</i>\n# mysql-aliases.cf\n\nuser         = mailsql\npassword     = $password\ndbname       = mailsql\ntable        = alias\nselect_field = destination\nwhere_field  = alias\nhosts        = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):698
+msgid "/etc/postfix/mysql-relocated.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):698
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/mysql-relocated.cf</i>\n# mysql-relocated.cf\n\nuser         = mailsql\npassword     = $password\ndbname       = mailsql\ntable        = relocated\nselect_field = destination\nwhere_field  = email\nhosts        = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):711
+msgid "/etc/postfix/mysql-transport.cf (optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):711
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/mysql-transport.cf</i>\n# mysql-transport.cf\n\nuser         = mailsql\npassword     = $password\ndbname       = mailsql\ntable        = transport\nselect_field = destination\nwhere_field  = domain\nhosts        = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):724
+msgid "/etc/postfix/mysql-virtual-gid.cf (optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):724
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/mysql-virtual-gid.cf</i>\n# mysql-virtual-gid.cf\n\nuser            = mailsql\npassword        = $password\ndbname          = mailsql\ntable           = users\nselect_field    = gid\nwhere_field     = email\nadditional_conditions = and postfix = 'y'\nhosts           = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):738
+msgid "/etc/postfix/mysql-virtual-maps.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):738
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/mysql-virtual-maps.cf</i>\n# mysql-virtual-maps.cf\n\nuser            = mailsql\npassword        = $password\ndbname          = mailsql\ntable           = users\nselect_field    = maildir\nwhere_field     = email\nadditional_conditions = and postfix = 'y'\nhosts           = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):752
+msgid "/etc/postfix/mysql-virtual-uid.cf (optional)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):752
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/mysql-virtual-uid.cf</i>\n# mysql-virtual-uid.cf\n\nuser            = mailsql\npassword        = $password\ndbname          = mailsql\ntable           = users\nselect_field    = uid\nwhere_field     = email\nadditional_conditions = and postfix = 'y'\nhosts           = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):766
+msgid "/etc/postfix/mysql-virtual.cf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):766
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/mysql-virtual.cf</i>\n# mysql-virtual.cf\n\nuser         = mailsql\npassword     = $password\ndbname       = mailsql\ntable        = virtual\nselect_field = destination\nwhere_field  = email\nhosts        = unix:/var/run/mysqld/mysqld.sock\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):779
+msgid "Lastly, edit <path>/etc/postfix/main.cf</path> one more time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):783
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/main.cf</i>\n<comment>(Ensure that there are no other alias_maps definitions)</comment>\nalias_maps = mysql:/etc/postfix/mysql-aliases.cf\nrelocated_maps = mysql:/etc/postfix/mysql-relocated.cf\n\nlocal_transport = local\nlocal_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname\n\nvirtual_transport = virtual\n<comment>(The domains listed by the mydestination should not be listed in\n the virtual_mailbox_domains parameter)</comment>\nvirtual_mailbox_domains = virt-domain.com, $other-virtual-domain.com\n\nvirtual_minimum_uid = 1000\n<comment>(Substitute $vmail-gid with the GID of the vmail group)</comment>\nvirtual_gid_maps = static:$vmail-gid\nvirtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf\nvirtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf\n<comment>(Substitute $vmail-uid with the UID of the vmail user)</comment>\nvirtual_uid_maps = static:$vmail-uid\nvirtual_mailbox_base = /\n#virtual_mailbox_limit =\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):808
+msgid "For security reasons you should change the permissions of the various <path>/etc/mail/mysql-*.cf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):813
+msgid "Changing file permission"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):813
+#, no-wrap
+msgid "\n# <i>chmod 640 /etc/postfix/mysql-*.cf</i>\n# <i>chgrp postfix /etc/postfix/mysql-*.cf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):818
+msgid "As of Postfix 2.0.x, there were a number of significant changes over the 1.1.x release. Notably the transport, virtual-gid, and virtual-uid tables are no longer necessary. The tables are still included if you wish to use them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(note):824
+msgid "It is recommended that you read VIRTUAL_README included with the postfix docs for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):829
+msgid "Make postfix reload its tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):829
+#, no-wrap
+msgid "\n# <i>postfix reload</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):833
+msgid "Now, if all went well, you should have a functioning mailhost. Users should be able to authenticate against the sql database, using their full email address, for pop3, imap, and smtp. I would highly suggest that you verify that everything is working at this point. If you run into problems (with as many things as this setup has going on, it's likely that you will) check the troubleshooting section of this howto."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):847
+msgid "Squirrelmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):851
+msgid "Install squirrelmail"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):851
+#, no-wrap
+msgid "\n# <i>emerge squirrelmail</i>\n<comment>(Install squirrelmail to localhost so that it's accessed by http://localhost/mail)\n(Substitute 1.4.3a-r2 with the version you use)</comment>\n\n# <i>webapp-config -I -h localhost -d /mail squirrelmail 1.4.3a-r2</i>\n# <i>cd /var/www/localhost/htdocs/mail/config</i>\n# <i>perl ./conf.pl</i>\n<comment>(Change your Organization, Server, and Folder settings for squirrelmail.\nNow you should be able to login to squirrelmail, again - with your full email address,\nand use your new webmail setup.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):869
+msgid "Mailman"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):873
+msgid "Last step: mailman. The new version of mailman has very nice virtual domain support, which is why I use it, not to mention it's really a great package. To get this package installed and working correctly for virtual domains is going to require a bit of hacking. I really recommend reading all of the mailman documentation, including README.POSTFIX.gz, to understand what's being done here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):882
+msgid "Install mailman"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):882
+#, no-wrap
+msgid "\n# <i>emerge mailman</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):886
+msgid "Setting defaults: Mailman/Defaults.py"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):886
+#, no-wrap
+msgid "\n# <i> nano -w /usr/local/mailman/Mailman/Defaults.py</i>\n<comment>(Change the values below to reflect your primary domain, virtuals will be set next.)</comment>\nDEFAULT_EMAIL_HOST = 'domain.com'\nDEFAULT_URL_HOST = 'www.domain.com'\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):893
+msgid "mailman config: mm_cfg.py"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):893
+#, no-wrap
+msgid "\n# <i>nano -w /usr/local/mailman/Mailman/mm_cfg.py</i>\nMTA = \"Postfix\"\nPOSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt-domain.com', 'virt.domain2.com']\nadd_virtualhost('www.virt.domain.com', 'virt.domain.com')\nadd_virtualhost('www.virt.domain2.com', 'virt.domain2.com')\n<comment>(This is required for your virtual domains for mailman to function.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):902
+msgid "And last but not least"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):902
+#, no-wrap
+msgid "\n<comment>(Once that's finished, add your first list.)</comment>\n\n# <i>su mailman</i>\n# <i>cd ~</i>\n# <i>./bin/newlist --urlhost='www.virt-domain.com' --emailhost='virt-domain.com' test</i>\nEnter the email of the person running the list: <i>your@email.address</i>\nInitial test password:\nHit enter to continue with test owner notification...\n<comment>(Virtual domain lists may also be specified with\nlist@domain.com style list names.)</comment>\n# <i>./bin/genaliases</i>\n<comment>(Now that your aliases have been generated,\nverify that they were added successfully.)</comment>\n\n# <i>nano -w data/aliases</i>\n# STANZA START: test\n# CREATED:\ntest:             \"|/usr/local/mailman/mail/mailman post test\"\ntest-admin:       \"|/usr/local/mailman/mail/mailman admin test\"\ntest-bounces:     \"|/usr/local/mailman/mail/mailman bounces test\"\ntest-confirm:     \"|/usr/local/mailman/mail/mailman confirm test\"\ntest-join:        \"|/usr/local/mailman/mail/mailman join test\"\ntest-leave:       \"|/usr/local/mailman/mail/mailman leave test\"\ntest-owner:       \"|/usr/local/mailman/mail/mailman owner test\"\ntest-request:     \"|/usr/local/mailman/mail/mailman request test\"\ntest-subscribe:   \"|/usr/local/mailman/mail/mailman subscribe test\"\ntest-unsubscribe: \"|/usr/local/mailman/mail/mailman unsubscribe test\"\n# STANZA END: test\n\n<comment>(Create the required mailman list)</comment>\n# <i>./bin/newlist mailman</i>\n# <i>./bin/genaliases</i>\n\n<comment>(Return to the root user)</comment>\n# <i>exit</i>\n\n# <i>/etc/init.d/mailman start</i>\n# <i>rc-update add mailman default</i>\n<comment>(To start mailman at once and on every reboot.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):944
+msgid "Adding mailman alias support to postfix"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):944
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/main.cf</i>\nowner_request_special = no\nrecipient_delimiter = +\n<comment>(Read README.POSTFIX.gz for details on this.)</comment>\n\nalias_maps     =\n  hash:/usr/local/mailman/data/aliases,\n  mysql:/etc/postfix/mysql-aliases.cf\n\nvirtual_alias_maps =\n  hash:/usr/local/mailman/data/virtual-mailman,\n  mysql:/etc/postfix/mysql-virtual.cf\n<comment>(This adds mailman alias file support to postfix\nYou may of course use the mysql tables for this,\nbut I hate doing that by hand. Also, if you are not\nusing virtual domains, adding the virtual alias maps\nto postfix may cause problems, be warned.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):964
+msgid "You should now be able to setup mailing lists for any domain on your box. Last note on this, make sure you run all mailman commands as the user mailman (<c>su mailman</c>) or else the permissions will be wrong and you'll have to fix them. Read the mailman doc's for more information on setting up and managing mailman lists."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):977
+msgid "Content Filtering and Anti-Virus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):981
+msgid "For content filtering and Anti-Virus, please consult our <uri link=\"/doc/en/mailfilter-guide.xml\">mail filtering gateway guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):991
+msgid "Wrap Up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):995
+msgid "Ok, you're all set, edit <path>/etc/postfix/master.cf</path> and turn off verbose mode for production use. You'll probably also want to add the services to your startup routine to make sure everything comes back up on a reboot. Make sure to add all the services you're using - apache, mysql, saslauthd, postfix, courier-imapd, courier-imapd-ssl, courier-pop3d, and courier-pop3d-ssl are all up to your decision on what access you want to provide. I generally have all the services enabled."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1005
+msgid "Wrap up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1005
+#, no-wrap
+msgid "\n# <i>postfix reload</i>\n# <i>rc-update add $service default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(e):1011
+msgid "Have fun!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1019
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1024
+msgid "Troubleshooting: This is a short troubleshooting guide for the set up we've detailed how to install here. It is not exhaustive, but meant as a place to get you started in figuring out problems. With a complicated setup such as this, it's imperative that you narrow down the problem to the particular component that is malfunctioning. In general I do that by following a few steps. Start from the base of the system and work your way up, ruling out components that work along the way until you discover which component is having the problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1037
+msgid "Step 1: Check your config files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1040
+msgid "Typos are killers, especially when dealing with authentication systems. Scan your config's and mailsql database for typo's. You can debug all you want, but if you're not passing the right information back and forth to your mail system, it's not going to work. If you make a change to a config file for a service, make sure you restart that service so that the config change gets picked up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1048
+msgid "How to restart a service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1048
+#, no-wrap
+msgid "\n# <i>/etc/init.d/service restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1055
+msgid "Step 2: Are all the necessary services actually running?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1058
+msgid "If it's not running, start it up. It's awful hard to debug a service that isn't running. Sometimes a service will act like it's started but still not function. Sometimes, when a bad config is used, or a bad transmission comes into a mail component, the service will hang and keep the port from being used by another process. Sometimes you can detect this with netstat. Or, if you've been at it awhile, just take a break and reboot your box in the meantime. That will clear out any hung services. Then you can come back fresh and try it again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1068
+msgid "Checking the status of a service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1068
+#, no-wrap
+msgid "\n# <i>/etc/init.d/$service status</i>\n# <i>netstat -a | grep $service (or $port)</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1076
+msgid "Step 3: Are all the service using the current config's?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1079
+msgid "If you've recently made a change to a config file, restart that service to make sure it's using the current version. Some of the components will dump their current config's to you, like postfix."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1085
+msgid "Some services can dump their current config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1085
+#, no-wrap
+msgid "\n# <i>apache2ctl fullstatus</i> (needs lynx installed)\n# <i>apache2ctl configtest</i> (checks config sanity)\n# <i>postconf -n</i> (will tell you exactly what param's postfix is using)\n# <i>/etc/init.d/$service restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1095
+msgid "Step 4: Check the logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1098
+msgid "Repeat after me, logs are my friend. My next troubleshooting stop is always the logs. Sometimes it's helpful to try a failed operation again then check the logs so that the error message is right at the bottom (or top depending on your logger) instead of buried in there somewhere. See if there is any information in your log that can help you diagnose the problem, or at the very least, figure out which component is having the problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1107
+msgid "Checking the logs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1107
+#, no-wrap
+msgid "\n# <i>kill -USR1 `ps -C metalog -o pid=`</i>(to turn off metalog buffering)\n# <i>nano -w /var/log/mail/current</i>\n# <i>cat /var/log/mysql/mysql.log</i>\n# <i>tail /var/log/apache2/error_log</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1114
+msgid "You may also find the debug_peer parameters in main.cf helpful. Setting these will increase log output over just verbose mode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1119
+msgid "adding debug_peer support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1119
+#, no-wrap
+msgid "\n# <i>nano -w /etc/postfix/main.cf</i>\ndebug_peer_level = 5\ndebug_peer_list = $host.domain.name\n<comment>(Uncomment one of the suggested debugger\ncommands as well.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1130
+msgid "Step 5: Talk to the service itself"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1133
+msgid "SMTP, IMAP, and POP3 all respond to telnet sessions. As we've seen earlier when we verified postfix's config. Sometimes it's helpful to open a telnet session to the service itself and see what's happening."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1139
+msgid "Connect to a service with telnet"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1139
+#, no-wrap
+msgid "\n# <i>telnet localhost $port</i>\n<comment>(SMTP is 25, IMAP is 143, POP3 is 110. You should receive at least an OK string,\nletting you know that the service is running and ready to respond to requests.)</comment>\n\nTrying 127.0.0.1...\nConnected to localhost.\nEscape character is '^]'.\n* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1153
+msgid "Step 6: Sometimes only the big guns will give you the information you need: strace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1156
+msgid "You should have this installed anyway. This is an invaluable tool for debugging software. You can start commands from the command line with strace and watch all the system calls as they happen. It often dumps a huge amount of information, so you'll either need to watch it realtime as you retry a failed transaction with the mail system, or dump the output to a file for review."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre:caption):1164
+msgid "Using strace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(pre):1164
+#, no-wrap
+msgid "\n# <i>emerge strace</i>\n# <i>strace $command</i>\n# <i>strace -p `ps -C $service -o pid=`</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(title):1173
+msgid "Step 7: Research"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(p):1176
+msgid "Once you have the information, if you can diagnose and fix the problem, great! If not, you'll probably need to go digging on the net for information that will help you fix it. Here's a list of sites you can check to see if your error has already been resolved. There's also a really good howto on setting up smtp-auth which contains some great debugging ideas."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1185
+msgid "<uri>http://forums.gentoo.org/</uri> - Great forums for gentoo users"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1186
+msgid "<uri>http://bugs.gentoo.org/</uri> - Bugs database for gentoo - great place to look for specific errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1190
+msgid "<uri>http://postfix.state-of-mind.de/</uri> - smtp-auth howto"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1191
+msgid "<uri>http://marc.theaimsgroup.com/?l=postfix-users</uri> - Postfix mailing lists - searchable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1195
+msgid "<uri>http://sourceforge.net/mailarchive/forum.php?forum_id=6705</uri> - Courier-imap mailing list archives - not searchable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1199
+msgid "<uri>http://www.google.com/</uri> - If all else fails, there's always google, which has never failed me"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(li):1203
+msgid "I also spend a lot of time on <uri link=\"irc://irc.gentoo.org/gentoo\">#gentoo</uri>. IRC is a great place to go for help."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//virt-mail-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/vpnc-howto.xml.pot b/doc/gettext/vpnc-howto.xml.pot
new file mode 100644
index 0000000..68a98b2
--- /dev/null
+++ b/doc/gettext/vpnc-howto.xml.pot
@@ -0,0 +1,728 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):6
+msgid "Gentoo vpnc HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):9
+msgid "dhaskew@earthlink.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail):9
+msgid "David H. Askew"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):17
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):12
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail):12
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):15
+msgid "fauli@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail):15
+msgid "Christian Faulhammer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):18
+msgid "fischer@unix-ag.uni-kl.de"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail):18
+msgid "Thomas Fischer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(author:title):20
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(mail:link):21
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(abstract):24
+msgid "This document details how to connect your workstation to a Cisco VPN concentrator utilizing vpnc to manage the connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(version):33
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(date):34
+msgid "2010-07-29"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):37
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):41
+msgid "If you're reading this, then you likely need to connect to your office network from home or during travel. Many companies utilize Cisco 3000 VPN concentrators for their VPN needs, and I am willing to bet that most Linux newbies think that they are forced to use Windows to connect to them. Well, this document informs you that connecting to a Cisco VPN is very possible and will hopefully enable you to setup a working tunnel using your Gentoo workstation or laptop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):53
+msgid "What this document is"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):57
+msgid "A guide to the basic workings of <c>vpnc</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):58
+msgid "A discussion of DNS and routing issues that relate to VPNs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):59
+msgid "Examples of managing VPN sessions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):60
+msgid "Useful tips and tricks (hopefully)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):66
+msgid "What this document is not"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):70
+msgid "An in-depth guide to VPN/encryption technologies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):71
+msgid "A feature by feature explanation of <c>vpnc</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):77
+msgid "Assumptions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):80
+msgid "The assumptions made at this point are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):85
+msgid "You have Gentoo installed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):86
+msgid "You have Internet access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):87
+msgid "You want to connect to a Cisco 3000 VPN concentrator"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):88
+msgid "You know how to configure, build, and install a new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):96
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):100
+msgid "In order for Linux to be able to open a VPN connection <e>Universal TUN/TAP device driver support</e> must be enabled in the kernel. What is it and why do you need it? Below is a relatively straight forward explanation from the kernel configuration dialog:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):107
+msgid "CONFIG_TUN"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):107
+#, no-wrap
+msgid "\nTUN/TAP provides packet reception and transmission for user space\nprograms. It can be viewed as a simple Point-to-Point or Ethernet\ndevice, which instead of receiving packets from a physical media,\nreceives them from user space program and instead of sending packets\nvia physical media writes them to the user space program.\n\nWhen a program opens /dev/net/tun, driver creates and registers\ncorresponding net device tunX or tapX. After a program closed above\ndevices, driver will automatically delete tunXX or tapXX device and\nall routes corresponding to it.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):120
+msgid "You can verify yourself if your kernel has TUN/TAP support with the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):125
+msgid "Checking the kernel config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):125
+#, no-wrap
+msgid "\n# <i> grep \"TUN\" /usr/src/linux/.config</i>\nCONFIG_INET_TUNNEL=m\n# CONFIG_INET6_TUNNEL is not set\n# CONFIG_IPV6_TUNNEL is not set\n<comment>(TUN/TAP enabled as a module)</comment>\nCONFIG_TUN=m\n# CONFIG_8139TOO_TUNE_TWISTER is not set\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):135
+msgid "As you can see above, <c>CONFIG_TUN=m</c> is compiled as a module. If it is disabled in your setup, enable it in your kernel of choice, rebuild, install, reboot and return to this document before continuing with the next steps."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):141
+msgid "Configuration location in the kernel configuration dialog"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):141
+#, no-wrap
+msgid "\nDevice Drivers  ---&gt;\n  Network device support  ---&gt;\n    [*] Universal TUN/TAP device driver support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):147
+msgid "If you built TUN/TAP support directly into the kernel, you should see information from <c>dmesg</c> output like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):152 ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):174
+msgid "Checking dmesg output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):152 ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):174
+#, no-wrap
+msgid "\n# <i>dmesg | grep TUN</i>\nUniversal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):157
+msgid "If you build TUN/TAP support as a module, you first must load the <c>tun</c> module:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):162
+msgid "Load tun module"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):162
+#, no-wrap
+msgid "\n# <i>modprobe tun</i>\n# <i>lsmod</i>\nModule                  Size  Used by\ntun                     7296  0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):169
+msgid "Now that the <c>tun</c> module is loaded, check <c>dmesg</c> output. You should see something like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):184
+msgid "Install Needed Software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):188
+msgid "Now that you have a working kernel setup, you need to install <c>net-misc/vpnc</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):193
+msgid "Installing vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):193
+#, no-wrap
+msgid "\n# <i>emerge -av net-misc/vpnc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):202
+msgid "Example Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):206
+msgid "In order to make the following sections more clear, we need an example setup to work from. For the purposes of this exercise, we will assume that you have a home network of several computers. All computers are on the 192.168.0.0 / 255.255.255.0 network. The LAN in question is run by a Gentoo box using an iptables firewall, DHCP, caching DNS, etc ... and it masquerades the LAN behind the public IP address it receives from an ISP. You also have a workstation on the LAN from which you want to be able to VPN into your office with."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):216
+msgid "Our example workstation configuration looks like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):220
+msgid "Our workstation configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):220
+#, no-wrap
+msgid "\n<comment>(Name server configuration)</comment>\n# <i>cat /etc/resolv.conf</i>\nnameserver      192.168.0.1\n\n<comment>(Network configuration)</comment>\n# <i>cat /etc/hosts</i>\n127.0.0.1       desktop localhost\n192.168.0.1     router\n192.168.2.2     mediacenter\n\n<comment>(Interface configuration)</comment>\n# <i>ifconfig -a</i>\neth0      Link encap:Ethernet  HWaddr 00:11:2F:8D:08:08\n          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0\n          inet6 addr: fe80::211:2fff:fe8d:808/64 Scope:Link\n          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1\n          RX packets:3657889 errors:0 dropped:0 overruns:0 frame:0\n          TX packets:2305893 errors:0 dropped:0 overruns:0 carrier:0\n          collisions:0 txqueuelen:1000\n          RX bytes:2193722103 (2092.0 Mb)  TX bytes:1415104432 (1349.5 Mb)\n          Interrupt:185 Memory:fac00000-0\n\nlo        Link encap:Local Loopback\n          inet addr:127.0.0.1  Mask:255.0.0.0\n          inet6 addr: ::1/128 Scope:Host\n          UP LOOPBACK RUNNING  MTU:16436  Metric:1\n          RX packets:35510 errors:0 dropped:0 overruns:0 frame:0\n          TX packets:35510 errors:0 dropped:0 overruns:0 carrier:0\n          collisions:0 txqueuelen:0\n          RX bytes:16023838 (15.2 Mb)  TX bytes:16023838 (15.2 Mb)\n\n<comment>(Routing information)</comment>\n# <i>netstat -r</i>\nKernel IP routing table\nDestination     Gateway         Genmask         Flags   MSS Window  irtt Iface\n192.168.0.0     *               255.255.255.0   U         0 0          0 eth0\nloopback        desktop         255.0.0.0       UG        0 0          0 lo\ndefault         router          0.0.0.0         UG        0 0          0 eth0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):266
+msgid "Configuring vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):270
+msgid "Now that you have <c>vpnc</c> installed and we have an example to work from, let's discuss the basics of setting up <c>vpnc</c>. The configuration file for <c>vpnc</c> connection settings can be located in a couple places, depending on how many profiles you want to setup. By default, <c>vpnc</c> looks first for <path>/etc/vpnc/default.conf</path> for its connection settings. If it doesn't find that file, then it looks for <path>/etc/vpnc.conf</path>. This setup will only address a single profile example and will use the configuration file location <path>/etc/vpnc.conf</path>. Make sure you do <e>not</e> have a <path>/etc/vpnc/default.conf</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):282
+msgid "Example /etc/vpnc.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):282
+#, no-wrap
+msgid "\nIPSec gateway vpngateway.domain.org\nIPSec ID group_id\nIPSec secret group_password\nXauth username network_signon\nXauth password network_password\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):290
+msgid "The configuration file example above should be modified to reflect the appropriate values for your setup. The gateway option <c>vpngateway.domain.org</c> can be a fully qualified domain name or an IP address. The ID and secret options should be given to you by a network administrator. If you cannot obtain this information but you currently have a working setup on a Windows box which utilizes the official Cisco VPN client, then all you have to do is export your profile. The user name and password options are for your normal network sign-on, such as a Windows NT domain account."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):302
+msgid "If you are forced to export your profile from a Windows machine, then what you will likely have is a file ending in <path>.pcf</path>. This file will have all the information you need. Below is an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):308
+msgid "Example profile.pcf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):308
+#, no-wrap
+msgid "\n[main]\nDescription=\nHost=VPNGATEWAY.DOMAIN.ORG\nAuthType=1\nGroupName=group_id\nGroupPwd=\nenc_GroupPwd=F3256220AA200A1D532556024F4F314B0388D48B0FBF2DB12\nEnableISPConnect=0\nISPConnectType=0\nISPConnect=FOOBAR\nISPCommand=\nUsername=\nSaveUserPassword=0\nUserPassword=\nenc_UserPassword=\nNTDomain=\nEnableBackup=0\nBackupServer=\nEnableMSLogon=1\nMSLogonType=0\nEnableNat=1\nTunnelingMode=0\nTcpTunnelingPort=10000\nCertStore=0\nCertName=\nCertPath=\nCertSubjectName=\nCertSerialHash=00000000000000000000000000000000\nSendCertChain=0\nVerifyCertDN=\nDHGroup=2\nForceKeepAlives=0\nPeerTimeout=90\nEnableLocalLAN=0\nEnableSplitDNS=1\nForceNetLogin=0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):347
+msgid "In the above example, we can see entries for <c>Host</c>, <c>GroupName</c> and <c>enc_GroupPwd</c>. Your <c>Username</c> and <c>UserPassword</c> may or may not be exported depending on the setup. To generate a working vpnc configuration out of it, you can use <c>pcf2vpnc</c>, included with vpnc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):354
+msgid "You can decrypt the password with the help from the <c>cisco-decrypt</c> program, shipped with the latest vpnc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):362
+msgid "Testing your setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):365
+msgid "Now that you have a configuration in place, it's time to test your setup. To start <c>vpnc</c> you do the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):370
+msgid "Example vpnc usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):370
+#, no-wrap
+msgid "\n# <i>vpnc</i>\nEnter password for username@vpngateway.domain.org:\nVPNC started in background (pid: 14788)...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):376
+msgid "As you can see from the above command output, once you type <c>vpnc</c> (as root), you are prompted for your password. After entering your password, which will not be echoed back to you, the <c>vpnc</c> process will automatically become a background process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):383
+msgid "If you specified the <c>Xauth password</c> option in your <c>vpnc</c> config file, then you will not be prompted for your password at <c>vpnc</c> startup. Additionally, if <c>vpnc</c> needs some extra options not specified in the configuration file, or if you have forgotten something, don't worry, it will ask you for it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):391
+msgid "Sample interface configuration changes made by vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):391
+#, no-wrap
+msgid "\n# <i> ifconfig -a</i>\neth1      Link encap:Ethernet  HWaddr 00:11:2F:8D:08:08\n          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0\n          inet6 addr: fe80::211:2fff:fe8d:808/64 Scope:Link\n          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1\n          RX packets:2101119 errors:0 dropped:0 overruns:0 frame:0\n          TX packets:1577559 errors:0 dropped:0 overruns:0 carrier:0\n          collisions:0 txqueuelen:1000\n          RX bytes:1757862627 (1676.4 Mb)  TX bytes:732200131 (698.2 Mb)\n          Interrupt:177 Memory:faa00000-0\n\nsit0      Link encap:IPv6-in-IPv4\n          NOARP  MTU:1480  Metric:1\n          RX packets:0 errors:0 dropped:0 overruns:0 frame:0\n          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0\n          collisions:0 txqueuelen:0\n          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)\n\ntun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00\n          inet addr:192.168.160.42  P-t-P:192.168.160.42  Mask:255.255.255.255\n          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1412  Metric:1\n          RX packets:1 errors:0 dropped:0 overruns:0 frame:0\n          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0\n          collisions:0 txqueuelen:500\n          RX bytes:60 (60.0 b)  TX bytes:616 (616.0 b)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):419
+msgid "Sample routing modifications made by vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):419
+#, no-wrap
+msgid "\n# <i>netstat -r</i>\nKernel IP routing table\nDestination     Gateway         Genmask         Flags   MSS Window  irtt Iface\nvpn01.domain.or router          255.255.255.255 UGH    1500 0          0 eth1\n192.168.0.0     *               255.255.255.0   U         0 0          0 eth1\nloopback        desktop         255.0.0.0       UG        0 0          0 lo\ndefault         *               0.0.0.0         U         0 0          0 tun0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):429
+msgid "As you can see from the above command output(s), <c>vpnc</c> has done the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):435
+msgid "Created the tun0 network interface, a virtual interface to handle the traffic across your VPN tunnel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):439
+msgid "Obtained the IP address for the tun0 device from your VPN provider"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):440
+msgid "Set the default route to your VPN gateway"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):443
+msgid "At this point, your workstation is capable of communicating with hosts via the VPN. Because <c>vpnc</c> sets your default route to your VPN gateway, all network traffic will travel across the VPN, even if it destined for the Internet or elsewhere not specifically specified by additional routes. For some, this basic type of connection may be satisfactory, but for most, additional steps need to be taken."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):452
+msgid "Additional things you might want to have:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):457
+msgid "DNS for the VPN"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):458
+msgid "A routing setup that will only send traffic destined for the VPN down the virtual tunnel. This way, you can browse the Internet while connected to the VPN, without your personal web/p2p etc. traffic going across the tunnel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(li):464
+msgid "A script to manage all this, because <c>vpnc</c> just doesn't do enough by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):470
+msgid "When you are ready to end the VPN session, execute <c>vpnc-disconnect</c>. An example is shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):475
+msgid "Don't disconnect yet, because we have additional things to test. The example below is just for informational purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):480
+msgid "vpnc-disconnect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):480
+#, no-wrap
+msgid "\n# <i>vpnc-disconnect</i>\nTerminating vpnc daemon (pid: 26250)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):490
+msgid "Set up DNS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):494
+msgid "Unfortunately, <c>vpnc</c> doesn't handle the setup and management of DNS for your newly established tunnel. The user is left to decide how DNS should be handled. You could just overwrite <path>/etc/resolv.conf</path> when you connect, but that would utilize your VPN DNS for all DNS queries regardless of whether or not the traffic is destined for your VPN tunnel. This is a very functional solution and if you simply need to connect to the tunnel, do your work, and then disconnect, read no further. But, if you want to be able to leave your tunnel connected for lengthy periods of time and don't want your work DNS servers handling requests for your personal traffic, read on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):506
+msgid "The ideal setup would allow you to separate your DNS queries into two categories: VPN-related and other. Under this setup, all VPN-related DNS queries would be answered by DNS servers located at the other end of your VPN tunnel and all other queries would continue to be answered by local or ISP supplied DNS servers. This is the setup that will be demonstrated here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):514
+msgid "We will consider VPN-related DNS queries to be any query belonging to the example.org domain, such as host1.example.org or server1.example.org."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):519
+msgid "So how do you set things up, so that only requests made to hosts on the example.org domain get sent to VPN supplied DNS servers? Well, you're going to need to install a local DNS server, but don't worry, it's much easier than you think. There are several software packages that can handle the type of setup we desire, but for the purposes of this demonstration, <c>dnsmasq</c> will be utilized. Let's emerge it now:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):528
+msgid "This DNS server software will not be available to the network, and will only answer requests from localhost, <c>127.0.0.1</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):533
+msgid "Install dnsmasq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):533
+#, no-wrap
+msgid "\n# <i>emerge dnsmasq</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):537
+msgid "Now you need to add an option to your <c>dnsmasq</c> startup options. Edit the following option to suit your needs. Substitute .example.org with the appropriate domain and the IP address with a valid DNS server that belongs to the VPN tunnel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):544
+msgid "/etc/conf.d/dnsmasq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):544
+#, no-wrap
+msgid "\nConfig file for /etc/init.d/dnsmasq\n\n# See the dnsmasq(8) man page for possible options to put here.\nDNSMASQ_OPTS=\"-S /.example.org/192.168.125.10\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):551
+msgid "Next, make sure that the first entry in <path>/etc/resolv.conf</path> is your local host <c>127.0.0.1</c>, followed by the location of the backup DNS servers that should handle the DNS traffic in case dnsmasq fails to start, or if it needs to forward a DNS query it doesn't currently have in its cache. An example <path>/etc/resolv.conf</path> is shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):559
+msgid "/etc/resolv.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):559
+#, no-wrap
+msgid "\nnameserver 127.0.0.1\nnameserver 192.168.0.1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):564
+msgid "Now that you have setup a rule for your VPN tunnel DNS, you need to start <c>dnsmasq</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):569
+msgid "Starting up dnsmasq"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):569
+#, no-wrap
+msgid "\n# <i>/etc/init.d/dnsmasq start</i>\n# <i>rc-update add dnsmasq default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):579
+msgid "Configuring the routing table"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):583
+msgid "The ideal scenario would be if only the traffic destined for VPN tunnel would travel across the link. At this point, you have a VPN tunnel setup and all traffic will travel across the tunnel, unless you specify additional routes. In order to fix this situation you need to know what networks are available to you on your VPN. The easiest way to find out the needed information is to ask a network administrator, but sometimes they are reluctant to answer such questions. If your local network admin won't provide the needed information, some trial and error experiments will be required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):594
+msgid "When the VPN tunnel was started, <c>vpnc</c> set the default route to the tunnel. So you must set your default route back to normal, so that things work as expected."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):600
+msgid "Resetting your default route"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):600
+#, no-wrap
+msgid "\n# <i>route add default gw 192.168.0.1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):604
+msgid "Earlier, when DNS services were being configured for your VPN, you specified a DNS server to handle your example.org domain. You need to add a route for the 192.168.125.0 subnet so that DNS queries will work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):610
+msgid "Adding a route for dns"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):610
+#, no-wrap
+msgid "\n# <i>route add -net 192.168.125.0 netmask 255.255.255.0 dev tun0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):614
+msgid "At this point, you should add any additional routes for known networks (such as for the subnet 192.168.160.0, which includes the IP address received by the TUN/TAP virtual device). If your friendly network administrator gave you the required info, great. Otherwise, you might need to ping hosts you will be connecting to frequently, to give yourself an idea about what your routing table should look like."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):623
+msgid "Due to your setup, when using VPN network services by name, you must specify the fully qualified domain name, for instance: webserver1.example.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):628
+msgid "Ping example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):628
+#, no-wrap
+msgid "\n# <i>ping intranet1.example.org</i>\nPING intranet1.example.org (172.25.230.29) 56(84) bytes of data.\n\n\n--- intranet1.example.org ping statistics ---\n18 packets transmitted, 0 received, 100% packet loss, time 16997ms\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):637
+msgid "As you can see from the above example, the ping probes to <c>intranet1.example.org</c> were unsuccessful. So we need to add a route for that subnet."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):643
+msgid "another route command example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):643
+#, no-wrap
+msgid "\n# <i>route add -net 172.25.230.0 netmask 255.255.255.0 dev tun0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):647
+msgid "A few ping and route commands later, you should be well on your way to a well working routing table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):657
+msgid "Manage the connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):659
+msgid "Calling vpnc when needed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):662
+msgid "Next is an example script to manage the VPN connection. You could execute it (as root) from an xterm to start a connection to your VPN. Then all you have to do is press return to disconnect the VPN. Obviously you will need to modify this for your setup, remembering to add all the additional routes that you may need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):670
+msgid "Example session management script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):670
+#, no-wrap
+msgid "\n#!/bin/bash\n\nsource /sbin/functions.sh\n\nebegin \"Connecting to the VPN\"\nvpnc\neend\n\nebegin \"Modifying the routing table\"\nroute add default gw 192.168.0.1\nroute add -net 172.25.230.0 netmask 255.255.255.0 dev tun0\nroute add -net 192.168.160.0 netmask 255.255.255.0 dev tun0\nroute add -net 192.168.125.0 netmask 255.255.255.0 dev tun0\neend\n\neinfo \"Press any key to disconnect ...\"\n\nread $disconnect\n\nebegin \"Disconnecting from the VPN\"\nvpnc-disconnect\neend\nebegin \"Reconfiguring the default routing table\"\nroute add default gw 192.168.0.1\neend\n\neinfo \"VPN should now be disconnected\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):703
+msgid "Start vpnc on boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):706
+msgid "Version 0.4.0-r1 of vpnc contains an init script (<path>/etc/init.d/vpnc</path>) which can handle multiple configurations. The default script looks for <path>/etc/vpnc/vpnc.conf</path>, but as many configurations as can be imagined are possible. Before and after shutdown and start-up custom-made scripts can be executed that are connected by their name to the corresponding init script (since version 0.5.1-r1). Their names end in <path>-preup.sh</path>, <path>-postup.sh</path>, <path>-predown.sh</path> and <path>-postdown.sh</path>, stored in the <path>/etc/init.d/scripts.d/</path> directory. The general naming scheme is sketched in the following table."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(th):720
+msgid "init script name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(th):721
+msgid "needed configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(th):722
+msgid "preup script name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):725
+msgid "/etc/init.d/vpnc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):726
+msgid "/etc/vpnc/vpnc.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):727
+msgid "/etc/vpnc/scripts.d/vpnc-preup.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):730
+msgid "/etc/init.d/vpnc.work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):731 ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):840
+msgid "/etc/vpnc/work.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(ti):732 ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):823
+msgid "/etc/vpnc/scripts.d/work-preup.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):736
+msgid "Add vpnc to default runlevel with the following commands (in this case for the standard configuration). Don't forget to add the tun module (if you have built it that way) to the kernels autoload mechanism at startup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):742
+msgid "Adding vpnc to startup scripts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):742
+#, no-wrap
+msgid "\n# <i>rc-update add vpnc default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):746
+msgid "If you don't want to save your password in the configuration file, you can tell the init script to show all output and prompts on standard output by editing <path>/etc/conf.d/vpnc</path>. Set the variable <c>VPNCOUTPUT</c> to yes or no, where its default is to not display screen output."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(note):753
+msgid "The init scripts don't handle DNS separation, but you can use the custom scripts to achieve that. See <uri link=\"#tipsscript\">Tips and Tricks</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):763
+msgid "Tips and Tricks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):765
+msgid "Graphical remote access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):768
+msgid "If you are looking for a Linux application that supports RDP (Remote Desktop Protocol) then give <c>grdesktop</c> a try. It's a GUI app written in GTK+ that fits in well with a Gnome desktop, but doesn't require it. If you don't want the GUI configuration dialogs that grdesktop provides, then just install <c>rdesktop</c>. Ultimately, grdesktop is just a frontend for rdesktop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):776
+msgid "If you are a KDE user, you might want to try <c>kvpnc</c>. It a appears to be a very mature VPN management GUI."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):781
+msgid "If you need to connect to a Windows machine which doesn't have a DNS entry, and you know the address of an available WINS server, you can use a tool called <c>nmblookup</c> to query the WINS server for the host name of the machine you want to connect to. Unfortunately, you have to install <c>samba</c> to get it, but if you are going to be working with boxes running Windows you might as well want to install samba, because it includes several other useful tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):790
+msgid "Installing samba"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):790
+#, no-wrap
+msgid "\n# <i>emerge -av samba</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):794
+msgid "When you have samba and its tools installed, test <c>nmblookup</c> by asking the WINS server at IP address 192.168.125.11 about a host named wintelbox1."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):799
+msgid "nmblookup example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):799
+#, no-wrap
+msgid "\n# <i>nmblookup -U 192.168.125.11 -R 'wintelbox1'</i>\nquerying wintelbox1 on 192.168.125.11\n172.25.230.76 wintelbox1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):808
+msgid "Custom scripts on boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):811
+msgid "The custom-made scripts for the <path>init.d</path> file can be used to setup a user-defined routing for the vpnc connection. The examples below show how to setup the routing table so that only connections to 123.234.x.x are routed over the VPN and all other connections use the default gateway. The example uses work-preup.sh to save the current default gateway before starting vpnc (which resets the default gateway using the VPN connection). Once vpnc has been started, <path>work-postup.sh</path> deletes this new default gateway, restores the old default gateway and sets the route for all connections to 123.234.x.x to use the vpnc connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):823
+#, no-wrap
+msgid "\n#!/bin/sh\nroute -n | grep -E '^0.0.0.0 ' | cut -c 17-32 &gt;/var/tmp/defaultgw\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre:caption):828
+msgid "/etc/vpnc/scripts.d/work-postup.sh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):828
+#, no-wrap
+msgid "\n#!/bin/sh\nroute del -net 0.0.0.0 netmask 0.0.0.0 dev tun1\nroute add default gw $(cat /var/tmp/defaultgw)\nroute add -net 123.234.0.0 netmask 255.255.0.0 dev tun1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):835
+msgid "The example scripts assume that the vpnc connection uses tun1 as tun device. You can set the device name in the connection's configuration file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(pre):840
+#, no-wrap
+msgid "\nInterface name tun1\nIPSec gateway vpn.mywork.com\nPidfile /var/run/vpnc.work.pid\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):851
+msgid "Useful Links"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri:link):857
+msgid "http://www.unix-ag.uni-kl.de/~massar/vpnc/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri):857
+msgid "vpnc homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri:link):860
+msgid "http://home.gna.org/kvpnc/en/index.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri):860
+msgid "kvpnc homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri:link):863
+msgid "http://www.nongnu.org/grdesktop/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(uri):863
+msgid "grdesktop homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(title):872
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(p):876
+msgid "Hopefully by now you have been able to connect to your VPN of choice and are well on your way to remote office work. Feel free to file a bug at <uri link=\"http://bugs.gentoo.org\">bugs.gentoo.org</uri> should you find a mistake or wish to make an addition or recommendation regarding this document."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//vpnc-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/vserver-howto.xml.pot b/doc/gettext/vserver-howto.xml.pot
new file mode 100644
index 0000000..d2a0cd3
--- /dev/null
+++ b/doc/gettext/vserver-howto.xml.pot
@@ -0,0 +1,72 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(guide:link):5
+msgid "/doc/en/vserver-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(guide:redirect):5
+msgid "/proj/en/vps/vserver-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(title):6
+msgid "Gentoo Linux-VServer Howto"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(mail:link):9
+msgid "hollow@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(mail):9
+msgid "Benedikt Boehm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(mail:link):12
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(mail):12
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(abstract):15
+msgid "In this Howto you will learn to setup a basic virtual server using the Linux-VServer Technology"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(version):24
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(date):25
+msgid "2006-10-06"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(title):28
+msgid "Moved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(p):32
+msgid "This document has been moved to a <uri link=\"/proj/en/vps/vserver-howto.xml\">new location</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//vserver-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/xen-guide.xml.pot b/doc/gettext/xen-guide.xml.pot
new file mode 100644
index 0000000..38d09a1
--- /dev/null
+++ b/doc/gettext/xen-guide.xml.pot
@@ -0,0 +1,444 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):7
+msgid "Configuring Gentoo with Xen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(mail:link):10
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(mail):10
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(abstract):13
+msgid "This guide describes how to start using Xen on your Gentoo system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(version):21
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(date):22
+msgid "2010-05-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):25 ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):56 ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):391
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):29
+msgid "The <uri link=\"http://www.xensource.com/\">Xen</uri> technology allows you to run multiple operating systems on a single physical system, govern resource consumption and even migrate domains (which are the virtual environments in which a guest operating system runs) from one Xen-powered system to another. Xen requires the host operating system to support Xen (which, in this case, will be a Linux kernel) but guest operating systems can run unmodified <e>if</e> your hardware supports Intel Virtualization Technology (VT-x) or AMD Virtualization Technology (SVM). Otherwise your guest operating systems must also support Xen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):40
+msgid "This guide will talk you through the configuration steps necessary to get Xen up and running on Gentoo Linux. We will not discuss Xen itself (the Xen project has <uri link=\"http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user\">decent documentation</uri> available) nor will we talk about specialized setups that might be very interesting for Xen setups but are not Xen-related (like exporting Portage through NFS, booting Linux using PXE, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):54
+msgid "Preparing Domain0"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):59
+msgid "<e>Domain0</e> is the primary domain under Xen, hosting the host operating system which governs all other domains. In this chapter we will prepare an existing Gentoo installation to become the host operating system in this domain and build the Xen-powered kernel so that Gentoo is ready to host other Xen domains."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):70
+msgid "Rebuilding the Gentoo Installation ?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):73
+msgid "A dramatic change that might be necessary is to rebuild the entire Gentoo installation with a different <c>CFLAGS</c> setting. Guest operating systems running under Xen might otherwise see major performance degradation. If you, however, are planning on checking out Xen rather than installing it for production use and are not terribly fond of rebuilding all programs, you can skip this step. In this case you will notice performance degradation but you will still be able to use Xen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(impo):83
+msgid "It is advised that, if you change your <c>CFLAGS</c> and build your system with a gcc lower than version 4, you do not have <c>-Os</c> set as it has been reported to produce broken code."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):89
+msgid "Editing the CFLAGS and rebuild the Gentoo installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):89
+#, no-wrap
+msgid "\n~# <i>nano -w /etc/make.conf</i>\n<comment>(Add -mno-tls-direct-seg-refs)</comment>\nCFLAGS=\"-O2 -march=pentium4 -pipe <i>-mno-tls-direct-seg-refs</i>\"\n\n~# <i>emerge -e world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):97
+msgid "If you boot your system using an initial ramdisk (initrd) you need to rebuild the initrd as well (which is best done by running all steps you would do when you rebuild your kernel)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):106
+msgid "Installing Xen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):109
+msgid "Xen actually contains many components, so you'll need to install a couple of packages. Because it is still <uri link=\"/doc/en/handbook/handbook-x86.xml?part=3&amp;chap=3#doc_chap2\">~arch masked</uri> you first need to unmask it by adding the necessary lines to <path>/etc/portage/package.keywords</path> and then install them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):117
+msgid "Unmasking and Installing Xen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):117
+#, no-wrap
+msgid "\n~# <i>nano -w /etc/portage/package.keywords</i>\napp-emulation/xen\napp-emulation/xen-tools\nsys-kernel/xen-sources\n\n~# <i>emerge xen xen-tools xen-sources</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):131 ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):213 ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):266
+msgid "Building the Kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):134
+msgid "Next we'll build the Linux kernel with Xen support. This kernel, whose sources are available at <path>/usr/src/linux-2.6.x.z-xen</path>, will be our main running kernel (i.e. the one running domain 0). In the <c>XEN</c> section you'll find drivers for all kinds of input/output, each driver having a <e>backend</e> and <e>frontend</e> implementation available. For the domain 0 kernel you need to select the <e>backend</e> implementation: these are used by the other domains (who use the <e>frontend</e> drivers) to communicate directly with the hardware."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):145
+msgid "Of course, don't forget to select <c>Xen-compatible</c> at <c>Processor type and features</c>. If you're wondering about networking: each interface in a domain has a point-to-point link to an interface on domain 0 (called <path>vifX.Y</path> where X is the domain number and Y the Yth interface of that domain), so you can configure your network the way you want (bridging, NAT, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):154
+msgid "Enabling Xen Support for i386 Kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):154
+#, no-wrap
+msgid "\nProcessor type and features  ---&gt;\n      Subarchitecture Type (Xen-compatible)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):159
+msgid "Enabling Xen Support for x86_64 Kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):159
+#, no-wrap
+msgid "\nProcessor type and features  ---&gt;\n      Subarchitecture Type (PC-compatible)\n  [*] Enable Xen compatible kernel\n  [*] Support for hot-pluggable CPUs\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):166
+msgid "Domain-0 Kernel Config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):166
+#, no-wrap
+msgid "\nBus options (PCI etc.)  ---&gt;\n  [*] PCI support\n  [ ]   Xen PCI Frontend Debugging\n\nNetworking  ---&gt;\n  Networking options  ---&gt;\n    &lt;*&gt; 802.1d Ethernet Bridging\n    <comment>Only required by bridged networking.</comment>\n\nXEN  ---&gt;\n  [*] Privileged Guest (domain 0)\n  &lt;*&gt; Backend driver support\n  &lt;*&gt;   Block-device backend driver\n  &lt;*&gt;   Network-device backend driver\n  &lt;*&gt;   PCI-device backend driver\n           PCI Backend Mode (Virtual PCI) ---&gt;\n  [*] Scrub memory before freeing it to Xen\n  [*] Disable serial port drivers\n      Xen version compatibility (3.0.4 and later)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):188
+msgid "Domain-U Kernel Config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):188
+#, no-wrap
+msgid "\nBus options (PCI etc.)  ---&gt;\n  [ ] PCI support\n\nDevice Drivers  ---&gt;\n  SCSI device support  ---&gt;\n    &lt; &gt; SCSI device support\n    <comment>Disabling SCSI support frees up the /dev/sd* device names\n    for use as Xen virtual block devices.</comment>\n\nXEN  ---&gt;\n  [ ] Privileged Guest (domain 0)\n  &lt;*&gt; Block-device frontend driver\n  &lt;*&gt; Network-device frontend driver\n  [*] Scrub memory before freeing it to Xen\n  [*] Disable serial port drivers\n      Xen version compatibility (3.0.4 and later)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):207
+msgid "A nice hint is to have the kernel make process store its intermediate object files elsewhere so that you can reuse the same kernel tree to build different configurations:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):213
+#, no-wrap
+msgid "\n~# <i>mkdir -p ~/build/dom0 ~/build/domU</i>\n~# <i>make O=~/build/dom0 menuconfig</i>\n<comment>(Configure the kernel)</comment>\n~# <i>make O=~/build/dom0 &amp;&amp; make O=~/build/dom0 modules_install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):220
+msgid "Once the kernel is built you'll find the kernel image immediately in the build directory (not inside <path>arch/</path> or any other directory) called <path>vmlinuz</path>. Copy it to <path>/boot</path> and then configure your bootloader to use the Xen hypervisor (one of the components installed previously) which is stored as <path>/boot/xen.gz</path>. In the bootloader configuration, add your newly built kernel as the kernel that Xen should boot. For instance, for GRUB:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):230
+msgid "GRUB Configuration for Xen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):230
+#, no-wrap
+msgid "\ntitle Xen 3.0 / Gentoo Linux 2.6.x.y\nroot (hd0,0)\nkernel /boot/xen.gz\nmodule /boot/kernel-2.6.x.y-xen0 root=/dev/hda3\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):237
+msgid "Now reboot your system into Xen. Once you are booted, you need to load the Xen daemon:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):242
+msgid "Loading the Xen daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):242
+#, no-wrap
+msgid "\n~# <i>/etc/init.d/xend start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):246
+msgid "Now check if you can do whatever you normally do on your system. If this is the case, you can edit your bootloader configuration to always boot into Xen and add the Xen deamon to the default runlevel so that it is started automatically next time you boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(note):253
+msgid "If you wish to start guest domains automatically on boot add <c>xendomains</c> to the default runlevel as well and create a symlink in <path>/etc/xen/auto/</path> to the Xen configuration files for the domains you wish to start."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):264
+msgid "Creating an Unpriviledged Domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):269
+msgid "Go to the Xen-powered Linux kernel source and update the configuration. It is wise to keep as many topics as possible similar to the main kernel except the <c>XEN</c> settings where drivers should now have their <e>frontend</e> implementation selected instead of the <e>backend</e>. Then build the kernel and place the resulting <path>vmlinuz</path> file where you want (we assume this is <path>/mnt/data/xen/kernel</path>):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):278
+msgid "Building the guest kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):278
+#, no-wrap
+msgid "\n~# <i>make O=~/build/domU</i>\n~# <i>cp ~/build/domU/vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):283
+msgid "It is also possible to create a single kernel image for both the administrative domain and the unpriviledged domain. More information about this can be found in the Xen user manual."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):292
+msgid "Creating the Domain Disks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):295
+msgid "For best performance, it is best to dedicate a partition (or logical volume) to a domain rather than a file based filesystem. However, if you are going to use Xen primarily for tests using a file based filesystem does have its advantages (especially regarding maintenance)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):302
+msgid "You can create a file based filesystem using <c>dd</c> and <c>mke2fs</c> (or any other file system creation tool). For instance, to create a 2Gbyte ext3 filesystem:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):308
+msgid "Creating a file based filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):308
+#, no-wrap
+msgid "\n~# <i>dd if=/dev/zero of=/mnt/data/xen/disks/ext3root.img bs=1M count=2048</i>\n~# <i>mke2fs -j /mnt/data/xen/disks/ext3root.img</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):316
+msgid "Configuring a Domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):319
+msgid "Next we create a Xen configuration file for a domain. You can store these configuration files where you want, for instance at <path>/mnt/data/xen/configs</path>. As an example, we create a configuration file for a small Gentoo environment which uses the disk image we created previously:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):327
+msgid "Creating a domain configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):327
+#, no-wrap
+msgid "\n~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n\nkernel = \"/mnt/data/xen/kernel/kernel-2.6.x.y-xen\"\nmemory = 512\nname   = \"gentoo\"\n<comment>(Map the disk image to the virtual /dev/sda1)</comment>\ndisk   = ['file:/mnt/data/xen/disks/ext3root.img,sda1,w']\nroot   = \"/dev/sda1 ro\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):338
+msgid "If you are using a block device (such as an lvm volume or partition) for the disk use 'phy:' instead of 'file:' and leave off /dev. For example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):343
+msgid "Using a block device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):343
+#, no-wrap
+msgid "\n<comment>(LVM Volume)</comment>\ndisk = [ 'phy:lvm/xen-guest-root,sda1,w' ]\n\n<comment>(Physical Partition)</comment>\ndisk = [ 'phy:sdb6,sda1,w' ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):351
+msgid "You can find example configuration files in <path>/etc/xen</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):358
+msgid "Launching the New Domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):361
+msgid "Now we're all set and we can launch the new domain. If the disk image contained an operating system, we could just create and attach the domain using the <c>xm</c> command (Xen manager):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):367
+msgid "Creating and starting a new domain"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):367
+#, no-wrap
+msgid "\n~# <i>xm create /mnt/data/xen/configs/gentoo -c</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):371
+msgid "The domain would be booted inside the terminal in which you executed the command. However, in our case, the disk image is empty so the domain won't boot up in anything useful. To fix this, you can loop-mount the image and install Gentoo as you're used to."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):378
+msgid "If you want to disconnect from the domain, press <path>Ctrl+]</path>. You can always reconnect to the domains' console using <c>xm console gentoo</c>. However, there is only one console per domain, so only use it when you can't access the domain otherwise (for instance, through SSH)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):389
+msgid "Networking on Unpriviledged Domains"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):394
+msgid "Xen supports at least two ways of configuring your (virtual) network: <e>routed</e> and <e>bridged</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):399
+msgid "When selecting the <e>routed</e> approach, the interface inside your unpriviledged domain is connected to the virtual interface on your administrative domain. On your administrative domain (domain 0), the virtual interface is linked together with <path>eth0</path>. The interface inside your unpriviledged domain should have an IP address on the same network as the interface on the administrative domain. Any communication to that IP address can only occur from the administrative domain, unless you set up specific routing rules."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):410
+msgid "When selecting the <e>bridged</e> approach, your default network interface on the administrative domain becomes a bridge which accepts connections to the virtual domains as well as to the IP address your administrative domain has."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):419
+msgid "Regular Routed Interfaces"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):422
+msgid "Before you set up the interface on your unpriviledged domain, make sure that Xen's <path>netloop</path> and <path>netbk</path> drivers are loaded. A quick hint: if you have <path>netloop</path> as a module, load it with <c>nloopbacks=0</c> so that it doesn't create pointless interfaces to the loopback device. Then, edit your domain configuration file and add a <c>vif</c> instruction to it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):431 ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):487
+msgid "Configuring a virtual interface"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):431
+#, no-wrap
+msgid "\n~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n\n<comment>(Add the vif instruction)</comment>\nvif    = [ 'ip=192.168.1.101, vifname=veth1' ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):438
+msgid "In the above example, the interface will be created for the unpriviledged domain (in which it will be called <path>eth0</path>) and Xen will ensure that address 192.168.1.101 will be reachable from the administrative domain through interface <path>veth1</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):445
+msgid "This doesn't mean that the virtual <path>eth0</path> interface will automatically have IP 192.168.1.101 assigned to it, but rather that, if you don't give it that IP, it will not be connected with the administrative domain and thus cannot be reached."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):452
+msgid "Now edit <path>/etc/xen/xend-config.sxp</path> as follows to select routed network configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):457 ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):499
+msgid "Editing xend-config.sxp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):457
+#, no-wrap
+msgid "\n~# <i>nano -w /etc/xen/xend-config.sxp</i>\n\n<comment>(Comment out the following lines)</comment>\n<i>#</i>(network-script network-bridge)\n<i>#</i>(vif-script vif-bridge)\n\n<comment>(Enable the following lines)</comment>\n(network-script network-route)\n(vif-script vif-route)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):472
+msgid "Bridged Interfaces"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):475
+msgid "Unlike the routed interfaces you now need to load the <path>netloop</path> driver with <c>nloopbacks=1</c> (or higher) as the additional loopback devices are used to create the bridge. For the other modules you still need the <path>netbk</path> module as well as briding functionality (<path>bridge</path> module if build as such)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):483
+msgid "Now edit your virtual domain and add the <c>vif</c> construct:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):487
+#, no-wrap
+msgid "\n~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n\n<comment>(Add the vif instruction)</comment>\nvif    = [ 'ip=192.168.1.101, vifname=veth0' ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):494
+msgid "Next edit <path>/etc/xen/xend-config.sxp</path> as follows to select bridged network configuration:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):499
+#, no-wrap
+msgid "\n~# <i>nano -w /etc/xen/xend-config.sxp</i>\n\n<comment>(Enable the following lines)</comment>\n(network-script network-bridge)\n(vif-script vif-bridge)\n\n<comment>(Comment out the following lines if not done already)</comment>\n<i>#</i> (network-script network-route)\n<i>#</i> (vif-script vif-route)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):511
+msgid "By default, the bridge will contain whatever interface is configured to be the default interface (the device that is listed under the default route through <c>ip route list</c>). If you want to alter this behavior, edit the <path>xend-config.sxp</path> as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):518
+msgid "Editing xend-config.sxp to change bridge configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):518
+#, no-wrap
+msgid "\n~# <i>nano -w /etc/xen/xend-config.sxp</i>\n\n<comment>(Edit the network-script line)</comment>\n(network-script <i>'</i>network-bridge <i>netdev=eth0 bridge=xenbr0 vifnum=0'</i>)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):525
+msgid "Once the configuration is done, restart the <c>xend</c> init script to have Xen build the bridge:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):530
+msgid "Restarting the xend daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):530
+#, no-wrap
+msgid "\n~# <i>/etc/init.d/xend restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):538
+msgid "Further Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):540
+msgid "Xen Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):545
+msgid "http://tx.downloads.xensource.com/downloads/docs/user/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):545
+msgid "Xen Users' Manual"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):549
+msgid "http://xen.xensource.com/documentation.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):549
+msgid "Xen Community Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):553
+msgid "http://wiki.xensource.com/xenwiki/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):553
+msgid "Xen Wiki"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):560
+msgid "Xen Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(li):564
+msgid "<uri link=\"http://virt-manager.et.redhat.com/\">app-emulation/virt-manager</uri> is a graphical tool for administering virtual machines"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/xfce-config.xml.pot b/doc/gettext/xfce-config.xml.pot
new file mode 100644
index 0000000..9e6e82e
--- /dev/null
+++ b/doc/gettext/xfce-config.xml.pot
@@ -0,0 +1,493 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):6
+msgid "The Xfce Configuration Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(mail:link):9
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(abstract):12
+msgid "This guide provides an extensive introduction to Xfce, a fast, lightweight, full-featured desktop environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(version):21
+msgid "1.28"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(date):22
+msgid "2010-08-31"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):25
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):27
+msgid "The Xfce desktop environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):30
+msgid "<uri link=\"http://www.xfce.org\">Xfce</uri> is a fast, lightweight desktop environment for Unix-like operating systems. It is designed for productivity, and is quite configurable while still adhering to the <uri link=\"http://www.freedesktop.org\">Freedesktop</uri> specifications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):37
+msgid "Unlike heavier desktop environments, such as <uri link=\"http://www.gnome.org\">Gnome</uri> and <uri link=\"http://www.kde.org\">KDE</uri>, Xfce uses far fewer system resources. Additionally, it offers greater modularity and fewer dependencies; it takes up less space on your hard disk and takes less time to install."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):45
+msgid "This guide will not only show you how to install and configure a minimal Xfce environment, but will also explore options to create a full-featured desktop in keeping with the Xfce philosophy: light, fast, and modular."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):56 ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):100
+msgid "Installing Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):58
+msgid "The basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):61
+msgid "First, make sure you've configured Xorg as shown in the <uri link=\"/doc/en/xorg-config.xml\">X Server Configuration Howto</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):66
+msgid "Next, double-check your USE flags in <path>/etc/make.conf</path>; you'll probably at least want <c>USE=\"-gnome -kde -minimal -qt4 branding dbus hal jpeg lock session startup-notification thunar X\"</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):72
+msgid "There's also another variable you can set in <path>/etc/make.conf</path> called XFCE_PLUGINS. This variable controls additional Xfce plugins for the panel. You can enable all of the plugins by adding <c>XFCE_PLUGINS=\"brightness menu trash</c> to <path>/etc/make.conf</path>. Here's a brief summary of the plugins:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dt):81
+msgid "brightness"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dd):82
+msgid "Lets you add a screen brightness applet to your panel, once you have installed <c>xfce4-power-manager</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dt):86
+msgid "menu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dd):87
+msgid "Lets you add a program menu to your panel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dt):88
+msgid "trash"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(dd):89
+msgid "Lets you add a Trash can to the panel. The Trash allows you to quickly delete files or recover them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):95
+msgid "Now that you've set your <c>USE</c> and <c>XFCE_PLUGINS</c> variables in <path>/etc/make.conf</path>, it's time to install Xfce."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):100
+#, no-wrap
+msgid "\n# <i>emerge -avt xfce4-meta</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):104
+msgid "Next, add your regular user(s) to the <c>plugdev</c>, <c>cdrom</c>, <c>cdrw</c>, and <c>usb</c> groups, so that they can take full advantage of <c>hal</c> and be able to mount and use devices such as cameras, optical drives, and USB sticks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):110
+msgid "Adding users to the hardware groups"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):110
+#, no-wrap
+msgid "\n<comment>(Replace username with your actual user)</comment>\n# <i>for x in plugdev cdrom cdrw usb ; do gpasswd -a username $x ; done</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):115
+msgid "Next, update your environment variables:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):119
+msgid "Updating environment variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):119
+#, no-wrap
+msgid "\n# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):123
+msgid "Now start up <c>hald</c> and add it to the default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):127
+msgid "Starting hald"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):127
+#, no-wrap
+msgid "\n# <i>/etc/init.d/hald start</i>\n# <i>rc-update add hald default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):132
+msgid "You'll also need a graphical terminal so that you can continue working with your new desktop environment. <c>x11-terms/terminal</c> is a good choice, as it's made specifically for Xfce. Install Terminal as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):138
+msgid "Installing Terminal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):138
+#, no-wrap
+msgid "\n# <i>emerge x11-terms/terminal</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):147
+msgid "Configuring Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):149 ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):174
+msgid "Starting Xfce"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):152
+msgid "Now that Xfce is now installed, we'll configure it to be the default desktop environment when we issue the <c>startx</c> command. Exit your root shell and log on as a regular user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):158
+msgid "Setting Xfce as the default desktop environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):158
+#, no-wrap
+msgid "\n$ <i>echo \"exec startxfce4\" &gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(note):162
+msgid "If you have ConsoleKit installed, your <path>~/.xinitrc</path> should instead contain <c>exec ck-launch-session startxfce4</c>. Otherwise, some of your applications may stop working. You'll also need to add consolekit to the default runlevel by running the following command as root: <c>rc-update add consolekit default</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):170
+msgid "Now start your graphical environment by typing <c>startx</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):174
+#, no-wrap
+msgid "\n$ <i>startx</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):178
+msgid "Congratulations, and welcome to your new Xfce desktop environment. Go ahead, explore it a bit. Then continue reading to learn how you can configure Xfce to suit your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):187
+msgid "Program access"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):190
+msgid "You might notice right-clicking on the desktop shows you the menu of all your applications. It's useful, but your desktop can easily be completely obscured by open windows, making it hard to to launch a new program. So, one of the first things you may wish to do is give yourself a handy application menu on your panel. Right click on this panel, and choose \"Add New Item\". Scroll through the list of choices and select \"Xfce Menu\". You can choose where you want it to be displayed on your panel. When clicked, it displays the application/preferences menu, providing a nicely categorized list of your installed programs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):204
+msgid "Sessions &amp; startup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):207
+msgid "If you've installed (or plan to install) popular Gnome or KDE applications such as <c>k3b</c>, <c>nautilus</c>, <c>kmail</c>, <c>evolution</c>, etc. then you should make sure that Xfce launches the appropriate services for these at startup. Navigate to Menu --&gt; Settings --&gt; Sessions &amp; Startup. On the \"Advanced\" tab, select the appropriate checkbox. This might slightly increase Xfce startup times, but it decreases load times for KDE and Gnome applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):216
+msgid "Xfce has the ability to save your session settings and running programs from the \"General\" tab in the Sessions &amp; Startup menu. They can be automatically saved when you logout, or Xfce can ask you each time. This feature is particularly useful for undoing configuration mistakes. Accidentally killed a panel? Just select \"No\" when prompted to save your current session, and the next time you start Xfce, your old desktop is restored. Want to automatically launch your open webbrowser, terminal, and email client the next time you login? Just save your session before logging out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):227
+msgid "You've now got a basic working environment installed and configured. But if you're interested in doing more, then continue reading!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):237
+msgid "Additional Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):239
+msgid "Panel plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):242
+msgid "In this chapter, we'll discuss some useful plugins and applications for everyday use within Xfce."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):247
+msgid "There are many plugins for the panel available in Portage; see for yourself with <c>emerge --search xfce</c>. Though for the most part their names are self-explanatory, a few deserve extra attention, as they are quite helpful. To use them, simply <c>emerge</c> them. They'll be added to the list of available items in the \"Add New Items\" menu shown when you right-click on the panel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):256
+msgid "<c>xfce4-battery-plugin</c> is perfect for laptop users. It displays battery percentage, time remaining, power source (AC or battery), fan status, warnings, and can even be configured to execute commands at certain power levels. This feature can be used to put the laptop into hibernate mode when the battery is almost exhausted."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):263
+msgid "<c>xfce4-verve-plugin</c> is a small command line embedded into the panel. It's quicker than opening up another terminal when you want to run a command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):268
+msgid "<c>xfce4-mount-plugin</c> gives you a handy method of mounting devices listed in <path>/etc/fstab</path> just by clicking your mouse"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):272
+msgid "<c>xfce4-sensors-plugin</c> lets you monitor your hardware sensors, such as CPU temperature, fan RPM, hard drive temp, motherboard voltage, and more"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):278
+msgid "If you can't find what you're looking for in the plugins specifically made for Xfce, try searching through the list of Gnome panel applets! That's right, by first emerging <c>xfce4-xfapplet-plugin</c>, you can install and run any applet made for Gnome."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):288
+msgid "Useful programs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):291
+msgid "We should now <c>emerge</c> some useful applications and utilities: <c>xfce4-mixer</c>, <c>xfprint</c>, <c>xfce4-taskmanager</c>, <c>xfwm4-themes</c>, <c>orage</c>, <c>mousepad</c>, <c>xfce4-power-manager</c>, <c>x11-terms/terminal</c>, and <c>thunar</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):298
+msgid "<c>xfce4-mixer</c> is a volume control for your sound card. It can also be run as a panel applet, giving you fast access to playback volume. <c>xfprint</c> provides easy printer management and job control; it's a must if you intend to do any printing from your desktop. <c>xfce4-taskmanager</c> displays a list of all running programs, and the CPU and memory consumption each one takes up. By right-clicking an item, you can kill a misbehaving application, pause and restart it, or even alter its runtime priority, which lets you fine-tune how much of a demand it puts on your system's resources."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):309
+msgid "<c>xfwm4-themes</c> adds several window manager themes. You may want to add a more full-coverage icon theme such as <c>tango-icon-theme</c> just to round out your desktop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):315
+msgid "<c>orage</c> is a simple, handy calendar. <c>mousepad</c> is a barebones text editor that starts up extremely quickly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):320
+msgid "<c>xfce4-power-manager</c> is an application to monitor and manage power usage. This is especially important for laptops! The power manager allows you to adjust screen brightness, choose maximum performance or battery-saving modes, and setup hibernate, suspend, and shutdown actions when the lid is shut or buttons are pressed. You can set <uri link=\"http://goodies.xfce.org/projects/applications/xfce4-power-manager\">xfce4-power-manager</uri> to warn you when your battery reaches certain levels, or even turn off your machine. The application comes with a couple of helpful panel plugins to display battery/charging status, and a brightness control."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):332
+msgid "<c>x11-terms/terminal</c> is an X11 terminal emulator, far more configurable and useful than the barebones <c>xterm</c>. <c>terminal</c> supports Unicode text, color schemes, pseudo-transparency and hardware-accelerated transparency via Xfce's built-in compositor, all out-of-the-box. Just make sure that the default action on the terminal launcher of your panel runs <path>/usr/bin/Terminal</path> instead of <path>xterm</path>. Right-click the launcher and choose \"Properties\" to change the command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):342
+msgid "<c>thunar</c> is Xfce's default graphical file manager. It's fast yet quite powerful, can support several plugins for even more functionality; just install them with <c>emerge</c>. Let's take a look:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):349
+msgid "<c>thunar-archive-plugin</c> lets you create and extract archive files using the right-click menu. It provides a handy <uri link=\"http://www.foo-projects.org/~benny/projects/thunar-archive-plugin\">front-end</uri> for graphical archiving applications such as <c>xarchiver</c>, <c>squeeze</c>, and <c>file-roller</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):356
+msgid "<c>thunar-media-tags-plugin</c> lets you intelligently rename multiple media files at once, and lets you <uri link=\"http://thunar.xfce.org/pwiki/projects/thunar-media-tags-plugin\">edit</uri> their information tags, such as id3 and ogg tags."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):362
+msgid "<c>thunar-thumbnailers</c> lets you <uri link=\"http://goodies.xfce.org/projects/thunar-plugins/thunar-thumbnailers\">preview</uri> certain types of files from within Thunar, such as images and fonts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):367
+msgid "<c>thunar-volman</c> automatically <uri link=\"http://foo-projects.org/~benny/projects/thunar-volman/\">manages</uri> removable media and drives."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):374
+msgid "Next, let's see about adding some useful but lightweight desktop applications, in keeping with Xfce's philosophy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):379
+msgid "Though <c>mousepad</c> is nice enough as a basic text editor, if you need a full-featured word processor but don't want the bloat of OpenOffice, try emerging <c>abiword</c>. <uri link=\"http://www.abisource.com\">AbiWord</uri> is lighter, faster, and is completely interoperable with industry-standard document types. It can also be further extended with <c>abiword-plugins</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):387
+msgid "Need a nice email client/newsreader that isn't as demanding as <c>thunderbird</c> or <c>evolution</c>? Try emerging <c>claws-mail</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):392
+msgid "For your internet chat needs, <c>irssi</c> is an excellent, tiny, incredibly configurable IRC client that runs in your terminal. If you prefer a compact all-in-one client that handles nearly all chat protocols, you may want to <c>emerge pidgin</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):399
+msgid "If you need movie and music players, look no further than <c>mplayer</c> and <uri link=\"/proj/en/desktop/sound/decibel.xml\">decibel-audio-player</uri>. They can play most every media format available quite nicely."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):405
+msgid "Finally, you'll need a webbrowser. Nearly all graphical webbrowsers require more resources than most of your other desktop applications. Still, <c>firefox</c> (or <c>firefox-bin</c>) is always a good choice. Alternatively, you may find <c>opera</c> to be quite fast. However, <c>opera</c> is not available on as many processor architectures as <c>firefox</c>, and it has more dependencies unless you override them with a few USE flags."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):414
+msgid "Adding a webbrowser"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):414
+#, no-wrap
+msgid "\n<comment>(Installing Mozilla Firefox)</comment>\n# <i>emerge firefox</i>\n<comment>(Installing Opera)</comment>\n# <i>echo \"www-client/opera gtk -kde\" &gt;&gt; /etc/portage/package.use</i>\n# <i>emerge opera</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):422
+msgid "Now that we've explored some good suggestions for rounding out your desktop applications, let's see what else we can do to enhance your Xfce experience."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):430
+msgid "Graphical login"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):433
+msgid "Remember when we added <c>startxfce4</c> to our <path>~/.xinitrc</path>? All you have to do to get into your desktop is type <c>startx</c> after logging in. This is fine if you prefer a completely text-based boot and login, but let's use a display manager that will automatically start Xfce after booting (so that you can login graphically)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):441
+msgid "First, let's make sure Xfce loads at boot:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):445
+msgid "Adding xdm to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):445
+#, no-wrap
+msgid "\n# <i>rc-update add xdm default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):449
+msgid "We aren't quite finished yet. We have to pick a display manager and set the appropriate variable. Though there are a few choices available in Portage, for this guide, we'll stick with <uri link=\"http://slim.berlios.de\">SLiM</uri>, the Simple Login Manager."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):456
+msgid "<c>slim</c> is speedy and lightweight, with minimal dependencies. Perfect for Xfce!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):461
+msgid "Installing SLiM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):461
+#, no-wrap
+msgid "\n# <i>emerge -avt slim</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(note):465
+msgid "The <c>branding</c> USE flag will pull in the <c>slim-themes</c> package, which will give you an assortment of login themes, including a Gentoo Linux theme."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):470
+msgid "Then edit the DISPLAYMANAGER variable in <path>/etc/conf.d/xdm</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):474
+msgid "Editing /etc/conf.d/xdm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):474
+#, no-wrap
+msgid "\nDISPLAYMANAGER=\"slim\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):478
+msgid "SLiM can automatically start your Xfce session if you add <c>XSESSION=\"Xfce4\"</c> to <path>/etc/env.d/90xsession</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):483
+msgid "Setting XSESSION"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):483
+#, no-wrap
+msgid "\n# <i>echo XSESSION=\\\"Xfce4\\\" &gt; /etc/env.d/90xsession</i>\n# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):491
+msgid "Beautifying your desktop"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):494
+msgid "A little customization of your desktop's appearance can go a long way. Xfce has all the options you'd expect from a modern desktop environment, font antialiasing settings, color schemes, dozens of window decorations, themes, and more. If these aren't enough, it's easy to install third-party themes, icon sets, mouse cursor themes, and wallpapers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):502
+msgid "A selection of nice Gentoo wallpapers in a variety of resolutions are hosted on the <uri link=\"/main/en/graphics.xml\">Gentoo website</uri>. If you're looking for icon sets and complete Xfce themes, <uri link=\"http://www.xfce-look.org/\">Xfce-Look</uri> has a huge collection. The important thing to remember about any third-party eyecandy you download is that it will usually first need to be unpacked and then installed to the proper directory. Icon sets go in <path>/usr/share/icons/</path>, and themes go to <path>/usr/share/themes/</path>; use these directories when you want all users to be able to access themes and icon sets. Individual users can install themes and icon sets to <path>~/.themes/</path> and <path>~/.icons/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):515
+msgid "If you installed SLiM as your display manager, there are lots of themes in the <c>slim-themes</c> package available in Portage. Also, be sure to check the SLiM <uri link=\"http://slim.berlios.de/themes01.php\">themes page</uri> for more themes. Creating your own SLiM theme is fairly easy; just read the <uri link=\"http://slim.berlios.de/themes_howto.php\">Themes HowTo</uri>. Gentoo also ships a <c>slim-themes</c> package that you can <c>emerge</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):524
+msgid "Finally, Xfce has its own built-in compositor to manage window transparency. This option can be found in Menu --&gt; Settings --&gt; Window Manager. For best performance, you will need to be running a graphics card with drivers that support hardware-accelerated rendering. Make sure you emerged <c>xfwm4</c> with the <c>xcomposite</c> USE flag. Next, you will need to enable compositing in <path>/etc/X11/xorg.conf</path> by adding the following section:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):533
+msgid "Enabling composite in xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):533
+#, no-wrap
+msgid "\nSection \"Extensions\"\n    Option  \"Composite\"  \"Enable\"\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):539
+msgid "This is the bare minimum configuration required for Xfce and Xorg-X11. However, setting up hardware-accelerated rendering depends on your individual graphics card, and is beyond the scope of this guide. Please see the other guides in the <uri link=\"/doc/en/index.xml?catid=desktop\">Desktop Documentation Resources</uri> list to learn about configuring hardware-accelerated rendering for your graphics card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):548
+msgid "Once you've finished setting up a beautiful Xfce desktop, the next thing to do is take a picture of it to share with other folks! Just install <c>xfce4-screenshooter</c> and post your pictures somewhere for all to admire."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):559
+msgid "Summary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):563
+msgid "Congratulations on making it this far! You've installed and configured a speedy desktop environment with a solid suite of applications for your computing needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):572
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):575
+msgid "Need additional help on configuring and using Xfce? Need more lightweight application suggestions? Try checking out:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(uri:link):581
+msgid "http://forums.gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(uri):581
+msgid "The Gentoo forums"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):582
+msgid "#xfce on irc.freenode.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(li):583
+msgid "The installed help files and other documentation provided by Xfce: <path>/usr/share/xfce4/doc/C/index.html</path>. Just point your browser at it and start reading. There are even a lot of \"hidden\" configuration options detailed in the help files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(uri:link):589
+msgid "http://www.xfce.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(uri):589
+msgid "Xfce's home page"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/xml-guide.xml.pot b/doc/gettext/xml-guide.xml.pot
new file mode 100644
index 0000000..ada22ad
--- /dev/null
+++ b/doc/gettext/xml-guide.xml.pot
@@ -0,0 +1,852 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):6
+msgid "Gentoo GuideXML Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):14
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):9
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):12
+msgid "drobbins@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail):12
+msgid "Daniel Robbins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author):14
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):17 ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):20 ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):18
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail):18
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):21
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail):21
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(abstract):27
+msgid "This guide shows you how to compose web documentation using the new lightweight Gentoo GuideXML syntax. This syntax is the official format for Gentoo documentation, and this document itself was created using GuideXML. This guide assumes a basic working knowledge of XML and HTML."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(version):38
+msgid "10"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(date):39
+msgid "2009-02-27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):42
+msgid "GuideXML basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):44
+msgid "GuideXML design goals"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):47
+msgid "The guideXML syntax is lightweight yet expressive, so that it is easy to learn yet also provides all the features we need for the creation of web documentation. The number of tags is kept to a minimum -- just those we need. This makes it easy to transform guide into other formats, such as DocBook XML/SGML or web-ready HTML."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):55
+msgid "The goal is to make it easy to <e>create</e> and <e>transform</e> guideXML documents."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):63
+msgid "Further Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):66
+msgid "If you are planning on contributing documentation to Gentoo, or you want to test GuideXML, please read our <uri link=\"/proj/en/gdp/doc/doc-tipsntricks.xml\">Doc Tips 'n' Tricks</uri> guide which contains tips and tricks for documentation development."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):73
+msgid "You may want to look at the <uri link=\"?passthru=1\">XML source</uri> of this document while you read it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):83
+msgid "GuideXML"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):85
+msgid "Basic structure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):88
+msgid "Let's start learning the GuideXML syntax. We'll start with the the initial tags used in a GuideXML document:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):93
+msgid "The initial part of a guide XML document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):93
+#, no-wrap
+msgid "\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE guide SYSTEM \"/dtd/guide.dtd\"&gt;\n&lt;!-- $Header$ --&gt;\n\n&lt;guide link=\"<i>/doc/en/guide.xml</i>\" lang=\"<i>en</i>\"&gt;\n&lt;title&gt;<i>Gentoo Documentation Guide</i>&lt;/title&gt;\n\n&lt;author title=\"<i>Author</i>\"&gt;\n  &lt;mail link=\"<i>yourname@gentoo.org</i>\"&gt;<i>Your Name</i>&lt;/mail&gt;\n&lt;/author&gt;\n\n&lt;abstract&gt;\n<i>This guide shows you how to compose web documentation using\nour new lightweight Gentoo GuideXML syntax.  This syntax is the official\nformat for Gentoo web documentation, and this document itself was created\nusing GuideXML.</i>\n&lt;/abstract&gt;\n\n&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt;\n&lt;!-- See http://creativecommons.org/licenses/by-sa/2.5 --&gt;\n&lt;license/&gt;\n\n&lt;version&gt;<i>1.0</i>&lt;/version&gt;\n&lt;date&gt;<i>2004-12-25</i>&lt;/date&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):120
+msgid "On the first lines, we see the requisite tag that identifies this as an XML document and specifies its DTD. The <c>&lt;!-- $Header$ --&gt;</c> line will be automatically modified by the CVS server and helps to track revisions. Next, there's a <c>&lt;guide&gt;</c> tag -- the entire guide document is enclosed within a <c>&lt;guide&gt; &lt;/guide&gt;</c> pair. <br/> The <c>link</c> attribute is optional and should preferably contain the absolute path to the document relatively to the document root even though the file name alone will work. It is only used to generate a link to a printer-friendly version of your document and check whether a translation is up-to-date. Our XSL back-engine passes the actual path to our XSL stylesheet. The link attribute is only used as a fall-back value in case the XML is processed by other means. <br/> The <c>lang</c> attribute should be used to specify the language code of your document. It is used to format the date and insert strings like \"<e>Note</e>\", \"<e>Content</e>\", etc. in the specified language. The default is English."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):140
+msgid "Next, there's a <c>&lt;title&gt;</c> tag, used to set the title for the entire guide document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):145
+msgid "Then, we come to the <c>&lt;author&gt;</c> tags, which contain information about the various authors of the document. Each <c>&lt;author&gt;</c> tag allows for an optional <c>title</c> element, used to specify the author's relationship to the document (author, co-author, editor, etc.). In this particular example, the authors' names are enclosed in another tag -- a <c>&lt;mail&gt;</c> tag, used to specify an email address for this particular person. The <c>&lt;mail&gt;</c> tag is optional and can be omitted, and at least one <c>&lt;author&gt;</c> element is required per guide document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):156
+msgid "Next, we come to the <c>&lt;abstract&gt;</c>, <c>&lt;version&gt;</c> and <c>&lt;date&gt;</c> tags, used to specify a summary of the document, the current version number, and the current version date (in YYYY-MM-DD format) respectively. Dates that are invalid or not in the YYYY-MM-DD format will appear verbatim in the rendered document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):164
+msgid "This sums up the tags that should appear at the beginning of a guide document. Besides the <c>&lt;title&gt;</c> and <c>&lt;mail&gt;</c> tags, these tags shouldn't appear anywhere else except immediately inside the <c>&lt;guide&gt;</c> tag, and for consistency it's recommended (but not required) that these tags appear before the content of the document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):172
+msgid "Finally we have the <c>&lt;license/&gt;</c> tag, used to publish the document under the <uri link=\"http://creativecommons.org/licenses/by-sa/2.5/\">Creative Commons - Attribution / Share Alike</uri> license as required by the <uri link=\"/proj/en/gdp/doc/doc-policy.xml\">Documentation Policy</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):182
+msgid "Chapters and sections"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):185
+msgid "Once the initial tags have been specified, you're ready to start adding the structural elements of the document. Guide documents are divided into chapters, and each chapter can hold one or more sections. Every chapter and section has a title. Here's an example chapter with a single section, consisting of a paragraph. If you append this XML to the XML in the <uri link=\"#doc_chap2_pre1\">previous excerpt</uri> and append a <c>&lt;/guide&gt;</c> to the end of the file, you'll have a valid (if minimal) guide document:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):196
+msgid "Minimal guide example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):196
+#, no-wrap
+msgid "\n&lt;chapter&gt;\n&lt;title&gt;<i>This is my chapter</i>&lt;/title&gt;\n&lt;section&gt;\n&lt;title&gt;<i>This is section one of my chapter</i>&lt;/title&gt;\n&lt;body&gt;\n\n&lt;p&gt;\n<i>This is the actual text content of my section.</i>\n&lt;/p&gt;\n\n&lt;/body&gt;\n&lt;/section&gt;\n&lt;/chapter&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):212
+msgid "Above, I set the chapter title by adding a child <c>&lt;title&gt;</c> element to the <c>&lt;chapter&gt;</c> element. Then, I created a section by adding a <c>&lt;section&gt;</c> element. If you look inside the <c>&lt;section&gt;</c> element, you'll see that it has two child elements -- a <c>&lt;title&gt;</c> and a <c>&lt;body&gt;</c>. While the <c>&lt;title&gt;</c> is nothing new, the <c>&lt;body&gt;</c> is -- it contains the actual text content of this particular section. We'll look at the tags that are allowed inside a <c>&lt;body&gt;</c> element in a bit."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(note):223
+msgid "A <c>&lt;guide&gt;</c> element must contain at least one <c>&lt;chapter&gt;</c> elements, a <c>&lt;chapter&gt;</c> must contain at least one <c>&lt;section&gt;</c> elements and a <c>&lt;section&gt;</c> element must contain at least one <c>&lt;body&gt;</c> element."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):233
+msgid "An example &lt;body&gt;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):236
+msgid "Now, it's time to learn how to mark up actual content. Here's the XML code for an example <c>&lt;body&gt;</c> element:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):241
+msgid "Example of a body element"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):241
+#, no-wrap
+msgid "\n&lt;p&gt;\nThis is a paragraph.  &lt;path&gt;/etc/passwd&lt;/path&gt; is a file.\n&lt;uri&gt;http://forums.gentoo.org&lt;/uri&gt; is my favorite website.\nType &lt;c&gt;ls&lt;/c&gt; if you feel like it.  I &lt;e&gt;really&lt;/e&gt; want to go to sleep now.\n&lt;/p&gt;\n\n&lt;pre caption=\"Code Sample\"&gt;\nThis is text output or code.\n# &lt;i&gt;this is user input&lt;/i&gt;\n\nMake HTML/XML easier to read by using selective emphasis:\n&lt;foo&gt;&lt;i&gt;bar&lt;/i&gt;&lt;/foo&gt;\n\n&lt;comment&gt;(This is how to insert a comment into a code block)&lt;/comment&gt;\n&lt;/pre&gt;\n\n&lt;note&gt;\nThis is a note.\n&lt;/note&gt;\n\n&lt;warn&gt;\nThis is a warning.\n&lt;/warn&gt;\n\n&lt;impo&gt;\nThis is important.\n&lt;/impo&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):271
+msgid "Now, here's how the <c>&lt;body&gt;</c> element above is rendered:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):275
+msgid "This is a paragraph. <path>/etc/passwd</path> is a file. <uri>http://forums.gentoo.org</uri> is my favorite web site. Type <c>ls</c> if you feel like it. I <e>really</e> want to go to sleep now."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):281
+msgid "Code Sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):281
+#, no-wrap
+msgid "\nThis is text output or code.\n# <i>this is user input</i>\n\nMake HTML/XML easier to read by using selective emphasis:\n&lt;foo&gt;<i>bar</i>&lt;/foo&gt;\n\n<comment>(This is how to insert a comment into a code block)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(note):291
+msgid "This is a note."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(warn):295
+msgid "This is a warning."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(impo):299
+msgid "This is important."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):306
+msgid "The &lt;body&gt; tags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):309
+msgid "We introduced a lot of new tags in the previous section -- here's what you need to know. The <c>&lt;p&gt;</c> (paragraph), <c>&lt;pre&gt;</c> (code block), <c>&lt;note&gt;</c>, <c>&lt;warn&gt;</c> (warning) and <c>&lt;impo&gt;</c> (important) tags all can contain one or more lines of text. Besides the <c>&lt;table&gt;</c>, <c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c> and <c>&lt;dl&gt;</c> elements (which we'll cover in just a bit), these are the only tags that should appear immediately inside a <c>&lt;body&gt;</c> element. Another thing -- these tags <e>should not</e> be stacked -- in other words, don't put a <c>&lt;note&gt;</c> element inside a <c>&lt;p&gt;</c> element. As you might guess, the <c>&lt;pre&gt;</c> element preserves its whitespace exactly, making it well-suited for code excerpts. You must name the <c>&lt;pre&gt;</c> tag with a <c>caption</c> attribute:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):324
+msgid "Named <pre/>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):324
+#, no-wrap
+msgid "\n&lt;pre caption=\"Output of uptime\"&gt;\n# &lt;i&gt;uptime&lt;/i&gt;\n16:50:47 up 164 days,  2:06,  5 users,  load average: 0.23, 0.20, 0.25\n&lt;/pre&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):334
+msgid "Epigraphs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):337
+msgid "Delegates from the original 13 states formed the Contented Congress. Thomas Jefferson, a Virgin, and Benjamin Franklin were two singers of the Declaration of Independence. Franklin discovered electricity by rubbing two cats backwards and declared, \"A horse divided against itself cannot stand.\" Franklin died in 1790 and is still dead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):345
+msgid "Epigraphs are sometimes used at the beginning of chapters to illustrate what is to follow. It is simply a paragraph with a <c>by</c> attribute that contains the signature."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):351
+msgid "Short epigraph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):351
+#, no-wrap
+msgid "\n&lt;p by=\"Anonymous student\"&gt;\nDelegates from the original 13 states formed the...\n&lt;/p&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):360
+msgid "&lt;path&gt;, &lt;c&gt;, &lt;b&gt;, &lt;e&gt;, &lt;sub&gt; and &lt;sup&gt;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):365
+msgid "The <c>&lt;path&gt;</c>, <c>&lt;c&gt;</c>, <c>&lt;b&gt;</c>, <c>&lt;e&gt;</c>, <c>&lt;sub&gt;</c> and <c>&lt;sup&gt;</c> elements can be used inside any child <c>&lt;body&gt;</c> tag, except for <c>&lt;pre&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):371
+msgid "The <c>&lt;path&gt;</c> element is used to mark text that refers to an <e>on-disk file</e> -- either an <e>absolute or relative path</e>, or a <e>simple filename</e>. This element is generally rendered with a mono spaced font to offset it from the standard paragraph type."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):378
+msgid "The <c>&lt;c&gt;</c> element is used to mark up a <e>command</e> or <e>user input</e>. Think of <c>&lt;c&gt;</c> as a way to alert the reader to something that they can type in that will perform some kind of action. For example, all the XML tags displayed in this document are enclosed in a <c>&lt;c&gt;</c> element because they represent something that the user could type in that is not a path. By using <c>&lt;c&gt;</c> elements, you'll help your readers quickly identify commands that they need to type in. Also, because <c>&lt;c&gt;</c> elements are already offset from regular text, <e>it is rarely necessary to surround user input with double-quotes</e>. For example, don't refer to a \"<c>&lt;c&gt;</c>\" element like I did in this sentence. Avoiding the use of unnecessary double-quotes makes a document more readable -- and adorable!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):393
+msgid "As you might have guessed, <c>&lt;b&gt;</c> is used to <b>boldface</b> some text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):398
+msgid "<c>&lt;e&gt;</c> is used to apply emphasis to a word or phrase; for example: I <e>really</e> should use semicolons more often. As you can see, this text is offset from the regular paragraph type for emphasis. This helps to give your prose more <e>punch</e>!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):405
+msgid "The <c>&lt;sub&gt;</c> and <c>&lt;sup&gt;</c> elements are used to specify <sub>subscript</sub> and <sup>superscript</sup>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):413
+msgid "Code samples and colour-coding"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):416
+msgid "To improve the readability of code samples, the following tags are allowed inside <c>&lt;pre&gt;</c> blocks:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):423
+msgid "Distinguishes user input from displayed text"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):425
+msgid "Comments relevant to the action(s) that appear after the comment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):427
+msgid "Denotes a keyword in the language used in the code sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):430
+msgid "Used for an identifier"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):433
+msgid "Used for a constant"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):436
+msgid "Used for a statement"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):439
+msgid "Used for a variable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(note):443
+msgid "Remember that all leading and trailing spaces, and line breaks in <c>&lt;pre&gt;</c> blocks will appear in the displayed html page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):448
+msgid "Sample colour-coded <c>&lt;pre&gt;</c> block:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):452
+msgid "My first ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):452
+#, no-wrap
+msgid "\n<comment># Copyright 1999-2009 <b>Gentoo Foundation</b>\n# Distributed under the terms of the GNU General Public License v2\n# $Header: $</comment>\n\n<ident>DESCRIPTION</ident>=<const>\"Exuberant ctags generates tags files for quick source navigation\"</const>\n<ident>HOMEPAGE</ident>=<const>\"http://ctags.sourceforge.net\"</const>\n<ident>SRC_URI</ident>=<const>\"mirror://sourceforge/ctags/<var>${P}</var>.tar.gz\"</const>\n\n<ident>LICENSE</ident>=<const>\"GPL-2\"</const>\n<ident>SLOT</ident>=<const>\"0\"</const>\n<ident>KEYWORDS</ident>=<const>\"~mips ~sparc ~x86\"</const>\n<ident>IUSE</ident>=<const>\"\"</const>\n\n<stmt>src_compile()</stmt> {\n    <keyword>econf</keyword> --with-posix-regex\n    <keyword>emake</keyword> || <keyword>die</keyword> <const>\"emake failed\"</const>\n}\n\n<stmt>src_install()</stmt> {\n    <keyword>make</keyword> <ident>DESTDIR</ident>=\"<var>${D}</var>\" install || <keyword>die</keyword> <const>\"install failed\"</const>\n\n    <keyword>dodoc</keyword> FAQ NEWS README\n    <keyword>dohtml</keyword> EXTENDING.html ctags.html\n}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):482
+msgid "&lt;mail&gt; and &lt;uri&gt;"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):485
+msgid "We've taken a look at the <c>&lt;mail&gt;</c> tag earlier; it's used to link some text with a particular email address, and takes the form <c>&lt;mail link=\"foo.bar@example.com\"&gt;Mr. Foo Bar&lt;/mail&gt;</c>. If you want to display the email address, you can use <c>&lt;mail&gt;foo.bar@example.com&lt;/mail&gt;</c>, this would be displayed as <mail>foo.bar@example.com</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):493
+msgid "Shorter forms make it easier to use names and emails of Gentoo developers. Both <c>&lt;mail&gt;neysx&lt;/mail&gt;</c> and <c>&lt;mail link=\"neysx\"/&gt;</c> would appear as <mail>neysx</mail>. If you want to use a Gentoo dev's email with a different content than his full name, use the second form with some content. For instance, use a dev's first name: <c>&lt;mail link=\"neysx\"&gt;Xavier&lt;/mail&gt;</c> appears as <mail link=\"neysx\">Xavier</mail>. <br/> This is particularly useful when you want to name a developer whose name contains \"funny\" characters that you can't type."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):506
+msgid "The <c>&lt;uri&gt;</c> tag is used to point to files/locations on the Internet. It has two forms -- the first can be used when you want to have the actual URI displayed in the body text, such as this link to <uri>http://forums.gentoo.org/</uri>. To create this link, I typed <c>&lt;uri&gt;http://forums.gentoo.org/&lt;/uri&gt;</c>. The alternate form is when you want to associate a URI with some other text -- for example, <uri link=\"http://forums.gentoo.org/\">the Gentoo Forums</uri>. To create <e>this</e> link, I typed <c>&lt;uri link=\"http://forums.gentoo.org/\"&gt;the Gentoo Forums&lt;/uri&gt;</c>. You don't need to write <c>http://www.gentoo.org/</c> to link to other parts of the Gentoo web site. For instance, a link to the <uri link=\"/doc/en/\">documentation main index</uri> should be simply <c>&lt;uri link=\"/doc/en/index.xml\"&gt;documentation main index&lt;/uri&gt;</c>. You can even omit <c>index.xml</c> when you link to a directory index, e.g. <c>&lt;uri link=\"/doc/en/\"&gt;documentation main index&lt;/uri&gt;</c>. Leaving the trailing slash saves an extra HTTP request."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):524
+msgid "You should not use a <c>&lt;uri&gt;</c> tag with a <c>link</c> attribute that starts with <c>mailto:</c>. In this case, use a <c>&lt;mail&gt;</c> tag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):529
+msgid "Please avoid the <uri link=\"http://en.wikipedia.org/wiki/Click_here\">click here syndrome</uri> as recommended by the <uri link=\"http://www.w3.org/QA/Tips/noClickHere\">W3C</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):538
+msgid "Figures"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):541
+msgid "Here's how to insert a figure into a document -- <c>&lt;figure link=\"mygfx.png\" short=\"my picture\" caption=\"my favorite picture of all time\"/&gt;</c>. The <c>link</c> attribute points to the actual graphic image, the <c>short</c> attribute specifies a short description (currently used for the image's HTML <c>alt</c> attribute), and a caption. Not too difficult :) We also support the standard HTML-style &lt;img src=\"foo.gif\"/&gt; tag for adding images without captions, borders, etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):554
+msgid "Tables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):557
+msgid "GuideXML supports a simplified table syntax similar to that of HTML. To start a table, use a <c>&lt;table&gt;</c> tag. Start a row with a <c>&lt;tr&gt;</c> tag. However, for inserting actual table data, we <e>don't</e> support the HTML &lt;td&gt; tag; instead, use the <c>&lt;th&gt;</c> if you are inserting a header, and <c>&lt;ti&gt;</c> if you are inserting a normal informational block. You can use a <c>&lt;th&gt;</c> anywhere you can use a <c>&lt;ti&gt;</c> -- there's no requirement that <c>&lt;th&gt;</c> elements appear only in the first row."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):568
+msgid "Besides, both table headers (<c>&lt;th&gt;</c>) and table items (<c>&lt;ti&gt;</c>) accept the <c>colspan</c> and <c>rowspan</c> attributes to span their content across rows, columns or both."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):574
+msgid "Furthermore, table cells (<c>&lt;ti&gt;</c> &amp; <c>&lt;th&gt;</c>) can be right-aligned, left-aligned or centered with the <c>align</c> attribute."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(th):581
+msgid "This title spans 4 columns"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(th):584
+msgid "This title spans 6 rows"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):585
+msgid "Item A1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):586
+msgid "Item A2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):587
+msgid "Item A3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):590
+msgid "Item B1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(th):591
+msgid "Blocky 2x2 title"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):594
+msgid "Item C1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):597
+msgid "Item D1..D3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):600
+msgid "Item E1..F1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):601
+msgid "Item E2..E3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(ti):604
+msgid "Item F2..F3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):611
+msgid "Lists"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):614
+msgid "To create ordered or unordered lists, simply use the XHTML-style <c>&lt;ol&gt;</c>, <c>&lt;ul&gt;</c> and <c>&lt;li&gt;</c> tags. Lists may only appear inside the <c>&lt;body&gt;</c> and <c>&lt;li&gt;</c> tags which means that you can have lists inside lists. Don't forget that you are writing XML and that you must close all tags including list items unlike in HTML."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):622
+msgid "Definition lists (<c>&lt;dl&gt;</c>) are also supported. Please note that neither the definition term tag (<c>&lt;dt&gt;</c>) nor the definition data tag (<c>&lt;dd&gt;</c>) accept any other block level tag such as paragraphs or admonitions. A definition list comprises:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):631
+msgid "A <b>D</b>efinition <b>L</b>ist Tag containing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):633
+msgid "Pairs of <b>D</b>efinition <b>T</b>erm Tags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):635
+msgid "and <b>D</b>efinition <b>D</b>ata Tags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):638
+msgid "The following list copied from <uri link=\"http://www.w3.org/TR/REC-html40/struct/lists.html\">w3.org</uri> shows that a definition list can contain ordered and unordered lists. It may not contain another definition list though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):649
+msgid "100 g. flour"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):650
+msgid "10 g. sugar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):651
+msgid "1 cup water"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):652
+msgid "2 eggs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):653
+msgid "salt, pepper"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):659
+msgid "Mix dry ingredients thoroughly"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):660
+msgid "Pour in wet ingredients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):661
+msgid "Mix for 10 minutes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):662
+msgid "Bake for one hour at 300 degrees"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(dd):666
+msgid "The recipe may be improved by adding raisins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):672
+msgid "Intra-document references"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):675
+msgid "GuideXML makes it really easy to reference other parts of the document using hyperlinks. You can create a link pointing to <uri link=\"#doc_chap1\">Chapter One</uri> by typing <c>&lt;uri link=\"#doc_chap1\"&gt;Chapter One&lt;/uri&gt;</c>. To point to <uri link=\"#doc_chap1_sect2\">section two of Chapter One</uri>, type <c>&lt;uri link=\"#doc_chap1_sect2\"&gt;section two of Chapter One&lt;/uri&gt;</c>. To refer to figure 3 in chapter 1, type <c>&lt;uri link=\"#doc_chap1_fig3\"&gt;figure 1.3&lt;/uri&gt;</c>. Or, to refer to <uri link=\"#doc_chap2_pre2\">code listing 2 in chapter 2</uri>, type <c>&lt;uri link=\"#doc_chap2_pre2\"&gt;code listing 2.2&lt;/uri&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):687
+msgid "However, some guides change often and using such \"counting\" can lead to broken links. In order to cope with this, you can define a name for a <c>&lt;chapter&gt;</c>, <c>&lt;section&gt;</c> or a <c>&lt;tr&gt;</c> by using the <c>id</c> attribute, and then point to that attribute, like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):694
+msgid "Using the id attribute"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):694
+#, no-wrap
+msgid "\n&lt;chapter id=\"foo\"&gt;\n&lt;title&gt;This is foo!&lt;/title&gt;\n...\n&lt;p&gt;\nMore information can be found in the &lt;uri link=\"#foo\"&gt;foo chapter&lt;/uri&gt;\n&lt;/p&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):706
+msgid "Disclaimers and obsolete documents"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):709
+msgid "A <c>disclaimer</c> attribute can be applied to guides and handbooks to display a predefined disclaimer at the top of the document. The available disclaimers are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):716
+msgid "<b>articles</b> is used for <uri link=\"/doc/en/articles/\">republished articles</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):720
+msgid "<b>draft</b> is used to indicate a document is still being worked on and should not be considered official"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):724
+msgid "<b>oldbook</b> is used on old handbooks to indicate they are not maintained anymore"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(li):728
+msgid "<b>obsolete</b> is used to mark a document as obsolete."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):731
+msgid "When marking a document as obsolete, you might want to add a link to a new version. The <c>redirect</c> attribute does just that. The user might be automatically redirected to the new page but you should not rely on that behaviour."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):738
+msgid "Disclaimer sample"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):738
+#, no-wrap
+msgid "\n&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;!DOCTYPE guide SYSTEM \"/dtd/guide.dtd\"&gt;\n&lt;!-- $Header$ --&gt;\n\n&lt;guide disclaimer=\"obsolete\" redirect=\"/doc/en/handbook/handbook-x86.xml\"&gt;\n&lt;title&gt;Gentoo x86 Installation Guide&lt;/title&gt;\n\n&lt;author title=\"Author\"&gt;\n...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):753
+msgid "FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):756
+msgid "FAQ documents need to start with a list of questions with links to their answers. Creating such a list is both time-consuming and error-prone. The list can be created automatically if you use a <c>faqindex</c> element as the first chapter of your document. This element has the same structure as a <c>chapter</c> to allow some introductory text. The structure of the document is expected to be split into chapters (at least one chapter) containing sections, each section containing one question specified in its <c>title</c> element with the answer in its <c>body</c>. The FAQ index will appear as one section per chapter and one link per question."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):768
+msgid "A quick look at a <uri link=\"/doc/en/faq.xml\">FAQ</uri> and <uri link=\"/doc/en/faq.xml?passthru=1\">its source</uri> should make the above obvious."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):779
+msgid "Handbook Format"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):781
+msgid "Guide vs Book"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):784
+msgid "For high-volume documentation, such as the <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1\">Installation Instructions</uri>, a broader format was needed. We designed a GuideXML-compatible enhancement that allows us to write modular and multi-page documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):794
+msgid "Main File"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):797
+msgid "The first change is the need for a \"master\" document. This document contains no real content, but links to the individual documentation modules. The syntax doesn't differ much from GuideXML:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):803
+msgid "Example book usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):803
+#, no-wrap
+msgid "\n&lt;?xml version='1.0' encoding='UTF-8'?&gt;\n&lt;!DOCTYPE book SYSTEM \"/dtd/book.dtd\"&gt;\n&lt;!-- $Header$ --&gt;\n\n&lt;<i>book</i>&gt;\n&lt;title&gt;Example Book Usage&lt;/title&gt;\n\n&lt;author...&gt;\n  ...\n&lt;/author&gt;\n\n&lt;abstract&gt;\n  ...\n&lt;/abstract&gt;\n\n&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt;\n&lt;!-- See http://creativecommons.org/licenses/by-sa/2.5 --&gt;\n&lt;license/&gt;\n\n&lt;version&gt;...&lt;/version&gt;\n&lt;date&gt;...&lt;/date&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):827
+msgid "So far no real differences (except for the <c>&lt;book&gt;</c> instead of <c>&lt;guide&gt;</c> tag). Instead of starting with the individual <c>&lt;chapter&gt;</c>s, you define a <c>&lt;part&gt;</c>, which is the equivalent of a separate part in a book:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):834
+msgid "Defining a part"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):834
+#, no-wrap
+msgid "\n&lt;part&gt;\n&lt;title&gt;Part One&lt;/title&gt;\n&lt;abstract&gt;\n  ...\n&lt;/abstract&gt;\n\n<comment>(Defining the several chapters)</comment>\n&lt;/part&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):845
+msgid "Each part is accompanied by a <c>&lt;title&gt;</c> and an <c>&lt;abstract&gt;</c> which gives a small introduction to the part."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):850
+msgid "Inside each part, you define the individual <c>&lt;chapter&gt;</c>s. Each chapter <e>must</e> be a separate document. As a result it is no surprise that a special tag (<c>&lt;include&gt;</c>) is added to allow including the separate document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):857
+msgid "Defining a chapter"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):857
+#, no-wrap
+msgid "\n&lt;chapter&gt;\n&lt;title&gt;Chapter One&lt;/title&gt;\n\n  &lt;include href=\"path/to/chapter-one.xml\"/&gt;\n\n&lt;/chapter&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):869
+msgid "Designing the Individual Chapters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):872
+msgid "The content of an individual chapter is structured as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):876
+msgid "Chapter Syntax"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):876
+#, no-wrap
+msgid "\n&lt;?xml version='1.0' encoding='UTF-8'?&gt;\n&lt;!DOCTYPE sections SYSTEM \"/dtd/book.dtd\"&gt;\n&lt;!-- $Header$ --&gt;\n\n&lt;!--  The content of this document is licensed under the CC-BY-SA license --&gt;\n&lt;!--  See http://creativecommons.org/licenses/by-sa/2.5 --&gt;\n\n&lt;sections&gt;\n\n&lt;abstract&gt;\n  This is a small explanation on chapter one.\n&lt;/abstract&gt;\n\n&lt;version&gt;...&lt;/version&gt;\n&lt;date&gt;...&lt;/date&gt;\n\n<comment>(Define the several &lt;section&gt; and &lt;subsection&gt;)</comment>\n\n&lt;/sections&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):898
+msgid "Inside each chapter you can define <c>&lt;section&gt;</c>s (equivalent of <c>&lt;chapter&gt;</c> in a Guide) and <c>&lt;subsection&gt;</c>s (equivalent of <c>&lt;section&gt;</c> in a Guide)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):904
+msgid "Each individual chapter should have its own date and version elements. The latest date of all chapters and master document will be displayed when a user browses through all parts of the book."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):915
+msgid "Advanced Handbook Features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):917
+msgid "Global Values"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):920
+msgid "Sometimes, the same values are repeated many times in several parts of a handbook. Global search and replace operations tend to forget some or introduce unwanted changes. Besides, it can be useful to define different values to be used in shared chapters depending on which handbook includes the chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):927
+msgid "Global values can be defined in a handbook master file and used in all included chapters."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):932
+msgid "To define global values, add a <c>&lt;values&gt;</c> element to the handbook master file. Each value is then defined in a <c>&lt;key&gt;</c> element whose <c>id</c> attribute identifies the value, i.e. it is the name of your variable. The content of the <c>&lt;key&gt;</c> is its value."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):939
+msgid "The following example defines three values in a handbook master file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):943
+msgid "Define values in a handbook"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):943
+#, no-wrap
+msgid "\n&lt;?xml version='1.0' encoding='UTF-8'?&gt;\n&lt;!DOCTYPE book SYSTEM \"/dtd/book.dtd\"&gt;\n&lt;!-- $Header$ --&gt;\n\n&lt;book&gt;\n&lt;title&gt;Example Book Usage&lt;/title&gt;\n\n<i>&lt;values&gt;\n &lt;key id=\"arch\"&gt;x86&lt;/key&gt;\n &lt;key id=\"min-cd-name\"&gt;install-x86-minimal-2007.0-r1.iso&lt;/key&gt;\n &lt;key id=\"min-cd-size\"&gt;57&lt;/key&gt;\n&lt;/values&gt;</i>\n\n&lt;author...&gt;\n  ...\n&lt;/author&gt;\n\n...\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):964
+msgid "The defined values can then be used throughout the handbook with the in-line <c>&lt;keyval id=\"key_id\"/&gt;</c> element. Specify the name of the key in its <c>id</c> attribute, e.g. &lt;keyval id=\"min-cd-name\"/&gt; would be replaced by \"install-x86-minimal-2007.0-r1.iso\" in our example."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):971
+msgid "Using defined values"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):971
+#, no-wrap
+msgid "\n&lt;p&gt;\nThe Minimal Installation CD is called &lt;c&gt;<i>&lt;keyval id=\"min-cd-name\"/&gt;</i>&lt;/c&gt;\nand takes up only <i>&lt;keyval id=\"min-cd-size\"/&gt;</i> MB of diskspace. You can use this\nInstallation CD to install Gentoo, but &lt;e&gt;only&lt;/e&gt; with a working Internet\nconnection.\n&lt;/p&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):980
+msgid "To make life easier on our translators, only use actual values, i.e. content that does not need to be translated. For instance, we defined the <c>min-cd-size</c> value to <c>57</c> and not <c>57 MB</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):989
+msgid "Conditional Elements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):992
+msgid "Chapters that are shared by several handbooks such as our <uri link=\"/doc/en/handbook/\">Installation Handbooks</uri> often have small differences depending on which handbook includes them. Instead of adding content that is irrelevant to some handbooks, authors can add a condition to the following elements: <c>&lt;section&gt;</c>, <c>&lt;subsection&gt;</c>, <c>&lt;body&gt;</c>, <c>&lt;note&gt;</c>, <c>&lt;impo&gt;</c>, <c>&lt;warn&gt;</c>, <c>&lt;pre&gt;</c>, <c>&lt;p&gt;</c>, <c>&lt;table&gt;</c>, <c>&lt;tr&gt;</c>, <c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c> and <c>&lt;li&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1004
+msgid "The condition must be an <uri link=\"http://en.wikipedia.org/wiki/XPath\">XPATH</uri> expression that will be evaluated when transforming the XML. If it evaluates to <c>true</c>, the element is processed, if not, it is ignored. The condition is specified in a <c>test</c> attribute."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1012
+msgid "The following example uses the <c>arch</c> value that is defined in each handbook master file to condition some content:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1017
+msgid "Using conditional elements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1017
+#, no-wrap
+msgid "\n&lt;body test=\"contains('AMD64 x86',func:keyval('arch'))\"&gt;\n\n&lt;p&gt;\nThis paragraph applies to both x86 and AMD64 architectures.\n&lt;/p&gt;\n\n&lt;p test=\"func:keyval('arch')='x86'\"&gt;\nThis paragraph only applies to the x86 architecture.\n&lt;/p&gt;\n\n&lt;p test=\"func:keyval('arch')='AMD64'\"&gt;\nThis paragraph only applies to the AMD64 architecture.\n&lt;/p&gt;\n\n&lt;p test=\"func:keyval('arch')='PPC'\"&gt;\nThis paragraph will never be seen!\nThe whole body is skipped because of the first condition.\n&lt;/p&gt;\n\n&lt;/body&gt;\n\n&lt;body test=\"contains('AMD64 PPC64',func:keyval('arch'))\"&gt;\n\n&lt;p&gt;\nThis paragraph applies to the AMD64, PPC64 <comment>and PPC</comment> architectures because\nthe 'AMD64 PPC64' string does contain 'PPC'.\n&lt;/p&gt;\n\n&lt;note test=\"func:keyval('arch')='AMD64' or func:keyval('arch')='PPC64'\"&gt;\nThis note only applies to the AMD64 and PPC64 architectures.\n&lt;/note&gt;\n\n&lt;/body&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1058
+msgid "Coding Style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1060
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1063
+msgid "Since all Gentoo Documentation is a joint effort and several people will most likely change existing documentation, a coding style is needed. A coding style contains two sections. The first one is regarding internal coding - how the XML-tags are placed. The second one is regarding the content - how not to confuse the reader."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1071
+msgid "Both sections are described next."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1078
+msgid "Internal Coding Style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1081
+msgid "<b>Newlines</b> must be placed immediately after <e>every</e> GuideXML-tag (both opening as closing), except for: <c>&lt;version&gt;</c>, <c>&lt;date&gt;</c>, <c>&lt;title&gt;</c>, <c>&lt;th&gt;</c>, <c>&lt;ti&gt;</c>, <c>&lt;li&gt;</c>, <c>&lt;i&gt;</c>, <c>&lt;e&gt;</c>, <c>&lt;uri&gt;</c>, <c>&lt;path&gt;</c>, <c>&lt;b&gt;</c>, <c>&lt;c&gt;</c>, <c>&lt;comment&gt;</c>, <c>&lt;mail&gt;</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1091
+msgid "<b>Blank lines</b> must be placed immediately after <e>every</e><c>&lt;body&gt;</c> (opening tag only) and before <e>every</e><c>&lt;chapter&gt;</c>, <c>&lt;p&gt;</c>, <c>&lt;table&gt;</c>, <c>&lt;author&gt;</c> (set), <c>&lt;pre&gt;</c>, <c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c>, <c>&lt;warn&gt;</c>, <c>&lt;note&gt;</c> and <c>&lt;impo&gt;</c> (opening tags only)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1100
+msgid "<b>Word-wrapping</b> must be applied at 80 characters except inside <c>&lt;pre&gt;</c>. You may only deviate from this rule when there is no other choice (for instance when a URL exceeds the maximum amount of characters). The editor must then wrap whenever the first whitespace occurs. You should try to keep the <e>rendered</e> content of <c>&lt;pre&gt;</c> elements within 80 columns to help console users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1109
+msgid "<b>Indentation</b> may not be used, except with the XML-constructs of which the parent XML-tags are <c>&lt;tr&gt;</c> (from <c>&lt;table&gt;</c>), <c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c>, <c>&lt;dl&gt;</c>, and <c>&lt;author&gt;</c>. If indentation is used, it <e>must</e> be two spaces for each indentation. That means <e>no tabs</e> and <e>not</e> more spaces. Besides, tabs are not allowed in GuideXML documents."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1118
+msgid "In case word-wrapping happens in <c>&lt;ti&gt;</c>, <c>&lt;th&gt;</c>, <c>&lt;li&gt;</c> or <c>&lt;dd&gt;</c> constructs, indentation must be used for the content."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1124
+msgid "An example for indentation is:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1128
+msgid "Indentation Example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1128
+#, no-wrap
+msgid "\n&lt;table&gt;\n&lt;tr&gt;\n  &lt;th&gt;Foo&lt;/th&gt;\n  &lt;th&gt;Bar&lt;/th&gt;\n&lt;/tr&gt;\n&lt;tr&gt;\n  &lt;ti&gt;This is an example for indentation&lt;/ti&gt;\n  &lt;ti&gt;\n    In case text cannot be shown within an 80-character wide line, you\n    must use indentation if the parent tag allows it\n  &lt;/ti&gt;\n&lt;/tr&gt;\n&lt;/table&gt;\n\n&lt;ul&gt;\n  &lt;li&gt;First option&lt;/li&gt;\n  &lt;li&gt;Second option&lt;/li&gt;\n&lt;/ul&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1149
+msgid "<b>Attributes</b> may not have spaces in between the attribute, the \"=\" mark, and the attribute value. As an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1154
+msgid "Attributes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1154
+#, no-wrap
+msgid "\n<comment>Wrong  :</comment>     &lt;pre caption = \"Attributes\"&gt;\n<comment>Correct:</comment>     &lt;pre caption=\"Attributes\"&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1162
+msgid "External Coding Style"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1165
+msgid "Inside tables (<c>&lt;table&gt;</c>) and listings (<c>&lt;ul&gt;</c>, <c>&lt;ol&gt;</c>) and <c>&lt;dl&gt;</c>, periods (\".\") should not be used unless multiple sentences are used. In that case, every sentence should end with a period (or other reading marks)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1172
+msgid "Every sentence, including those inside tables and listings, should start with a capital letter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1177
+msgid "Periods and capital letters"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1177
+#, no-wrap
+msgid "\n&lt;ul&gt;\n  &lt;li&gt;No period&lt;/li&gt;\n  &lt;li&gt;With period. Multiple sentences, remember?&lt;/li&gt;\n&lt;/ul&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1184
+msgid "Code Listings should <e>always</e> have a <c>caption</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1188
+msgid "Try to use <c>&lt;uri&gt;</c> with the <c>link</c> attribute as much as possible. In other words, the <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri> is preferred over <uri>http://forums.gentoo.org</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1194
+msgid "When you comment something inside a <c>&lt;pre&gt;</c> construct, use <c>&lt;comment&gt;</c> and parentheses or the comment marker for the language that is being used (<c>#</c> for bash scripts and many other things, <c>//</c> for C code, etc.) Also place the comment <e>before</e> the subject of the comment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre:caption):1202
+msgid "Comment example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(pre):1202
+#, no-wrap
+msgid "\n<comment>(Substitute \"john\" with your user name)</comment>\n# <i>id john</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1212
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(title):1214
+msgid "Start writing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(p):1217
+msgid "GuideXML has been specially designed to be \"lean and mean\" so that developers can spend more time writing documentation and less time learning the actual XML syntax. Hopefully, this will allow developers who aren't unusually \"doc-savvy\" to start writing quality Gentoo documentation. You might be interested in our <uri link=\"/proj/en/gdp/doc/doc-tipsntricks.xml\">Documentation Development Tips &amp; Tricks</uri>. If you'd like to help (or have any questions about GuideXML), please post a message to the <uri link=\"/main/en/lists.xml\">gentoo-doc mailing list</uri> stating what you'd like to tackle. Have fun!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//xml-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/xorg-config.xml.pot b/doc/gettext/xorg-config.xml.pot
new file mode 100644
index 0000000..9a134af
--- /dev/null
+++ b/doc/gettext/xorg-config.xml.pot
@@ -0,0 +1,584 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):6
+msgid "The X Server Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(mail:link):9
+msgid "swift"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(abstract):15
+msgid "Xorg is the X Window server which allows users to have a graphical environment at their fingertips. This HOWTO explains what Xorg is, how to install it and what the various configuration options are."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(version):25
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(date):26
+msgid "2010-10-12"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):29
+msgid "What is the X Window Server?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):31
+msgid "Graphical vs Command-Line"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):34
+msgid "The average user may be frightened at the thought of having to type in commands. Why wouldn't he be able to point and click his way through the freedom provided by Gentoo (and Linux in general)? Well, of course you are able to do this! Linux offers a wide variety of flashy user interfaces and environments which you can install on top of your existing installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):42
+msgid "This is one of the biggest surprises new users come across: a graphical user interface is nothing more than an application which runs on your system. It is <e>not</e> part of the Linux kernel or any other internals of the system. It is a powerful tool that fully enables the graphical abilities of your workstation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):49
+msgid "As standards are important, a standard for drawing and moving windows on a screen, interacting with the user through mouse, keyboard and other basic, yet important aspects has been created and named the <e>X Window System</e>, commonly abbreviated as <e>X11</e> or just <e>X</e>. It is used on Unix, Linux and Unix-like operating systems throughout the world."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):57
+msgid "The application that provides Linux users with the ability to run graphical user interfaces and that uses the X11 standard is Xorg-X11, a fork of the XFree86 project. XFree86 has decided to use a license that might not be compatible with the GPL license; the use of Xorg is therefore recommended. The official Portage tree does not provide an XFree86 package anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):68
+msgid "The X.org Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):71
+msgid "The <uri link=\"http://www.x.org\">X.org</uri> project created and maintains a freely redistributable, open-source implementation of the X11 system. It is an open source X11-based desktop infrastructure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):77
+msgid "Xorg provides an interface between your hardware and the graphical software you want to run. Besides that, Xorg is also fully network-aware, meaning you are able to run an application on one system while viewing it on a different one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):89 ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):315
+msgid "Installing Xorg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):93
+msgid "Before you can install Xorg, you need to prepare your system for it. First, we'll set up the kernel to support input devices and video cards. Then we'll prepare <path>/etc/make.conf</path> so that the right drivers and Xorg packages are built and installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):103
+msgid "Input driver support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):106
+msgid "By default, Xorg uses <c>evdev</c>, a generic input driver. You'll need to activate support for <c>evdev</c> by making a change to your kernel configuration. Read the <uri link=\"/doc/en/kernel-config.xml\">Kernel Configuration Guide</uri> if you don't know how to setup your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):113
+msgid "Enabling evdev in the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):113
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\n  Input device support ---&gt;\n  &lt;*&gt;  Event interface\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):122
+msgid "Kernel modesetting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):125
+msgid "Modern open-source video drivers rely on kernel modesetting (KMS). KMS provides an improved graphical boot with less flickering, faster user switching, a built-in framebuffer console, seamless switching from the console to Xorg, and other features. KMS conflicts with legacy framebuffer drivers, which must remain <b>disabled</b> in your kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):133
+msgid "First, prepare your kernel for KMS. You need to do this step regardless of which Xorg video driver you're using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):138
+msgid "Configuring framebuffers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):138
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\n  Graphics support ---&gt;\n    Support for frame buffer devices ---&gt;\n    <comment>(Disable all drivers, including VGA, Intel, nVidia, and ATI)</comment>\n\n    <comment>(Further down, enable basic console support. KMS uses this.)</comment>\n    Console display driver support ---&gt;\n      &lt;*&gt;  Framebuffer Console Support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):149
+msgid "Next, configure your kernel to use the proper KMS driver for your video card. Intel, nVidia, and ATI are the most common cards, so follow code listing for your card below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):155
+msgid "For Intel cards:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):159
+msgid "Intel settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):159
+#, no-wrap
+msgid "\nDevice Drivers ---&gt;\n  Graphics support ---&gt;\n    /dev/agpgart (AGP Support) ---&gt;\n    &lt;*&gt;  Intel 440LX/BX/GX, I8xx and E7x05 chipset support\n    Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---&gt;\n    &lt;*&gt;  Intel 830M, 845G, 852GM, 855GM, 865G (i915 driver)\n         i915 driver\n    [*]    Enable modesetting on intel by default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):170
+msgid "For nVidia cards:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):174
+msgid "nVidia settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):174
+#, no-wrap
+msgid "\n<comment>(Enable DRM)</comment>\nDevice Drivers ---&gt;\n  Graphics support ---&gt;\n  &lt;*&gt;  Direct Rendering Manager ---&gt;\n\n<comment>(Nouveau is currently in the Staging drivers section)</comment>\nDevice Drivers ---&gt;\n  Staging drivers ---&gt;\n  [ ]  Exclude Staging drivers from being built\n  &lt;*&gt;    Nouveau (nVidia) cards\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):187
+msgid "For newer ATI cards (<uri link=\"/doc/en/ati-faq.xml\">RadeonHD 2000 and up</uri>), you will need to emerge <c>radeon-ucode</c>. Once you have installed <c>radeon-ucode</c>, configure your kernel as shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):193
+msgid "ATI settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):193
+#, no-wrap
+msgid "\n<comment>(Setup the kernel to use the radeon-ucode firmware)</comment>\nDevice Drivers ---&gt;\n  Generic Driver Options ---&gt;\n  [*]  Include in-kernel firmware blobs in kernel binary\n  <comment># RadeonHD 2000, 3000, and 4000 series cards:</comment>\n  (radeon/R600_rlc.bin radeon/R700_rlc.bin) External firmware blobs\n  <comment># RadeonHD 5000, a.k.a Evergreen, and newer cards:</comment>\n  (radeon/CEDAR_me.bin radeon/CEDAR_pfp.bin radeon/CEDAR_rlc.bin\n   radeon/CYPRESS_me.bin radeon/CYPRESS_pfp.bin radeon/CYPRESS_rlc.bin\n   radeon/JUNIPER_me.bin radeon/JUNIPER_pfp.bin radeon/JUNIPER_rlc.bin\n   radeon/REDWOOD_me.bin radeon/REDWOOD_pfp.bin \n   radeon/REDWOOD_rlc.bin) External firmware blobs\n   (/lib/firmware/) Firmware blobs root directory\n\n<comment>(Enable Radeon KMS support)</comment>\nDevice Drivers ---&gt;\n  Graphics support ---&gt;\n  &lt;*&gt;  Direct Rendering Manager ---&gt;\n  &lt;*&gt;    ATI Radeon\n  [*]      Enable modesetting on radeon by default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):216
+msgid "Old Radeon cards (X1900 series and older) don't need the <c>radeon-ucode</c> package or any firmware configuration. Just enable the Direct Rendering Manager and ATI Radeon modesetting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):222
+msgid "Now that you're done setting up KMS, continue with preparing <path>/etc/make.conf</path> in the next section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):230
+msgid "make.conf configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):233
+msgid "Now that your kernel is prepared, you have to configure two important variables in the <path>/etc/make.conf</path> file before you can install Xorg."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):238
+msgid "The first variable is <c>VIDEO_CARDS</c>. This is used to set the video drivers that you intend to use and is usually based on the kind of video card you have. The most common settings are <c>nouveau</c> for nVidia cards or <c>radeon</c> for ATI cards. Both have actively developed, well-supported open-source drivers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):246
+msgid "You may also try the proprietary drivers from nVidia and ATI, <c>nvidia</c> and <c>fglrx</c> respectively. However, setting up the proprietary drivers is beyond the scope of this guide. Please read the <uri link=\"/doc/en/nvidia-guide.xml\">Gentoo Linux nVidia Guide</uri> and <uri link=\"/doc/en/ati-faq.xml\">Gentoo Linux ATI FAQ</uri>. If you don't know which drivers you should choose, refer to these guides for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):255
+msgid "The <c>intel</c> driver may be used for desktops or laptops with common Intel integrated graphics chipsets."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):260
+msgid "<c>VIDEO_CARDS</c> may contain more than one driver, each separated with a space."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):265
+msgid "The second variable is <c>INPUT_DEVICES</c> and is used to determine which drivers are to be built for input devices. In most cases setting it to <c>evdev</c> should work just fine. If you use alternative input devices, such as a Synaptics touchpad for a laptop, be sure to add it to <c>INPUT_DEVICES</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):273
+msgid "Now you should decide which drivers you will use and add necessary settings to the <path>/etc/make.conf</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):278
+msgid "Sample make.conf entries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):278
+#, no-wrap
+msgid "\n<comment>(For mouse, keyboard, and Synaptics touchpad support)</comment>\nINPUT_DEVICES=\"evdev synaptics\"\n<comment>(For nVidia cards)</comment>\nVIDEO_CARDS=\"nouveau\"\n<comment>(OR, for ATI Radeon cards)</comment>\nVIDEO_CARDS=\"radeon\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):287
+msgid "If the suggested settings don't work for you, you should run <c>emerge -pv xorg-drivers</c>, check all the options available and choose those which apply to your system. This example is for a system with a keyboard, mouse, Synaptics touchpad, and a Radeon video card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):294
+msgid "Displaying all the driver options available"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):294
+#, no-wrap
+msgid "\n# <i>emerge -pv xorg-drivers</i>\n\nThese are the packages that would be merged, in order:\n\nCalculating dependencies... done!\n[ebuild   R   ]  x11-base/xorg-drivers-1.8  INPUT_DEVICES=\"evdev synaptics\n-acecad -aiptek -elographics% -fpit% -joystick -keyboard -mouse -penmount -tslib\n-virtualbox -vmmouse -void -wacom\"\nVIDEO_CARDS=\"radeon -apm -ark -ast -chips -cirrus -dummy -epson -fbdev -fglrx\n(-geode) -glint -i128 (-i740) (-impact) -intel -mach64 -mga -neomagic (-newport)\n-nouveau -nv -nvidia -r128 -radeonhd -rendition -s3 -s3virge -savage\n-siliconmotion -sis -sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb)\n(-sunleo) (-suntcx) -tdfx -tga -trident -tseng -v4l -vesa -via -virtualbox\n-vmware (-voodoo) (-xgi)\" 0 kB\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):311
+msgid "After setting all the necessary variables you can install the Xorg package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):315
+#, no-wrap
+msgid "\n# <i>emerge xorg-server</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):319
+msgid "You could install the <c>xorg-x11</c> metapackage instead of the more lightweight <c>xorg-server</c>. Functionally, <c>xorg-x11</c> and <c>xorg-server</c> are the same. However, <c>xorg-x11</c> brings in many more packages that you probably don't need, such as a huge assortment of fonts in many different languages. They're not necessary for a working desktop."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):327
+msgid "When the installation is finished, you will need to re-initialise some environment variables before you continue. Just run <c>env-update</c> followed by <c>source /etc/profile</c> and you're all set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):333
+msgid "Re-initialising the environment variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):333
+#, no-wrap
+msgid "\n# <i>env-update</i>\n# <i>source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):338
+msgid "Now it's time to start the Hardware Abstraction Layer (HAL) daemon and set it to automatically start each time you boot. This is necessary to get a working X environment, otherwise your input devices won't be detected and you'll probably just get a blank screen. We'll cover HAL more in the <uri link=\"#using_hal\">next section</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):346
+msgid "Starting HAL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):346
+#, no-wrap
+msgid "\n# <i>/etc/init.d/hald start</i>\n# <i>rc-update add hald default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):356
+msgid "Configuring Xorg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):358
+msgid "Using HAL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):361
+msgid "The X server is designed to work out-of-the-box, with no need to manually edit Xorg's configuration files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):366
+msgid "You should first try <uri link=\"#using_startx\">starting X</uri> without creating <path>/etc/X11/xorg.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):371
+msgid "If Xorg won't start (if there's something wrong with the screen, or with your keyboard/mouse), then you can try fixing problems by using the right configuration files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):377
+msgid "By default, Xorg uses HAL (Hardware Abstraction Layer) to detect and configure devices such as keyboards and mice."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):382
+msgid "HAL comes with many premade device rules, also called policies. These policy files are available in <path>/usr/share/hal/fdi/policy/</path>. Just find a few that suit your needs most closely and copy them to <path>/etc/hal/fdi/policy/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(impo):389
+msgid "Do not edit the files in <path>/usr/share/hal/fdi/</path>! Just copy the ones you need, and edit them once they're placed in the proper <path>/etc</path> location."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):395
+msgid "For example, to get a basic working keyboard/mouse combination, you could copy the following files to <path>/etc/hal/fdi/policy/</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):400
+msgid "Using HAL policy files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):400
+#, no-wrap
+msgid "\n# <i>cp /usr/share/hal/fdi/policy/10osvendor/10-input-policy.fdi /etc/hal/fdi/policy</i>\n# <i>cp /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi /etc/hal/fdi/policy</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):405
+msgid "There are several other HAL policies in <path>/usr/share/hal/fdi/</path> that may interest you, such as laptop configurations, storage device handling, power management, and more. Just copy any of the policies to <path>/etc/hal/fdi/policy/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(impo):412
+msgid "Remember, <e>every</e> time you finish making changes to HAL policy files, you need to restart the HAL daemon by running <c>/etc/init.d/hald restart</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):417
+msgid "You can edit the policy files in <path>/etc/hal/fdi/policy</path> to your liking. You may want to make a few tweaks or to expose additional functionality. Let's go through an example of tweaking a HAL policy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):423
+msgid "One very convenient trick is to kill the X server entirely by pressing Ctrl-Alt-Backspace. This is useful when your X server is malfunctioning, frozen, etc. It's not as extreme as rebooting the whole machine with Ctrl-Alt-Del."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):429
+msgid "Recent X server versions disabled this key combination by default. However, you can reenable it by copying <path>10-x11-input.fdi</path> to <path>/etc/hal/fdi/policy</path> and editing it. You'll need to add just one line to the appropriate section, as shown below:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):436
+msgid "Editing 10-x11-input.fdi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):436
+#, no-wrap
+msgid "\n<comment>(Open the file in your preferred editor)</comment>\n# <i>nano -w /etc/hal/fdi/policy/10-x11-input.fdi</i>\n<comment>(Find the \"input.keys\" section)</comment>\n&lt;match key=\"info.capabilities\" contains=\"input.keys\"&gt;\n<comment>(Add the \"terminate\" merge string as shown)</comment>\n&lt;match key=\"info.capabilities\" contains=\"input.keys\"&gt;\n      &lt;merge key=\"input.x11_driver\" type=\"string\"&gt;keyboard&lt;/merge&gt;\n      <i>&lt;merge key=\"input.xkb.options\" type=\"string\"&gt;terminate:ctrl_alt_bksp&lt;/merge&gt;</i>\n      &lt;match key=\"/org/freedesktop/Hal/devices/computer:system.kernel.name\"\n             string=\"Linux\"&gt;\n        &lt;merge key=\"input.x11_driver\" type=\"string\"&gt;evdev&lt;merge&gt;\n      &lt;/match&gt;\n    &lt;/match&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):452
+msgid "Once you're done, run <c>/etc/init.d/hald restart</c> so that HAL picks up your changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):457
+msgid "There, now you have a handy way of killing an unresponsive X server. This is useful when programs have frozen your display entirely, or when configuring and tweaking your Xorg environment. Be careful when killing your desktop with this key combination -- most programs really don't like it when you end them this way, and you may lose some (or all) of what you were working on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):465
+msgid "Hopefully just working with the HAL policy files results in a working X desktop. If Xorg still won't start, or there's some other problem, then you'll need to manually configure <path>xorg.conf</path> as shown in the next section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):474
+msgid "The xorg.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(note):477
+msgid "Configuring <path>xorg.conf</path> should be seen as a \"last resort\" option. It really desirable to run without one if possible, and to do all your configuration via HAL policy files. If you still can't get a working configuration, then read on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):484
+msgid "The configuration file of Xorg is called <path>xorg.conf</path> and it resides in <path>/etc/X11</path>. Xorg provides an example configuration as <path>/etc/X11/xorg.conf.example</path> which you can use to create your own configuration. It is heavily commented, but if you are in need of more documentation regarding the syntax, don't hesitate to read the man page:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):492
+msgid "Reading the xorg.conf man page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):492
+#, no-wrap
+msgid "\n$ <i>man 5 xorg.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):499
+msgid "Automatic Generation of xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):502
+msgid "Xorg itself is able to guess most parameters for you. In most cases, you will only have to change some lines to get the resolution you want up and running. If you are interested in more in-depth tweaking, be sure to check the resources at the end of this chapter. But first, let us generate a (hopefully working) Xorg configuration file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):510
+msgid "Generating an xorg.conf file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):510
+#, no-wrap
+msgid "\n# <i>Xorg -configure</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):514
+msgid "Be sure to read the last lines printed on your screen when Xorg has finished probing your hardware. If it tells you it failed at some point, you're forced to manually write an <path>xorg.conf</path> file. Assuming that it didn't fail, it will have told you that it has written <path>/root/xorg.conf.new</path> ready for you to test. So let's test. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):522
+msgid "Testing the xorg.conf.new file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):522
+#, no-wrap
+msgid "\n# <i>X -retro -config /root/xorg.conf.new</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):526
+msgid "If all goes well, you should see a simple black and white pattern. Verify if your mouse works correctly and if the resolution is good. You might not be able to deduce the exact resolution, but you should be able to see if it's too low. You can exit any time by pressing Ctrl-Alt-Backspace."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):536 ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):545
+msgid "Copying over xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):539
+msgid "Let us copy over the <path>xorg.conf.new</path> to <path>/etc/X11/xorg.conf</path> now, so we won't have to continuously run <c>X -config</c> -- typing just <c>startx</c> is easier. :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):545
+#, no-wrap
+msgid "\n# <i>cp /root/xorg.conf.new /etc/X11/xorg.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):552
+msgid "Using startx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):555
+msgid "Now try <c>startx</c> to start up your X server. <c>startx</c> is a script that executes an <e>X session</e>, that is, it starts the X server and some graphical applications on top of it. It decides which applications to run using the following logic:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(li):563
+msgid "If a file named <path>.xinitrc</path> exists in the home directory, it will execute the commands listed there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(li):567
+msgid "Otherwise, it will read the value of the XSESSION variable and will execute one of the sessions available in <path>/etc/X11/Sessions/</path> accordingly. You can set the value of XSESSION in <path>/etc/env.d/90xsession</path> to make it a default for all the users on the system. For example, as root, run <c>echo XSESSION=\"Xfce4\" &gt; /etc/env.d/90xsession</c>. This will create the <path>90xsession</path> file and set the default X session to <uri link=\"/doc/en/xfce-config.xml\">Xfce</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):579
+msgid "Starting X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):579
+#, no-wrap
+msgid "\n$ <i>startx</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):583
+msgid "You can kill the X session by using the Ctrl-Alt-Backspace key combination. This will, however, make X exit disgracefully -- something that you might not always want."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):589
+msgid "If you haven't yet installed a window manager, all you'll see is a black screen. Since this can also be a sign that something's wrong, you may want to emerge <c>twm</c> and <c>xterm</c><e>only to test X</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):595
+msgid "Once those two programs are installed, run <c>startx</c> again. A few xterm windows should appear, making it easier to verify that X is working correctly. Once you're satisfied with the results, run <c>emerge --unmerge twm xterm</c> as root to get rid of the testing packages. You won't need them once you've setup a proper desktop environment."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):608
+msgid "Tweaking X settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):610
+msgid "Setting your Resolution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):613
+msgid "If you feel that the screen resolution is wrong, you will need to check two sections in your <path>xorg.conf</path> configuration. First of all, you have the <e>Screen</e> section which lists the resolutions, if any that your X server will run at. By default, this section might not list any resolutions at all. If this is the case, Xorg will estimate the resolutions based on the information in the second section, <e>Monitor</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):622
+msgid "What happens is that Xorg checks the settings of <c>HorizSync</c> and <c>VertRefresh</c> in the <e>Monitor</e> section to compute valid resolutions. For now, leave these settings as-is. Only when the changes to the <e>Screen</e> section (which we will describe in a minute) don't work, then you will need to look up the specs for your monitor and fill in the correct values."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(warn):630
+msgid "Do <b>not</b> \"just\" change the values of these two monitor related variables without consulting the technical specifications of your monitor. Setting incorrect values lead to out-of-sync errors at best and smoked up screens at worst."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):637
+msgid "Now let us change the resolution. In the next example from <path>/etc/X11/xorg.conf</path> we add the <c>PreferredMode</c> line so that our X server starts at 1440x900 by default. Don't mind the given strings -- they are examples and will most likely differ from the settings on your system. However, the <c>Option</c> in the <c>Device</c> section must match the name of your monitor (<c>DVI-0</c>), which can be obtained by running <c>xrandr</c>. You'll need to <c>emerge xrandr</c> just long enough to get this information. The argument after the monitor name (in the <c>Device</c> section) must match the <c>Identifier</c> in the <c>Monitor</c> section."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):649
+msgid "Changing the Monitor section in /etc/X11/xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):649
+#, no-wrap
+msgid "\nSection \"Device\"\n  Identifier  \"RadeonHD 4550\"\n  Option      \"Monitor-DVI-0\" \"DVI screen\"\nEndSection\nSection \"Monitor\"\n  Identifier  \"DVI screen\"\n  Option      \"PreferredMode\" \"1440x900\"\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):660
+msgid "Run X (<c>startx</c>) to discover it uses the resolution you want."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):667
+msgid "Multiple monitors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):670
+msgid "You can configure more than one monitor in <path>/etc/X11/xorg.conf</path>. All you have to do is give each monitor an identifer, then list its physical position, such as \"RightOf\" or \"Above\" another monitor. The following example shows how to configure a DVI and a VGA monitor, with the VGA monitor as the right-hand screen:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):678
+msgid "Configuring multiple monitors in xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):678
+#, no-wrap
+msgid "\nSection \"Device\"\n  Identifier \"RadeonHD 4550\"\n  Option     \"Monitor-DVI-0\" \"DVI screen\"\n  Option     \"Monitor-VGA-0\" \"VGA screen\"\nEndSection\n\nSection \"Monitor\"\n  Identifier \"DVI screen\"\nEndSection\n\nSection \"Monitor\"\n  Identifier \"VGA screen\"\n  Option     \"RightOf\" \"DVI screen\"\nEndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):698
+msgid "Configuring your keyboard"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):701
+msgid "To setup X to use an international keyboard, you can copy the content of <path>/usr/share/doc/hal-*/*/use-estonian-layout.fdi.bz2</path> to <path>/etc/hal/fdi/policy/10-xinput-configuration.fdi</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre:caption):707
+msgid "Using an existing config file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(pre):707
+#, no-wrap
+msgid "\n# <i>bzcat /usr/share/doc/hal-*/*/use-estonian-layout.fdi.bz2 &gt; /etc/hal/fdi/policy/10-xinput-configuration.fdi</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):711
+msgid "Now you can just edit <path>10-xinput-configuration.fdi</path> and change the Estonian keyboard layout (<c>ee</c>) to your own, such as Great Britain (<b>gb</b>) or Polish (<b>pl</b>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):717
+msgid "When you're finished, run <c>/etc/init.d/hald restart</c> as root to make sure that HAL picks up your configuration file changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):725
+msgid "Finishing up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):728
+msgid "Run <c>startx</c> and be happy about the result. Congratulations, you now (hopefully) have a working Xorg on your system. The next step is to install a useful window manager or desktop environment such as KDE, GNOME, or Xfce, but that's not part of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):740
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):742
+msgid "Creating and Tweaking xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):745
+msgid "First of all, <c>man xorg.conf</c> and <c>man evdev</c> provide quick yet complete references about the syntax used by these configuration files. Be sure to have them open on a terminal near you when you edit your configuration files!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):752
+msgid "Also, be sure to look at <path>/etc/X11/xorg.conf.example</path>; you may wish to copy this and use it as a foundation for writing your own <path>xorg.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):758
+msgid "You may find the X.org <uri link=\"http://www.x.org/wiki/FAQ\">FAQ</uri> provided on their website, in addition to their other documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):763
+msgid "There are also many online resources on editing <path>xorg.conf</path>. We only list few of them here, be sure to <uri link=\"http://www.google.com\">Google</uri> for more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(title):772
+msgid "Other resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):775
+msgid "More information about installing and configuring various graphical desktop environments and applications can be found in the <uri link=\"/doc/en/?catid=desktop\">Gentoo Desktop Documentation Resources</uri> section of our documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(p):782
+msgid "If you're upgrading to <c>xorg-server</c> 1.8 from an earlier version, then be sure to read the <uri link=\"/proj/en/desktop/x/x11/xorg-server-1.8-upgrade-guide.xml\">migration guide</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//xorg-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
+
diff --git a/doc/gettext/zsh.xml.pot b/doc/gettext/zsh.xml.pot
new file mode 100644
index 0000000..29f4b56
--- /dev/null
+++ b/doc/gettext/zsh.xml.pot
@@ -0,0 +1,515 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(guide:link):5
+msgid "/doc/en/zsh.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):6
+msgid "zsh Configuration and Installation Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(author:title):8 ../../gentoo/xml/htdocs/doc/en//zsh.xml(author:title):11
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail:link):9
+msgid "hekonsek@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail):9
+msgid "Henryk Konsek"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail:link):12
+msgid "morritt.andrew@gmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail):12
+msgid "Andrew Morritt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(author:title):14 ../../gentoo/xml/htdocs/doc/en//zsh.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail:link):15
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail):15
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail:link):18
+msgid "welp@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(mail):18
+msgid "Peter Weller"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(abstract):21
+msgid "This guide shows how to install and configure zsh quickly. After reading this document you will be able use many zsh features such as advanced tab-completion, command correction and prompt management."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(version):31
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(date):32
+msgid "2006-10-18"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):35
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):37
+msgid "Installing zsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):40
+msgid "To install <c>zsh</c> under Gentoo, we need to emerge the <c>app-shells/zsh</c> (zsh itself) and <c>app-shells/zsh-completion</c> (zsh completion scripts) packages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):46
+msgid "Emerging zsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):46
+#, no-wrap
+msgid "\n# <i>emerge zsh zsh-completion</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):53
+msgid "Entering zsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):56
+msgid "When you start <c>zsh</c> for the first time, you get the following message. You can skip this menu as we will create an init file later in this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):61
+msgid "Skipping the initial config"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):61
+#, no-wrap
+msgid "\n$ <i>zsh</i>\nThis is the Z Shell configuration function for new users, zsh-newuser-install.\nYou are seeing this message because you have no zsh startup files\n(the files .zshenv, .zprofile, .zshrc, .zlogin in the directory\n~).  This function can help you with a few settings that should\nmake your use of the shell easier.\n\nYou can:\n\n(q)  Quit and do nothing.  The function will be run again next time.\n\n(0)  Exit, creating the file ~/.zshrc containing just a comment.\n     That will prevent this function being run again.\n\n(1)  Continue to the main menu.\n\n--- Type one of the keys in parentheses --- <i>q</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):86
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):88
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):91
+msgid "To start zsh for a single session, run <c>zsh</c>. For a more permanent solution, please refer to the chapter on <uri link=\"#savingsettings\">Saving settings</uri>. After the installation, <c>zsh</c> seems to be very simple and rather limited in the area of functionality. To change this, several configuration changes need to be performed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):102
+msgid "Advanced Tab-completion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):105
+msgid "To enable the famous <c>zsh</c> tab-completion system, you need to run the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):110
+msgid "Enabling completion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):110
+#, no-wrap
+msgid "\n% <i>autoload -U compinit</i>\n% <i>compinit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):115
+msgid "Default completion style is quite plain and ugly. If you want to improve its appearance, enter the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):120
+msgid "Completion style improvements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):120
+#, no-wrap
+msgid "\n% <i>zstyle ':completion:*:descriptions' format '%U%B%d%b%u'</i>\n% <i>zstyle ':completion:*:warnings' format '%BSorry, no matches for: %d%b'</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):128
+msgid "Command correction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):131
+msgid "It is also a good idea to enable the auto-correction of the commands typed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):135
+msgid "Enabling correction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):135
+#, no-wrap
+msgid "\n% <i>setopt correctall</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):142
+msgid "Prompts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):145
+msgid "The prompt may seem quite boring however, but we can fix it easily in several steps. First, we need to initialize advanced prompt support:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):150
+msgid "Enabling advanced prompts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):150
+#, no-wrap
+msgid "\n% <i>autoload -U promptinit</i>\n% <i>promptinit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):155
+msgid "Available prompts samples may be printed via the <c>prompt -p</c> command. Now we can activate our favorite one:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):160
+msgid "Choosing a sample prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):160
+#, no-wrap
+msgid "\n<comment>(Replace gentoo with the prompt of your choice)</comment>\n% <i>prompt gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(note):165
+msgid "If you're playing around with the different prompts, and you don't want to see a sample of every one, you can use <c>prompt -l</c> to list the prompts available."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):171
+msgid "Another option is to create your own prompt. To do this you will need to set the PS1 environment variable."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):176
+msgid "A simple custom prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):176
+#, no-wrap
+msgid "\n% <i>export PS1=\"[Test Prompt] &gt; \"</i>\n[Test Prompt] &gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):181
+msgid "While it is good to be able to create a custom text prompt, zsh also provides many escape sequences that allow system information to be inserted into the prompt. Some of the escape sequences available are:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(th):189
+msgid "Sequence"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(th):190
+msgid "Printed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):193
+msgid "%T"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):194
+msgid "System time (HH:MM)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):197
+msgid "%*"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):198
+msgid "System time (HH:MM:SS)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):201
+msgid "%D"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):202
+msgid "System date (YY-MM-DD)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):205
+msgid "%n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):206
+msgid "Your username"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):209
+msgid "%B - %b"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):210
+msgid "Begin - end bold print"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):213
+msgid "%U - %u"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):214
+msgid "Begin - end underlining"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):217
+msgid "%d"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):218
+msgid "Your current working directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):221
+msgid "%~"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):222
+msgid "Your current working directory, relative to ~"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):225
+msgid "%M"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):226
+msgid "The computer's hostname"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):229
+msgid "%m"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):230
+msgid "The computer's hostname (truncated before the first period)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):233
+msgid "%l"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(ti):234
+msgid "Your current tty"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):238
+msgid "These escape sequences may simply be inserted into the environment variable, PS1, and zsh will parse them automatically."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):243
+msgid "A more complex prompt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):243
+#, no-wrap
+msgid "\n% <i>export PS1=\"[%* - %D] %d %% \"</i>\n[08:44:23 - 06-02-18] /home/username %\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):251
+msgid "History"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):254
+msgid "Unfortunately, the default zsh configuration in Gentoo does not include command history support. As working with a shell without history is very frustrating, we should enter the following commands:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):260
+msgid "Basic history configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):260
+#, no-wrap
+msgid "\n% <i>export HISTSIZE=2000</i>\n% <i>export HISTFILE=\"$HOME/.history\"</i>\n\n<comment>(History won't be saved without the following command)</comment>\n% <i>export SAVEHIST=$HISTSIZE</i>\n"
+msgstr ""
+
+#. does not work
+#. <p>
+#. It is very comfortable to search commands in history using the up/down arrow
+#. keys, especially after typing the few first letters of the desired command.
+#. </p>
+#. 
+#. <p>
+#. To enable this feature, enter the following commands:
+#. </p>
+#. 
+#. <pre caption="Setting context searching">
+#. % <i>bindkey `tput kcuu1` history-beginning-search-backward >/dev/null 2>&amp;1</i>
+#. % <i>bindkey `tput kcud1` history-beginning-search-forward >/dev/null 2>&amp;1 </i>
+#. </pre>
+#. 
+#. <p>
+#. To try the above feature, try the following commands:
+#. </p>
+#. 
+#. TODO: use commands that *are* in the history, i.e. commands from above samples
+#. 
+#. <pre caption="History searching based on the first letters of the commands">
+#. <comment>(Do not press Enter after typing)</comment>
+#. % <i>vim /etc/</i>
+#. <comment>(Now press up arrow key)</comment>
+#. % <i>vim /etc/fstab</i>
+#. <comment>(Press up arrow key once again)</comment>
+#. % <i>vim /etc/X11/xorg.conf</i>
+#. </pre>
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):299
+msgid "To prevent history from recording duplicated entries (such as <c>ls -l</c> entered many times during single shell session), you can set the <c>hist_ignore_all_dups</c> option:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):305
+msgid "Setting ignoring of duplicates"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):305
+#, no-wrap
+msgid "\n% <i>setopt hist_ignore_all_dups</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):309
+msgid "A useful trick to prevent particular entries from being recorded into a history by preceding them with at least one space."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):314
+msgid "Preventing particular entry from being recorded"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):314
+#, no-wrap
+msgid "\n% <i>setopt hist_ignore_space</i>\n\n<comment>(This command won't be recorded. Note the extra space before it.)</comment>\n% <i> cat /proc/cpuinfo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):324
+msgid "Miscellaneous settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):327
+msgid "You can set the <c>autocd</c> option if you want to avoid tedious typing of <c>cd</c> command while changing current directory (for example <c>/etc</c> instead of <c>cd /etc</c>)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):333
+msgid "Setting autocd option"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):333
+#, no-wrap
+msgid "\n% <i>setopt autocd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):337
+msgid "If standard bash-like globbing does not satisfy you, <c>extendedglob</c> option may be set to enable extended globbing (one similar to regular expressions)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):343
+msgid "Setting extended globbing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):343
+#, no-wrap
+msgid "\n% <i>setopt extendedglob</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):347
+msgid "When option above is set, you are able to use extended globbing queries such as <c>cp ^*.(tar|bz2|gz)</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):357
+msgid "Saving settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):359
+msgid "Saving zsh settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):362
+msgid "Once we have customized <c>zsh</c> the way we like it, it is a good idea to save these options as the <c>zsh</c> defaults for the system. One possible way to achieve this is to write our settings in the <path>/etc/zsh/zshrc</path> script. Alternatively, we could make them the defaults for our account only be editing <path>~/.zshrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):370
+msgid "An example zshrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):370
+#, no-wrap
+msgid "\n#!/bin/zsh\n\n# completion\nautoload -U compinit\ncompinit\n\n# correction\nsetopt correctall\n\n# prompt\nautoload -U promptinit\npromptinit\nprompt gentoo\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):391
+msgid "Making zsh default shell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):393
+msgid "Option for users with root privileges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):396
+msgid "We can change shell for given user with <c>usermod</c> command."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):400
+msgid "Switching to zsh permanently using usermod"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):400
+#, no-wrap
+msgid "\n# <i>usermod -s /bin/zsh userlogin</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(title):407
+msgid "Alternative for non-root users"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):410
+msgid "If your system administrator (despite gentle requests, that is) refuses to set the shell to zsh for you, you can set <c>bash</c> to execute <c>zsh</c> on startup, all you need to do is make a slight modification to your <path>~/.bashrc</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):417
+msgid "Sample ~/.bashrc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):417
+#, no-wrap
+msgid "\n<comment>(Add the following to your ~/.bashrc)</comment>\nexec zsh\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(p):422
+msgid "Another method of changing shells is to use the <c>chsh</c> command (a utility used to change a user's login shell). A normal user may only change the login shell for his own account. As root, you can change the login shell of any user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre:caption):428
+msgid "Switching to zsh permanently using chsh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(pre):428
+#, no-wrap
+msgid "\n<comment>(Replace \"username\" with your own username)</comment>\n$ <i>chsh -s /bin/zsh username</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//zsh.xml(None):0
+msgid "translator-credits"
+msgstr ""
+