dynamic xhtml with xquery

[Gary Lewis]

Michael got the diagnosis right (escaped markup) even though I didn't
have the words to describe the problem accurately.

Today I read Norman Walsh's 2003 article in xml.com on escaped markup.
My simple question to this mailing list suddenly looks like a can of
worms. And a google search of the topic turned up many other
discussions of the problem.

Yikes! Guess I'll let go of this problem temporarily.

If anyone knows of an "easy-read" on escaped markup suitable for an
xquery rookie, please let me know.

Thanks.
Gary Lewis

On Fri, Jul 10, 2009 at 2:15 PM, Michael Kay<http://x-query.com/mailman/listinfo/talk> wrote:
> If your input contains escaped markup that you want to treat as markup then
> you have to unescape it. The easiest way to do that is to put it through an
> XML parser. Unfortunately there's no standard XQuery function to do that.
> Saxon has saxon:parse(), other products may have similar extensions, or you
> may be able to write your own.
>
> A better solution is to persuade people not to escape their markup...
>
> Regards,
>
> Michael Kay
> http://www.saxonica.com/
> http://twitter.com/michaelhkay
>
>
>
>> -----Original Message-----
>> From: http://x-query.com/mailman/listinfo/talk
>> [mailto:http://x-query.com/mailman/listinfo/talk] On Behalf Of Gary Lewis
>> Sent: 10 July 2009 17:52
>> To: http://x-query.com/mailman/listinfo/talk
>> Subject:  dynamic xhtml with xquery
>>
>> I'm stuck on a problem that must occur frequently, yet lots
>> of reading, google searches, and xquery experimentation have
>> not yet provided a solution. I'm writing in hopes that
>> someone can point me to an faq or similar info.
>>
>> Here's the situation. I'd like to use xquery to write dynamic
>> xhtml (ie, to write xhtml on-the-fly that can be viewed in a
>> browser without additional editing).
>>
>> I started with a small project involving rss, using zorba's
>> xquery REST functionality and GET to access the rss (returned
>> as xml). I then wrote an xquery to serialize the xml and
>> return xhtml. No problems when displayed in a browser
>> (Firefox) ... except for special characters. As you'd expect,
>> the GET returns angle brackets as &lt; and &gt; and since the
>> rss contains many href links there are many of these &lt; and
>> &gt; substitutions. The browser renders them correctly as >
>> and < but, naturally, the resulting href is seen as text and
>> not as a link.
>>
>> I've tried lots of different possible solutions, all of which
>> I realize now were silly although useful for learning what not to do.
>>
>> Any help would be much appreciated.
>>
>> Thanks.
>>
>> Gary Lewis
>> _______________________________________________
>> http://x-query.com/mailman/listinfo/talk
>> http://x-query.com/mailman/listinfo/talk
>
>