[Psi-devel] leading and trailing newlines and no linkification

Norman Rasmussen norman at rasmussen.co.za
Wed May 9 03:28:44 PDT 2007


On 5/9/07, Francisco Joaquín Rodríguez Prados <prados at gmail.com> wrote:
>
> On 08/05/07, Frederik Schwarzer <schwarzerf at gmail.com<schwarzerf at gmail.com>>
> wrote:
> >
> > Remaining question is, if this is considered as a bug in kopete (and
> > others)
> > and if there in any source to read about the specifications that define
> > these
> > things?
>
>
> More than a bug I think it is *their* solution to xhtml message creation.
> As far as I know, there's no place in the JEP where it is said how xhtml
> messages should be encapsulated (I mean, which tag is preferable for
> single/multiline messages).
>
> Maybe the logical option would be <span> tag for single-line messages, and
> multiple <p> tags for multiline. But that's not a convention, is a hack
> which would work for us (remember we render nick+first message line
> together). In any case, xhtml render in Psi now sucks because we are
> translating xhtml code to plain rich text - i.e. no flexible linespace and
> all.
>

Having a look at the examples in XEP-0071 it seems that:

   <p>Line 1</p><p>Line 2</p>

should be rendered as:

   Line 1

   Line 2

so I'd say there's nothing wrong with Psi's current implementation.

The XEP also mentions (8.9) that line breaks should be converted into
<br/>'s, so:

   <p>Line 1<br/>Line 2</p>

would be rendered as:

   Line 1
   Line 2

as the Frederik expected.

-- 
- Norman Rasmussen
- Email: norman at rasmussen.co.za
- Home page: http://norman.rasmussen.co.za/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.affinix.com/pipermail/psi-devel-affinix.com/attachments/20070509/5098fa52/attachment.htm 


More information about the psi-devel mailing list