- oXygen-user - www.oxygenxml.com

ro.sync.ecss.extensions.docbook.table.InsertTableOperation in Web Author
by Jirka Kosek 23 Oct '18

23 Oct '18

Hi, I'm creating DocBook customization for work in Web Author. Customized schema allows only informatables in HTML syntax. I have modified original insert.table action from DocBook framework in the following way: Activation XPath: oxy:allows-child-element("*:informaltable") Default table model: html This works fine in standalone Author, but user has to untick "Title" in order to insert informaltable instead of table with title. However when I deploy the same framework to Web Author insert.table action is not doing anything. If I try to invoke it in the wrong location I'm getting proper warning "The action ... is not available in the current location". But when I position caret to proper location and press table button nothing happens. Are there any Web Author limitations for ro.sync.ecss.extensions.docbook.table.InsertTableOperation operation that are causing this behaviour? Before I customized activation XPath and default table model button was invoking table creation dialog. But now nothing happens. Also it would be nice if ro.sync.ecss.extensions.docbook.table.InsertTableOperation would have more parameters that would allow customization of table insert dialog, e.g. - checking/unchecking title - disabling some table models (CALS, HTML) - disabling title - providing default row/column count - providing default frame options Many thanks in advance, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML and Web consulting and training services DocBook/DITA customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------

3 4

Dragging PDF images into a DITA topic: use image element instead of xref?
by Yves Barbion 22 Oct '18

22 Oct '18

Hi group I have my images (vector graphics) in PDF format. When I select an image in Windows Explorer and drag it into a DITA topic, I see that an xref to this pdf file is created, as shown in the example below: <xref href="Graphics/ce.pdf" format="pdf"/> Instead, I want to have an image element like this: <image href="Graphics/ce.pdf" id="image_b3d_gwd_nfb"/> This is oXygen's behaviour when I drag other graphic file formats (for example EPS, JPG, PNG) into my editor. Is there also a way to do this with images in PDF format? Thanks Yves

2 1

Validation faulty
by Bernhard Kleine 19 Oct '18

19 Oct '18

I have some tables. While validation works for one with a similar construct, the other table appears faulty This works: <simplesect> <title/> <table> <title>Rote Liste</title> <tgroup cols="4" align="center"> ... and this does not work: <para>Mit den eigentlichen Bläulingen (Bl) wird die Sache schwieriger. <table frame="void"> <title>Bläuling noch nicht fotografiert</title> <?dbfo keep-together="always" ?> <tgroup cols="4" align="left"> <colspec colname="c1" colnum="1" colwidth="109.2pt"/> ... can you please explain. I have this error regularily that a table should have a caption and not a title. Cheers Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

2 2

Version of Saxon used for Schematron validation in Web Author
by Jirka Kosek 17 Oct '18

17 Oct '18

Hi, I'm trying to use Schematron for additional validation in Web Author. My Schematron uses functions supported only in Saxon-PE/EE, namely file:exists(). This works in a standalone Author, but in a Web Author I'm getting the following error message: Errors were reported during stylesheet compilation Cannot find a 1-argument function named {http://expath.org/ns/file}exists() This suggests that Web Author is using Saxon-HE that is not supporting such extension functions. Could this be changed somewhere in Web Author configuration? Many thanks in advance, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML and Web consulting and training services DocBook/DITA customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------

2 1

[Ann] New Oxygen XML DITA publishing webinar "Creating Custom Publishing Templates for WebHelp and PDF Output"
by Radu Coravu 17 Oct '18

17 Oct '18

Hi everyone, Next week on Wednesday, October 24, 2018 at 11:00 AM US Eastern time we are hosting a new webinar called "Creating Custom Publishing Templates for WebHelp and PDF Output". The webinar will provide an in-depth look at Oxygen's Publishing Templates feature used in certain DITA transformations, how to create your own custom templates, and specific use-cases for customizing various aspects of the DITA-based WebHelp and PDF output. You can register for free at: https://www.oxygenxml.com/events/2018/webinar_creating_custom_publishing_te… Regards, Radu Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com

1 0

Keyboard shortcuts in Web Author
by Jirka Kosek 16 Oct '18

16 Oct '18

Hi, for desktop oXygen it's easy to create actions in framework and assign them to keyboard shortcuts. Is this possible for Web Author as well? I've read documentation but I haven't noticed such possibility. Many thanks in advance, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML and Web consulting and training services DocBook/DITA customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------

2 3

Differences in CSS counters between Author and Web Author
by Jirka Kosek 15 Oct '18

15 Oct '18

Hi, I'm creating customized CSS stylesheet for DocBook based vocabulary. In Author I need to prepend Figure X.Y label before each figure title. Where X is chapter number and Y is number of figure inside chapter. I'm doing this by providing additional styleheet in framework that is extending DocBook framework: figure > title:before { content: "Figure " counter(chapter_count) "." counter(figure) " "; } figure { counter-increment: figure; } chapter > title:before { counter-reset: figure sect1_count; } This works as expected in desktop Author. However in Web Author figure number is being reset for each section, so for example for document like <chapter> ... <section> ... <figure>  ... </section> <section> ... <figure>  ... </section> </chapter> Web Author labels both figures as 1.1. I have briefly looked into HTML/CSS code of Web Author and it seems that you are somehow preprocessing Author CSS stylesheet for browser and this particular case is not handled properly. I suppose there is no easy workaround for this, but perhaps next version of Web Author could fix this ;-) Many thanks and have a nice day, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML and Web consulting and training services DocBook/DITA customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------

2 2

Location of XSpec framework
by Christophe Marchand 12 Oct '18

12 Oct '18

