Hi all,
at http://www.kannel.org/~amalysh/kannel-utf8.patch is a not so huge patch
that converts internal kannel charset to UTF-8. Please note that I didn't
add smsbox compatibility code, means smsbox expect text body to be encoded
in UTF-8 as default also MOs will be forwarded in UTF-8. It
Hi Alex,
Awesome initiative! I've been hoping for this to happen for quite a
while. There are a few issues though:
1. In the gwlib/latin1_to_gsm.h, (space) is replaced with
(0x1B), and is mapped to NRP instead of just . (If you follow me)
2. For some odd reason, smsbox trims the message
Hi,
Am 20.07.2006, 12:48 Uhr, schrieb Peter Christensen <[EMAIL PROTECTED]>:
Hi Alex,
Awesome initiative! I've been hoping for this to happen for quite a
Thanks!
while. There are a few issues though:
1. In the gwlib/latin1_to_gsm.h, (space) is replaced with
(0x1B), and is mapped to N
Hi,
Alexander Malysh wrote:
Hi,
Am 20.07.2006, 12:48 Uhr, schrieb Peter Christensen <[EMAIL PROTECTED]>:
Hi Alex,
Awesome initiative! I've been hoping for this to happen for quite a
Thanks!
while. There are a few issues though:
1. In the gwlib/latin1_to_gsm.h, (space) is replaced with
Hi Alex,
So when can we have the patch for UTF-8 in CVS?
It seems from your and Peter's comments, that the only issues are to have a
cgi variable for the escape sign and one for the charset. Once the patch is
in CVS, the Kannel community will not have to find ways to have the Greek
charset or how
Hi All,
as no objections were here, commited to cvs.
Am 13.07.2006, 21:35 Uhr, schrieb Alexander Malysh <[EMAIL PROTECTED]>:
patch that converts internal kannel charset to UTF-8. Please note that I
didn't add smsbox compatibility code, means smsbox expect text body to
be encoded in UTF-8 as
Hi List,
When i am trying ro run test_ppg, I get:
2006-10-03 17:32:46 [13211] [14] WARNING: wap.mime:
check_control_headers: Content-Type missingin SOAP part
2006-10-03 17:32:46 [13211] [14] WARNING: wap.mime: mime_parse:
erroneous soap entity headers in the multipart
This runs an version
Hi Aarno,
I don't see how internal charset could be related to toupper things.
Internal charset just change msgdata encoding in sms structure to utf-8.
Am 09.10.2006, 10:07 Uhr, schrieb Aarno Syvänen <[EMAIL PROTECTED]>:
Hi List,
When i am trying ro run test_ppg, I get:
2006-10-03 17:32:4
e. (i mean returned
string will be UTF-8 coded)
Vincent.
- Original Message -
From: "Alexander Malysh" <[EMAIL PROTECTED]>
To:
Sent: Monday, October 09, 2006 1:03 PM
Subject: Re: [PATH] convert internal charset to UTF-8
Hi Aarno,
I don't see how internal c
be updated.
Vincent.
- Original Message -
From: "Vincent CHAVANIS" <[EMAIL PROTECTED]>
To:
Sent: Monday, October 09, 2006 4:47 PM
Subject: Re: [PATH] convert internal charset to UTF-8
Just a little warning,
It also changes the sms-services when get-url is called.
It will
ault as latin1
(or clearly indicates here a compatibility breaker)
Also, the userguide need to be updated.
Vincent.
- Original Message - From: "Vincent CHAVANIS"
<[EMAIL PROTECTED]>
To:
Sent: Monday, October 09, 2006 4:47 PM
Subject: Re: [PATH] convert internal charset
On Thu, 2006-10-12 at 13:27 +0200, Alexander Malysh wrote:
> I would like to keep UTF-8 as default charset. So we can send any charset
> we want w/o any troubles. I agree that we should document it in userguide.
> For users that want further send in latin1: they can use 'charset=LATIN1'
> cgi
Alexander Malysh wrote:
Hi Vincent,
I would like to keep UTF-8 as default charset. So we can send any
charset we want w/o any troubles. I agree that we should document it in
userguide. For users that want further send in latin1: they can use
'charset=LATIN1' cgi parameter for sendsms inte
au destinataire : compte épuisé
E50_TMSGSMS non remis au destinataire : compte épuisé
regards
Vincent.
- Original Message -
From: "Stipe Tolj" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, October 12, 2006 3:33 PM
Subject: Re: [PATH] convert internal charset to
; <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, October 12, 2006 3:33 PM
Subject: Re: [PATH] convert internal charset to UTF-8
Alexander Malysh wrote:
Hi Vincent,
I would like to keep UTF-8 as default charset. So we can send any
charset we want w/o any troubles. I agree that we should d
Vincent CHAVANIS wrote:
before (MO)
E50_NMSG
2852453A2950657572206465206D61207205616374696F6E2070617320726170706F7274207F2071756F693F
E50_AMSG(RE:)Peur de ma réaction pas rapport à quoi?
E50_TMSG(RE:)Peur de ma réaction pas rapport à quoi?
before (DLR)
E50_NMSG
534D53206E
right.
- Original Message -
From: "Stipe Tolj" <[EMAIL PROTECTED]>
To: "Vincent CHAVANIS" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, October 12, 2006 4:23 PM
Subject: Re: [PATH] convert internal charset to UTF-8
a sms-service will get UTF-8'ed v
On Thu, 2006-10-12 at 16:23 +0200, Stipe Tolj wrote:
> a sms-service will get UTF-8'ed values for non ASCII chars rather then
> latin as before, right?
Which is the expected behavior, IMO. Called service should be able to
handle Content-Type header properly and convert as necessary.
--
.O.
..O
Enver ALTIN wrote:
On Thu, 2006-10-12 at 16:23 +0200, Stipe Tolj wrote:
a sms-service will get UTF-8'ed values for non ASCII chars rather then
latin as before, right?
Which is the expected behavior, IMO. Called service should be able to
handle Content-Type header properly and convert as ne
19 matches
Mail list logo
