forked from I2P_Developers/i2p.www
Updated translation strings
This commit is contained in:
str4d
184
pots/blog.pot
184
pots/blog.pot
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: I2P website\n"
|
||||
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
|
||||
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
|
||||
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -5645,6 +5645,7 @@ msgstr ""
|
||||
|
||||
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
|
||||
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
|
||||
msgid ""
|
||||
"Take part in Summer Dev!\n"
|
||||
"========================"
|
||||
@@ -5680,6 +5681,7 @@ msgstr ""
|
||||
|
||||
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
|
||||
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
|
||||
msgid ""
|
||||
"We'll be posting here as we go, but you can also follow our progress, and"
|
||||
" share\n"
|
||||
@@ -6678,3 +6680,183 @@ msgstr ""
|
||||
msgid "Add bash completion scripts to Debian packages"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
|
||||
msgid ""
|
||||
"================================\n"
|
||||
"I2P Summer Dev 2017: MOAR Speed!\n"
|
||||
"================================"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
|
||||
msgid ""
|
||||
"This year's Summer Dev will be focused on metrics collection and "
|
||||
"performance improvements for the network."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
|
||||
msgid ""
|
||||
"It's that time of year again! We're embarking on our summer development\n"
|
||||
"programme, where we focus on a particular aspect of I2P to push it "
|
||||
"forward. For\n"
|
||||
"the next three months, we'll be encouraging both new contributors and "
|
||||
"existing\n"
|
||||
"community members to pick a task and have fun with it!"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
|
||||
msgid ""
|
||||
"`Last year`_, we focused on helping users and developers leverage I2P, by"
|
||||
"\n"
|
||||
"improving API tooling and giving some love to applications that run over "
|
||||
"I2P.\n"
|
||||
"This year, we want to improve the user experience by working on an aspect"
|
||||
" that\n"
|
||||
"affects everyone: performance."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
|
||||
msgid "`Last year`"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
|
||||
msgid ""
|
||||
"Despite onion-routing networks often being called \"low-latency\" "
|
||||
"networks, there\n"
|
||||
"is significant overhead created by routing traffic through additional "
|
||||
"computers.\n"
|
||||
"I2P's unidirectional tunnel design means that by default, a round trip "
|
||||
"between\n"
|
||||
"two Destinations will involve twelve participants! Improving the "
|
||||
"performance of\n"
|
||||
"these participants will help to both reduce the latency of end-to-end\n"
|
||||
"connections [1]_, and increase the quality of tunnels network-wide."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
|
||||
msgid ""
|
||||
"MOAR speed!\n"
|
||||
"==========="
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
|
||||
msgid "Our development programme this year will have four components:"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
|
||||
msgid ""
|
||||
"Measure\n"
|
||||
"-------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
|
||||
msgid ""
|
||||
"We can't tell if we improve performance without a baseline! We'll be "
|
||||
"creating a\n"
|
||||
"metrics system for collecting usage and performance data about I2P in a\n"
|
||||
"privacy-preserving way, as well as porting various benchmarking tools to "
|
||||
"run\n"
|
||||
"over I2P (e.g. iperf3_)."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
|
||||
msgid ""
|
||||
"Optimise\n"
|
||||
"--------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
|
||||
msgid ""
|
||||
"There's a lot of scope for improving the performance of our existing "
|
||||
"code, to\n"
|
||||
"e.g. reduce the overhead of participating in tunnels. We will be looking "
|
||||
"at\n"
|
||||
"potential improvements to:"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
|
||||
msgid "Cryptographic primitives"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
|
||||
msgid ""
|
||||
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
|
||||
"(Streaming_)"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
|
||||
msgid "Peer profiling"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
|
||||
msgid "Tunnel path selection"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
|
||||
msgid ""
|
||||
"Advance\n"
|
||||
"-------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
|
||||
msgid ""
|
||||
"We have several open proposals for improving the scalability of the I2P "
|
||||
"network\n"
|
||||
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
|
||||
"will be\n"
|
||||
"working on these proposals, and begin implementing the finalised ones in "
|
||||
"the\n"
|
||||
"various network routers. The more feedback these proposals receive, the "
|
||||
"sooner\n"
|
||||
"we can roll them out, and the sooner I2P services can start using them!"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
|
||||
msgid ""
|
||||
"Research\n"
|
||||
"--------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
|
||||
msgid ""
|
||||
"I2P is a packet-switched network, like the internet it runs on top of. "
|
||||
"This\n"
|
||||
"gives us significant flexibility in how we route packets, both for "
|
||||
"performance\n"
|
||||
"and privacy. The majority of this flexibility is unexplored! We want to\n"
|
||||
"encourage research into how various clearnet techniques for improving "
|
||||
"bandwidth\n"
|
||||
"can be applied to I2P, and how they might affect the privacy of network\n"
|
||||
"participants."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
|
||||
msgid ""
|
||||
"We have many more ideas for things we'd like to get done in these areas. "
|
||||
"If\n"
|
||||
"you're interested in hacking on privacy and anonymity software, designing"
|
||||
"\n"
|
||||
"protocols (cryptographic or otherwise), or researching future ideas - "
|
||||
"come and\n"
|
||||
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
|
||||
"into\n"
|
||||
"our community, both inside and outside the I2P network. We'll also be "
|
||||
"sending\n"
|
||||
"I2P stickers out to all new contributors taking part! If you want to chat"
|
||||
" about\n"
|
||||
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
|
||||
" can\n"
|
||||
"also find us in #i2p-dev on OFTC or Freenode."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
|
||||
msgid ""
|
||||
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
|
||||
" attacks, so it would be reasonable to ask whether improved performance "
|
||||
"equates to reduced privacy. Some latency can help privacy if applied "
|
||||
"correctly via random delays or batching (neither of which are currently "
|
||||
"employed by any general-purpose onion-routing network). However, if a "
|
||||
"tunnel has uniform overall latency, then traffic confirmation attacks "
|
||||
"should be just as viable with or without that latency; thus there should "
|
||||
"be little statistical difference when the latency is reduced uniformly."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: I2P website\n"
|
||||
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
|
||||
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
|
||||
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -341,26 +341,26 @@ msgstr ""
|
||||
msgid "April 2017"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:300
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:296
|
||||
#, 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:303
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:299
|
||||
msgid "Full restricted routes"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:304
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:300
|
||||
msgid "Tunnel mixing and padding"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:305
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:301
|
||||
msgid "User defined message delays"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:313
|
||||
#: i2p2www/pages/site/get-involved/roadmap.html:309
|
||||
#, python-format
|
||||
msgid ""
|
||||
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "
|
||||
|
||||
Reference in New Issue
Block a user