RE: [RFI] octstr_recode

I don't agree here - if the message in unicode, it is most likely
readable by anyone interested in receiving this message in unicode -
i.e.: if I'm interested in receiving hebrew messages in unicode (don't
know of any other coding supported by phones that can be used for hebrew
- my phone at least doesn't do windows-1255 ;-), then I think it's
likely to assume that my editor, viewer and scripts can handle hebrew.
the only question is - which unicode encoding ? 
UTF8 is 'ascii safe' and readable by most editors/viewers, so I think we
should be safe using that.
 
Oded Arbel
m-Wise Inc.
[email protected]
 
--
Geoffrey : "I have a feeling this is going to be the beginning of a
beautiful hatred."
 -- from "The Two Mrs. Carrolls"


-----Original Message-----
From: Andreas Fink [mailto:[email protected]]
Sent: Tuesday, March 05, 2002 9:38 PM
To: Bruno David Rodrigues
Cc: [email protected]
Subject: Re: [RFI] octstr_recode
I understand your goal. Support incoming Unicode.
Well the question is do we need to recode in this case?
If the incoming message is in unicode, its most probably not readable by
us (being iso8859-1 only humans)). So why not simply carry them along
"as is". the coding in DCS from the incoming message tells us its
unicode, and thats enough for us.


The only thing I see a problem with is SMSbox'es keywords where it would
have to split off a keyword (ok that can be done) but then we need to
enter non english keywords in a ascii textfile which gets tough....


-- 

Andreas Fink
Fink-Consulting