- oXygen-user - www.oxygenxml.com

XPath-validation in non-XSLT-files
by Theun Fleer 30 Oct '06

30 Oct '06

Hello, When editing XLST-files in oXygen7.2 on WinXP the XPath-expressions in the "select" and "match" attributes can be validated. When typing an incorrect XPath-expression, a wavy yellow line is shown, and an error description at the bottom of the screen; "content completion" is also an option. We are currently editing non-XSLT-files: a custom XML format with a custom namespace in which we must edit a lot of long XPath-expressions. We would like the same validation options as in the XLST-files... is this possible, and how? Kind regards, and keep up the good work! Theun Fleer Daidalos BV, The Netherlands Drs. T. Fleer Consultant GSM: +31 (0)6 40 58 50 27 Daidalos BV Source of Innovation Hoekeindsehof 1-4 2665 JZ Bleiswijk Tel.: +31 (0) 10 850 1200 Fax: +31 (0) 10 850 1199 www.daidalos.nl KvK 27164984 De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend.

2 1

Xerces command line parsing?
by Andrew Rouner 17 Oct '06

17 Oct '06

Hello, I am looking for the right syntax and method to be able to batch-parse XML files from the command line using Xerces. I need to use Xerces as I am attempting to replicate parsing using oXygen (which has Xerces as its default parser). If anyone can send along the syntax for doing this or can point me to a resource that can help, I'd very much appreciate it. I previously used xmllint/LIBXML to do command line parsing of my TEI files, which worked well for files calling on the TEI xlite DTD. I am now dealing with files that use the full TEI and must rely on the xml catalog, i.e.: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE TEI.2 PUBLIC "-//TEI P4//DTD Main Document Type//EN" "tei2.dtd" [ <!ENTITY % TEI.XML 'INCLUDE'> <!ENTITY % TEI.mixed 'INCLUDE'> <!ENTITY % TEI.drama 'INCLUDE'> <!ENTITY % TEI.corpus 'INCLUDE'> <!ENTITY % TEI.prose 'INCLUDE'> <!ENTITY % TEI.figures 'INCLUDE'> <!ENTITY % TEI.linking 'INCLUDE'> <!ENTITY % TEI.transcr 'INCLUDE'> <!ENTITY % TEI.names.dates 'INCLUDE'> <!ENTITY % TEI.spoken 'INCLUDE'> <!ENTITY % TEI.header 'INCLUDE'> <!ENTITY % ISOlat1 SYSTEM 'http://www.tei-c.org/Entity_Sets/Unicode/iso-lat1.ent'> %ISOlat1; <!ENTITY % ISOlat2 SYSTEM 'http://www.tei-c.org/Entity_Sets/Unicode/iso-lat2.ent'> %ISOlat2; <!ENTITY % ISOnum SYSTEM 'http://www.tei-c.org/Entity_Sets/Unicode/iso-num.ent'> %ISOnum; <!ENTITY % ISOpub SYSTEM 'http://www.tei-c.org/Entity_Sets/Unicode/iso-pub.ent'> %ISOpub; ]> I need to use Xerces, because I find that the default parser in oXygen (which is Xerces) can successfully parse these files (and LIBXML does not work for files using the full TEI due to problems with the DTD). My best understanding (which may be completely off) is that to use Xerces as an XML parser in the command line, what I am essentially doing, is using the syntax to run an XML file through an XSL stylesheet (on the assumption that the source file has to validate to run successfully. I have modified a previous stylesheet that processes all TEI elements found in these documents, and I use this syntax: java com.icl.saxon.StyleSheet -x org.apache.xerces.parsers.SAXParser source_file.xml stylesheet.xsl > /dev/null I am using Xerces as it comes with oXygen (and have not downloaded it separately). Since I am only really interested in parsing and not the output, I pipe it to /dev/null. I have the following in my bash profile for the PATH: CLASSPATH=$CLASSPATH:/Applications/oxygen/lib/saxon.jar:\ /Applications/oxygen/frameworks/docbook/xsl/extensions/saxon653.jar.ext:/App lications/oxygen/lib/xercesImpl.jar export CLASSPATH The above command WORKS, and will pick up SOME errors, but is clearly missing others. Does anyone have any more straightforward syntax for just PARSING with Xerces, or have any ideas why some errors (I have tested) are not being reported through this process? (One possibility is that it's just checking well-formedness, not validity, which I need to test further.) Thanks in advance for any help/suggestions. Andrew Andrew Rouner Digital Library Services Washington University Libraries St. Louis, MO EMAIL: arouner(a)wustl.edu > From: Oxygen XML Editor support <support(a)oxygenxml.com> > Date: Tue, 25 Jul 2006 12:47:23 +0300 > To: Andrew Rouner <arouner(a)wustl.edu> > Subject: Re: Differences in validators/ dtd problems? > > Dear Andrew Rouner, > > Thank you for contacting us. > The default parser used by oXygen is Xerces 2.8.0 (that is the latest > Xerces version). This looks at a first glance like a problem/bug in XMLLINT. > If you want to invoke Xerces to parse a document from command line then > you can do that though one of its sample applications: > http://xerces.apache.org/xerces2-j/samples.html > > Best Regards, > George > --------------------------------------------------------------------- > George Cristian Bina > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > > >

