AW: BXE validation problems
"Heintz Peter" <[email protected]> Mon, 26 Jul 2004 11:58:43 +0200
| Newsgroups | gmane.editors.bitflux.general |
|---|---|
| Message-ID | <6643227F60B238429EC9BC4E838A21A528C5C8@mucs0129.muc.knorr-bremse.com> |
Sorry send by mist. Here is the complete set of files -----Ursprüngliche Nachricht----- Von: Heintz Peter Gesendet: Montag, 26. Juli 2004 11:55 An: 'Christian Stocker' Cc: [email protected] Betreff: AW: [bx-editor-users] BXE validation problems Thanks for your quick response. This validation problem is gone some how but now I have got an other problem. I just tried to post it to the lenya user group but I received an mail delivery failure. My problem now. I can load my sample file in bxe without any message but the JavaScript Console lists the following error Error: startElement has no properties Source File: http://localhost...../releaNG.js Line: 300 Trying to save the document gives me the following message: Error: this.ownerDocument.vdom.firstChild has no properties Source File: http://localhost...../NodeVal.js Line 232 I am not having a CSS file so far so the content seem to be listed in default style. But I also wonder why I only can select the root element and no sub-elements in bxe. Here are my actual files. The first error I try the reproduce and to send you later. -----Ursprüngliche Nachricht----- Von: Christian Stocker [mailto:[email protected]] Gesendet: Montag, 26. Juli 2004 11:25 An: Heintz Peter Cc: [email protected] Betreff: Re: [bx-editor-users] BXE validation problems Hi Peter (your mail was in the "to be approved" queue...) On 22.7.2004 17:16 Uhr, Peter Heintz wrote: > I am trying to use bxe within lenya to edit a forrest document file. So I > converted the forrest DTD in RELAXNG. To get a root element I just created the > following additional RELAXNG file: > > <?xml version="1.0" encoding="UTF-8"?> > > <grammar xmlns="http://relaxng.org/ns/structure/1.0"> > <include href="document-v12.mod.rng"/> > > <start> > <ref name="document"/> > </start> > </grammar> Can you send me (or put online somewhere) all your relaxng-files and a sample xml document? It's hard to debug this way ;) thanks chregu > > Validation my example document with jing does not indicate a validation problem > but withing bxe I always get the message that header and body elements are not > allowed as child of the document root element. Any ideas are welcome. > > Versions: > BXE 0.9.5 > Lenya 1.2 > > > Thanks in advance! > Peter > -- christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich phone +41 1 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 http://www.bitflux.ch | [email protected] | gnupg-keyid 0x5CE1DECB This e-mail including any files attached is intended for the addressee only. It may contain trade secrets or undisclosed or otherwise confidential information. If you are not the intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Thank you for your cooperation -- bx-editor-users mailing list [email protected] http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-users
document-v12-mod.rng
(application/octet-stream, 27.6 KB) - not displayed
docdescription.rng
(application/octet-stream, 340 B) - not displayed
docdescription.xml
(text/xml, 8.7 KB)
<?xml version="1.0"?> <!-- edited with XMLSPY v2004 rel. 4 U (http://www.xmlspy.com) by XMLSPY 2004 Enterprise Ed. Release 4, Installed for 5 users (with SMP from 2003-10-28 to 2004-10-28) (Knorr Bremse Systeme für Schienenfahrzeuge GmbH) --> <document> <header> <title>The document-v1.2 DTD</title> <authors> <person name="Jeff Turner" email="[email protected]"/> </authors> <notice>This document doesn't make any sense at all.</notice> <abstract>A nonsense document using all possible elements in the current <code>document-v12.dtd</code>.</abstract> </header> <body> <section> <title>Sample Content</title> <p>This is a simple paragraph. Most documents contain a fair amount of paragraphs. Paragraphs are called <code><p></code>.</p> <p xml:space="preserve">With the <code><p xml:space="preserve"></code> attribute, you can declare that whitespace should be preserved, without implying it is in any other way special.</p> <p>A number of in-line elements are available in the DTD, we will show them inside an unordered list (<code><ul></code>):</p> <ul> <li>Here is a simple list item (<code><li></code>).</li> <li>Have you seen the use of the <code><code></code> element in the previous item?</li> <li>Also, we have <code><sub></code> and <code><sup></code> elements to show content <sup>above</sup> or <sub>below</sub> the text baseline.</li> <li>There is a facility to <em>emphasize</em> certain words using the <code><em></code> <strong> <code><strong></code> </strong> elements.</li> <li>We can use <icon height="22" width="26" src="images/icon.png" alt="feather"/> <code><icon></code>s, too.</li> <li>Another possibility is the <code><img></code> element: <img src="images/icon.png" alt="another feather" height="22" width="26"/>, which offers the ability to refer to an image map.</li> <li>We have elements for hyperlinking: <dl> <dt> <code><link href="faq.html"></code> </dt> <dd>Use this to <link href="faq.html" title="Example of a document via link">link</link> to another document. As per normal, this will open the new document in the same browser window.</dd> <dt> <code><link href="#section"></code> </dt> <dd>Use this to <link href="#section" title="Example of a document via local anchor">link</link> to the named anchor in the current document. </dd> <dt> <code><link href="faq.html#forrest"></code> </dt> <dd>Use this to <link href="faq.html#forrest" title="Example of a document via link and anchor">link</link> to another document and go to the named anchor. This will open the new document in the same browser window. </dd> <dt> <code><jump href="faq.html"></code> </dt> <dd>Use this to <jump href="faq.html" title="Example of a document via jump">jump</jump> to another document and optionally go to a named <jump href="faq.html#forrest" title="Example of a document via jump to anchor">anchor</jump> within that document. This will open the new document in the same browser window. So what is the difference between link and jump? The jump behaves differently, in that it will replace any frames in the current window. This is the equivalent of <code><a ... target="_top"></code> </dd> <dt> <code><fork href="faq.html"></code> </dt> <dd>Use this to <fork href="faq.html" title="Example of a document via fork">fork</fork> your webbrowser to another document. This will open the document in a new, unnamed browser window. This is the equivalent of <code><a ... target="_blank"></code> </dd> </dl> </li> <li>Oh, by the way, a definition list <code><dl></code> was used inside the previous list item. We could put another <ul> <li>unordered list</li> <li>inside the list item</li> </ul> <table> <caption>A sample nested table</caption> <tr> <td>Or even tables.. </td> <td> <table> <tr> <td>inside tables..</td> </tr> </table> </td> </tr> <tr> <td>or inside lists, but I believe this liberty gets quickly quite hairy as you see.</td> </tr> </table> </li> </ul> <p>So far for the in-line elements, let's look at some paragraph-level elements.</p> <fixme author="SN">The <code><fixme></code> element is used for stuff which still needs work. Mind the <code>author</code> attribute!</fixme> <note>Use the <code><note></code> element to draw attention to something, e.g. ...The <code><code></code> element is used when the author can't express himself clearly using normal sentences ;-)</note> <warning>Sleep deprivation can be the result of being involved in an open source project. (a.k.a. the <code><warning></code> element).</warning> <p>Apart from unordered lists, we have ordered lists too, of course.</p> <ol> <li>Item 1</li> <li>Item 2</li> <li>This should be 3 if my math is still OK.</li> </ol> <anchor id="section"/> <section> <title>Using sections</title> <p>You can use sections to put some structure in your document. For some strange historical reason, the section title is an attribute of the <code><section></code> element.</p> </section> <section> <title>Sections, the sequel</title> <p>Just some second section.</p> <section> <title>Section 2.1</title> <p>Which contains a subsection (2.1).</p> </section> </section> <anchor id="source"/> <section> <title>Showing preformatted source code</title> <p>Enough about these sections. Let's have a look at more interesting elements, <code><source></code> for instance:</p> <source>// This example is from the book _Java in a Nutshell_ by David Flanagan. // Written by David Flanagan. Copyright (c) 1996 O'Reilly & Associates. // You may study, use, modify, and distribute this example for any purpose. // This example is provided WITHOUT WARRANTY either expressed or implied. import java.applet.*; // Don't forget these import statements! import java.awt.*; public class FirstApplet extends Applet { // This method displays the applet. // The Graphics class is how you do all drawing in Java. public void paint(Graphics g) { g.drawString("Hello World", 25, 50); } }</source> <p>Please take care to still use a sensible line-length within your source elements.</p> </section> <section id="table"> <title>Using tables</title> <p>And now for a table:</p> <table> <caption>Table caption</caption> <tr> <th>heading cell</th> <th>heading cell</th> </tr> <tr> <td>data cell</td> <td>data cell</td> </tr> </table> <p>Not much of attributes with <code><table></code>, if you ask me.</p> </section> <anchor id="second-figure-anchor"/> <section id="figure"> <title>Using figures</title> <p>And a figure to end all of this.</p> <figure src="images/project-logo.gif" alt="project logo" width="220" height="65"/> </section> </section> <section> <title>Changes since <link href="site:document-v11">document-v11</link> </title> <p> doc-v12 enhances doc-v11 by relaxing various restrictions that were found to be unnecessary. </p> <ul> <li> Links ((link|jump|fork) and inline elements (br|img|icon|acronym) are allowed inside title. </li> <li> Paragraphs (p|source|note|warning|fixme), table and figure|anchor are allowed inside li. </li> <li> Paragraphs (p|source|note|warning|fixme), lists (ol|ul|dl), table, figure|anchor are allowed inside definition lists (dd) and tables (td and dh). </li> <li> Inline content (strong|em|code|sub|sup|br|img|icon|acronym|link|jump|fork) is allowed in strong and em. </li> </ul> </section> </body> <footer> <legal>© 2002 Apache Forrest</legal> </footer> </document>
docdescription2xhtml.xsl
(application/octet-stream, 653 B) - not displayed
document2html.xsl
(application/octet-stream, 9.9 KB) - not displayed