On Fri, 2002-11-22 at 04:54, Alan McNatty wrote:
Hi Oded,
It was included - but as mentioned implied iconv was required not
optional.
No so - configure will check for it and set HAVE_ICONV only if the header file exists (which to me suggests that the library is installed - I don't know
On Sun, 2002-11-24 at 05:34, Stipe Tolj wrote:
I would leave it in gsm character set as far as possible because the receiver might want to do its own conversion. And converting it to latin1 is not lossless.
in any case not convert it if coding means its binary
yep, agreed, binary things
On Sonntag, November 24, 2002, at 04:35 Uhr, Alan McNatty wrote:
On Fri, 2002-11-22 at 21:04, Andreas Fink wrote:
Why gsm_to_latin1 if we know encoding?
We don't, well the smpp driver doesn't - that's the whole point of this
patch. In the case where the data coding is set to SMSC default
Hi
At 12:57 PM 11/24/02 +0100, Andreas Fink wrote:
We
don't, well the smpp driver doesn't - that's the whole point of this
patch. In the case where the data coding is set to SMSC default (0x00) -
the smpp driver doesn't know what decoding to do.
Well the spec says that its GSM character set.
my mistake - I have replied to the sender, not the mailing list.
Original Message
Subject: Re: wap push receiving on siemens
Date: Sun, 24 Nov 2002 04:00:27 +0100
From: Stipe Tolj [EMAIL PROTECTED]
Organization: Wapme Systems AG
To: Szymon Stasik [EMAIL PROTECTED]
References:
yes but what I'm saying that is we should leave it in the character set
it is.
gsm_to_latin1 is something which is not a good idea either as it is run
also on binary and unicode content in the current code. In a situation where
you chain multiple kannels for incoming you simply
On Sonntag, November 24, 2002, at 03:36 Uhr, Oded Arbel wrote:
yes but what I'm saying that is we should leave it in the character set it is.
gsm_to_latin1 is something which is not a good idea either as it is run also on binary and unicode content in the current code. In a situation where
one point though - how will you handle drivers (like
SMPP) that allow you to send specific native character encodings instead of
UCS-2 when using non-GSM compatible alphabets ? send only in unicode
?
In that case the coding should indicate the specific native character set
On Sonntag, November 24, 2002, at 04:49 Uhr, Oded Arbel wrote:
one point though - how will you handle drivers (like SMPP) that allow you to send specific native character encodings instead of UCS-2 when using non-GSM compatible alphabets ? send only in unicode ?
In that case the coding
one point though - how will
you handle drivers (like SMPP) that allow you to send specific native
character encodings instead of UCS-2 when using non-GSM compatible alphabets
? send only in unicode ?
In that case the coding should indicate the specific native
10 matches
Mail list logo