2 1

Problem with Oxygen on Kubuntu Dapper Dake
by Thomas Zastrow 10 Oct '06

10 Oct '06

Hi there, I can't install Oxygen 7.2 on Kubuntu Dapper Dake. There is a Java-installation and the variables JAVA_HOME and JAVA are pointing to it. After starting oxygen.sh I get the error: zastrow@schleppi:~/downloads/progs$ ./oxygen.sh Starting Installer ... java.lang.NoClassDefFoundError: javax.swing.JOptionPane at java.lang.Class.initializeClass(libgcj.so.7) at com.install4j.runtime.installer.Installer.reportExeption(Unknown Source) at com.install4j.runtime.installer.Installer.main(Unknown Source) at java.lang.reflect.Method.invoke(libgcj.so.7) at com.exe4j.runtime.LauncherEngine.launch(Unknown Source) at com.install4j.runtime.Launcher.main(Unknown Source) Best, Tom -- Thomas Zastrow Seminar fuer Sprachwissenschaft Universitaet Tuebingen http://www.sfs.uni-tuebingen.de/dialectometry/ Wilhelm Str. 19 D-72074 Tübingen Tel.: 07071/29-73968 Fax: 07071/29-5214

3 3

XML Schema validation broken in 7.2?
by Allison Bloodworth 10 Oct '06

10 Oct '06

Hi, Last week I upgraded (I think from Oxygen 7.1) to Oxygen 7.2 which is using Xerces 2.8.0 for schema validation. Suddenly XML instance documents that are definitely not valid are being called valid by Oxygen. I am using the red "checkmark" button for which the tool tip is "Validate Document". I am creating the files by opening a new document in Oxygen and attaching a schema that way. Documents with no content in the elements as well as documents that are just completely wrong are coming up as valid. When I validate using Xerces at the command line (java sax.Counter) I am getting the proper errors for these same documents. Additionally, I am getting the proper errors in Oxygen when I try to validate the schema itself. What could be going wrong? Allison Bloodworth Principal Administrative Analyst Technology Program Office University of California, Berkeley (415) 377-8243 abloodworth(a)berkeley.edu

2 1

RE: [oXygen-user] Macro to Strip Tags from DocBook Olink target.dbFile
by Miller, Ray (Centech) 10 Oct '06

10 Oct '06

>> I think the effect of surrounding the chapter title in an "i" element in the olink target file is intended, not a side effect as you can see in the template which generates it: <xsl:template match="chapter|appendix" mode="insert.title.markup"> <xsl:param name="purpose"/> <xsl:param name="xrefstyle"/> <xsl:param name="title"/> <xsl:choose> <xsl:when test="$purpose = 'xref'"> <i> <xsl:copy-of select="$title"/> </i> </xsl:when> <xsl:otherwise> <xsl:copy-of select="$title"/> </xsl:otherwise> </xsl:choose> </xsl:template> You can remove the <i> and </i> tags in a customization layer of the main DocBook stytlesheet which duplicates this template and modifies it by removing these tags. Apply the customization layer instead of the main DocBook stylesheet to remove the tags prior to transformations and perform the transformations at the same time (if collect.xref.targets is set to 'yes').<< I see that now. But the target database file will not validate against targetdatabase.dtd with the <i> tags. Is this a developer oversight or an error in my usage? Ray

