Javascript version.
Stabilized js+added some extra i/o formats on both

Explanation:
============

New output formats for geographic coordinates:
----------------------------------------------

	Originally, utm2geo() returns coordinates in sexagesimal (non
absolute) format and utm2geo_abs() the absolute version whith 'N' or 'S'
extra vector.

	Now, there is intermediate utm2geo_dec() which returns data in
decimal format (just like google uses) BEFORE converting it to its
sexagesimal components.

	Also, utm2geo() has been renamed to utm2geo_sex() for coherence, but
there is also utm2geo() failback method that simply call utm2geo_sex for
backward compatiblility.

	Next, geo2utm() has been modified to automatically accept decimal
degrees and alternative syntax with single parameter consisting in an
array with all parameters in the same order. This way, the output of
utm2geo() can be directly feeded to geo2utm().

	Same thing now happen also with utm2geo_dec() and derivates
(utm2geo_sex(), utm2geo_abs() and backward-compatibility function
utm2geo() which underlays to utm2geo_dec()): All can receive all its
parameters in a single "packed" array. That means that the result of
geo2utm() can be feeded to any of utm2geo*() flavours to get back the
originally feeded coordinates with only a small precission mistake
(reasonably tested).

Javascript version:
-------------------

	Reasonably tested fixing initial php to js translation bugs.

	Fully synced with php version (including new methods which actually
was originally implemented in its js version.

	Tested with Node.js and Firefox 25.0