Update LangTask

Hello Nicholas,

buildlang.php contains hardcoded data for e.g. the manifest, which doesn't allow me to use it. I've converted it to a Phing task: LangTask. I don't think you were using the old LangTask, so I've overwritten it with the new one.

Now it runs under Phing we've got more control about it. Therefore I edited the version to use the SHA of the
GIT commit. If you commit the pulled translations before building the languages then this works fine.

Another modification is that I used "Download for Joomla! $minJversion+" in stead of "Download for Joomla! 1.6/1.7/2.5/3.x" for a KISS approach. We could make it variable if you like.

Using the new LangTask is quite simple:
1. Add this to the Phing build file:
<pre>&lt;taskdef name="langdeploy" classname="phingext.LangTask" /&gt;

&lt;target name="lang-deploy" description="Generate and upload language files" depends="setup-properties"&gt;
	&lt;langdeploy version="${ext.version}" /&gt;
&lt;/target&gt;</pre>2. Add the variables to your build.properties. For example:
<pre>langbuilder.author			= Twentronix.com
langbuilder.authorurl		= https://www.twentronix.com
langbuilder.license 		= http://www.gnu.org/licenses/gpl-3.0.html GNU/GPL
langbuilder.minjversion		= 2.5
langbuilder.packagename 	= cookieconfirm
langbuilder.hosturl			= http://cdn.twentronix.com
langbuilder.software 		= Cookie Confirm
langbuilder.timezone		= Europe/Amsterdam</pre>3. Create a hardlink for LangTask.php

When you've migrated all your repositories, you can delete the /buildlang folder
I'm curious about your opinion.

Cheers,
Jurian