2 1

Macro to Strip Tags from DocBook Olink target.db File
by Miller, Ray (Centech) 09 Oct '06

09 Oct '06

docbook-rng-5.0b8 xsl-1.71.0 saxon-6.5.5 oxygen-7.2.0 (eclipse-3.2 plugin) When generating an olink target data file (targetdb.xml), tags <i> and </i> surround each chapter's element text. Would like a macro to strip the aforementioned tags from targetdb.xml subsequent to pre-processing but prior to transformations, executing automatically each time a transformation is run on the project AND the stringparm collect.xref.targets is set to 'yes' or 'only'. Currently performing this activity utilizing find/replace (ugh). I believe a site-published solution (under Documentation/Articles) addressing the removal of unwanted tags and characters (along with the macro) from a DocBook target.db document will be of interest to other oXygen/DocBook users. Advise and comments please. Ray

2 1

using automatic character conversion in XML to XML transformation
by Dever, Paul (ELS) 09 Oct '06

09 Oct '06

If I transform my XML document to HTML using the HTML output method oXygen automatically turns special characters into HTML character entities (e.g., a copyright symbol gets transformed into "©"). I want to use that functionality in a transformation from XML to XML using XML as an output method, but I can't figure out how to do it. Is there a way? Thanks, --Paul ___________________________ Paul Dever :: Manager, Electronic Workflows :: EPD-US (T) +1 314-995-3291 :: (E) p.dever(a)elsevier.com <mailto:p.dever@elsevier.com> 11830 Westline Industrial Drive, St. Louis, MO 63146 ELSEVIER

2 1

New user: unicode editing
by Craig Ugoretz 23 Sep '06

23 Sep '06

Hello, I am new to oxygen and am very interested in its unicode functionality. Unfortunately, I have not been able to locate a dialog for entering, searching for, or replacing unicode characters like other unicode enabled editors I have reviewed. What do I need to do to access this functionality in oxygen? Sincerely, Craig

3 2

areaspec feature in docbook
by Achim Oehlenschlaeger 14 Sep '06

14 Sep '06

Hello, I'm using Oxygen 7.2 and want to use the areaspec feature to define linkable areas in a graphics object. I tried the example from http://www.docbook.org/tdg/en/html/mediaobjectco.html but don't get the desired result. I did read and follow the readme file in: ...\Oxygen XML Editor 7.2\frameworks\docbook\xsl\extensions I tried the Docbook transformation scenario as delivered with oxygen first, than I also added the DocBook extension to the scenario, than I switched to Xalan (I also switched the extension) but the result is always the same as shown below. Thanks, Achim Input: ------ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE mediaobjectco PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"> <mediaobjectco> <imageobjectco> <areaspec units="calspair"> <areaset id="oneway" coords=""> <area id="oneway1" coords="300 400"/> <area id="oneway2" coords="325 340"/> </areaset> <area id="myhouse" coords="425 590"/> </areaspec> <imageobject> <imagedata fileref="http://maps.example.com/EARTH?USA?MA?01007"/> </imageobject> </imageobjectco> </mediaobjectco> Output: ------- <html> <head> <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></title> <meta content="DocBook XSL Stylesheets V1.70.1" name="generator"> </head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <div class="mediaobjectco"> <img border="0" usemap="N10003" src="http://maps.example.com/EARTH?USA?MA?01007"> <map name="N10003"><area shape="rect" coords="NaN,NaN,NaN,NaN"> <area shape="rect" coords="NaN,NaN,NaN,NaN"> <area shape="rect" coords="NaN,NaN,NaN,NaN"> </map> </div> </body> </html>

2 1

\\machinename\username SAMBA shares
by Chris Chiasson 10 Sep '06

10 Sep '06

Hi, oXygen for Eclipse declines to transform any of my XML files on my SAMBA share. It works fine when I copy the entire workspace to my hard disk and then try it. I just recently moved my workspace to my SAMBA share so I could build with ant on Linux. The error came up when I was trying a manual transformation to diagnose an XEP problem... I am using the right click->transformation->configure transformation method. The error is: Configure Transformation Scenario Configure transformation skipped. Content type not handled for resource: Engineering_Optimization.xml -- http://chris.chiasson.name/

2 4