Closed GoogleCodeExporter closed 9 years ago
i think this is a problem on receiving phones. all my phones display the german
characters correctly.
maybe not all phones support utf8. how does the characters look like? are they
displayed as 2 chars?
Original comment by felix.bechstein
on 1 Dec 2009 at 7:04
Original comment by felix.bechstein
on 1 Dec 2009 at 7:05
hello felix. Sorry for my late response.
For ü,ß the character is an double "?" and on my brothers phone it is a
placeholder.
Iam using a htc magic with the lastest cyanogenmod 4.2.11.1.
Regards
Original comment by camilosc...@gmail.com
on 31 Dec 2009 at 12:15
hmmm.. it seems there are more than me that have that problem. If you look on
your
market rating.
Original comment by camilosc...@gmail.com
on 31 Dec 2009 at 3:21
sending sms via gmx+g1+cm results in getting öäüß transmitted as they
should. but €
failed.
sms received on same device and a nokia phone.
think the problem is utf8 vs. iso8859-15 on some old phones.
Original comment by felix.bechstein
on 4 Jan 2010 at 7:10
please try this apk.
i set encoding to iso8859-15
the €-sign isn't shown correctly on any connector i tested.
but it's possible now to send sms with € via o2 (which was not possible
before)
please tell me what connectors are used. and what are the results with these
connectors.
Original comment by felix.bechstein
on 5 Jan 2010 at 5:54
Attachments:
hey felix! Iam using the gmx and innosend connector and tried it with innosend.
sadly
it was not succesfull. with your file i get also these "?".
Original comment by camilosc...@gmail.com
on 5 Jan 2010 at 6:50
tried the newest cm version allready?
Original comment by felix.bechstein
on 7 Jan 2010 at 7:51
jep. it is fixed. the problem was the cynogen rom. Thank you!
Original comment by camilosc...@gmail.com
on 7 Jan 2010 at 9:56
Original comment by felix.bechstein
on 8 Jan 2010 at 6:59
reopen ? because with the last update 2.8.3 its seems as its a really bug.
regards
Original comment by camilosc...@gmail.com
on 10 Jan 2010 at 11:27
fixed again, this was just an issue while switching from http get to post.
Original comment by felix.bechstein
on 10 Jan 2010 at 2:02
Original issue reported on code.google.com by
camilosc...@gmail.com
on 30 Nov 2009 at 11:27