RE: EMI2

2001-11-13 Thread Jacob Vennervald Madsen

It is alphanumeric.
Do you think it makes a difference?

Jacob

-Original Message-
From: Bruno David Simoes Rodrigues [mailto:[EMAIL PROTECTED]]
Sent: 12. november 2001 22:59
To: Jacob Vennervald Madsen
Cc: [EMAIL PROTECTED]
Subject: Re: EMI2


Is your username alphanumeric ?

The code of emi2 just encodes a numeric username, we have to
see if emi specs say something about encoding alphanumeric
usernames.

I'm always using numéric usernames (usually the short code)

- Original Message -
From: "Jacob Vennervald Madsen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 1:53 PM
Subject: EMI2


Hi List

I'm using Kannel 1.1.5 on a Linux machine.
I'm trying to connect to a CMG UCP interface.
This is my configuration:

group = smsc
smsc = emi2
host = smsc.maingate.se
port = 5001
smsc-username = **
smsc-password = **
receive-port = 9171
connect-allow-ip = 195.67.90.149

When i start Kannel I get the following error:

2001-11-12 13:43:24 [0] DEBUG: smsc_emi2: start called
2001-11-12 13:43:24 [7] DEBUG: sms_router: time to sleep
2001-11-12 13:43:24 [7] DEBUG: sms_router: list_len = 0
2001-11-12 13:43:24 [6] DEBUG: Sending operation type 60, message with
password not shown in log file.
2001-11-12 13:43:24 [6] DEBUG: emi2 parsing packet: <00/00035/R/60/N/02/
Syntax error/FA>
2001-11-12 13:43:24 [6] ERROR: Got negative ack. op:60, trn:0, error:2
(Syntax error), message: Syntax error
2001-11-12 13:43:24 [6] ERROR: smsc_emi2: Server rejected our login,
giving up
2001-11-12 13:43:24 [5] DEBUG: Thread 5 (gw/smsc_emi2.c:emi2_listener)
terminates.
2001-11-12 13:43:24 [6] DEBUG: smsc_emi2 connection has completed
shutdown.
2001-11-12 13:43:24 [6] DEBUG: Thread 6 (gw/smsc_emi2.c:emi2_sender)
terminates.

Any ideas?

Jacob







RE: EMI2

2001-11-13 Thread Jacob Vennervald Madsen

The SMSC I am connected to apparently doesn't support 60-series
operations.
Is there any way i can make kannel use 50-series operations instead?

Jacob

-Original Message-
From: Jacob Vennervald Madsen 
Sent: 13. november 2001 09:25
To: Bruno David Simoes Rodrigues
Cc: [EMAIL PROTECTED]
Subject: RE: EMI2


It is alphanumeric.
Do you think it makes a difference?

Jacob

-Original Message-
From: Bruno David Simoes Rodrigues [mailto:[EMAIL PROTECTED]]
Sent: 12. november 2001 22:59
To: Jacob Vennervald Madsen
Cc: [EMAIL PROTECTED]
Subject: Re: EMI2


Is your username alphanumeric ?

The code of emi2 just encodes a numeric username, we have to
see if emi specs say something about encoding alphanumeric
usernames.

I'm always using numéric usernames (usually the short code)

- Original Message -
From: "Jacob Vennervald Madsen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 1:53 PM
Subject: EMI2


Hi List

I'm using Kannel 1.1.5 on a Linux machine.
I'm trying to connect to a CMG UCP interface.
This is my configuration:

group = smsc
smsc = emi2
host = smsc.maingate.se
port = 5001
smsc-username = **
smsc-password = **
receive-port = 9171
connect-allow-ip = 195.67.90.149

When i start Kannel I get the following error:

2001-11-12 13:43:24 [0] DEBUG: smsc_emi2: start called
2001-11-12 13:43:24 [7] DEBUG: sms_router: time to sleep
2001-11-12 13:43:24 [7] DEBUG: sms_router: list_len = 0
2001-11-12 13:43:24 [6] DEBUG: Sending operation type 60, message with
password not shown in log file.
2001-11-12 13:43:24 [6] DEBUG: emi2 parsing packet: <00/00035/R/60/N/02/
Syntax error/FA>
2001-11-12 13:43:24 [6] ERROR: Got negative ack. op:60, trn:0, error:2
(Syntax error), message: Syntax error
2001-11-12 13:43:24 [6] ERROR: smsc_emi2: Server rejected our login,
giving up
2001-11-12 13:43:24 [5] DEBUG: Thread 5 (gw/smsc_emi2.c:emi2_listener)
terminates.
2001-11-12 13:43:24 [6] DEBUG: smsc_emi2 connection has completed
shutdown.
2001-11-12 13:43:24 [6] DEBUG: Thread 6 (gw/smsc_emi2.c:emi2_sender)
terminates.

