I Have the same problem.

The ñ char works fine, but the chars like (á, é, í, ó, ú) produces the SMS lenght
down to 60 characters.

I have been testing the problem.

When chars like á, é, í, ó, ú are used (ant other strange chars like º or ·), the
lenght of the SMS is shorted to 60 characters. If you do not exceed the 60 chars
limit, it is sent correctly. However, if you write more than 60 characters and use
several SMS fragments, the SMS is sent in a wrong way and only the first fragment is
received right. 

It seems to be a problem managing long sms (more than 1 fragment) with accented chars.

I think that the problems come by the encoding that the spanish telephone operators
uses to encode the SMS. It's possible that Android use UTF-8 (Unicode) and the
spanish operators need ISO-8859-1 or ISO-8859-15...

Searching i found that the standar codification for the SMS uses 7 bits. In this
alphabet it's included Ñ and the ñ but not the accents. So when we write an accent,
the telephone should change to UTF-8 or UTF-16 and the length of the SMS is reduced.

There's something more related on this somehow... Virtual Keyboard doesn't include 
grave-accented vowels (à, è, etc.) when Locale is set to Spanish, so I assume this 
should also be considered

I do not know the GSM alphabet encoding precisely but i do know that on all the other 
phones i had letters such as à é ç or ù at least where encoded with no problem in GSM 
alphabet : for exemple i used to be able to send a 160 char SMS containing the 
mentioned letter within one SMS only which i think means it was not UTF-8 or UTF-16 
encoded

I have the exact same problem running Cyanogen's build in Australia… only happens to a few random 
contacts though.

Please fix this!

I have the same issue: when SMS windows shows .../3 there is a good chance message
will be corrupted and chinese characters will be received by receiver. 

As long as SMS windows shows /1 or /2 (split over 1-2 SMS), message should not be
corrupted.

As soon as character like "ê" is inserted (e.g. french word grêle), I think Android
switches to another coding scheme that takes more space. Then SMS is split over
several SMS messages. Bug appears mostly when split over 3 SMS according to my tests.

Same problem with French language, HTC Magic, build CRC1.
It's quite annoying, because you don't know whether the message made it alright,
except if your receiver tells you.....
Also, i've been using ChompSMS lately (another sms app), and it seems like the
problem doesn't happen there (can someone confirm this?), so that would make it an
app problem, not an OS problem.

Thanks!

Hi, I have the same problem.... But unfortunately even with ChompSMS the problem is
the same.

Rgds,

Same problem here : after inserting a character like 'ê' the sms split after 64
characters instead of 145 and everything after the 65th character is not readable
(squares instead of common chars)

My provider is SFR in France.

I have the same problem with Polish characters. 

Same problem with HTC Hero in France ( Provider : SFR France )

Same problem with HTC Hero and SFR in France

Anyone knows if there's a workaround using a third-party SMS application?

Thanks

I use chompsms and handcentSMS they are able to correctly handle unicode characters
in SMS (I try on HTC Magic SFR).

Same issue here.

HTC Magic (Vodafone)
firmware 1.5
kernel: 2.6.27-00393-g6607056

Steps to reproduce:
- Write a long SMS that gets converted to MMS. If you erase some characters to go 
back to SMS 
lenght boundaries the resulting text to the receiver is a mix of symbols.
Copy-Pasting the sent text (with the right lenght) gives an identical result.
If the receiver sends that corrupted sms back, on the android device those symbols 
appears like 
KANJI.

Other ways to have the same problem: using special characters like capital grave 
chars and 
others or using emotes from the UI menu.

Exactly the same on HTC Hero (Poland)!

Is this a duplicate of  issue 2719  or a separate issue?

If it's a separate issue, please provide:
-the network on which the SMS originates
-the network on which the SMS is received
-the exact phone model that has problems receiving those messages

Yes, seems to be a duplicate of 2719.

N.B. seems to have been fixed by my network operator (Sunrise). I was using an HTC Magic.

network origin: Sunrise, Switzerland
network received: Swisscom, Switzerland

Messages that were failing before are now working and I cannot reproduce the issue
with an HTC Magic or HTC Hero.

And I tried by using embedded SMS/MMS application or chompSMS and issue doesn't show
up anymore. I copied )copy & paste) the exact same  messages as before. 

Seems like the operator changed a configuration somewhere! Can someone help
understand what the operator could have changed?

I agree, i think this is a duplicate of 2719
In 2719, in comments 25, 26 and 27, i explained one possible reason : it was about 
multi-part sms containing non-GSMAlphabet chars : the parts containing only 
GSMAlphabet will get a GSMAlphabet encoding tag in their header while the one 
containing non-GSMAlphabet chars will get a UTF16 encoding tag in heir header and 
this is not correct according to the GSM standards and most phone will decode all the 
parts using the encoding tag found in the header of the first SMS hence if the first 
tag was UTF16 then when decoding a message which is in fact GSMAlphabet then you end 
up with kanji and if the first tag was GSMAlpahbet, when you reach a UTF16 part, you 
end up with sqaures.

I think that the  issue 2719  is a duplicate of this one. This issue is older :).

I have the problem in this situations:

Network origin: Vodafone. Spain
Network received: Movistar and Vodafone. Spain.

My terminal is a HTC Magic (Vodafone).
Firmware: 1.5
Kernel version: 2.6.27-00393-g6607056san@sandroid#1
Compilation number: CRC1

As you can see, I have updated the kernel version (since my last post) but the
problem is still there.

Please, fix the issue and let me know if you need more information.

Thanks.

Oops, I forgot the exact phone model that receives the messages.

They were:
- Nokia 7310 Supernova
- Nokia 5310 XpressMusic
- Nokia 7373

still the same problem here too:

From network SFR Vodafone France, on a HTC magic 1.5 CRC1
To network SFR Vodafone France, on a Nokia 5800 ExpressMusic

Thanks for the extra information. At this point I will close this issue as a
duplicate of  issue 2719  (yes, indeed, this issue is older, but 2719 ended up with
more stars and got looked at first). At this point we believe that the issue is fixed
in donut.

Ok. Don't worry. Just kidding :)

Thank you very much.

(No comment was entered for this change.)

Same problem with HTC Hero in Spain with Orange...

(No comment was entered for this change.)

 Issue 3227  has been merged into this issue.

 Issue 2936  has been merged into this issue.

I've the same problem with my HTC Magic

Network Operator: TMN (Portugal)

I've the same problem with my HTC Hero
Network Operator: Orange (Spain)

I've the same problem with my HTC Magic

Network Operator: TMN (Portugal)

How resolve the problem ???  It' s Drammatic when some people receive the sms....

I have the same problem with HTC Magic with Donut in Italy.

Same problem with Android 1.6 Donut in a HTC Magic from Vodafone Spain.