This is true for non English (or Latin based) languages. However, for regular ASCII, it holds that 1 char = 1 byte.I think it's two bytes per character. One byte allows 256 different characters, and there are more than that available (consider that you can send a message in languages such as Japanese or Arabic if you wish).
Well, I guess it depends on whether the phone/network is clever enough to dynamically switch encoding based on what's been entered, or whether it'll do everything in "extended" (Unicode?) format.This is true for non English (or Latin based) languages. However, for regular ASCII, it holds that 1 char = 1 byte.
Ah, and this would apply for a regular text message, yes?This is true for non English (or Latin based) languages. However, for regular ASCII, it holds that 1 char = 1 byte.
Goddammit you snuck in againWell, I guess it depends on whether the phone/network is clever enough to dynamically switch encoding based on what's been entered, or whether it'll do everything in "extended" (Unicode?) format.
Transmission of short messages between the SMSC and the handset is done whenever using the Mobile Application Part (MAP) of the SS7 protocol. Messages are sent with the MAP MO- and MT-ForwardSM operations, whose payload length is limited by the constraints of the signaling protocol to precisely 140 octets (140 octets = 140 * 8 bits = 1120 bits). Short messages can be encoded using a variety of alphabets: the default GSM 7-bit alphabet, the 8-bit data alphabet, and the 16-bit UCS-2 alphabet. Depending on which alphabet the subscriber has configured in the handset, this leads to the maximum individual short message sizes of 160 7-bit characters, 140 8-bit characters, or 70 16-bit characters. GSM 7-bit alphabet support is mandatory for GSM handsets and network elements, but characters in languages such as Arabic, Chinese, Korean, Japanese or Cyrillic alphabet languages (e.g. Russian, Serbian, Bulgarian, etc.) must be encoded using the 16-bit UCS-2 character encoding (see Unicode). Routing data and other metadata is additional to the payload size.
Unnecessary anecdote: I used to have a handset which, when set to use English, used up several characters in the character count when using letters like ç, but when set to French ç only equalled one letter in the character count.All these replies, no one bothered to look it up ?
Routing and metadata are not counted, but depending if you bust character count, your message could cost you extra as there is such a thing as concatenated SMS, which is a set of SMS messages that each represent a segment of the total message. Each segment could be charged as a seperate SMS since that is what it is. If your message requires segmentation for a concatenated SMS, your character count will be lower as an additional header is inserted right into the user data portion (7 bytes for 7 bit ASCII encoded messages, 8 bytes for 8-bit or 16 bit encoded messages.This mightn't be relevant to the question, since each message sent is a flat rate.