Any ideas?

Jacob








Re: doc/PNG Files

2001-11-13 Thread David Holland

On Mon, Nov 12, 2001 at 02:37:10PM +1300, Worik Macky Turei Stanton wrote:
> A lot of the *.png files under doc are corrupted.

Which ones?

> Are you the correct person to notify?

Not really; I just keep the machine running kannel.3glab.org happy. I've
cc'ed the devel list. Someone there might have a better idea.

Dave
-- 
David Holland   =*=   Systems Manager   =*=   tel: +44 01223 478900
http://www.3glab.com/   =*= 3G Lab, UK  =*=   fax: +44 01223 478901




RE: doc/PNG Files

2001-11-13 Thread Jörg Pommnitz

 
[jpo@jpo wtls]$ pwd
/home/jpo/CVS/gateway/doc/wtls
[jpo@jpo wtls]$ file *.png
fig10o.png:   PNG image data, CORRUPTED,
fig1o.png:PNG image data, CORRUPTED,
fig2o.png:PNG image data, CORRUPTED,
fig3o.png:PNG image data, CORRUPTED,
fig4o.png:PNG image data, CORRUPTED,
fig4out.png:  PNG image data, CORRUPTED,
fig5o.png:PNG image data, CORRUPTED,
fig5out.png:  PNG image data, CORRUPTED,
fig6o.png:PNG image data, CORRUPTED,
fig6out1.png: PNG image data, CORRUPTED,
fig6out.png:  PNG image data, CORRUPTED,
fig7o.png:PNG image data, CORRUPTED,
fig8o.png:PNG image data, CORRUPTED,
fig9o.png:PNG image data, CORRUPTED,



-Original Message-
From: David Holland
To: Worik Macky Turei Stanton
Cc: [EMAIL PROTECTED]
Sent: 11/13/01 1:36 PM
Subject: Re: doc/PNG Files

On Mon, Nov 12, 2001 at 02:37:10PM +1300, Worik Macky Turei Stanton
wrote:
> A lot of the *.png files under doc are corrupted.

Which ones?

> Are you the correct person to notify?

Not really; I just keep the machine running kannel.3glab.org happy. I've
cc'ed the devel list. Someone there might have a better idea.

Dave
-- 
David Holland   =*=   Systems Manager   =*=   tel: +44 01223
478900
http://www.3glab.com/   =*= 3G Lab, UK  =*=   fax: +44 01223
478901




RE: doc/PNG Files

2001-11-13 Thread Jörg Pommnitz

The transition from revision 1.1 to 1.2 looks very suspicious
to me:


revision 1.2
date: 2001/10/31 18:59:33;  author: keogh;  state: Exp;  lines: +0 -225
Kannel updates

revision 1.1
date: 2001/09/03 21:55:10;  author: davi;  state: Exp;
*** empty log message ***


Regards
  Jörg




Re: doc/PNG Files

2001-11-13 Thread David Holland

On Tue, Nov 13, 2001 at 02:06:41PM +0100, Jörg Pommnitz wrote:
> [jpo@jpo wtls]$ file *.png
> fig10o.png:   PNG image data, CORRUPTED,
> fig1o.png:PNG image data, CORRUPTED,

I see rev 1.2 was checked in on 2001-10-31, that version appears to be
the problem, because the 1.1 files are OK. At least, fig1o.png v1.1 is
fine, I didn't check them all.

1.2 was checked in by Paul Keogh. Paul, what did you do?

Dave
-- 
David Holland   =*=   Systems Manager   =*=   tel: +44 01223 478900
http://www.3glab.com/   =*= 3G Lab, UK  =*=   fax: +44 01223 478901




At modules

2001-11-13 Thread Alexei Pashkovsky



