On Mar 13, 2015 7:47 PM, João M. S. Silva <<a href="mailto:joao.m.santos.silva@gmail.com">joao.m.santos.silva@gmail.com</a>> wrote: > > On 03/13/2015 05:31 PM, Aleksander Morgado wrote: >> >> When using --messaging-create-sms-with-data the encoding type is set >> as being raw. If you're sending text you really need to use the >> "text=whatever" option. Maybe you need to escape the EOLs before >> setting them in ${text}? Truth be told, I never tested it with >> multiple lines... :) > > > Does not seem to work. Either with single-escaping: > > Content | number: '---------' > | text: '1st line\n2nd line' > > or double-escaping: > > Content | number: '---------' > | text: '1st line\\n2nd line' > > the SMS's are received as presented in the Content above, i.e. the \n are not interpreted correctly, they are treated as 2 chars. > > With --messaging-create-sms-with-data the message is correctly presented in a smartphone, so I guess raw mode works OK. > > I think the problem is that the non-smartphone is not capable of understanding the SMS in raw (GSM 7-bit) mode. > > Thanks anyway. Any further hints? This must be possible since I receive line wrapped SMS's in this older phone Raw mode is not gsm7. Raw mode is 8bit mode. Text mode is either gsm7 or ucs2. I guess we can just un-escape the text in mmcli before sending it to MM, shouldnt be a big deal.