- oXygen-user - www.oxygenxml.com

HTML5 transformation
by Peter West 05 Aug '14

05 Aug '14

I'm transforming EPUB2 files to xhtml5 for EPUB3. Here's the beginning of one of the EPUB2 files. <?xml version='1.0' encoding='utf-8'?> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Personal Knowledge: Towards a Post-Critical Philosophy</title> <meta content="http://www.w3.org/1999/xhtml; charset=utf-8" http-equiv="Content-Type" /> ... </head> My xsl file has, inter alia, this: <xsl:output method="xhtml" html-version="5"/> When I do the transform, I get html5 output, including the meta element, like so: <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>Personal Knowledge: Towards a Post-Critical Philosophy</title> ... </head> Oxygen and Jing do not like http-equiv="Content-Type" Uh-uh, no way. They want Default-Style or Refresh, and nothing else will do. I went through every contortion I could think of to recast teh meta element, to no avail. I could generate a second meta element, but I could not get rid of the original meta. I was as though that meta was hard coded into the html5 transformer. So I have two questions. Is it possible to circumvent the copy of the existing head subelements, including meta? Why is the xslt so stubborn about http-equiv="Content-Type", when the validation rejects it for html5? Peter West "...the kingdom of heaven is like a merchant in search of fine pearls, who, finding one pearl of great value, sold all that he had and bought it." Peter West "...the kingdom of heaven is like a merchant in search of fine pearls, who, finding one pearl of great value, sold all that he had and bought it."

2 1

OSX: Using Java 7 With Oxygen
by Eliot Kimber 04 Aug '14

04 Aug '14

I have just updated my OS X system to Java 7. I get Java 7 as the java version from the command line: contrext01:DITA-OT ekimber$ java -version java version "1.7.0_65" Java(TM) SE Runtime Environment (build 1.7.0_65-b17) Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode) And I was able to configure Eclipse to use the Java 7 runtime. However, Oxygen is still using the Java 6 JRE and I can't see how to change it. The instructions in the help that specify using the Java Preferences utility are out of date as that utility is no longer provided by Apple and the Oracle Java preferences doesn't show anything except the Java 7 runtime. If I look at the system properties in the About Oxygen all the java-related properties reflect Java 6, not Java 7, but I don't see any place that these are actually being set (not in my .bashrc, not in the Oxygen app plist files). What do I do to get Oxygen to use the 1.7 JRE? Thanks, E. ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

4 4

XSLT keys in the outline view
by Wendell Piez 25 Jul '14

25 Jul '14

Hi, I can't remember why key declarations are not included in the XSLT outline view, and in any case wonder whether this could not be revisited. What was the reason again? Cheers, Wendell -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

2 2

hashtag on docbook 5 fop-PDF output -- why?
by Robert Nagle 24 Jul '14

24 Jul '14

HI, there, I am helping a client use Oxygen to produce a PDF of my Docbook 5 project. (In case you are wondering, this is NOT the same client I asked about last week --- but a different one from two years ago!) The docbook 5 project is valid. When I run the out-of-the-box Docbook 5 PDF (with FOP), I can generate the project on my machine. But my client generates a file successfully (with no errors or messages) with the latest XML Editor -- except it's nothing but # characters.... I seem to remember having encountered the same error before, but I don't remember what I did with it. Both of us have Win 7 64 bit versions. I Have Author 16 while my client has Editor 16 which was just installed today. We have made no customizations yet to the transformation. I'm guessing it's an encoding error, but I'm not sure where to go fix it (or why a clean Editor install with a general Docbook 5-fop-pdf would give that kind of message). Do you have any ideas? On another note, I want to thank Sorin for helping me with my problem last week. Robert -- Robert Nagle 6121 Winsome Ln #56C, Houston TX 77057-5581 (H) 713 893 3424/ (W) 832-251-7522 Carbon Neutral Since Jan 2010 http://www.robertnagle.info

2 1

advantages of using Eclipse plugin?
by Tom Johnson 23 Jul '14

23 Jul '14

I'm curious to know what the advantages are for using the Oxygen plugin for Eclipse instead of the standalone version of Oxygen? I'm not doing any deep development work, which might be where the advantages are. I see that, using the Oxygen plugin, you can transform content into Eclipse Help, but otherwise, I am not sure why I would want to use Oxygen inside of Eclipse. Tom --------------------- 801-822-2241 blog: idratherbewriting.com twitter: tomjohnson

2 1

how to make processing instructions work with an Oxygen Docbook transform?
by Robert Nagle 17 Jul '14

17 Jul '14

