Hi Maciek!

Maciek Niedzielski schrieb:
 <content:part type="text/html">
  <html xmlns="......">.....</html>
 </content:part>

Well this one would not work. HTML is based on SGML which cannot always directly included in XML.

You will either have to include it escaping the special characters:

<content:part type="text/html">
   &lt;html xmlns=".......">.....&lt;/html>
</content:part>

Or you have to restrict it to use XHTML (which is based on XML as you know):

<content:part type="application/xhtml+xml">
    <html xmlns="......">.....</html>
</content:part>

... and you would have to define (either implicit or explicit) which types are included directly and which have to be escaped.

Personally I prefere using XHTML instead of HTML. But if you are really XHTML (1.1) aware, you should also have no problems, that XHTML-IM has its own profile of XHTML.

Due to my feelings it is correct, that we limit the set of allowed elements. If a client has problems implementing this, it is caused because they are trying to use a UI widget, that is designed for HTML and not for XHTML.

But I am no client developper, so please let the other people discuss this topic ...


Matthias

--
Matthias Wimmer      Fon +49-700 77 00 77 70
Züricher Str. 243    Fax +49-89 95 89 91 56
81476 München        http://ma.tthias.eu/

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to