- oXygen-user - www.oxygenxml.com

Buffer-related questions (when opened from plugin)
by Florent Georges 15 Jun '12

15 Jun '12

Hi, When opening a buffer from within a plugin (using Workspace.open()), is there any way to 1/ attach a specific value to the buffer (kind of a buffer-scoped variable, in my case just a boolean flag) and 2/ to specify a method to be called before closing the buffer (kind of a buffer listener, so I can do some treatment before closing it)? Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

2 5

Plugin needs a system property to be configured
by Florent Georges 14 Jun '12

14 Jun '12

Hi, I am writing a plugin for oXygen. As part of that plugin, I use a third-party library that needs a system property to be set. For now, I added it to oxygen13.2.vmoptions, but this is really not user-friendly (wrt to installation). The other option I can think of is to set the property from within Java during plugin instantiation (the class extending Plugin), but I am not sure oXygen ensures this is called before everything else in the plugin. What is the idiomatic way to set a system property (especially as part of a plugin)? It would be nice to be able to set it in the plugin.xml actually. Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

2 2

Re: [oXygen-user] Syntax problem with xslt 'contains' text()
by G. Ken Holman 12 Jun '12

12 Jun '12

At 2012-06-12 18:44 +0100, McGibbney, Lewis John wrote: >In particular I wish to grab every occurrence of an <xs:element> >where the substitutionGroup value is equal to "ifc:IfcBuildingElement" > >I've been using the following xsl code and it is not working. > ><?xml version="1.0" encoding="UTF-8"?> ><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl" > xmlns:ifc="http://www.iai-tech.org/ifcXML/IFC2x3/FINAL" > exclude-result-prefixes="xs xd" > version="2.0"> > <xsl:output method="xml" omit-xml-declaration="yes" indent="yes"/> > <xsl:strip-space elements="*"/> > > <xsl:template name="main" match="/"> > <xsl:for-each select="xs:schema/xs:element"> > <xsl:if test="@substitutionGroup[contains(text(), > ifc:IfcBuildingElement)]"> Above you are asking to compare a text node with the child element named IfcBuildingElement in the namespace associated with the ifc prefix. Two problems: attribute nodes never contain text node children, and you are asking for the content of a child element rather than simple text. Do you not just want the following? <xsl:if test="contains(@substitution,'ifc:IfcBuildingElement')"> But up above you say "is equal to" so that means you could probably live with a simple string comparison (which does nothing about string normalization): <xsl:if test="@substitution='ifc:IfcBuildingElement'"> Note this does not accommodate namespsce prefix dereferencing ... you are just checking for a string. Which is what I think you are asking for. > <xsl:value-of select="xs:schema/xs:element"/> At this point you are addressing an xs:schema child of the previously selected xs:element, which is also wrong ... I suspect you don't want to walk away from the element you just tested. Do you want the element's name? You are asking for the string value of the element's descendants and I don't think you want that. That will always just be white space in the schema. Did you want to copy the element declarations? If so you could have: <xsl:copy-of select="xs:schema/ xs:element[@substitutionGroup='ifc:IfcBuildingElement']"/> >It would be great if someone could point out to me either the >incorrect syntax or the absence of the correct configuration. I hope this helps. If you could find some basic instruction on XPath nodes and node addressing, it would help you to understand where you went wrong. . . . . . . . . . Ken -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Oct 2012 Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/m/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal

1 0

Syntax problem with xslt 'contains' text()
by McGibbney, Lewis John 12 Jun '12

12 Jun '12

Good Afternoon Everyone, I have a large schema file [0]. I wish to grab a subset of the <xs:element>'s within the XSD and print them to a significantly smaller and more manageable/relevant output file. In particular I wish to grab every occurrence of an <xs:element> where the substitutionGroup value is equal to "ifc:IfcBuildingElement" I've been using the following xsl code and it is not working. <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl" xmlns:ifc="http://www.iai-tech.org/ifcXML/IFC2x3/FINAL" exclude-result-prefixes="xs xd" version="2.0"> <xsl:output method="xml" omit-xml-declaration="yes" indent="yes"/> <xsl:strip-space elements="*"/> <xsl:template name="main" match="/"> <xsl:for-each select="xs:schema/xs:element"> <xsl:if test="@substitutionGroup[contains(text(), ifc:IfcBuildingElement)]"> <xsl:value-of select="xs:schema/xs:element"/> </xsl:if> </xsl:for-each> </xsl:template> </xsl:stylesheet> It would be great if someone could point out to me either the incorrect syntax or the absence of the correct configuration. Kind Regards Lewis [0] http://www.buildingsmart-tech.org/ifcXML/IFC2x3/FINAL/IFC2X3.xsd Glasgow Caledonian University is a registered Scottish charity, number SC021474 Winner: Times Higher Education’s Widening Participation Initiative of the Year 2009 and Herald Society’s Education Initiative of the Year 2009. http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,6219,e… Winner: Times Higher Education’s Outstanding Support for Early Career Researchers of the Year 2010, GCU as a lead with Universities Scotland partners. http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,15691,…

