Paul, here is what we do with XQDoc generation:

- from the module we generate a XQDoc XML
- from the XQDoc XML we generate XHTML

In the XQuery code of the module that generates the XQDoc XML I can not
state something like this:

fn:replace($XQDoc_content_as_string, " ", codepoints-to-
string(160))

because  " " is not a valid XML entity.

So, you are right, the bug should not be marked "Invalid", it should be
marked "Known limitation"/"Won't fix"

** Changed in: zorba
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/967284

Title:
  XQDoc doesn't understand  

Status in Zorba - The XQuery Processor:
  Won't Fix

Bug description:
  Given the following HTML as part of an XQDoc comment:

  <table>
    <tr><td>foo&nbsp;bar</td></tr>
  </table>

  one gets the error:

  can not parse as XML for xqdoc: loader parsing error: Entity 'nbsp'
  not defined; raised at /Users/pjl/src/flwor/zorba/repo/feature-
  ft_module/zorba/src/compiler/parsetree/parsenode_print_xqdoc_visitor.cpp:433

  The parser needs to accept &nbsp; so a non-breaking space can be
  included in the HTML.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zorba/+bug/967284/+subscriptions

-- 
Mailing list: https://launchpad.net/~zorba-coders
Post to     : zorba-coders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zorba-coders
More help   : https://help.launchpad.net/ListHelp

Reply via email to