ploosqva
18th March 2009, 01:34 PM
As everyone who tried using T9 and non-ascii characters you probably are aware of the, let's call it, *Question mark glitch*.
For anyone not familliar with this, the problem is that when ha the "Use Unicode when necessary" box unchecked and inserts a non-ascii character in a SMS message, the recipient receives question marks.
There seems to be no built in solution. Checking the box implies avoiding Unicode, which is painful when using T9 in some languages.
OK, now let me explain why I'm posting in this forum.
I'm doing a research on available options to create some simple app, which can help with the above. The ideas are:
1. A background application/service, which would intercept outgoing SMS messages and strip any Unicode characters
This was my first idea. Unfortunately I've had hard time finding a viable solution. As long as sending and intercepting incoming messages is easy, control over outgoing SMS doesn't look too good. The CEMAPI is a pain but I may be missing somethig.
2. Another idea is to remap the Send softkey to own logic, which would strip Unicode.
This seems an eay, higher-level approach to the first idea. If anyone would find this a good idea, do point in the right direction. Specifically in remapping the softkey (all I was able to find was rempping Today screen softkeys).
3. One last idea is simply to create a replacement SMS messaging app.
Many of those exist but I'd very much like them it to nicely integrate with WinMo and TF3D. Is that any doable?
For anyone not familliar with this, the problem is that when ha the "Use Unicode when necessary" box unchecked and inserts a non-ascii character in a SMS message, the recipient receives question marks.
There seems to be no built in solution. Checking the box implies avoiding Unicode, which is painful when using T9 in some languages.
OK, now let me explain why I'm posting in this forum.
I'm doing a research on available options to create some simple app, which can help with the above. The ideas are:
1. A background application/service, which would intercept outgoing SMS messages and strip any Unicode characters
This was my first idea. Unfortunately I've had hard time finding a viable solution. As long as sending and intercepting incoming messages is easy, control over outgoing SMS doesn't look too good. The CEMAPI is a pain but I may be missing somethig.
2. Another idea is to remap the Send softkey to own logic, which would strip Unicode.
This seems an eay, higher-level approach to the first idea. If anyone would find this a good idea, do point in the right direction. Specifically in remapping the softkey (all I was able to find was rempping Today screen softkeys).
3. One last idea is simply to create a replacement SMS messaging app.
Many of those exist but I'd very much like them it to nicely integrate with WinMo and TF3D. Is that any doable?