Hi all,
since we still had some troubles with recent AT2 
module, 
I have tried the new AT module made by 
Matthew.
The kannel I got from his page was installed in 
production machine.
I was amazed by performance, it was really nice to 
discover that siemens could actually be this fast!
The speed is greatly improved, and I didn't speak 
about stability yet.
I think the new AT is way better than the previous 
one and if you compare stability+productivity, than better than AT2 too, though 
I really like the changes Andreas made to AT2.
Look at this line to understand :
6    AT: /dev/usb/ttyUSB6 (online 
218s, rcvd 155, sent 0, failed 0, queued 0 msgs)
This is fantastic.
The previous At module's best result was 1 sms per 
5 sec.
I think we should change the AT in CVS with this 
one.
Extremely recommended.
 


Re: doc/PNG Files

2001-11-13 Thread David Holland

On Tue, Nov 13, 2001 at 02:09:29PM +0100, Jörg Pommnitz wrote:
> The transition from revision 1.1 to 1.2 looks very suspicious
> to me:

I've reverted the contents of the wtls/*.png files to what they were at
1.1 (so now they are all 1.3).

Dave
-- 
David Holland   =*=   Systems Manager   =*=   tel: +44 01223 478900
http://www.3glab.com/   =*= 3G Lab, UK  =*=   fax: +44 01223 478901




EMI2 fix for multi recipients

2001-11-13 Thread Jacob Vennervald Madsen

Hi List

When I use AT or CIMD2 as smsc and sepcify multiple recipients separated
by '+' in the http url, everything works just fine.
The smsbox receivs the request and the bearerbox sends one message per
receiver.
But when I use EMI2 as smsc and specify multiple recipients, the smsbox
receives it correctly but the bearerbox tries to send all the messages
through one operation to the EMI2 SMSC.
This is not possible through the use of operation 51.
Has anybody made a patch for this problem?

Best regards,
Jacob Vennervald Madsen
Mobile System Developer

GoPinocchio
Norrebrogade 45
DK-2200 Copenhagen
www.gopinocchio.com
+45 26750106

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.





Re: EMI2 fix for multi recipients

2001-11-13 Thread Uoti Urpala

Jacob Vennervald Madsen wrote:

> When I use AT or CIMD2 as smsc and sepcify multiple recipients separated
> by '+' in the http url, everything works just fine.


This "multi-send" feature is broken and should not be used. It doesn't 
work correctly with any of the options that depend on or affect phone 
numbers.





RE: EMI2 fix for multi recipients

2001-11-13 Thread Jacob Vennervald Madsen

So when I use kannel I should make one http request per recipient?

Has anybody tried to send messages to more than 10.000 recipients?
How does it perform?
I mean it does create a huge network overhead.

Jacob

-Original Message-
From: Uoti Urpala [mailto:[EMAIL PROTECTED]]
Sent: 13. november 2001 17:57
To: [EMAIL PROTECTED]
Subject: Re: EMI2 fix for multi recipients


Jacob Vennervald Madsen wrote:

> When I use AT or CIMD2 as smsc and sepcify multiple recipients
separated
> by '+' in the http url, everything works just fine.


This "multi-send" feature is broken and should not be used. It doesn't 
work correctly with any of the options that depend on or affect phone 
numbers.






Re: At modules

2001-11-13 Thread Nick Clarey

Howdy,

> The previous At module's best result was 1 sms per 5 sec.
> I think we should change the AT in CVS with this one.
> Extremely recommended.

Great, I'd love to. Now if someone could just submit a properly formatted
patch for review...it might get applied. Feeling keen, Alexei?

See ya,

Nick





Re: At modules

2001-11-13 Thread Alexei Pashkovsky



Hi all,
don't hurry with the update, I already found some 
minor bugs.
There's one strange thing when new AT cannot delete 
a mesage from SIM, it reads it again and again.
The position cursor is mismatched.
Log :
 
2001-11-13 19:14:56 [15] DEBUG: Read from modem: 
'OK'2001-11-13 19:14:56 [15] DEBUG: AT: Command: 
AT+CMGR=62001-11-13 19:14:57 [9] DEBUG: AT: Command: 
AT+CPMS="SM"2001-11-13 19:14:57 [7] DEBUG: AT: Command: 
AT+CPMS="SM"2001-11-13 19:14:57 [11] DEBUG: AT: Command: 
AT+CPMS="SM"2001-11-13 19:14:57 [21] DEBUG: Read from modem: '+CMGR: 
1,,240791449737019037200C9144876171453110'2001-11-13 19:14:57 [21] 
DEBUG: Read from modem: '+CMGR: 
1,,240791449737019037200C91448761714531104100840005CCFCF83D07
 
