>I'm doing development for an SMS app on a handspring. Having a bit >of a problem >with the PalmOS character substitution of characters in the GSM alphabet. The >problem is as follows; > >When a message is sent to the device which contains characters that are not in >the PalmOS alphabet (delta, phi, gamma, etc) then they are substituted by >strings (\Delta, \Phi, etc). This is fine, but as part of the app I have to >receive the GSM character '1)' (its hex 1B in GSM). This obviously >isn't in the >PalmOS alphabet either but instead of substituting it with a string the device >just ignores the character altogether. The only reason I know its missing is >because I know what I sent to the device. Does anyone know if there is anyway >of receiving this character ?
The 0x1B character code in GSM is an escape character. I think that in the specification document you're looking at, it's displayed as '1)' in the glyph table because there's a note below the table that explains how this is used to extend the GSM character set. The valid escape sequences are: 0x1B0A 0x000C # FORM FEED 0x1B14 0x005E # CIRCUMFLEX ACCENT 0x1B28 0x007B # LEFT CURLY BRACKET 0x1B29 0x007D # RIGHT CURLY BRACKET 0x1B2F 0x005C # REVERSE SOLIDUS 0x1B3C 0x005B # LEFT SQUARE BRACKET 0x1B3D 0x007E # TILDE 0x1B3E 0x005D # RIGHT SQUARE BRACKET 0x1B40 0x007C # VERTICAL LINE 0x1B65 0x20AC # EURO SIGN If 0x1B is followed by something other than one of the ten byte values referenced above, it should be treated as a non-breaking space character. I don't know if that's what Handspring does in their GSM->PalmLatin conversion code. -- Ken -- Ken Krugler TransPac Software, Inc. <http://www.transpac.com> +1 530-470-9200 -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
