First, my apologies: I know that this has been discussed elsewhere, and
I know most of the pieces, but I can't seem to get the entire assembly
working. I'm thus appealing for help.
Here's my goal: I'm trying to author XHTML+XForms documents. I would
like to validate them and preferably have autocompletion. At this
stage, I'm not interested in custom XSD schemas in my XForms instances.
I followed the help here:
http://www.oxygenxml.com/pipermail/oxygen-user/2005-July/000518.htmlhttp://groups.yahoo.com/group/rng-users/message/432
...and I have XHTML 2 validation/completion working. I *thought* that
XHTML2 would give me XForms and XML Events. Alas, here's the xhtml2.rng
snippet:
<x:h2>XForms module</x:h2>
<x:p>To-Do: work out integration of XForms</x:p>
<!--include href="xforms-11.rng"/-->
So no dice. I then went on a day-long Google hunt, learning more about
namespace routing languages etc. than I could possibly have wanted to
know. I tried numerous iterations of numerous schemas for numerous specs.
Next, I reviewed the oXygen mailing list archives and forum and found this:
http://www.oxygenxml.com/forum/ftopic1769.html
However, the example there didn't work for me. Meaning, I could put
<xf:fake/> in my docs and it would still validate.
I'd really be interested to hear that someone got XForms plus any flavor
of XHTML working in oXygen. By working, I mean correct validation and
autocompletion. I don't particularly care if it is XHTML 1 or 2, RNG or
XSD or NRL, or what version of the spec is used.
If anybody has a tarball containing an example document and the pile of
schema docs it needed, I would be thrilled. All in all, either this
stuff is hard or I'm pretty dumb.
--Paul
>> Yes, it should, and it does why I test it with the html/chunk.xsl stylesheet. Are you using a customization layer with the chunking stylesheet? If so, you have to construct it carefully to get the import sequence right. If you don't, then you get a mix of chunked and non-chunked behavior, and I suspect that is what happened in your target.db file. See:
http://www.sagehill.net/docbookxsl/ChunkingCustomization.html
If you were following those guidelines, then something else is going on that will require more information. <<
Commented out all customizations; issues unchanged.
For some yet unknown reason when utilizing oXygen (eclipse plugin) on the Linux side, the extended characters €œ<text>€� to not appear surrounding the section text of <xreftext>, Windows side only; will resolve on the oXygen list. Using UTF-8 encoding.
The <i> tags persist at the chapter <xref> sections surrounding chapter text.
Also <span class="trademark"/> appears in the map within the <ttl> element (just began using the trademark element in a section element).
Lastly, when the aforementioned tags are deleted, the olinkdb.xml map validates on the Linux side and subsequent HTML transformations behave as expected. From the Windows side, validation complains “Invalid byte 1 of 1-byte UTF-8 sequence.” Again, this issue is probably best addressed on the oXygen list but any help would be appreciated.
Using docbook-rng-5.0b5, docbook-xsl-snapshot (4/30/06), oxygen-7.1.0 (eclipse-3.1.2 plugin), saxon-6.5.5
Ray