OK'2001-11-13 19:14:57 [21] DEBUG: AT: 
Command: AT+CMGD=12001-11-13 19:14:57 [21] DEBUG: Read from modem: '+CMS 
ERROR: 321'2001-11-13 19:14:57 [21] DEBUG: deleteing index at mem index : 
1
 
2001-11-13 19:14:57 [21] DEBUG: smscconn (AT: 
/dev/usb/ttyUSB7): new message received2001-11-13 19:14:57 [21] DEBUG: AT: 
Command: AT+CPMS="SM"2001-11-13 19:14:57 [6] DEBUG: boxc_sender: sent 
message to <127.0.0.1>2001-11-13 19:14:57 [5] DEBUG: boxc_receiver: 
got ack2001-11-13 19:14:57 [15] DEBUG: Read from modem: 
'OK'2001-11-13 19:14:57 [15] DEBUG: AT: Command: 
AT+CMGR=72001-11-13 19:14:57 [19] DEBUG: AT: Command: 
AT+CPMS="SM"2001-11-13 19:14:57 [21] DEBUG: AT: Command: 
AT+CMGR=12001-11-13 19:14:58 [13] DEBUG: AT: Command: 
AT+CPMS="SM"2001-11-13 19:14:58 [15] DEBUG: Read from modem: 
'OK'2001-11-13 19:14:58 [15] DEBUG: AT: Command: 
AT+CMGR=82001-11-13 19:14:58 [21] DEBUG: Read from modem: '+CMGR: 
1,,240791449737019037200C9144876171453110'2001-11-13 19:14:58 [21] 
DEBUG: Read from modem: '+CMGR: 
1,,240791449737019037200C91448761714531104100840005CCFCF83D07
 
OK'2001-11-13 19:14:58 [21] DEBUG: AT: 
Command: AT+CMGD=12001-11-13 19:14:58 [17] DEBUG: AT: Command: 
AT+CPMS="SM"2001-11-13 19:14:58 [21] DEBUG: Read from modem: '+CMS ERROR: 
321'2001-11-13 19:14:58 [21] DEBUG: deleteing index at mem index : 
1
 
2001-11-13 19:14:58 [21] DEBUG: smscconn (AT: 
/dev/usb/ttyUSB7): new message received2001-11-13 19:14:58 [21] DEBUG: AT: 
Command: AT+CPMS="SM"2001-11-13 19:14:58 [6] DEBUG: boxc_sender: sent 
message to <127.0.0.1>2001-11-13 19:14:58 [5] DEBUG: boxc_receiver: 
got ack2001-11-13 19:14:59 [21] DEBUG: AT: Command: AT+CMGR=12001-11-13 
19:14:59 [15] DEBUG: Read from modem: 'OK'2001-11-13 19:14:59 [15] 
DEBUG: AT: Command: AT+CMGR=9
 
- Original Message - 
From: "Nick Clarey" <[EMAIL PROTECTED]>
To: "Alexei Pashkovsky" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 8:17 
PM
Subject: Re: At modules
> Howdy,> > > The previous At module's best result 
was 1 sms per 5 sec.> > I think we should change the AT in CVS with 
this one.> > Extremely recommended.> > Great, I'd love 
to. Now if someone could just submit a properly formatted> patch for 
review...it might get applied. Feeling keen, Alexei?> > See 
ya,> > Nick> > 


Re: At modules

2001-11-13 Thread Matthew Flax

Check your log again Alexei,

Your SIM has 15 memory spots. When the first is taken, the second is used.
Hence the AT module reads from the first to the fifteenth :
at+cmgr=1
at+cmgr=2
at+cmgr=3
at+cmgr=4
... and so on 
at+cmgr=15

Every time a new SMS is received, then it gets dispatched to the first
memory location - normally 1 unless it is used.

The following addition to the code is important and is not in my release :
File : smsc_at.c
Function : static int send_modem_command

