save chars improvement

[GoogleCodeExporter]

Save chart button clears diacritics in the 
first step, and the 2nd push trims spaces.

This would be very handy as diacritics 
consumes a lot of extra bits and some 
providers (fishtext ie) does not support it.

Original issue reported on code.google.com by tomas.j...@gmail.com on 26 May 2010 at 10:55

[GoogleCodeExporter]

what are diacritics? :x

Original comment by felix.bechstein on 27 May 2010 at 4:44

• Added labels: Component-Logic, Priority-Low, Product-WebSMS, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Diacritics are special characters (like accent marks), for example 
ěščřžýáíéúů etc.
To remove diacritics means to convert ě->e, ú->u, ů->u, etc.

Normal SMS length is 160 chars. If you use a single char with diacritical mark 
in 
SMS, then the length of the SMS is limited just to 70 chars (the code table 
with 
special chars is bigger so it needs more bits to define a character). 
So you can save much more space by removing diacritics than trimming spaces.

http://en.wikipedia.org/wiki/Diacritics - I am talking just about latin 
alphabet ;-)

Original comment by tomas.j...@gmail.com on 27 May 2010 at 7:34

[GoogleCodeExporter]

thx for information

Original comment by felix.bechstein on 27 May 2010 at 6:06

• Changed state: Accepted

[GoogleCodeExporter]

i decided to decline this request,
feel free to do it your self.
I'll be happy to merge a patch.

Original comment by f...@ub0r.de on 17 Jun 2012 at 2:58

• Changed state: WontFix

[GoogleCodeExporter]

Hi Felix,
Pleeeeaseeee, could you perhaps reconsider? I would be happy to make a donation 
of €10 based on this. I am pretty sure there would be significant interest in 
my home country (poland), just recently came across the thread about this which 
was 150 pages long. I would be happy to actually advertise your app on all 
android forums in poland, too and especially on all threads where i see this 
issue. I know probably doesn't start to cover the effort, but still hope it 
shows that this is needed. the problem here is not only what tomas described 
above, but mainly the fact the message arriving to old-style phone is 
unreadable full of &^*&^"£%$ letters etc. many of us have a need to text older 
family members who are not necessarily as quick with technology as we are, 
their phone standard is say "nokia 3210", so texting them is likely to come 
like this if modern phone is used and sms is composed using any of 
builtin/swype/swiftkey keyboards etc. keyboard makers don't want to solve this 
as they consider it to be smsapp improvement...
there are actually a few sms apps that do this already:
- samsung messaging app has a function called input->GSM alphabet which 
converts diacritics entered in sms before sending, ie. message is seen as 
containing diacritics but they get replaced before sending to destination
- go sms pro has a similar function, works same as in samsung app.
why don't i want to use the other apps? well they don't have plugins support 
that your app has, i would specifically like to take advantage of web sms 
gateways which the other apps don't support.
any help i can give, let me know. unfortunately i can't code it myself...

Rgds,
Bogdan

Original comment by lipski.b...@gmail.com on 21 Aug 2013 at 8:14

[GoogleCodeExporter]

btw. sorry if misread the enh request, just read it again. I hope the OP meant 
for websms to handle diacritics in the way samsung/gosmspro do, if it was sth 
else, I would be happy to open it as new enh. Rgds,B.

Original comment by lipski.b...@gmail.com on 21 Aug 2013 at 8:17

[GoogleCodeExporter]

ok, i found a simple solution for android 2.3+

please verify

Original comment by f...@ub0r.de on 23 Aug 2013 at 3:50

• Changed state: ShouldBeFixed

Attachments:

• WebSMS-release.apk

[GoogleCodeExporter]

Original comment by f...@ub0r.de on 16 Oct 2013 at 5:46

• Changed state: Fixed