Re: [jdev] XHTML-IM XEP implementation
On Fri, Jan 05, 2007 at 12:35:05AM +0100, Bernhard Zwischenbrugger wrote: > Hi > > The depends on "character encoding" only, it hasn't much to do > with xmpp. In fact it does: http://www.xmpp.org/rfcs/rfc3920.html#xml-restrictions So the only predefined entities allowed are: > If you want to use you have to start the stream with > "us-ascii" (which is default encoding for html - xhtml has utf-8 as > default encoding): > > > xmlns:stream="http://etherx.jabber.org/streams"; > > > Jabber Servers maybe don't support it. They don't because the spec allows only UTF-8: http://www.xmpp.org/rfcs/rfc3920.html#xml-encoding /psa
Re: [jdev] XHTML-IM XEP implementation
Hi The depends on "character encoding" only, it hasn't much to do with xmpp. It's the same with ü for ü ö for ö ... If you want to use you have to start the stream with "us-ascii" (which is default encoding for html - xhtml has utf-8 as default encoding): http://etherx.jabber.org/streams"; > Jabber Servers maybe don't support it. Since windows 95 we have unicode (utf-8) it makes no sense to go back to old us-ascii, iso-8859-x, EBCDIC, BCD,... Bernhard Am Donnerstag, den 04.01.2007, 22:35 +0200 schrieb Norman Rasmussen: > What about just making whitespace significant in the xmpp spec? > > i.e. most client will want to replace space with nbsp before > displaying to the user, or maybe you can set a flag on the html > renderer > > On 12/15/06, Bernhard Zwischenbrugger <[EMAIL PROTECTED]> wrote: > > Depends on encoding > > is encoding="us-ascii" > > > Is it possible to use ? > > > > > > > > UTF-8 does not allow > > use > > > > Bernhard > > > > > >
Re: [jdev] XHTML-IM XEP implementation
Justin Karneges wrote: On Thursday 04 January 2007 1:04 pm, Maciek Niedzielski wrote: Norman Rasmussen wrote: Whitespace is significant in the element, no? True, so we need to remind client developers that it's significant in the html node too, and that it's the job of the _receiving_ client to ensure that the whitespace is preserved (not the sending client) Just a question I always wanted to ask: Is it possible for a server to rewrite a stanza (and break the whitespaces)? Whitespace is always significant. That's XML. If a server rewrites XML, the whitespace must still be there. As for XHTML, whitespace significance really depends on how XHTML is supposed to work. Yes, the whitespace is there, since XHTML is XML, but what is the meaning of the whitespace to an XHTML renderer? I don't believe this is ours to decide. If XHTML is just like HTML, where any length of whitespace simplifies down to one character for presentation, then we should probably respect this in XHTML-IM. http://www.xmpp.org/extensions/xep-0071.html#w3c-conformance Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.shtml smime.p7s Description: S/MIME Cryptographic Signature
Re: [jdev] XHTML-IM XEP implementation
On Thursday 04 January 2007 1:04 pm, Maciek Niedzielski wrote: > Norman Rasmussen wrote: > >> Whitespace is significant in the element, no? > > > > True, so we need to remind client developers that it's significant in > > the html node too, and that it's the job of the _receiving_ client to > > ensure that the whitespace is preserved (not the sending client) > > Just a question I always wanted to ask: Is it possible for a server to > rewrite a stanza (and break the whitespaces)? Whitespace is always significant. That's XML. If a server rewrites XML, the whitespace must still be there. As for XHTML, whitespace significance really depends on how XHTML is supposed to work. Yes, the whitespace is there, since XHTML is XML, but what is the meaning of the whitespace to an XHTML renderer? I don't believe this is ours to decide. If XHTML is just like HTML, where any length of whitespace simplifies down to one character for presentation, then we should probably respect this in XHTML-IM. -Justin
Re: [jdev] XHTML-IM XEP implementation
gosh I hope not. On 1/4/07, Maciek Niedzielski <[EMAIL PROTECTED]> wrote: Norman Rasmussen wrote: >> Whitespace is significant in the element, no? > True, so we need to remind client developers that it's significant in > the html node too, and that it's the job of the _receiving_ client to > ensure that the whitespace is preserved (not the sending client) Just a question I always wanted to ask: Is it possible for a server to rewrite a stanza (and break the whitespaces)? -- Maciek A: It's against natural order of reading. xmpp:[EMAIL PROTECTED] Q: Why is that? xmpp:[EMAIL PROTECTED] A: People answering above quoted text. Q: What's the most annoying on newsgroups? -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
Re: [jdev] XHTML-IM XEP implementation
Norman Rasmussen wrote: >> Whitespace is significant in the element, no? > True, so we need to remind client developers that it's significant in > the html node too, and that it's the job of the _receiving_ client to > ensure that the whitespace is preserved (not the sending client) Just a question I always wanted to ask: Is it possible for a server to rewrite a stanza (and break the whitespaces)? -- Maciek A: It's against natural order of reading. xmpp:[EMAIL PROTECTED] Q: Why is that? xmpp:[EMAIL PROTECTED] A: People answering above quoted text. Q: What's the most annoying on newsgroups? signature.asc Description: OpenPGP digital signature
Re: [jdev] XHTML-IM XEP implementation
True, so we need to remind client developers that it's significant in the html node too, and that it's the job of the _receiving_ client to ensure that the whitespace is preserved (not the sending client) By making it a receiving job, we keep the bandwidth down :-) On 1/4/07, Peter Saint-Andre <[EMAIL PROTECTED]> wrote: Whitespace is significant in the element, no? Norman Rasmussen wrote: > What about just making whitespace significant in the xmpp spec? > > i.e. most client will want to replace space with nbsp before > displaying to the user, or maybe you can set a flag on the html > renderer > > On 12/15/06, Bernhard Zwischenbrugger <[EMAIL PROTECTED]> wrote: >> Depends on encoding >> is encoding="us-ascii" >> > Is it possible to use ? >> > >> > >> UTF-8 does not allow >> use >> >> Bernhard >> >> -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
Re: [jdev] XHTML-IM XEP implementation
Whitespace is significant in the element, no? Norman Rasmussen wrote: What about just making whitespace significant in the xmpp spec? i.e. most client will want to replace space with nbsp before displaying to the user, or maybe you can set a flag on the html renderer On 12/15/06, Bernhard Zwischenbrugger <[EMAIL PROTECTED]> wrote: Depends on encoding is encoding="us-ascii" > Is it possible to use ? > > UTF-8 does not allow use Bernhard smime.p7s Description: S/MIME Cryptographic Signature
Re: [jdev] XHTML-IM XEP implementation
What about just making whitespace significant in the xmpp spec? i.e. most client will want to replace space with nbsp before displaying to the user, or maybe you can set a flag on the html renderer On 12/15/06, Bernhard Zwischenbrugger <[EMAIL PROTECTED]> wrote: Depends on encoding is encoding="us-ascii" > Is it possible to use ? > > UTF-8 does not allow use Bernhard -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
Re: [jdev] XHTML-IM XEP implementation
Depends on encoding is encoding="us-ascii" > Is it possible to use ? > > UTF-8 does not allow use Bernhard
Re: [jdev] XHTML-IM XEP implementation
On 12/15/06, Tomasz Sterna <[EMAIL PROTECTED]> wrote: And last, but not least... HTML is squashing whitespace. So.. Bye bye indentation. All pasted code, tables etc. ends up completely unreadable. Is it possible to use ? -- Regards, Oleg