Add a 'usleep' command at the following point in the function :
  /* send the command */
  write(fd, cmd, strlen(cmd));
  write(fd, "\r", 1);

  usleep(10);

  /* We don't want to wait forever -
   * This is not perfect but OK for now */
  for( i=0; i<1000; i++) {

reguards
Matt

On 13 November 2001, Alexei Pashkovsky wrote:
> Hi all,
> don't hurry with the update, I already found some minor bugs.
> There's one strange thing when new AT cannot delete a mesage from SIM, it reads it 
>again and again.
> The position cursor is mismatched.
> Log :
> 
> 2001-11-13 19:14:56 [15] DEBUG: Read from modem: '
> OK
> '
> 2001-11-13 19:14:56 [15] DEBUG: AT: Command: AT+CMGR=6
> 2001-11-13 19:14:57 [9] DEBUG: AT: Command: AT+CPMS="SM"
> 2001-11-13 19:14:57 [7] DEBUG: AT: Command: AT+CPMS="SM"
> 2001-11-13 19:14:57 [11] DEBUG: AT: Command: AT+CPMS="SM"
> 2001-11-13 19:14:57 [21] DEBUG: Read from modem: '
> +CMGR: 1,,24
> 0791449737019037200C9144876171453110'
> 2001-11-13 19:14:57 [21] DEBUG: Read from modem: '
> +CMGR: 1,,24
> 0791449737019037200C91448761714531104100840005CCFCF83D07
> 
> OK
> '
> 2001-11-13 19:14:57 [21] DEBUG: AT: Command: AT+CMGD=1
> 2001-11-13 19:14:57 [21] DEBUG: Read from modem: '+CMS ERROR: 321'
> 2001-11-13 19:14:57 [21] DEBUG: deleteing index at mem index : 1
> 
> 2001-11-13 19:14:57 [21] DEBUG: smscconn (AT: /dev/usb/ttyUSB7): new message received
> 2001-11-13 19:14:57 [21] DEBUG: AT: Command: AT+CPMS="SM"
> 2001-11-13 19:14:57 [6] DEBUG: boxc_sender: sent message to <127.0.0.1>
> 2001-11-13 19:14:57 [5] DEBUG: boxc_receiver: got ack
> 2001-11-13 19:14:57 [15] DEBUG: Read from modem: '
> OK
> '
> 2001-11-13 19:14:57 [15] DEBUG: AT: Command: AT+CMGR=7
> 2001-11-13 19:14:57 [19] DEBUG: AT: Command: AT+CPMS="SM"
> 2001-11-13 19:14:57 [21] DEBUG: AT: Command: AT+CMGR=1
> 2001-11-13 19:14:58 [13] DEBUG: AT: Command: AT+CPMS="SM"
> 2001-11-13 19:14:58 [15] DEBUG: Read from modem: '
> OK
> '
> 2001-11-13 19:14:58 [15] DEBUG: AT: Command: AT+CMGR=8
> 2001-11-13 19:14:58 [21] DEBUG: Read from modem: '
> +CMGR: 1,,24
> 0791449737019037200C9144876171453110'
> 2001-11-13 19:14:58 [21] DEBUG: Read from modem: '
> +CMGR: 1,,24
> 0791449737019037200C91448761714531104100840005CCFCF83D07
> 
> OK
> '
> 2001-11-13 19:14:58 [21] DEBUG: AT: Command: AT+CMGD=1
> 2001-11-13 19:14:58 [17] DEBUG: AT: Command: AT+CPMS="SM"
> 2001-11-13 19:14:58 [21] DEBUG: Read from modem: '+CMS ERROR: 321'
> 2001-11-13 19:14:58 [21] DEBUG: deleteing index at mem index : 1
> 
> 2001-11-13 19:14:58 [21] DEBUG: smscconn (AT: /dev/usb/ttyUSB7): new message received
> 2001-11-13 19:14:58 [21] DEBUG: AT: Command: AT+CPMS="SM"
> 2001-11-13 19:14:58 [6] DEBUG: boxc_sender: sent message to <127.0.0.1>
> 2001-11-13 19:14:58 [5] DEBUG: boxc_receiver: got ack
> 2001-11-13 19:14:59 [21] DEBUG: AT: Command: AT+CMGR=1
> 2001-11-13 19:14:59 [15] DEBUG: Read from modem: '
> OK
> '
> 2001-11-13 19:14:59 [15] DEBUG: AT: Command: AT+CMGR=9
> 
> - Original Message - 
> From: "Nick Clarey" <[EMAIL PROTECTED]>
> To: "Alexei Pashkovsky" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, November 13, 2001 8:17 PM
> Subject: Re: At modules
> 
> 
> > Howdy,
> > 
> > > The previous At module's best result was 1 sms per 5 sec.
> > > I think we should change the AT in CVS with this one.
> > > Extremely recommended.
> > 
> > Great, I'd love to. Now if someone could just submit a properly formatted
> > patch for review...it might get applied. Feeling keen, Alexei?
> > 
> > See ya,
> > 
> > Nick
> > 
> > 

-- 
Matt

For electronic musicians ...
Vector Bass  : http://mffmvectorbass.sourceforge.net/
For developers ...
3D Audio Library : http://mffm3daudiolib.sourceforge.net/
Multimedia Time Code : http://mffmtimecode.sourceforge.net/




Encoding and charset_to_utf8

2001-11-13 Thread Worik Macky Turei Stanton

Friends

(At least in the case of...) When a message is sent via the http
interface to smsbox smsbox_req_handle calls charset_processing to
translate the text.

If the coding is UCS2 and the charset is not UTF-16BE it is converted
to utf8, thence to UTF-16BE.

So far so good.

But I have some questions about the charset_to_utf8.  

charset_to_utf8 uses libxml2 to do the grunt work of translating the
encoding (xmlFindCharEncodingHandler and xmlCharEncInFunc).  I have
been looking at...

http://xmlsoft.org/html/libxml-encoding.html#XMLCHARENCODING

This has lists a few charecter codings.  (I have listed them via cut
and paste below).  My email archives have emails in quite a few
different encodings.  What about them?

The char types I have found in my email archive...

 BIG5
 EUC-KR
 GB2312
 GB2312_CHARSET
 ISO-10646
 ISO-2022-JP
 ISO-8859-1
 ISO-8859-2
 ISO-8859-4
 ISO-8859-7
 ISO-8859-9;
 KOI8-R
 UNKNOWN-8BIT
 US-ASCII
 UTF-8
 Windows-1250
 Windows-1251
 Windows-1252
 X-UNKNOWN
 big5
 euc-kr
 gb2312
 iso-2022-kr
 iso-8859-1
 iso-8859-1
 iso-8859-13
 iso-8859-15
 koi8-r
 ks_c_5601-1987
 unknown-8bit
 windows-1256
 x-user-defined

The chartypes listed on http://xmlsoft.org/html/libxml-encoding.html


 XML_CHAR_ENCODING_ERROR=   -1, /* No char encoding detected */
 XML_CHAR_ENCODING_NONE=0, /* No char encoding detected */
 XML_CHAR_ENCODING_UTF8=1, /* UTF-8 */
 XML_CHAR_ENCODING_UTF16LE= 2, /* UTF-16 little endian */
 XML_CHAR_ENCODING_UTF16BE= 3, /* UTF-16 big endian */
 XML_CHAR_ENCODING_UCS4LE=  4, /* UCS-4 little endian */
 XML_CHAR_ENCODING_UCS4BE=  5, /* UCS-4 big endian */
 XML_CHAR_ENCODING_EBCDIC=  6, /* EBCDIC uh! */
 XML_CHAR_ENCODING_UCS4_2143=7, /* UCS-4 unusual ordering */
 XML_CHAR_ENCODING_UCS4_3412=8, /* UCS-4 unusual ordering */
 XML_CHAR_ENCODING_UCS2=9, /* UCS-2 */
 XML_CHAR_ENCODING_8859_1=  10,/* ISO-8859-1 ISO Latin 1 */
 XML_CHAR_ENCODING_8859_2=  11,/* ISO-8859-2 ISO Latin 2 */
 XML_CHAR_ENCODING_8859_3=  12,/* ISO-8859-3 */
 XML_CHAR_ENCODING_8859_4=  13,/* ISO-8859-4 */
 XML_CHAR_ENCODING_8859_5=  14,/* ISO-8859-5 */
 XML_CHAR_ENCODING_8859_6=  15,/* ISO-8859-6 */
 XML_CHAR_ENCODING_8859_7=  16,/* ISO-8859-7 */
 XML_CHAR_ENCODING_8859_8=  17,/* ISO-8859-8 */
 XML_CHAR_ENCODING_8859_9=  18,/* [ISO-8859-9 */
 XML_CHAR_ENCODING_2022_JP=  19,/* ISO-2022-JP */
 XML_CHAR_ENCODING_SHIFT_JIS=20,/* Shift_JIS */
 XML_CHAR_ENCODING_EUC_JP=   21,/* EUC-JP */
 XML_CHAR_ENCODING_ASCII=22 /* pure ASCII */

Worik

-- 
  Worik Macky Turei Stanton
Bullseye!!   [EMAIL PROTECTED]
   Aotearoa