From 94c4538fb6bb2abbb04fab29a95666b30862093f Mon Sep 17 00:00:00 2001 From: str4d <str4d@mail.i2p> Date: Sat, 26 Oct 2013 22:14:49 +0000 Subject: [PATCH] Updated translations --- .../translations/de/LC_MESSAGES/priority.po | 170 +- i2p2www/translations/fr/LC_MESSAGES/about.po | 439 +- i2p2www/translations/fr/LC_MESSAGES/blog.po | 76 +- i2p2www/translations/fr/LC_MESSAGES/docs.po | 34 +- .../translations/pt/LC_MESSAGES/priority.po | 56 +- .../translations/ru_RU/LC_MESSAGES/about.po | 2512 ++++++++++ .../translations/ru_RU/LC_MESSAGES/blog.po | 137 +- .../ru_RU/LC_MESSAGES/comparison.po | 874 ++++ .../ru_RU/LC_MESSAGES/get-involved.po | 4129 +++++++++++++++++ .../ru_RU/LC_MESSAGES/priority.po | 7 +- .../ru_RU/LC_MESSAGES/research.po | 141 + .../zh_CN/LC_MESSAGES/priority.po | 15 +- 12 files changed, 8371 insertions(+), 219 deletions(-) create mode 100644 i2p2www/translations/ru_RU/LC_MESSAGES/about.po create mode 100644 i2p2www/translations/ru_RU/LC_MESSAGES/comparison.po create mode 100644 i2p2www/translations/ru_RU/LC_MESSAGES/get-involved.po create mode 100644 i2p2www/translations/ru_RU/LC_MESSAGES/research.po diff --git a/i2p2www/translations/de/LC_MESSAGES/priority.po b/i2p2www/translations/de/LC_MESSAGES/priority.po index 5609367a3..39035e4f5 100644 --- a/i2p2www/translations/de/LC_MESSAGES/priority.po +++ b/i2p2www/translations/de/LC_MESSAGES/priority.po @@ -6,6 +6,7 @@ # amiga4000 <amiga4000@mail.i2p>, 2008 # D.A. Loader, 2013 # SteinQuadrat, 2013 +# Ashoka <martin2p@posteo.de>, 2013 # nextloop <ga25day@mytum.de>, 2013 # zeroflag <zeroflag@i2pmail.org>, 2013 msgid "" @@ -13,8 +14,8 @@ msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" "POT-Creation-Date: 2013-09-30 21:40+0000\n" -"PO-Revision-Date: 2013-09-30 21:44+0000\n" -"Last-Translator: str4d <str4d@i2pmail.org>\n" +"PO-Revision-Date: 2013-10-16 09:33+0000\n" +"Last-Translator: Ashoka <martin2p@posteo.de>\n" "Language-Team: German " "(http://www.transifex.com/projects/p/I2P/language/de/)\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" @@ -44,7 +45,7 @@ msgstr "I2P Blog als ATOM-Feed" #: i2p2www/pages/blog/index.html:17 #, python-format msgid "Posted %(date)s by %(author)s" -msgstr "" +msgstr "verfasst %(date)s von %(author)s" #: i2p2www/pages/blog/latest.html:5 msgid "More blog posts…" @@ -52,11 +53,11 @@ msgstr "mehr Blogartikel…" #: i2p2www/pages/blog/post.html:6 msgid "Posted:" -msgstr "" +msgstr "geschrieben:" #: i2p2www/pages/blog/post.html:7 msgid "Author:" -msgstr "" +msgstr "Autor:" #: i2p2www/pages/downloads/debian.html:4 msgid "Debian I2P Packages" @@ -91,12 +92,18 @@ msgid "" "with these packages on <a href=\"http://%(trac)s\">Trac</a> at\n" "<a href=\"http://%(trac)s\">http://%(trac)s</a>." msgstr "" +"Die I2P Pakete arbeiten <em>möglicherweise</em> auf Systemen, welche oben" +" nicht aufgeführt sind. Bitte meldet jedes Problem mit diesen Packeten " +"auf <a href=\"http://%(trac)s\">Trac</a> aufâŽ\n" +"<a href=\"http://%(trac)s\">http://%(trac)s</a>." #: i2p2www/pages/downloads/debian.html:23 msgid "" "Option 1: <a href=\"#ubuntu\">Recent versions</a> of Ubuntu and its " "derivatives (<em>Try this if you're not using Debian)</em>" msgstr "" +"Option 1: <a href=\"#ubuntu\">Neuste Versionen</a> von Ubuntu und dessen " +"Derivate (<em>Versuche dies, wenn du kein Debian benutzt)</em>." #: i2p2www/pages/downloads/debian.html:24 msgid "Option 2: <a href=\"#debian\">Debian</a> (including Debian-derivatives)" @@ -107,6 +114,8 @@ msgid "" "Option 3: <a href=\"#nonlinux\">Non-Linux</a> (and possibly Non-x86 " "architectures)" msgstr "" +"Option 3: <a href=\"#nonlinux\">Nicht-Linux</a> (und möglicherweise " +"Nicht-x86 Prozessor-Architekturen)" #: i2p2www/pages/downloads/debian.html:28 msgid "" @@ -116,7 +125,7 @@ msgstr "" #: i2p2www/pages/downloads/debian.html:29 msgid "Adding the PPA via the command line and installing I2P" -msgstr "" +msgstr "Die PPA per Terminal hinzufügen und I2p installieren" #: i2p2www/pages/downloads/debian.html:32 msgid "Open a terminal and enter:" @@ -128,10 +137,17 @@ msgid "" "gpg key that the repository has been signed with. The GPG key ensures\n" "that the packages have not been tampered with since being built." msgstr "" +"Mit diesem Befehl wird die PPA sowie der dazugehörige GPG-Schlüssel mit " +"dem die Paketquelle signiert wurde zur Sourceliste hinzugefügt.\n" +"Der GPG-Schlüssel ist notwendig, um sicher zu stellen, dass die " +"heruntergeladenen Pakete echte sind und nicht nachträglich manipuliert " +"wurden." #: i2p2www/pages/downloads/debian.html:41 msgid "Notify your package manager of the new PPA by entering:" msgstr "" +"Informiere deinen Paketmanager über die neue PPA, indem du folgendes " +"eingibst: " #: i2p2www/pages/downloads/debian.html:43 msgid "" @@ -139,6 +155,9 @@ msgid "" "repository that is enabled on your system, including the I2P PPA that\n" "was added with the earlier command." msgstr "" +"Dieser Befehl fragt jede auf deinem System eingeschaltet Paketquelle nach" +" der neuesten Softwareliste ab. Inklusive der I2P PPA, welche mit dem " +"vorherigen Befehl hinzugefügt wurde. " #: i2p2www/pages/downloads/debian.html:49 #: i2p2www/pages/downloads/debian.html:112 @@ -148,19 +167,23 @@ msgstr "Sie/Du bist nun bereit I2P zu installieren!" #: i2p2www/pages/downloads/debian.html:53 msgid "Adding the PPA Using Synaptic" -msgstr "" +msgstr "Die PPA über Synaptic hinzufügen" #: i2p2www/pages/downloads/debian.html:56 msgid "" "Open Synaptic (System -> Administration -> Synaptic Package " "Manager)." msgstr "" +"Öffne Synaptic (System -> Administration -> Synaptic Package " +"Manager)." #: i2p2www/pages/downloads/debian.html:61 msgid "" "Once Synaptic opens, select <em>Repositories</em> from the " "<em>Settings</em> menu." msgstr "" +"Sobald sich Synaptic öffnet, wähle <em>Paketquellen</em> von dem " +"<em>Einstellungen</em> Menü." #: i2p2www/pages/downloads/debian.html:66 msgid "" @@ -169,6 +192,10 @@ msgid "" "<em>Add Source</em>. Click the <em>Close</em> button then " "<em>Reload</em>." msgstr "" +"Klicke den <em>Andere Quellen</em> tab und klicke <em>Hinzufügen</em>. " +"Füge den Code <code>ppa:i2p-maintainers/i2p</code> in das APT-Linien-Feld" +" ein und klicke <em>Quelle hinzufügen</em>. Klicke den " +"<em>Schliessen</em> Button und dann <em>Reload</em>." #: i2p2www/pages/downloads/debian.html:71 msgid "" @@ -178,6 +205,12 @@ msgid "" "so you may see a <em>Mark additional required changes?</em> popup. If so," " click <em>Mark</em> then <em>Apply</em>." msgstr "" +"In der \"Schnell Filter Box\", schreibst du <code>i2p</code> und drückst " +"Enter. Wenn <code>i2p</code> in der Ergebnisliste wiedergegeben wird, " +"rechtsklicke <code>i2p</code> und wähle <em>markiere für " +"Installation</em>. Anschliessend wirst du wahrscheinlich <em>markiere " +"zusätzliche benötigte Änderungen?</em> in einem Popup sehen. Ist dies der" +" Fall, klicke <em>markieren</em> dann <em>Anwenden</em>." #: i2p2www/pages/downloads/debian.html:77 msgid "" @@ -185,6 +218,9 @@ msgid "" "part of <a href=\"#Post-install_work\">starting I2P</a> and configuring " "it for your system." msgstr "" +"Nach dem der Installationsprozess abgeschlossen ist, kannst du zu dem " +"nächsten Teil von <a href=\"#Post-install_work\">starting I2P</a> " +"wechseln und es für dein System konfigurieren." #: i2p2www/pages/downloads/debian.html:82 msgid "Instructions for Debian Lenny and newer" @@ -205,6 +241,8 @@ msgstr "" #: i2p2www/pages/downloads/debian.html:92 msgid "Add the GPG key that signs the repository with the following command:" msgstr "" +"Füge den GPG Schlüssel, für das Signieren der Paketquelle mit folgendem " +"Befehl hinzu:" #: i2p2www/pages/downloads/debian.html:94 msgid "You'll have output like the following if the command was successful:" @@ -217,6 +255,8 @@ msgstr "" #: i2p2www/pages/downloads/debian.html:103 msgid "Notify your package manager of the new PPA by entering" msgstr "" +"Informiere deinen Paketmanager über die neue PPA, indem du folgendes " +"eingibst: " #: i2p2www/pages/downloads/debian.html:105 msgid "" @@ -224,6 +264,9 @@ msgid "" "repository enabled on your system, including the I2P PPA added in step\n" "1." msgstr "" +"Dieser Befehl fragt jede auf deinem System eingeschaltet Paketquelle nach" +" der neuesten Softwareliste ab. Inklusive der I2P PPA, welche in der 1. " +"Etappe hinzugefügt wurde. " #: i2p2www/pages/downloads/debian.html:116 #: i2p2www/pages/downloads/debian.html:147 @@ -235,7 +278,7 @@ msgstr "" #: i2p2www/pages/downloads/debian.html:120 msgid "Instructions for Non-Linux / Non-x86" -msgstr "" +msgstr "Einführung für \"Nicht-Linux\" und \"Nicht-x86\" basierende Systeme" #: i2p2www/pages/downloads/debian.html:122 msgid "" @@ -270,13 +313,15 @@ msgstr "" #: i2p2www/pages/downloads/debian.html:151 #: i2p2www/pages/downloads/list.html:166 msgid "Post-install work" -msgstr "" +msgstr "Arbeit nach der Installation" #: i2p2www/pages/downloads/debian.html:154 msgid "" "Using these I2P packages the I2P router can be started in the following\n" "three ways:" msgstr "" +"Unter Benutzung dieser I2P Pakete kann der I2P Router mit 3 verschiedenen" +" Möglichkeiten gestartet werden:" #: i2p2www/pages/downloads/debian.html:160 msgid "" @@ -372,7 +417,7 @@ msgstr "saubere Installationen" #: i2p2www/pages/downloads/list.html:76 i2p2www/pages/downloads/list.html:135 #: i2p2www/pages/downloads/list.html:264 msgid "select alternate link" -msgstr "" +msgstr "wähle alternativen Link" #: i2p2www/pages/downloads/list.html:39 msgid "Download that file and run it." @@ -422,7 +467,7 @@ msgstr "" #: i2p2www/pages/downloads/list.html:102 msgid "Packages for Debian & Ubuntu are available." -msgstr "" +msgstr "Pakete sind für Debian und Ubuntu verfügbar." #: i2p2www/pages/downloads/list.html:116 #, python-format @@ -463,6 +508,8 @@ msgid "" "The files are signed by zzz,\n" "<a href=\"%(signingkey)s\">whose key is here</a>." msgstr "" +"Diese Dateien wurden durch zzz signiert, <a " +"href=\"%(signingkey)s\">dessen Schlüssel hier ist</a>." #: i2p2www/pages/downloads/list.html:162 msgid "" @@ -470,6 +517,9 @@ msgid "" "href=\"https://launchpad.net/i2p/trunk\">Launchpad</a> and <a " "href=\"http://code.google.com/p/i2p/\">Google Code</a>." msgstr "" +"I2p kann auch von unseren Projektseiten heruntergeladen werden, diese " +"sind <a href=\"https://launchpad.net/i2p/trunk\">Launchpad</a> und <a " +"href=\"http://code.google.com/p/i2p/\">Google Code</a>." #: i2p2www/pages/downloads/list.html:168 msgid "" @@ -479,6 +529,9 @@ msgid "" "href=\"http://localhost:7657/index.jsp\">router console</a>,\n" "which has further instructions." msgstr "" +"Nach der Installation unter Windows einfach den \"Start I2P\" Button " +"drücken, wodurch die <a href=\"http://localhost:7657/index.jsp\">Router " +"Konsole</a> mit weiteren Anleitungen erscheint." #: i2p2www/pages/downloads/list.html:174 msgid "" @@ -518,11 +571,11 @@ msgstr "" #: i2p2www/pages/downloads/list.html:203 msgid "Updates from earlier releases:" -msgstr "" +msgstr "Updates von früheren Versionen:" #: i2p2www/pages/downloads/list.html:205 msgid "Both automatic and manual upgrades are available for the release." -msgstr "" +msgstr "Automatische und manuelle Updates sind für die Veröffentlichung verfügbar." #: i2p2www/pages/downloads/list.html:210 msgid "Automatic updates" @@ -535,6 +588,10 @@ msgid "" " router console\n" "when it appears." msgstr "" +"Wenn du I2P 0.7.5 oder eine spätere Version verwendest, sollte dein I2P-" +"Router die neue Version selbständig finden. Um zur neuen Version " +"aufzusteigen, klicke einfach den 'Download Update' Button in der Router-" +"Konsole sobald dieser erscheint." #: i2p2www/pages/downloads/list.html:218 msgid "" @@ -599,7 +656,7 @@ msgstr "" #: i2p2www/pages/downloads/list.html:282 msgid "Click <a href=\"http://localhost:7657/configservice.jsp\">\"Restart\"</a>" -msgstr "" +msgstr "Klicke <a href=\"http://localhost:7657/configservice.jsp\">\"Restart\"</a>" #: i2p2www/pages/downloads/list.html:287 msgid "Grab a cup of coffee and come back in 11 minutes" @@ -611,6 +668,8 @@ msgid "" "The file is signed by zzz,\n" "<a href=\"%(signingkey)s\">whose key is here</a>." msgstr "" +"Diese Datei wurde von zzz signiert, <a href=\"%(signingkey)s\">dessen " +"Schlüssel hier zu finden ist</a>." #: i2p2www/pages/downloads/list.html:300 msgid "Previous Releases" @@ -626,6 +685,11 @@ msgid "" "and within the I2P network on <a " "href=\"http://%(echelon)s/\">%(echelon)s</a>." msgstr "" +"Frühere Veröffentlichungen sind verfügbar auf <a " +"href=\"http://code.google.com/p/i2p/downloads/list?can=1\">Google " +"Code</a>âŽ\n" +"und <a href=\"https://launchpad.net/i2p/trunk\">Launchpad</a>âŽ\n" +"und im I2P Netzwerk auf <a href=\"http://%(echelon)s/\">%(echelon)s</a>." #: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4 msgid "Mirror selection" @@ -637,7 +701,7 @@ msgstr "Datei:" #: i2p2www/pages/downloads/select.html:10 msgid "Any mirror" -msgstr "" +msgstr "Irgendein Downloadmirror" #: i2p2www/pages/global/bounty.html:19 msgid "" @@ -743,11 +807,11 @@ msgstr "" #: i2p2www/pages/global/macros:21 msgid "Previous" -msgstr "" +msgstr "vorheriger" #: i2p2www/pages/global/macros:36 msgid "Next" -msgstr "" +msgstr "nächsten" #: i2p2www/pages/global/macros:43 msgid "Posted in" @@ -883,7 +947,7 @@ msgstr "Konfigurations Dateien" #: i2p2www/pages/global/nav.html:72 msgid "GeoIP files" -msgstr "" +msgstr "GeoIP Daten" #: i2p2www/pages/global/nav.html:75 i2p2www/pages/global/nav.html:91 msgid "Plugins" @@ -1077,15 +1141,15 @@ msgstr "" #: i2p2www/pages/papers/list.html:29 msgid "By topic" -msgstr "" +msgstr "Nach Thema" #: i2p2www/pages/papers/list.html:35 msgid "By date" -msgstr "" +msgstr "Nach Datum" #: i2p2www/pages/papers/list.html:41 msgid "By author" -msgstr "" +msgstr "Nach Autor" #: i2p2www/pages/papers/list.html:83 #, python-format @@ -1100,7 +1164,7 @@ msgstr "" #: i2p2www/pages/site/contact.html:2 msgid "Contact" -msgstr "" +msgstr "Kontakt" #: i2p2www/pages/site/contact.html:5 msgid "" @@ -1177,11 +1241,11 @@ msgstr "" #: i2p2www/pages/site/contact.html:43 msgid "Lists" -msgstr "" +msgstr "Listen" #: i2p2www/pages/site/contact.html:46 msgid "Archive" -msgstr "" +msgstr "Archive" #: i2p2www/pages/site/contact.html:47 msgid "" @@ -1201,7 +1265,7 @@ msgstr "" #: i2p2www/pages/site/contact.html:62 msgid "Servers:" -msgstr "" +msgstr "Server:" #: i2p2www/pages/site/faq.html:2 msgid "Frequently Asked Questions" @@ -1217,7 +1281,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51 msgid "What systems will I2P run on?" -msgstr "" +msgstr "Auf welchen Systemen wird I2P laufen?" #: i2p2www/pages/site/faq.html:10 msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?" @@ -1225,7 +1289,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:263 msgid "My router has very few active peers, is this OK?" -msgstr "Mein Router hat sehr wenige aktive Peers, ist das OK?" +msgstr "Mein Router hat sehr wenige aktive Peers, ist das OK?" #: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:498 msgid "What do the Active x/y numbers mean in the router console?" @@ -1241,11 +1305,11 @@ msgstr "" #: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:348 msgid "Is using an outproxy safe?" -msgstr "" +msgstr "Ist es sicher einen Outproxie zu benutzen?" #: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:374 msgid "Most of the eepsites within I2P are down?" -msgstr "" +msgstr "Sind die meisten Eepsites im I2P-Netzwerk nicht erreichbar?" #: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:527 msgid "What ports does I2P use?" @@ -1253,11 +1317,11 @@ msgstr "Welche Ports werden von I2P genutzt?" #: i2p2www/pages/site/faq.html:17 msgid "Why is I2P listening for connections on port 32000?" -msgstr "" +msgstr "Warum lauscht I2P auf dem 32000 für Verbindungen?" #: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62 msgid "I think I found a bug, where can I report it?" -msgstr "" +msgstr "Ich glaube, ich habe eine Fehler gefunden. Wo kann ich diesen melden?" #: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:107 msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?" @@ -1269,7 +1333,7 @@ msgstr "Ich habe eine Frage!" #: i2p2www/pages/site/faq.html:22 msgid "Setup" -msgstr "" +msgstr "Einrichtung" #: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:232 msgid "" @@ -1289,7 +1353,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:383 msgid "How do I set up my own eepsite?" -msgstr "" +msgstr "Wie kann ich meine eigene Eepsite einrichten?" #: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:416 msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?" @@ -1313,7 +1377,7 @@ msgstr "Ist es möglich, I2P als SOCKS Proxy zu nutzen?" #: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:489 msgid "How do I configure my browser?" -msgstr "" +msgstr "Wie kann ich meinen Browser entsprechend einstellen?" #: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:434 msgid "" @@ -1359,7 +1423,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:45 msgid "Errors and Their Solutions" -msgstr "" +msgstr "Fehler und derren Lösungen" #: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:784 msgid "" @@ -1417,7 +1481,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:71 msgid "Discuss with the developers on IRC in #i2p-dev" -msgstr "" +msgstr "Diskutiere mit den Entwicklern per IRC in #i2p-dev" #: i2p2www/pages/site/faq.html:75 msgid "Please include relevant information from the router logs and wrapper logs." @@ -1788,7 +1852,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:344 msgid "Done." -msgstr "" +msgstr "Fertig." #: i2p2www/pages/site/faq.html:350 #, python-format @@ -1972,7 +2036,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:481 msgid "Whats an \"eepsite\"?" -msgstr "" +msgstr "Was ist eine \"Eepseite\" ?" #: i2p2www/pages/site/faq.html:483 msgid "" @@ -1981,6 +2045,8 @@ msgid "" "setting your web browser's HTTP proxy to use the web proxy (typically it\n" "listens on localhost port 4444), and browsing to the site." msgstr "" +"Eine Eepsite ist eine Webseite, welche anonym gehostet ist - du kannst " +"diese betreten" #: i2p2www/pages/site/faq.html:491 #, python-format @@ -2275,7 +2341,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:735 msgid "Why is I2P listening on port 32000?" -msgstr "" +msgstr "Warum lauscht I2P auf dem Port 32000 ?" #: i2p2www/pages/site/faq.html:737 msgid "" @@ -2320,7 +2386,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:767 msgid "Stop your I2P router" -msgstr "" +msgstr "Stoppe deinen I2P Router" #: i2p2www/pages/site/faq.html:770 msgid "" @@ -2334,7 +2400,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:780 msgid "Start your I2P router" -msgstr "" +msgstr "Starte deinen I2P Router" #: i2p2www/pages/site/faq.html:787 msgid "" @@ -2435,11 +2501,11 @@ msgstr "" #: i2p2www/pages/site/impressum.html:4 msgid "German laws" -msgstr "" +msgstr "Deutsche Gesetze" #: i2p2www/pages/site/index.html:2 msgid "I2P Anonymous Network" -msgstr "" +msgstr "I2P Anonymes Netzwerk" #: i2p2www/pages/site/index.html:4 msgid "" @@ -2450,7 +2516,7 @@ msgstr "" #: i2p2www/pages/site/index.html:7 msgid "What does I2P do for you?" -msgstr "" +msgstr "Was macht I2P für dich?" #: i2p2www/pages/site/index.html:8 msgid "" @@ -2462,11 +2528,11 @@ msgstr "" #: i2p2www/pages/site/index.html:9 #, python-format msgid "Get I2P %(version)s" -msgstr "" +msgstr "Bekomme I2P %(version)s" #: i2p2www/pages/site/index.html:13 msgid "What is I2P?" -msgstr "" +msgstr "Was ist I2P ?" #: i2p2www/pages/site/index.html:15 msgid "" @@ -2498,11 +2564,11 @@ msgstr "" #: i2p2www/pages/site/index.html:28 msgid "Read more…" -msgstr "" +msgstr "Lese more…" #: i2p2www/pages/site/index.html:33 msgid "What can you do with I2P?" -msgstr "" +msgstr "Was kannst du mit I2P machen?" #: i2p2www/pages/site/index.html:36 #, python-format @@ -2576,19 +2642,19 @@ msgstr "" #: i2p2www/pages/site/links.html:12 msgid "I2P on the web" -msgstr "" +msgstr "I2P im Netz" #: i2p2www/pages/site/links.html:20 msgid "Friends of I2P" -msgstr "" +msgstr "Freunde von I2P" #: i2p2www/pages/site/links.html:32 msgid "More Projects and Documentation" -msgstr "" +msgstr "Mehr Projekte und Dokumentationen" #: i2p2www/pages/site/links.html:42 msgid "Press" -msgstr "" +msgstr "Presse" #: i2p2www/pages/site/links.html:46 msgid "Boards, newssite, others" diff --git a/i2p2www/translations/fr/LC_MESSAGES/about.po b/i2p2www/translations/fr/LC_MESSAGES/about.po index e81772b05..956e298d9 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/about.po +++ b/i2p2www/translations/fr/LC_MESSAGES/about.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" "POT-Creation-Date: 2013-09-01 03:42+0000\n" -"PO-Revision-Date: 2013-10-09 11:07+0000\n" +"PO-Revision-Date: 2013-10-26 08:28+0000\n" "Last-Translator: Towatowa441\n" "Language-Team: French " "(http://www.transifex.com/projects/p/I2P/language/fr/)\n" @@ -272,11 +272,11 @@ msgstr "" #: i2p2www/pages/site/about/hall-of-fame.html:2 msgid "Hall Of Fame" -msgstr "" +msgstr "Hall de gloire" #: i2p2www/pages/site/about/hall-of-fame.html:5 msgid "I2P'<small>s</small> Hall of Fame" -msgstr "" +msgstr "Hall de Gloire de I2P" #: i2p2www/pages/site/about/hall-of-fame.html:6 #, python-format @@ -578,7 +578,7 @@ msgstr "Client Bitcoin pour I2P" #: i2p2www/pages/site/about/hall-of-fame.html:21 msgid "Unit Tests for I2P router" -msgstr "" +msgstr "Tests d'unité pour routeur I2P" #: i2p2www/pages/site/about/hall-of-fame.html:23 msgid "Bounty Robert" @@ -662,6 +662,25 @@ msgid "" "href=\"http://en.wikipedia.org/wiki/Public_key_encryption\">public " "keys</a>)." msgstr "" +"I2P est un réseau anonyme, qui fournit une simple couche logicielle que " +"les applications peuvent\n" +"utiliser pour communiquer entre elles de manière anonyme et sécurisée. " +"Le réseau lui-même est\n" +"strictement basé paquets (à la manière de <a " +"href=\"http://fr.wikipedia.org/wiki/Internet_Protocol\">IP</a>), mais il " +"y a \n" +"une bibliotèque disponible pour permettre des communications en streaming" +" par dessus de cela (à la\n" +"manière de <a " +"href=\"http://fr.wikipedia.org/wiki/Transmission_Control_Protocol\">TCP</a>)." +"\n" +"Toute la communication est chiffrée de bout en bout (au total il y a " +"quatre couches de\n" +"chiffrage utilisées en envoyant un paquet) et même les points de fin " +"(\"destinations\")\n" +"sont des identifiants cryptographiques (essentiellement une paire de <a " +"href=\"https://fr.wikipedia.org/wiki/Cryptographie_asymétrique\" >clés " +"publiques</a>)." #: i2p2www/pages/site/about/intro.html:17 msgid "How does it work?" @@ -731,6 +750,21 @@ msgid "" "lookups \n" "are required." msgstr "" +"La première fois qu'un client veut contacter un autre client, ils font " +"une requête\n" +"envers la \"<a href=\"%(netdb)s\">base de données</a>\" complètement " +"distribuée - \n" +"c'est une <a " +"href=\"https://fr.wikipedia.org/wiki/Table_de_hachage_distribuée\">\n" +"table de hachage distribuée (DHT)</a> à la structure personnalisée basée " +"depuis l'\n" +"<a href=\"https://fr.wikipedia.org/wiki/Kademlia\">algorithme " +"Kademlia</a>. Cela est fait\n" +"pour trouver plus efficacement les tunnels entrants de l'autre pair, mais" +" les messages ultérieurs\n" +"entre eux incluent habituellement cette donnée donc il n'est pas requis " +"de faire d'autres\n" +"consultation de la base de données réseau." #: i2p2www/pages/site/about/intro.html:44 #, python-format @@ -795,6 +829,25 @@ msgid "" " those are \n" "not ready for use yet." msgstr "" +"I2PTunnel est actuellement utilisé pour laisser les gens faire " +"fonctionner leur propre\n" +"site Web anonyme (\"Eepsite\") en faisant fonctionner un serveur web " +"normal et\n" +"en dirigeant I2PTunnel vers lui, auquel les gens peuvent avoir accès " +"anonymement à travers I2P avec un navigateur web normal en faisant " +"fonctionner un proxy HTTP I2PTunnel (\"eepproxy\"). De plus, nous " +"utilisons le même\n" +"technique pour faire fonctionner un réseau IRC anonyme (où le serveur IRC" +" est hébergé anonymement, et des clients IRC standard utilisent un " +"I2PTunnel pour le contacter). Il y a d'autres efforts de développement " +"d'applications qui ont aussi lieu, comme de construise une application " +"optimisée de transfert de fichier par essaimage (à la <a " +"href=\"http://www.bittorrent.com/\">BitTorrent</a>), un système de " +"stockage distribué (à la <a " +"href=\"https://freenetproject.org/\">Freenet</a> / <a " +"href=\"http://mnetproject.org/\">MNet</a>), et un système de blog (un <a " +"href=\"http://www.livejournal.com/\">LiveJournal</a> pleinement " +"distribué), mais celles-ci ne sont pas encore prête pour être utilisées." #: i2p2www/pages/site/about/intro.html:76 msgid "" @@ -820,6 +873,27 @@ msgid "" " \n" "certain circumstances the technique could be appropriate." msgstr "" +"I2P n'est pas en soi un réseau \"outproxy\" - le client auquel vous " +"envoyez un message \n" +"est l'identifiant cryptographique, pas une certaine adresse IP, donc le " +"message doit\n" +"se doit d'être adressé à quelqu'un exécutant I2P. Cependant, il est " +"possible pour ce client \n" +"d'être un outproxy, vous permettant de se servir de sa connexion Internet" +" anonymement.\n" +"Pour démontrer ceci, le \"eepproxy\" va accepter des URLs non normales à " +"I2P\n" +"(par exemple \"http://www.i2p.net\") et les expédier à une destination " +"spécifique\n" +"qui exécute un proxy HTTP <a href=\"http://www.squid-cache.org/\">squid/a" +" >, permettant\n" +"la navigation anonyme simple sur le Web normal. De simple outproxies " +"comme celui-là \n" +"ne sont pas viables à long terme pour plusieurs raisons (incluant le coût" +" d'en faire\n" +"tourner un aussi bien que les problèmes d'anonymat et de sécurité qu'ils " +"amènent), mais dans\n" +"certaines circonstances cette technique peut se révéler appropriée." #: i2p2www/pages/site/about/intro.html:90 #, python-format @@ -1321,7 +1395,7 @@ msgstr "contact presse, gère les relations publiques et les affaires" #: i2p2www/pages/site/about/team.html:30 #, python-format msgid "<a href=\"http://%(forum)s/\">Forum</a> admin" -msgstr "" +msgstr "Admin du <a href=\"http://%(forum)s/\">forum</a>" #: i2p2www/pages/site/about/team.html:32 msgid "manage the public user forum" @@ -1329,7 +1403,7 @@ msgstr "gère le forum utilisateurs public" #: i2p2www/pages/site/about/team.html:35 msgid "Mirrors admin" -msgstr "" +msgstr "gère les miroirs du projet" #: i2p2www/pages/site/about/team.html:37 msgid "manage the project mirrors" @@ -1346,47 +1420,47 @@ msgstr "gére les référentiels monotones publics" #: i2p2www/pages/site/about/team.html:45 msgid "Packager; Linux" -msgstr "" +msgstr "Packager des distribution Linux" #: i2p2www/pages/site/about/team.html:47 msgid "Linux (Debian/Ubuntu) distribution packager" -msgstr "" +msgstr "Packager des distribution Linux (Debian/Ubuntu)" #: i2p2www/pages/site/about/team.html:50 msgid "Packager; Windows" -msgstr "" +msgstr "Packager; Windows" #: i2p2www/pages/site/about/team.html:52 msgid "Windows installer packager" -msgstr "" +msgstr "Packager de l'installateur sous Windows" #: i2p2www/pages/site/about/team.html:55 msgid "Release Manager" -msgstr "" +msgstr "Responsable des versions" #: i2p2www/pages/site/about/team.html:57 msgid "Builds and signs the releases" -msgstr "" +msgstr "Compile et signe les versions" #: i2p2www/pages/site/about/team.html:60 msgid "Update admin" -msgstr "" +msgstr "Admin des update" #: i2p2www/pages/site/about/team.html:62 msgid "Monitors and recruits in-network update hosts" -msgstr "" +msgstr "Surveille et recrute des hôtes de mise à jour dans le réseau" #: i2p2www/pages/site/about/team.html:65 msgid "Reseed admin" -msgstr "" +msgstr "Admin réamorçage" #: i2p2www/pages/site/about/team.html:67 msgid "Monitors, advises and recruits reseed hosts" -msgstr "" +msgstr "Surveille, conseille et recrute des hôtes de réamorçage" #: i2p2www/pages/site/about/team.html:70 msgid "Security expert" -msgstr "" +msgstr "Expert en sécurité" #: i2p2www/pages/site/about/team.html:71 i2p2www/pages/site/about/team.html:76 #: i2p2www/pages/site/about/team.html:81 i2p2www/pages/site/about/team.html:101 @@ -1403,23 +1477,23 @@ msgstr "vacant" #: i2p2www/pages/site/about/team.html:72 msgid "threat model / crypto expert" -msgstr "" +msgstr "Modèle de menace / expert crypto" #: i2p2www/pages/site/about/team.html:75 msgid "User Advocate" -msgstr "" +msgstr "Avocat des utilisateurs" #: i2p2www/pages/site/about/team.html:77 msgid "gather, prioritize, advocate for user needs" -msgstr "" +msgstr "Rassemble, priorise, défend les besoins exprimés" #: i2p2www/pages/site/about/team.html:80 msgid "Web Designer" -msgstr "" +msgstr "Concepteur web" #: i2p2www/pages/site/about/team.html:82 msgid "manage the public project website content design" -msgstr "" +msgstr "Gère le design du site web public du projet" #: i2p2www/pages/site/about/team.html:85 #, python-format @@ -1428,7 +1502,7 @@ msgstr "Admin du <a href=\"%(website)s\">serveur Web</a>" #: i2p2www/pages/site/about/team.html:87 msgid "manage the public project webservers" -msgstr "" +msgstr "Gère les serveurs web publics du projet" #: i2p2www/pages/site/about/team.html:90 #, python-format @@ -1437,23 +1511,23 @@ msgstr "Admin du <a href=\"%(website)s\">site web</a>" #: i2p2www/pages/site/about/team.html:92 msgid "manage the public project website content" -msgstr "" +msgstr "Gère le contenu du site web public du projet" #: i2p2www/pages/site/about/team.html:95 msgid "News Admin" -msgstr "" +msgstr "Admin actualités" #: i2p2www/pages/site/about/team.html:97 msgid "manage router console news feed" -msgstr "" +msgstr "Gérer le fil d'actualités de la console du routeur" #: i2p2www/pages/site/about/team.html:100 msgid "Director of passion" -msgstr "" +msgstr "Directeur de passion" #: i2p2www/pages/site/about/team.html:102 msgid "community motivator" -msgstr "" +msgstr "motivateur de communauté" #: i2p2www/pages/site/about/team.html:106 msgid "Dev" @@ -1461,79 +1535,79 @@ msgstr "Développement" #: i2p2www/pages/site/about/team.html:107 msgid "Core Lead" -msgstr "" +msgstr "Meneur principal" #: i2p2www/pages/site/about/team.html:109 msgid "lead dev for the SDK and router" -msgstr "" +msgstr "Dirige le développement du SDK et du routeur" #: i2p2www/pages/site/about/team.html:112 #, python-format msgid "<a href=\"http://%(postman)s/\">I2P mail</a> lead" -msgstr "" +msgstr "Meneur de <a href=\"http://%(postman)s/\">I2P mail</a>" #: i2p2www/pages/site/about/team.html:114 msgid "organize and develop the i2p mail system" -msgstr "" +msgstr "organise et développe le système de courrier d'i2p" #: i2p2www/pages/site/about/team.html:117 #, python-format msgid "<a href=\"http://%(i2host)s/\">I2Host</a> lead" -msgstr "" +msgstr "Meneur de <a href=\"http://%(i2host)s/\">I2Host</a>" #: i2p2www/pages/site/about/team.html:119 msgid "I2Host addressbook application" -msgstr "" +msgstr "Application carnet d'adresses I2Host " #: i2p2www/pages/site/about/team.html:122 #, python-format msgid "<a href=\"http://%(bob)s/\">BOB</a> lead" -msgstr "" +msgstr "Meneur de <a href=\"http://%(bob)s/\">BOB</a>" #: i2p2www/pages/site/about/team.html:124 msgid "Basic Open Bridge" -msgstr "" +msgstr "Basic Open Bridge" #: i2p2www/pages/site/about/team.html:127 #, python-format msgid "<a href=\"http://%(bote)s/\">I2P-Bote</a> lead" -msgstr "" +msgstr "Meneur de <a href=\"http://%(bote)s/\">I2P-Bote</a>" #: i2p2www/pages/site/about/team.html:129 msgid "I2PBote plugin" -msgstr "" +msgstr "Plugin I2PBote" #: i2p2www/pages/site/about/team.html:132 #, python-format msgid "<a href=\"http://%(bob)s/\">Robert</a> lead" -msgstr "" +msgstr "Meneur de <a href=\"http://%(bob)s/\">Robert</a>" #: i2p2www/pages/site/about/team.html:134 msgid "Robert BitTorrent client" -msgstr "" +msgstr "Client BitTorrent Robert" #: i2p2www/pages/site/about/team.html:137 #, python-format msgid "<a href=\"http://%(forum)s/viewforum?f=25\">I2Phex</a> lead" -msgstr "" +msgstr "Meneur de <a href=\"http://%(forum)s/viewforum?f=25\">I2Phex</a>" #: i2p2www/pages/site/about/team.html:139 msgid "I2Phex Gnutella client" -msgstr "" +msgstr "Client Gnutella I2Phex" #: i2p2www/pages/site/about/team.html:142 #, python-format msgid "<a href=\"http://%(forum)s/viewforum?f=21\">I2PSnark</a> lead" -msgstr "" +msgstr "Meneur de <a href=\"http://%(forum)s/viewforum?f=21\">I2PSnark</a>" #: i2p2www/pages/site/about/team.html:144 msgid "Maintains the integrated Bittorrent client" -msgstr "" +msgstr "Maintient le client Bittorrent intégré" #: i2p2www/pages/site/about/team.html:147 #, python-format msgid "<a href=\"http://%(forum)s/viewforum?f=30\">iMule</a> lead" -msgstr "" +msgstr "Meneur <a href=\"http://%(forum)s/viewforum?f=30\">iMule</a>" #: i2p2www/pages/site/about/team.html:149 msgid "eMule client over I2P" @@ -1542,19 +1616,19 @@ msgstr "Client eMule sur I2P" #: i2p2www/pages/site/about/team.html:152 #, python-format msgid "<a href=\"http://%(forum)s/viewforum?f=29\">Syndie</a> lead" -msgstr "" +msgstr "Meneur <a href=\"http://%(forum)s/viewforum?f=29\">Syndie</a>" #: i2p2www/pages/site/about/team.html:154 msgid "Syndie development" -msgstr "" +msgstr "Développement de Syndie" #: i2p2www/pages/site/about/team.html:157 msgid "Susimail lead" -msgstr "" +msgstr "Meneur de Susimail" #: i2p2www/pages/site/about/team.html:159 msgid "Susimail development" -msgstr "" +msgstr "Développement de Susimail" #: i2p2www/pages/site/about/team.html:162 msgid "Console" @@ -1562,7 +1636,7 @@ msgstr "Console" #: i2p2www/pages/site/about/team.html:164 msgid "Router console HTML/CSS design" -msgstr "" +msgstr "Design HTML/CSS de la console routeur" #: i2p2www/pages/site/about/team.html:167 msgid "SAM" @@ -1570,11 +1644,11 @@ msgstr "SAM" #: i2p2www/pages/site/about/team.html:169 msgid "SAM maintainer" -msgstr "" +msgstr "Maintient SAM" #: i2p2www/pages/site/about/team.html:172 msgid "I2PCPP lead" -msgstr "" +msgstr "Meneur I2PCPP" #: i2p2www/pages/site/about/team.html:174 msgid "C++ Router" @@ -1622,19 +1696,21 @@ msgstr "Contributeurs" #: i2p2www/pages/site/about/team.html:212 msgid "fire2pe dev, console enhancements" -msgstr "" +msgstr "Fire2pe dev, améliorations console" #: i2p2www/pages/site/about/team.html:216 msgid "desktopgui, dijjer port" -msgstr "" +msgstr "Interface graphique utilisateur, portage dijjer" #: i2p2www/pages/site/about/team.html:220 msgid "Debian/Ubuntu Packager and PPA maintainer" -msgstr "" +msgstr "Packager Debian/Ubuntu et mainteneur de PPA " #: i2p2www/pages/site/about/team.html:224 msgid "Routerconsole backend and UI work, website revamp, unit tests work" msgstr "" +"Arrière-plan et travail sur l'UI de la console routeur, réorganisation du" +" site Web, travail sur les tests d'unité" #: i2p2www/pages/site/about/team.html:229 msgid "Help needed on many fronts!" @@ -1646,7 +1722,7 @@ msgstr "Anciens contributeurs" #: i2p2www/pages/site/about/team.html:235 msgid "I2PTunnel development, ministreaming library" -msgstr "" +msgstr "développement I2PTunnel, mini bibliothèque de flux" #: i2p2www/pages/site/about/team.html:239 msgid "Project lead, Syndie lead" @@ -1654,11 +1730,11 @@ msgstr "Responsable du projet, idem pour Syndie" #: i2p2www/pages/site/about/team.html:243 msgid "Project lead, Syndie lead, I2Phex, support guru" -msgstr "" +msgstr "Responsable du projet, meneur de Syndie, I2Phex, gourou en support" #: i2p2www/pages/site/about/team.html:247 msgid "iMule lead" -msgstr "" +msgstr "Meneur iMule" #: i2p2www/pages/site/about/team.html:251 #: i2p2www/pages/site/about/team.html:255 @@ -1668,11 +1744,11 @@ msgstr "Travail I2Phex" #: i2p2www/pages/site/about/team.html:263 msgid "Python SAM library, attack simulations" -msgstr "" +msgstr "Bibliothèque Python SAM, simulations d'attaques" #: i2p2www/pages/site/about/team.html:267 msgid "i2pmail development" -msgstr "" +msgstr "Développement de i2pmail" #: i2p2www/pages/site/about/team.html:271 msgid "Syndie help" @@ -1680,47 +1756,49 @@ msgstr "Aide pour Syndie" #: i2p2www/pages/site/about/team.html:275 msgid "i2p mail,susimail and susidns apps" -msgstr "" +msgstr "Apps i2p mail, susimail et susidns" #: i2p2www/pages/site/about/team.html:279 msgid "I2Phex (port of Phex to I2P)" -msgstr "" +msgstr "I2Phex (portage de Phex vers I2P)" #: i2p2www/pages/site/about/team.html:283 msgid "addressbook,i2p-bt,syndie client" -msgstr "" +msgstr "carnet d'adresses, i2p-bt, client Syndie" #: i2p2www/pages/site/about/team.html:287 msgid "organize and develop the i2p-bt BitTorrent port" -msgstr "" +msgstr "Organise et développe le portage BitTorrent i2p-bt" #: i2p2www/pages/site/about/team.html:291 msgid "addressbook, i2p-bt, syndie client development" -msgstr "" +msgstr "Carnet d'adresses, i2p-bt, développement du client Syndie" #: i2p2www/pages/site/about/team.html:295 msgid "encryption and signature routines, I2PIM" -msgstr "" +msgstr "Routines d'encryption et de signature, I2PIM" #: i2p2www/pages/site/about/team.html:299 msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)" -msgstr "" +msgstr "Code jython de SAM, travail sur stasher (DHT) et v2v (VoI2P)" #: i2p2www/pages/site/about/team.html:303 msgid "installer, systray, bogobot" -msgstr "" +msgstr "installateur, zone de notification, bogobot" #: i2p2www/pages/site/about/team.html:307 msgid "jbigi development, wiki migration, doc cleanup" -msgstr "" +msgstr "Développement jbigi, migration du wiki, nettoyage de la doc" #: i2p2www/pages/site/about/team.html:311 msgid "java debugging and client development on I2PTunnel and the router console" msgstr "" +"Débogage java debugging et développement de client sur I2PTunnel et la " +"console du routeur" #: i2p2www/pages/site/about/team.html:315 msgid "SAM perl module" -msgstr "" +msgstr "Module perl de SAM" #: i2p2www/pages/site/about/team.html:319 msgid "i2psnark work" @@ -1728,11 +1806,11 @@ msgstr "travail i2psnark" #: i2p2www/pages/site/about/team.html:323 msgid "java cleanup" -msgstr "" +msgstr "Nettoyage Java" #: i2p2www/pages/site/about/team.html:327 msgid "docs. wiki migration" -msgstr "" +msgstr "Docs. Migration du wiki" #: i2p2www/pages/site/about/team.html:331 msgid "translations into French" @@ -1740,11 +1818,11 @@ msgstr "traductions en français" #: i2p2www/pages/site/about/team.html:335 msgid "C port of jcpuid" -msgstr "" +msgstr "Portage en C de jcpuid" #: i2p2www/pages/site/about/team.html:339 msgid "C# SAM library, pants, fortuna integration" -msgstr "" +msgstr "Bibliothèque SAM C#, pants, fortuna integration" #: i2p2www/pages/site/about/team.html:343 msgid "libSAM" @@ -1761,11 +1839,11 @@ msgstr "Thèmes console et site web" #: i2p2www/pages/site/about/team.html:358 msgid "… and many others" -msgstr "" +msgstr "… et de nombreux autres" #: i2p2www/pages/site/about/performance/future.html:2 msgid "Future Performance Improvements" -msgstr "" +msgstr "Améliorations de la performance dans le futur" #: i2p2www/pages/site/about/performance/future.html:4 msgid "August 2010" @@ -1784,6 +1862,17 @@ msgid "" " course\n" "not comprehensive, but it does cover the major ones that are seen." msgstr "" +"Il y a quelques techniques majeures qui peuvent être faites pour " +"s'améliorer\n" +"la performance perçue de I2P - certaines des suivantes sont liées au CPU," +" d'autres\n" +"sont liées à la bande passante, et d'autres sont liées au protocole. " +"Cependant, toutes\n" +"ces dimensions affectent la latence, le débit, et la performance perçue " +"du\n" +"réseau, comme elles réduisent le conflit pour des ressources rares. Cette" +" liste est bien sûr\n" +"incomplète, mais elle couvre vraiment les points majeurs qui sont vus." #: i2p2www/pages/site/about/performance/future.html:15 #: i2p2www/pages/site/about/performance/index.html:106 @@ -1792,10 +1881,13 @@ msgid "" "For past performance improvements see the <a href=\"%(history)s\">\n" "Performance History</a>." msgstr "" +"Pour les améliorations de performance passées voir l'<a " +"href=\"%(history)s\">\n" +"histoire de performance</a>." #: i2p2www/pages/site/about/performance/future.html:20 msgid "Better peer profiling and selection" -msgstr "" +msgstr "Meilleure sélection et profilage du pair" #: i2p2www/pages/site/about/performance/future.html:21 #, python-format @@ -1811,10 +1903,20 @@ msgid "" "ourselves to a <a href=\"%(sybilpdf)s\">Sybil</a> attack\n" "from a powerful adversary with lots of fast machines." msgstr "" +"Une des parties probablement les plus importantes pour obtenir la " +"performance plus rapide sera\n" +"d'améliorer comment les routeurs choisissent les pairs( au travers " +"desquels ils construisent leurs tunnels -\n" +"en s'assurant qu'ils n'utilisent pas de pairs avec des liens lents ou " +"avec des liens rapides qui\n" +"seraient surchargés, etc. De plus, nous devons nous assurer que nous ne " +"nous exposons pas\n" +"nous-mêmes à une attaque <a href=\"%(sybilpdf)s\">Sybil</a>\n" +"lancée depuis un adversaire puissant avec beaucoup de machines rapides." #: i2p2www/pages/site/about/performance/future.html:30 msgid "Network database tuning" -msgstr "" +msgstr "Réglage de la base de données réseau" #: i2p2www/pages/site/about/performance/future.html:31 msgid "" @@ -1834,10 +1936,26 @@ msgid "" "if we\n" "bounce back a reply), as well as how many concurrent searches we perform." msgstr "" +"Nous allons vouloir être plus efficaces en guérissant la base de données " +"de réseau\n" +"et les algorithmes de maintenance - plutôt que constamment explorer le " +"keyspace pour de nouveaux\n" +"pairs - cause d'un nombre important de messages de réseau et de charge de" +" routeur - nous\n" +"pouvons ralentir ou peut même arrêter d'explorer jusqu'à ce que nous " +"détections qu'il y a\n" +"quelque chose de nouveau méritant d'être trouvé (ex: dégrader le taux " +"d'exploration en se basant sur la dernière fois que quelqu'un nous a " +"donné une référence de quelqu'un dont nous n'avions jamais entendu " +"parler). Nous pouvons aussi faire certains\n" +"réglages sur ce que nous envoyons actuellement - sur combien de pairs " +"nous rebondissons (ou même si nous\n" +"rebondissons en retour une réponse), aussi bien que combien de recherches" +" simultanées nous accomplissons." #: i2p2www/pages/site/about/performance/future.html:42 msgid "Session Tag Tuning and Improvements" -msgstr "" +msgstr "Réglage et améliorations de Tag de session" #: i2p2www/pages/site/about/performance/future.html:43 #, python-format @@ -1862,6 +1980,23 @@ msgid "" "encryption with\n" "a trivial AES operation." msgstr "" +"La façon dont l'algorithme <a " +"href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a>\n" +"fonctione est en gérant un ensemble de tableaux de 32 octets à usage " +"unique, et en\n" +"les faisant expirer s'ils ne sont pas utilisés assez rapidement. Si nous " +"les faisons expirer trop tôt, nous\n" +"sommes obligés de nous replier en ayant recours à un (coûteux) plein " +"chiffrage ElGamal, mais si nous ne\n" +"les faisons pas expirer assez rapidement, nous devons réduire leur " +"quantité pour que nous ne soyons pas \n" +"à court de mémoire (et si le destinataire est d'une façon ou d'une autre " +"corrompu et perd certaines étiquettes, encore plus d'échecs de chiffrage " +"peuvent se produire avant la détection). Avec une certaine détection plus" +" active et\n" +"des algorithmes de retour d'information, nous pouvons sans risque et plus" +" efficacement ajuster la durée de vie des étiquettes, remplaçant le " +"chiffrage ElGamal avec une insignifiante opération AES." #: i2p2www/pages/site/about/performance/future.html:55 #, python-format @@ -1869,10 +2004,13 @@ msgid "" "Additional ideas for improving Session Tag delivery are described on the\n" "<a href=\"%(elgamalaes)s#future\">ElGamal/AES+SessionTag page</a>." msgstr "" +"Des idées supplémentaires pour améliorer la livraison d'étiquette de " +"session (Session Tag) sont décrites sur la\n" +"<a href=\"%(elgamalaes)s#future\">page ElGamal/AES+SessionTag page</a>." #: i2p2www/pages/site/about/performance/future.html:61 msgid "Migrate sessionTag to synchronized PRNG" -msgstr "" +msgstr "Migrer l'étiquette de session (sessionTag) vers un PRNG synchronisé" #: i2p2www/pages/site/about/performance/future.html:62 #, python-format @@ -1893,6 +2031,24 @@ msgid "" "of what messages are successfully delivered so that we know what tags \n" "we may use." msgstr "" +"Dès maintenant, notre algorithme <a " +"href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a>\n" +"fonctionne en étiquetant chaque message crypté avec un \"nonce\" " +"(occasion ?) unique aléatoire\n" +"de 32 octets (\"une étiquette de session\"), identifiant ce message comme" +" étant crypté\n" +"avec la clé de la session AES associée. Ceci empêche des pairs de " +"distinguer\n" +"les messages faisant partie de la même session, sachant que chaque " +"message a une nouvelle étiquette complètement aléatoire. Pour accomplir " +"ceci, tous les quelques messages empaquette un tout\n" +"nouvel ensemble d'étiquettes de session dans le message crypté lui-même, " +"livrant d'une manière transparente\n" +"une façon d'identifier des messages futurs. Nous devons alors garder la " +"trace\n" +"de quels messages sont livrés avec succès afin que nous sachions quelles " +"étiquettes\n" +"nous pouvons utiliser." #: i2p2www/pages/site/about/performance/future.html:74 msgid "" @@ -1911,10 +2067,28 @@ msgid "" "demand (with the recipient precalculating the next few possible values \n" "to handle out of order delivery)." msgstr "" +"Ceci marche bien et c'est assez robuste, cependant c'est inefficace en " +"termes\n" +"d'utilisation de bande passante, comme cela exige la livraison de ces " +"étiquettes en avance de\n" +"temps (et toutes les étiquettes peuvent ne pas être nécessaires, ou " +"certaines peuvent être gaspillés, en raison de\n" +"leur expiration). En moyenne cependant, pré délivrer l'étiquette de " +"session coûte\n" +"32 octets par message (la taille d'une étiquette). Comme Taral l'a " +"suggéré, cette\n" +"taille peut être évitée en remplaçant la livraison des étiquettes par un " +"PRNG synchronisé\n" +" - quand une nouvelle session est établie (via un block ElGamal crypté),\n" +"les deux côtés essaiment un PRNG pour utilisation et produisent les " +"étiquettes de session sur\n" +"demande (avec le destinataire pré calculant à l'avance les quelques peu " +"de valeurs suivantes possibles\n" +"afin de traiter la panne de livraison)." #: i2p2www/pages/site/about/performance/future.html:87 msgid "Longer lasting tunnels" -msgstr "" +msgstr "Tunnels de longue durée" #: i2p2www/pages/site/about/performance/future.html:88 msgid "" @@ -1926,6 +2100,12 @@ msgid "" "the\n" "network and CPU load (due to expensive tunnel creation messages)." msgstr "" +"La durée actuelle de tunnel est par défaut de 10 minutes, c'est assez " +"arbitraire, quoique\n" +"cela \"va bien\". Une fois que nous aurons le code de guérison de tunnel " +"et un code de détection d'échec plus efficace, nous pourrons sans risque " +"varier ces durées, réduisant les\n" +"charges réseau et UC (dues aux coûteux messages de création de tunnel)." #: i2p2www/pages/site/about/performance/future.html:95 msgid "" @@ -1939,6 +2119,15 @@ msgid "" "Also, it would be difficult to maintain backward compatibility with such " "a change." msgstr "" +"Ceci semble être une réparation facile pour une haute charge sur des " +"routeurs à grande bande passante, mais\n" +"nous ne devrions pas y recourir jusqu'à ce que nous ayons ajusté le " +"tunnel construisant des algorithmes plus loin. \n" +"Cependant, la durée de vie de tunnel de 10 minutes est codée en dur dans" +" un bon nombre d'endroits,\n" +"donc un effort substantiel serait exigé pour changer la durée.\n" +"Aussi, il serait difficile de maintenir la compatibilité descendante avec" +" un tel changement." #: i2p2www/pages/site/about/performance/future.html:102 msgid "" @@ -1946,10 +2135,14 @@ msgid "" "high,\n" "there are no current plans to extend tunnel lifetime." msgstr "" +"Actuellement, puisque dans le réseau le taux de réussite de construction " +"de tunnel est en moyenne assez élevé,\n" +"il n'y a actuellement aucun plan visant à étendre la durée de vie de " +"tunnel." #: i2p2www/pages/site/about/performance/future.html:108 msgid "Adjust the timeouts" -msgstr "" +msgstr "Ajuster les temps d'échéance" #: i2p2www/pages/site/about/performance/future.html:109 msgid "" @@ -1969,6 +2162,20 @@ msgid "" "tunnel that\n" "doesn't pass our test within 60 seconds \"dead\"?" msgstr "" +"Encore une autre des choses assez arbitraires mais avec le \"sentiment " +"que ça va bien\" que nous avons : ce sont\n" +"les temps d'échéance (time out) actuels pour les diverses activités. " +"Pourquoi avons-nous un temps d'échéance\n" +"de 60 secondes en cas de \"pair inaccessible\" ? Pourquoi essayons-nous " +"d'envoyer à travers un tunnel différent\n" +"qu'un LeaseSet annonce après 10 secondes ? Pourquoi les questions à la " +"base de données de réseau\n" +"sont limitées par des plafonds de 60 ou 20 secondes ? Pourquoi les " +"destinations sont-elles configurées pour demander un nouvel ensemble de " +"tunnels toutes les 10 minutes ? Pourquoi permettons-nous 60 secondes à un" +" pair pour répondre à notre requête à se joindre un tunnel ? Pourquoi " +"considérons-nous un tunnel qui\n" +"ne passe pas notre test dans les 60 secondes \"mort\" ?" #: i2p2www/pages/site/about/performance/future.html:119 msgid "" @@ -1977,16 +2184,23 @@ msgid "" "as tunable parameters to allow for more appropriate tradeoffs between\n" "bandwidth, latency, and CPU usage." msgstr "" +"Chacun de ces impondérables peut être abordé avec du code plus adaptatif," +" et aussi\n" +"avec des paramètres ajustables pour tenir compte de différences plus " +"appropriées entre\n" +"bande passante, latence et utilisation de CPU." #: i2p2www/pages/site/about/performance/future.html:125 msgid "Full streaming protocol improvements" -msgstr "" +msgstr "Améliorations du protocole full streaming" #: i2p2www/pages/site/about/performance/future.html:128 msgid "" "Perhaps re-enable the interactive stream profile (the \n" "current implementation only uses the bulk stream profile)." msgstr "" +"Peut-être re-permettre le profil stream interactif (la\n" +"mise en Å“uvre actuelle utilise seulement le profil stream en vrac (bulk)." #: i2p2www/pages/site/about/performance/future.html:134 msgid "" @@ -1996,6 +2210,11 @@ msgid "" " \n" "the router's overall bandwidth limiting, of course." msgstr "" +"Limitation de bande passante au niveau du client (ou dans les deux " +"directions sur un flux stream,\n" +"ou probablement partagée à travers de multiples flux stream). Ceci serait" +" bien sûr en supplément à \n" +"la limitation de bande passante globale du routeur." #: i2p2www/pages/site/about/performance/future.html:141 msgid "" @@ -2003,12 +2222,17 @@ msgid "" "known \n" "destinations)." msgstr "" +"Listes de contrôle d'accès (permettant seulement des flux vers ou depuis " +"certaines autres\n" +"destinations connues)." #: i2p2www/pages/site/about/performance/future.html:147 msgid "" "Web controls and monitoring the health of the various streams, as well \n" "as the ability to explicitly close or throttle them." msgstr "" +"Le contrôle Web et le contrôle de la santé des divers flux, autant\n" +"que la capacité de, explicitement, les fermer ou les étrangler." #: i2p2www/pages/site/about/performance/future.html:153 #, python-format @@ -2017,10 +2241,13 @@ msgid "" "\n" "<a href=\"%(streaming)s#future\">streaming library page</a>." msgstr "" +"Des idées supplémentaires pour améliorer la bibliothèque de streaming " +"sont décrites sur la\n" +"<a href=\"%(streaming)s#future\">page de bibliothèque streaming</a>." #: i2p2www/pages/site/about/performance/history.html:2 msgid "Performance History" -msgstr "" +msgstr "Historique performance" #: i2p2www/pages/site/about/performance/history.html:4 #, python-format @@ -2031,10 +2258,15 @@ msgid "" "page\n" "for current issues and thoughts." msgstr "" +"Des améliorations notables de performance ont été faites en utilisant les" +" techniques ci-dessous.\n" +"Il y a plus pour faire, voir la page <a " +"href=\"%(performance)s\">performance</a>\n" +"pour les problèmes actuels et les pensées." #: i2p2www/pages/site/about/performance/history.html:10 msgid "Native math" -msgstr "" +msgstr "maths natales" #: i2p2www/pages/site/about/performance/history.html:11 #: i2p2www/pages/site/about/performance/history.html:67 @@ -2042,7 +2274,7 @@ msgstr "" #: i2p2www/pages/site/about/performance/history.html:105 #: i2p2www/pages/site/about/performance/history.html:133 msgid "implemented" -msgstr "" +msgstr "implémenté" #: i2p2www/pages/site/about/performance/history.html:12 #, python-format @@ -2057,6 +2289,17 @@ msgid "" "<a href=\"%(jbigi)s\">NativeBigInteger for faster public key " "cryptography</a></i>)" msgstr "" +"Quand j'ai dernièrement établi le profil du code d'I2P, la grande " +"majorité du temps a été passée dans\n" +"une fonction : java.math.BigInteger's\n" +"<a href=\"%(modpow)s\">modPow</a>.\n" +"Plutôt que d'essayer d'accorder cette méthode, nous ferons appel à \n" +"<a href=\"%(gmp)s\">GNU MP</a> - une bibliothèque mathématique follement " +"rapide\n" +"(avec assembleur accordé pour beaucoup d'architectures). (<i>éditeur : " +"voir\n" +"<a href=\"%(jbigi)s\">NativeBigInteger pour cryptographie clé publique " +"plus rapide</a></i>)" #: i2p2www/pages/site/about/performance/history.html:23 msgid "" @@ -2102,6 +2345,11 @@ msgid "" "I2PTunnel or\n" "mihi's ministreaming lib):" msgstr "" +"Ce tweak d'algorithme sera seulement approprié pour les applications qui " +"veulent que leurs\n" +"pairs leur répondent à elles (quoique cela inclue toutes les utilisations" +" de I2PTunnel ou\n" +"de Mihi's ministreaming lib) :" #: i2p2www/pages/site/about/performance/history.html:39 msgid "" @@ -2437,6 +2685,14 @@ msgid "" "I2P attempts to spread the load across a lot of I2P nodes because of this" " reason." msgstr "" +"Pour garder l'anonymat un routeur ne devrait pas être utilisé par " +"l'ensemble du réseau pour la construction de tunnels.\n" +"Si un routeur agit comme un routeur de tunnel pour tous les nÅ“uds de I2P," +" il devient un véritable point central de défaillance, ainsi qu'un point " +"central pour récolter des adresses IP et des données des clients. Ce " +"n'est pas bon.\n" +"I2P tente de répartir la charge sur un grand nombre de nÅ“uds I2P à cause " +"de cette raison." #: i2p2www/pages/site/about/performance/index.html:79 msgid "" @@ -2450,6 +2706,17 @@ msgid "" " type.\n" "This limits the amount of traffic routed across your I2P node as well." msgstr "" +"Un autre point est le réseau complètement maillé. Chaque connexion " +"saut-à -saut utilise une connexion TCP ou UDP sur les nÅ“uds I2P. Avec 1000" +" connexions, on voit\n" +"1000 connexions TCP. C'est beaucoup et certains routeurs (DSL, câble, " +"...) domestique ou de petit bureau permettent seulement un petit nombre " +"de connexions (ou deviennent simplement fous si vous utilisez plus de X " +"connexions.)\n" +"I2P essaie de limiter le nombre de ces connexions pour être en dessous de" +" 1500 par UDP et par type TCP.\n" +"Ce qui limite la quantité de trafic acheminé à travers votre nÅ“ud I2P " +"aussi." #: i2p2www/pages/site/about/performance/index.html:86 msgid "" diff --git a/i2p2www/translations/fr/LC_MESSAGES/blog.po b/i2p2www/translations/fr/LC_MESSAGES/blog.po index a29f680b5..8fcd687ce 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/blog.po +++ b/i2p2www/translations/fr/LC_MESSAGES/blog.po @@ -5,13 +5,14 @@ # Translators: # Boxoa590, 2013 # magma <magma@mail.i2p>, 2011 +# Towatowa441, 2013 msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" "POT-Creation-Date: 2013-09-30 21:40+0000\n" -"PO-Revision-Date: 2013-09-30 21:43+0000\n" -"Last-Translator: str4d <str4d@i2pmail.org>\n" +"PO-Revision-Date: 2013-10-10 21:41+0000\n" +"Last-Translator: Towatowa441\n" "Language-Team: French " "(http://www.transifex.com/projects/p/I2P/language/fr/)\n" "Plural-Forms: nplurals=2; plural=(n > 1)\n" @@ -133,15 +134,15 @@ msgstr "Sommes de contrôle SHA256 :" #: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39 msgid "Major changes" -msgstr "" +msgstr "Changements majeurs" #: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47 msgid "Wrapper Update" -msgstr "" +msgstr "Mise à jour du wrapper" #: i2p2www/blog/2012/05/02/0.9-Release.rst:23 msgid "Update Info" -msgstr "" +msgstr "Info de mise à jour" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2 msgid "0.9.2 Release" @@ -1088,11 +1089,11 @@ msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28 msgid "UPnP fix for some hardware" -msgstr "" +msgstr "Corrections UPnP pour certains matériels" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2 msgid "0.9.8 Release" -msgstr "" +msgstr "Sortie 0.9.8" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9 @@ -1103,6 +1104,12 @@ msgid "" "also have anonymity improvements including padding of SSU packets and " "longer router private keys." msgstr "" +"0.9.8 inclut le soutien pour IPV6 attendu depuis longtemps. Il est activé" +" par défaut, mais bien sûr vous avez besoin d'une adresse publique IPv6 " +"pour l'utiliser. La configuration est dans l'onglet de configuration " +"'réseau' de votre console. Nous avons aussi des améliorations d'anonymat " +"incluant le remplissage de paquets SSU et de plus longues clés privées de" +" routeur." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11 #, python-format @@ -1111,7 +1118,7 @@ msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13 msgid "IPv6 Details" -msgstr "" +msgstr "Détails IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15 msgid "" @@ -1123,6 +1130,14 @@ msgid "" " in \n" "the router console. If IPv6 is causing problems you may disable it there." msgstr "" +"IPv6 est activé et préféré par défaut. Si vous avez une adresse publique " +"IPv6\n" +"et que vous vous connectez à un autre routeur avec une adresse IPv6 " +"publiée, il sera\n" +"connecté via IPv6. Il y a une nouvelle section de configuration IPv6 sur " +"/confignet dans\n" +"la console de routeur. Si IPv6 cause des problèmes vous pouvez le mettre " +"hors de service là ." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22 msgid "" @@ -1194,10 +1209,14 @@ msgid "" "the \n" "network is still performing fairly well, so keep spreading the word." msgstr "" +"Nous éprouvons une croissance du réseau au cours des dernières semaines, " +"ce qui cause un peu cahoteux pour certains, particulièrement les week-" +"ends. Cependant, le réseau fonctionne toujours assez bien, donc continuez" +" à passer le mot." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69 msgid "More Changes Coming" -msgstr "" +msgstr "Changements majeurs à venir" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71 msgid "" @@ -1216,7 +1235,7 @@ msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81 msgid "New Website" -msgstr "" +msgstr "Nouveau site web" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83 msgid "" @@ -1226,10 +1245,15 @@ msgid "" "contribute to the new website translations on Transifex, especially the \n" "website_priority resource." msgstr "" +"Après un effort héroïque par str4d, la prévisualisation du nouveau site " +"Web est disponible à http: // i2hq.srv.i2p2.de. Nous espérons le voir " +"vivant à https: //geti2p.net et http://www.i2p2.i2p bientôt. S'il vous " +"plaît contribuez aux traductions d nouveau site Web sur Transifex, " +"particulièrement la ressource website_priority." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91 msgid "Community Participation" -msgstr "" +msgstr "Participation communauté" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93 msgid "" @@ -1240,42 +1264,56 @@ msgid "" "It's great to see people participating at these events and representing " "I2P." msgstr "" +"Début août, hottuna et zzz ont assisté au DEFCON 21 à Las Vegas. \n" +"Le dernier week-end, echelon a assisté à la conférence CTS IV à Berlin " +"et\n" +"psi a assisté au hackfest Tahoe-LAFS au GNOU 30 à Cambridge, Mass.\n" +"Plusieurs d'entre nous seront au 30C3 à Hambourg vers la fin de cette " +"année. \n" +"C'est super de voir des gens participer à ces événements et représenter " +"I2P." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105 msgid "IPv6 support for both NTCP and SSU" -msgstr "" +msgstr "Soutient IPv6 pour à la fois NTCP et SSU" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109 msgid "SSU protocol obfuscation by adding random padding" -msgstr "" +msgstr "Obscurcissement de protocole SSU par ajout de remplissage aléatoire" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110 msgid "Longer encryption and DH private keys for users on faster platforms" msgstr "" +"Chiffrage plus long et clés privées DH pour utilisateurs sur plates-" +"formes plus rapides" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114 msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)" -msgstr "" +msgstr "Répare I2PTunnel / verrouillage I2CP et duplicatas (partiel)" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115 msgid "Fix translation of HTTP proxy error pages" -msgstr "" +msgstr "Corrige les traductions des pages d'erreur de proxy HTTP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116 msgid "Fix occasional runtime exception in NTCP" -msgstr "" +msgstr "Répare une exception occasionnelle de runtime dans NTCP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120 msgid "Big rework of transport code to accommodate multiple addresses and IPv6" msgstr "" +"Grand re-travail du code de transport afin de s'accommoder des adresses " +"multiples et de IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121 msgid "Streaming: Improved recovery from lost acks, other fixes" -msgstr "" +msgstr "Streaming : rétablissement amélioré des acks perdus, d'autres corrections" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122 msgid "Use Transifex for translation of initial news and HTTP proxy error pages" msgstr "" +"Utilise Transifex pour la traduction des nouvelles initiales et des pages" +" d'erreur de proxy HTTP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123 msgid "" @@ -1285,9 +1323,9 @@ msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124 msgid "New Romanian translation" -msgstr "" +msgstr "Nouvelle traduction Roumaine" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126 msgid "Wrapper 3.5.20 (new installs and PPA only)" -msgstr "" +msgstr "Wrapper 3.5.20 (nouvelles installations et PPA seulement)" diff --git a/i2p2www/translations/fr/LC_MESSAGES/docs.po b/i2p2www/translations/fr/LC_MESSAGES/docs.po index ce827b915..27d0cf12e 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/docs.po +++ b/i2p2www/translations/fr/LC_MESSAGES/docs.po @@ -11,7 +11,7 @@ msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" "POT-Creation-Date: 2013-09-30 21:40+0000\n" -"PO-Revision-Date: 2013-10-03 09:11+0000\n" +"PO-Revision-Date: 2013-10-26 08:36+0000\n" "Last-Translator: Towatowa441\n" "Language-Team: French " "(http://www.transifex.com/projects/p/I2P/language/fr/)\n" @@ -23,7 +23,7 @@ msgstr "" #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:25 msgid "Index to Technical Documentation" -msgstr "" +msgstr "Index de la documentation technique" #: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3 #: i2p2www/pages/site/docs/spec/datagrams.html:3 @@ -38,7 +38,7 @@ msgstr "Comment fonctionne I2P" #: i2p2www/pages/site/docs/index.html:8 msgid "Following is an index to the technical documentation for I2P." -msgstr "" +msgstr "Ce qui suit est un index de la documentation technique pour I2P." #: i2p2www/pages/site/docs/index.html:12 msgid "" @@ -120,7 +120,7 @@ msgstr "" #: i2p2www/pages/site/docs/index.html:38 msgid "Application-Layer Topics" -msgstr "" +msgstr "Sujets couche d'application" #: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2 msgid "Naming and Addressbook" @@ -132,11 +132,11 @@ msgstr "Aperçu des plugins" #: i2p2www/pages/site/docs/index.html:43 msgid "Plugin Specification" -msgstr "" +msgstr "Specification Plugin" #: i2p2www/pages/site/docs/index.html:44 msgid "Router software updates" -msgstr "" +msgstr "Mises à jour de logiciel routeur" #: i2p2www/pages/site/docs/index.html:45 #: i2p2www/pages/site/docs/applications/bittorrent.html:2 @@ -145,29 +145,31 @@ msgstr "Bittorrent par-dessus I2P" #: i2p2www/pages/site/docs/index.html:46 msgid "I2PControl Plugin API" -msgstr "" +msgstr "API plugin I2PControl" #: i2p2www/pages/site/docs/index.html:47 msgid "hostsdb.blockfile Format" -msgstr "" +msgstr "Format hostsdb.blockfile" #: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:185 msgid "Configuration File Format" -msgstr "" +msgstr "Format de fichier de configuration" #: i2p2www/pages/site/docs/index.html:51 msgid "Application Layer API and Protocols" -msgstr "" +msgstr "Couche d'application : API et protocoles" #: i2p2www/pages/site/docs/index.html:52 msgid "" "High-level, easy-to-use APIs for applications written in any language to " "send and receive data." msgstr "" +"Des API de haut niveau, faciles à utiliser pour des applications écrites " +"dans n'importe quelle langue pour envoyer et recevoir des données." #: i2p2www/pages/site/docs/index.html:54 msgid "Application Development Overview and Guide" -msgstr "" +msgstr "Vue d'ensemble et guide de développement d'application" #: i2p2www/pages/site/docs/index.html:72 msgid "SAM Protocol" @@ -187,22 +189,24 @@ msgstr "Protocole BOB" #: i2p2www/pages/site/docs/index.html:81 msgid "End-to-End Transport API and Protocols" -msgstr "" +msgstr "API et protocoles de transport de bout en bout " #: i2p2www/pages/site/docs/index.html:82 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." msgstr "" +"Les protocoles de bout en bout utilisés par les clients pour des " +"communications fiables et non fiables." #: i2p2www/pages/site/docs/index.html:84 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" -msgstr "" +msgstr "Bibliothèque streaming" #: i2p2www/pages/site/docs/index.html:86 msgid "Streaming Javadoc" -msgstr "" +msgstr "Javadoc streaming" #: i2p2www/pages/site/docs/index.html:88 #: i2p2www/pages/site/docs/api/datagrams.html:2 @@ -211,7 +215,7 @@ msgstr "Datagrammes" #: i2p2www/pages/site/docs/index.html:90 msgid "Datagram Javadoc" -msgstr "" +msgstr "Javadoc datagramme" #: i2p2www/pages/site/docs/index.html:93 msgid "Client-to-Router Interface API and Protocol" diff --git a/i2p2www/translations/pt/LC_MESSAGES/priority.po b/i2p2www/translations/pt/LC_MESSAGES/priority.po index b4bf6b4be..9ca38cb45 100644 --- a/i2p2www/translations/pt/LC_MESSAGES/priority.po +++ b/i2p2www/translations/pt/LC_MESSAGES/priority.po @@ -12,8 +12,8 @@ msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" "POT-Creation-Date: 2013-09-30 21:40+0000\n" -"PO-Revision-Date: 2013-10-08 01:25+0000\n" -"Last-Translator: Danton Medrado\n" +"PO-Revision-Date: 2013-10-25 18:41+0000\n" +"Last-Translator: hxdcmls\n" "Language-Team: Portuguese " "(http://www.transifex.com/projects/p/I2P/language/pt/)\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" @@ -43,7 +43,7 @@ msgstr "Feed ATOM do blog do I2P" #: i2p2www/pages/blog/index.html:17 #, python-format msgid "Posted %(date)s by %(author)s" -msgstr "" +msgstr "Postado %(date)s por %(author)s" #: i2p2www/pages/blog/latest.html:5 msgid "More blog posts…" @@ -817,6 +817,9 @@ msgid "" "donation</a>, \n" "marking the amount for the %(donatename)s bounty!" msgstr "" +"O valor dos prêmios pode ser aumentado por mais doações. Acreditas que " +"esses são importantes? <a href=\"%(donate)s\">Inclua sua doação</a>, " +"marcando o valor para o prêmio do %(donatename)s!" #: i2p2www/pages/global/error_404.html:3 msgid "Not found" @@ -963,15 +966,15 @@ msgstr "Introdução técnica" #: i2p2www/pages/global/nav.html:23 msgid "Threat model" -msgstr "" +msgstr "Modelo da ameaça" #: i2p2www/pages/global/nav.html:24 msgid "Garlic routing" -msgstr "" +msgstr "Roteador de cebola" #: i2p2www/pages/global/nav.html:25 msgid "Network database" -msgstr "" +msgstr "Banco de dados da rede" #: i2p2www/pages/global/nav.html:26 msgid "Tunnel routing" @@ -1027,7 +1030,7 @@ msgstr "" #: i2p2www/pages/global/nav.html:59 msgid "Transports" -msgstr "" +msgstr "Transportes" #: i2p2www/pages/global/nav.html:61 msgid "Transport layer overview" @@ -1047,7 +1050,7 @@ msgstr "" #: i2p2www/pages/global/nav.html:70 msgid "Configuration files" -msgstr "" +msgstr "Arquivos de configuração" #: i2p2www/pages/global/nav.html:72 msgid "GeoIP files" @@ -1067,7 +1070,7 @@ msgstr "" #: i2p2www/pages/global/nav.html:80 msgid "Software updates" -msgstr "" +msgstr "Atualizações de programas" #: i2p2www/pages/global/nav.html:83 msgid "Tunnels" @@ -1167,7 +1170,7 @@ msgstr "" #: i2p2www/pages/global/nav.html:124 msgid "Academic research" -msgstr "" +msgstr "Pesquisa acadêmica" #: i2p2www/pages/global/nav.html:125 msgid "Guides" @@ -1284,7 +1287,7 @@ msgstr "" #: i2p2www/pages/site/contact.html:13 msgid "Channel list:" -msgstr "" +msgstr "Lista de canais:" #: i2p2www/pages/site/contact.html:15 msgid "General i2p discussion" @@ -1323,7 +1326,7 @@ msgstr "" #: i2p2www/pages/site/contact.html:33 msgid "Subscribing" -msgstr "" +msgstr "Inscrevendo" #: i2p2www/pages/site/contact.html:34 msgid "" @@ -1331,10 +1334,13 @@ msgid "" "below) and fill out the form. I2P-internal email addresses " "(foobar@mail.i2p) can be used." msgstr "" +"Para se inscrever-se em uma lista de discussão, acesse a página de " +"informações da lista (link abaixo) e preencha o formulário. Endereços " +"I2P-internos (foobar@mail.i2p) podem ser usados." #: i2p2www/pages/site/contact.html:38 msgid "Unsubscribing" -msgstr "" +msgstr "Cancelando inscrição" #: i2p2www/pages/site/contact.html:39 msgid "" @@ -1342,6 +1348,9 @@ msgid "" "to the list information page (linked below) and enter your subscription " "email address." msgstr "" +"Para cancelar a inscrição a partir de uma lista de discussão ou editar as" +" suas opções de inscrição, acesse a página de informações da lista (link " +"abaixo) e digite o seu endereço de email de inscrição." #: i2p2www/pages/site/contact.html:43 msgid "Lists" @@ -1356,12 +1365,16 @@ msgid "" "General I2P discussion - anything that doesn't fit in a different list " "goes here." msgstr "" +"Discussão geral I2P - qualquer coisa que não se encaixa em uma lista " +"diferente vai aqui." #: i2p2www/pages/site/contact.html:53 msgid "" "You don't like mailing lists? Then this is for you. All mailing lists are" " available via NNTP as well." msgstr "" +"Você não gosta de listas de discussão? Então isto é para você. Todas as " +"listas de discussão estão disponÃveis via NNTP tranquilamente." #: i2p2www/pages/site/contact.html:58 msgid "Group-List-mapping:" @@ -1373,7 +1386,7 @@ msgstr "Servidores:" #: i2p2www/pages/site/faq.html:2 msgid "Frequently Asked Questions" -msgstr "" +msgstr "Perguntas Mais Frequentes" #: i2p2www/pages/site/faq.html:4 msgid "Index" @@ -1385,7 +1398,7 @@ msgstr "Geral" #: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51 msgid "What systems will I2P run on?" -msgstr "" +msgstr "Quais sistemas I2P serão executados?" #: i2p2www/pages/site/faq.html:10 msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?" @@ -1407,7 +1420,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:348 msgid "Is using an outproxy safe?" -msgstr "" +msgstr "Está usando um outproxy seguro?" #: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:374 msgid "Most of the eepsites within I2P are down?" @@ -1431,7 +1444,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:845 msgid "I have a question!" -msgstr "" +msgstr "Eu tenho uma pergunta!" #: i2p2www/pages/site/faq.html:22 msgid "Setup" @@ -2050,6 +2063,8 @@ msgid "" "See the\n" "<a href=\"http://%(forum)s/viewtopic.php?t=2068\">I2P Bittorrent FAQ</a>" msgstr "" +"Veja oâŽ\n" +"<a href=\"http://%(forum)s/viewtopic.php?t=2068\">I2P Bittorrent FAQ</a>" #: i2p2www/pages/site/faq.html:425 msgid "" @@ -2602,7 +2617,7 @@ msgstr "" #: i2p2www/pages/site/index.html:7 msgid "What does I2P do for you?" -msgstr "" +msgstr "O que o I2P faz por você?" #: i2p2www/pages/site/index.html:8 msgid "" @@ -2610,6 +2625,9 @@ msgid "" "over the Internet. Many activities that would risk your privacy on the " "public Internet can be conducted anonymously inside I2P." msgstr "" +"A rede I2P fornece fortes proteções de privacidade para a comunicação " +"através da Internet. Muitas atividades que arriscam a sua privacidade na " +"Internet pública pode ser realizada de forma anônima dentro I2P." #: i2p2www/pages/site/index.html:9 #, python-format @@ -2654,7 +2672,7 @@ msgstr "" #: i2p2www/pages/site/index.html:33 msgid "What can you do with I2P?" -msgstr "" +msgstr "O que você pode fazer com o I2P?" #: i2p2www/pages/site/index.html:36 #, python-format diff --git a/i2p2www/translations/ru_RU/LC_MESSAGES/about.po b/i2p2www/translations/ru_RU/LC_MESSAGES/about.po new file mode 100644 index 000000000..b2b5a5138 --- /dev/null +++ b/i2p2www/translations/ru_RU/LC_MESSAGES/about.po @@ -0,0 +1,2512 @@ +# Russian (Russia) translations for I2P. +# Copyright (C) 2013 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# IOException <opexob@yandex.ru>, 2013 +# Millennium <u235xc@gmail.com>, 2013 +# keedley <zhopa@mita.pp.ru>, 2013 +# sassy <sassy.but.classic@gmail.com>, 2013 +# Narengoyn <narengoyn@gmail.com>, 2013 +# TrackIt <Terexnik@gmail.com>, 2013 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" +"POT-Creation-Date: 2013-09-01 03:42+0000\n" +"PO-Revision-Date: 2013-10-25 16:04+0000\n" +"Last-Translator: sassy <sassy.but.classic@gmail.com>\n" +"Language-Team: Russian (Russia) " +"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 0.9.6\n" + +#: i2p2www/pages/site/about/browser-config.html:2 +msgid "Web Browser Configuration" +msgstr "ÐšÐ¾Ð½Ñ„Ð¸Ð³ÑƒÑ€Ð°Ñ†Ð¸Ñ Ð²ÐµÐ±-браузера" + +#: i2p2www/pages/site/about/browser-config.html:5 +msgid "" +"Your web browser will need to be configured in order to browse eepsites " +"and to\n" +"utilize the outproxies available within I2P. Below are walkthroughs for " +"some of\n" +"the most popular browsers." +msgstr "" +"Ваш браузер нужно наÑтроить, чтобы вы могли пользоватьÑÑ eep-Ñайтами и\n" +"другими I2P-ÑервиÑами. Ðиже опиÑаны шаги длÑ\n" +"наиболее популÑрных браузеров." + +#: i2p2www/pages/site/about/browser-config.html:11 +msgid "How to configure your browser" +msgstr "Как наÑтроить ваш браузер" + +#: i2p2www/pages/site/about/browser-config.html:17 +#: i2p2www/pages/site/about/browser-config.html:73 +msgid "Outproxy Terms Of Service" +msgstr "Правила Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Outproxy" + +#: i2p2www/pages/site/about/browser-config.html:22 +msgid "Internet Explorer 8 or Chrome" +msgstr "Internet Explorer 8 или Chrome" + +#: i2p2www/pages/site/about/browser-config.html:23 +msgid "" +"In the tools menu select the \"Internet Options\" line to open the " +"settings. In the\n" +"settings window choose the connections tab and click on LAN settings for " +"the\n" +"proxy port configuration." +msgstr "" +"Чтобы открыть наÑтройки, в меню ИнÑтрументы выберите \"ÐаÑтройки " +"Интернет\". Ð’\n" +"окне наÑтроек перейдите к вкладке параметров ÑÐ¾ÐµÐ´Ð¸Ð½ÐµÐ½Ð¸Ñ Ð¸ щелкните по " +"наÑтройкам Ñети(LAN) длÑ\n" +"конфигурации порта прокÑи-Ñервера." + +#: i2p2www/pages/site/about/browser-config.html:28 +msgid "IE Internet Options" +msgstr "ÐаÑтройки Интернет в IE" + +#: i2p2www/pages/site/about/browser-config.html:29 +msgid "" +"Now set the checkmark at \"use a proxy server for your LAN\" and at the " +"\"Bypass\n" +"proxy server for local addresses\". With a click on Advanced-button you " +"open the\n" +"window to open the ports. Enter the values like on the picture, IP " +"127.0.0.1\n" +"and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save " +"the\n" +"settings and your browser is set to use the I2P proxy." +msgstr "" +"Теперь уÑтановите флажок \"ИÑпользовать прокÑи-Ñервер Ð´Ð»Ñ Ð»Ð¾ÐºÐ°Ð»ÑŒÐ½Ñ‹Ñ… " +"подключений\" а так же флажок \"Ðе иÑпользовать прокÑи-Ñервер Ð´Ð»Ñ " +"локальных адреÑов\". По нажатии кнопки Дополнительно открываетÑÑ Ð¾ÐºÐ½Ð¾ " +"наÑтроек прокÑи-Ñервера. Заполните Ð¿Ð¾Ð»Ñ ÐºÐ°Ðº показано на картинке, Ð°Ð´Ñ€ÐµÑ " +"прокÑи-Ñервера 127.0.0.1 и порт 4444 Ð´Ð»Ñ HTTP, порт 4445 Ð´Ð»Ñ HTTPS. Ðажав" +" кнопку OK вы Ñохраните наÑтройки тем Ñамым подготовив браузер Ð´Ð»Ñ " +"иÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ I2P прокÑи-Ñервера." + +#: i2p2www/pages/site/about/browser-config.html:36 +msgid "IE Proxy Settings" +msgstr "ÐаÑтройки прокÑи-Ñервера в IE" + +#: i2p2www/pages/site/about/browser-config.html:40 +msgid "" +"From the Tools menu, select Options to bring up the Firefox settings " +"panel.\n" +"Click the icon labelled <em>Advanced</em>, then click on the " +"<em>Network</em>\n" +"tab. In the <em>Connections</em> section, click on the Settings button. " +"You'll\n" +"see a Window like the following:" +msgstr "" +"Ð’ меню ÐаÑтройки, выберите пункт Опции, что бы открыть панель наÑтроек " +"Firefox. Ðажмите на иконку Ñ Ð½Ð°Ð·Ð²Ð°Ð½Ð¸ÐµÐ¼ <em>Дополнительно</em>, затем " +"нажмите на закладку <em>Сеть</em>. Ð’ Ñекции <em>Соединение</em>, нажмите " +"кнопку ÐаÑтройки. Ð’Ñ‹ увидите окно как показано ниже:" + +#: i2p2www/pages/site/about/browser-config.html:46 +msgid "Firefox Network Options" +msgstr "Firefox Ñетевые опции" + +#: i2p2www/pages/site/about/browser-config.html:47 +msgid "" +"In the <em>Connection Settings</em> window, click the circle next to " +"<em>Manual\n" +" proxy configuration</em>, then enter 127.0.0.1, port 4444 in the HTTP" +" Proxy\n" +"field. Enter 127.0.0.1, port 4445 in the SSL Proxy field.\n" +"Be sure to enter localhost and 127.0.0.1 into the \"No Proxy for\" box." +msgstr "" +"Ð’ окне <em>Параметры ÑоединениÑ</em> кликните кружок Ñ€Ñдом Ñ <em>РучнаÑ\n" +"наÑтройка ÑервиÑа прокÑи</em>, затем введите 127.0.0.1, порт 4444 в поле " +"HTTP\n" +"прокÑи. Введите 127.0.0.1, порт 4445 в поле SSL прокÑи.\n" +"УбедитеÑÑŒ, что ввели localhost и 127.0.0.1 в поле \"Ðе иÑпользовать " +"прокÑи длÑ\"." + +#: i2p2www/pages/site/about/browser-config.html:53 +msgid "Firefox Proxy Settings" +msgstr "ÐаÑтройки прокÑи Ð´Ð»Ñ Firefox" + +#: i2p2www/pages/site/about/browser-config.html:57 +msgid "" +"From the <em>Settings</em> menu, select <em>Configure Konqueror</em>. In " +"the\n" +"Web Browsing group on the left side, select Proxy Services.\n" +"In this new window, select the option \"Manually specify the proxy " +"settings\" and\n" +"click the <em>Setup</em> box." +msgstr "" +"Ð’ меню <em>Settings</em>, выберите <em>Configure Konqueror</em>. Ð’ группе" +"\n" +"Web Browsing левой чаÑти окна, выберите Proxy Services.\n" +"Ð’ поÑвившемÑÑ Ð¾ÐºÐ½Ðµ, выберите опцию \"Manually specify the proxy " +"settings\" и\n" +"нажмите кнопку <em>Setup</em>." + +#: i2p2www/pages/site/about/browser-config.html:63 +msgid "Konqueror Proxy Options" +msgstr "ÐаÑтройки прокÑи Ð´Ð»Ñ Konqueror" + +#: i2p2www/pages/site/about/browser-config.html:64 +msgid "" +"Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port" +" 4445 into\n" +"HTTPS box. Click the <em>New</em> button in the Exceptions section. Enter" +"\n" +"localhost and click OK. Click the <em>New</em> button once more and enter" +"\n" +"127.0.0.1 and OK. Hit OK once more to close the configuration window." +msgstr "" +"Введите 127.0.0.1 и порт 4444 в ÑоответÑтвующих полÑÑ… HTTP. Введите " +"127.0.0.1 и порт 4445 в ÑоответÑтвующих полÑÑ… HTTPS.\n" +"Ðажмите кнопку <em>New</em> в Ñекции Exceptions. Введите\n" +"localhost и нажмите OK. Ðажмите кнопку <em>New</em> ещё раз и введите\n" +"127.0.0.1 и нажмите OK. Ðажмите OK ещё раз, что бы закрыть окно наÑтроек." + +#: i2p2www/pages/site/about/browser-config.html:70 +msgid "Konqueror Proxy Ports" +msgstr "Konqueror порты прокÑи" + +#: i2p2www/pages/site/about/browser-config.html:74 +msgid "" +"Remember: I2P was not designed for creating proxies to the outer " +"Internet.\n" +"Instead, it is meant to be used as an internal network." +msgstr "" +"Помните: I2P не был Ñпроектирован Ð´Ð»Ñ ÑÐ¾Ð·Ð´Ð°Ð½Ð¸Ñ Ð¿Ñ€Ð¾ÐºÑи во внешний " +"интернет.\n" +"ВмеÑто Ñтого I2P предназначена Ð´Ð»Ñ Ð¸ÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ð² качеÑтве внутренней " +"Ñети." + +#: i2p2www/pages/site/about/browser-config.html:78 +msgid "" +"<b>The I2P project itself does not run any proxies to the Internet. Any " +"such proxy\n" +"services are run by by private volunteers and could be shut down or\n" +"unreachable at anytime.</b>" +msgstr "" +"<b>Проект I2P Ñам по Ñебе не запуÑкает никаких прокÑи в интернет. Любые\n" +"такие прокÑи-ÑервиÑÑ‹ управлÑÑŽÑ‚ÑÑ Ð´Ð¾Ð±Ñ€Ð¾Ð²Ð¾Ð»ÑŒÑ†Ð°Ð¼Ð¸ и могут отключитьÑÑ Ð¸Ð»Ð¸\n" +"Ñтать недоÑтупными в любой момент.</b>" + +#: i2p2www/pages/site/about/browser-config.html:83 +#, python-format +msgid "" +"By default, I2P comes with two outproxies configured: " +"<code>%(http)s</code>\n" +"(an HTTP-only proxy) and <code>%(https)s</code> (an HTTPS proxy\n" +"routed through Tor." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:88 +msgid "" +"Both of these outproxies are configured with connection limits. This " +"means\n" +"that only set amount of accesses are allowed per client. Once the limit " +"is\n" +"reached, the client is blocked out for a timeframe of 1min/1h/1 day. Be\n" +"respectful and do not overload these services with too many requests!" +msgstr "" +"Оба Ñти аутпрокÑи наÑтроены Ñ Ð¾Ð³Ñ€Ð°Ð½Ð¸Ñ‡ÐµÐ½Ð¸Ñми ÑоединениÑ. Ðто значит,\n" +"что только определённое количеÑтво доÑтупов разрешено Ð´Ð»Ñ ÐºÐ°Ð¶Ð´Ð¾Ð³Ð¾ " +"клиента. \n" +"Как только лимит иÑчерпан, клиент блокируетÑÑ Ð½Ð° Ñрок в 1 минуту/1чаÑ/1 " +"день.\n" +"Будьте вежливы и не перегружайте Ñти ÑервиÑÑ‹ Ñлишком многими запроÑами!" + +#: i2p2www/pages/site/about/browser-config.html:94 +msgid "" +"Filtering is active on these outproxies (for example, mibbit and torrent\n" +"tracker access is blocked). Eepsites\n" +"that are accessible via .i2p addresses are also not allowed via the " +"outproxies.\n" +"As a convenience, <code>false.i2p</code> blocks ad servers." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:100 +msgid "" +"<a href=\"https://www.torproject.org\">Tor</a> is good application to use" +" as an\n" +"outproxy to the Internet." +msgstr "" +"<a href=\"https://www.torproject.org\">Tor</a> - Ñто хорошее приложение " +"длÑ\n" +"иÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ ÐµÐ³Ð¾ как аутпрокÑи в интернет. " + +#: i2p2www/pages/site/about/glossary.html:2 +msgid "Glossary" +msgstr "Словарь." + +#: i2p2www/pages/site/about/glossary.html:4 +msgid "" +"This page lists often-used terminology when discussing I2P and " +"cryptography." +msgstr "" +"Ðа Ñтой Ñтранице перечиÑлены термины, чаÑто иÑпользуемые при обÑуждении " +"I2P и криптографии." + +#: i2p2www/pages/site/about/hall-of-fame.html:2 +msgid "Hall Of Fame" +msgstr "Зал Славы" + +#: i2p2www/pages/site/about/hall-of-fame.html:5 +msgid "I2P'<small>s</small> Hall of Fame" +msgstr "Зал Славы I2P" + +#: i2p2www/pages/site/about/hall-of-fame.html:6 +#, python-format +msgid "Current balance: as of %(date)s" +msgstr "Текущий баланÑ: по ÑоÑтоÑнию на %(date)s" + +#: i2p2www/pages/site/about/hall-of-fame.html:9 +#: i2p2www/pages/site/about/hall-of-fame.html:47 +#: i2p2www/pages/site/about/hall-of-fame.html:173 +#: i2p2www/pages/site/about/hall-of-fame.html:174 +#: i2p2www/pages/site/about/hall-of-fame.html:175 +#: i2p2www/pages/site/about/hall-of-fame.html:176 +#: i2p2www/pages/site/about/hall-of-fame.html:178 +#: i2p2www/pages/site/about/hall-of-fame.html:179 +#: i2p2www/pages/site/about/hall-of-fame.html:180 +#: i2p2www/pages/site/about/hall-of-fame.html:183 +#: i2p2www/pages/site/about/hall-of-fame.html:184 +#: i2p2www/pages/site/about/hall-of-fame.html:185 +#: i2p2www/pages/site/about/hall-of-fame.html:188 +#: i2p2www/pages/site/about/hall-of-fame.html:189 +#: i2p2www/pages/site/about/hall-of-fame.html:190 +#: i2p2www/pages/site/about/hall-of-fame.html:191 +#: i2p2www/pages/site/about/hall-of-fame.html:192 +#: i2p2www/pages/site/about/hall-of-fame.html:193 +#: i2p2www/pages/site/about/hall-of-fame.html:194 +#: i2p2www/pages/site/about/hall-of-fame.html:195 +#: i2p2www/pages/site/about/hall-of-fame.html:196 +#: i2p2www/pages/site/about/hall-of-fame.html:197 +#: i2p2www/pages/site/about/hall-of-fame.html:198 +#: i2p2www/pages/site/about/hall-of-fame.html:199 +#: i2p2www/pages/site/about/hall-of-fame.html:200 +#: i2p2www/pages/site/about/hall-of-fame.html:203 +#: i2p2www/pages/site/about/hall-of-fame.html:204 +#: i2p2www/pages/site/about/hall-of-fame.html:205 +#: i2p2www/pages/site/about/hall-of-fame.html:206 +#: i2p2www/pages/site/about/hall-of-fame.html:207 +#: i2p2www/pages/site/about/hall-of-fame.html:208 +#: i2p2www/pages/site/about/hall-of-fame.html:210 +#: i2p2www/pages/site/about/hall-of-fame.html:211 +#: i2p2www/pages/site/about/hall-of-fame.html:214 +#: i2p2www/pages/site/about/hall-of-fame.html:215 +#: i2p2www/pages/site/about/hall-of-fame.html:216 +#: i2p2www/pages/site/about/hall-of-fame.html:217 +#: i2p2www/pages/site/about/hall-of-fame.html:218 +#: i2p2www/pages/site/about/hall-of-fame.html:220 +#: i2p2www/pages/site/about/hall-of-fame.html:221 +#: i2p2www/pages/site/about/hall-of-fame.html:222 +#: i2p2www/pages/site/about/hall-of-fame.html:223 +#: i2p2www/pages/site/about/hall-of-fame.html:224 +#: i2p2www/pages/site/about/hall-of-fame.html:225 +#: i2p2www/pages/site/about/hall-of-fame.html:227 +#: i2p2www/pages/site/about/hall-of-fame.html:228 +#: i2p2www/pages/site/about/hall-of-fame.html:229 +#: i2p2www/pages/site/about/hall-of-fame.html:230 +#: i2p2www/pages/site/about/hall-of-fame.html:232 +#: i2p2www/pages/site/about/hall-of-fame.html:233 +#: i2p2www/pages/site/about/hall-of-fame.html:234 +#: i2p2www/pages/site/about/hall-of-fame.html:235 +#: i2p2www/pages/site/about/hall-of-fame.html:236 +#: i2p2www/pages/site/about/hall-of-fame.html:239 +#: i2p2www/pages/site/about/hall-of-fame.html:240 +#: i2p2www/pages/site/about/hall-of-fame.html:241 +#: i2p2www/pages/site/about/hall-of-fame.html:242 +#: i2p2www/pages/site/about/hall-of-fame.html:244 +#: i2p2www/pages/site/about/hall-of-fame.html:245 +#: i2p2www/pages/site/about/hall-of-fame.html:246 +#: i2p2www/pages/site/about/hall-of-fame.html:248 +#: i2p2www/pages/site/about/hall-of-fame.html:249 +#: i2p2www/pages/site/about/hall-of-fame.html:250 +#: i2p2www/pages/site/about/hall-of-fame.html:251 +#: i2p2www/pages/site/about/hall-of-fame.html:253 +#: i2p2www/pages/site/about/hall-of-fame.html:254 +#: i2p2www/pages/site/about/hall-of-fame.html:255 +#: i2p2www/pages/site/about/hall-of-fame.html:256 +#: i2p2www/pages/site/about/hall-of-fame.html:257 +#: i2p2www/pages/site/about/hall-of-fame.html:263 +#: i2p2www/pages/site/about/hall-of-fame.html:266 +#: i2p2www/pages/site/about/hall-of-fame.html:267 +#: i2p2www/pages/site/about/hall-of-fame.html:268 +#: i2p2www/pages/site/about/hall-of-fame.html:269 +#: i2p2www/pages/site/about/hall-of-fame.html:270 +#: i2p2www/pages/site/about/hall-of-fame.html:272 +#: i2p2www/pages/site/about/hall-of-fame.html:273 +#: i2p2www/pages/site/about/hall-of-fame.html:274 +#: i2p2www/pages/site/about/hall-of-fame.html:279 +#: i2p2www/pages/site/about/hall-of-fame.html:280 +#: i2p2www/pages/site/about/hall-of-fame.html:281 +#: i2p2www/pages/site/about/hall-of-fame.html:282 +#: i2p2www/pages/site/about/hall-of-fame.html:283 +#: i2p2www/pages/site/about/hall-of-fame.html:284 +#: i2p2www/pages/site/about/hall-of-fame.html:285 +#: i2p2www/pages/site/about/hall-of-fame.html:286 +#: i2p2www/pages/site/about/hall-of-fame.html:287 +#: i2p2www/pages/site/about/hall-of-fame.html:288 +#: i2p2www/pages/site/about/hall-of-fame.html:290 +#: i2p2www/pages/site/about/hall-of-fame.html:291 +#: i2p2www/pages/site/about/hall-of-fame.html:301 +#: i2p2www/pages/site/about/hall-of-fame.html:302 +#: i2p2www/pages/site/about/hall-of-fame.html:303 +#: i2p2www/pages/site/about/hall-of-fame.html:304 +#: i2p2www/pages/site/about/hall-of-fame.html:305 +#: i2p2www/pages/site/about/hall-of-fame.html:306 +#: i2p2www/pages/site/about/hall-of-fame.html:307 +#: i2p2www/pages/site/about/hall-of-fame.html:308 +#: i2p2www/pages/site/about/hall-of-fame.html:309 +#: i2p2www/pages/site/about/hall-of-fame.html:310 +#: i2p2www/pages/site/about/hall-of-fame.html:311 +#: i2p2www/pages/site/about/hall-of-fame.html:312 +#: i2p2www/pages/site/about/hall-of-fame.html:313 +#: i2p2www/pages/site/about/hall-of-fame.html:314 +#: i2p2www/pages/site/about/hall-of-fame.html:315 +#: i2p2www/pages/site/about/hall-of-fame.html:316 +#: i2p2www/pages/site/about/hall-of-fame.html:317 +#: i2p2www/pages/site/about/hall-of-fame.html:318 +#: i2p2www/pages/site/about/hall-of-fame.html:319 +#: i2p2www/pages/site/about/hall-of-fame.html:320 +#: i2p2www/pages/site/about/hall-of-fame.html:321 +#: i2p2www/pages/site/about/hall-of-fame.html:325 +#: i2p2www/pages/site/about/hall-of-fame.html:326 +#: i2p2www/pages/site/about/hall-of-fame.html:327 +#: i2p2www/pages/site/about/hall-of-fame.html:328 +#: i2p2www/pages/site/about/hall-of-fame.html:329 +#: i2p2www/pages/site/about/hall-of-fame.html:330 +#: i2p2www/pages/site/about/hall-of-fame.html:331 +#: i2p2www/pages/site/about/hall-of-fame.html:333 +#: i2p2www/pages/site/about/hall-of-fame.html:334 +#: i2p2www/pages/site/about/hall-of-fame.html:335 +#: i2p2www/pages/site/about/hall-of-fame.html:336 +#: i2p2www/pages/site/about/hall-of-fame.html:337 +#: i2p2www/pages/site/about/hall-of-fame.html:338 +#: i2p2www/pages/site/about/hall-of-fame.html:339 +#: i2p2www/pages/site/about/hall-of-fame.html:340 +#: i2p2www/pages/site/about/hall-of-fame.html:341 +#: i2p2www/pages/site/about/hall-of-fame.html:344 +#: i2p2www/pages/site/about/hall-of-fame.html:345 +#: i2p2www/pages/site/about/hall-of-fame.html:346 +#: i2p2www/pages/site/about/hall-of-fame.html:347 +#: i2p2www/pages/site/about/hall-of-fame.html:348 +#: i2p2www/pages/site/about/hall-of-fame.html:350 +#: i2p2www/pages/site/about/hall-of-fame.html:352 +#: i2p2www/pages/site/about/hall-of-fame.html:353 +#: i2p2www/pages/site/about/hall-of-fame.html:354 +#: i2p2www/pages/site/about/hall-of-fame.html:355 +#: i2p2www/pages/site/about/hall-of-fame.html:356 +#: i2p2www/pages/site/about/hall-of-fame.html:357 +#: i2p2www/pages/site/about/hall-of-fame.html:358 +#: i2p2www/pages/site/about/hall-of-fame.html:360 +#: i2p2www/pages/site/about/hall-of-fame.html:361 +#: i2p2www/pages/site/about/hall-of-fame.html:362 +#: i2p2www/pages/site/about/hall-of-fame.html:363 +#: i2p2www/pages/site/about/hall-of-fame.html:364 +#: i2p2www/pages/site/about/hall-of-fame.html:365 +#: i2p2www/pages/site/about/hall-of-fame.html:366 +#: i2p2www/pages/site/about/hall-of-fame.html:367 +#: i2p2www/pages/site/about/hall-of-fame.html:368 +#: i2p2www/pages/site/about/hall-of-fame.html:369 +#: i2p2www/pages/site/about/hall-of-fame.html:370 +#: i2p2www/pages/site/about/hall-of-fame.html:371 +#: i2p2www/pages/site/about/hall-of-fame.html:372 +#: i2p2www/pages/site/about/hall-of-fame.html:373 +#: i2p2www/pages/site/about/hall-of-fame.html:375 +#: i2p2www/pages/site/about/hall-of-fame.html:376 +#: i2p2www/pages/site/about/hall-of-fame.html:377 +#: i2p2www/pages/site/about/hall-of-fame.html:380 +#: i2p2www/pages/site/about/hall-of-fame.html:381 +#: i2p2www/pages/site/about/hall-of-fame.html:384 +#: i2p2www/pages/site/about/hall-of-fame.html:385 +#: i2p2www/pages/site/about/hall-of-fame.html:387 +#: i2p2www/pages/site/about/hall-of-fame.html:388 +#: i2p2www/pages/site/about/hall-of-fame.html:401 +#: i2p2www/pages/site/about/hall-of-fame.html:402 +#: i2p2www/pages/site/about/hall-of-fame.html:403 +#: i2p2www/pages/site/about/hall-of-fame.html:404 +#: i2p2www/pages/site/about/hall-of-fame.html:405 +#: i2p2www/pages/site/about/hall-of-fame.html:406 +#: i2p2www/pages/site/about/hall-of-fame.html:407 +#: i2p2www/pages/site/about/hall-of-fame.html:408 +#: i2p2www/pages/site/about/hall-of-fame.html:409 +#: i2p2www/pages/site/about/hall-of-fame.html:410 +#: i2p2www/pages/site/about/hall-of-fame.html:411 +#: i2p2www/pages/site/about/hall-of-fame.html:412 +#: i2p2www/pages/site/about/hall-of-fame.html:413 +#: i2p2www/pages/site/about/hall-of-fame.html:414 +#: i2p2www/pages/site/about/hall-of-fame.html:415 +#: i2p2www/pages/site/about/hall-of-fame.html:416 +#: i2p2www/pages/site/about/hall-of-fame.html:417 +#: i2p2www/pages/site/about/hall-of-fame.html:418 +#: i2p2www/pages/site/about/hall-of-fame.html:419 +#: i2p2www/pages/site/about/hall-of-fame.html:420 +#: i2p2www/pages/site/about/hall-of-fame.html:421 +#: i2p2www/pages/site/about/hall-of-fame.html:422 +#: i2p2www/pages/site/about/hall-of-fame.html:423 +#: i2p2www/pages/site/about/hall-of-fame.html:424 +#: i2p2www/pages/site/about/hall-of-fame.html:425 +#: i2p2www/pages/site/about/hall-of-fame.html:426 +#: i2p2www/pages/site/about/hall-of-fame.html:427 +#: i2p2www/pages/site/about/hall-of-fame.html:428 +#: i2p2www/pages/site/about/hall-of-fame.html:429 +#: i2p2www/pages/site/about/hall-of-fame.html:430 +#: i2p2www/pages/site/about/hall-of-fame.html:431 +#: i2p2www/pages/site/about/hall-of-fame.html:432 +#: i2p2www/pages/site/about/hall-of-fame.html:433 +#: i2p2www/pages/site/about/hall-of-fame.html:434 +#: i2p2www/pages/site/about/hall-of-fame.html:435 +#: i2p2www/pages/site/about/hall-of-fame.html:437 +#: i2p2www/pages/site/about/hall-of-fame.html:438 +#: i2p2www/pages/site/about/hall-of-fame.html:439 +#: i2p2www/pages/site/about/hall-of-fame.html:440 +#: i2p2www/pages/site/about/hall-of-fame.html:441 +#: i2p2www/pages/site/about/hall-of-fame.html:442 +#: i2p2www/pages/site/about/hall-of-fame.html:443 +#: i2p2www/pages/site/about/hall-of-fame.html:444 +#: i2p2www/pages/site/about/hall-of-fame.html:446 +#: i2p2www/pages/site/about/hall-of-fame.html:447 +#: i2p2www/pages/site/about/hall-of-fame.html:448 +#: i2p2www/pages/site/about/hall-of-fame.html:450 +#: i2p2www/pages/site/about/hall-of-fame.html:451 +#: i2p2www/pages/site/about/hall-of-fame.html:452 +#: i2p2www/pages/site/about/hall-of-fame.html:453 +#: i2p2www/pages/site/about/hall-of-fame.html:454 +#: i2p2www/pages/site/about/hall-of-fame.html:456 +#: i2p2www/pages/site/about/hall-of-fame.html:459 +#: i2p2www/pages/site/about/hall-of-fame.html:460 +#: i2p2www/pages/site/about/hall-of-fame.html:461 +#: i2p2www/pages/site/about/hall-of-fame.html:462 +#: i2p2www/pages/site/about/hall-of-fame.html:463 +#: i2p2www/pages/site/about/hall-of-fame.html:464 +#: i2p2www/pages/site/about/hall-of-fame.html:465 +#: i2p2www/pages/site/about/hall-of-fame.html:466 +#: i2p2www/pages/site/about/hall-of-fame.html:467 +#: i2p2www/pages/site/about/hall-of-fame.html:468 +#: i2p2www/pages/site/about/hall-of-fame.html:469 +#: i2p2www/pages/site/about/hall-of-fame.html:470 +#: i2p2www/pages/site/about/hall-of-fame.html:471 +#: i2p2www/pages/site/about/hall-of-fame.html:472 +#: i2p2www/pages/site/about/hall-of-fame.html:474 +#: i2p2www/pages/site/about/hall-of-fame.html:475 +#: i2p2www/pages/site/about/hall-of-fame.html:476 +#: i2p2www/pages/site/about/hall-of-fame.html:478 +#: i2p2www/pages/site/about/hall-of-fame.html:481 +#: i2p2www/pages/site/about/hall-of-fame.html:482 +#: i2p2www/pages/site/about/hall-of-fame.html:483 +#: i2p2www/pages/site/about/hall-of-fame.html:484 +#: i2p2www/pages/site/about/hall-of-fame.html:485 +#: i2p2www/pages/site/about/hall-of-fame.html:486 +#: i2p2www/pages/site/about/hall-of-fame.html:487 +#: i2p2www/pages/site/about/hall-of-fame.html:488 +#: i2p2www/pages/site/about/hall-of-fame.html:489 +#: i2p2www/pages/site/about/hall-of-fame.html:490 +#: i2p2www/pages/site/about/hall-of-fame.html:491 +#: i2p2www/pages/site/about/hall-of-fame.html:492 +#: i2p2www/pages/site/about/hall-of-fame.html:493 +#: i2p2www/pages/site/about/hall-of-fame.html:494 +#: i2p2www/pages/site/about/hall-of-fame.html:495 +#: i2p2www/pages/site/about/hall-of-fame.html:496 +#: i2p2www/pages/site/about/hall-of-fame.html:497 +#: i2p2www/pages/site/about/hall-of-fame.html:498 +#: i2p2www/pages/site/about/hall-of-fame.html:499 +#: i2p2www/pages/site/about/hall-of-fame.html:501 +#: i2p2www/pages/site/about/hall-of-fame.html:502 +#: i2p2www/pages/site/about/hall-of-fame.html:503 +msgid "General fund" +msgstr "Общий фонд" + +#: i2p2www/pages/site/about/hall-of-fame.html:10 +#: i2p2www/pages/site/about/hall-of-fame.html:12 +#: i2p2www/pages/site/about/hall-of-fame.html:14 +#: i2p2www/pages/site/about/hall-of-fame.html:20 +#, python-format +msgid "%(euroval)s € and %(btcval)s BTC" +msgstr "%(euroval)s &евро; и %(btcval)s BTC" + +#: i2p2www/pages/site/about/hall-of-fame.html:11 +msgid "Datastorage bounty" +msgstr "ÐŸÑ€ÐµÐ¼Ð¸Ñ Ð·Ð° Хранилище данных" + +#: i2p2www/pages/site/about/hall-of-fame.html:13 +msgid "Native IPv6 I2P" +msgstr "Ðативный IPv6 I2P" + +#: i2p2www/pages/site/about/hall-of-fame.html:15 +msgid "I2PHex bounty" +msgstr "ÐŸÑ€ÐµÐ¼Ð¸Ñ Ð·Ð° I2PHex" + +#: i2p2www/pages/site/about/hall-of-fame.html:16 +#: i2p2www/pages/site/about/hall-of-fame.html:18 +#: i2p2www/pages/site/about/hall-of-fame.html:22 +#, python-format +msgid "%(euroval)s €" +msgstr "%(euroval)s &евро;" + +#: i2p2www/pages/site/about/hall-of-fame.html:17 +msgid "I2P in debian mirrors" +msgstr "I2P на зеркалах debian" + +#: i2p2www/pages/site/about/hall-of-fame.html:19 +msgid "Bitcoin client for I2P" +msgstr "Биткоин-клиент Ð´Ð»Ñ I2P" + +#: i2p2www/pages/site/about/hall-of-fame.html:21 +msgid "Unit Tests for I2P router" +msgstr "Модульные теÑÑ‚Ñ‹ Ð´Ð»Ñ Ð¼Ð°Ñ€ÑˆÑ€ÑƒÑ‚Ð¸Ð·Ð°Ñ‚Ð¾Ñ€Ð° I2P" + +#: i2p2www/pages/site/about/hall-of-fame.html:23 +msgid "Bounty Robert" +msgstr "Вознаграждение за Robert" + +#: i2p2www/pages/site/about/hall-of-fame.html:24 +msgid "Bounty Syndie" +msgstr "Вознаграждение за Syndie" + +#: i2p2www/pages/site/about/hall-of-fame.html:25 +msgid "Bounty I2P for CCR Microtic Board" +msgstr "Вознаграждение за I2P Ð´Ð»Ñ CCR Microtic Board" + +#: i2p2www/pages/site/about/hall-of-fame.html:28 +msgid "Current monthly running costs:" +msgstr "Текущие ежемеÑÑчные ÑкÑплуатационные раÑходы:" + +#: i2p2www/pages/site/about/hall-of-fame.html:39 +msgid "Big thanks go to the following people who have donated to I2P!" +msgstr "Ð‘Ð¾Ð»ÑŒÑˆÐ°Ñ Ð±Ð»Ð°Ð³Ð¾Ð´Ð°Ñ€Ð½Ð¾ÑÑ‚ÑŒ Ñледующим людÑм, Ñделавшим пожертвование Ð´Ð»Ñ I2P!" + +#: i2p2www/pages/site/about/hall-of-fame.html:40 +#, python-format +msgid "" +"If you have made a donation, please send an email to <a " +"href=\"mailto:%(echelon)s\">echelon</a>\n" +"with your name or nick (and optionally homepage) so we can list you here." +msgstr "" +"ЕÑли вы Ñделали пожертвование, пожалуйÑта, пошлите email на <a " +"href=\"mailto:%(echelon)s\">echelon</a>\n" +"Ñ Ð²Ð°ÑˆÐ¸Ð¼ именем или ником (и, по желанию, домашней Ñтраницей), чтобы мы " +"Ñмогли указать Ð²Ð°Ñ Ð·Ð´ÐµÑÑŒ." + +#: i2p2www/pages/site/about/hall-of-fame.html:45 +msgid "Current monthly subscriptions:" +msgstr "Текущие подпиÑки на меÑÑц:" + +#: i2p2www/pages/site/about/hall-of-fame.html:51 +msgid "2013 donations and costs:" +msgstr "ÐŸÐ¾Ð¶ÐµÑ€Ñ‚Ð²Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¸ раÑходы 2013 года:" + +#: i2p2www/pages/site/about/hall-of-fame.html:170 +msgid "2012 donations and costs:" +msgstr "ÐŸÐ¾Ð¶ÐµÑ€Ñ‚Ð²Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¸ раÑходы в 2012 году:" + +#: i2p2www/pages/site/about/hall-of-fame.html:298 +msgid "2011 donations and costs:" +msgstr "ÐŸÐ¾Ð¶ÐµÑ€Ñ‚Ð²Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¸ раÑходы в 2011 году:" + +#: i2p2www/pages/site/about/hall-of-fame.html:399 +msgid "Previous to 2011 donations:" +msgstr "ÐŸÐ¾Ð¶ÐµÑ€Ñ‚Ð²Ð¾Ð²Ð°Ð½Ð¸Ñ Ð´Ð¾ 2011 года:" + +#: i2p2www/pages/site/about/intro.html:2 +msgid "Intro" +msgstr "Введение" + +#: i2p2www/pages/site/about/intro.html:4 +msgid "The Invisible Internet Project" +msgstr "Проект Ðевидимый Интернет" + +#: i2p2www/pages/site/about/intro.html:5 +msgid "" +"I2P is an anonymous network, exposing a simple layer that applications " +"can \n" +"use to anonymously and securely send messages to each other. The network " +"itself is \n" +"strictly message based (a la \n" +"<a href=\"http://en.wikipedia.org/wiki/Internet_Protocol\">IP</a>), but " +"there is a \n" +"library available to allow reliable streaming communication on top of it " +"(a la \n" +"<a " +"href=\"http://en.wikipedia.org/wiki/Transmission_Control_Protocol\">TCP</a>)." +" \n" +"All communication is end to end encrypted (in total there are four layers" +" of \n" +"encryption used when sending a message), and even the end points " +"(\"destinations\") \n" +"are cryptographic identifiers (essentially a pair of <a " +"href=\"http://en.wikipedia.org/wiki/Public_key_encryption\">public " +"keys</a>)." +msgstr "" +"I2P - Ñто Ð°Ð½Ð¾Ð½Ð¸Ð¼Ð½Ð°Ñ Ñеть, Ð¾Ñ‚ÐºÑ€Ñ‹Ð²Ð°ÑŽÑ‰Ð°Ñ Ð¿Ñ€Ð¾Ñтой уровень, который приложениÑ" +" могут\n" +"иÑпользовать, чтобы анонимно и безопаÑно обмениватьÑÑ ÑообщениÑми друг\n" +"Ñ Ð´Ñ€ÑƒÐ³Ð¾Ð¼. Сеть Ñама по Ñебе оÑнована Ñтрого на обмене ÑообщениÑми (вроде" +" \n" +"<a href=\"http://ru.wikipedia.org/wiki/IP\">IP</a>), но еÑÑ‚ÑŒ библиотека, " +"ÑпоÑобнаÑ\n" +"разрешать надёжное потоковое Ñоединение поверх них (вроде \n" +"<a href=\"http://ru.wikipedia.org/wiki/TCP\"TCP</a>).\n" +"Ð’Ñе ÑÐ¾ÐµÐ´Ð¸Ð½ÐµÐ½Ð¸Ñ Ð·Ð°ÑˆÐ¸Ñ„Ñ€Ð¾Ð²Ð°Ð½Ñ‹ из конца в конец (в Ñумме, четыре ÑÐ»Ð¾Ñ " +"шифрованиÑ\n" +"иÑпользуютÑÑ Ð¿Ñ€Ð¸ отправке ÑообщениÑ), и даже конечные точки " +"(\"адреÑаты\") - \n" +"Ñто криптографичеÑкие идентификаторы (по ÑущеÑтву, пара <a " +"href=\"http://ru.wikipedia.org/wiki/%D0%9A%D1%80%D0%B8%D0%BF%D1%82%D0%BE%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BC%D0%B0_%D1%81_%D0%BE%D1%82%D0%BA%D1%80%D1%8B%D1%82%D1%8B%D0%BC_%D0%BA%D0%BB%D1%8E%D1%87%D0%BE%D0%BC\">открытых" +" ключей</a>)." + +#: i2p2www/pages/site/about/intro.html:17 +msgid "How does it work?" +msgstr "Как Ñто работает?" + +#: i2p2www/pages/site/about/intro.html:19 +#, python-format +msgid "" +"To anonymize the messages sent, each client application has their I2P " +"\"router\"\n" +"build a few inbound and outbound \"<a " +"href=\"%(tunnelrouting)s\">tunnels</a>\" - a \n" +"sequence of peers that pass messages in one direction (to and from the " +"client, \n" +"respectively). In turn, when a client wants to send a message to another" +" client, \n" +"the client passes that message out one of their outbound tunnels " +"targeting one of the \n" +"other client's inbound tunnels, eventually reaching the destination. " +"Every \n" +"participant in the network chooses the length of these tunnels, and in " +"doing so, \n" +"makes a tradeoff between anonymity, latency, and throughput according to " +"their \n" +"own needs. The result is that the number of peers relaying each end to " +"end \n" +"message is the absolute minimum necessary to meet both the sender's and " +"the \n" +"receiver's threat model." +msgstr "" +"Чтобы анонимизировать отправлÑемое Ñообщение, каждое приложение-клиент\n" +"имеет Ñвой I2P \"маршрутизатор\", ÑтроÑщий неÑколько входÑщих и иÑходÑщих" +"\n" +"\"<a href=\"%(tunnelrouting)s\">туннелей</a>\" - поÑледовательноÑÑ‚ÑŒ " +"пиров,\n" +"передающих ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð² одном направлении (к и от клиента ÑоответÑтвенно)." +"\n" +"Ð’ Ñвою очередь, когда один клиент хочет поÑлать Ñообщение другому, он\n" +"передаёт Ñто Ñообщение через один из Ñвоих иÑходÑщих туннелей, " +"нацеливаÑÑÑŒ\n" +"на один из входÑщих туннелей другого клиента, в конечном итоге доÑÑ‚Ð¸Ð³Ð°Ñ \n" +"пункта назначениÑ. Каждый учаÑтник Ñети выбирает длину Ñтих туннелей, и\n" +"таким образом идёт на компромиÑÑ Ð¼ÐµÐ¶Ð´Ñƒ анонимноÑтью, временем ожиданиÑ\n" +"и пропуÑкной ÑпоÑобноÑтью в ÑоответÑтвии Ñо Ñвоими нуждами. Ð’ результате," +"\n" +"количеÑтво пиров, ретранÑлирующих каждое Ñообщение из конца в конец,\n" +"Ñведено к абÑолютному минимуму, необходимому, чтобы удовлетворить\n" +"\"модель угрозы\" (уровень желаемой безопаÑноÑти) как отправителÑ, так и " +"получателÑ. " + +#: i2p2www/pages/site/about/intro.html:33 +#, python-format +msgid "" +"The first time a client wants to contact another client, they make a " +"query \n" +"against the fully distributed \"<a href=\"%(netdb)s\">network \n" +"database</a>\" - a custom structured <a " +"href=\"http://en.wikipedia.org/wiki/Distributed_hash_table\">\n" +"distributed hash table (DHT)</a> based off the \n" +"<a href=\"http://en.wikipedia.org/wiki/Kademlia\"> Kademlia " +"algorithm</a>. This is done \n" +"to find the other client's inbound tunnels efficiently, but subsequent " +"messages \n" +"between them usually includes that data so no further network database " +"lookups \n" +"are required." +msgstr "" +"Когда один клиент в первый раз хочет ÑвÑзатьÑÑ Ñ Ð´Ñ€ÑƒÐ³Ð¸Ð¼ клиентом, они " +"делают запроÑ\n" +"к полноÑтью раÑпределённой \"<a href=\"%(netdb)s\">Ñетевой âŽ\n" +"базе данных</a>\" - перÑонально Ñтруктурированной\n" +"<a href=\"http://ru.wikipedia.org/wiki/DHT\">раÑпределённой хеш-таблице " +"(DHT)</a>,\n" +"оÑнованной на <a href=\"http://ru.wikipedia.org/wiki/Kademlia\"> " +"алгоритме Kademilia</a>. Ðто Ñделано\n" +"Ð´Ð»Ñ Ñффективного поиÑка входÑщих туннелей других клиентов, но поÑледующие" +" ÑообщениÑ\n" +"между ними обычно включают в ÑÐµÐ±Ñ Ñти данные, поÑтому поиÑк в Ñетевой " +"базе данных\n" +"больше не требуетÑÑ. " + +#: i2p2www/pages/site/about/intro.html:44 +#, python-format +msgid "More details about how I2P works are <a href=\"%(docs)s\">available</a>." +msgstr "Более <a href=\"%(docs)s\">подробно</a> о том, как работает I2P." + +#: i2p2www/pages/site/about/intro.html:48 +msgid "What can you do with it?" +msgstr "Как вы можете Ñто иÑпользовать?" + +#: i2p2www/pages/site/about/intro.html:50 +#, python-format +msgid "" +"Within the I2P network, applications are not restricted in how they can \n" +"communicate - those that typically use UDP can make use of the base I2P \n" +"functionality, and those that typically use TCP can use the TCP-like " +"streaming\n" +"library. We have a generic TCP/I2P bridge application \n" +"(\"<a href=\"%(i2ptunnel)s\">I2PTunnel</a>\") that enables people to " +"forward TCP streams\n" +"into the I2P network as well as to receive streams out of the network and" +" \n" +"forward them towards a specific TCP/IP address." +msgstr "" +"Внутри Ñети I2P Ð¿Ñ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð½Ðµ ограничены в ÑпоÑобах коммуникации - \n" +"те, что обычно иÑпользуют UDP, могут иÑпользовать базовый функционал\n" +"I2P, а те, что обычно иÑпользуют TCP, могут иÑпользовать TCP-подобную \n" +"потоковую библиотеку. У Ð½Ð°Ñ ÐµÑÑ‚ÑŒ приложение общего TCP/IP моÑта\n" +"(\"<a href=\"%(i2ptunnel)s\">I2PTunnel</a>\"), которое позволÑет людÑм \n" +"переÑылать TCP потоки в I2P Ñеть также как получать потоки извне Ñети и \n" +"переÑылать их на определённый TCP/IP адреÑ." + +#: i2p2www/pages/site/about/intro.html:60 +msgid "" +"I2PTunnel is currently used to let people run their own anonymous website" +" \n" +"(\"eepsite\") by running a normal webserver and pointing an I2PTunnel " +"'server' \n" +"at it, which people can access anonymously over I2P with a normal web " +"browser \n" +"by running an I2PTunnel HTTP proxy (\"eepproxy\"). In addition, we use " +"the same \n" +"technique to run an anonymous IRC network (where the IRC server is hosted" +" \n" +"anonymously, and standard IRC clients use an I2PTunnel to contact it). " +"There \n" +"are other application development efforts going on as well, such as one " +"to \n" +"build an optimized swarming file transfer application (a la \n" +"<a href=\"http://www.bittorrent.com/\">BitTorrent</a>), a \n" +"distributed data store (a la <a " +"href=\"https://freenetproject.org/\">Freenet</a> / \n" +"<a href=\"http://mnetproject.org/\">MNet</a>), and a blogging system (a " +"fully \n" +"distributed <a href=\"http://www.livejournal.com/\">LiveJournal</a>), but" +" those are \n" +"not ready for use yet." +msgstr "" +"I2PTunnel в наÑтоÑщее Ð²Ñ€ÐµÐ¼Ñ Ð¸ÑпользуетÑÑ, чтобы позволить людÑм Ñоздать\n" +"ÑобÑтвенный анонимный вебÑайт (\"eepsite\"), запуÑтив нормальный " +"вебÑервер и \n" +"указав \"Ñерверу\" I2PTunnel на него, который люди Ñмогут поÑещать " +"анонимно\n" +"через I2P и обычный браузер, запуÑÐºÐ°Ñ HTTP прокÑи I2PTunnel " +"(\"eeproxy\"). К тому же,\n" +"мы иÑпользуем ту же Ñамую технику, чтобы запуÑкать анонимную Ñеть IRC " +"(где \n" +"IRC-Ñервер хоÑтитÑÑ Ð°Ð½Ð¾Ð½Ð¸Ð¼Ð½Ð¾, а Ñтандартный IRC-клиент иÑпользует " +"I2PTunnel, чтобы\n" +"ÑвÑзать Ñ Ð½Ð¸Ð¼). ПрилагаютÑÑ ÑƒÑÐ¸Ð»Ð¸Ñ Ð¸ Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚ÐºÐ¸ других приложений, " +"например\n" +"Ð¿Ñ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¾Ð¿Ñ‚Ð¸Ð¼Ð¸Ð·Ð¸Ñ€Ð¾Ð²Ð°Ð½Ð½Ð¾Ð³Ð¾ кооперативного обмена файлами (вроде \n" +"<a href=\"http://www.bittorrent.com/\">BitTorrent</a>), раÑпределённого " +"хранилища данных\n" +"(вроде <a href=\"https://freenetproject.org/\">Freenet</a> / âŽ\n" +"<a href=\"http://mnetproject.org/\">MNet</a>), и ÑиÑтемы Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð±Ð»Ð¾Ð³Ð¾Ð² " +"(полноÑтью\n" +"раÑпределённый <a href=\"http://www.livejournal.com/\">LiveJournal</a>), " +"но они пока \n" +"не готовы к иÑпользованию." + +#: i2p2www/pages/site/about/intro.html:76 +msgid "" +"I2P is not inherently an \"outproxy\" network - the client you send a " +"message \n" +"to is the cryptographic identifier, not some IP address, so the message " +"must \n" +"be addressed to someone running I2P. However, it is possible for that " +"client\n" +"to be an outproxy, allowing you to anonymously make use of their Internet" +" \n" +"connection. To demonstrate this, the \"eepproxy\" will accept normal " +"non-I2P \n" +"URLs (e.g. \"http://www.i2p.net\") and forward them to a specific " +"destination\n" +"that runs a <a href=\"http://www.squid-cache.org/\">squid</a> HTTP proxy," +" allowing \n" +"simple anonymous browsing of the normal web. Simple outproxies like that" +" are \n" +"not viable in the long run for several reasons (including the cost of " +"running \n" +"one as well as the anonymity and security issues they introduce), but in" +" \n" +"certain circumstances the technique could be appropriate." +msgstr "" +"I2P не ÑвлÑетÑÑ, по Ñути, Ñетью \"аутпрокÑи\": клиент, которому вы " +"поÑылаете\n" +"Ñообщение, - Ñто криптографичеÑкий идентификатор, не какой-то IP адреÑ,\n" +"поÑтому Ñообщение должно быть адреÑовано тому, кто иÑпользует I2P. " +"Однако,\n" +"Ð´Ð»Ñ Ñтого клиента возможно быть аутпрокÑи, позволÑÑ Ð²Ð°Ð¼ анонимно " +"иÑпользовать\n" +"его интернет-Ñоединение. Ð’ качеÑтве демонÑтрации, \"eeproxy\" примет " +"нормальный\n" +"не-I2P URL (такой как \"http://www.i2p.net\") и перенаправит его в " +"определённый пункт,\n" +"иÑпользующий <a href=\"http://www.squid-cache.org/\">squid</a> HTTP " +"прокÑи, позволÑÑ\n" +"проÑтой анонимный Ñерфинг обычного интернета. ПроÑтые аутпрокÑи как Ñтот " +"не \n" +"жизнеÑпоÑобны в долгоÑрочной перÑпективе по неÑкольким причинам (включаÑ\n" +"раÑходы на поддержание работы, также как проблемы Ñ Ð°Ð½Ð¾Ð½Ð¸Ð¼Ð½Ð¾Ñтью и " +"безопаÑноÑтью,\n" +"которые Ð´Ð»Ñ Ð½Ð¸Ñ… характерны), но в определённых обÑтоÑтельÑтвах такой " +"метод может быть\n" +"целеÑообразным." + +#: i2p2www/pages/site/about/intro.html:90 +#, python-format +msgid "" +"The I2P development <a href=\"%(team)s\">team</a> is an open group, " +"welcome to all \n" +"who are interested in <a href=\"%(volunteer)s\">getting involved</a>, and" +" all of \n" +"the code is <a href=\"%(licenses)s\">open source</a>. The core I2P SDK " +"and the \n" +"current router implementation is done in Java (currently working with " +"both \n" +"sun and kaffe, gcj support planned for later), and there is a \n" +"<a href=\"%(sam)s\">simple socket based API</a> for accessing the network" +" from \n" +"other languages (with a C library available, and both Python and Perl in" +" \n" +"development). The network is actively being developed and has not yet " +"reached \n" +"the 1.0 release, but the current <a href=\"%(roadmap)s\">roadmap</a> " +"describes \n" +"our schedule." +msgstr "" +"<a href=\"%(team)s\">Команда</a> разработчиков I2P - Ñто группа Ð¾Ñ‚ÐºÑ€Ñ‹Ñ‚Ð°Ñ " +"Ð´Ð»Ñ Ð²Ñех кто заинтереÑован <a href=\"%(volunteer)s\">принÑÑ‚ÑŒ учаÑтие</a>," +" и веÑÑŒ код проÑкта - Ñто <a href=\"%(licenses)s\">открытый код</a>. " +"Ядро I2P SDK и Ñ‚ÐµÐºÑƒÑ‰Ð°Ñ Ñ€ÐµÐ°Ð»Ð¸Ð·Ð°Ñ†Ð¸Ñ Ñ€Ð¾ÑƒÑ‚ÐµÑ€Ð° выполнены на Ñзыке Java (в " +"наÑтоÑщий момент поддерживаютÑÑ Ñ€ÐµÐ°Ð»Ð¸Ð·Ð°Ñ†Ð¸Ð¸ от \n" +"sun и kaffe, Ñ€ÐµÐ°Ð»Ð¸Ð·Ð°Ñ†Ð¸Ñ Ð¿Ð¾Ð´Ð´ÐµÑ€Ð¶ÐºÐ¸ gcj запланирована на будущее), также " +"ÑущеÑтвует\n" +"<a href=\"%(sam)s\">проÑтое оÑнованное на Ñокетах API</a> Ð´Ð»Ñ Ð´Ð¾Ñтупа к " +"Ñети из других Ñзыков (библиотека Ð´Ð»Ñ C уже доÑтупна, а Ð´Ð»Ñ Python и Perl" +" в \n" +"процеÑÑе разработки). Проект активно разрабатываетÑÑ Ñ…Ð¾Ñ‚ÑŒ ещё и не доÑтиг" +" Ñтадии релиза 1.0, но текущий <a href=\"%(roadmap)s\">план Ñ€Ð°Ð·Ð²Ð¸Ñ‚Ð¸Ñ " +"проекта</a> опиÑывает дальнейший путь нашей команды." + +#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4 +msgid "Presentations on I2P" +msgstr "Презентации в I2P" + +#: i2p2www/pages/site/about/media.html:5 +#, python-format +msgid "" +"Following are links to presentations, videos, and tutorials about I2P. " +"Links to research papers on I2P are available <a " +"href=\"%(papers)s\">here</a>." +msgstr "" +"Ðиже приведены ÑÑылки на презентации, видео и руководÑтва по I2P. СÑылки " +"на иÑÑледовательÑкие работы по I2P доÑтупны <a " +"href=\"%(papers)s\">здеÑÑŒ</a>." + +#: i2p2www/pages/site/about/media.html:8 +#, python-format +msgid "To request an addition to this page, please send to %(email)s." +msgstr "Материалы Ð´Ð»Ñ Ð´Ð¾Ð±Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð½Ð° Ñту Ñтраницу отÑылайте на %(email)s." + +#: i2p2www/pages/site/about/media.html:11 +msgid "" +"\n" +"Newest links are at the bottom of each section." +msgstr "" +"\n" +"Свежие ÑÑылки в начале каждого раздела." + +#: i2p2www/pages/site/about/media.html:16 +msgid "Presentations" +msgstr "Презентации" + +#: i2p2www/pages/site/about/media.html:19 +#, python-format +msgid "" +"IIP Presentation at CodeCon\n" +"<a href=\"%(mp3)s\">MP3 audio</a>\n" +"<a href=\"%(transcript)s\">transcript</a>\n" +"Lance James (0x90), February 2002." +msgstr "" +"ÐŸÑ€ÐµÐ·ÐµÐ½Ñ‚Ð°Ñ†Ð¸Ñ IIP на конференции CodeCon\n" +"<a href=\"%(mp3)s\">MP3 audio</a>\n" +"<a href=\"%(transcript)s\">Ñтенограмма</a>\n" +"Lance James (0x90), Февраль 2002." + +#: i2p2www/pages/site/about/media.html:27 +#, python-format +msgid "" +"IIP Presentation at ToorCon\n" +"<a href=\"%(mp3)s\">MP3 audio</a>\n" +"<a href=\"%(slides)s\">slides</a>\n" +"Lance James (0x90), September 2002." +msgstr "" +"ÐŸÑ€ÐµÐ·ÐµÐ½Ñ‚Ð°Ñ†Ð¸Ñ IIP на конференции ToorCon\n" +"<a href=\"%(mp3)s\">MP3 audio</a>\n" +"<a href=\"%(slides)s\">Ñлайды</a>\n" +"Lance James (0x90), СентÑбрь 2002." + +#: i2p2www/pages/site/about/media.html:35 +#, python-format +msgid "" +"<a href=\"%(video)s\">To Be or I2P</a>\n" +"(Youtube Video)\n" +"An introduction into anonymous communication with I2P.\n" +"<a href=\"%(pdf)s\">To Be or I2P (PDF presentation)</a>,\n" +"Jens Kubieziel, 24C3 Berlin, December 28, 2007." +msgstr "" +"<a href=\"%(video)s\">Быть или I2P</a>\n" +"(Youtube Video)\n" +"Введение в анонимную ÑвÑзь Ñ I2P.\n" +"<a href=\"%(pdf)s\">Быть или I2P (Ð¿Ñ€ÐµÐ·ÐµÐ½Ñ‚Ð°Ñ†Ð¸Ñ PDF)</a>,\n" +"Jens Kubieziel, 24C3 Berlin, Декабрь 28, 2007." + +#: i2p2www/pages/site/about/media.html:44 +#, python-format +msgid "" +"<a href=\"%(video)s\">Video of I2P talk at Chemnitz Linux Tag</a>,\n" +"Lars Schimmer,\n" +"March 14-15, 2009" +msgstr "" +"<a href=\"%(video)s\">ВидеозапиÑÑŒ обÑÑƒÐ¶Ð´ÐµÐ½Ð¸Ñ I2P на Chemnitz Linux " +"Tag</a>,\n" +"Lars Schimmer,\n" +"Март 14-15, 2009" + +#: i2p2www/pages/site/about/media.html:50 +#, python-format +msgid "" +"HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of" +" Adrian Hong's talk\n" +"\"Hackers for Human Rights\".\n" +"<a href=\"%(mp3)s\">MP3 audio</a>" +msgstr "" +"ÐÐВЕРÐОЕ New York Июль 17, 2010 - Краткий обзор I2P от zzz, в конце " +"выÑÑ‚ÑƒÐ¿Ð»ÐµÐ½Ð¸Ñ Adrian Hong's\n" +"\"Хакеры за Права Человека\".\n" +"<a href=\"%(mp3)s\">MP3 audio</a>" + +#: i2p2www/pages/site/about/media.html:56 +#, python-format +msgid "" +"<a href=\"%(link)s\">Into the I2P Darknet: Welcome to Cipherspace</a>\n" +"Adrian Crenshaw. Schmoocon Firetalk, January 2011" +msgstr "" +"<a href=\"%(link)s\">Ð’ I2P Darknet: Добро пожаловать в Cipherspace</a>\n" +"Adrian Crenshaw. Schmoocon Firetalk, Январь 2011" + +#: i2p2www/pages/site/about/media.html:61 +#, python-format +msgid "" +"<a href=\"%(link)s\">Using techhnology to advance liberty</a>\n" +"(Youtube Video)\n" +"Eric Johnson.\n" +"<a href=\"http://agora.io/etienne\">Agora I/O Unconference</a>, March 27," +" 2011.\n" +"I2P covered from 10:00 to 20:00 in the video." +msgstr "" +"<a href=\"%(link)s\">ИÑпользование технологий Ð´Ð»Ñ Ñ€Ð°ÑпроÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ " +"Ñвободы</a>\n" +"(Youtube Video)\n" +"Eric Johnson.\n" +"<a href=\"http://agora.io/etienne\">Agora I/O Unconference</a>, Март 27, " +"2011.\n" +"Ð˜Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ð¸Ñ Ð¾Ð± I2P Ñ 10:00 до 20:00." + +#: i2p2www/pages/site/about/media.html:69 +#, python-format +msgid "" +"<a href=\"%(pdf)s\">The Bright side of darknets</a>, FOSSCOMM Patras May " +"2011" +msgstr "<a href=\"%(pdf)s\">Ð¡Ð²ÐµÑ‚Ð»Ð°Ñ Ñторона darknet</a>, FOSSCOMM Patras Май 2011" + +#: i2p2www/pages/site/about/media.html:73 +#, python-format +msgid "" +"<a href=\"%(link)s\">Common Darknet Weaknesses</a>\n" +"(Youtube Video)\n" +"Adrian Crenshaw, <a href=\"http://aide.marshall.edu/\">AIDE</a>, July " +"11-15, 2011." +msgstr "" +"<a href=\"%(link)s\">Общие уÑзвимоÑти Darknet</a>\n" +"(Youtube Video)\n" +"Adrian Crenshaw, <a href=\"http://aide.marshall.edu/\">AIDE</a>, Июль " +"11-15, 2011." + +#: i2p2www/pages/site/about/media.html:79 +#, python-format +msgid "" +"<a href=\"%(link)s\">I2P / Tor Workshop Notes</a>\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011." +msgstr "" +"<a href=\"%(link)s\">Заметки Ñ Ñеминаров по I2P / Tor</a>\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, ÐвгуÑÑ‚ 6, 2011." + +#: i2p2www/pages/site/about/media.html:84 +#, python-format +msgid "" +"<a href=\"%(live)s\">Cipherspaces/Darknets: An Overview Of Attack " +"Strategies -\n" +"DEF CON Live version (Youtube Video)</a>,\n" +"<a href=\"%(studio)s\">\"Studio\" version (Youtube Video)</a>,\n" +"<a href=\"%(slides)s\">Slides (ppt)</a>\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011." +msgstr "" +"<a href=\"%(live)s\">Cipherspaces/Darknets: Обзор Ñтратегий атак -\n" +"DEF CON Ð–Ð¸Ð²Ð°Ñ Ð²ÐµÑ€ÑÐ¸Ñ (Youtube Video)</a>,\n" +"<a href=\"%(studio)s\">\"СтудийнаÑ\" верÑÐ¸Ñ (Youtube Video)</a>,\n" +"<a href=\"%(slides)s\">Слайды (ppt)</a>\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, ÐвгуÑÑ‚ 7, 2011." + +#: i2p2www/pages/site/about/media.html:94 +msgid "" +"<a href=\"http://0x375.org/\">Modern cipherspace ecosystems</a>, 0x375 " +"0x06 4/11/2011" +msgstr "" +"<a href=\"http://0x375.org/\">Современные ÑкоÑиÑтемы cipherspace </a>, " +"0x375 0x06 4/11/2011" + +#: i2p2www/pages/site/about/media.html:100 +msgid "Tutorials" +msgstr "РуководÑтва" + +#: i2p2www/pages/site/about/media.html:103 +#, python-format +msgid "" +"<a href=\"%(link)s\">I2P Windows Tutorial</a>\n" +"(Youtube Video)\n" +"This guide will show you how to install I2P in Windows XP.\n" +"By <a href=\"http://telecomix.org/\">Telecomix</a>" +msgstr "" +"<a href=\"%(link)s\">РуководÑтво I2P под Windows</a>\n" +"(Youtube Video)\n" +"Ðтот гид объÑÑнит как уÑтановить I2P в Windows XP.\n" +"Ðвтор <a href=\"http://telecomix.org/\">Telecomix</a>" + +#: i2p2www/pages/site/about/media.html:111 +#, python-format +msgid "" +"<a href=\"%(link)s\">I2P Debian Tutorial</a>\n" +"(Youtube Video)\n" +"This will guide you through how to install I2P on a Debian Linux System.\n" +"By <a href=\"http://telecomix.org/\">Telecomix</a>" +msgstr "" +"<a href=\"%(link)s\">РуководÑтво I2P под Debian</a>\n" +"(Youtube Video)\n" +"Ðтот гид объÑÑнит как уÑтановить I2P в Debian Linux System.\n" +"Ðвтор <a href=\"http://telecomix.org/\">Telecomix</a>" + +#: i2p2www/pages/site/about/media.html:119 +#, python-format +msgid "" +"<a href=\"%(link)s\">How to set up anonymous site in I2P</a>\n" +"(Youtube Video)\n" +"How to set up an anonymous web site in I2P.\n" +"By <a href=\"http://telecomix.org/\">Telecomix</a>" +msgstr "" +"<a href=\"%(link)s\">Как поднÑÑ‚ÑŒ анонимный веб-Ñайт в Ñети I2P</a>\n" +"(Youtube Video)\n" +"Как поднÑÑ‚ÑŒ анонимный веб-Ñайт в Ñети I2P.\n" +"Ðвтор <a href=\"http://telecomix.org/\">Telecomix</a>" + +#: i2p2www/pages/site/about/media.html:126 +#, python-format +msgid "" +"<a href=\"%(link)s\">I2P Tutorial Mac OS X</a>\n" +"(Youtube Video)\n" +"A tutorial on how to run i2p on Mac OS X and how to connect to " +"irc.telecomix.i2p.\n" +"By <a href=\"http://telecomix.org/\">Telecomix</a>" +msgstr "" +"<a href=\"%(link)s\">РуководÑтво I2P под Mac OS X</a>\n" +"(Youtube Video)\n" +"РуководÑтво по запуÑку i2p под Mac OS X, и как подключитьÑÑ Ðº " +"irc.telecomix.i2p.\n" +"Ðвтор <a href=\"http://telecomix.org/\">Telecomix</a>" + +#: i2p2www/pages/site/about/media.html:133 +#, python-format +msgid "" +"<a href=\"%(link)s\">Felix Atari explains the basic principles of I2P</a>" +"\n" +"(Youtube Video)\n" +"Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n" +"By <a href=\"http://telecomix.org/\">Telecomix</a>" +msgstr "" +"<a href=\"%(link)s\">Felix Atari объÑÑнÑет оÑновные принципы I2P</a>\n" +"(Youtube Video)\n" +"Felix Atari Ñотрудник Telecomix Crypto Munitions Bureau.\n" +"Ðвтор <a href=\"http://telecomix.org/\">Telecomix</a>" + +#: i2p2www/pages/site/about/media.html:140 +#, python-format +msgid "" +"<a href=\"%(link)s\">How to get onto I2P, the anonymous P2P Darknet " +"(Windows Install)</a>\n" +"(Youtube Video)\n" +"This tutorial shows how to install and configure software needed to " +"access I2P." +msgstr "" +"<a href=\"%(link)s\">Как попаÑÑ‚ÑŒ в I2P, анонимный P2P Darknet (уÑтновка в" +" Windows)</a>\n" +"(Youtube Video)\n" +"Ðто руководÑтво объÑÑнит как уÑтановить и наÑтроить ПО Ð´Ð»Ñ Ð´Ð¾Ñтупа в I2P." + +#: i2p2www/pages/site/about/media.html:146 +#, python-format +msgid "" +"<a href=\"%(link)s\">How to connect to I2P</a>\n" +"(Youtube Video)\n" +"How to install I2P on Ubuntu." +msgstr "" +"<a href=\"%(link)s\">Как подключитьÑÑ Ðº Ñети I2P</a>\n" +"(Youtube Video)\n" +"Как уÑтановить I2P в Ubuntu." + +#: i2p2www/pages/site/about/media.html:152 +#, python-format +msgid "" +"<a href=\"%(link)s\">Installing the I2P darknet software in Linux</a>\n" +"(Video)\n" +"Adrian Crenshaw.\n" +"January 2011" +msgstr "" +"<a href=\"%(link)s\">УÑтановка ПО I2P darknet в Linux</a>\n" +"(Video)\n" +"Adrian Crenshaw.\n" +"Январь 2011" + +#: i2p2www/pages/site/about/media.html:159 +#, python-format +msgid "" +"<a href=\"%(link)s\">Short garlic routing animation</a>\n" +"(Youtube Video)\n" +"Adrian Crenshaw.\n" +msgstr "" +"<a href=\"%(link)s\">Короткий роли о чеÑночной маршрутизации</a>\n" +"(Youtube Video)\n" +"Adrian Crenshaw.\n" + +#: i2p2www/pages/site/about/media.html:167 +msgid "Articles and Interviews" +msgstr "Статьи и интервью" + +#: i2p2www/pages/site/about/media.html:170 +#, python-format +msgid "" +"0x90 Interviewed by DistributedCity\n" +"<a href=\"%(link1)s\">Part 1</a>\n" +"<a href=\"%(link2)s\">Part 2</a>\n" +"July 26, 2002." +msgstr "" +"0x90 в интервью DistributedCity\n" +"<a href=\"%(link1)s\">ЧаÑÑ‚ÑŒ 1</a>\n" +"<a href=\"%(link2)s\">ЧаÑÑ‚ÑŒ 2</a>\n" +"Июль 26, 2002." + +#: i2p2www/pages/site/about/media.html:178 +#, python-format +msgid "" +"0x90 Interviewed by El Pais\n" +"(original in Spanish)\n" +"<a href=\"%(link)s\">English translation</a>\n" +"October 31, 2002." +msgstr "" +"0x90 в интервью El Pais\n" +"(в оригинале на иÑпанÑком)\n" +"<a href=\"%(link)s\">английÑкий перевод</a>\n" +"ОктÑбрь 31, 2002." + +#: i2p2www/pages/site/about/media.html:185 +#, python-format +msgid "" +"<a href=\"%(link)s\">2003 Business Week article referencing " +"invisiblenet</a>" +msgstr "<a href=\"%(link)s\">2003 Business Week ÑÑ‚Ð°Ñ‚ÑŒÑ Ð¾ невидимой Ñети</a>" + +#: i2p2www/pages/site/about/media.html:189 +#, python-format +msgid "" +"<a href=\"%(link)s\">Netzwelt.de article about being anonymous in the " +"Internet</a>\n" +"(German)\n" +"November 2007." +msgstr "" +"<a href=\"%(link)s\">Netzwelt.de ÑÑ‚Ð°Ñ‚ÑŒÑ Ð¾Ð± анонимноÑти в Интернет</a>\n" +"(на немецком)\n" +"ÐоÑбрь 2007." + +#: i2p2www/pages/site/about/media.html:195 +#, python-format +msgid "" +"<a href=\"%(link)s\">zzz interviewed by gulli.com</a>\n" +"March 2009\n" +"<a href=\"%(german)s\">German translation</a>" +msgstr "" + +#: i2p2www/pages/site/about/media.html:202 +#, python-format +msgid "" +"<a href=\"%(mp3)s\">zzz interviewed on the InfoSec Daily Podcast Ep. 454 " +"(mp3)</a>\n" +"August 18, 2011" +msgstr "" +"<a href=\"%(mp3)s\">zzz в интервью на InfoSec Daily Podcast Ep. 454 " +"(mp3)</a>\n" +"ÐвгуÑÑ‚ 18, 2011" + +#: i2p2www/pages/site/about/media.html:207 +#, python-format +msgid "" +"<a href=\"%(link)s\">I2P - Anonymity for the Masses</a>,\n" +"Jonathan Cox,\n" +"November 11, 2011." +msgstr "" +"<a href=\"%(link)s\">I2P - ÐнонимноÑÑ‚ÑŒ Ð´Ð»Ñ Ð’Ñех</a>,\n" +"Jonathan Cox,\n" +"ÐоÑбрь 11, 2011." + +#: i2p2www/pages/site/about/media.html:213 +#, python-format +msgid "" +"<a href=\"%(mp3)s\">zzz and Lance James interviewed on the InfoSec Daily " +"Podcast Ep. 596 (mp3)</a>\n" +"February 16, 2012" +msgstr "" +"<a href=\"%(mp3)s\">zzz и Lance James в интервью на InfoSec Daily Podcast" +" Ep. 596 (mp3)</a>\n" +"Февраль 16, 2012" + +#: i2p2www/pages/site/about/team.html:2 +msgid "Team" +msgstr "Команда" + +#: i2p2www/pages/site/about/team.html:4 +msgid "I2P Project Members" +msgstr "УчаÑтники проекта I2P" + +#: i2p2www/pages/site/about/team.html:5 +#, python-format +msgid "" +"We are a small group of people spread around several continents, working " +"to\n" +"advance different aspects of the project and discussing the design of the" +"\n" +"network.\n" +"<a href=\"%(volunteer)s\">Get involved!</a>" +msgstr "" +"Мы Ð¼Ð°Ð»ÐµÐ½ÑŒÐºÐ°Ñ Ð³Ñ€ÑƒÐ¿Ð¿Ð° людей, раÑÐ¿Ñ€ÐµÐ´ÐµÐ»ÐµÐ½Ð½Ð°Ñ Ð¿Ð¾ неÑкольким континентам, мы " +"работаем над\n" +"продвижением различных чаÑтей проекта и обÑуждаем архитектуру \n" +"Ñети.\n" +"<a href=\"%(volunteer)s\">ПриÑоединÑйтеÑÑŒ!</a>" + +#: i2p2www/pages/site/about/team.html:14 +msgid "Admin" +msgstr "ÐдминиÑтрациÑ" + +#: i2p2www/pages/site/about/team.html:15 +msgid "Project Manager" +msgstr "Менеджер проектов" + +#: i2p2www/pages/site/about/team.html:17 +msgid "point of contact of last resort" +msgstr "контакт Ð´Ð»Ñ ÐºÑ€Ð°Ð¹Ð½Ð¸Ñ… Ñлучаев" + +#: i2p2www/pages/site/about/team.html:20 +msgid "Treasurer" +msgstr "Казначей" + +#: i2p2www/pages/site/about/team.html:22 +msgid "manage donations / accounts / bounties" +msgstr "управлÑет пожертвованиÑми / Ñчетами / премиÑми" + +#: i2p2www/pages/site/about/team.html:25 +msgid "PR manager" +msgstr "PR-менеджер" + +#: i2p2www/pages/site/about/team.html:27 +msgid "press contact, manages public relations and affairs" +msgstr "контакты Ñ Ð¿Ñ€ÐµÑÑой, публичные Ð¾Ñ‚Ð½Ð¾ÑˆÐµÐ½Ð¸Ñ Ð¸ дела" + +#: i2p2www/pages/site/about/team.html:30 +#, python-format +msgid "<a href=\"http://%(forum)s/\">Forum</a> admin" +msgstr "ÐдминиÑтратор <a href=\"http://%(forum)s/\">форума</a>" + +#: i2p2www/pages/site/about/team.html:32 +msgid "manage the public user forum" +msgstr "управлÑет публичным форумом пользователей" + +#: i2p2www/pages/site/about/team.html:35 +msgid "Mirrors admin" +msgstr "ÐдминиÑтратор зеркал" + +#: i2p2www/pages/site/about/team.html:37 +msgid "manage the project mirrors" +msgstr "управлÑет зеркалами проекта" + +#: i2p2www/pages/site/about/team.html:40 +#, python-format +msgid "<a href=\"%(monotone)s\">Monotone</a> guru" +msgstr "Гуру <a href=\"%(monotone)s\">Monotone</a>" + +#: i2p2www/pages/site/about/team.html:42 +msgid "manage the public monotone repositories" +msgstr "управлÑет публичными хранилищами monotone" + +#: i2p2www/pages/site/about/team.html:45 +msgid "Packager; Linux" +msgstr "Упаковщик; Linux" + +#: i2p2www/pages/site/about/team.html:47 +msgid "Linux (Debian/Ubuntu) distribution packager" +msgstr "упаковщик диÑтрибутивов под Linux (Debian/Ubuntu) " + +#: i2p2www/pages/site/about/team.html:50 +msgid "Packager; Windows" +msgstr "Упаковщик; Windows" + +#: i2p2www/pages/site/about/team.html:52 +msgid "Windows installer packager" +msgstr "упаковщик диÑтрибутивов под Windows" + +#: i2p2www/pages/site/about/team.html:55 +msgid "Release Manager" +msgstr "Менеджер по выпуÑку" + +#: i2p2www/pages/site/about/team.html:57 +msgid "Builds and signs the releases" +msgstr "Собирает и подпиÑывает релизы" + +#: i2p2www/pages/site/about/team.html:60 +msgid "Update admin" +msgstr "ÐдминиÑтратор обновлений" + +#: i2p2www/pages/site/about/team.html:62 +msgid "Monitors and recruits in-network update hosts" +msgstr "" + +#: i2p2www/pages/site/about/team.html:65 +msgid "Reseed admin" +msgstr "ÐдминиÑтратор начальных загрузок" + +#: i2p2www/pages/site/about/team.html:67 +msgid "Monitors, advises and recruits reseed hosts" +msgstr "Ðаблюдает, Ñоветует и набирает узлы Ð´Ð»Ñ Ð½Ð°Ñ‡Ð°Ð»ÑŒÐ½Ð¾Ð¹ загрузки" + +#: i2p2www/pages/site/about/team.html:70 +msgid "Security expert" +msgstr "ÐкÑперт по безопаÑноÑти" + +#: i2p2www/pages/site/about/team.html:71 i2p2www/pages/site/about/team.html:76 +#: i2p2www/pages/site/about/team.html:81 i2p2www/pages/site/about/team.html:101 +#: i2p2www/pages/site/about/team.html:138 +#: i2p2www/pages/site/about/team.html:148 +#: i2p2www/pages/site/about/team.html:153 +#: i2p2www/pages/site/about/team.html:158 +#: i2p2www/pages/site/about/team.html:163 +#: i2p2www/pages/site/about/team.html:168 +#: i2p2www/pages/site/about/team.html:206 +#: i2p2www/pages/site/about/team.html:228 +msgid "vacant" +msgstr "открыта ваканÑиÑ" + +#: i2p2www/pages/site/about/team.html:72 +msgid "threat model / crypto expert" +msgstr "ÑкÑперт по моделированию угроз / шифрованию" + +#: i2p2www/pages/site/about/team.html:75 +msgid "User Advocate" +msgstr "ПользовательÑкий Ðдвокат" + +#: i2p2www/pages/site/about/team.html:77 +msgid "gather, prioritize, advocate for user needs" +msgstr "" +"Ñбор Ñведений, раÑÑтановка приоритетов, адвокатÑкие уÑлуги Ð´Ð»Ñ " +"пользователей" + +#: i2p2www/pages/site/about/team.html:80 +msgid "Web Designer" +msgstr "Web-дизайнер" + +#: i2p2www/pages/site/about/team.html:82 +msgid "manage the public project website content design" +msgstr "управление дизайном веб-Ñайта публичного проекта" + +#: i2p2www/pages/site/about/team.html:85 +#, python-format +msgid "<a href=\"%(website)s\">Webserver</a> admin" +msgstr "ÐдминиÑтратор <a href=\"%(website)s\">веб-Ñервера</a>" + +#: i2p2www/pages/site/about/team.html:87 +msgid "manage the public project webservers" +msgstr "управление веб-Ñерверами публичного проекта" + +#: i2p2www/pages/site/about/team.html:90 +#, python-format +msgid "<a href=\"%(website)s\">Website</a> admin" +msgstr "ÐдминиÑтратор <a href=\"%(website)s\">веб-Ñайта</a>" + +#: i2p2www/pages/site/about/team.html:92 +msgid "manage the public project website content" +msgstr "управление Ñодержимым веб-Ñайта публичного проекта" + +#: i2p2www/pages/site/about/team.html:95 +msgid "News Admin" +msgstr "ÐдминиÑтратор новоÑтей" + +#: i2p2www/pages/site/about/team.html:97 +msgid "manage router console news feed" +msgstr "управлÑет лентой новоÑтей конÑоли маршрутизатора" + +#: i2p2www/pages/site/about/team.html:100 +msgid "Director of passion" +msgstr "Директор ÑтраÑти" + +#: i2p2www/pages/site/about/team.html:102 +msgid "community motivator" +msgstr "мотиватор ÑообщеÑтва" + +#: i2p2www/pages/site/about/team.html:106 +msgid "Dev" +msgstr "Разработка" + +#: i2p2www/pages/site/about/team.html:107 +msgid "Core Lead" +msgstr "Главный разработчик Ядра" + +#: i2p2www/pages/site/about/team.html:109 +msgid "lead dev for the SDK and router" +msgstr "ведет разработку SDK и роутера" + +#: i2p2www/pages/site/about/team.html:112 +#, python-format +msgid "<a href=\"http://%(postman)s/\">I2P mail</a> lead" +msgstr "Главный разработчик <a href=\"http://%(postman)s/\">почты I2P</a>" + +#: i2p2www/pages/site/about/team.html:114 +msgid "organize and develop the i2p mail system" +msgstr "организует и разрабатывает почтовую ÑиÑтему i2p" + +#: i2p2www/pages/site/about/team.html:117 +#, python-format +msgid "<a href=\"http://%(i2host)s/\">I2Host</a> lead" +msgstr "Главный разработчик <a href=\"http://%(i2host)s/\">I2Host</a>" + +#: i2p2www/pages/site/about/team.html:119 +msgid "I2Host addressbook application" +msgstr "адреÑÑÐ½Ð°Ñ ÐºÐ½Ð¸Ð³Ð° I2Host" + +#: i2p2www/pages/site/about/team.html:122 +#, python-format +msgid "<a href=\"http://%(bob)s/\">BOB</a> lead" +msgstr "Главный разработчик <a href=\"http://%(bob)s/\">BOB</a>" + +#: i2p2www/pages/site/about/team.html:124 +msgid "Basic Open Bridge" +msgstr "Basic Open Bridge" + +#: i2p2www/pages/site/about/team.html:127 +#, python-format +msgid "<a href=\"http://%(bote)s/\">I2P-Bote</a> lead" +msgstr "Главный разработчик <a href=\"http://%(bote)s/\">I2P-Bote</a>" + +#: i2p2www/pages/site/about/team.html:129 +msgid "I2PBote plugin" +msgstr "модуль I2PBote" + +#: i2p2www/pages/site/about/team.html:132 +#, python-format +msgid "<a href=\"http://%(bob)s/\">Robert</a> lead" +msgstr "Главный разработчик <a href=\"http://%(bob)s/\">Robert</a>" + +#: i2p2www/pages/site/about/team.html:134 +msgid "Robert BitTorrent client" +msgstr "торрент клиент Robert BitTorrent" + +#: i2p2www/pages/site/about/team.html:137 +#, python-format +msgid "<a href=\"http://%(forum)s/viewforum?f=25\">I2Phex</a> lead" +msgstr "Главный разработчик <a href=\"http://%(forum)s/viewforum?f=25\">I2Phex</a>" + +#: i2p2www/pages/site/about/team.html:139 +msgid "I2Phex Gnutella client" +msgstr "клиент I2Phex Gnutella" + +#: i2p2www/pages/site/about/team.html:142 +#, python-format +msgid "<a href=\"http://%(forum)s/viewforum?f=21\">I2PSnark</a> lead" +msgstr "" +"Главный разработчик <a " +"href=\"http://%(forum)s/viewforum?f=21\">I2PSnark</a>" + +#: i2p2www/pages/site/about/team.html:144 +msgid "Maintains the integrated Bittorrent client" +msgstr "Поддерживает интегрированный клиент Bittorrent" + +#: i2p2www/pages/site/about/team.html:147 +#, python-format +msgid "<a href=\"http://%(forum)s/viewforum?f=30\">iMule</a> lead" +msgstr "Главный разработчик <a href=\"http://%(forum)s/viewforum?f=30\">iMule</a>" + +#: i2p2www/pages/site/about/team.html:149 +msgid "eMule client over I2P" +msgstr "клиент eMule через I2P" + +#: i2p2www/pages/site/about/team.html:152 +#, python-format +msgid "<a href=\"http://%(forum)s/viewforum?f=29\">Syndie</a> lead" +msgstr "Главный разработчик <a href=\"http://%(forum)s/viewforum?f=29\">Syndie</a>" + +#: i2p2www/pages/site/about/team.html:154 +msgid "Syndie development" +msgstr "разработка Syndie" + +#: i2p2www/pages/site/about/team.html:157 +msgid "Susimail lead" +msgstr "Главный разработчик Susimail" + +#: i2p2www/pages/site/about/team.html:159 +msgid "Susimail development" +msgstr "разработка Susimail" + +#: i2p2www/pages/site/about/team.html:162 +msgid "Console" +msgstr "КонÑоль" + +#: i2p2www/pages/site/about/team.html:164 +msgid "Router console HTML/CSS design" +msgstr "Дизайн HTML/CSS конÑоли маршрутизатора" + +#: i2p2www/pages/site/about/team.html:167 +msgid "SAM" +msgstr "SAM" + +#: i2p2www/pages/site/about/team.html:169 +msgid "SAM maintainer" +msgstr "Ñопровождение SAM" + +#: i2p2www/pages/site/about/team.html:172 +msgid "I2PCPP lead" +msgstr "Главный разработчик I2PCPP" + +#: i2p2www/pages/site/about/team.html:174 +msgid "C++ Router" +msgstr "C++ Маршрутизатор" + +#: i2p2www/pages/site/about/team.html:177 +msgid "Console Translations" +msgstr "Перевод конÑоли" + +#: i2p2www/pages/site/about/team.html:179 +msgid "Chinese" +msgstr "КитайÑкий" + +#: i2p2www/pages/site/about/team.html:183 +msgid "Dutch" +msgstr "ДатÑкий" + +#: i2p2www/pages/site/about/team.html:187 +msgid "French" +msgstr "ФранцузÑкий" + +#: i2p2www/pages/site/about/team.html:191 +msgid "German" +msgstr "Ðемецкий" + +#: i2p2www/pages/site/about/team.html:195 +msgid "Russian" +msgstr "РуÑÑкий" + +#: i2p2www/pages/site/about/team.html:199 +msgid "Spanish" +msgstr "ИÑпанÑкий" + +#: i2p2www/pages/site/about/team.html:203 +msgid "Arabic" +msgstr "ÐрабÑкий" + +#: i2p2www/pages/site/about/team.html:207 +msgid "Other languages" +msgstr "Другие Ñзыки" + +#: i2p2www/pages/site/about/team.html:210 +msgid "Contributors" +msgstr "Помощники" + +#: i2p2www/pages/site/about/team.html:212 +msgid "fire2pe dev, console enhancements" +msgstr "разработка fire2pe, улучшение конÑоли" + +#: i2p2www/pages/site/about/team.html:216 +msgid "desktopgui, dijjer port" +msgstr "desktopgui, портирование dijjer" + +#: i2p2www/pages/site/about/team.html:220 +msgid "Debian/Ubuntu Packager and PPA maintainer" +msgstr "ДиÑÑ‚Ñ€Ð¸Ð±ÑƒÑ†Ð¸Ñ Debian/Ubuntu и поддержка PPA" + +#: i2p2www/pages/site/about/team.html:224 +msgid "Routerconsole backend and UI work, website revamp, unit tests work" +msgstr "" +"БÑкенд конÑоли маршрутизатора и работа на UI, иÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð¿Ð¾ веб-Ñайту, " +"юнит-теÑтирование" + +#: i2p2www/pages/site/about/team.html:229 +msgid "Help needed on many fronts!" +msgstr "Ðеобходима помощь на многих фронтах работы!" + +#: i2p2www/pages/site/about/team.html:233 +msgid "Past contributors" +msgstr "Также помогали" + +#: i2p2www/pages/site/about/team.html:235 +msgid "I2PTunnel development, ministreaming library" +msgstr "Разработка I2PTunnel, библиотеки минипотоков" + +#: i2p2www/pages/site/about/team.html:239 +msgid "Project lead, Syndie lead" +msgstr "Главный разработчик проекта, главный разработчик Syndie" + +#: i2p2www/pages/site/about/team.html:243 +msgid "Project lead, Syndie lead, I2Phex, support guru" +msgstr "" +"Главный разработчик проекта, главный разработчик Syndie, I2Phex, гуру " +"поддержки" + +#: i2p2www/pages/site/about/team.html:247 +msgid "iMule lead" +msgstr "Главный разработчик iMule" + +#: i2p2www/pages/site/about/team.html:251 +#: i2p2www/pages/site/about/team.html:255 +#: i2p2www/pages/site/about/team.html:259 +msgid "I2Phex work" +msgstr "Разработчик I2Phex" + +#: i2p2www/pages/site/about/team.html:263 +msgid "Python SAM library, attack simulations" +msgstr "Python библиотека SAM, ÑмулÑÑ†Ð¸Ñ Ð°Ñ‚Ð°Ðº" + +#: i2p2www/pages/site/about/team.html:267 +msgid "i2pmail development" +msgstr "разработка i2pmail" + +#: i2p2www/pages/site/about/team.html:271 +msgid "Syndie help" +msgstr "Файл Ñправки Syndie" + +#: i2p2www/pages/site/about/team.html:275 +msgid "i2p mail,susimail and susidns apps" +msgstr "Ð¿Ñ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾Ñ‡Ñ‚Ñ‹ i2p, susimail и susidns" + +#: i2p2www/pages/site/about/team.html:279 +msgid "I2Phex (port of Phex to I2P)" +msgstr "I2Phex (портирование Phex на I2P)" + +#: i2p2www/pages/site/about/team.html:283 +msgid "addressbook,i2p-bt,syndie client" +msgstr "адреÑÑÐ½Ð°Ñ ÐºÐ½Ð¸Ð³Ð°, i2p-bt, клиент syndie" + +#: i2p2www/pages/site/about/team.html:287 +msgid "organize and develop the i2p-bt BitTorrent port" +msgstr "Ð°Ñ€Ð³Ð°Ð½Ð¸Ð·Ð°Ñ†Ð¸Ñ Ð¸ разработка порта i2p-bt BitTorrent" + +#: i2p2www/pages/site/about/team.html:291 +msgid "addressbook, i2p-bt, syndie client development" +msgstr "адреÑÑÐ½Ð°Ñ ÐºÐ½Ð¸Ð³Ð°, i2p-bt, разработка клиента syndie" + +#: i2p2www/pages/site/about/team.html:295 +msgid "encryption and signature routines, I2PIM" +msgstr "задачи по шифрованию и подпиÑанию, I2PIM" + +#: i2p2www/pages/site/about/team.html:299 +msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)" +msgstr "кодирование SAM jython, работа над stasher (DHT) и v2v (VoI2P)" + +#: i2p2www/pages/site/about/team.html:303 +msgid "installer, systray, bogobot" +msgstr "инÑталлÑтор, systray, bogobot" + +#: i2p2www/pages/site/about/team.html:307 +msgid "jbigi development, wiki migration, doc cleanup" +msgstr "разработка jbigi, Ð¼Ð¸Ð³Ñ€Ð°Ñ†Ð¸Ñ wiki, чиÑтка doc" + +#: i2p2www/pages/site/about/team.html:311 +msgid "java debugging and client development on I2PTunnel and the router console" +msgstr "отладка java и разработка клиента I2PTunnel и конÑоли маршрутизатора" + +#: i2p2www/pages/site/about/team.html:315 +msgid "SAM perl module" +msgstr "модуль perl Ð´Ð»Ñ SAM" + +#: i2p2www/pages/site/about/team.html:319 +msgid "i2psnark work" +msgstr "разработка i2psnark" + +#: i2p2www/pages/site/about/team.html:323 +msgid "java cleanup" +msgstr "чиÑтка java" + +#: i2p2www/pages/site/about/team.html:327 +msgid "docs. wiki migration" +msgstr "документациÑ. Ð¼Ð¸Ð³Ñ€Ð°Ñ†Ð¸Ñ wiki" + +#: i2p2www/pages/site/about/team.html:331 +msgid "translations into French" +msgstr "перевод на французкий" + +#: i2p2www/pages/site/about/team.html:335 +msgid "C port of jcpuid" +msgstr "Портирование jcpuid на C " + +#: i2p2www/pages/site/about/team.html:339 +msgid "C# SAM library, pants, fortuna integration" +msgstr "Библиотека C# SAM, pants, интегрирование fortuna" + +#: i2p2www/pages/site/about/team.html:343 +msgid "libSAM" +msgstr "libSAM" + +#: i2p2www/pages/site/about/team.html:347 +#: i2p2www/pages/site/about/team.html:351 +msgid "i2p-bt tracker development" +msgstr "разработка Ñ‚Ñ€Ñкера i2p-bt" + +#: i2p2www/pages/site/about/team.html:355 +msgid "Console and website themes" +msgstr "Темы Ð´Ð»Ñ ÐºÐ¾Ð½Ñоли и веб-Ñайта" + +#: i2p2www/pages/site/about/team.html:358 +msgid "… and many others" +msgstr "… и многие другие" + +#: i2p2www/pages/site/about/performance/future.html:2 +msgid "Future Performance Improvements" +msgstr "ПредÑтоÑщие ÑƒÐ»ÑƒÑ‡ÑˆÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð¸Ð·Ð²Ð¾Ð´Ð¸Ñ‚ÐµÐ»ÑŒÐ½Ð¾Ñти" + +#: i2p2www/pages/site/about/performance/future.html:4 +msgid "August 2010" +msgstr "ÐвгуÑÑ‚ 2010" + +#: i2p2www/pages/site/about/performance/future.html:7 +msgid "" +"There are a few major techniques that can be done to improve the " +"perceived\n" +"performance of I2P - some of the following are CPU related, others " +"bandwidth\n" +"related, and others still are protocol related. However, all of those\n" +"dimensions affect the latency, throughput, and perceived performance of " +"the\n" +"network, as they reduce contention for scarce resources. This list is of" +" course\n" +"not comprehensive, but it does cover the major ones that are seen." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:15 +#: i2p2www/pages/site/about/performance/index.html:106 +#, python-format +msgid "" +"For past performance improvements see the <a href=\"%(history)s\">\n" +"Performance History</a>." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:20 +msgid "Better peer profiling and selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:21 +#, python-format +msgid "" +"Probably one of the most important parts of getting faster performance " +"will\n" +"be improving how routers choose the peers that they build their tunnels " +"through\n" +"- making sure they don't use peers with slow links or ones with fast " +"links that\n" +"are overloaded, etc. In addition, we've got to make sure we don't expose" +"\n" +"ourselves to a <a href=\"%(sybilpdf)s\">Sybil</a> attack\n" +"from a powerful adversary with lots of fast machines." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:30 +msgid "Network database tuning" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:31 +msgid "" +"We're going to want to be more efficient with the network database's " +"healing\n" +"and maintenance algorithms - rather than constantly explore the keyspace " +"for new\n" +"peers - causing a significant number of network messages and router load " +"- we\n" +"can slow down or even stop exploring until we detect that there's " +"something new\n" +"worth finding (e.g. decay the exploration rate based upon the last time " +"someone\n" +"gave us a reference to someone we had never heard of). We can also do " +"some\n" +"tuning on what we actually send - how many peers we bounce back (or even " +"if we\n" +"bounce back a reply), as well as how many concurrent searches we perform." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:42 +msgid "Session Tag Tuning and Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:43 +#, python-format +msgid "" +"The way the <a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> " +"algorithm\n" +"works is by managing a set of random one-time-use 32 byte arrays, and " +"expiring\n" +"them if they aren't used quickly enough. If we expire them too soon, " +"we're\n" +"forced to fall back on a full (expensive) ElGamal encryption, but if we " +"don't\n" +"expire them quickly enough, we've got to reduce their quantity so that we" +" don't\n" +"run out of memory (and if the recipient somehow gets corrupted and loses " +"some\n" +"tags, even more encryption failures may occur prior to detection). With " +"some\n" +"more active detection and feedback driven algorithms, we can safely and " +"more\n" +"efficiently tune the lifetime of the tags, replacing the ElGamal " +"encryption with\n" +"a trivial AES operation." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:55 +#, python-format +msgid "" +"Additional ideas for improving Session Tag delivery are described on the\n" +"<a href=\"%(elgamalaes)s#future\">ElGamal/AES+SessionTag page</a>." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:61 +msgid "Migrate sessionTag to synchronized PRNG" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:62 +#, python-format +msgid "" +"Right now, our <a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> \n" +"algorithm works by tagging each encrypted message with a unique random \n" +"32 byte nonce (a \"session tag\"), identifying that message as being " +"encrypted \n" +"with the associated AES session's key. This prevents peers from " +"distinguishing \n" +"messages that are part of the same session, since each message has a " +"completely \n" +"new random tag. To accomplish this, every few messages bundle a whole \n" +"new set of session tags within the encrypted message itself, " +"transparently \n" +"delivering a way to identify future messages. We then have to keep track" +" \n" +"of what messages are successfully delivered so that we know what tags \n" +"we may use." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:74 +msgid "" +"This works fine and is fairly robust, however it is inefficient in terms" +" \n" +"of bandwidth usage, as it requires the delivery of these tags ahead of \n" +"time (and not all tags may be necessary, or some may be wasted, due to \n" +"their expiration). On average though, predelivering the session tag costs" +" \n" +"32 bytes per message (the size of a tag). As Taral suggested though, that" +" \n" +"size can be avoided by replacing the delivery of the tags with a " +"synchronized \n" +"PRNG - when a new session is established (through an ElGamal encrypted \n" +"block), both sides seed a PRNG for use and generate the session tags on \n" +"demand (with the recipient precalculating the next few possible values \n" +"to handle out of order delivery)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:87 +msgid "Longer lasting tunnels" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:88 +msgid "" +"The current default tunnel duration of 10 minutes is fairly arbitrary, " +"though\n" +"it \"feels okay\". Once we've got tunnel healing code and more effective" +" failure\n" +"detection, we'll be able to more safely vary those durations, reducing " +"the\n" +"network and CPU load (due to expensive tunnel creation messages)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:95 +msgid "" +"This appears to be an easy fix for high load on the big-bandwidth " +"routers, but\n" +"we should not resort to it until we've tuned the tunnel building " +"algorithms further.\n" +"However, the 10 minute tunnel lifetime is hardcoded in quite a few " +"places,\n" +"so substantial effort would be required to change the duration.\n" +"Also, it would be difficult to maintain backward compatibility with such " +"a change." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:102 +msgid "" +"Currently, since the network average tunnel build success rate is fairly " +"high,\n" +"there are no current plans to extend tunnel lifetime." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:108 +msgid "Adjust the timeouts" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:109 +msgid "" +"Yet another of the fairly arbitrary but \"okay feeling\" things we've got" +" are the\n" +"current timeouts for various activities. Why do we have a 60 second " +"\"peer\n" +"unreachable\" timeout? Why do we try sending through a different tunnel " +"that a\n" +"LeaseSet advertises after 10 seconds? Why are the network database " +"queries\n" +"bounded by 60 or 20 second limits? Why are destinations configured to " +"ask for a\n" +"new set of tunnels every 10 minutes? Why do we allow 60 seconds for a " +"peer to\n" +"reply to our request that they join a tunnel? Why do we consider a " +"tunnel that\n" +"doesn't pass our test within 60 seconds \"dead\"?" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:119 +msgid "" +"Each of those imponderables can be addressed with more adaptive code, as " +"well\n" +"as tunable parameters to allow for more appropriate tradeoffs between\n" +"bandwidth, latency, and CPU usage." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:125 +msgid "Full streaming protocol improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:128 +msgid "" +"Perhaps re-enable the interactive stream profile (the \n" +"current implementation only uses the bulk stream profile)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:134 +msgid "" +"Client level bandwidth limiting (in either or both directions on a " +"stream, \n" +"or possibly shared across multiple streams). This would be in addition to" +" \n" +"the router's overall bandwidth limiting, of course." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:141 +msgid "" +"Access control lists (only allowing streams to or from certain other " +"known \n" +"destinations)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:147 +msgid "" +"Web controls and monitoring the health of the various streams, as well \n" +"as the ability to explicitly close or throttle them." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:153 +#, python-format +msgid "" +"Additional ideas for improving the streaming library are described on the" +"\n" +"<a href=\"%(streaming)s#future\">streaming library page</a>." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:2 +msgid "Performance History" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:4 +#, python-format +msgid "" +"Notable performance improvements have been made using the techniques " +"below.\n" +"There is more to do, see the <a href=\"%(performance)s\">Performance</a> " +"page\n" +"for current issues and thoughts." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:10 +msgid "Native math" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:11 +#: i2p2www/pages/site/about/performance/history.html:67 +#: i2p2www/pages/site/about/performance/history.html:82 +#: i2p2www/pages/site/about/performance/history.html:105 +#: i2p2www/pages/site/about/performance/history.html:133 +msgid "implemented" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:12 +#, python-format +msgid "" +"When I last profiled the I2P code, the vast majority of time was spent " +"within\n" +"one function: java.math.BigInteger's\n" +"<a href=\"%(modpow)s\">modPow</a>.\n" +"Rather than try to tune this method, we'll call out to\n" +"<a href=\"%(gmp)s\">GNU MP</a> - an insanely fast math library\n" +"(with tuned assembler for many architectures). (<i>Editor: see\n" +"<a href=\"%(jbigi)s\">NativeBigInteger for faster public key " +"cryptography</a></i>)" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:23 +msgid "" +"\n" +"ugha and duck are working on the C/JNI glue code, and the existing java " +"code\n" +"is already deployed with hooks for that whenever its ready. Preliminary " +"results\n" +"look fantastic - running the router with the native GMP modPow is " +"providing over\n" +"a 800% speedup in encryption performance, and the load was cut in " +"half. This\n" +"was just on one user's machine, and things are nowhere near ready for " +"packaging\n" +"and deployment, yet." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:32 +msgid "Garlic wrapping a \"reply\" LeaseSet" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:33 +msgid "implemented but needs tuning" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:34 +msgid "" +"This algorithm tweak will only be relevant for applications that want " +"their\n" +"peers to reply to them (though that includes everything that uses " +"I2PTunnel or\n" +"mihi's ministreaming lib):" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:39 +msgid "" +"Previously, when Alice sent Bob a message, when Bob replied he had to do " +"a\n" +"lookup in the network database - sending out a few requests to get " +"Alice's\n" +"current LeaseSet. If he already has Alice's current LeaseSet, he can " +"instead\n" +"just send his reply immediately - this is (part of) why it typically " +"takes a\n" +"little longer talking to someone the first time you connect, but " +"subsequent\n" +"communication is faster. Currently - for all clients - we wrap\n" +"the sender's current LeaseSet in the garlic that is delivered to the " +"recipient,\n" +"so that when they go to reply, they'll <i>always</i> have the LeaseSet " +"locally\n" +"stored - completely removing any need for a network database lookup on " +"replies.\n" +"This trades off a large portion of the sender's bandwidth for that faster" +" reply.\n" +"If we didn't do this very often,\n" +"overall network bandwidth usage would decrease, since the recipient " +"doesn't\n" +"have to do the network database lookup." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:54 +msgid "" +"For unpublished LeaseSets such as \"shared clients\", this is the only " +"way to\n" +"get the LeaseSet to Bob. Unfortunately this bundling every time adds\n" +"almost 100% overhead to a high-bandwidth connection, and much more to" +"\n" +"a connection with smaller messages." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:60 +msgid "" +"Changes scheduled for release 0.6.2 will bundle the LeaseSet only when\n" +"necessary, at the beginning of a connection or when the LeaseSet changes." +"\n" +"This will substantially reduce the total overhead of I2P messaging." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:66 +msgid "More efficient TCP rejection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:68 +msgid "" +"At the moment, all TCP connections do all of their peer validation after\n" +"going through the full (expensive) Diffie-Hellman handshaking to " +"negotiate a\n" +"private session key. This means that if someone's clock is really wrong," +" or\n" +"their NAT/firewall/etc is improperly configured (or they're just running " +"an\n" +"incompatible version of the router), they're going to consistently " +"(though not\n" +"constantly, thanks to the shitlist) cause a futile expensive " +"cryptographic\n" +"operation on all the peers they know about. While we will want to keep " +"some\n" +"verification/validation within the encryption boundary, we'll want to " +"update the\n" +"protocol to do some of it first, so that we can reject them cleanly\n" +"without wasting much CPU or other resources." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:81 +msgid "Adjust the tunnel testing" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:83 +msgid "" +"Rather than going with the fairly random scheme we have now, we should " +"use a\n" +"more context aware algorithm for testing tunnels. e.g. if we already " +"know its\n" +"passing valid data correctly, there's no need to test it, while if we " +"haven't\n" +"seen any data through it recently, perhaps its worthwhile to throw some " +"data its\n" +"way. This will reduce the tunnel contention due to excess messages, as " +"well as\n" +"improve the speed at which we detect - and address - failing tunnels." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:92 +msgid "Persistent Tunnel / Lease Selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:93 +msgid "" +"Outbound tunnel selection implemented in 0.6.1.30, inbound lease " +"selection \n" +"implemented in release 0.6.2." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:97 +msgid "" +"Selecting tunnels and leases at random for every message creates a large" +" \n" +"incidence of out-of-order delivery, which prevents the streaming lib from" +" \n" +"increasing its window size as much as it could. By persisting with the \n" +"same selections for a given connection, the transfer rate is much faster." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:104 +msgid "Compress some data structures" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:106 +msgid "" +"The I2NP messages and the data they contain is already defined in a " +"fairly\n" +"compact structure, though one attribute of the RouterInfo structure is " +"not -\n" +"\"options\" is a plain ASCII name = value mapping. Right now, we're " +"filling it\n" +"with those published statistics - around 3300 bytes per peer. Trivial to" +"\n" +"implement GZip compression would nearly cut that to 1/3 its size, and " +"when you\n" +"consider how often RouterInfo structures are passed across the network, " +"that's\n" +"significant savings - every time a router asks another router for a " +"networkDb\n" +"entry that the peer doesn't have, it sends back 3-10 RouterInfo of them." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:117 +msgid "Update the ministreaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:118 +msgid "replaced by full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:119 +msgid "" +"Currently mihi's ministreaming library has a fairly simple stream " +"negotiation\n" +"protocol - Alice sends Bob a SYN message, Bob replies with an ACK " +"message, then\n" +"Alice and Bob send each other some data, until one of them sends the " +"other a\n" +"CLOSE message. For long lasting connections (to an IRC server, for " +"instance),\n" +"that overhead is negligible, but for simple one-off request/response " +"situations\n" +"(an HTTP request/reply, for instance), that's more than twice as many " +"messages as\n" +"necessary. If, however, Alice piggybacked her first payload in with the " +"SYN\n" +"message, and Bob piggybacked his first reply with the ACK - and perhaps " +"also\n" +"included the CLOSE flag - transient streams such as HTTP requests could " +"be\n" +"reduced to a pair of messages, instead of the " +"SYN+ACK+request+response+CLOSE." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:132 +msgid "Implement full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:134 +msgid "" +"The ministreaming protocol takes advantage of a poor design decision in " +"the\n" +"I2P client protocol (I2CP) - the exposure of \"mode=GUARANTEED\", " +"allowing what\n" +"would otherwise be an unreliable, best-effort, message based protocol to " +"be used\n" +"for reliable, blocking operation (under the covers, its still all " +"unreliable and\n" +"message based, with the router providing delivery guarantees by garlic " +"wrapping\n" +"an \"ACK\" message in with the payload, so once the data gets to the " +"target, the\n" +"ACK message is forwarded back to us [through tunnels, of course])." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:143 +#, python-format +msgid "" +"As I've <a href=\"%(link)s\">said</a>, having\n" +"I2PTunnel (and the ministreaming lib) go this route was the best thing " +"that\n" +"could be done, but more efficient mechanisms are available. When we rip " +"out the\n" +"\"mode=GUARANTEED\" functionality, we're essentially leaving ourselves " +"with an\n" +"I2CP that looks like an anonymous IP layer, and as such, we'll be able to" +"\n" +"implement the streaming library to take advantage of the design " +"experiences of\n" +"the TCP layer - selective ACKs, congestion detection, nagle, etc." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:2 +msgid "Performance" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:5 +msgid "" +"How does I2P work, why is it slow, and why does it not use my full " +"bandwidth?" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:7 +msgid "" +"Probably one of the most frequent things people ask is \"how fast is " +"I2P?\",\n" +"and no one seems to like the answer - \"it depends\". After trying out " +"I2P, the\n" +"next thing they ask is \"will it get faster?\", and the answer to that is" +" a most\n" +"emphatic <b>yes</b>." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:14 +msgid "" +"I2P is a full dynamic network. Each client is known to other nodes and " +"tests local known nodes for reachability and capacity.\n" +"Only reachable and capable nodes are saved to a local NetDB (This is " +"generally only a portion of the network, around 500-1000).\n" +"When I2P builds tunnels, it selects the best resource from this pool. For" +" example, a small subset of 20-50 nodes are only available to build " +"tunnels with.\n" +"Because testing happens every minute, the pool of used nodes changes " +"every minute.\n" +"Each I2P node knows a different part of the net, meaning that each router" +" has a different set of I2P nodes to be used for tunnels.\n" +"Even if two routers have the same subset of known nodes, the tests for " +"reachability and capacity will likely show different results, as the " +"other routers could be under load just as one router tests, but be free " +"if the second router tests." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:23 +msgid "" +"The above describes why each I2P node has different nodes to build " +"tunnels.\n" +"Because every I2P node has a different latency and bandwith, tunnels " +"(which are built via those nodes) have different latency and bandwidth " +"values.\n" +"And because every I2P node has different tunnels built, no two I2P nodes " +"have the same tunnel sets." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:29 +msgid "" +"A server/client is known as a \"destination\" and each destination has at" +" least one inbound and one outbound tunnel. The default is 3 hops per " +"tunnel.\n" +"This adds up to 12 hops (aka 12 different I2P nodes) for a full roundtrip" +" client-server-client." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:34 +msgid "" +"Each data package is sent through 6 other I2P nodes until it reaches the " +"server:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:40 +msgid "and on way back 6 different I2P nodes:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:47 +msgid "" +"As most traffic on I2P (www, torrent,...) needs ack packages until new " +"data is sent, it needs to wait until a ack package returns from the " +"server.\n" +"In the end: send data, wait for ack, send more data, wait for ack,..\n" +"As the RTT (RoundTripTime) adds up from the latency of each individual " +"I2P node and each connection on this roundtrip, it takes usually 1-3 " +"seconds until a ack package comes back to the client.\n" +"With some internals of TCP and I2P transport, a data package has a " +"limited size and cannot be as large as we want it to be.\n" +"Together these conditions set a limit of max bandwidth per tunnel of " +"20-50 kbyte/sec.\n" +"But if ONLY ONE hop in the tunnel has only 5 kb/sec bandwidth to spend, " +"the whole tunnel is limited to 5 kb/sec, independent of the \n" +"latency and other limitations." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:57 +msgid "" +"Due to encryption used and other setups in I2P (howto built up tunnels, " +"latency, ...) it is quite expensive in CPU time to build a tunnel. This " +"is \n" +"why a destination is only allowed to have a max of 6 IN and 6 OUT tunnels" +" to transport data. With a max of 50 kb/sec per tunnel, a destination " +"could \n" +"use roughly 300 kb/sec traffic combined ( in reality it could be more if " +"shorter tunnels are used with low or no anonymity available).\n" +"Used tunnels are discarded every 10 minutes and new ones are built up.\n" +"This change of tunnels (and sometimes clients that shutdown hard due to " +"usage of \"shut down at once\" or situations where there is power loss) " +"does \n" +"sometimes break tunnels and connections, as seen on the IRC2P Network in " +"loss of connection (ping timeout) or on when using eepget." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:66 +msgid "" +"With a limited set of destinations and a limited set of tunnels per " +"destination, one I2P node only uses a limited set of tunnels across other" +" I2P nodes.\n" +"For example, if an I2P node is \"hop1\" in the small example above, we " +"only see 1 participating tunnel originating from the client.\n" +"If we sum up the whole I2P network, only a rather limited number of " +"participating tunnels could be built with a limited amount of bandwidth " +"all together.\n" +"If one distributes these limited numbers across the number of I2P nodes, " +"there is only a fraction of available bandwidth/capacity available for " +"use." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:73 +msgid "" +"To remain anonymous one router should not be used by the whole network " +"for building tunnels.\n" +"If one router does act as a tunnel router for ALL I2P nodes, it becomes a" +" very real central point of failure as well as a central point to grab " +"IPs and data from the clients. This is not good.\n" +"I2P attempts to spread the load across a lot of I2P nodes because of this" +" reason." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:79 +msgid "" +"Another point is the full mesh network. Each connection hop-hop utilizes " +"one TCP or UDP connection on the I2P nodes. With 1000 connections, one " +"sees \n" +"1000 TCP connections. That is quite a lot and some home and small office " +"routers (DSL, cable,..) only allow a small number of connections (or just" +" go mad if you use more than X connections).\n" +"I2P tries to limit these connections to be under 1500 per UDP and per TCP" +" type.\n" +"This limits the amount of traffic routed across your I2P node as well." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:86 +msgid "" +"In summary, I2P is very complex and there is no easy way to pinpoint why " +"your node is not used.\n" +"If your node is reachable and has a bandwidth setting of >128 kbyte/sec " +"shared and is reachable 24/7, it should be used after some time for " +"participating traffic.\n" +"If it is down in between, the testing of your I2P node done by other " +"nodes will tell them: you are not reachable. This blocks your node for at" +" least \n" +"24h on other nodes. So, the other nodes which tested you as down will not" +" use your node for 24h for building tunnels. This is why your traffic " +"will \n" +"be lower after a restart/shutdown for a minimum of 24h." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:94 +msgid "" +"Also: other I2P nodes needs to know your I2P router to test it for " +"reachability and capacity. It takes time for other nodes to get known to " +"your node. \n" +"It will be faster if you use I2P and build more tunnels, e.g. use a " +"torrent or www for some time." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:99 +msgid "Performance Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:101 +#, python-format +msgid "" +"For possible future performance improvements see\n" +"<a href=\"%(future)s\">Future Performance Improvements</a>." +msgstr "" + diff --git a/i2p2www/translations/ru_RU/LC_MESSAGES/blog.po b/i2p2www/translations/ru_RU/LC_MESSAGES/blog.po index 04c66b246..b394e559d 100644 --- a/i2p2www/translations/ru_RU/LC_MESSAGES/blog.po +++ b/i2p2www/translations/ru_RU/LC_MESSAGES/blog.po @@ -4,14 +4,16 @@ # # Translators: # keedley <zhopa@mita.pp.ru>, 2013 +# sassy <sassy.but.classic@gmail.com>, 2013 # Ðрефьев Ð”ÐµÐ½Ð¸Ñ <jujjer@gmail.com>, 2013 +# Narengoyn <narengoyn@gmail.com>, 2013 msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" "POT-Creation-Date: 2013-09-30 21:40+0000\n" -"PO-Revision-Date: 2013-09-30 21:43+0000\n" -"Last-Translator: str4d <str4d@i2pmail.org>\n" +"PO-Revision-Date: 2013-10-22 15:05+0000\n" +"Last-Translator: sassy <sassy.but.classic@gmail.com>\n" "Language-Team: Russian (Russia) " "(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " @@ -228,8 +230,8 @@ msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35 msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" msgstr "" -"ИÑправлены проблемы в UDP Ð´Ð»Ñ Ð¼Ð°Ñ€ÑˆÑ€ÑƒÑ‚Ð¸Ð·Ð°Ñ‚Ð¾Ñ€Ð¾Ð² Ñ ÑƒÐ¼ÐµÐ½ÑŒÑˆÐµÐ½Ð½Ñ‹Ð¼ MTU, " -"напримерн на VPN" +"ИÑправлены проблемы в UDP Ð´Ð»Ñ Ð¼Ð°Ñ€ÑˆÑ€ÑƒÑ‚Ð¸Ð·Ð°Ñ‚Ð¾Ñ€Ð¾Ð² Ñ ÑƒÐ¼ÐµÐ½ÑŒÑˆÐµÐ½Ð½Ñ‹Ð¼ MTU, например" +" на VPN" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36 msgid "Fix i2psnark bug that prevented a completion announcement to the tracker" @@ -632,6 +634,12 @@ msgid "" "with i2psnark. If this doesn't work, it should fall back to standard in-" "network HTTP update." msgstr "" +"Ð’ Ñтом цикле обновлений 1% o Ñлучайных роутеров (Ð¿Ð»ÑŽÑ Ð²Ñе роутеры, " +"работающие на\n" +"верÑии Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²) будут пытатьÑÑ Ð¾Ð±Ð½Ð¾Ð²Ð¸Ñ‚ÑŒÑÑ Ñ‡ÐµÑ€ÐµÐ· " +"ÑкÑпериментальный внетриÑетевой bittorent\n" +"Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ i2psnark. ЕÑли Ñто не Ñработает, обновление должно произойти " +"через Ñтандартный внутриÑетевой HTTP." #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27 msgid "Defenses and Bug Fixes" @@ -1098,7 +1106,7 @@ msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65 msgid "Don't install as a service on Windows by default" -msgstr "" +msgstr "Ðе уÑтанавливать в качеÑтве ÑервиÑа Windows по умолчанию" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66 msgid "Reduce transport idle timeouts" @@ -1114,7 +1122,7 @@ msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69 msgid "IE 10 support" -msgstr "" +msgstr "Поддержка IE 10" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70 msgid "" @@ -1214,15 +1222,22 @@ msgid "" "also have anonymity improvements including padding of SSU packets and " "longer router private keys." msgstr "" +"0.9.8 включает долгожданную поддержку IPv6. Она включена по умолчанию, " +"но, конечно же, вам нужен публичный IPv6 адреÑ, чтобы иÑпользовать её. " +"ÐаÑтраиваетÑÑ Ð²Ð¾ вкладке наÑтроек \"Ñеть\" в вашей конÑоли. Мы также " +"уÑилили анонимноÑÑ‚ÑŒ, Ð²ÐºÐ»ÑŽÑ‡Ð°Ñ Ð¼Ð½Ð¾Ð³Ð¾Ñлойные SSU пакеты и более длинные " +"закрытые ключи роутера. " #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11 #, python-format msgid "30% of you will update via in-network torrent in this update cycle." msgstr "" +"Ð’ Ñтом цикле обновлений 30% o из Ð²Ð°Ñ Ð±ÑƒÐ´ÑƒÑ‚ обновлены через внутриÑетевой " +"торрент-клиент." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13 msgid "IPv6 Details" -msgstr "" +msgstr "ПодробноÑти об IPv6." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15 msgid "" @@ -1234,6 +1249,11 @@ msgid "" " in \n" "the router console. If IPv6 is causing problems you may disable it there." msgstr "" +"IPv6 включён и предпочитаетÑÑ Ð¿Ð¾ умлочанию. ЕÑли у Ð²Ð°Ñ ÐµÑÑ‚ÑŒ публичный " +"IPv6 адреÑ\n" +"и вы ÑоединÑетеÑÑŒ Ñ Ð´Ñ€ÑƒÐ³Ð¸Ð¼ роутером Ñ Ð¿ÑƒÐ±Ð»Ð¸Ñ‡Ð½Ñ‹Ð¼ IPv6 адреÑом, они\n" +"ÑоединÑÑ‚ÑÑ Ñ‡ÐµÑ€ÐµÐ· IPv6. Ð’ /confignet в конÑоли роутера - Ð½Ð¾Ð²Ð°Ñ ÑекциÑ\n" +" наÑтройки IPv6. ЕÑли IPv6 вызывает проблемы, вы можете отключить его там." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22 msgid "" @@ -1252,6 +1272,22 @@ msgid "" "we recommend that you use only one IPv4 and one IPv6 address. There are\n" "bugs still to be fixed with multiple addresses of each type." msgstr "" +"Как чаÑÑ‚ÑŒ уÑилий в облаÑти Ñ€Ð°Ð·Ð²Ð¸Ñ‚Ð¸Ñ IPv6, I2P теперь поддерживает " +"множеÑтвенные\n" +"публичные IP адреÑа. ЕÑли у Ð²Ð°Ñ ÐµÑÑ‚ÑŒ множеÑтвенные публичные IP адреÑа " +"(IPv4, IPv6,\n" +"или оба), вы можете включить или выключить каждый из них в /confignet. По" +"\n" +"умолчанию, иÑпользуетÑÑ Ñначала IPv4, а IPv6 адреÑа к нему обращаютÑÑ. " +"ЕÑли у Ð²Ð°Ñ ÐµÑÑ‚ÑŒ\n" +"множеÑтвенные адреÑа, вам Ñтоит проверить наÑтройки в /confignet и " +"поправить\n" +"их, еÑли необходимо.\n" +"Заметьте, что в то Ð²Ñ€ÐµÐ¼Ñ ÐºÐ°Ðº вы можете включить множеÑтвенные IPv4 и IPv6" +" адреÑа в /confignet,\n" +"мы рекомендуем иÑпользовать только один IPv4 и один IPv6 адреÑа. Ð’ÑÑ‘ ещё\n" +"еÑÑ‚ÑŒ ошибки Ñ Ð¼Ð½Ð¾Ð¶ÐµÑтвенными адреÑами каждого типа, которые нужно " +"иÑправить." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34 msgid "" @@ -1264,10 +1300,19 @@ msgid "" "and disable it necessary. Please report any bugs on \n" "http://trac.i2p2.i2p." msgstr "" +"Ð’ то Ð²Ñ€ÐµÐ¼Ñ ÐºÐ°Ðº поддержка IPv6 проектировалаÑÑŒ и разрабатывалаÑÑŒ в течение" +" неÑкольких лет, она\n" +"была протеÑтирована только ограниченным количеÑтвом пользователей и вÑÑ‘ " +"ещё на Ñтадии беты.\n" +"ЕÑли у Ð²Ð°Ñ ÐµÑÑ‚ÑŒ публичный IPv6 адреÑ, пожалуйÑта, проверÑйте ваш " +"маршрутизатор и логи на предмет проблем,\n" +"и отключите его, еÑли необходимо. ПожалуйÑта, Ñообщайте о любых ошибках " +"на\n" +"http://trac.i2p2.i2p" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42 msgid "Rekeying Details" -msgstr "" +msgstr "ПодробноÑти о Подробном вводе. " #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44 msgid "" @@ -1284,6 +1329,15 @@ msgid "" "released. \n" "Please be patient and things should start to improve after a few days." msgstr "" +"Ð”Ð»Ñ Ñ‚ÐµÑ… из ваÑ, кто запуÑкает I2P на быÑтром аппаратном обеÑпечении\n" +" (в оÑновном, 64-битном x86), маршрутизатор Ñгенерирует новый профиль\n" +"иÑÐ¿Ð¾Ð»ÑŒÐ·ÑƒÑ Ð±Ð¾Ð»ÐµÐµ длинные ключи. Ðто в значительной Ñтепени Ñократит\n" +"ваш транзитный трафик на 48 чаÑов или более, пока ваш маршрутизатор\n" +"ре-интегрируетÑÑ Ð² Ñеть. По причине новых ключей, большого количеÑтва\n" +"торрент-обновлений и недавнего роÑта Ñети мы ожидаем ÑущеÑтвенных\n" +"Ñбоев в Ñети в течение недели или более поÑле выпуÑка обновлениÑ.\n" +"ПожалуйÑта, будьте терпеливы: вÑÑ‘ должно начать улучшатьÑÑ Ñ‡ÐµÑ€ÐµÐ·\n" +"неÑколько дней." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54 msgid "" @@ -1296,6 +1350,15 @@ msgid "" "We will evaluate the network performace before deciding whether to\n" "change the key length on slower hardware in a future release." msgstr "" +"Ðти Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð´Ð»Ñ Ð½ÐµÐºÐ¾Ñ‚Ð¾Ñ€Ñ‹Ñ… из Ð²Ð°Ñ Ð¼Ð¾Ð³ÑƒÑ‚ привеÑти к более выÑокой\n" +"нагрузке на процеÑÑор. Мы делаем вÑÑ‘ возможное, чтобы повыÑить " +"ÑффективноÑÑ‚ÑŒ,\n" +"но более выÑокий уровень безопаÑноÑти обычно требует больше раÑчётов.\n" +"БыÑтродейÑтвие также может быть низким в течение первой недели\n" +"из-за оттока Ñети.\n" +"Мы оценим производительноÑÑ‚ÑŒ Ñети, прежде чем принимать решение об\n" +"изменении длины ключа на более медленном оборудовании в\n" +"будущих релизах." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63 msgid "" @@ -1305,10 +1368,14 @@ msgid "" "the \n" "network is still performing fairly well, so keep spreading the word." msgstr "" +"Мы переживаем быÑтрый роÑÑ‚ Ñети в поÑдление неÑколько недель,\n" +"который вызывает у некоторых проблемы, оÑобенно по выходным.\n" +"Однако, Ñеть вÑÑ‘ ещё работает доÑтаточно хорошо, так что продолжайте\n" +"раÑпроÑтранÑÑ‚ÑŒ информацию." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69 msgid "More Changes Coming" -msgstr "" +msgstr "Впереди Больше Изменений." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71 msgid "" @@ -1324,10 +1391,22 @@ msgid "" "in \n" "minimum requirements will be announced well in advance." msgstr "" +"Мы находимÑÑ Ð½Ð° начальной Ñтадии Ð¿Ñ€Ð¾ÐµÐºÑ‚Ð¸Ñ€Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¾Ñновных изменений\n" +"Ð´Ð»Ñ ÑƒÑÐ¸Ð»ÐµÐ½Ð¸Ñ Ð½Ð°ÑˆÐµÐ³Ð¾ шифрованиÑ. Более Ñильное шифрование будет " +"иÑпользовать\n" +"больше реÑурÑов процеÑÑора и возможно потребует Java 7 JRE как минимум. " +"Мы\n" +"понимаем, что вы хотите запуÑкать I2P на маломощном и/или Ñтаром " +"оборудовании.\n" +"Мы прилагаем вÑе уÑилиÑ, что уменьшить неудобÑтва, но Ð½ÐµÐºÐ¾Ñ‚Ð¾Ñ€Ð°Ñ Ð¿Ð¾Ñ‚ÐµÑ€Ñ\n" +"быÑтродейÑÑ‚Ð²Ð¸Ñ Ð½ÐµÐ¸Ð·Ð±ÐµÐ¶Ð½Ð°. Кроме того, Java 5 и 6 более не поддерживаютÑÑ\n" +"Oracle. Ð¡ÐµÐ¹Ñ‡Ð°Ñ Ñамое Ð²Ñ€ÐµÐ¼Ñ Ð¿ÐµÑ€ÐµÐ¹Ñ‚Ð¸ на Java 7. Любые Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð² " +"минимальных\n" +"требованиÑÑ… будут анонÑированы заранее." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81 msgid "New Website" -msgstr "" +msgstr "Ðовый ВебÑайт" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83 msgid "" @@ -1337,10 +1416,15 @@ msgid "" "contribute to the new website translations on Transifex, especially the \n" "website_priority resource." msgstr "" +"ПоÑле героичеÑких уÑилий str4d предварительный проÑмотр\n" +"нового Ñайта доÑтупен на http://i2hq.srv.i2p2.de. Мы надеемÑÑ Ñкоро \n" +"увидеть его вживую на https://geti2p.net и http://www.i2p2.i2p.\n" +"ПожалуйÑта, Ñделайте Ñвой вклад в новый перевод вебÑайта на \n" +"Transifex, оÑобенно в разделе website_priority." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91 msgid "Community Participation" -msgstr "" +msgstr "УчаÑтие в СообщеÑтве" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93 msgid "" @@ -1351,54 +1435,71 @@ msgid "" "It's great to see people participating at these events and representing " "I2P." msgstr "" +"Ð’ начале авгуÑта hottuna и zzz принимали учаÑтие в DEFCON 21 в Ð›Ð°Ñ " +"ВегаÑе.\n" +"Ð’ минувшие выходные echelon поучаÑтвовал в конференции CTS IV в Берлине,\n" +"а psi - в хакфеÑте Tahoe-LAFS на GNU 30 в Кембридже, штат МаÑÑачуÑетÑ.\n" +"Ðекоторые из Ð½Ð°Ñ Ð±ÑƒÐ´ÑƒÑ‚ на 30C3 в Гамбурге в Ñтом году.\n" +"Ðто клаÑÑно - видеть людей, учаÑтвующих в Ñтих мероприÑтиÑÑ… и \n" +"предÑтавлÑющих I2P." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105 msgid "IPv6 support for both NTCP and SSU" -msgstr "" +msgstr "Поддержка IPv6 Ð´Ð»Ñ Ð¾Ð±Ð¾Ð¸Ñ… NTCP и SSU" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109 msgid "SSU protocol obfuscation by adding random padding" -msgstr "" +msgstr "Затемнение протокола SSU добавлением Ñлучайного наполнениÑ" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110 msgid "Longer encryption and DH private keys for users on faster platforms" msgstr "" +"Более длинные ключи ÑˆÐ¸Ñ„Ñ€Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¸ закрытые ключи DH Ð´Ð»Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»ÐµÐ¹ на " +"более быÑтрых платформах." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114 msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)" -msgstr "" +msgstr "ИÑправлены блокировка и дублирование (чаÑтично) I2PTunnel / I2C" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115 msgid "Fix translation of HTTP proxy error pages" -msgstr "" +msgstr "ИÑправлен перевод Ñтраниц ошибок HTTP прокÑи" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116 msgid "Fix occasional runtime exception in NTCP" -msgstr "" +msgstr "ИÑправлено ÑлучающееÑÑ Ð¸Ð½Ð¾Ð³Ð´Ð° иÑключение времени Ð²Ñ‹Ð¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ Ð² NTCP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120 msgid "Big rework of transport code to accommodate multiple addresses and IPv6" msgstr "" +"Ð‘Ð¾Ð»ÑŒÑˆÐ°Ñ Ð¿ÐµÑ€ÐµÑ€Ð°Ð±Ð¾Ñ‚ÐºÐ° транÑпортного кода Ð´Ð»Ñ ÑоглаÑÐ¾Ð²Ð°Ð½Ð¸Ñ Ð¼Ð½Ð¾Ð¶ÐµÑтвенных " +"адреÑов и IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121 msgid "Streaming: Improved recovery from lost acks, other fixes" msgstr "" +"Streaming: улучшено воÑÑтановление поÑле потерÑнных подтверждений, другие" +" иÑправлениÑ" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122 msgid "Use Transifex for translation of initial news and HTTP proxy error pages" msgstr "" +"ИÑпользование Transifex Ð´Ð»Ñ Ð¿ÐµÑ€ÐµÐ²Ð¾Ð´Ð° начальных новоÑтей и Ñтраниц ошибок " +"HTTP прокÑи" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123 msgid "" "Translation updates: Chinese, French, German, Portuguese, Russian, " "Swedish, Turkish" msgstr "" +"ÐžÐ±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ Ð¿ÐµÑ€ÐµÐ²Ð¾Ð´Ð°: китайÑкий, французÑкий, немецкий, португальÑкий, " +"руÑÑкий, шведÑкий, турецкий" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124 msgid "New Romanian translation" -msgstr "" +msgstr "Ðовый румынÑкий перево" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126 msgid "Wrapper 3.5.20 (new installs and PPA only)" -msgstr "" +msgstr "Wrapper 3.5.20 (только новые уÑтановки и PPA)" diff --git a/i2p2www/translations/ru_RU/LC_MESSAGES/comparison.po b/i2p2www/translations/ru_RU/LC_MESSAGES/comparison.po new file mode 100644 index 000000000..0769bfa8c --- /dev/null +++ b/i2p2www/translations/ru_RU/LC_MESSAGES/comparison.po @@ -0,0 +1,874 @@ +# Russian (Russia) translations for I2P. +# Copyright (C) 2013 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# keedley <zhopa@mita.pp.ru>, 2013 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" +"POT-Creation-Date: 2013-08-30 23:32+0000\n" +"PO-Revision-Date: 2013-09-21 17:36+0000\n" +"Last-Translator: keedley <zhopa@mita.pp.ru>\n" +"Language-Team: Russian (Russia) " +"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 0.9.6\n" + +#: i2p2www/pages/site/comparison/freenet.html:2 +msgid "I2P Compared to Freenet" +msgstr "I2P в Ñравнении Ñ Freenet" + +#: i2p2www/pages/site/comparison/freenet.html:8 +msgid "" +"Freenet is a fully distributed, peer to peer anonymous publishing " +"network, offering \n" +"secure ways to store data, as well as some approaches attempting to " +"address the loads\n" +"of a flash flood. While Freenet is designed as a distributed data store," +" people have\n" +"built applications on top of it to do more generic anonymous " +"communication, such as \n" +"static websites and message boards." +msgstr "" +"Freenetn Ñто полноÑтью раÑпределеннаÑ, точка-точка, Ð°Ð½Ð¾Ð½Ð¸Ð¼Ð½Ð°Ñ Ñеть Ð´Ð»Ñ " +"публикации, предоÑтавлÑÑŽÑ‰Ð°Ñ Ð±ÐµÐ·Ð¾Ð¿Ð°Ñный ÑпоÑоб хранить данные, как и " +"некоторые подходы, позволÑющие обрабатывать нагрузки\n" +"в пиках. Ð¥Ð¾Ñ‚Ñ Freenet разработан как раÑпределенное хранилище, " +"пользователи Ñделали\n" +"Ð¿Ñ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾Ð²ÐµÑ€Ñ… него, которые позволÑÑŽÑ‚ другие формы взаимодейÑтвиÑ, " +"такие как Ñтатичные\n" +"веб-Ñайты и доÑки Ñообщений." + +#: i2p2www/pages/site/comparison/freenet.html:16 +#, python-format +msgid "" +"Compared to I2P, Freenet offers some substantial benefits - it is a " +"distributed data\n" +"store, while I2P is not, allowing people to retrieve the content " +"published by others \n" +"even when the publisher is no longer online. In addition, it should be " +"able to \n" +"distribute popular data fairly efficiently. I2P itself does not and will" +" not provide \n" +"this functionality. On the other hand, there is overlap for users who " +"simply want to \n" +"communicate with each other anonymously through websites, message boards," +" file sharing\n" +"programs, etc. There have also been some attempts to develop a " +"distributed data \n" +"store to run on top of I2P,\n" +"(most recently a port of <a href=\"%(tahoe)s\">Tahoe-LAFS</a>)\n" +"but nothing is yet ready for general use." +msgstr "" +"По Ñравнению Ñ I2P, Freenet имеет некоторые преимущеÑтва - Ñто " +"раÑпределенное хранилище\n" +"данных, чем I2P не ÑвлÑетÑÑ, позволÑющее людÑм обмениватьÑÑ Ð´Ð°Ð½Ð½Ñ‹Ð¼Ð¸, даже" +" еÑли оригинальный\n" +"автор более недоÑтупен. Также Ñеть позволÑет Ñффективно раÑпределÑÑ‚ÑŒ " +"даынные. I2P Ñам по Ñебе не имеет и не будет иметь такой функции. С " +"другой Ñтороны, здеÑÑŒ еÑÑ‚ÑŒ недоÑтаток Ð´Ð»Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»ÐµÐ¹, которые проÑто " +"хотÑÑ‚ анонимно общатьÑÑ Ñ‡ÐµÑ€ÐµÐ· веб-Ñайты, доÑки объÑвлений, программы " +"файлообмена и Ñ‚.д\n" +"Ð’ I2P еÑÑ‚ÑŒ варианты реализации таких функций Ñ Ð¿Ð¾Ð¼Ð¾ÑˆÑŒÑŽ Ñпециальных " +"приложений (a href=\"%(tahoe)s\">Tahoe-LAFS</a>), но еще ничего Ð´Ð»Ñ " +"обычного иÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ð½Ðµ готово." + +#: i2p2www/pages/site/comparison/freenet.html:29 +msgid "" +"However, even ignoring any implementations issues, there are some " +"concerns \n" +"about Freenet's algorithms from both a scalability and anonymity " +"perspective, owing \n" +"largely to Freenet's heuristic driven routing. The interactions of " +"various techniques \n" +"certainly may successfully deter various attacks, and perhaps some " +"aspects of the \n" +"routing algorithms will provide the hoped for scalability. " +"Unfortunately, not much\n" +"analysis of the algorithms involved has resulted in positive results, but" +" there is still\n" +"hope. At the very least, Freenet does provide substantial anonymity " +"against an attacker\n" +"who does not have the resources necessary to analyze it further." +msgstr "" +"Тем не менее, даже не Ð¾Ð±Ñ€Ð°Ñ‰Ð°Ñ Ð²Ð½Ð¸Ð¼Ð°Ð½Ð¸Ðµ на проблемы реализации, еÑÑ‚ÑŒ " +"определенные ÑоображениÑ\n" +"об алгоритмах Freenet Ñ Ñ‚Ð¾Ñ‡ÐºÐ¸ Ð·Ñ€ÐµÐ½Ð¸Ñ Ð¼Ð°ÑÑˆÑ‚Ð°Ð±Ð¸Ñ€Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¸ анонимноÑти, в " +"облаÑти ÑвриÑтичеÑкой маршрутизации внутри Freenet. ВзаимодейÑтвие разных" +" техник определенно может защитить от Ñ€Ñда аттак, \n" +"и возможно некоторые аÑпекты алгоритмов маршрутизации дают надежды на " +"маÑштабирование. К Ñожалению, немного из попыток анализа алгоритмов дали " +"позитивные результаты, но надежда еÑÑ‚ÑŒ.\n" +"Ð’ конце концов, Freenet предоÑтавлÑет значительный уровень анонимноÑти " +"против атакующего, который не обладает доÑтаточными Ð´Ð»Ñ Ð´Ð°Ð»ÑŒÐ½ÐµÐ¹ÑˆÐµÐ³Ð¾ " +"анализа реÑурÑами." + +#: i2p2www/pages/site/comparison/index.html:2 +msgid "Comparing I2P to other projects" +msgstr "Сравнение I2P Ñ Ð´Ñ€ÑƒÐ³Ð¸Ð¼Ð¸ проектами" + +#: i2p2www/pages/site/comparison/index.html:4 +msgid "" +"There are a great many other applications and projects working on " +"anonymous \n" +"communication and I2P has been inspired by much of their efforts. This " +"is not \n" +"a comprehensive list of anonymity resources - both freehaven's \n" +"<a href=\"http://freehaven.net/anonbib/topic.html\">Anonymity " +"Bibliography</a>\n" +"and GNUnet's <a href=\"https://www.gnunet.org/links/\">related " +"projects</a>\n" +"serve that purpose well. That said, a few systems stand out for further\n" +"comparison. The following have individual comparison pages:" +msgstr "" +"СущеÑтвует много других хороших приложений и проектов в облаÑти анонимных" +" коммуникаций, и I2P определенно обогащаетÑÑ Ð¸Ñ… опытом. Ðто не \n" +"полный ÑпиÑок подобных реÑурÑов - у freehaven'а в \n" +"<a href=\"http://freehaven.net/anonbib/topic.html\">Anonymity " +"Bibliography</a>\n" +"и в GNUnet <a href=\"https://www.gnunet.org/links/\">проектах</a>\n" +"Ñти ÑпиÑки полнее. Ð’Ñего неÑколько ÑиÑтем имеет ÑмыÑл Ñравнивать далее." +" \n" +"Ðиже перечиÑлены Ñтраницы, поÑвÑщенные ÑравнениÑм Ñ Ñтими ÑиÑтемами:" + +#: i2p2www/pages/site/comparison/index.html:20 +#, python-format +msgid "" +"The following are discussed on the <a href=\"%(othernetworks)s\">other " +"networks page:</a>" +msgstr "ОбÑуждаетÑÑ Ð½Ð° <a href=\"%(othernetworks)s\">Ñтранице других Ñетей:</a>" + +#: i2p2www/pages/site/comparison/index.html:32 +#, python-format +msgid "" +"The content of this page is subject to update, discussion and dispute, " +"and we welcome comments and additions.\n" +"You may contribute an analysis by entering a <a " +"href=\"http://%(trac)s/report/1\">new ticket on Trac</a>." +msgstr "" +"Содержимое Ñтой Ñтраницы может обновлÑÑ‚ÑŒÑÑ, обÑуждатьÑÑ Ð¸ " +"ниÑпровершатьÑÑ, и мы приветÑтвуем комментарии и добавлениÑ. \n" +"Ð’Ñ‹ можете внеÑти Ñвой вклад, опубликовав <a " +"href=\"http://%(trac)s/report/1\">в Trac новую запиÑÑŒ</a>" + +#: i2p2www/pages/site/comparison/other-networks.html:2 +msgid "I2P Compared to Other Anonymous Networks" +msgstr "I2P в Ñравнении Ñ Ð´Ñ€ÑƒÐ³Ð¸Ð¼Ð¸ анонимными ÑетÑми" + +#: i2p2www/pages/site/comparison/other-networks.html:5 +msgid "The following networks are discussed on this page." +msgstr "Следующие Ñети обÑуждаютÑÑ Ð½Ð° Ñтой Ñтранице:" + +#: i2p2www/pages/site/comparison/other-networks.html:16 +#, python-format +msgid "" +"Most of the following sections are fairly old, and may not be accurate.\n" +"For an overview of available comparisons, see the\n" +"<a href=\"%(comparison)s\">main network comparisons page</a>.\n" +"You may contribute an analysis by entering a\n" +"<a href=\"http://%(trac)s/report/1\">new ticket on %(trac)s</a>." +msgstr "" +"Многие из Ñекций довольно Ñтарые и могут быть неточными.\n" +"Ð”Ð»Ñ ÑпиÑка извеÑтных Ñравнений, Ñмотрите <a " +"href=\"%(comparison)s\">Ñтраницу Ñравнений Ñетей</a>.âŽ\n" +"Ð’Ñ‹ можете опубликовать Ñвой анализ через âŽ\n" +"<a href=\"http://%(trac)s/report/1\">тикет-ÑиÑтему %(trac)s</a>." + +#: i2p2www/pages/site/comparison/other-networks.html:29 +#, python-format +msgid "" +"Morphmix and Tarzan are both fully distributed, peer to peer networks of" +" \n" +"anonymizing proxies, allowing people to tunnel out through the low " +"latency \n" +"mix network. Morphmix includes some very interesting collusion detection" +" \n" +"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of " +"IP\n" +"addresses to accomplish the same. The two primary differences between \n" +"these systems and I2P are related to I2P's <a " +"href=\"%(threatmodel)s\">threat model</a> \n" +"and their out-proxy design (as opposed to providing both sender and " +"receiver \n" +"anonymity). There is source code available to both systems, but we are " +"not aware \n" +"of their use outside of academic environments." +msgstr "" +"Morphmix и Tarzan Ñто полноÑтью раÑпределенные точка-точка Ñети анонимных" +" прокÑи-Ñерверов, позволÑющие людÑм организовывать ÑÐ¾ÐµÐ´Ð¸Ð½ÐµÐ½Ð¸Ñ Ñ‡ÐµÑ€ÐµÐ· " +"Ñмешанную Ñеть Ñ Ð½Ð¸Ð·ÐºÐ¸Ð¼Ð¸ задержками.\n" +"Morphmix включает интереÑные алгоритмы обхода коллизий и защиты от атаки" +" Sybil, а Tarzan иÑпользует Ð´Ð»Ñ Ñтого недоÑтаток IP адреÑов. Два " +"оÑновных Ð¾Ñ‚Ð»Ð¸Ñ‡Ð¸Ñ Ñ‚Ð°ÐºÐ¸Ñ… ÑиÑтем от I2P ÑвÑзаны Ñ <a " +"href=\"%(threatmodel)s\">моделью угроз</a> I2P \n" +"и их дизайнов выходÑщих узлов (в отличии от обеÑÐ¿ÐµÑ‡ÐµÐ½Ð¸Ñ Ð°Ð½Ð¾Ð½Ð¸Ð¼Ð½Ð¾Ñти и " +"отправителÑ, и получателÑ). Ð”Ð»Ñ Ð¾Ð±Ð¾Ð¸Ñ… ÑиÑтем доÑтупны иÑходные коды, но " +"нам не извеÑтно об их иÑпользовании за пределами научной деÑтельноÑти." + +#: i2p2www/pages/site/comparison/other-networks.html:153 +msgid "" +"\n" +"Mixminion and Mixmaster are networks to support anonymous email against a" +" very\n" +"powerful adversary.\n" +"High-latency messaging applications running on top of I2P\n" +"(for example\n" +"<a href=\"http://syndie.i2p2.de/\">Syndie</a> or\n" +"I2PBote)\n" +"may perhaps prove adequate to meet the threat\n" +"model of those adversaries, while running in parallel along side the " +"needs of low latency users, to provide\n" +"a significantly larger anonymity set.\n" +"High-latency support within the I2P router itself may or may not be added" +" in a distant future release.\n" +"It is too early to say if I2P will meet the needs of users requiring " +"extreme protection for email." +msgstr "" +"\n" +"Mixminion и Mixmaster Ñто Ñети, обеÑпечивающие обмен email при " +"противодейÑтвии мощному противнику.\n" +"СредÑтва обмена ÑообщениÑми Ñ Ð²Ñ‹Ñокой задержкой поверх I2P\n" +"(например, <a href=\"http://syndie.i2p2.de/\">Syndie</a> или\n" +"I2PBote)\n" +"возможно окажутÑÑ Ð²Ð¿Ð¾Ð»Ð½Ðµ отвечающими модели угроз в таких уÑловиÑÑ…, " +"оÑобенно ÑкÑплуатируÑÑÑŒ на фоне трафика многочиÑленных пользователей Ñ " +"низкими задержками, что добавит дополнительный уровень анонимноÑти.\n" +"Поддержка работы Ñ Ð²Ñ‹Ñокими задержками в I2P-маршрутизаторе может, а " +"может и не быть добавлена в отдаленном будущем релизе.\n" +"Пока рано говорить, Ñможет ли I2P удовлетворить Ñ‚Ñ€ÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»ÐµÐ¹ " +"по ÑкÑтремальной защите email Ñообщений." + +#: i2p2www/pages/site/comparison/other-networks.html:167 +msgid "" +"As with Tor and Onion Routing, \n" +"both Mixminion and Mixmaster take the directory based approach as well." +msgstr "" +"Как и в Ñлучае Tor и Onion Routing, Mixminion и Mixmaster применÑÑŽÑ‚ " +"подход на оÑнове Ñправочных директорий." + +#: i2p2www/pages/site/comparison/other-networks.html:177 +#, python-format +msgid "" +"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing " +"web requests,\n" +"and as such it has a few centralized nodes (participants in the cascade) " +"that blend\n" +"and mix requests from clients through the sequence of nodes (the cascade)" +" before \n" +"proxying out onto the web. The scope, threat model, and security is " +"substantially \n" +"different from I2P, but for those who don't require significant anonymity" +" but still\n" +"are not satisfied with an Anonymizer-like service, JAP is worth " +"reviewing. One\n" +"caution to note is that anyone under the jurisdiction of the German " +"courts may want\n" +"to take care, as the German Federal Bureau of Criminal Investigation " +"(FBCI) has \n" +"successfully mounted an \n" +"<a href=\"%(url)s\">attack</a> \n" +"on the network. Even though the method of this attack was later found to" +" be illegal \n" +"in the German courts, the fact that the data was successfully collected " +"is the \n" +"concern. Courts change their minds based upon circumstance, and this is " +"evidence that \n" +"if a government body or intelligence agency wanted to, they could gather " +"the data, even \n" +"if it may be found inadmissible in some courts later)" +msgstr "" +"JAP (Java Anonymous Proxy) Ñто Ñеть Ñмешанных каÑкадов Ð´Ð»Ñ Ð°Ð½Ð¾Ð½Ð¸Ð¼Ð¸Ð·Ð°Ñ†Ð¸Ð¸ " +"веб-запроÑов, и Ð´Ð»Ñ Ñтого применÑетÑÑ Ð½ÐµÑколько централизованных узлов " +"(учаÑтников каÑкада), которые Ñмешивают и обрабатывают запроÑÑ‹ " +"пользователей через набор узлов (каÑкад) перед доÑтавкой их в Ñеть.\n" +"Задача, модель угроз и безопаÑноÑти ÑущеÑтвенно отличаютÑÑ Ð¾Ñ‚ принÑÑ‚Ñ‹Ñ… в " +"I2P, но те, кто не нуждаетÑÑ Ð² значительном уровне анонимноÑти, но не " +"удовлетворен уровнем анонимноÑти ÑущеÑтвующих анонимайзеров, могут " +"раÑÑмотреть Ñтот вариант. Те, кто в зоне ответÑтвенноÑти немецкого " +"законодательÑтва, должны учитывать опаÑноÑÑ‚ÑŒ того, что German Federal " +"Bureau of Criminal Investigation (FBCI) уÑпешно провело <a " +"href=\"%(url)s\">атаку</a> на Ñту Ñеть.\n" +"Ð¥Ð¾Ñ‚Ñ Ð¼ÐµÑ‚Ð¾Ð´Ñ‹ атаки позже были признаны незаконными в немецком Ñуде, факт " +"уÑпешного Ñбора данных Ñтоит учитывать. Суды могут поменÑÑ‚ÑŒ Ñвои Ñ€ÐµÑˆÐµÐ½Ð¸Ñ " +"по обÑтоÑтельÑтвам и техничеÑкую возможноÑÑ‚ÑŒ Ñбора информации " +"правительÑтвом или агентÑтвами Ð½ÐµÐ»ÑŒÐ·Ñ ÑбраÑывать Ñо Ñчетов)." + +#: i2p2www/pages/site/comparison/other-networks.html:199 +#, python-format +msgid "" +"Both of these systems work through the same basic \n" +"<a href=\"%(antnet)s\">antnet</a> routing, providing some degree of\n" +"anonymity based on the threat model of providing plausible deniability " +"against a simple \n" +"non-colluding adversary. With the antnet routing, they first either do a" +" random walk or a \n" +"broadcast search to find some peer with the data or identity desired, and" +" then use a feedback\n" +"algorithm to optimize that found path. This works well for applications " +"that merely want to know \n" +"what other people around them have to offer - \"How are y'all doing\" vs." +" \"Hey Alice, how are you\" - \n" +"you basically get a local cluster of nodes that can share files with and " +"maintain some degree of \n" +"anonymity (though you don't have much control over who is in that group " +"of peers)." +msgstr "" +"Обе Ñти ÑиÑтемы работают на одном базовом механизме <a " +"href=\"%(antnet)s\">маршрутизации</a>, добиваÑÑÑŒ некоторой анонимноÑти, " +"предоÑтавлÑÑ Ð¿ÑƒÑ‚ÑŒ отказа при неÑложном, не организованном противнике. " +"ИÑÐ¿Ð¾Ð»ÑŒÐ·ÑƒÑ antnet маршрутизацию, они Ñначала делают Ñлучайный проход, или " +"широковещательный Ð·Ð°Ð¿Ñ€Ð¾Ñ Ð½Ð° поиÑк пира Ñ Ð½ÑƒÐ¶Ð½Ñ‹Ð¼Ð¸ данными или адреÑами, а " +"затем иÑпользуют обратную ÑвÑзь Ð´Ð»Ñ Ð¾Ð¿Ñ‚Ð¸Ð¼Ð¸Ð·Ð°Ñ†Ð¸Ð¸ найденного пути. Ðто " +"нормально работает Ð´Ð»Ñ Ð¿Ñ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ð¹, которые Ñобирают информацию о том, что" +" другие пиры вокруг могут предложить - \"как у Ð²Ð°Ñ Ð²Ñех дела?\" против " +"\"ÐлиÑа, привет, Ñ‚Ñ‹ как?\". Ðа выходе вы получаете локальный набор " +"узлов, Ñ ÐºÐ¾Ñ‚Ð¾Ñ€Ñ‹Ð¼Ð¸ можно обмениватьÑÑ Ñ„Ð°Ð¹Ð»Ð°Ð¼Ð¸ и поддерживать определенный " +"уровень анонимноÑти (Ñ…Ð¾Ñ‚Ñ Ð²Ñ‹ не имеете оÑобого ÐºÐ¾Ð½Ñ‚Ñ€Ð¾Ð»Ñ Ð½Ð°Ð´ тем, кто " +"будет в Ñтой группе пиров)." + +#: i2p2www/pages/site/comparison/other-networks.html:211 +msgid "" +"However, the algorithm does not scale well at all - if the application " +"wants to speak with a \n" +"particular peer it ends up doing a broadcast search or random walk " +"(though if they are lucky enough\n" +"for that to succeed, the antnet routing should optimize that found " +"connection). This means that \n" +"while these networks can work great at small scales, they are not " +"suitable for large networks where\n" +"someone wants to get in touch with another specific peer. That does not " +"mean that there is no \n" +"value in these systems, just that their applicability is limited to " +"situations where their \n" +"particular issues can be addressed." +msgstr "" +"Тем не менее, Ñтот алгоритм не очень хорошо маÑштабируетÑÑ - еÑли " +"приложение хочет говорить Ñ ÐºÐ¾Ð½ÐºÑ€ÐµÑ‚Ð½Ñ‹Ð¼ пиром, оно делает " +"широковещательный Ð·Ð°Ð¿Ñ€Ð¾Ñ Ð¸Ð»Ð¸ Ñлучайный поик (хотÑ, еÑли поиÑк удалÑÑ, " +"antnet позволит оптимизировать ÑвÑзб). Ðто означает, что Ñ…Ð¾Ñ‚Ñ Ñти Ñети " +"работают на малом чиÑле узлов, Ð´Ð»Ñ Ð±Ð¾Ð»ÑŒÑˆÐ¾Ð³Ð¾ чиÑла узлов они не очень " +"применимы при попытке ÑвÑзатьÑÑ Ñ ÐºÐ¾Ð½ÐºÑ€ÐµÑ‚Ð½Ñ‹Ð¼ пиром. Ðто не означает, что " +"Ñти ÑиÑтемы беÑполезны, проÑто их применимоÑÑ‚ÑŒ ограничена ÑценариÑми, где" +" Ñти недоÑтатки можно обработать другими ÑредÑтвами." + +#: i2p2www/pages/site/comparison/other-networks.html:222 +#, python-format +msgid "" +"This was a closed-source network targeted at Iranian users.\n" +"Tor did a\n" +"<a href=\"http://blog.torproject.org/blog/ten-things-look-circumvention-" +"tool\">good writeup on what to look for in a circumvention tool</a>.\n" +"Suffice it to say that being closed source and publicly targeting a " +"specific country are not good ideas.\n" +"I2P is, of course, open source. However, that source, and our\n" +"<a href=\"%(docs)s\">technical documentation</a>, need much more review." +msgstr "" +"Ðто Ñеть Ñ Ð·Ð°ÐºÑ€Ñ‹Ñ‚Ñ‹Ð¼Ð¸ иÑходниками, Ð¿Ñ€ÐµÐ´Ð½Ð°Ð·Ð½Ð°Ñ‡ÐµÐ½Ð½Ð°Ñ Ð´Ð»Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»ÐµÐ¹ в " +"Иране. \n" +"Tor выпуÑтил âŽ\n" +"<a href=\"http://blog.torproject.org/blog/ten-things-look-circumvention-" +"tool\">на что Ñмотреть при выборе ÑредÑтв обхода</a>.âŽ\n" +"ДоÑтаточно Ñказать, что будучи закрытм приложением и Ñвно целÑÑÑŒ в " +"конкретную группу пользователей, иÑпользование ÑиÑтемы не ÑвлÑетÑÑ " +"хорошей идеей.âŽ\n" +"I2P ÑвлÑетÑÑ ÑредÑтвом Ñ Ð¾Ñ‚ÐºÑ€Ñ‹Ñ‚Ñ‹Ð¼ кодом. Тем не менее, Ñти коды и наша âŽ\n" +"<a href=\"%(docs)s\">техничеÑÐºÐ°Ñ Ð´Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ð¸Ñ</a> нуждаютÑÑ Ð² большем " +"количеÑтве обÑуждений и контроле." + +#: i2p2www/pages/site/comparison/other-networks.html:231 +msgid "Paid VPN Services" +msgstr "Платные VPN ÑервиÑÑ‹" + +#: i2p2www/pages/site/comparison/other-networks.html:232 +#: i2p2www/pages/site/comparison/other-networks.html:238 +#, python-format +msgid "" +"You may contribute an analysis by entering a\n" +"<a href=\"http://%(trac)s/report/1\">new ticket on %(trac)s</a>." +msgstr "" +"Ð’Ñ‹ можете внеÑти Ñвой вклад, опубликовав <a " +"href=\"http://%(trac)s/report/1\">новую запиÑÑŒ в %(trac)s</a>." + +#: i2p2www/pages/site/comparison/other-networks.html:237 +msgid "Others" +msgstr "Другие" + +#: i2p2www/pages/site/comparison/tor.html:2 +msgid "I2P Compared to Tor" +msgstr "I2P в Ñравнении Ñ Tor" + +#: i2p2www/pages/site/comparison/tor.html:8 +#, python-format +msgid "" +"Tor and Onion Routing are both anonymizing proxy networks, \n" +"allowing people to tunnel out through their low latency mix \n" +"network. The two primary differences between Tor / \n" +"Onion-Routing and I2P are again related to differences in \n" +"the threat model and the out-proxy design (though Tor\n" +"supports hidden services as well). In addition, Tor\n" +"takes the directory-based approach - providing a \n" +"centralized point to manage the overall 'view' of the \n" +"network, as well as gather and report statistics, as \n" +"opposed to I2P's distributed <a href=\"%(netdb)s\">network \n" +"database</a> and <a href=\"%(peerselection)s\">peer selection</a>." +msgstr "" +"Tor и Onion Routing Ñто анонимные Ñети прокÑи-Ñерверов, позволÑющие " +"пользователÑм\n" +"туннелировать данные через их Ñеть Ñ Ð½Ð¸Ð·ÐºÐ¸Ð¼Ð¸ задержками. Два оÑновных " +"Ð¾Ñ‚Ð»Ð¸Ñ‡Ð¸Ñ Tor и I2P \n" +"оÑнованы на разнице в моделÑÑ… угроз и дизайне выходных прокÑи-узлов (хотÑ" +" Tor и поддерживает Ñкрытые ÑервиÑÑ‹, как и I2P). Кроме того, Tor " +"реализует централизованную точку Ð´Ð»Ñ ÑƒÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð²Ð¸Ð´Ð¸Ð¼Ð¾Ñтью Ñети, а так же" +" Ð´Ð»Ñ Ñбора ÑтатиÑтики, в отличие от раÑпределенной модели Ñети I2P, <a " +"href=\"%(netdb)s\">базы Ñети</a> и <a href=\"%(peerselection)s\">выбора " +"пира</a>." + +#: i2p2www/pages/site/comparison/tor.html:22 +msgid "" +"The I2P/Tor outproxy functionality does have a few \n" +"substantial weaknesses against certain attackers - \n" +"once the communication leaves the mixnet, global passive\n" +"adversaries can more easily mount traffic analysis. In \n" +"addition, the outproxies have access to the cleartext \n" +"of the data transferred in both directions, and \n" +"outproxies are prone to abuse, along with all of the \n" +"other security issues we've come to know and love with \n" +"normal Internet traffic." +msgstr "" +"Ð¤ÑƒÐ½ÐºÑ†Ð¸Ñ Ð²Ñ‹Ñ…Ð¾Ð´Ð½Ñ‹Ñ… узлов в I2P/Tor обладает неÑколькими Ñвными проблемами " +"- \n" +"как только данные покидают Ñеть, глобальные наблюдатели легко " +"обеÑпечивают мониторинг Ñтого траффика. Ð’ добавок, выходные узлы имеют " +"доÑтуп к незашифрованным данным в обе Ñтороны, а также легко выÑвлÑÑŽÑ‚ÑÑ Ð¸" +" подвержены разного рода атакам реального мира. И Ñто вÑе в добавление к " +"обычным проблемам безопаÑноÑти, которые мы знаем. " + +#: i2p2www/pages/site/comparison/tor.html:34 +msgid "" +"However, many people don't need to worry about those \n" +"situations, as they are outside their threat model. It\n" +"is, also, outside I2P's (formal) functional scope (if people want\n" +"to build outproxy functionality on top of an anonymous\n" +"communication layer, they can). In fact, some I2P users\n" +"currently take advantage of Tor to outproxy." +msgstr "" +"Тем не менее, многим людÑм не Ñтоит беÑпокоитьÑÑ Ð½Ð° Ñтот Ñчет, Ñ‚.к. они " +"за пределами угроз модели. Они также вне (формальной) границы I2P (еÑли " +"людÑм нужно Ñделать выходной узел, они могут его Ñделать). Ðа Ñамом деле," +" Ñ€Ñд пользователей I2P в качеÑтве выходного узла иÑпользуют Tor." + +#: i2p2www/pages/site/comparison/tor.html:48 +msgid "Comparison of Tor and I2P Terminology" +msgstr "Сравнение терминологии Tor и I2P" + +#: i2p2www/pages/site/comparison/tor.html:49 +msgid "" +"While Tor and I2P are similar in many ways, much of the terminology is " +"different." +msgstr "" +"Ð¥Ð¾Ñ‚Ñ Tor и I2P во многом похожи, у них значительно отличаетÑÑ " +"терминологиÑ." + +#: i2p2www/pages/site/comparison/tor.html:54 +msgid "Cell" +msgstr "Ячейка" + +#: i2p2www/pages/site/comparison/tor.html:54 +msgid "Message" +msgstr "Сообщение" + +#: i2p2www/pages/site/comparison/tor.html:55 +msgid "Client" +msgstr "Клиент" + +#: i2p2www/pages/site/comparison/tor.html:55 +msgid "Router or Client" +msgstr "Маршрутизатор или Клиент" + +#: i2p2www/pages/site/comparison/tor.html:56 +msgid "Circuit" +msgstr "Цепочка" + +#: i2p2www/pages/site/comparison/tor.html:56 +msgid "Tunnel" +msgstr "Туннель" + +#: i2p2www/pages/site/comparison/tor.html:57 +msgid "Directory" +msgstr "Справочник" + +#: i2p2www/pages/site/comparison/tor.html:57 +msgid "NetDb" +msgstr "NetDb" + +#: i2p2www/pages/site/comparison/tor.html:58 +msgid "Directory Server" +msgstr "Сервер Ñправочников" + +#: i2p2www/pages/site/comparison/tor.html:58 +msgid "Floodfill Router" +msgstr "Floodfill маршрутизатор" + +#: i2p2www/pages/site/comparison/tor.html:59 +msgid "Entry Guards" +msgstr "Входные Ñтражи" + +#: i2p2www/pages/site/comparison/tor.html:59 +msgid "Fast Peers" +msgstr "БыÑтрые пиры" + +#: i2p2www/pages/site/comparison/tor.html:60 +msgid "Entry Node" +msgstr "Входные узлы" + +#: i2p2www/pages/site/comparison/tor.html:60 +msgid "Inproxy" +msgstr "Входной прокÑи" + +#: i2p2www/pages/site/comparison/tor.html:61 +msgid "Exit Node" +msgstr "Выходной узел" + +#: i2p2www/pages/site/comparison/tor.html:61 +msgid "Outproxy" +msgstr "Выходной прокÑи" + +#: i2p2www/pages/site/comparison/tor.html:62 +msgid "Hidden Service" +msgstr "Скрытый ÑервиÑ" + +#: i2p2www/pages/site/comparison/tor.html:62 +msgid "Eepsite or Destination" +msgstr "Eepsite или Ðазначение" + +#: i2p2www/pages/site/comparison/tor.html:63 +msgid "Hidden Service Descriptor" +msgstr "ДеÑкриптор Ñкрытого ÑервиÑа" + +#: i2p2www/pages/site/comparison/tor.html:63 +msgid "LeaseSet" +msgstr "LeaseSet" + +#: i2p2www/pages/site/comparison/tor.html:64 +msgid "Introduction point" +msgstr "Введение" + +#: i2p2www/pages/site/comparison/tor.html:64 +msgid "Inbound Gateway" +msgstr "Входной шлюз" + +#: i2p2www/pages/site/comparison/tor.html:65 +msgid "Node" +msgstr "Узел" + +#: i2p2www/pages/site/comparison/tor.html:65 +#: i2p2www/pages/site/comparison/tor.html:67 +#: i2p2www/pages/site/comparison/tor.html:70 +msgid "Router" +msgstr "Маршрутизатор" + +#: i2p2www/pages/site/comparison/tor.html:66 +msgid "Onion Proxy" +msgstr "Onion Proxy" + +#: i2p2www/pages/site/comparison/tor.html:66 +msgid "I2PTunnel Client (more or less)" +msgstr "I2PTunnel клиент (более-менее)" + +#: i2p2www/pages/site/comparison/tor.html:67 +msgid "Relay" +msgstr "Relay" + +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Rendezvous Point" +msgstr "Точка вÑтречи" + +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "somewhat like Inbound Gateway + Outbound Endpoint" +msgstr "что-то вроде Входной шлюз + Ð’Ñ‹Ñ…Ð¾Ð´Ð½Ð°Ñ Ñ‚Ð¾Ñ‡ÐºÐ°" + +#: i2p2www/pages/site/comparison/tor.html:69 +msgid "Router Descriptor" +msgstr "ДеÑкриптор маршрутизатора" + +#: i2p2www/pages/site/comparison/tor.html:69 +msgid "RouterInfo" +msgstr "RouterInfo" + +#: i2p2www/pages/site/comparison/tor.html:70 +msgid "Server" +msgstr "Сервер" + +#: i2p2www/pages/site/comparison/tor.html:73 +msgid "Benefits of Tor over I2P" +msgstr "ПреимущеÑтва Tor перед I2P" + +#: i2p2www/pages/site/comparison/tor.html:76 +msgid "" +"Much bigger user base; much more visibility in the academic and hacker " +"communities; benefits from\n" +"formal studies of anonymity, resistance, and performance;\n" +"has a non-anonymous, visible, university-based leader" +msgstr "" +"Значительно Ð±Ð¾Ð»ÑŒÑˆÐ°Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»ÑŒÑÐºÐ°Ñ Ð±Ð°Ð·Ð°; Большее внимание Ñо Ñтороны " +"науки и хакерÑкого ÑообщеÑтва; выгоды от формальных иÑÑледований " +"анонимноÑти, ÑÐ¾Ð¿Ñ€Ð¾Ñ‚Ð¸Ð²Ð»ÐµÐ½Ð¸Ñ Ð¸ производительноÑти;\n" +"извеÑтен не анонимный, видимый, ÑвÑзанный Ñ ÑƒÐ½Ð¸Ð²ÐµÑ€Ñитетом лидер" + +#: i2p2www/pages/site/comparison/tor.html:82 +msgid "Has already solved some scaling issues I2P has yet to address" +msgstr "" +"Уже разрешили Ñ€Ñд проблем маÑштабированиÑ, к которым I2P еще проÑто не " +"подошел" + +#: i2p2www/pages/site/comparison/tor.html:83 +msgid "Has significant funding" +msgstr "Имеет значительное финанÑирование" + +#: i2p2www/pages/site/comparison/tor.html:84 +msgid "Has more developers, including several that are funded" +msgstr "Больше разработчиков, Ð²ÐºÐ»ÑŽÑ‡Ð°Ñ Ñ€Ñд оплачиваемых" + +#: i2p2www/pages/site/comparison/tor.html:86 +msgid "" +"More resistant to state-level blocking due to TLS transport layer and " +"bridges\n" +"(I2P has proposals for \"full restricted routes\" but these are not yet " +"implemented)" +msgstr "" +"Более уÑтойчивый к блокировкам на уровне гоÑударÑтв, Ð±Ð»Ð°Ð³Ð¾Ð´Ð°Ñ€Ñ Ñ‚Ñ€Ð°Ð½Ñпорту" +" поверх TLS и моÑтам (I2P имеет Ð¿Ñ€ÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾ \"полноÑтью закрытым " +"путÑм\", но они еще не реализованы)" + +#: i2p2www/pages/site/comparison/tor.html:91 +msgid "Big enough that it has had to adapt to blocking and DOS attempts" +msgstr "ДоÑтаточно Ð±Ð¾Ð»ÑŒÑˆÐ°Ñ Ñеть, чтобы адаптироватьÑÑ Ðº блокировке и попыткам DOS" + +#: i2p2www/pages/site/comparison/tor.html:92 +msgid "Designed and optimized for exit traffic, with a large number of exit nodes" +msgstr "" +"Разработан и оптимизирован Ð´Ð»Ñ Ð²Ñ‹Ñ…Ð¾Ð´Ð° трафика, Ñ Ð±Ð¾Ð»ÑŒÑˆÐ¸Ð¼ чиÑлом выходных" +" узлов" + +#: i2p2www/pages/site/comparison/tor.html:94 +msgid "" +"Better documentation, has formal papers and specifications,\n" +"better website, many more translations" +msgstr "" +"Лучше документациÑ, еÑÑ‚ÑŒ иÑÑÐ»ÐµÐ´Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¸ Ñпецификации,\n" +"лучше вебÑайт, гораздо больше переведенных данных" + +#: i2p2www/pages/site/comparison/tor.html:99 +msgid "More efficient with memory usage" +msgstr "Более Ñффективен в иÑпользовании памÑти" + +#: i2p2www/pages/site/comparison/tor.html:100 +msgid "Tor client nodes have very low bandwidth overhead" +msgstr "Клиенты Tor работают Ñ Ð¾Ñ‡ÐµÐ½ÑŒ небольшими затратами на протоколе" + +#: i2p2www/pages/site/comparison/tor.html:102 +msgid "" +"Centralized control reduces the complexity at each\n" +"node and can efficiently address Sybil attacks" +msgstr "" +"Централизованный контроль уменьшает ÑложноÑÑ‚ÑŒ каждого узла и может " +"Ñффективно работать Ñ Ð°Ñ‚Ð°ÐºÐ°Ð¼Ð¸ Sybil" + +#: i2p2www/pages/site/comparison/tor.html:108 +msgid "" +"A core of high capacity nodes provides higher\n" +"throughput and lower latency" +msgstr "" +"Ðабор выÑокопроизводительных узлов обеÑпечивает выÑокую " +"производительноÑÑ‚ÑŒ и меньшие задержки" + +#: i2p2www/pages/site/comparison/tor.html:113 +msgid "C, not Java (ewww)" +msgstr "Ñ€ÐµÐ°Ð»Ð¸Ð·Ð°Ñ†Ð¸Ñ Ð½Ð° C, не Java (фу...)" + +#: i2p2www/pages/site/comparison/tor.html:116 +msgid "Benefits of I2P over Tor" +msgstr "ПреимущеÑтва I2P перед Tor" + +#: i2p2www/pages/site/comparison/tor.html:118 +msgid "" +"Designed and optimized for hidden services, which are much faster than in" +" Tor" +msgstr "" +"Разработан и оптимизирован Ð´Ð»Ñ Ñ€Ð°Ð±Ð¾Ñ‚Ñ‹ Ñкрытых ÑервиÑов, что гораздо " +"быÑтрее, чем в Tor" + +#: i2p2www/pages/site/comparison/tor.html:119 +msgid "Fully distributed and self organizing" +msgstr "ПолноÑтью раÑÐ¿Ñ€ÐµÐ´ÐµÐ»ÐµÐ½Ð½Ð°Ñ Ð¸ ÑамоорганизующаÑÑÑ Ñеть" + +#: i2p2www/pages/site/comparison/tor.html:121 +msgid "" +"Peers are selected by continuously profiling and ranking performance,\n" +"rather than trusting claimed capacity" +msgstr "" +"Пиры выбираютÑÑ Ð½Ð° оÑнове поÑтоÑнного профайлинга и замеров по " +"производительноÑти,\n" +"нежели по объÑвленной пиром пропуÑкной ÑпоÑобноÑти" + +#: i2p2www/pages/site/comparison/tor.html:127 +msgid "" +"Floodfill peers (\"directory servers\") are varying and untrusted,\n" +"rather than hardcoded" +msgstr "" +"Пиры Floodfill (\"Ñправочные Ñервера\") поÑтоÑнно менÑÑŽÑ‚ÑÑ Ð¸ не обладают " +"доверием, в отличие от Ñвно прошитых в Tor" + +#: i2p2www/pages/site/comparison/tor.html:132 +msgid "Small enough that it hasn't been blocked or DOSed much, or at all" +msgstr "ДоÑтаточно небольшаÑ, чтобы ее Ñильно блокировали или DOS'или. " + +#: i2p2www/pages/site/comparison/tor.html:133 +msgid "Peer-to-peer friendly" +msgstr "ОбеÑпечивает пиринговые ÑервиÑÑ‹" + +#: i2p2www/pages/site/comparison/tor.html:134 +msgid "Packet switched instead of circuit switched" +msgstr "Коммутирует пакеты, нежели ÑоединениÑ" + +#: i2p2www/pages/site/comparison/tor.html:137 +msgid "" +"implicit transparent load balancing of messages \n" +"across multiple peers, rather than a single path" +msgstr "" +"Ð¯Ð²Ð½Ð°Ñ Ð¿Ñ€Ð¾Ð·Ñ€Ð°Ñ‡Ð½Ð°Ñ Ð±Ð°Ð»Ð°Ð½Ñировка Ñообщений по многим пирам, в отличие от " +"иÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¾Ð´Ð½Ð¾Ð³Ð¾ пути" + +#: i2p2www/pages/site/comparison/tor.html:143 +msgid "" +"resilience vs. failures by running multiple \n" +"tunnels in parallel, plus rotating tunnels" +msgstr "" +"ÐадежноÑÑ‚ÑŒ и отказоуÑтойчивоÑÑ‚ÑŒ за Ñчет Ð¿Ð¾Ð´Ð´ÐµÑ€Ð¶Ð°Ð½Ð¸Ñ Ð½ÐµÑкольких " +"параллельных туннелей и обеÑÐ¿ÐµÑ‡ÐµÐ½Ð¸Ñ Ñ€Ð¾Ñ‚Ð°Ñ†Ð¸Ð¸ туннелей" + +#: i2p2www/pages/site/comparison/tor.html:149 +msgid "" +"scale each client's connections at O(1) instead \n" +"of O(N) (Alice has e.g. 2 inbound tunnels that are \n" +"used by all of the peers Alice is talking with, \n" +"rather than a circuit for each)" +msgstr "" +"ÑÐ¾ÐµÐ´Ð¸Ð½ÐµÐ½Ð¸Ñ ÐºÐ°Ð¶Ð´Ð¾Ð³Ð¾ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ Ð¼Ð°ÑштабируютÑÑ ÐºÐ°Ðº O(1) вмеÑто O(N) " +"(например, ÐлиÑа держит 2 входÑщих туннелÑ, которые может иÑпользовать " +"любой пир, Ñ ÐºÐ¾Ñ‚Ð¾Ñ€Ñ‹Ð¼ ÐлиÑа общаетÑÑ, а не держим по цепочке на каждый " +"пир)" + +#: i2p2www/pages/site/comparison/tor.html:159 +msgid "" +"Unidirectional tunnels instead of bidirectional\n" +"circuits, doubling the number of nodes a peer has to\n" +"compromise to get the same information." +msgstr "" +"ОдноÑторонние туннели, вмеÑто двуÑторонних цепочек, ÑƒÐ´Ð²Ð°Ð¸Ð²Ð°Ñ Ñ‡Ð¸Ñло узлов," +" которые пир должен Ñкомпроменировать, чтобы получить ту же информацию" + +#: i2p2www/pages/site/comparison/tor.html:166 +msgid "" +"Protection against detecting client activity, even\n" +"when an attacker is participating in the tunnel, as\n" +"tunnels are used for more than simply passing end \n" +"to end messages (e.g. netDb, tunnel management, \n" +"tunnel testing)" +msgstr "" +"Защита против Ð´ÐµÑ‚ÐµÐºÑ‚Ð¸Ñ€Ð¾Ð²Ð°Ð½Ð¸Ñ ÐºÐ»Ð¸ÐµÐ½Ñ‚Ñкой активноÑти, даже еÑли\n" +"атакующий учаÑтвует в туннеле, так как туннели иÑпользуютÑÑ Ð½Ðµ только длÑ" +" передачи Ñообщений, но и Ð´Ð»Ñ Ñ€Ð°Ð±Ð¾Ñ‚Ñ‹ NetDb, ÑƒÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ñ‚ÑƒÐ½Ð½ÐµÐ»Ñми, " +"проверки работоÑпоÑобноÑти туннелей)" + +#: i2p2www/pages/site/comparison/tor.html:175 +msgid "" +"Tunnels in I2P are short lived, decreasing the number\n" +"of samples that an attacker can use to mount an \n" +"active attack with, unlike circuits in Tor, which are\n" +"typically long lived." +msgstr "" +"Ð’ I2P реализованы короткоживущие туннели, что уменьшает количеÑтво " +"примеров, которые атакующий может иÑпользовать Ð´Ð»Ñ Ð°Ñ‚Ð°ÐºÐ¸, в отличие от " +"цепочек в Tor'е, которые как правило живут долго. " + +#: i2p2www/pages/site/comparison/tor.html:183 +msgid "" +"I2P APIs are designed specifically for anonymity and\n" +"security, while SOCKS is designed for functionality." +msgstr "" +"API I2P Ñпроектированы под анонимноÑÑ‚ÑŒ и безопаÑноÑÑ‚ÑŒ, тогда как SOCKS " +"Ñделан Ð´Ð»Ñ Ñ„ÑƒÐ½ÐºÑ†Ð¸Ð¾Ð½Ð°Ð»ÑŒÐ½Ð¾Ñти" + +#: i2p2www/pages/site/comparison/tor.html:188 +msgid "Essentially all peers participate in routing for others" +msgstr "" +"За редким иÑключением, вÑе пиры учаÑтвуют в маршрутизации трафика Ð´Ð»Ñ " +"других" + +#: i2p2www/pages/site/comparison/tor.html:190 +msgid "" +"The bandwidth overhead of being a full peer is low, \n" +"while in Tor, while client nodes don't require much\n" +"bandwidth, they don't fully participate in the mixnet." +msgstr "" +"Затраты на работу в полном режиме довольно низки, тогда как в Tor, еÑли " +"клиент Ñам по Ñебе не требует много полоÑÑ‹, но они еще и не полноÑтью " +"иÑпользуют Ñеть." + +#: i2p2www/pages/site/comparison/tor.html:196 +msgid "Integrated automatic update mechanism" +msgstr "Ð’Ñтроенный механизм автоматичеÑких обновлений" + +#: i2p2www/pages/site/comparison/tor.html:197 +msgid "Both TCP and UDP transports" +msgstr "ИÑпользуетÑÑ ÐºÐ°Ðº TCP, так и UDP транÑпорт" + +#: i2p2www/pages/site/comparison/tor.html:198 +msgid "Java, not C (ewww)" +msgstr "Ð ÐµÐ°Ð»Ð¸Ð·Ð°Ñ†Ð¸Ñ Ð½Ð° Java, не C (фу....)" + +#: i2p2www/pages/site/comparison/tor.html:201 +msgid "Other potential benefits of I2P but not yet implemented" +msgstr "Другие потенциальные, но еще не реализованные преимущеÑтва I2P" + +#: i2p2www/pages/site/comparison/tor.html:202 +msgid "...and may never be implemented, so don't count on them!" +msgstr "... и возможно никогда не реализуемые, так что не раÑÑчитывайте на них" + +#: i2p2www/pages/site/comparison/tor.html:205 +msgid "" +"Defense vs. message count analysis by garlic wrapping \n" +"multiple messages" +msgstr "" +"Защита от количеÑтвенного анализа Ñообщений за Ñчет\n" +"Ð·Ð°Ð²Ð¾Ñ€Ð°Ñ‡Ð¸Ð²Ð°Ð½Ð¸Ñ Ð½ÐµÑкольких Ñообщений в одно" + +#: i2p2www/pages/site/comparison/tor.html:211 +msgid "" +"Defense vs. long term intersection by adding delays \n" +"at various hops (where the delays are not discernible\n" +"by other hops)" +msgstr "" +"Защита от ÑтатиÑтичеÑкого анализа за Ñчет Ð´Ð¾Ð±Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð·Ð°Ð´ÐµÑ€Ð¶ÐµÐº на разных " +"хопах\n" +"(где задержки не завиÑÑÑ‚ от других хоÑтов)" + +#: i2p2www/pages/site/comparison/tor.html:218 +msgid "" +"Various mixing strategies at the tunnel level (e.g.\n" +"create a tunnel that will handle 500 messages / minute,\n" +"where the endpoint will inject dummy messages if there\n" +"are insufficient messages, etc)" +msgstr "" +"Разные Ñтратегии имитовÑтавки на уровне туннелей (например\n" +"Ñоздание туннелÑ, который будет обрабатывать 500 Ñообщений в минуту, \n" +"где Ñндпойнт поÑылает Ñлучайные данные, еÑли полезный трафик не " +"передаетÑÑ Ð¸ Ñ‚.д)" + diff --git a/i2p2www/translations/ru_RU/LC_MESSAGES/get-involved.po b/i2p2www/translations/ru_RU/LC_MESSAGES/get-involved.po new file mode 100644 index 000000000..7b948df06 --- /dev/null +++ b/i2p2www/translations/ru_RU/LC_MESSAGES/get-involved.po @@ -0,0 +1,4129 @@ +# Russian (Russia) translations for I2P. +# Copyright (C) 2013 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# IOException <opexob@yandex.ru>, 2013 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" +"POT-Creation-Date: 2013-09-30 21:40+0000\n" +"PO-Revision-Date: 2013-10-25 17:54+0000\n" +"Last-Translator: IOException <opexob@yandex.ru>\n" +"Language-Team: Russian (Russia) " +"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 0.9.6\n" + +#: i2p2www/pages/site/get-involved/donate.html:2 +#: i2p2www/pages/site/get-involved/index.html:74 +msgid "Donate" +msgstr "Пожертвовать" + +#: i2p2www/pages/site/get-involved/donate.html:4 +msgid "" +"Thank you for your interest in contributing to I2P!\n" +"The details of how you\n" +"can make your contribution are provided below." +msgstr "" +"СпаÑибо за ваш Ð¸Ð½Ñ‚ÐµÑ€ÐµÑ Ð¿Ñ€Ð¾Ñвленный к поддержке проекта I2P!\n" +"ПодробноÑти о том как вы\n" +"можете Ñделать Ñвой вклад приведены ниже." + +#: i2p2www/pages/site/get-involved/donate.html:11 +#: i2p2www/pages/site/get-involved/donate.html:27 +#, python-format +msgid "" +"As of %(date)s, eche|on has been running a\n" +"<a href=\"%(coinurl)s\">%(cointype)s</a> account for the I2P project.\n" +"If you'd like to donate using %(cointype)s, just transfer your\n" +"desired amount of coins to the account <b>%(account)s</b>\n" +"and leave eche|on a note if you'd like your donation to be\n" +"mentioned on the I2P webpage." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:22 +#: i2p2www/pages/site/get-involved/donate.html:38 +msgid "For easy usage, use the QR code below!" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:44 +#, python-format +msgid "You can donate direct via PayPal to the account \"%(account)s\"." +msgstr "Ð’Ñ‹ можете пожертвовать на прÑмую через PayPal на аккаунт \"%(account)s\"." + +#: i2p2www/pages/site/get-involved/donate.html:50 +msgid "One time donation:" +msgstr "Разовое пожертвование:" + +#: i2p2www/pages/site/get-involved/donate.html:64 +msgid "Donate 10 €/month for 12 months:" +msgstr "Жертвовать по 10 €/меÑÑц в течение 12 меÑÑцев:" + +#: i2p2www/pages/site/get-involved/donate.html:72 +#: i2p2www/pages/site/get-involved/donate.html:84 +#: i2p2www/pages/site/get-involved/donate.html:96 +#: i2p2www/pages/site/get-involved/donate.html:108 +msgid "I2P donation " +msgstr "пожертвовать I2P" + +#: i2p2www/pages/site/get-involved/donate.html:78 +msgid "Donate 20 €/month for 12 months:" +msgstr "Жертвовать по 20 €/меÑÑц в течение 12 меÑÑцев:" + +#: i2p2www/pages/site/get-involved/donate.html:90 +msgid "Donate 30 €/month for 12 months:" +msgstr "Жертвовать по 30 €/меÑÑц в течение 12 меÑÑцев:" + +#: i2p2www/pages/site/get-involved/donate.html:102 +msgid "Donate 50 €/month for 12 months:" +msgstr "Жертвовать по 50 €/меÑÑц в течение 12 меÑÑцев:" + +#: i2p2www/pages/site/get-involved/donate.html:117 +msgid "Flattr this" +msgstr "Через Flattr" + +#: i2p2www/pages/site/get-involved/donate.html:122 +msgid "" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" +"as the envelope can be lost on the way to us." +msgstr "" +"ЕÑли вы хотите более или менее Ñохранить анонимноÑÑ‚ÑŒ, вы можете отправить" +" деньги почтой. Однако Ñто менее безопаÑно\n" +"так как конверт может потерÑÑ‚ÑŒÑÑ Ð¿Ð¾ пути к нам. " + +#: i2p2www/pages/site/get-involved/donate.html:126 +#, python-format +msgid "" +"If you'd like to donate via snail mail, send an email to <a " +"href=\"mailto:%(email)s?subject=information about snailmail " +"donation\">%(email)s</a>\n" +" and you'll receive an email with instructions detailing how to proceed." +msgstr "" +"ЕÑли вы хотите Ñделать пожертвование по ÑредÑтвам бумажной почты, " +"отправьте Ñлектронное пиÑьмо на Ð°Ð´Ñ€ÐµÑ <a " +"href=\"mailto:%(email)s?subject=information about snailmail " +"donation\">%(email)s</a>\n" +" и в ответ вы получите пиÑьмо Ñ Ð¿Ð¾Ð´Ñ€Ð¾Ð±Ð½Ñ‹Ð¼Ð¸ инÑтрукциÑми как Ñто " +"оÑущеÑтвить." + +#: i2p2www/pages/site/get-involved/donate.html:131 +#, python-format +msgid "" +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the <a " +"href=\"%(halloffame)s\">hall of fame</a>." +msgstr "" +"Рпока, вы можете взглÑнуть на щедрые пожертвованиÑ\n" +"Ñделанные проекту I2P в <a href=\"%(halloffame)s\">зале Ñлавы</a>." + +#: i2p2www/pages/site/get-involved/index.html:2 +msgid "Get Involved!" +msgstr "ПриÑоединÑйтеÑÑŒ!" + +#: i2p2www/pages/site/get-involved/index.html:4 +msgid "We need your help!" +msgstr "Ðам нужна ваша помощь!" + +#: i2p2www/pages/site/get-involved/index.html:5 +msgid "" +"To get involved, please feel free to join us on the #i2p IRC channel (on\n" +"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or " +"irc.postman.i2p)." +msgstr "" +"Что бы принÑÑ‚ÑŒ учаÑтие, не ÑтеÑнÑÑÑÑŒ заходите на наш IRC канал #i2p (на " +"Ñервере\n" +"irc.freenode.net, или в Ñети I2P на Ñерверах irc.freshcoffee.i2p или " +"irc.postman.i2p)." + +#: i2p2www/pages/site/get-involved/index.html:9 +#, python-format +msgid "" +"If you're interested in joining our <a href=\"%(team)s\">team</a>, please" +" get in\n" +"touch as we're always looking for eager contributors!" +msgstr "" +"ЕÑли вы хотите приÑоединить к нашей <a href=\"%(team)s\">команде</a>, " +"пожалуйÑта, ÑвÑжитеÑÑŒ Ñ Ð½Ð°Ð¼Ð¸, так как мы поÑтоÑнно ищем новых активных " +"учаÑтников." + +#: i2p2www/pages/site/get-involved/index.html:13 +msgid "" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" +"Here's a list to help you get started!" +msgstr "" +"Ðам нужна помощь по многим направлениÑм, поÑтому вам не обÑзательно знать" +" Ñзык Java, чтобы оказать помощь!\n" +"Вот ÑпиÑок, который поможет вам начать!" + +#: i2p2www/pages/site/get-involved/index.html:18 +msgid "Spread the Word!" +msgstr "РаÑÑкажите о наÑ!" + +#: i2p2www/pages/site/get-involved/index.html:19 +msgid "" +"Tell people about I2P on forums, blogs, and comments to articles.\n" +"Fix up the Wikipedia article about I2P in your language.\n" +"Tell your friends." +msgstr "" +"РаÑÑказывайте людÑм о I2P на форумах, в блогах и в комментариÑÑ… к " +"ÑтатьÑм.\n" +"ИÑправлÑйте и дополнÑйте Ñтатьи о I2P в Википедии на вашем Ñзыке.\n" +"РаÑÑкажите Ñвоим друзьÑм." + +#: i2p2www/pages/site/get-involved/index.html:24 +msgid "Testing" +msgstr "ТеÑтирование" + +#: i2p2www/pages/site/get-involved/index.html:25 +#, python-format +msgid "" +"Run the latest builds from <a href=\"%(monotone)s\">monotone</a>\n" +"and report results on #i2p or as bugs on <a " +"href=\"http://%(trac)s/report/1\">Trac</a>." +msgstr "" +"ЗапуÑкайте Ñвежие Ñборки из Ñ€ÐµÐ¿Ð¾Ð·Ð¸Ñ‚Ð¾Ñ€Ð¸Ñ <a " +"href=\"%(monotone)s\">monotone</a>\n" +"и Ñообщайте о результатах на канале #i2p или об ошибках в <a " +"href=\"http://%(trac)s/report/1\">Trac</a>." + +#: i2p2www/pages/site/get-involved/index.html:29 +msgid "Documentation" +msgstr "ДокументациÑ" + +#: i2p2www/pages/site/get-involved/index.html:30 +msgid "" +"Help fix the parts of the website that are outdated or incomplete.\n" +"Translate pages into other languages." +msgstr "" +"Помогите иÑправить разделы Ñайта, Ñодержащие уÑтаревшую или неполную " +"информацию.\n" +"Переводите Ñтраницы на другие Ñзыки." + +#: i2p2www/pages/site/get-involved/index.html:34 +msgid "Pictures" +msgstr "ИзображениÑ" + +#: i2p2www/pages/site/get-involved/index.html:35 +msgid "Make some more pictures, fix the old ones on the website" +msgstr "Добавьте больше картинок, обновите уÑтаревшие на Ñайте" + +#: i2p2www/pages/site/get-involved/index.html:38 +msgid "Content" +msgstr "Контент" + +#: i2p2www/pages/site/get-involved/index.html:39 +msgid "Make an eepsite! Add some content! Contribute to the community!" +msgstr "Создайте eep-Ñайт! Добавьте Ñодержимое! Сделайте вклад в ÑообщеÑтво!" + +#: i2p2www/pages/site/get-involved/index.html:42 +msgid "Services" +msgstr "Службы" + +#: i2p2www/pages/site/get-involved/index.html:43 +msgid "" +"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n" +"a naming service, a search engine, an eepsite monitor... many of these\n" +"aren't that hard." +msgstr "" +"ЗапуÑтите Ñлужбу на eep-Ñайте. Ðто может быть прокÑи-Ñервер, форум, " +"трекер, Ñлужба имён, поиÑковый ÑервиÑ, мониторинг eep-Ñайтов... много " +"вÑего и Ñто не так уж Ñложно." + +#: i2p2www/pages/site/get-involved/index.html:48 +msgid "Applications" +msgstr "Программы" + +#: i2p2www/pages/site/get-involved/index.html:49 +#, python-format +msgid "" +"Write or port applications for I2P! There's some guidelines and\n" +"a list of ideas on the <a href=\"%(apps)s\">applications page</a>." +msgstr "" +"Создавайте или портируйте программы Ð´Ð»Ñ I2P! Ð’Ñ‹ найдёте неÑколько " +"руководÑтв и ÑпиÑок идей на <a href=\"%(apps)s\">Ñтранице приложений</a>." + +#: i2p2www/pages/site/get-involved/index.html:53 +msgid "Coding" +msgstr "Программируйте" + +#: i2p2www/pages/site/get-involved/index.html:54 +#, python-format +msgid "" +"There's plenty to do if you know Java or are ready to learn.\n" +"Check for open tickets on <a href=\"http://%(trac)s/report/1\">Trac</a>\n" +"or the TODO list on <a href=\"http://%(zzz)s\">%(zzz)s</a> for\n" +"some ideas on where to start.\n" +"See the <a href=\"%(newdevs)s\">new developer's guide</a> for details." +msgstr "" +"ЕÑÑ‚ÑŒ много задач Ð´Ð»Ñ Ñ€ÐµÐ°Ð»Ð¸Ð·Ð°Ñ†Ð¸Ð¸ еÑли вы знаете Java или готовы учить.\n" +"Проверьте открытые заÑвки в <a href=\"http://%(trac)s/report/1\">Trac</a>" +"\n" +"или в ÑпиÑке TODO <a href=\"http://%(zzz)s\">%(zzz)s</a>\n" +"что бы определитьÑÑ Ñ Ñ‡ÐµÐ³Ð¾ можно начать.\n" +"ПроÑмотрите <a href=\"%(newdevs)s\">руководÑтво разработчиков</a> Ð´Ð»Ñ " +"выÑÑÐ½ÐµÐ½Ð¸Ñ Ð¿Ð¾Ð´Ñ€Ð¾Ð±Ð½Ð¾Ñтей." + +#: i2p2www/pages/site/get-involved/index.html:61 +msgid "Translation" +msgstr "Перевод" + +#: i2p2www/pages/site/get-involved/index.html:62 +#, python-format +msgid "" +"Help translate the website and the software into your language.\n" +"See the <a href=\"%(newtrans)s\">new translator's guide</a> for details." +msgstr "" +"Помогите перевеÑти веб-Ñайт и программное обеÑпечение на ваш Ñзык.\n" +"ОбратитеÑÑŒ к <a href=\"%(newtrans)s\">руководÑтву переводчика</a> Ð´Ð»Ñ " +"подробноÑтей." + +#: i2p2www/pages/site/get-involved/index.html:66 +msgid "Analysis" +msgstr "Ðнализ" + +#: i2p2www/pages/site/get-involved/index.html:67 +#, python-format +msgid "" +"Study or test the code to look for vulnerabilities.\n" +"Both anonymity vulnerabilities from the various\n" +"<a href=\"%(threatmodel)s\">threat models</a>,\n" +"and DOS and other weaknesses due to securities holes,\n" +"need researching." +msgstr "" +"Изучайте или теÑтируйте иÑходный код Ð´Ð»Ñ Ð²Ñ‹ÑÐ²Ð»ÐµÐ½Ð¸Ñ ÑƒÑзвимоÑтей.\n" +"И различные <a href=\"%(threatmodel)s\">модели угроз</a> деанонимизации,\n" +"и DOS, и другие проблемы безопаÑноÑти требуют тщательного изучениÑ." + +#: i2p2www/pages/site/get-involved/roadmap.html:2 +msgid "Roadmap" +msgstr "План разработки" + +#: i2p2www/pages/site/get-involved/roadmap.html:7 +msgid "" +"Include some seed data in the distribution so a central reseed location " +"isn't required?" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:10 +#, python-format +msgid "" +"Reachability Mapping / handle peers partially reachable / enhanced <a " +"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:13 +msgid "Improve help pages and website" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:14 +msgid "More translations" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:15 +msgid "SSU disconnect message" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:16 +msgid "Iterative floodfill lookups" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:21 +msgid "Full review of anonymity issues and other vulnerabilities" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:22 +msgid "" +"Reduce memory usage, remove debugging overhead, make it run better on " +"slow and embedded machines" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:25 +msgid "Docs" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:30 +msgid "Full restricted routes" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:35 +msgid "Tunnel mixing and padding" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:36 +msgid "User defined message delays" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:39 +#, python-format +msgid "" +"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info " +"about some of these tasks." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:2 +msgid "To Do List" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:4 +msgid "I2P Project Targets" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:5 +#, python-format +msgid "" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also <a href=\"%(roadmap)s\">the roadmap</a>. Want to " +"help?\n" +"<a href=\"%(volunteer)s\">Get involved</a>!" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:16 +#: i2p2www/pages/site/get-involved/todo.html:54 +msgid "Core functionality" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:16 +#: i2p2www/pages/site/get-involved/todo.html:28 +#: i2p2www/pages/site/get-involved/todo.html:52 +msgid "link" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:18 +#: i2p2www/pages/site/get-involved/todo.html:57 +msgid "NAT/Firewall bridging via 1-hop restricted routes" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:130 +msgid "High degree transport layer with UDP, NBIO, or NIO" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:24 +#: i2p2www/pages/site/get-involved/todo.html:218 +msgid "NetworkDB and profile tuning and ejection policy for large nets" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:28 +#: i2p2www/pages/site/get-involved/todo.html:242 +msgid "Security / anonymity" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:30 +#: i2p2www/pages/site/get-involved/todo.html:245 +msgid "" +"Per-hop tunnel id & new permuted TunnelVerificationStructure " +"encryption" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:33 +#: i2p2www/pages/site/get-involved/todo.html:295 +msgid "Strict ordering of participants within tunnels" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:36 +msgid "Randomly permuted tunnel lengths" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:39 +#: i2p2www/pages/site/get-involved/todo.html:357 +msgid "Full blown n-hop restricted routes with optional trusted links" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:42 +#: i2p2www/pages/site/get-involved/todo.html:376 +msgid "Hashcash for routerIdentity, destination, and tunnel request" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:45 +#: i2p2www/pages/site/get-involved/todo.html:405 +msgid "Advanced tunnel operation (batching/mixing/throttling/padding)" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:48 +#: i2p2www/pages/site/get-involved/todo.html:442 +msgid "Stop & go mix w/ garlics & tunnels" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:52 +#: i2p2www/pages/site/get-involved/todo.html:456 +msgid "Performance" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:62 +msgid "Implemented in I2P 0.6.0.6" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:63 +msgid "" +"The functionality of allowing routers to fully participate within the " +"network \n" +"while behind firewalls and NATs that they do not control requires some " +"basic \n" +"restricted route operation (since those peers will not be able to receive" +" \n" +"inbound connections). To do this successfully, you consider peers one of" +" \n" +"two ways:" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:73 +msgid "" +"<b>Peers who have reachable interfaces</b> - these peers do not need to \n" +"do anything special" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:77 +msgid "" +"<b>Peers who do not have reachable interfaces</b> - these peers must " +"build \n" +"a tunnel pointing at them where the gateway is one of the peers they have" +" \n" +"established a connection with who has both a publicly reachable interface" +" \n" +"and who has agreed to serve as their 'introducer'." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:85 +msgid "" +"To do this, peers who have no IP address simply connect to a few peers, \n" +"build a tunnel through them, and publish a reference to those tunnels " +"within \n" +"their RouterInfo structure in the network database." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:90 +msgid "" +"When someone wants to contact any particular router, they first must get" +" \n" +"its RouterInfo from the network database, which will tell them whether " +"they \n" +"can connect directly (e.g. the peer has a publicly reachable interface) \n" +"or whether they need to contact them indirectly. Direct connections occur" +" \n" +"as normal, while indirect connections are done through one of the " +"published \n" +"tunnels." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:98 +msgid "" +"When a router just wants to get a message or two to a specific hidden " +"peer, \n" +"they can just use the indirect tunnel for sending the payload. However, \n" +"if the router wants to talk to the hidden peer often (for instance, as " +"part \n" +"of a tunnel), they will send a garlic routed message through the indirect" +" \n" +"tunnel to that hidden peer which unwraps to contain a message which " +"should \n" +"be sent to the originating router. That hidden peer then establishes an \n" +"outbound connection to the originating router and from then on, those two" +" \n" +"routers can talk to each other directly over that newly established " +"direct \n" +"connection." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:109 +msgid "" +"Of course, that only works if the originating peer can receive " +"connections \n" +"(they aren't also hidden). However, if the originating peer is hidden, " +"they \n" +"can simply direct the garlic routed message to come back to the " +"originating \n" +"peer's inbound tunnel." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:115 +msgid "" +"This is not meant to provide a way for a peer's IP address to be " +"concealed, \n" +"merely as a way to let people behind firewalls and NATs fully operate " +"within \n" +"the network. Concealing the peer's IP address adds a little more work, as" +" \n" +"described <a href=\"#fullRestrictedRoutes\">below.</a>" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:121 +msgid "" +"With this technique, any router can participate as any part of a tunnel." +" \n" +"For efficiency purposes, a hidden peer would be a bad choice for an " +"inbound \n" +"gateway, and within any given tunnel, two neighboring peers wouldn't want" +" \n" +"to be hidden. But that is not technically necessary." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:133 +msgid "Both UDP and NIO have been Implemented in I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:134 +msgid "" +"Standard TCP communication in Java generally requires blocking socket \n" +"calls, and to keep a blocked socket from hanging the entire system, those" +" \n" +"blocking calls are done on their own threads. Our current TCP transport \n" +"is implemented in a naive fashion - for each peer we are talking to, we \n" +"have one thread reading and one thread writing. The reader thread simply" +" \n" +"loops a bunch of read() calls, building I2NP messages and adding them \n" +"to our internal inbound message queue, and the writer thread pulls " +"messages \n" +"off a per-connection outbound message queue and shoves the data through \n" +"write() calls." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:145 +msgid "" +"We do this fairly efficiently, from a CPU perspective - at any time, \n" +"almost all of these threads are sitting idle, blocked waiting for " +"something \n" +"to do. However, each thread consumes real resources (on older Linux " +"kernels, \n" +"for instance, each thread would often be implemented as a fork()'ed " +"process). \n" +"As the network grows, the number of peers each router will want to talk \n" +"with will increase (remember, I2P is fully connected, meaning that any \n" +"given peer should know how to get a message to any other peer, and " +"restricted \n" +"route support will probably not significantly reduce the number of " +"connections \n" +"necessary). This means that with a 100,000 router network, each router \n" +"will have up to 199,998 threads just to deal with the TCP connections!" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:157 +msgid "" +"Obviously, that just won't work. We need to use a transport layer that \n" +"can scale. In Java, we have two main camps:" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:162 +#, python-format +msgid "" +"Implemented in I2P 0.6 (\"SSU\") as documented <a " +"href=\"%(ssu)s\">elsewhere</a>" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:165 +msgid "" +"Sending and receiving UDP datagrams is a connectionless operation - if \n" +"we are communicating with 100,000 peers, we simply stick the UDP packets" +" \n" +"in a queue and have a single thread pulling them off the queue and " +"shoving \n" +"them out the pipe (and to receive, have a single thread pulling in any \n" +"UDP packets received and adding them to an inbound queue)." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:172 +msgid "" +"However, moving to UDP means losing the benefits of TCP's ordering, " +"congestion \n" +"control, MTU discovery, etc. Implementing that code will take significant" +" \n" +"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" +"a while ago I was taking some measurements in the simulator and on the \n" +"live net, and the vast majority of messages transferred would fit easily" +" \n" +"within a single unfragmented UDP packet, and the largest of the messages" +" \n" +"would fit within 20-30 packets. As mule pointed out, TCP adds a " +"significant \n" +"overhead when dealing with so many small packets, as the ACKs are within" +" \n" +"an order of magnitude in size. With UDP, we can optimize the transport \n" +"for both efficiency and resilience by taking into account I2P's " +"particular \n" +"needs." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:185 +msgid "It will be a lot of work though." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:188 +msgid "NIO or NBIO" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:189 +msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:192 +msgid "" +"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" +" \n" +"developers to take advantage of the operating system's nonblocking IO \n" +"capabilities - allowing you to maintain a large number of concurrent IO \n" +"operations without requiring a separate thread for each. There is much \n" +"promise with this approach, as we can scalable handle a large number of \n" +"concurrent connections and we don't have to write a mini-TCP stack with \n" +"UDP. However, the NIO packages have not proven themselves to be battle-" +"ready, \n" +"as the Freenet developer's found. In addition, requiring NIO support " +"would \n" +"mean we can't run on any of the open source JVMs like <a " +"href=\"http://www.kaffe.org/\">Kaffe</a>, \n" +"as <a href=\"http://www.classpath.org/\">GNU/Classpath</a> has only " +"limited \n" +"support for NIO. <i>(note: this may not be the case anymore, as there \n" +"has been some progress on Classpath's NIO, but it is an unknown " +"quantity)</i>" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:206 +#, python-format +msgid "" +"Another alternative along the same lines is the <a href=\"%(link)s\">Non" +" \n" +"Blocking I/O</a> package - essentially a cleanroom NIO implementation \n" +"(written before NIO was around). It works by using some native OS code \n" +"to do the nonblocking IO, passing off events through Java. It seems to \n" +"be working with Kaffe, though there doesn't seem to be much development \n" +"activity on it lately (likely due to 1.4's NIO deployment)." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:221 +msgid "" +"Within the current network database and profile management " +"implementation, \n" +"we have taken the liberty of some practical shortcuts. For instance, we \n" +"don't have the code to drop peer references from the K-buckets, as we \n" +"don't have enough peers to even plausibly fill any of them, so instead, \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" +"in memory without problems. While we have the capacity to use trimmed \n" +"down profiles (which we can maintain 100s of thousands in memory), we \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" +"eject a profile altogether. It just wouldn't be practical to write that \n" +"code yet, since we aren't going to need it for a while." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:236 +msgid "" +"That said, as the network grows we are going to want to keep these " +"considerations \n" +"in mind. We will have some work to do, but we can put it off for later." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:248 +#: i2p2www/pages/site/get-involved/todo.html:332 +#, python-format +msgid "" +"Addressed in I2P 0.5 as documented <a " +"href=\"%(tunnelimpl)s\">elsewhere</a>" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:251 +msgid "" +"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" +"going to Dave, then to Charlie, then Bob, and finally Alice " +"(A<--B<--C<--D<--E), \n" +"all five of them will know they are participating in tunnel \"123\", as \n" +"the messages are tagged as such. What we want to do is give each hop " +"their \n" +"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" +"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" +"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" +"the tunnel had the same tunnel ID, collusion attacks aren't much work." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:261 +msgid "" +"Adding a unique tunnel ID per hop isn't hard, but by itself, " +"insufficient. \n" +"If Dave and Bob are under the control of the same attacker, they wouldn't" +" \n" +"be able to tell they are in the same tunnel due to the tunnel ID, but \n" +"would be able to tell by the message bodies and verification structures \n" +"by simply comparing them. To prevent that, the tunnel must use layered \n" +"encryption along the path, both on the payload of the tunneled message \n" +"and on the verification structure (used to prevent simple tagging " +"attacks). \n" +"This requires some simple modifications to the TunnelMessage, as well \n" +"as the inclusion of per-hop secret keys delivered during tunnel creation" +" \n" +"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" +"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" +"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" +"signature of the hash of the (encrypted) payload at each step. The " +"gateway \n" +"then sends that 16-step encrypted message, along with a 16-step and " +"16-wide \n" +"encrypted mapping to the first hop, which then decrypts the mapping and \n" +"the payload with their secret key, looking in the 16-wide mapping for \n" +"the entry associated with their own hop (keyed by the per-hop tunnel ID)" +" \n" +"and verifying the payload by checking it against the associated signed \n" +"hash." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:282 +msgid "" +"The tunnel gateway does still have more information than the other peers" +" \n" +"in the tunnel, and compromising both the gateway and a tunnel participant" +" \n" +"would allow those peers to collude, exposing the fact that they are both" +" \n" +"in the same tunnel. In addition, neighboring peers know that they are \n" +"in the same tunnel anyway, as they know who they send the message to (and" +" \n" +"with IP-based transports without restricted routes, they know who they \n" +"got it from). However, the above two techniques significantly increase \n" +"the cost of gaining meaningful samples when dealing with longer tunnels." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:298 +msgid "Implemented in release 0.6.2" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:301 +#, python-format +msgid "" +"As Connelly <a href=\"%(link)s\">proposed</a> to deal with the\n" +"<a href=\"%(pdf1)s\">predecessor attack</a> <a href=\"%(pdf2)s\">(2008\n" +"update)</a>, keeping the order of peers within our tunnels consistent \n" +"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" +"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" +"get to substantially sample Alice's peer selection group. We may even \n" +"want to explicitly allow Bob to participate in Alice's tunnels in only \n" +"one way - receiving a message from Dave and sending it to Charlie - and \n" +"if any of those peers are not available to participate in the tunnel (due" +" \n" +"to overload, network disconnection, etc), avoid asking Bob to participate" +" \n" +"in any tunnels until they are back online." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:316 +msgid "" +"More analysis is necessary for revising the tunnel creation - at the \n" +"moment, we simply select and order randomly within the peer's top tier \n" +"of peers (ones with fast + high capacity)." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:321 +msgid "" +"Adding a strict ordering to peers in a tunnel also improves the anonymity" +" \n" +"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" +" \n" +"is always the same would be particularly damning. However, peers with \n" +"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" +"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" +"duration) minutes, use a 1-hop tunnel)." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:338 +msgid "" +"Without tunnel length permutation, if someone were to somehow detect that" +" \n" +"a destination had a particular number of hops, it might be able to use " +"that \n" +"information to identify the router the destination is located on, per the" +" \n" +"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" +"receives a tunnel message from Charlie and forwards it to Alice, Bob " +"knows \n" +"Alice is the final router in the tunnel. If Bob were to identify what " +"destination \n" +"that tunnel served (by means of colluding with the gateway and harvesting" +" \n" +"the network database for all of the LeaseSets), he would know the router" +" \n" +"on which that destination is located (and without restricted routes, that" +" \n" +"would mean what IP address the destination is on)." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:350 +msgid "" +"It is to counter user behavior that tunnel lengths should be permuted, \n" +"using algorithms based on the length requested (for example, the 1/MTBF \n" +"length change for 0-hop tunnels outlined above)." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:360 +msgid "" +"The restricted route functionality described before was simply a " +"functional \n" +"issue - how to let peers who would not otherwise be able to communicate \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" +"those peers, using them to both send and receive all of its messages. \n" +"Those hidden peers who want to be completely isolated would also refuse \n" +"to connect to peers who attempt to get them to (as demonstrated by the \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" +"clove that has a request for delivery to a particular peer and tunnel \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" +"to forward it as requested." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:379 +#, python-format +msgid "" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a <a " +"href=\"%(link)s\">Sybil</a> \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" +"a resource or running a peer aren't appropriate for use within I2P, as \n" +"doing so would compromise the anonymity of the system. Instead, we want \n" +"to make certain requests \"expensive\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:387 +msgid "" +"<a href=\"http://www.hashcash.org/\">Hashcash</a> is one technique that \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" +"creating a new destination (done only once when creating a service), or \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" +"that is sufficiently expensive while not an excessive burden for people \n" +"with few resources." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:398 +msgid "" +"There are a few other algorithms that we can explore for making those \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" +"appropriate." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:408 +#, python-format +msgid "" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" +"routers. To defend against these, we will want to essentially turn some \n" +"of the tunnels into its own mix cascade - delaying messages received at \n" +"the gateway and passing them in batches, reordering them as necessary, \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" +"messages by peers in the path). There has been a significant amount of \n" +"<a href=\"%(pdf)s\">research</a> \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" +"tunnel mixing strategies." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:421 +msgid "" +"In addition to the anonymity aspects of more varied tunnel operation, \n" +"there is a functional dimension as well. Each peer only has a certain \n" +"amount of data they can route for the network, and to keep any particular" +" \n" +"tunnel from consuming an unreasonable portion of that bandwidth, they \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" +"may be configured to throttle itself after passing 600 messages (1 per \n" +"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" +"last minute). Excess messages may be delayed or summarily dropped. With \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" +"tunnels, refusing to agree to allocate more bandwidth than the peer has \n" +"available." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:434 +msgid "" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" +"to avoid failed peers or to inject additional hops into the path. This \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" +"with instructions to redefine the next-hop in the tunnel." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:445 +msgid "" +"Beyond the per-tunnel batching and mixing strategy, there are further \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" +"each step in a garlic routed path to define a delay or window in which \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" +"clove exposed includes delay instructions." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:457 +#, python-format +msgid "" +"Performance related improvements are listed on the\n" +"<a href=\"%(futureperf)s\">Performance</a> page." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2 +msgid "Bounty Arabic translation of webpage and router console" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3 +#: i2p2www/pages/site/get-involved/bounties/index.html:119 +msgid "Arabic translation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6 +msgid "" +"To improve I2P usage and attract more people\n" +"into I2P echelon set out this bounty for translation\n" +"of the I2P web page and I2P router console into Arabic." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12 +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12 +msgid "This bounty is set into 2 subparts:" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14 +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14 +msgid "Part 1 is translation of the webpage." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17 +msgid "" +"For collecting the bounty of 20 BTC you need to translate the following " +"pages:" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 +msgid "" +"Part 2 is the translation of the router console. The router console was\n" +"partly translated and the bounty of 80 BTC was paid to hamada." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34 +msgid "Judge is echelon." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2 +msgid "Bounty creating a I2P native Bitcoin client" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3 +msgid "BTC I2P native client" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6 +msgid "" +"For a future of I2P and attract more people\n" +"into I2P this bounty is to create a I2P native Bitcoin client. \n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" +"the existant bitcoin network." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 +msgid "Judge is psychonaut who donated the first 30 € to this bounty." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:2 +msgid "Bounty datastorage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:3 +msgid "datastore" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:6 +msgid "" +"To improve I2P's usage and to be independent of routers \n" +"online status we want a datastorage as a extension to I2P.\n" +"Like in Freenet the datastorage should be distributed and every\n" +"participating node should be able to configure his options.\n" +"The files should be saved in chunks and at least 2-3 times to\n" +"obtain redundancy. Usage of storage space should be auto balanced.\n" +"As it is a extra application, it should work flawless within I2P and\n" +"cooperate nice with the I2P router. Maybe a integration within the\n" +"webpage/router could be done." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:17 +msgid "" +"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n" +"\"eepsites in datastorage\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:21 +msgid "" +"The frost for I2P datastorage bounty is paid for a frost like program \n" +"with which files/messages are stored into database and got from database." +"\n" +"It needs to work with a GUI." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:26 +msgid "" +"The eepsite served out of I2P datastorage extends a I2P router to send\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" +"saved inside of datastorage and are taken from it.\n" +"Extension:\n" +"For better integration all datastorage participants could serve that " +"eepsite." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:36 +msgid "" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" +"free to distribute)." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2 +msgid "Bounty I2P package in Debian and Ubuntu mirrors" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3 +msgid "I2P Ubuntu/Debian package" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 +msgid "" +"For the future of I2P and in order to attract more people\n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" +"archive mirrors.\n" +"To claim this bounty, the I2P router package needs to be available from\n" +"Ubuntu and Debian archive mirrors and Debian bug \n" +"<a href=\"http://bugs.debian.org/cgi-" +"bin/bugreport.cgi?bug=448638\">448638</a> \n" +"needs to be closed successfully." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2 +msgid "Bounty I2PHex code implementation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3 +msgid "i2phex code implementation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6 +msgid "" +"To improve I2P usage and attract more people\n" +"into I2PHex P2P ArneBab setout the bounty for implementing actual\n" +"Phex code onto I2PHex." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:2 +msgid "Bounties" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:5 +msgid "Bounties for I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:6 +msgid "" +"While we always gratefully accept any contributions of code, \n" +"documentation, and the like, there are other ways to help I2P move \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" +"rapidly if we were able to support all of our contributors to work on \n" +"I2P full time. However, as with any open source project, that's not a \n" +"possibility. Instead, we are making use of a bounty system, whereby \n" +"anyone can get support for working on something that people want \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" +"their support goes to what they care about." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:18 +msgid "" +"We are also keeping open the ability for people who want to support I2P \n" +"but don't have strong feelings about the bounties available. Those " +"people\n" +"can simply put their trust in the I2P team to do what we feel is best by\n" +"donating to a catch-all general fund that will be used as deemed \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" +"etc), and the like." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:27 +msgid "Current bounties" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:30 +#: i2p2www/pages/site/get-involved/bounties/index.html:92 +#: i2p2www/pages/site/get-involved/bounties/index.html:105 +msgid "Name" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:30 +#: i2p2www/pages/site/get-involved/bounties/index.html:92 +#: i2p2www/pages/site/get-involved/bounties/index.html:105 +msgid "Status" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:30 +#: i2p2www/pages/site/get-involved/bounties/index.html:92 +msgid "Judge" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:30 +#: i2p2www/pages/site/get-involved/bounties/index.html:92 +msgid "Dev" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:30 +#: i2p2www/pages/site/get-involved/bounties/index.html:92 +msgid "Bounty" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:32 +msgid "Frost for I2P datastorage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:33 +#: i2p2www/pages/site/get-involved/bounties/index.html:40 +#: i2p2www/pages/site/get-involved/bounties/index.html:47 +#: i2p2www/pages/site/get-involved/bounties/index.html:54 +#: i2p2www/pages/site/get-involved/bounties/index.html:75 +#: i2p2www/pages/site/get-involved/bounties/index.html:82 +msgid "Proposal in development" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:35 +#: i2p2www/pages/site/get-involved/bounties/index.html:42 +#: i2p2www/pages/site/get-involved/bounties/index.html:49 +#: i2p2www/pages/site/get-involved/bounties/index.html:56 +#: i2p2www/pages/site/get-involved/bounties/index.html:77 +#: i2p2www/pages/site/get-involved/bounties/index.html:97 +msgid "vacant" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:39 +msgid "Eepsites served out of I2P datastorage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:46 +msgid "Backporting Phex code onto I2PHex" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:53 +msgid "I2P package in Debian and Ubuntu mirrors" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:60 +msgid "Bitcoin client for I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:61 +msgid "Done, phase of verification" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:67 +msgid "Unit tests and Multi-router Simulation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:68 +msgid "Partly done, partly in work, partly still open" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:89 +msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:94 +msgid "Bundling bounties" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:95 +msgid "Proposed" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:102 +msgid "Claimed bounties" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:105 +msgid "Dev team" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:107 +msgid "Make I2P IPv6 native" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:114 +msgid "Setting up a SILC server" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:124 +msgid "Datastore over I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:129 +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3 +msgid "Russian translation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:134 +msgid "Swarming file transfer" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:139 +msgid "Streaming library window size" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:144 +msgid "IRC connect time monitor" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:149 +msgid "Unit tests (part 1)" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:161 +msgid "" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" +"people listed!" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2 +msgid "Bounty I2P IPv6 native" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3 +msgid "native IPv6 I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6 +msgid "" +"For a future of I2P and attract more people\n" +"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n" +"To claim this bounty, the I2P router needs to run full on native\n" +"IPv6 connections like it does on IPv4." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17 +#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 +msgid "" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" +"free to distribute)." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/netdb.html:2 +msgid "NetDB Backend" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/netdb.html:3 +msgid "netDB backend" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/netdb.html:7 +msgid "" +"The current NetDB implementation (namely the FloodFill system)\n" +"needs to be extended with another backend to improve reliability,\n" +"reduce attack surface and solve the scalability issue for the \n" +"coming years." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/netdb.html:14 +msgid "" +"A solution likely based on a DHT will be investigated and \n" +"finally implemented." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2 +msgid "Bounty russian translation of webpage and router console" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6 +msgid "" +"To improve I2P usage and attract more people\n" +"into I2P a anonymous donator set out the bounty for translation\n" +"of the I2P web page and I2P router console into russian language." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 +msgid "" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 +msgid "" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" +"to be translated to collect the bounty of $115 USD." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37 +msgid "Judge is the russian donor." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:2 +msgid "Bounty migrate I2P IRC to SILC" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:3 +msgid "I2P silc server" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:7 +msgid "" +"For a future of I2P and attract more people\n" +"into I2P this bounty is to setup and host a I2P SILC server. \n" +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:12 +msgid "" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" +"A second server should be set up, to." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:16 +msgid "" +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:22 +msgid "Judge is An Anonymous Secret Society, society@mail.i2p." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2 +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3 +msgid "Syndie development" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7 +msgid "" +"Beside of I2P we want to encourage users\n" +"to care more about anonymity and security. As I2P is a low \n" +"latency network with its natural limits, the software SYNDIE\n" +"can overcome some of these limits and provide better anonymity\n" +"for people who really need it." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14 +msgid "" +"For our bad sake the syndie project was out of development for \n" +"quite a long time yet (5 years). To get a fresh and new built \n" +"with needed bugfixes we set out this bounty. Also syndie needs\n" +"some enhancements and a better GUI for users to work with it.\n" +"Current bounty sum is 50 Bitcoin." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22 +msgid "" +"The latest Syndie coding rally did improve the situation of the\n" +"Syndie package dramatically. A new Syndie package with bugfixes\n" +"was created and made available on different webpages.\n" +"As a result of this work, the bounty sum was reduced and\n" +"the withdrawn money moved to the IPv6 bounty." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2 +msgid "Bounty unittests" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3 +msgid "unit test" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7 +msgid "" +"To improve I2P's maintainability, we want to have a solid set of\n" +"automated unit tests for the critical code. While we do have some\n" +"unit tests at the moment, they are ad-hoc and partly unfinished. \n" +"This bounty is for someone to check the existing tests and move over\n" +"old ones to jUnit, automate their execution, extend them to provide \n" +"better code coverage, and publish the report online. Its a massive \n" +"effort, but can be broken down into phases, listed below (phase 2 \n" +"must occur first, but further phases may happen in any order).\n" +"As this needs some reading of code, it is the best start point for\n" +"new devs to get a good overview of I2P code and coding. A good job\n" +"for college students, interns or anyone who is just interested." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20 +msgid "" +"Take care! Jobs and bounties shuffled a bit!\n" +"Phase 6,7 and 8 are still open!" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112 +#, python-format +msgid "Phase %(phase)s:" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27 +msgid "CI jenkins and IRC bot" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114 +#, python-format +msgid "Bounty: %(euro)s €" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29 +msgid "server runs and this section is blocked" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31 +msgid "" +"To collect this bounty, a continuous integration server (Jenkins,\n" +"old name was Hudson) must be set up and a connected IRC bot needs \n" +"to set up in the channel #i2p-dev on IRC2p network to print out\n" +"results of build tests.<br>\n" +"The server needs to be run long term." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41 +msgid "Check existing SDK tests" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69 +msgid "paid to str4d" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45 +#, python-format +msgid "" +"To collect this bounty, the existing SDK tests must be checked \n" +"and made to work again. The need to be integrated into the ant \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" +"<a href=\"%(clover)s\">Clover</a>). The ant script\n" +"must be capable of generating test status results as a web page, \n" +"which will be published online." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56 +msgid "SDK test coverage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80 +msgid "paid to unittests dev team" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60 +msgid "" +"To collect this bounty, the automated unit tests of the SDK \n" +"(i2p/core/java/src) must work again." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67 +msgid "Router test migration" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71 +msgid "" +"As with phase 2, the existing unit tests for the router must be\n" +"moved over to the automated system." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78 +msgid "Router test coverage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82 +msgid "" +"To collect this bounty, the automated unit tests of the router \n" +"(i2p/router/java/src) must work again." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89 +msgid "Streaming lib tests" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94 +msgid "" +"To collect this bounty, a new set of unit tests must meet a \n" +"measured code coverage of 90% of the streaming lib \n" +"(i2p/apps/ministreaming/ and i2p/apps/streaming/)." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102 +msgid "Unit tests coverage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106 +msgid "" +"To collect this bounty, all above unit tests must meet the 100%\n" +"coverage marker (except for log statements)." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113 +msgid "MultiRouter simulation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115 +msgid "will be split in more sub-tasks" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117 +msgid "" +"To collect this bounty, the existing in-memory multi-router\n" +"simulation must be checked, made work again and extend to simulate\n" +"lots of routers in memory on a single machine. This bounty will\n" +"be split in more fine grained subworks." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126 +msgid "" +"Judge on all these works is the donor and donor decides if a phase is\n" +"called succesfull done and money can be paid." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2 +msgid "Bounty I2P vuze plugin" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3 +msgid "vuze plugin" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6 +msgid "" +"To improve I2P usage and attract more people\n" +"into I2P torrent P2P I setout the bounty for a working I2P vuze\n" +"plugin.\n" +"The plugin needs to be official and submitted to vuze for publication\n" +"on their webpage/repository for plugins.\n" +"It should be easy to install and configured, work smooth and flawless.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" +"It should work with *.b32.i2p destinations as with signed (516++ bits) \n" +"destinations." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:2 +msgid "Application Development" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:3 +msgid "May 2013" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:6 +msgid "Application Development Guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:8 +msgid "Contents" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:10 +#: i2p2www/pages/site/get-involved/develop/applications.html:16 +msgid "Why write I2P-specific code?" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:11 +#: i2p2www/pages/site/get-involved/develop/applications.html:102 +msgid "Important concepts" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:12 +#: i2p2www/pages/site/get-involved/develop/applications.html:190 +msgid "Development options" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:13 +#: i2p2www/pages/site/get-involved/develop/applications.html:303 +msgid "Start developing - a simple guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:18 +#, python-format +msgid "" +"There are multiple ways to use applications in I2P.\n" +"Using <a href=\"%(i2ptunnel)s\">I2PTunnel</a>,\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" +"This is very effective for client-server scenario's,\n" +"where you need to connect to a single website.\n" +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in <a href=\"#tunnel.serverclient\">Figure 1</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:26 +msgid "" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" +"as shown in <a href=\"#tunnel.peertopeer\">Figure 2</a>.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" +"In addition, with many protocols you will need to force everyone to \n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" +"(host and port)." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:37 +msgid "" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" +"can avoid compromising user identities." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:43 +msgid "" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" +"fragmentation of messages." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:57 +#: i2p2www/pages/site/get-involved/develop/applications.html:59 +msgid "" +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:59 +msgid "Figure 1:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:64 +#: i2p2www/pages/site/get-involved/develop/applications.html:66 +msgid "" +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:66 +msgid "Figure 2:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:70 +msgid "In summary, a number of reasons to write I2P-specific code:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:74 +msgid "" +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:78 +msgid "" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" +"that does not leak such information, keeping users anonymous and secure." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:83 +msgid "" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" +"on I2P, which is a network with a much higher latency." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:90 +#, python-format +msgid "" +"I2P supports a standard <a href=\"%(plugins)s\">plugins interface</a> for" +" developers\n" +"so that applications may be easily integrated and distributed." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:96 +msgid "" +"Applications written in Java and accessible/runnable\n" +"using an HTML interface via the standard webapps/app.war\n" +"may be considered for inclusion in the i2p distribution." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:104 +msgid "There are a few changes that require adjusting to when using I2P:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:108 +msgid "Destination ~= host+port" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:110 +msgid "" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" +"plus port number pair, though there are a few differences." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:118 +msgid "" +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:123 +msgid "" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" +"must stay on a single host." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:130 +msgid "" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" +"certificate, which may contain proof of work or blinded data." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:135 +#, python-format +msgid "" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" +"managed using \"subscriptions\" to naming services).\n" +"There may be some secure, human readable, scalable, and globally \n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" +"since there are those who don't think such a beast is possible.\n" +"<a href=\"%(naming)s\">Further information on the naming system</a> is " +"available." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:149 +#, python-format +msgid "" +"While most applications do not need to distinguish protocols and ports,\n" +"I2P <em>does</em> support them. Complex applications may specify a " +"protocol,\n" +"from port, and to port, on a per-message basis, to multiplex traffic on\n" +"a single destination.\n" +"See the <a href=\"%(datagrams)s\">datagram page</a> for details.\n" +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:158 +msgid "Anonymity and confidentiality" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:160 +msgid "" +"I2P has transparent end to end encryption\n" +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:167 +msgid "" +"Of course, I2P transparently anonymizes the\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" +"to expose." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:176 +msgid "I2P datagrams can be up to several KB" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:178 +#, python-format +msgid "" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" +"See the <a href=\"%(datagrams)s\">datagram page</a> for details.\n" +"For many applications, 10 KB of data is sufficient for an\n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" +"application without having to write fragmentation, resends, etc." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:192 +msgid "" +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:197 +msgid "Streaming Lib" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:198 +#, python-format +msgid "" +"The <a href=\"%(streaming)s\">full streaming library</a> is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the <a href=\"#start.streaming\">Streaming development guide</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:204 +#, python-format +msgid "" +"BOB is the <a href=\"%(bob)s\">Basic Open Bridge</a>,\n" +"allowing an application in any language to make streaming connections \n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" +"is planned in the near future. BOB also contains several tools, such as \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" +"found at this <a href=\"http://%(boburl)s/\">eepsite</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:217 +msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:218 +#, python-format +msgid "" +"SAM is the <a href=\"%(sam)s\">Simple Anonymous Messaging</a> protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" +"and event based handling. SAM supports three styles of operation:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:225 +msgid "" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:228 +msgid "" +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:231 +msgid "" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" +"is self authenticating)" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:237 +msgid "" +"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" +"communications with the SAM bridge." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:244 +#, python-format +msgid "" +"<a href=\"%(samv2)s\">SAM V2</a> is a new version used by imule\n" +"that fixes some of the problems in <a href=\"%(sam)s\">SAM</a>.\n" +"<br />\n" +"<a href=\"%(samv3)s\">SAM V3</a> is used by imule since version 1.4.0." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:252 +msgid "" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" +"their own unique I2P destination and their own set of tunnels, keys, etc." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:264 +msgid "" +"I2P supports a SOCKS V4 and V5 proxy.\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" +"and untested." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:271 +msgid "Removed" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:272 +msgid "" +"There used to be a simple \"ministreaming\" library,\n" +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:277 +msgid "Datagrams" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:278 +msgid "Recommended for UDP-like applications" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:279 +#, python-format +msgid "" +"The <a href=\"%(datagrams)s\">Datagram library</a> allows sending UDP-" +"like packets.\n" +"It's possible to use:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:284 +msgid "Repliable datagrams" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:285 +msgid "Raw datagrams" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:289 +msgid "Not recommended" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:290 +#, python-format +msgid "" +"<a href=\"%(i2cp)s\">I2CP</a> itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:297 +msgid "Web Applications" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:298 +msgid "" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"server instead is straightforward.\n" +"Any standard web app technology should work." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:304 +msgid "" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the <a " +"href=\"#start.streaming\">streaming library</a> or datagram library.\n" +"Using another programming language, SAM or BOB can be used." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:310 +msgid "Developing with the streaming library" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:312 +msgid "" +"The following example shows how to create TCP-like client and server " +"applications\n" +"using the streaming library." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:317 +msgid "This will require the following libraries in your classpath:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:321 +msgid "The streaming library itself" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:322 +msgid "Factory and interfaces for the streaming library" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:323 +msgid "Standard I2P classes, data structures, API, and utilities" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:326 +msgid "" +"Network communication requires the usage of I2P network sockets.\n" +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:331 +msgid "" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" +"and creating an I2PServerSocket.\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" +"so it will create a new Destination for us.\n" +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:362 +msgid "Code example 1: initializing the server application." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:364 +msgid "" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" +"A real server would have to be able to handle multiple clients.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" +"The bold code is the new code we add." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:448 +msgid "Code example 2: accepting connections from clients and handling messages." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:452 +msgid "" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" +"one huge block of characters):" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:466 +msgid "" +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:470 +msgid "" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" +"Again, we will need to start by getting an I2PSocketManager.\n" +"We won't use an I2PSession and an I2PServerSocket this time.\n" +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:554 +msgid "" +"Code example 3: starting the client and connecting it to the server " +"application." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:556 +msgid "" +"Finally, you can run both the server and the client application.\n" +"First, start the server application. It will print a Destination string " +"(like shown <a href=\"#start.streaming.destination\">above</a>).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:562 +msgid "Congratulations, you have successfully communicated over I2P!" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:566 +msgid "Existing Applications" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:567 +msgid "Contact us if you would like to contribute." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:588 +msgid "Application Ideas" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:590 +msgid "NNTP server - there have been some in the past, none at the moment" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:593 +msgid "" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:596 +msgid "PGP Key server and/or proxy" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:599 +msgid "" +"Content Distribution / DHT applications - resurrect feedspace,\n" +"port dijjer, look for alternatives" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:603 +msgid "Help out with <a href=\"http://syndie.i2p2.de/\">Syndie</a> development" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:606 +msgid "" +"Web-based applications - The sky is the limit for hosting web-server-" +"based\n" +"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n" +"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:611 +msgid "" +"Resurrect some old apps, several previously in the i2p source package -\n" +"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2 +msgid "I2P Developer's MTN Keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4 +msgid "MTN Keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5 +msgid "" +"Monotone servers used by the I2P project require two types of keys to be " +"used." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 +msgid "" +"<a href=\"#commit\">Commit Keys</a> to sign changes checked-in to the " +"respository; and" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10 +msgid "" +"<a href=\"#transport\">Transport Keys</a> to push changes to remote " +"servers." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13 +#, python-format +msgid "" +"Everyone that uses Monotone to checkout the I2P codebase will need to\n" +"<a href=\"%(monotone)s#obtaining-and-deploying-developers-" +"keys\">import</a> the\n" +"developer commit keys, but only Monotone <a " +"href=\"%(monotone)s#operating-a-monotone-server\">\n" +"server operators</a> will need to import the <a " +"href=\"#transport\">transport keys</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20 +msgid "Developer Commit keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:247 +msgid "Developer Transport Keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:248 +#, python-format +msgid "" +"<b>Note:</b> Transport keys are only needed for setting up a\n" +"<a href=\"%(monotone)s#operating-a-monotone-server\">Monotone server</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2 +msgid "License Agreements" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5 +#, python-format +msgid "For more information see <a href=\"%(licenses)s\">the licenses page</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8 +msgid "" +"Following is a monotonerc file defining the current trust list.\n" +"Developers must use this file in ~/.monotone/monotonerc or\n" +"_MTN/montonerc in their i2p.i2p workspace." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17 +msgid "Agreements" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:2 +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115 +msgid "Licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:4 +msgid "I2P Software Licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:5 +#, python-format +msgid "" +"As required by our\n" +"<a href=\"%(threatmodel)s\">threat model</a> (among other reasons), the \n" +"software developed to support the anonymous communication \n" +"network we call I2P must be freely available, open source, \n" +"and user modifiable. To meet these criteria, we make use of\n" +"a variety of legal and software engineering techniques so\n" +"as to remove as many barriers to entry for those considering\n" +"making use of or contributing to the I2P effort." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:16 +msgid "" +"While the information below may be more confusing than just simply \n" +"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n" +"the short answer to the question \"How is I2P licensed?\" is this:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:22 +msgid "All software bundled in the I2P distributions will allow:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:24 +msgid "use without fee" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:25 +msgid "" +"use with no restrictions on how, when, where, why, or by whom is running " +"it" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:26 +msgid "access to the source code without fee" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:27 +msgid "modifications to the source" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:30 +msgid "" +"Most of the software guarantees much more - the ability of <b>anyone</b> " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" +"we lose out." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:43 +msgid "Component licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:44 +msgid "" +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:57 +msgid "Component" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:58 +msgid "Source path" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:59 +msgid "Resource" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:60 +msgid "Primary license" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:61 +msgid "Alternate licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:62 +msgid "Lead developer" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:271 +msgid "GPL + java exception" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:272 +#, python-format +msgid "" +"While it may be redundant, just for clarity the\n" +"<a href=\"%(gpl)s\">GPL</a>'ed code included within\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" +"explicitly authorizing the use of Java's standard libraries:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:288 +msgid "" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" +"resource packaging may be changed if the repository is reorganized." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:296 +msgid "Commit privileges" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:297 +#, python-format +msgid "" +"Developers may push changes to a distributed monotone repository if you\n" +"receive permission from the person running that repository.\n" +"See the <a href=\"%(monotone)s\">Monotone Page</a> for details." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:303 +msgid "" +"However, to have changes included in a release, developers\n" +"must be trusted by the release manager (currently zzz).\n" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:310 +msgid "" +"Unless marked otherwise, all code I commit is implicitly licensed under\n" +"the component's primary license" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:314 +msgid "" +"If specified in the source, the code may be explicitly licensed under one" +"\n" +"of the component's alternate licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:318 +msgid "" +"I have the right to release the code I commit under the terms I\n" +"am committing it" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:324 +#, python-format +msgid "" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" +"information.\n" +"<a href=\"%(licenseagreements)s\">See developers' license agreements</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2 +msgid "Release Signing Key" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4 +msgid "Releases 0.7.6 and later are signed by zzz. His public key is:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40 +msgid "" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2 +msgid "Signed Developer Keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 +msgid "" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" +"verified differently, since he's away, and only left a binary detached\n" +"signature for his key." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16 +msgid "Monotone keys for zzz" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47 +msgid "Monotone keys for welterde" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79 +msgid "Monotone keys for Complication" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114 +msgid "Monotone keys for jrandom" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169 +msgid "Others" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 +msgid "" +"<u>Tip:</u> To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" +"76BA A76E 0BED`." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 +msgid "" +"<b>Tip:</b> To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" +"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 +msgid "" +"<b>Tip:</b> To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" +"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 +msgid "" +"<b>Tip:</b> To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" +"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" +"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 +msgid "" +"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" +"below." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 +msgid "" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" +"mtn-committers.asc`:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 +msgid "" +"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" +"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" +"`mtn-committers` file:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170 +#, python-format +msgid "" +"Some of the developers have included their Monotone keys in their <a " +"href=\"%(licenseagreements)s\">signed license agreement</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2 +msgid "Developer Guidelines and Coding Style" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4 +#, python-format +msgid "Read the <a href=\"%(newdevs)s\">new developers guide</a> first." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8 +msgid "Basic Guidelines and Coding Style" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10 +msgid "" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" +"programming envrionment.\n" +"The following applies mostly to the main development branch i2p.i2p.\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" +"check with the appropriate developer for guidance." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18 +msgid "Community" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20 +msgid "" +"Please don't just \"write code\". If you can, participate in other " +"development activities, including:\n" +"development discussions and support on IRC, zzz.i2p, and forum.i2p; " +"testing;\n" +"bug reporting and responses; documentation; code reviews; etc." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25 +msgid "" +"Active devs should be available periodically on IRC #i2p-dev.\n" +"Be aware of the current release cycle.\n" +"Adhere to release milestones such as feature freeze, tag freeze, and\n" +"the checkin deadline for a release." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 +msgid "" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" +"used monotone before. Ask for help if you need it.\n" +"Once pushed, checkins are forever, there is no undo. Please be careful.\n" +"If you have not used monotone before, start with baby steps.\n" +"Check in some small changes and see how it goes." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42 +msgid "" +"Test your changes before checking them in.\n" +"If you prefer the checkin-before-test development model,\n" +"use your own development branch (e.g. i2p.i2p.yourname.test)\n" +"and propagate back to i2p.i2p once it is working well.\n" +"Do not break the build. Do not cause regressions.\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" +"you push your change." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51 +msgid "" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" +"and increment the build revision in RouterVersion.java." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56 +msgid "" +"Ensure that you have the latest monotonerc file in _MTN.\n" +"Do not check in on top of untrusted revisions." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60 +msgid "" +"Ensure that you pull the latest revision before you check in.\n" +"If you inadvertently diverge, merge and push as soon as possible.\n" +"Don't routinely make others merge for you.\n" +"Yes, we know that monotone says you should push and then merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" +"without creating a merge revision." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 +msgid "" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" +"and do the development there so you do not block releases." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75 +msgid "Coding Style" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77 +msgid "" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" +"In some places, the coding style is different.\n" +"Use common sense. Emulate the style in the file you are modifying." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84 +msgid "" +"New classes and methods require at least brief javadocs. Add @since " +"release-number." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 +msgid "" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" +"Be careful not to make any changes that break compatibility.\n" +"Don't add methods to the API unless they are of general utility.\n" +"Javadocs for API methods should be clear and complete.\n" +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95 +msgid "" +"Tag strings for translation where appropriate.\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" +"translators have a chance to update before the release." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 +msgid "" +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104 +msgid "" +"We require Java 6 to build but only Java 5 to run I2P.\n" +"Do not use Java 6 classes or methods without handling the class not found" +" exceptions\n" +"and providing alternate Java 5 code. See classes in net.i2p.util for " +"examples." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109 +msgid "" +"Explicitly convert between primitive types and classes;\n" +"don't rely on autoboxing/unboxing." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117 +msgid "" +"Only check in code that you wrote yourself.\n" +"Before checking in any code or library jars from other sources,\n" +"justify why it is necessary,\n" +"verify the license is compatible,\n" +"and obtain approval from the lead developer." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124 +msgid "" +"For any images checked in from external sources,\n" +"it is your responsibility to first verify the license is compatible.\n" +"Include the license and source information in the checkin comment." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131 +msgid "Bugs" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133 +#, python-format +msgid "" +"Managing Trac tickets is everybody's job, please help.\n" +"Monitor %(trac)s for tickets you have been assigned or can help with.\n" +"Assign, categorize, comment on, fix, or close tickets if you can." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138 +msgid "" +"Close a ticket when you think you've fixed it.\n" +"We don't have a test department to verify and close tickets.\n" +"If you arent sure you fixed it, close it and add a note saying\n" +"\"I think I fixed it, please test and reopen if it's still broken\".\n" +"Add a comment with the dev build number or revision and set\n" +"the milestone to the next release." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:2 +msgid "Using an IDE with I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:4 +msgid "" +"The main I2P development branch (<code>i2p.i2p</code>) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:10 +msgid "" +"The main I2P development branches (<code>i2p.i2p</code> and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:16 +msgid "" +"Check out the I2P branch into some directory (e.g. " +"<code>$HOME/dev/i2p.i2p</code>)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:20 +msgid "" +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:24 +msgid "" +"Select \"File - Import...\" and then under \"General\" select \"Existing " +"Projects into Workspace\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:28 +msgid "" +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:32 +msgid "If necessary, click \"Refresh\" to refresh the list of projects." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:36 +msgid "Select every project in the list, and click \"Finish\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:40 +msgid "" +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:48 +msgid "" +"The main I2P development branches (<code>i2p.i2p</code> and branches from" +" it) contain NetBeans project files." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:2 +msgid "Monotone" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:4 +msgid "Monotone Guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:9 +msgid "Operating a Monotone client" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:11 +#: i2p2www/pages/site/get-involved/guides/monotone.html:63 +msgid "Generating Monotone keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:12 +msgid "Trust and initializing your repository" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:13 +#: i2p2www/pages/site/get-involved/guides/monotone.html:196 +msgid "Obtaining and deploying developers' keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:14 +#: i2p2www/pages/site/get-involved/guides/monotone.html:227 +msgid "Setting up trust evaluation hooks" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:15 +#: i2p2www/pages/site/get-involved/guides/monotone.html:268 +msgid "" +"Pulling the <code>i2p.i2p</code>, <code>i2p.www</code> and " +"<code>i2p.syndie</code> branches" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:16 +#: i2p2www/pages/site/get-involved/guides/monotone.html:308 +msgid "Verifying that trust evaluation works" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:17 +#: i2p2www/pages/site/get-involved/guides/monotone.html:357 +msgid "Checking out a working copy of the latest version" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:18 +#: i2p2www/pages/site/get-involved/guides/monotone.html:384 +msgid "Updating your working copy to the latest version" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:22 +#: i2p2www/pages/site/get-involved/guides/monotone.html:414 +msgid "Operating a Monotone Server" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:24 +msgid "Obtaining and deploying developers’ transport keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:25 +#: i2p2www/pages/site/get-involved/guides/monotone.html:424 +msgid "Granting push and pull access" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:26 +#: i2p2www/pages/site/get-involved/guides/monotone.html:469 +msgid "Running Monotone in server mode" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:27 +#: i2p2www/pages/site/get-involved/guides/monotone.html:494 +msgid "Differences under Debian GNU/Linux" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:34 +#, python-format +msgid "" +"This is a revised version of <a " +"href=\"%(transitionguide)s\">Complication's original\n" +" guide</a> detailing the use of Monotone in I2P development.\n" +" For basic instructions see the <a href=\"%(newdevs)s\">quick-start " +"guide</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:42 +#, python-format +msgid "" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered <a " +"href=\"http://www.monotone.ca/\">Monotone</a> (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a <a href=\"%(licenses)s#commit\">license agreement</a> needs to be " +"signed\n" +" before commit rights are granted)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:52 +msgid "" +"Some of Monotone's noteworthy qualities are: distributed\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" +" having the ability to resume interrupted synchronization attempts." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:61 +msgid "Operating a Monotone Client" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:66 +msgid "" +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:74 +msgid "" +"Without a transport key, one cannot:\n" +" <ul>\n" +" <li>pull code from a server which doesn't allow global read " +"access</li>\n" +" <li>push code to any server</li>\n" +" <li>run a Monotone server</li>\n" +" </ul>" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:85 +msgid "" +"Without a commit key, one cannot:\n" +" <ul>\n" +" <li>commit any code</li>\n" +" </ul>" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:94 +msgid "" +"If you only intend to retrieve code from MTN, feel free to skip to the\n" +" <a href=\"#trust-and-initializing-your-repository\">next section</a>. " +"If you want\n" +" to generate keys, read the following." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:102 +msgid "" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" +" address does not need to exist. For example, your keys might be named:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:113 +msgid "" +"Monotone stores keys under <code><b>$HOME/.monotone/keys</b></code> in " +"text files which\n" +" are named identically to the keys. For example:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:123 +msgid "" +"To generate transport and commit keys, enter the following commands at a " +"prompt:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:133 +msgid "" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" +" Monotone server." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:141 +msgid "Trust, and initializing your repository" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:145 +msgid "" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" +" not replace reading diffs." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:155 +msgid "" +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:161 +msgid "" +"After <a href=\"#obtaining-and-deploying-developers-keys\">importing the " +"developers' keys into Monotone</a> and\n" +" <a href=\"#setting-up-trust-evaluation-hooks\">setting up trust " +"evaluation hooks</a>,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" +" needed due to the push access policies in place." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:171 +msgid "" +"A repository can hold many branches. For example, our repository holds " +"the\n" +" following main branches:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:176 +msgid "The I2P router and associated programs" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:177 +msgid "The I2P project website" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:178 +msgid "Syndie, a distributed forums tool" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:183 +msgid "" +"By convention, the I2P Monotone repository is named <code>i2p.mtn</code>." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" <code>i2p.mtn</code> file and branch directories to be stored and issue" +" the following\n" +" command:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:199 +msgid "" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" +" " +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:206 +#, python-format +msgid "" +"Developers' commit keys are provided GPG-signed <a " +"href=\"%(signedkeys)s\">on another page</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:212 +#, python-format +msgid "" +"To import developers' keys after verifying their authenticity, copy <a " +"href=\"%(devkeys)s\">all of the keys</a> into a new\n" +" file. Create this file (e.g. <code><b>keys.txt</b></code>) in the same " +"directory where <code>i2p.mtn</code> is located. Import the keys with the" +" command:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:222 +msgid "" +"<b>Note</b>: <i>Never</i> add keys to " +"<code><b>$HOME/.monotone/keys</b></code> manually." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:230 +msgid "" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" +" That is not acceptable for I2P development." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:237 +msgid "" +"Change into the directory <code><b>$HOME/.monotone</b></code> and open " +"the file\n" +" <code>monotonerc</code> with a text editor. Copy and paste the " +"following two functions into this file:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:246 +msgid "" +"The first function determines an intersection between two sets, in our " +"case a\n" +" revision's signers and trusted signers." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:253 +msgid "" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" +" revision is trusted. Otherwise, the revision is not trusted." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:262 +msgid "" +"More information about Trust Evauluation Hooks can be found in the <a " +"href=\"http://www.monotone.ca/docs/Hooks.html\">official Monotone " +"documentation</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:271 +msgid "" +"Enter the directory where you initialized <code>i2p.mtn<code>. Depending " +"on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" +" perform the <code>pull</code> operation in different ways." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:279 +msgid "If you only want I2P sources:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:288 +msgid "If you want all branches:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:294 +msgid "" +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:300 +msgid "" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" +" to selectively provide some people with tampered data." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:311 +msgid "To verify that trust evaluation works:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:315 +msgid "Make a backup of your <code>monotonerc</code> file." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:316 +msgid "" +"Modify <code><b>monotonerc</b></code> by setting the trusted_signers " +"variable in the following way:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:322 +msgid "" +"With <code><b>monotonerc</b></code> configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where <code>i2p.mtn</code> was created and attempt a checkout " +"of the I2P branch:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:332 +msgid "" +"A directory named <code>i2p.i2p</code> should <b>not</b> appear. You " +"should encounter many\n" +" error messages like:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:349 +msgid "" +"If you are satisfied with results, restore the backup of\n" +" <code>monotonerc</code> that was created above. If you didn't create a " +"backup\n" +" as advised, re-read <a href=\"#setting-up-trust-evaluation-" +"hooks\">Setting up trust evaluation hooks</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:360 +msgid "" +"If you already have a branch checked out, skip to the <a href" +"=\"#updating-your-working-copy-to-the-latest-version\">next\n" +" section</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:367 +msgid "" +"Change into the directory where <code>i2p.mtn</code> is located. Over " +"there issue:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:376 +msgid "" +"The checkout should complete without error messages and a directory named" +"\n" +" <code>i2p.i2p</code> should appear in the current directory. " +"Congratulations! You have\n" +" successfully checked out the latest I2P sources, ready to be compiled." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:387 +msgid "" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" +" <code>i2p.mtn</code> is located and issue:\n" +" <ul>\n" +" <li>$ <code><b>mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 " +"i2p.i2p</b></code></li>\n" +" </ul>" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:398 +msgid "Now change into your <code>i2p.i2p</code> directory, and over there issue:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:407 +msgid "" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" +" should be ready to compile." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:416 +msgid "Obtaining and deploying developers' transport keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:419 +msgid "" +"As a server operator you may want to grant push access to certain " +"developers." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:427 +msgid "By default the Monotone server denies all access." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:433 +msgid "To grant pull access to all clients, set the following in" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:445 +msgid "" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:451 +msgid "" +"Add the name of the user's transport key to\n" +"<code>$HOME/.monotone/write-permissions</code>, such as\n" +"<code><pre>\n" +" zzz-transport@mail.i2p\n" +" complication-transport@mail.i2p\n" +"</pre></code>\n" +"with one key per line." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:462 +msgid "" +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section <a href" +"=\"#obtaining-and-deploying-developers-keys\">Obtaining and deploying " +"developers' keys</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:472 +msgid "" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" +" Make a copy of your development database, then start the server with:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:479 +msgid "" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" +" (or by clearing the password for your transport key)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:487 +msgid "" +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:497 +msgid "" +"Debian (amongst other distributions) has integrated Monotone into their\n" +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:505 +msgid "" +"Permissions are granted by editing the files\n" +" <code>/etc/monotone/read-permissions</code> and\n" +" <code>/etc/monotone/write-permissions</code>. You'll also need to edit\n" +" <code>/etc/default/monotone</code> to enable monotone to start at boot " +"or to\n" +" customize the host, port, or database location." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:2 +msgid "New Developer's Guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:4 +msgid "" +"\n" +"So you want to start work on I2P? Great!\n" +"Here's a quick guide to getting started\n" +"on contributing to the website or the software, doing development or " +"creating translations." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:9 +#, python-format +msgid "" +"\n" +"Not quite ready for coding?\n" +"Try <a href=\"%(volunteer)s\">getting involved</a> first." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:16 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:27 +msgid "Basic study" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:17 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:41 +msgid "Getting the I2P code" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:18 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:112 +msgid "Building I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:19 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:133 +msgid "Development ideas" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:20 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:141 +msgid "Making the results available" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:21 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:162 +msgid "Get to know us!" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:22 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:168 +msgid "Translations" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:23 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:174 +msgid "Tools" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:29 +msgid "" +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at <a " +"href=\"http://www.mindview.net/Books/TIJ/\">Thinking in Java</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:33 +#, python-format +msgid "" +"Study the <a href=\"%(intro)s\">how intro</a>,\n" +"the <a href=\"%(docs)s\">other \"how\" documents</a>,\n" +"the <a href=\"%(techintro)s\">tech intro</a>,\n" +"and associated documents.\n" +"These will give you a good overview of how I2P is structured and what " +"different things it does." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:43 +msgid "" +"For development on the i2p router or the embedded applications,\n" +"get the monotone source repository installed - short instructions:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:48 +msgid "" +"Install <a href=\"http://www.monotone.ca/\">monotone</a>.\n" +"Monotone is a version control system.\n" +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:53 +msgid "" +"Skim over the <a " +"href=\"http://www.monotone.ca/docs/Tutorial.html\">monotone tutorial</a>," +" to make sure you understand the concepts." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:57 +msgid "" +"If you want to remain anonymous, you need to do an additional step, to " +"set up a connection to a monotone server over I2P:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:60 +#, python-format +msgid "" +"Enable the <a href=\"%(i2ptunnel)s\">i2ptunnel</a> client tunnel on port " +"8998 pointing to mtn.i2p2.i2p." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:64 +msgid "" +"Pick a directory where you want to put all your I2P files, and create a " +"monotone database:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:67 +msgid "" +"Define the trust list by creating <code>~/.monotone/monotonerc</code> (or" +" <code>_MTN/monotonerc</code> in the i2p.i2p workspace) with the " +"following contents:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:72 +#, python-format +msgid "" +"Copy and paste the <a href=\"%(devkeys)s\">developer's commit keys</a> " +"into a new file (e.g. <code>keys.txt</code>) in the same directory\n" +" that <code>i2p.mtn</code> is in. Import the keys into your database " +"with <br><code><pre> mtn -d i2p.mtn read < keys.txt</pre></code>" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:76 +msgid "" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:78 +msgid "Anonymously:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:81 +msgid "Non-anonymously:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:83 +msgid "" +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:90 +msgid "" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:92 +msgid "" +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:96 +msgid "Remarks" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:97 +msgid "" +"\n" +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:100 +msgid "" +"The initial pull may take several hours using the tunnel.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" +"If you are in a hurry, use the non-anonymous access." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:105 +#, python-format +msgid "" +"A full list of branches, including i2p.i2p and i2p.www can be found on <a" +" href=\"%(viewmtn)s\">viewmtn</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:108 +#, python-format +msgid "" +"A long explanation about using monotone is available on the <a " +"href=\"%(monotone)s\">monotone page</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:114 +#, python-format +msgid "" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" +"(<a href=\"%(sunjdk6)s\">Sun JDK 6</a> strongly recommended) and\n" +"<a href=\"http://ant.apache.org/\">Apache ant</a>\n" +"version 1.7.0 or higher.\n" +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:122 +msgid "" +"To build or work on console translations, you need\n" +"the xgettext, msgfmt, and msgmerge tools from the\n" +"<a href=\"http://www.gnu.org/software/gettext/\">GNU gettext package</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:128 +#, python-format +msgid "" +"For development on new applications,\n" +"see the <a href=\"%(apps)s\">application development guide</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:134 +#, python-format +msgid "" +"See <a href=\"http://%(zzz)s/forums/3\">zzz's TODO lists</a>,\n" +"<a href=\"%(todo)s\">this website's TODO list</a> or\n" +"<a href=\"http://%(trac)s/report/1\">Trac</a>\n" +"for ideas." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:143 +#, python-format +msgid "" +"See the bottom of <a href=\"%(licenses)s#commit\">the licenses page</a> " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:148 +msgid "Short version of how to generate and use keys if you plan to commit:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:150 +msgid "use an empty passphrase" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:151 +msgid "enter a passphrase" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:152 +#, python-format +msgid "" +"<a href=\"mailto:%(email)s\">send</a> this to a mtn repo operator to get " +"push privileges" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:153 +#, python-format +msgid "" +"send this to <a href=\"mailto:%(email)s\">a release manager</a> to get " +"commit privileges - not required for website" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:154 +msgid "check in with this key" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:155 +msgid "push with this key" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:157 +#, python-format +msgid "Long version: see the <a href=\"%(monotone)s\">monotone page</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:163 +#, python-format +msgid "" +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have <a href=\"%(guidelines)s\">additional guidelines for regular" +" developers</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:169 +#, python-format +msgid "" +"Website and router console translators: See the <a " +"href=\"%(newtrans)s\">New Translator's Guide</a>\n" +"for next steps." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:175 +msgid "" +"I2P is open source software that is mostly developed using open sourced\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" +"are interested in profiling the I2P codebase." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:183 +#, python-format +msgid "" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" +"<a href=\"%(java)s\">YourKit Java Profiler</a> and\n" +"<a href=\"%(dotnet)s\">YourKit .NET Profiler</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:2 +msgid "New Translator's Guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:4 +msgid "Here's a very quick guide to getting started." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:6 +msgid "How to Translate the Website" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:8 +#, python-format +msgid "" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" +"translate the website is to sign up for an account at \n" +"<a href=\"%(transifex)s\">Transifex</a> and request to join a translation" +" team. \n" +"Alternatively it can be done \"the old way\" as outlined below." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:17 +#: i2p2www/pages/site/get-involved/guides/new-translators.html:82 +msgid "Preparation" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:19 +#: i2p2www/pages/site/get-involved/guides/new-translators.html:84 +#, python-format +msgid "" +"Come to #i2p-dev on irc and talk to people.\n" +"Claim the language -\n" +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on <a href=\"%(url)s\">this wiki " +"page</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:25 +#, python-format +msgid "" +"Follow the <a href=\"%(newdevs)s\">new developer's guide</a>,\n" +"Including the installation of monotone,\n" +"checking out i2p.www branch, and generate your own monotone keys.\n" +"It is not required that you sign a dev agreement." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:33 +msgid "" +"<b>Create files:</b>\n" +"If the file for your language does not exist yet:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:38 +msgid "" +"Run \"<code>./extract-messages.sh</code>\" to generate a " +"<code>messages.pot</code> in the base directory.\n" +"Edit the header of this file, then run \"<code>./init-new-po.sh " +"locale</code>\" to generate the file\n" +"<code>i2p2www/translations/locale/LC_MESSAGES/messages.po</code>. " +"\"<code>mtn add</code>\" this file." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:43 +msgid "" +"Edit <code>i2p2www/pages/global/lang.html</code> and add a line for your " +"language (copy an existing line)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:46 +msgid "" +"Add a flag image file to <code>i2p2www/static/images/flags/</code> for " +"the menu (copy from the router)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:52 +msgid "" +"<b>Edit files:</b>\n" +"Edit <code>i2p2www/translations/locale/LC_MESSAGES/messages.po</code>.\n" +"To work with .po files efficiently, you may wish to use <a " +"href=\"http://www.poedit.net/download.php\">POEdit</a>" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:58 +#: i2p2www/pages/site/get-involved/guides/new-translators.html:151 +msgid "" +"<b>Check in:</b>\n" +"\"<code>mtn pull</code>\", \"<code>mtn update</code>\". Then check in by " +"\"<code>mtn ci -k yourname@mail.i2p file1 file2 ...</code>\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"<code>mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p</code>\".\n" +"This synchronizes your local repo with the repo on the target machine." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:65 +#: i2p2www/pages/site/get-involved/guides/new-translators.html:158 +msgid "Repeat. Check in often. Don't wait until it is perfect." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:72 +msgid "How to Translate the Router Console" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:74 +#, python-format +msgid "" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"<a href=\"%(transifex)s\">Transifex</a> and request to join a translation" +" team. \n" +"Alternatively it can be done \"the old way\" as outlined below." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:90 +#, python-format +msgid "" +"Follow the <a href=\"%(newdevs)s\">new developer's guide</a>,\n" +"including the installation of monotone and the gettext tools,\n" +"checking out i2p.i2p branch, and generate your own monotone keys." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:95 +msgid "Generate your own gpg key and sign the dev agreement." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:101 +msgid "" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" +"At least an i2p homepage in your language would be great." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:106 +msgid "" +"<b>What to translate:</b>\n" +"There are about 15 files in the i2p.i2p branch that needs translation:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:132 +msgid "" +"Where xx is your language code like fr/de/ch/zh/...\n" +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:137 +msgid "" +"<b>Create files:</b>\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file <code>foo_xx.bar</code> for your language.\n" +"Then \"<code>mtn add</code>\" the file.\n" +"After creating a .po file, edit the headers. Then run \"<code>ant " +"distclean poupdate</code>\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:144 +msgid "" +"<b>Start to work:</b>\n" +"Edit the HTML files with any text editor.\n" +"Be sure not to use an editor in HTML mode that reformats everything.\n" +"To work with .po files efficiently, you may wish to use <a " +"href=\"http://www.poedit.net/download.php\">POEdit</a>" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:163 +msgid "" +"As you can see, it's not that difficult.\n" +"If you have questions about the meaning of the terms in the console, ask " +"in <code>#i2p-dev</code> on IRC." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:169 +msgid "FAQ" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:171 +msgid "" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:175 +msgid "A: Several reasons:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:178 +#, python-format +msgid "" +"You might be interested in translating via Transifex. Request to join a " +"translation team <a href=\"%(transifex)s\">here</a>." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:182 +msgid "" +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:186 +msgid "" +"Maybe you are thinking translation is a one-step process. It isn't. You " +"can't do it all at once. You will make mistakes. You need to test it and " +"tweak it to make it look right <i>before</i> you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:190 +msgid "" +"Having translators use a source control system directly provides " +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:194 +msgid "" +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:198 +msgid "" +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:202 +msgid "" +"Installing and using monotone is not that difficult. Several of the " +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:206 +msgid "" +"Our items to translate are not \"documents\". They are html files and po " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " +"transfer." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:210 +msgid "" +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:215 +msgid "" +"<b>In summary:</b>\n" +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:220 +msgid "More Information" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:221 +#, python-format +msgid "" +"The #i2p-dev channel on IRC, or the <a " +"href=\"http://%(zzz)s/forums/14\">translation forum on %(zzz)s</a>." +msgstr "" + diff --git a/i2p2www/translations/ru_RU/LC_MESSAGES/priority.po b/i2p2www/translations/ru_RU/LC_MESSAGES/priority.po index dbe0928c2..9ee416f0e 100644 --- a/i2p2www/translations/ru_RU/LC_MESSAGES/priority.po +++ b/i2p2www/translations/ru_RU/LC_MESSAGES/priority.po @@ -6,6 +6,7 @@ # tengo <akin@rbcmail.ru>, 2013 # denixx <denixx.baykin@gmail.com>, 2013 # keedley <zhopa@mita.pp.ru>, 2013 +# sassy <sassy.but.classic@gmail.com>, 2013 # JD1 <johndoe29a@gmail.com>, 2013 # Ðрефьев Ð”ÐµÐ½Ð¸Ñ <jujjer@gmail.com>, 2013 msgid "" @@ -13,8 +14,8 @@ msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" "POT-Creation-Date: 2013-09-30 21:40+0000\n" -"PO-Revision-Date: 2013-10-02 10:22+0000\n" -"Last-Translator: denixx <denixx.baykin@gmail.com>\n" +"PO-Revision-Date: 2013-10-22 15:01+0000\n" +"Last-Translator: sassy <sassy.but.classic@gmail.com>\n" "Language-Team: Russian (Russia) " "(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " @@ -3401,7 +3402,7 @@ msgstr "" #: i2p2www/pages/site/links.html:12 msgid "I2P on the web" -msgstr "" +msgstr "I2P в Ñети" #: i2p2www/pages/site/links.html:20 msgid "Friends of I2P" diff --git a/i2p2www/translations/ru_RU/LC_MESSAGES/research.po b/i2p2www/translations/ru_RU/LC_MESSAGES/research.po new file mode 100644 index 000000000..3eedb2009 --- /dev/null +++ b/i2p2www/translations/ru_RU/LC_MESSAGES/research.po @@ -0,0 +1,141 @@ +# Russian (Russia) translations for I2P. +# Copyright (C) 2013 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# keedley <zhopa@mita.pp.ru>, 2013 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" +"POT-Creation-Date: 2013-08-30 23:32+0000\n" +"PO-Revision-Date: 2013-09-21 16:10+0000\n" +"Last-Translator: keedley <zhopa@mita.pp.ru>\n" +"Language-Team: Russian (Russia) " +"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 0.9.6\n" + +#: i2p2www/pages/site/research/index.html:2 +msgid "Academic Research" +msgstr "Ðаучные иÑÑледованиÑ" + +#: i2p2www/pages/site/research/index.html:4 +msgid "" +"Academic research and analysis of I2P is an important part of ensuring " +"that the software and network performs as expected and is safe for users " +"in hostile environments." +msgstr "" +"Ðаучное иÑÑледование и анализ I2P Ñто Ð²Ð°Ð¶Ð½Ð°Ñ Ñ‡Ð°ÑÑ‚ÑŒ процеÑÑа ÐºÐ¾Ð½Ñ‚Ñ€Ð¾Ð»Ñ " +"безопаÑноÑти програмного обеÑÐ¿ÐµÑ‡ÐµÐ½Ð¸Ñ Ð¸ Ñети в целом, в опаÑных уÑловиÑÑ… " +"Ñовременного мира." + +#: i2p2www/pages/site/research/index.html:8 +msgid "Testing Attacks on I2P" +msgstr "ТеÑтовые атаки на I2P" + +#: i2p2www/pages/site/research/index.html:10 +msgid "" +"I2P can be run as a separate test network by controlling the locations " +"that a new router reseeds from so that it only finds other test routers." +msgstr "" +"I2P можно запуÑкать как отдельную Ñеть, ÐºÐ¾Ð½Ñ‚Ñ€Ð¾Ð»Ð¸Ñ€ÑƒÑ Ñ€Ð°ÑположениÑ, откуда " +"новые маршрутизаторы получают Ñвои Ñиды, так чтобы теÑтовые " +"маршрутизаторы работали только Ñ Ñ‚ÐµÑтовыми маршрутизаторами." + +#: i2p2www/pages/site/research/index.html:14 +msgid "" +"The standard mode of operation is to have one JVM per router instance; " +"hence running multiple copies of I2P on a single machine is inadvisable, " +"both due to the potential resource drain and the certain port conflicts. " +"To better facilitate setting up small test networks, I2P has a " +"multirouter mode which enables multiple distinct routers to be run in the" +" same JVM." +msgstr "" +"Стандартный ÑпоÑоб работы Ñто иÑпользовать одну JVM на один ÑкземплÑÑ€ " +"маршрутизатора. ЗапуÑк неÑкольких копий I2P на одной машине не " +"рекомендуетÑÑ, как Ñ Ñ‚Ð¾Ñ‡ÐºÐ¸ Ð·Ñ€ÐµÐ½Ð¸Ñ Ñ€ÐµÑурÑов, так и Ñ Ñ‚Ð¾Ñ‡ÐºÐ¸ Ð·Ñ€ÐµÐ½Ð¸Ñ " +"конфликтов по портам. Ð”Ð»Ñ Ð»ÑƒÑ‡ÑˆÐµÐ³Ð¾ Ñ€Ð°Ð·Ð²ÐµÑ€Ñ‚Ñ‹Ð²Ð°Ð½Ð¸Ñ Ð½ÐµÐ±Ð¾Ð»ÑŒÑˆÐ¸Ñ… теÑтовых Ñетей," +" I2P может работать в режиме multirouter, который реализует запуÑк " +"неÑкольких маршрутизаторов в рамках одной JVM." + +#: i2p2www/pages/site/research/index.html:18 +msgid "" +"MultiRouter can be started from the i2p base directory by running the " +"below command." +msgstr "" +"MultiRouter можно запуÑтить из базовой директории I2P Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ команды " +"ниже:" + +#: i2p2www/pages/site/research/index.html:23 +msgid "" +"Additionally, I2P can be started in a virtual network mode. This mode " +"disables all transports, allowing the router to be tested in isolation " +"without network traffic. To enable this mode, add " +"<code>i2p.vmCommSystem=true</code> to the router.config before starting." +msgstr "" +"I2P можно также запуÑкать в режиме виртуальной Ñети. Ðтот режим отключает" +" вÑе транÑпорты, позволÑÑ Ñ‚ÐµÑтировать маршрутизатор без Ñетевого доÑтупа." +" Чтобы включить такой режим, добавьме <code>i2p.vmCommSystem=true</code>" +" в router.config до запуÑка" + +#: i2p2www/pages/site/research/index.html:27 +msgid "Testing the Live I2P Network" +msgstr "ТеÑтирование работающей I2P Ñети" + +#: i2p2www/pages/site/research/index.html:29 +#, python-format +msgid "" +"If you are planning on conducting research on the live I2P network, " +"please <a href=\"%(contact)s\">contact us</a> before you commence your " +"testing. While we do not discourage researchers from responsibly testing " +"their ideas on the live network, if an attack becomes apparent and we " +"don't have any line of communication then we will end up taking " +"countermeasures which could interfere with the test." +msgstr "" +"ЕÑли вы планируете произоводить иÑÑÐ»ÐµÐ´Ð¾Ð²Ð°Ð½Ð¸Ñ Ð½Ð° живой I2P Ñети, " +"пожалуйÑта, <a href=\"%(contact)s\">ÑвÑжитеÑÑŒ Ñ Ð½Ð°Ð¼Ð¸</a> заранее. Ð¥Ð¾Ñ‚Ñ Ð¼Ñ‹" +" не против ответÑтвенных иÑÑледователей, которые проверÑÑŽÑ‚ Ñвои идеи на " +"живой Ñети, еÑли мы заметим вмешательÑтво и у Ð½Ð°Ñ Ð½Ðµ будет ÑпоÑоба " +"ÑвÑзатьÑÑ, иÑÑледование может быть иÑпорчено применÑемыми нами " +"контр-мерами." + +#: i2p2www/pages/site/research/index.html:33 +msgid "Prior Research" +msgstr "СущеÑтвующие иÑÑледованиÑ" + +#: i2p2www/pages/site/research/index.html:35 +#, python-format +msgid "" +"A list of known published papers about I2P is available <a " +"href=\"%(papers)s\">here</a>." +msgstr "" +"СпиÑок извеÑтных публикаций про I2P доÑтупен <a href=\"%(papers)s\">вот " +"тут</a>." + +#: i2p2www/pages/site/research/papers.html:2 +#: i2p2www/pages/site/research/papers.html:4 +msgid "Papers on I2P" +msgstr "Публикации про I2P" + +#: i2p2www/pages/site/research/papers.html:6 +msgid "Following are links to research papers about I2P." +msgstr "СпиÑок ÑÑылок на иÑÑÐ»ÐµÐ´Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¿Ð¾ теме I2P" + +#: i2p2www/pages/site/research/papers.html:8 +#, python-format +msgid "To request an addition to this page, please send to %(email)s." +msgstr "Чтобы добавить что-то на Ñту Ñтраницу, пишите на %(email)s." + +#: i2p2www/pages/site/research/papers.html:12 +msgid "Newest links are at the top of the page." +msgstr "Ðовые ÑÑылки вверху Ñтраницы." + +#: i2p2www/pages/site/research/papers.html:17 +msgid "Papers and Research" +msgstr "Публикации и иÑÑледованиÑ" + diff --git a/i2p2www/translations/zh_CN/LC_MESSAGES/priority.po b/i2p2www/translations/zh_CN/LC_MESSAGES/priority.po index 506f83d88..ca2a80e99 100644 --- a/i2p2www/translations/zh_CN/LC_MESSAGES/priority.po +++ b/i2p2www/translations/zh_CN/LC_MESSAGES/priority.po @@ -3,6 +3,7 @@ # This file is distributed under the same license as the I2P project. # # Translators: +# kwh <14alpaca@gmail.com>, 2013 # walking <waling@mail.i2p>, 2013 # xtoaster <zhazhenzhong@gmail.com>, 2013 msgid "" @@ -10,8 +11,8 @@ msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" "POT-Creation-Date: 2013-09-30 21:40+0000\n" -"PO-Revision-Date: 2013-09-30 21:44+0000\n" -"Last-Translator: str4d <str4d@i2pmail.org>\n" +"PO-Revision-Date: 2013-10-20 01:03+0000\n" +"Last-Translator: kwh <14alpaca@gmail.com>\n" "Language-Team: Chinese (China) " "(http://www.transifex.com/projects/p/I2P/language/zh_CN/)\n" "Plural-Forms: nplurals=1; plural=0\n" @@ -937,7 +938,7 @@ msgstr "支æŒçš„应用" #: i2p2www/pages/global/nav.html:35 msgid "Bittorrent" -msgstr "" +msgstr "Bittorrent" #: i2p2www/pages/global/nav.html:38 msgid "API" @@ -1534,7 +1535,7 @@ msgstr "" #: i2p2www/pages/site/faq.html:71 msgid "Discuss with the developers on IRC in #i2p-dev" -msgstr "" +msgstr "与开å‘者们在IRC频é“#i2p-dev上讨论" #: i2p2www/pages/site/faq.html:75 msgid "Please include relevant information from the router logs and wrapper logs." @@ -2582,7 +2583,7 @@ msgid "" "I2P is used by many people who care about their privacy: activists, " "oppressed people, journalists and whistleblowers, as well as the average " "person.\n" -msgstr "" +msgstr "I2P被很多关注自己éšç§çš„人使用，例如活动家，被压迫的人民，记者，爆料者和一般人。\n" #: i2p2www/pages/site/index.html:21 msgid "" @@ -2590,13 +2591,13 @@ msgid "" "to make attacks more and more difficult to mount. Its anonymity will get " "stronger as the size of the network increases and with ongoing academic " "review.\n" -msgstr "" +msgstr "没有网络å¯ä»¥åšåˆ°å®Œç¾ŽåŒ¿å，I2Pçš„ç›®æ ‡æ˜¯è®©æ”»å‡»å˜å¾—更困难，让匿å性更强以åŠè®©åŒ¿å网络更大，并且æŒç»è¿›è¡Œè¯„测。\n" #: i2p2www/pages/site/index.html:24 msgid "" "I2P is available on desktops, embedded systems (like the Raspberry Pi) " "and Android phones. Help spread the word!\n" -msgstr "" +msgstr "I2P在计算机，嵌入å¼ç³»ç»Ÿ(æ¯”å¦‚æ ‘èŽ“æ´¾)和安å“手机上å¯ç”¨ã€‚å¸®åŠ©æˆ‘ä»¬ä¼ æ’。\n" #: i2p2www/pages/site/index.html:28 msgid "Read more…" -- GitLab