- Add a python script (generate-android-i18n-strings.py)
that generates the translated android strings.xml as per:
https://developer.android.com/guide/topics/resources/providing-resources#AlternativeResources
It considers the dists/android/res/values/strings.xml file as
a base template to generate those translated strings.xml files.
- The python script also generates a fake cpp with strings from
dists/android/res/values/strings.xml. These strings will be picked
up by gettext to make it translatable. If there is any change in the
original strings.xml file, we won't have to worry about the changes
in cpp file.
- Add documentation for the generate-android-i18n-strings.py script
Different platforms have different levels of support of encodings and
often have slight variations. We already have tables for most encoding
with only CJK missing. Full transcoding inclusion allows us to get reliable
encoding results independently of platform. The biggest con is the need for
external tables encoding.dat.
It removes a duplicate table for korean in graphics/korfont.cpp
MSVC8 gives various compile error relating to templates that were changed
back in 2008, leading me to belive that no one is using it, and that there
is not point adding work arounds for a 9 year old compiler no one uses.