Hi, there, (I'm on the latest version of Oxygen Author, using FOP PDF transform). I'd like to use a Dcobook processing instruction for page breaks on PDF -- as mentioned in Bob's book. http://www.sagehill.net/docbookxsl/PageBreaking.html#HardPageBreaks I'd like to use one of the Oxygen transforms for Docbook. What are my options here? I see that in the transform dialog you have an "Additional XSLT stylesheet" option on the XSLT tab. Can I use that? I created a file pi-docbook.xsl which is just this: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo=" http://www.w3.org/1999/XSL/Format" xmlns:d="http://docbook.org/ns/docbook" exclude-result-prefixes="d" xmlns="http://www.w3.org/1999/xhtml" version="1.0"> <xsl:template match="processing-instruction('hard-pagebreak')"> <fo:block break-after='page'/> </xsl:template> </xsl:stylesheet> If I add this simple XSL file to use as an additional XSLT stylesheet (in the Edit Scenario dialog--> XSLT tab), it gave me an error. (See below). It seems to give me some prolog errors. I have used processing instructions successfully if I download my own Docbook XSLT and transform my project using a customization layer (which then imports the docbook files). I know how to do that. But I'm working for a client and would like to give them something easy which they can do entirely with the Oxygen transforms. Do you have any ideas about how to do PIs? or do you know why I get this error message? thanks. The process 'Apache FOP' ended with code: 1. The error was: ERROR - Exception org.apache.fop.apps.FOPException: org.xml.sax.SAXParseException; systemId: file:/C:/Users/kingrobert/Documents/Dropbox/job/source/index.xml_xslt; lineNumber: 1; columnNumber: 39; Content is not allowed in prolog. net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException; systemId: file:/C:/Users/kingrobert/Documents/Dropbox/job/source/index.xml_xslt; lineNumber: 1; columnNumber: 39; Content is not allowed in prolog. at org.apache.fop.cli.InputHandlerFOP.transformTo(Unknown Source) at org.apache.fop.cli.InputHandlerFOP.renderTo(Unknown Source) at org.apache.fop.cli.Main.startFOP(Main.java:177) at org.apache.fop.cli.Main.main(Main.java:208) Caused by: net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException; systemId: file:/C:/Users/kingrobert/Documents/Dropbox/job/source/index.xml_xslt; lineNumber: 1; columnNumber: 39; Content is not allowed in prolog. at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:420) at net.sf.saxon.event.Sender.send(Sender.java:143) at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:46) ... 4 more Caused by: org.xml.sax.SAXParseException; systemId: file:/C:/Users/kingrobert/Documents/Dropbox/job/source/index.xml_xslt; lineNumber: 1; columnNumber: 39; Content is not allowed in prolog. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScannerXerces.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:396) ... 6 more --------- net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException; systemId: file:/C:/Users/kingrobert/Documents/Dropbox/job/source/index.xml_xslt; lineNumber: 1; columnNumber: 39; Content is not allowed in prolog. at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:420) at net.sf.saxon.event.Sender.send(Sender.java:143) at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:46) at org.apache.fop.cli.InputHandlerFOP.transformTo(Unknown Source) at org.apache.fop.cli.InputHandlerFOP.renderTo(Unknown Source) at org.apache.fop.cli.Main.startFOP(Main.java:177) at org.apache.fop.cli.Main.main(Main.java:208) Caused by: org.xml.sax.SAXParseException; systemId: file:/C:/Users/kingrobert/Documents/Dropbox/job/source/index.xml_xslt; lineNumber: 1; columnNumber: 39; Content is not allowed in prolog. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScannerXerces.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:396) ... 6 more --------- org.xml.sax.SAXParseException; systemId: file:/C:/Users/kingrobert/Documents/Dropbox/job/source/index.xml_xslt; lineNumber: 1; columnNumber: 39; Content is not allowed in prolog. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScannerXerces.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:396) at net.sf.saxon.event.Sender.send(Sender.java:143) at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:46) at org.apache.fop.cli.InputHandlerFOP.transformTo(Unknown Source) at org.apache.fop.cli.InputHandlerFOP.renderTo(Unknown Source) at org.apache.fop.cli.Main.startFOP(Main.java:177) at org.apache.fop.cli.Main.main(Main.java:208) -- Robert Nagle 6121 Winsome Ln #56C, Houston TX 77057-5581 (H) 713 893 3424/ (W) 832-251-7522 Carbon Neutral Since Jan 2010 http://www.robertnagle.info

2 1

SVN client version
by Tom Cleghorn 16 Jul '14

16 Jul '14

Hi, We've run into a situation where some users have Subversion 1.8 working copies made by TortoiseSVN, but would like to be able to use SyncroSVN alongside it and/or instead of it, but the version bundled with Oxygen seems to still be pre-1.8, and the latest TortoiseSVN version appears to only work with 1.8 working copies. Is there any way round this other than checking out a new working copy? Perhaps it's possible to upgrade the bundled version of SyncroSVN? As an alternative, does an Oxygen Editor licence key work with the standalone version of SyncroSVN? Or is 1.8 support in the bundled version planned soon? Many thanks!

2 1

[Ann] New maintenance build available for oXygen 16.0 (2014060420)
by Oxygen XML Editor Support (Adrian Buza) 11 Jul '14

11 Jul '14

Dear oXygen users, We announce the release of a new maintenance build (2014060420) for oXygen 16.0 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2014060420 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

4 3

[Ann] New maintenance build available for oXygen 16.0 (2014070913)
by Oxygen XML Editor Support (Adrian Buza) 10 Jul '14

10 Jul '14

Dear oXygen users, We announce the release of a new maintenance build (2014070913) for oXygen 16.0 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2014070913 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

shortcut key Ctrl+Shift+Space doesn't work in author-mode
by Madlik, Monika (LNG-VIE) 08 Jul '14

08 Jul '14

Hello, I just wanted to use the shortcut key Ctrl+Shift+Space within the author-mode of my Oxygen 15.2 version. But within the author-mode I don’t get any suggestions … This shortcut key works only when I’m in the text-mode. Is this an intended behavior of the author-mode? Best regards, Monika . . . . . . . . . . . . . . . . . . . . . . . . . . Ing. Monika Madlik Developer LexisNexis A-1030 Wien, Marxergasse 25 Monika.Madlik(a)lexisnexis.at<mailto:Monika.Madlik@lexisnexis.at> Tel.: +43 1 53452 1568 Fax.: +43 1 534 52 146 . . . . . . . . . . . . . . . . . . . . . . . . . .

2 1