Hello, I use oXygen 20.1, with XSpec add-on. I try to modify framework to test XSpec enhancements in oXygen. It seems the framework is at two different locations (I use a MacBook Pro) : * /Users/<me>/Library/Preferences/com.oxygenxml.developer/extensions/v20.1/frameworks/https___raw.githubusercontent.com_xspec_oXygen_XML_editor_xspec_support_master_build_update_site.xml/xspec.support-1.0.1 * /Applications/Oxygen XML Developer/frameworks/xspec Am I correct ? How do I know wich framework is used ? Best regards, Christophe

2 2

Error when transforming
by Bernhard Kleine 09 Oct '18

09 Oct '18

I can savely transform each chapter of my book, but when I try to transform the entire book, I encounter the following error: The process 'Apache FOP' ended with code: 1. The error was: ERROR - Exception org.apache.fop.apps.FOPException java.util.NoSuchElementException 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:186) at org.apache.fop.cli.Main.main(Main.java:217) Caused by: java.util.NoSuchElementException at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:69) at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:27) at org.apache.fop.layoutmgr.AbstractLayoutManager.setCurrentChildLM(AbstractLayoutManager.java:132) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:275) at org.apache.fop.layoutmgr.list.ListItemContentLayoutManager.getNextKnuthElements(ListItemContentLayoutManager.java:234) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:251) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:500) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:293) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:148) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:293) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:225) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:121) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:269) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:787) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:451) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:141) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at net.sf.saxon.event.ContentHandlerProxy.endElement(Unknown Source) at net.sf.saxon.event.NamespaceReducer.endElement(NamespaceReducer.java:228) at net.sf.saxon.event.ComplexContentOutputter.endElement(ComplexContentOutputter.java:578) at net.sf.saxon.event.ReceivingContentHandler.endElement(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImplXerces.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.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:427) at net.sf.saxon.event.Sender.send(Sender.java:138) at net.sf.saxon.jaxp.IdentityTransformer.transform(IdentityTransformer.java:383) ... 4 more --------- java.util.NoSuchElementException at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:69) at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:27) at org.apache.fop.layoutmgr.AbstractLayoutManager.setCurrentChildLM(AbstractLayoutManager.java:132) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:275) at org.apache.fop.layoutmgr.list.ListItemContentLayoutManager.getNextKnuthElements(ListItemContentLayoutManager.java:234) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:251) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:500) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:293) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:148) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:293) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:225) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:121) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:269) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:787) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:451) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:141) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at net.sf.saxon.event.ContentHandlerProxy.endElement(Unknown Source) at net.sf.saxon.event.NamespaceReducer.endElement(NamespaceReducer.java:228) at net.sf.saxon.event.ComplexContentOutputter.endElement(ComplexContentOutputter.java:578) at net.sf.saxon.event.ReceivingContentHandler.endElement(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImplXerces.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.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:427) at net.sf.saxon.event.Sender.send(Sender.java:138) at net.sf.saxon.jaxp.IdentityTransformer.transform(IdentityTransformer.java:383) 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:186) at org.apache.fop.cli.Main.main(Main.java:217) I have already increased the size of memory to be used. I donot see where the error occurs. Please point me to the source of the trouble. Thanks a lot Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

3 6

[Ann] Explore XSpec for unit testing XSLT and Schematron in a new Oxygen XML webinar!
by Oxygen XML Editor Support (Radu Coravu) 04 Oct '18

04 Oct '18

Hi everybody, We, the Oxygen XML Editor team, are happy to invite you to join us for a new highly requested webinar, called "XSpec Unit Testing for XSLT and Schematron". The event will be hosted on October 10, 2018 at 11:00 AM US Eastern time. This is an opportunity for you to learn about the XSpec framework and how you can use it to write unit tests for XSLT and Schematron. This webinar is presented by Alex Jitianu, one of Oxygen's chief software engineers. The main topics that will be covered during the webinar are: * A presentation of the Test Driven Development (TDD) concept and an overview of the XSpec unit testing framework * How to create and execute XSpec scenarios in Oxygen to test XSLT scripts and Schematron schemas * An Oxygen plugin designed to improve the default XSpec support and speed up XSpec test scenario development You can register for free at: https://www.oxygenxml.com/events/2018/webinar_xspec_unit_testing_for_xslt_a… Even if you cannot attend, by registering, you will receive an email with a link to the recording of the event. This is the second webinar of a series of webinars that the Oxygen team will continue to present in the coming months. The first webinar was presented on September 26 and it provided an exploration of the new collaboration product, Oxygen Content Fusion. This product will dramatically increase the efficiency and quality of the review process of any documentation team. A recording of this event is available at: https://www.oxygenxml.com/events/2018/webinar_exploring_oxygen_content_fusi… Here is the full list of the other upcoming webinars: Oct. 24, 11 AM ET - Creating Custom Publishing Templates for WebHelp and PDF Output https://www.oxygenxml.com/events/2018/webinar_creating_custom_publishing_te… Nov. 7, 11 AM ET - Creating Oxygen Frameworks https://www.oxygenxml.com/events/2018/webinar_creating_oxygen_frameworks.ht… Nov. 28, 11 AM ET - Getting Started with Creating Schematron Rules and Schematron Quick Fixes https://www.oxygenxml.com/events/2018/webinar_creating_schematron_rules_and… Dec. 5, 11 AM ET - Simple DITA Project Setup https://www.oxygenxml.com/events/2018/webinar_simple_dita_project_setup.html Dec. 12, 11 AM ET - Oxygen XML Editor Productivity Tips and Tricks https://www.oxygenxml.com/events/2018/webinar_oxygen_productivity_tips_and_… Hope to see you soon! Oxygen Team http://www.oxygenxml.com

1 0