[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: | John Weiss <[EMAIL PROTECTED]> writes: > | | Consider, instead, the case where there's a separate tag in a | | "special-char" XML namespace. You still need to add the code to | | handle the "wynn", of course. However, your parse changes become | | trivial: the tag, "<special-char:wynn/>" needs no new code to parse | | it (since the DTD tells the XML parser how to do that). You just use | | your wynn-handling-code as your "action to take for the | | <special-char:wynn/> tag. Finally, you need to add | | "<special-char:wynn/>" as an optional tag in your DTD/XSchema. This | | has no impact on existing docs. > | How do you decalre a namespace in a DTD? > | I get a lot of > | UserGuide.lyx.xml:354: element eos: validity error : No declaration | for element | eos | Read <font emph="on">Extended Features</font><specialchar:eos/> | ^ | This is the DTD I hacked together, and it really shows how bad the | current xml format is.
New version of the DTD, missing namespace stuff... it works... kindo.
lyxformat.dtd
Description: Binary data
--
Lgb
