The Android 4.x+ code has changed a lot since the initial import
of the eyes-free codebase. A lot of bug fixes and improvements
have been made to it.

The eyes-free codebase had two different code paths:
  *  one for ICS (4.0) or later, using the Java-based TTS APIs
     provided by the Android platform;
  *  one for pre-ICS using an internal C++-based TTS API.

Thus, any bug fixes or improvements would have to be done to both
code bases if Android 2.x/3.x support is required. This is not
maintainable.

If pre-ICS support is to be re-added in the future, the plan will
be to:
  *  forward the C++-based APIs to the Java-based APIs via a
     compatibility layer;
  *  use a compatibility layer (Android Support Library?) for using
     the ICS settings API on pre-ICS.

The original variant list UI resulted in a long, complex list that
was difficult to navigate. This change splits up that list into
more manageable groups.

Conflicts:
	README.md

The i phoneme is used for the reduced i sound in e.g. happy
(/h'api/). Thus, the following words contrast:

    word   eSpeak   IPA
    happy  /h'api/  /hˈapi/
    been   /b'i:n/  /bˈiːn/
    bin    /b'In/   /bˈɪn/

Before this change, /h'api/ would be transcribed in IPA as /hˈapɪ/
which is wrong. After this change, it is transcribed correctly.

When running any of the following:

    espeak -x "[[]]"
    espeak --ipa "[[]]"

eSpeak would SEGFAULT. This is because phon_out_buf is NULL as no
phonemes have been written and as this is the first call to
GetTranslatedPhonemeString, the phoneme buffer has not been
allocated yet. However, GetTranslatedPhonemeString attempts to add
a NULL character to the end of the phoneme buffer, and thus crashes.

Android does not support UN M.49 territory codes. Instead:
  *  4.2 and earlier return an empty string;
  *  4.3 throws a MissingResourceException.