Pulled out URLs from about/intro as translation vars

i2p2www/pages/site/about/intro.html

@@ -2,16 +2,17 @@
 {% block title %}{{ _('Intro') }}{% endblock %}
 {% block content %}
 <h1>{{ _('The Invisible Internet Project') }} (I2P)</h1>      
-<p>{% trans -%}
+<p>{% trans ip='http://en.wikipedia.org/wiki/Internet_Protocol',
+tcp='http://en.wikipedia.org/wiki/Transmission_Control_Protocol',
+pke='http://en.wikipedia.org/wiki/Public_key_encryption' -%}
 I2P is an anonymous network, exposing a simple layer that applications can 
 use to anonymously and securely send messages to each other. The network itself is 
-strictly message based (a la 
-<a href="http://en.wikipedia.org/wiki/Internet_Protocol">IP</a>), but there is a 
+strictly message based (a la <a href="{{ ip }}">IP</a>), but there is a 
 library available to allow reliable streaming communication on top of it (a la 
-<a href="http://en.wikipedia.org/wiki/Transmission_Control_Protocol">TCP</a>).  
+<a href="{{ tcp }}">TCP</a>).  
 All communication is end to end encrypted (in total there are four layers of 
 encryption used when sending a message), and even the end points ("destinations") 
-are cryptographic identifiers (essentially a pair of <a href="http://en.wikipedia.org/wiki/Public_key_encryption">public keys</a>).
+are cryptographic identifiers (essentially a pair of <a href="{{ pke }}">public keys</a>).
 {%- endtrans %}</p>
 
 <h2>{{ _('How does it work?') }}</h2>
@@ -30,12 +31,14 @@ message is the absolute minimum necessary to meet both the sender's and the
 receiver's threat model.
 {%- endtrans %}</p>
 
-<p>{% trans netdb=site_url('docs/how/network-database') -%}
+<p>{% trans netdb=site_url('docs/how/network-database'),
+dht='http://en.wikipedia.org/wiki/Distributed_hash_table',
+kad='http://en.wikipedia.org/wiki/Kademlia' -%}
 The first time a client wants to contact another client, they make a query 
 against the fully distributed "<a href="{{ netdb }}">network 
-database</a>" - a custom structured <a href="http://en.wikipedia.org/wiki/Distributed_hash_table">
+database</a>" - a custom structured <a href="{{ dht }}">
 distributed hash table (DHT)</a> based off the 
-<a href="http://en.wikipedia.org/wiki/Kademlia"> Kademlia algorithm</a>. This is done 
+<a href="{{ kad }}">Kademlia algorithm</a>. This is done 
 to find the other client's inbound tunnels efficiently, but subsequent messages 
 between them usually includes that data so no further network database lookups 
 are required.
@@ -57,7 +60,10 @@ into the I2P network as well as to receive streams out of the network and
 forward them towards a specific TCP/IP address.
 {%- endtrans %}</p>
 
-<p>{% trans -%}
+<p>{% trans bittorrent='http://www.bittorrent.com/',
+freenet='https://freenetproject.org/',
+mnet='http://www.livejournal.com/',
+livejournal='http://www.livejournal.com/' -%}
 I2PTunnel is currently used to let people run their own anonymous website 
 ("eepsite") by running a normal webserver and pointing an I2PTunnel 'server' 
 at it, which people can access anonymously over I2P with a normal web browser 
@@ -66,21 +72,21 @@ technique to run an anonymous IRC network (where the IRC server is hosted
 anonymously, and standard IRC clients use an I2PTunnel to contact it).  There 
 are other application development efforts going on as well, such as one to 
 build an optimized swarming file transfer application (a la 
-<a href="http://www.bittorrent.com/">BitTorrent</a>), a 
-distributed data store (a la <a href="https://freenetproject.org/">Freenet</a> / 
-<a href="http://mnetproject.org/">MNet</a>), and a blogging system (a fully 
-distributed <a href="http://www.livejournal.com/">LiveJournal</a>), but those are 
+<a href="{{ bittorrent }}">BitTorrent</a>), a 
+distributed data store (a la <a href="{{ freenet }}">Freenet</a> / 
+<a href="{{ mnet }}">MNet</a>), and a blogging system (a fully 
+distributed <a href="{{ livejournal }}">LiveJournal</a>), but those are 
 not ready for use yet.
 {%- endtrans %}</p>
 
-<p>{% trans -%}
+<p>{% trans squid='http://www.squid-cache.org/' -%}
 I2P is not inherently an "outproxy" network - the client you send a message 
 to is the cryptographic identifier, not some IP address, so the message must 
 be addressed to someone running I2P.  However, it is possible for that client
 to be an outproxy, allowing you to anonymously make use of their Internet 
 connection.  To demonstrate this, the "eepproxy" will accept normal non-I2P 
 URLs (e.g. "http://www.i2p.net") and forward them to a specific destination
-that runs a <a href="http://www.squid-cache.org/">squid</a> HTTP proxy, allowing 
+that runs a <a href="{{ squid }}">squid</a> HTTP proxy, allowing 
 simple anonymous browsing of the normal web.  Simple outproxies like that are 
 not viable in the long run for several reasons (including the cost of running 
 one as well as the anonymity and security issues they introduce), but in