For searching the archives, marklogic.markmail.org will be pre-constrained to just messages on marklogic-related lists.
ian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stewart Shelline > Sent: Wednesday, August 27, 2008 3:30 PM > To: General Mark Logic Developer Discussion > Subject: RE: [MarkLogic Dev General] Quirks of generating > xhtml with xquery > > One way to handle the textarea problem is to use a namespace > convention like this: > > <html xmlns="http://www.w3.org/1999/xhtml";> > ... > <body xmlns=""> > ... > <textarea name="desc" cols="40" rows="3" > id="form-control" xmlns="http://www.w3.org/1999/xhtml";></textarea> > > As mentioned earlier today, the best way to get around > javascript problems is to put the javascript in a separate file. > > To search this mailing list, go to http://www.markmail.org. > You can constrain search results to just this list by > prefacing your keywords with list:marklogic in the search box. > > Stewart > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Eric Palmitesta > Sent: Wednesday, August 27, 2008 3:54 PM > To: ML Developer Mailing List > Subject: [MarkLogic Dev General] Quirks of generating xhtml > with xquery > > Aaron and I discussed this briefly at the training seminar, > but I'd like to get a sense of what other developers are > doing to get around the quirks of generating xhtml with > xquery (rather than a java servlet/jsp based website which > pulls records from MarkLogic via XDBC/XCC. > > One such quirk: Childless elements with no internal nodes and > an explicit closing tag are automatically folded into > elements with no closing tag. <div></div>, which is valid > xhtml, will become <div /> after being processed by MarkLogic > (breaks visual representation). Some better examples are > <script ...></script> and <textarea></textarea>, which are > expected to contain no internal nodes in xhtml. > > I've taken to writing things like > > <script ... >{" "}</script> > > or > > <textarea> </textarea> > > which successfully preserves the explicit closing tag, > keeping xhtml happy. Is there a more elegant way to do this? > > Are there other banana-peels I should watch out for when > generating xhtml with xquery? Is creating an entire website > by generating xhtml with xquery generally frowned upon, or > accepted? Admittedly, it seems less flexible than a <web > language>-based site, however the xdmp namespace seems to > provide sufficient functionality, and transforming xml data > into xhtml is incredibly easy with xquery. > > Cheers, > > Eric > > > PS > My vocabulary might be incorrect regarding words like 'tag' > and 'node', please correct me if necessary. > > PPS > I can see the archives at > http://xqzone.marklogic.com/pipermail/general/ > but are they searchable? I have a feeling newcomers such as > myself will be prone to asking questions which have already > been discussed at length. > _______________________________________________ > General mailing list > [email protected] > http://xqzone.com/mailman/listinfo/general > > ---------------------------------------------------------------------- > NOTICE: This email message is for the sole use of the > intended recipient(s) and may contain confidential and > privileged information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email > and destroy all copies of the original message. > _______________________________________________ > General mailing list > [email protected] > http://xqzone.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
