On Fri, Nov 7, 2008 at 11:06 AM, Jonathan Dickinson
<[EMAIL PROTECTED]> wrote:
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter
>> Saint-Andre
>> Sent: 07 November 2008 01:51 AM
>> To: Jabber/XMPP software development list
>> Subject: Re: [jdev]
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter
> Saint-Andre
> Sent: 07 November 2008 01:51 AM
> To: Jabber/XMPP software development list
> Subject: Re: [jdev] BOM
>
> Jonathan Dickinson wrote:
> > Much obliged. As a case of interopability, may
Jonathan Dickinson wrote:
> Much obliged. As a case of interopability, maybe something like:
> entities MUST NOT send byte order marks, however, they MUST tolerate
> them.
I'm not sure exactly what "tolerate" means.
> I am sure there are one or two (possible no longer maintained)
> libraries out
Hi
I wrote a very simple code in Ruby to register a new user.
I doesn't work.
++
Ruby code
require 'rubygems'
require 'xmpp4r'
include Jabber
c = Client.new(JID.new('[EMAIL PROTECTED]/Ruby'))
password='123'
c.connect
c.register(password)
+
I ca
Hi
I wrote a very simple code in Ruby to register a new user.
I doesn't work.
++
Ruby code
require 'rubygems'
require 'xmpp4r'
include Jabber
c = Client.new(JID.new('[EMAIL PROTECTED]/Ruby'))
password='123'
c.connect
c.register(password)
+
I ca
On Fri, Nov 7, 2008 at 1:49 AM, Jonathan Dickinson
<[EMAIL PROTECTED]> wrote:
> Much obliged. As a case of interopability, maybe something like: entities
> MUST NOT send byte order marks, however, they MUST tolerate them.
>
> I am sure there are one or two (possible no longer maintained) libraries
On Thursday 06 November 2008 12:49:30 Jonathan Dickinson wrote:
> Much obliged. As a case of interopability, maybe something like: entities
> MUST NOT send byte order marks, however, they MUST tolerate them.
As I understand it, BOM are used only for UTF-16. At the XML layer in
Psi/Iris, I believ
Much obliged. As a case of interopability, maybe something like: entities MUST
NOT send byte order marks, however, they MUST tolerate them.
I am sure there are one or two (possible no longer maintained) libraries out
there that ignorantly write them out. 2 years ago agsxmpp did (qualified with a
Waqas Hussain wrote:
> On Thu, Nov 6, 2008 at 4:00 PM, Jonathan Dickinson
> <[EMAIL PROTECTED]> wrote:
>>
>> What's the official stance on BOM (Byte order marks)? I have had to
>> specifically remove them because most client (e.g. Cocinnella) sporadically
>> break if they are there (strangely, firs
On Thu, Nov 6, 2008 at 4:00 PM, Jonathan Dickinson
<[EMAIL PROTECTED]> wrote:
> Hi All,
>
>
>
> What's the official stance on BOM (Byte order marks)? I have had to
> specifically remove them because most client (e.g. Cocinnella) sporadically
> break if they are there (strangely, first time you try
Hi All,
What's the official stance on BOM (Byte order marks)? I have had to
specifically remove them because most client (e.g. Cocinnella) sporadically
break if they are there (strangely, first time you try to log in, after that
it's fine).
The client says unexpected char "[]" (where the block
11 matches
Mail list logo