1 0

Oxygen CSS parser appears to not understand @media queries
by Eliot Kimber 11 Jun '12

11 Jun '12

Please see http://www.w3.org/TR/css3-mediaqueries/ It looks like the CSS parser in 14.0, build 2012052416 doesn't understand this new feature of CSS. Is it possible to add it? Cheers, E. -- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/

2 6

null-warnings for schema
by Roderik Dernison 07 Jun '12

07 Jun '12

Hi, I made my "ling"-schema as an extension of the dita-schema. Now I'm getting warnings like: Description: Public: null System: file:/D:/oxygen-13.2/frameworks/dita/DITA-OT/schema/ling/xsd/lingDomain.xsd = null And: Description: Public: null System: file:/D:/oxygen-13.2/frameworks/dita/resources/dita-1.2-for-xslt2-mandatory.sch = null And when I add text to my topic the list of warnings grows. What can I have done wrong? Kind regards, Roderik Dernison ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ----------------------------------------------------------

2 1

[ann] [beta] oXygen XML Editor version 14 beta is available for testing
by George Cristian Bina 29 May '12

29 May '12

Dear oXygen users, We are happy to announce that version 14 of oXygen XML Editor is almost ready for release. Because the new version introduces many new features, we decided to release this beta version and thus have the chance to receive your early feedback before the final release. Some of these new features will be presented at the oXygen Users Meetup in Paris, June 11: http://www.oxygenxml.com/oXygen-user-meetup-Paris2012.html Please see below for: * oXygen 14 beta download information * a license key for testing * a summary of the most important additions/new features in version 14 = Download = You can download version 14 beta for your platform from http://www.oxygenxml.com/download-beta.html Please install this side by side with your current oXygen installation. = License key = License key for version 14 beta ------START-LICENSE-KEY------ Registration_Name=oxygen 14 beta user Company= Category=Enterprise Component=XML-Editor, XSLT-Debugger, Saxon-SA Version=14 Number_of_Licenses=1 Date=05-17-2012 Trial=31 SGN=MCwCFAkZnxOqlYndXSHLSIhrGOC0I2/+AhQ0tEWVN8L4ToTKODltVOhFh7BvPg\=\= -------END-LICENSE-KEY------- = Main additions/new features in version 14 = *General* *Support for plugin and framework repositories* *Updates on Transformation and Validation scenarios* *EPUB 3.0* *Development* *Master files* *XSLT Unit Test* *XSLT 3.0* *Improved support for MarkLogic* *CTRL/CMD + click navigation* *In-place rename* *XPath/XQuery builder* *Authoring* *Change tracking and comment callouts* *Improved table editing* *New feedback-enabled WebHelp output for DITA* *Discontinuous selection* *XPath filter for Find/Replace in Author mode* *Author mode used for selecting DITA conref target elements* *Others* *Find and replace improvements* *Search results highlighted in editors* *Improved JavaScript support* *Updated Saxon-EE to its latest version* = General = *Plugin and framework repositories* As a developer you will be able to distribute your plugins and frameworks to users by placing them in a repository and publish that on your website. When you update your plugins or frameworks the users will be notified that a new version is available and they will have the option to update automatically to that new version. As a user, you can easily install new plugins and frameworks by just pointing oXygen with a URL to a repository. You will be able to browse available plugins and frameworks and select the ones you want to install. *Updates on Transformation and Validation scenarios* - Added the possibility to associate and execute multiple scenarios - Redesigned the transformation scenarios view and transformation and validation scenarios dialogs - Improved the management of the global, project and document type scenarios - Import and export operations *EPUB 3.0* The EPUB support was updated to include validation for EPUB 3.0 files. = Development = *Master files* In version 14 oXygen introduces a new innovative concept called "Master files" which simplifies the configuration and development of XML projects. The Master Files are defined at project level and are automatically used by oXygen to determine the context for operations such as validation, content-completion, refactoring or search for XSD, XSL and RNG modules. A "Master" file generally means the root of an import/include tree of modules. * Benefits: - When a module is validated oXygen will automatically identify the master files which include that module and it validates all of them, thus the module will be validated in the context it is used from. You will see from this how a change in that module affects your whole project. - When you edit a module the Outline view and the content completion will present all the components collected starting from the Master files which include that module, thus you get to see all the referable components even if they are defined in the main file or in other modules. - Search and refactoring actions, like search references or rename components operate by default on the scope defined by the Master Files * How to define the Master Files: - Drop files in the "Master Files" logical folder in the project - Use the "Add to Master Files" contextual menu action on a file that you want to mark as Master file - Use the "Add Files" contextual menu action available on the "Master File" logical folder * Best practices defining Master Files: - Add only the top level files, the ones which are the roots of the include/import graph - Keep the file set to a minimum. Do not add standalone files (the ones which do not import or include other files). Adding too many files may affect performance *XSLT Unit Test* oXygen 14 comes with XSpec to provide XSLT Unit Test support. You can easily create a test for an XSLT stylesheet by triggering the New -> XSLT Unit Test action from the contextual menu of the Project View when the selection is an XSLT stylesheet that you want to test. This will automatically generate an XSpec stub with the templates and functions from that stylesheet that you want to test. The editing of the XSpec is then assisted with content completion and a default transformation scenario is set on XSpec files which run the tests, generating as output the test report, so all you need to do to run your tests is to click on the "Apply transformation" button. *XSLT 3.0* If an XSLT stylesheet has the version attribute set to 3.0 then the XSLT 3.0 support will be enabled automatically providing - content completion for XSLT 3.0 - transformations and XSLT validation - updated Outline view and the search and refactoring actions to handle 3.0 additions *Improved support for MarkLogic* The support for developing XML and XQuery applications with MarkLogic was improved in many areas. - Remote debugging support - Remote editing - Improved XQuery validation *CTRL/CMD + click navigation* By pressing CTRL (CMD on Mac) in an XSL/XSD/RNG editor the components will become links where you can easily navigate to that component's definition by clicking on that link. *In-place rename* The rename action on components in the current file will perform an in-place rename. There is no additional dialog, the component is highlighted in the editor to mark that you are in rename mode and the rename is performed as you type. *XPath/XQuery builder* The XPath builder view was redesigned and it was extended to provide also XQuery support resulting in the new XPath/XQuery Builder. Some of the new additions are - history and favorites - evaluate as you type - expression error checking = Authoring = *Change tracking and comment callouts* The annotations/comments are presented in callouts next to the editing area, thus making it easy to collaborate on document editing and review. The callouts can be configured to present changes (insertions or deletions) as well as additional information e.g. the changed content or the date when that change or comment was created. *Improved table editing* Support for selecting columns and rows and moving them with drag and drop or cut/copy/paste actions. Delete on table selection removes only the values, the structure should be modified using the table specific actions, delete row, column, etc. *New feedback-enabled WebHelp output for DITA* By configuring a couple of parameters you can generate feedback-enabled webhelp. A sample feedback-enabled webhelp is available on our website: http://www.oxygenxml.com/doc/demo_webhelp/ *Discontinuous selection* It is possible to select multiple text ranges (discontinuous selection) or multiple elements in the Author page and cut/copy/paste them. *XPath filter for Find/Replace in Author mode* The XPath filter which was available only in Text mode is now available in the visual editing (Author) mode. *Author mode used for selecting conref target elements* The insertion of a DITA conref is easier as oXygen presents the target elements rendered through its Author mode, not the XML source, so you can preview the content you conref to as you create that conref. = Other = *Find and replace improvements* - Preview for "Replace all in Files" - Multi line support for "Find Replace in Files" *Search results highlighted in editors* The results of the XPath, Find, Search References/Declarations operations are highlighted in the editor and marked in the side bar, in both author and text mode. *Improved JavaScript support* Content Completion, Outliner and Validation for the JS script files. *Updated Saxon-EE to its latest version* oXygen is shipped with the latest Saxon Enterprise Edition, version 9.4.0.3. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

