SMS message reader should use localized text-parts to produce final text

[GoogleCodeExporter]

The text reader currently has the poarts that are used to form the final 
message between phone number and message text hard-coded to english.

This leads to funny output on German phones, where the TTS language defaults to 
German (of course...). Ideally, the app would request the Locale's language 
from the TTS service and use the strings.xml that matches the language of the 
TTS service. This is reuqired as its possible to even set another default 
language for the TTS service that is different from the default language (if 
this is impossible, as a minimum, the text should be localized to default 
locale, so the default strings.xml as used for the GUI language).

Original issue reported on code.google.com by uwe.h.schindler on 15 Aug 2011 at 6:59

[GoogleCodeExporter]

Original comment by JimR...@gmail.com on 15 Aug 2011 at 10:43

• Changed state: Accepted
• Added labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

Can you send me the new strings.xml entries here before your release a new 
version, so I can translate all of them (including the new SMS related still 
missing)? I will post corrections asap.

Original comment by uwe.h.schindler on 15 Aug 2011 at 11:07

[GoogleCodeExporter]

Uwe: Sure.  I should have done that before 2.2.3 release but there were some 
bad bugs in 2.1.0 and 2.2.2 so I pushed that out rather quickly.  I will fix 
this issue and send the strings file.  When I get the strings file back I will 
post the next release for testing and then to market.

Original comment by JimR...@gmail.com on 15 Aug 2011 at 11:23

[GoogleCodeExporter]

Fixed in 2.2.4

Original comment by JimR...@gmail.com on 16 Aug 2011 at 12:19

• Changed state: Fixed