6 6

XML DIff algorithms
by Peter West 28 May '12

28 May '12

I notice from the SDK that XML Diff uses an algorithm "based on Sasha and Zhang" for its XML_ACCURATE diff. Do you know of any implementations based on DocTreeDiff? http://www.techfak.uni-bielefeld.de/ags/pi/lehre/PatTreesWS11/change_contro… There is a lot of information out there on this topic; most of it seems to be from Springer; and none of that is freely available. See http://www.springerlink.com/content/720344g11375g004/ The ability to derive accurate deltas is essential for good version control of ODF and OOXML documents, of course. I'm looking at the Oxygen diff sdk for ways to provide diffs for mercurial or git. Peter West "Did not our hearts burn within us while he talked to us on the road...?"

3 2

[Ann] New maintenance build available for oXygen 13.2 (2012052412)
by Adrian Buza 28 May '12

28 May '12

Dear oXygen users, We announce the release of a new maintenance build (2012052412) for oXygen 13.2 (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#2012052412 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

Bug in the Ant schema
by Florent Georges 24 May '12

24 May '12

Hi, With oXygen 13.2, when opening an existing Ant build script (or when creating a new one from scratch), if in a target we have an 'ant' task with some property: <project basedir="." default="dist" name="prj"> <target name="dist"> <ant> <property name="n" value="v"/> </ant> </target> </project> then oXygen complains that: E [Xerces] The content of element type "ant" must match "EMPTY". Even though this is an important feature when using DITA-OT ;-) This might be a good idea to amend the schema? Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

8 10