- oXygen-user - www.oxygenxml.com

XSLT Processor under XProc
by David Levy 11 Jan '16

11 Jan '16

I have just started to experiment with XProc. Prior to using XProc, I have been transforming XML with XSLT and the transformation scenario lets me select among a number of transformation engines such as various flavors of Saxon. When I run the transformation under XProc as a p:xslt step, I am getting some errors that didn't appear with Saxon. These are easily solved, but I wonder: (1) What XSLT engine is being used with XProc? Does Calabash provide its own engine? (2) Can I control which engine is being used within XProc? With thanks, David

1 0

Debugger says that watched variable is in "Slot -1"
by Gioele Barabucci 03 Jan '16

03 Jan '16

Hello, while debugging an XSLT function, I added a watch on the parameter `$origin` and another on `string($origin//key)`. The former works flawlessly, the latter always displays the following error: > Error: Local variable $origin uses slot -1 but only 3 slots > are allocated on the stack frame I get this error when the debugger stops at the breakpoint I have placed on the `xsl:if` instruction of the following function: <xsl:function name="f:siblings-until"> <xsl:param name="origin" as="element()"/> <xsl:param name="stopper" as="xs:QName"/> <xsl:variable name="next-sibling" select="$origin/following-sibling::*[1]"/> <xsl:variable name="is-stopper" as="xs:boolean" select="node-name($origin) eq $stopper"/> <xsl:variable name="is-last" as="xs:boolean" select="not($next-sibling)"/> <xsl:if test="not($is-stopper) and not($is-last)"> <xsl:sequence select="$origin, f:siblings-until($next-sibling, $stopper)"/> </xsl:if> </xsl:function> Regards, -- Gioele Barabucci <gioele(a)svario.it>

1 0

Using a different (minor) version of Saxon with oXygen?
by Gioele Barabucci 24 Dec '15

24 Dec '15

Hello, I would like to use Saxon 9.6.0.8 with oXygen 17.1. However, oXygen 17.1 ships with Saxon 9.6.0.7. How can I suggest (or force) oXygen to use a different Saxon JAR? Being limited to Saxon-HE is OK for me, dirty hack are OK as well. Version 9.6.0.8 contains a fix for a very particular bug that I encountered and reported. Without that fix some transformations I am working on take days to complete instead of minutes. Regards, -- Gioele Barabucci <gioele(a)svario.it>

2 3

Parameter substitution in global grouped SQF fixes
by Amanda Galtman 23 Dec '15

23 Dec '15

Hi, I've read in the Schematron Quick Fixes spec that a fix definition or fix group can be global inside <sqf:fixes> or it can be local inside a given Schematron <rule> element. I am seeing cases where a fix group with an abstract parameter works as expected when the fix is inside <rule>, but the parameter substitution does not happen when the fix is inside <sqf:fixes>. The Schematron part of the substitution works as expected, so the problem seems restricted to the quick-fix. The substitution also works when I don't group fixes inside <sqf:group>. The April 2015 draft of the SQF spec says "To be done" in the "Variables and parameter" section. I am not sure whether I'm doing something wrong, or whether the implementation is incomplete. I'm hoping someone on the list knows more. Here's a simple test case that you can put inside the DocBook 5.0 RelaxNG schema. (The "s" namespace is http://purl.oclc.org/dsdl/schematron and I also had to add the sqf namespace definition.) <sqf:fixes> <sqf:group id="testfix"> <sqf:fix id="testfix1"> <sqf:param name="expectedrolevalue" abstract="true"/> <sqf:description> <sqf:title>Set role=$expectedrolevalue</sqf:title> <sqf:p>Set the role attribute to the value '$expectedrolevalue'.</sqf:p> </sqf:description> <sqf:add node-type="attribute" target="role">$expectedrolevalue</sqf:add> </sqf:fix> </sqf:group> </sqf:fixes> <s:pattern abstract="true" id="testcase_ABSTRACT"> <s:rule context="db:para/db:$childname"> <s:assert test="@role='$expectedrolevalue'" sqf:fix="testfix">Expected role attribute to be set to $expectedrolevalue.</s:assert> </s:rule> </s:pattern> <s:pattern is-a="testcase_ABSTRACT"> <s:param name="childname" value="literal"/> <s:param name="expectedrolevalue" value="blah"/> </s:pattern> The quick fix doesn't properly substitute "blah" for $expectedrolevalue. But it does if you either remove <sqf:group> and change id="testfix1" to id="testfix", OR move the entire <sqf:group> element into <s:rule>. Thanks, Amanda

2 2

XML Catalog puzzle
by Gary Gapinski 22 Dec '15

22 Dec '15

2 2

Custom headers on HTTP requests
by Tom Cleghorn 22 Dec '15

22 Dec '15

Hi, Is there any means of controlling the HTTP headers Oxygen sends when using 'Open URL' from the File menu? I'm working with an API that uses Accept headers to return different subsets of a large document, and it'd be very useful to be able to control that within Oxygen too. Thanks! Cambridge University Press is the publishing business of the University of Cambridge with VAT registered number GB 823 8476 09. Our principal office is at University Printing House, Shaftesbury Road, Cambridge, CB2 8BS, United Kingdom.

3 2

Overriding Schematron process-assert template during XML validation
by Amanda Galtman 18 Dec '15

18 Dec '15

Hi, Is there a way to make Oxygen's RelaxNG/Schematron validation of XML files pick up my customizations of templates like process-assert or process-message? I know how to make this work outside of Oxygen, but I'm having trouble finding the right hooks in Oxygen (and tinkering with oxygen.jar seems like a really bad idea). Do I extend the Schematron framework, or is that used only for editing Schematron source files? Thanks, Amanda

3 5

[Ann] New maintenance build available for oXygen 17.1 (2015121117)
by Oxygen XML Editor Support (Adrian Buza) 17 Dec '15

17 Dec '15

Dear oXygen users, We announce the release of a new maintenance build (2015121117) for oXygen 17.1 (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#2015121117 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.2020 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

FTP from inside XProc in oXygen?
by Wendell Piez 15 Dec '15

15 Dec '15

Fellow oXygen connoisseurs, I have attached an FTP site to my Data Source Explorer, which makes me happy, as it is easy to upload results of my XProc Transformation Scenario to my site just by copying from the Project view. What I wonder is whether this operation could not be simplified even further. This process in particular is an XProc pipeline, which generates some results and creates others by moving static resources in the file system. (So p:store and p:zip are involved, it's not just binding pipeline results.) If I could configure either or both the Transformation Scenario or the XProc itself to write to my (authenticated) FTP server, I would be overjoyed. I would welcome any hints or ideas. Thanks! Cheers, Wendell -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

3 2

How to include smaller files into a "master document" in Oxygen?
by Jean-Luc Chevillard 11 Dec '15

11 Dec '15

Greetings! I am currently editing several XML files which are the chapters of a Tamil thesaurus, and each file is dangerously close to the size limit connected with the script specificity. ("support for RTL languages" has to be activated, for proper display, and I have already increased the default size beyond which RTL language support is automatically deactivated) I would appreciate pointers on the best methods for dealing with the larger entity, i.e. the sum of the chapters. Can I create a MASTER document in Oxygen in which the chapters are INCLUDED (by mentionning their names) for the sake of processing the sum of the chapters? (I currently run XSLT transformations on separate chapters for making indices? How to do that for the sum of the chapters?) Thanks for any pointers to the appropriate section inside the Oxygen documentation (provided that it is possible to do that in Oxygen ...). If the "RTL language" limit was not there, I would have used a single file but that does not seem to be possible. -- Jean-Luc Chevillard (Paris-Pondicherry-Hamburg) "https://univ-paris-diderot.academia.edu/JeanLucChevillard"

3 6

xd:doc documentation generation and maven
by cmarchand＠oxiane.com 11 Dec '15

11 Dec '15

Hello, is there a way to automate a XSL documentation generation - ideally from a maven project.. ? Is there an entry in Oxygen API to generate such a documentation that a maven plugin - or any other tool - could reuse ? Well, the purpose is to generate a xsl-library documentation from continuous integration, so it can be done in a jenkins plugin (which is simpler than in a maven plugin). Any hint ? Best regards, Christophe

5 5

Any way to control output of Schematron validation?
by Maloney, Christopher (NIH/NLM/NCBI) [C] 09 Dec '15

09 Dec '15

We are using schematron validation in oXygen, with a custom element in our output messages. I'm finding that this causes the output messages to be unusable, because they are displayed on only one line, and that line is taken up by the custom element, and all of it's various namespace declarations. I'm attaching a screenshot -- not sure if it will get through the mailman. Is there any way to configure oxygen to show the text value of these messages? It would be much more useful. As it is, the user has to hover the mouse over the message, or r-click and do "show messages", and even then, the message is dominated by this element, because of all the (unused) namespace declarations on it. Thanks! -- Chris Maloney NIH/NLM/NCBI (Contractor) Building 45, 4AN36D-12 301-594-2842

6 10

Oxygen XML Blog Post: Overview of DITA Reuse Strategies
by Radu Coravu 02 Dec '15

02 Dec '15

Hi everybody, Just finished my latest blog post. It's an overview about all possibilities of reusing content with DITA: > http://blog.oxygenxml.com/2015/11/dita-reuse-strategies-short-tutorial.html Hope you'll enjoy it. If you have any feedback, it is as usual welcomed. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

[oXygen XML Editor Blog] - Sharing Application Settings
by oXygen XML Editor Blog 26 Nov '15

26 Nov '15

oXygen XML Editor Blog /////////////////////////////////////////// Sharing Application Settings Posted: 24 Nov 2015 11:44 PM PST http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/ijz2ztr8NGQ/sharing-… There are varios ways in the Oxygen standalone version through which a team of writers can share and use a set of common settings. Below I will try to list each of these possibilities along with useful links: Save the settings at project level and have all users use the same project "projectName.xpr" file in the Project view when editing. Most of the Oxygen Preference pages have a switch radio button which allows you to pass the settings to Project level and save them in the current project configuration file opened in the Project view. If you commit that Project configuration file to a version control system like GIT or SVN, all writers can open and use that project when working with the repository content. For example, when we work on the Oxygen User's Manual using our common GitHub repository, we all open in the Project view the "userguide.xpr" project which comes with various fixed options (eg: enabling automatic spell checking):https://github.com/oxygenxml/userguide You can find out more details about sharing projects here: https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/sharing-proje…. Create and then provide a default options XML document to others. When placed in a specific place in the Oxygen installation or referenced via a specific property in the application startup script, this default options XML document will be used by the application to provide default values for certain settings. You can find out more about how default options work here:https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/default-…. Have others manually import an options XML document which you exported from Oxygen:https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/import…. An Oxygen plugin could use our Java API to impose fixed options when the application starts using the API method: PluginWorkspaceProvider.getPluginWorkspace().setGlobalObjectProperty(key, value). In our Maven-based SDK we have a sample plugin called ImposeOptions which imposes a fixed set of options when the application starts. If you want to share document type configurations (for editing certain XML vocabulary) you can find more details in this older blog post: http://blog.oxygenxml.com/2015/08/document-type-extension-sharing.html. -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

[Ann] New maintenance build available for oXygen 17.1 (2015111718)
by Oxygen XML Editor Support (Adrian Buza) 20 Nov '15

20 Nov '15

Dear oXygen users, We announce the release of a new maintenance build (2015111718) for oXygen 17.1 (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#2015111718 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.2020 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

[oXygen XML Editor Blog] - Possibilities to obtain PDF from DITA
by oXygen XML Editor Blog 18 Nov '15

18 Nov '15

oXygen XML Editor Blog /////////////////////////////////////////// Possibilities to obtain PDF from DITA Posted: 16 Nov 2015 01:07 PM PST http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/sXZMCVP56Pc/possibil… Lately while attending Tekom 2015 and DITA OT Day 2015 I happened to come across two more DITA to PDF solutions that I did not know about so I tried to compile below a list of all DITA to PDF possibilities that I know of, along with some details: Legacy DITA to PDF editing solution. It is no longer distribute with DITA OT 2.x and is probably not compatible anymore with it. Default DITA to PDF solution embedded in the DITA Open Toolkit distribution. Besides Apache FOP you can also use RenderX XEP or Antenna House for publishing. It's customization can be done either via a plugin or via a PDF customization folder: https://www.oxygenxml.com/doc/versions/17.1/ug-editor/index.html#topics/dit…. DITA to PDF using CSS. This open source DITA OT plugin was developed by Oxygen as an alternative to the default PDF publishing. It allows styling the DITA content using CSS and publishing to PDF using either Prince XML or Antenna House. Antenna House DITA OT plugin for producing PDF from DITA using Antenna House. There is also a DITA specialization plugin which allows you to set specific formatting attributes directly to DITA elements. The TopLeaf XML Publisher commercial product allows you to produce various outputs like PDF and EPUB from XML content. The application also has a visual PDF layout formatter, it comes also with a DITA OT plugin and has installation instructions for Oxygen:http://www.turnkey.com.au/tksweb/xmtp/webhelp_out/oxygen/install.html. Miramo, again a commercial solution which recently started developing support for DITA using a DITA OT plugin. Possibly user based DITA to PDF publishing will be free and server based production will require buying a license. Like TopLeaf, it also has a visual PDF layout designer. Adobe FrameMaker can also publish to PDF using its own solution. Now the question would be, why there are so many solutions available? In my opinion all these solutions are available because the default DITA to PDF output still requires quite a lot of XSLT skills in order to customize. Jarno Elovirta's PDF plugin generator covers some of the mainstream possible customizations but not all. What do you think? -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

4 3

Automatic Validation - in text mode, in Eclipse release of oXygen
by Echlin, Robert 09 Nov '15

09 Nov '15

Hi I have developed some schematron rules to apply to DITA content for our staff. We use the IXIASOFT CMS Client, which means that we are using oXygen inside of Eclipse. When I open a file in Author Mode, the schematron rules are applied automatically. Red and yellow underlines flag the items considered invalid by the Schematron rules. When I switch to editing the file in Text mode, the Schematron rules are not applied automatically. I have to manually run validation. We are behind in the IXIASOFT releases, so we are using Eclipse 3.5.2 and oXygen 16.1. Is there a setting I can change to fix this? Is this fixed in oXygen 17.1? Is it fixed in newer versions of Eclipse? All my very best, Rob -- Rob Echlin, Documentation Systems Architect, Wind River Office: 613-270-5796, Cell: 613-266-8311, Skype: rob.echlin.wr

2 5

displaying <> around element names in Schematron messages
by Echlin, Robert 02 Nov '15

02 Nov '15

Hi Adrian and Radu et all, I want to display Schematron messages such as: - a <systemoutput> element must be inside a <codeblock> element. The display in oXygen looks like this: - a <systemoutput> element must be inside a <codeblock> element. I was expecting this: - a <systemoutput> element must be inside a <codeblock> element. Is there a way to achieve that? Or can you add it in a future release, please? All my very best, Rob -- Rob Echlin, Documentation Systems Architect, Wind River Office: 613-270-5796, Cell: 613-266-8311, Skype: rob.echlin.wr

2 4

[oXygen XML Editor Blog] - Adding CALS-table related functionality to your custom Oxygen framework
by oXygen XML Editor Blog 31 Oct '15

31 Oct '15

oXygen XML Editor Blog /////////////////////////////////////////// Adding CALS-table related functionality to your custom Oxygen framework Posted: 30 Oct 2015 07:32 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/dZaVU4PwlCc/adding-c… Oxygen comes with full support for CALS tables in DITA and Docbook documents, meaning that you can easily make selections, resize columns, and invoke special actions like insert or delete rows and columns, join, or split cells. You can also easily customize tables properties such as alignments, separators, and table borders. But what if you are editing documents from other vocabularies, containing tables with CALS structure? What you can do to obtain the same table editing features? Let's suppose that you already created an Oxygen framework for your documents vocabulary (if you need further information about frameworks, see http://blog.oxygenxml.com/2014/08/the-oxygen-sdk-part-2-frameworks.html) What we want to obtain next is to extract all the CALS tables related support from Docbook framework and add it to your custom framework. Why Docbook and not DITA as reference? Because the DITA customization is based on the "class" attribute checking while the Docbook one is more general (element-name oriented). Table rendering copy [oXygen_install_dir]\frameworks\docbook\css\cals_table.css in your framework css directory in the Document Type edit dialog, Author tab, CSS sub-tab, add the ${framework}/css/cals_table.css entry to the list of the CSSs In this way the table will be rendered properly in Author mode and the following features will be available: select cells (CTRL+click), rows (click before the row), columns (click on top of the row), tables (click in the left-up corner of the table) resize table column Create table actions Here are the table-related actions implemented in Docbook that you can implement also in you framework: Expand colspecs Insert/Delete Rows Insert/Delete Columns Table Properties Join cells Split cell Copy [oXygen_installation_dir]\frameworks\docbook\docbook.jar in your framework directory (this jar contains all the table operations classes needed to create table actions). In Document type edit dialog go to Classpath tab and add the docbook.jar from your framework directory to the list of paths. In this way you have access to all table operations from your framework. For every table action you have to define a corresponding action in the Document type configuration dialog. Here are the details: https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/the-action-di…. You can look at the corresponding Docbook action to see the properties (id, name, icons, the conditions that enables it, the specific operation for CALS tables). Once you created these actions you can add them to the UI. Add table actions to menu, toolbar and contextual menu To add an action to the menu go to Document Type configuration dialog, Author tab, Menu sub-tab, select the action from Available actions section and add it to the Current action section. To add an action to the contextual menu go to Document Type configuration dialog, Author tab, Contextual menu sub-tab, select the action from Available actions section and add it to the Current action section. To add an action to the toolbar go to Document Type configuration dialog, Author tab, Toolbar sub-tab, select the action from Available actions section and add it to the Current action section. If all goes well, your custom framework which uses the standard CALS table naming mechanism will properly handle tables, both for display and for table-related operations. -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

[Ann] New maintenance build available for oXygen 17.1 (2015102718)
by Oxygen XML Editor Support (Adrian Buza) 29 Oct '15

29 Oct '15

Dear oXygen users, We announce the release of a new maintenance build (2015102718) for oXygen 17.1 (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#2015102718 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.2020 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

[oXygen XML Editor Blog] - How Special Paste works in Oxygen
by oXygen XML Editor Blog 29 Oct '15

29 Oct '15

oXygen XML Editor Blog /////////////////////////////////////////// How Special Paste works in Oxygen Posted: 28 Oct 2015 04:48 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/8aMRl4DpDek/how-spec… If you've worked with one of the XML vocabularies for which Oxygen has out of the box support like DITA, Docbook, TEI, XHTML you've probably already used the support Oxygen has for converting content pasted in the application from external applications like Microsoft Word, Excel or from any web browser. This is a very useful feature for converting various types of content to XML because it preserves and converts styling, links, lists, tables and image references. The feature relies on the fact that when copying content in the applications mentioned above, they set in the clipboard the HTML equivalent of the copied content. So all Oxygen has to do is clean up that HTML, make it wellformed XHTML and apply conversion XSLT stylesheets over it. This support is not hardcoded and anybody who is developing an Oxygen framework customization for a certain XML vocabulary can provide conversion stylesheets for external pasted HTML content. I will describe how this works for the DITA framework and you can do the same for yours. You can also use this information to modify the way in which smart paste works for the bundled framework configurations. In the Preferences->Document Type Association page you can choose to edit (or extend) the DITA document type association. In the Extensions tab the Extensions bundle implementation is set to DITAExtensionsBundle which resides in the DITA Java extensions archive dita.jar. The DITAExtensionsBundle is an extension of the ExtensionsBundle API and it provides its own external object extension handler: /** * @see ro.sync.ecss.extensions.api.ExtensionsBundle#createExternalObjectInsertionHandler() */ @Override public AuthorExternalObjectInsertionHandler createExternalObjectInsertionHandler() { return new DITAExternalObjectInsertionHandler(); } The DITAExternalObjectInsertionHandler extends the base class AuthorExternalObjectInsertionHandler and provides a reference to its specific conversion stylesheet: /** * @see ro.sync.ecss.extensions.api.AuthorExternalObjectInsertionHandler#getImporterStylesheetFileName(ro.sync.ecss.extensions.api.AuthorAccess) */ @Override protected String getImporterStylesheetFileName(AuthorAccess authorAccess) { return "xhtml2ditaDriver.xsl"; }Note: The Extensions tab also allows you to specify the external object insertion handler as a separate extension. In the same Document Type edit dialog in the Classpath tab you will see that there is a reference to a framework-specific resources folder like:${framework}/resources/ If you look on disk in the DITA framework resources folder: "OXYGEN_INSTALL_DIR\frameworks\dita\resources" you will find the xhtml2ditaDriver.xsl stylesheet there. The stylesheet imports various other stylesheets which you could probably fully reuse and which apply various cleanups on HTML produced with MS Word. It also handles the conversion between the pasted HTML content and DITA so it is a good starting point, you can copy the entire set of XSLT stylesheets to your framework and use those as a starting point. -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

conditional table columns
by Surbhi SINGHAL 27 Oct '15

27 Oct '15

Hello As far as I know, this is not possible, but just in case, if there is any possibility. I have a 5 column table where I need to make 3 columns conditional based on audience attribute. Is this possible? Since it might be a common challenge, what are the work-arounds that are used for tackle such scenarios. Thanx Surbhi

2 1

Replacing icons on oXygen form control elements with a custom made icon font
by Stefan Eike 26 Oct '15

26 Oct '15

Hi, I have written a blog post about creating oXygen form control elements with a custom made icon font. This may boost the rendering performance in Author view when using many form control elements and large files. http://xephon2.github.io/2015/10/21/fontello/ Best regards, Stefan

1 0

[oXygen XML Editor Blog] - DITA-related improvements and goodies in Oxygen 17.1
by oXygen XML Editor Blog 24 Oct '15

24 Oct '15

oXygen XML Editor Blog /////////////////////////////////////////// DITA-related improvements and goodies in Oxygen 17.1 Posted: 23 Oct 2015 06:26 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/4_KvUa2YiFs/dita-rel… I'm happy to announce this autumn the release of Oxygen 17.1. We've been quite buzy in the last months working on it and we hope you'll enjoy it in your daily XML-related activities. Oxygen 17.1 comes with official support for the latest operating systems, Windows 10 and Mac OSX OS X El Capitan (10.11). It also comes with a new user interface color theme called "Light" that makes the entire application interface look crisp and clean. Besides this, you now have the support to define custom color themes and share them with your team. As always we also have lots of DITA-related improvements: The dialogs for inserting conkeyrefs, conrefs and keyrefs to metadata have all been merged in one intuitive to use toolbar action called "Reuse content". The dialog used to insert or to edit properties for a topic reference now also allows you to: Set profiling attributes. Define metadata content. Set any other valid attribute on the topic reference. Experimental support for DITA 1.3. You can enable DITA 1.3 support (using the latest DITA Open Toolkit 2.1.2 bundled with the application) from the "Preferences->DITA" page. This support includes support for editing and validation, scoped keys and branch filtering. Scoped Keys Support. You can establish key scopes and insert references to keys inside or outside key scopes. oXygen will also takes key scopes into account when it validates and checks for completeness, resolves key and content key references, and publishes. Branch Filtering Support. The DITA 1.3 branch filtering mechanism makes it possible to reuse the content of topics multiple times within the same map, each time using different filters. You can find out more about DITA 1.3 support from our user's manual: http://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/dita1-3-suppor… or by watching this video demo: https://www.oxygenxml.com/demo/DITA_13.html The oXygen WebHelp system was also improved to enhance your published output. Google Search, Google Analytics, and some popular social media widgets can now be integrated into your WebHelp system and search features are now available in offline mode. Oxygen 17.1 comes bundled with an experimental new plugin developed by Jarno Elovirta for generating MS Word output (OOXML) from DITA content. Once you decide in the "Preferences->DITA" page to use the bundled DITA Open Toolkit 2.1.2, you will also enable the ability to create Lightweight DITA topics and maps so you can experiment with this exciting new standard in the making: http://dita.xml.org/blog/lightweight-dita. -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

[Ann] Oxygen XML Editor 17.1 beta
by Oxygen XML Editor Support (Adrian Buza) 07 Oct '15

07 Oct '15

Dear oXygen users, We are happy to announce that version 17.1 of oXygen XML Editor is close to being released. We have decided to offer a beta version prior to the final release to give you the opportunity to send us your feedback on the new features. Below, please see information about: * Downloading - oXygen 17.1 beta downloading links and notes * Licensing - a trial license key for testing * What's new - a summary of the most important new features in version 17.1 = Downloading = Editor: http://www.oxygenxml.com/beta17_1/oxygenxml_editor.html Author: http://www.oxygenxml.com/beta17_1/oxygenxml_author.html Important Notes: - This build is meant for testing purposes only. Do not use it for production work. - You should install this beta version in a different directory than your current Oxygen installation. For Windows, we also recommend that you disable file associations during the installation to preserve your current Oxygen file associations with the various XML file types. - All feedback is welcome. = Licensing = If you already have a license key for Oxygen XML Editor or Author with an active SMP, it will also work for this beta version. If you don't have one, a registration dialog box will open and you can use the following 30-day trial license key: ------START-LICENSE-KEY------ Registration_Name=17.1 Beta Company= Category=Enterprise Component=XML-Editor, XSLT-Debugger, Saxon-SA Version=17 Number_of_Licenses=1 Date=10-01-2015 Trial=31 SGN=MCwCFDbLWEdcFoEi5FHK/14DDwUOSAMLAhRZvDRNJPFv4wH+MCz6yccVs/XyCw\=\= -------END-LICENSE-KEY------- = What's new in Oxygen XML Editor 17.1 = XML Quick Fixes * Quick Fixes Presented in a Tooltip Window * Support for Schematron Quick Fixes in Other Documents * Support for the user-entry Element in Schematron Quick Fixes * Improved Performance for Schematron Quick Fixes XML Refactoring * Custom Operations Support XSLT Files User Interface * New Color Themes * Breadcrumb Now Available in Text Mode DITA Support * Improvements to Various Actions and Dialog Boxes * Improvements to the DITA Map to PDF WYSIWYG Experimental Transformation Scenario * Publish DITA Content to Microsoft Office Word Format * Indicator to Show Multiple References to the Same Topic in a DITA Map * Automatically contribute New File Templates from a DITA OT plugin * Experimental Lightweight DITA support DITA 1.3 Support * Create and Edit DITA 1.3 Documents * Scoped Keys Support * Branch Filtering Support CSS * Improvements to the oxy_xpath Function * Support for the :focus-within CSS Level 4 Pseudo-Class * Support for the :has CSS Level 4 Pseudo-Class * Support for the text-indent CSS Property * Support for the 'outline' CSS Property * Support for Negative Margins and Indents * Improved Performance for DITA CSS API * JavaScript-based Workspace Access Plugin Extension * AuthorStylesheet Plugin Extension * API to Customize Callouts * Customize Actions in the Review Panel * Execute XQuery Update Scripts on Content in Author Mode * Change the Tag Display Mode * Add a Drag and Drop Listener to Author Mode * Validate Editor Content * Advanced Custom Rule Matcher * Specify Initial State for Custom Contributed View * Customize Highlights in Author Mode * Treat Expanded/Referenced Content as transparent when running XPath Expressions * Escape/Unescape Attribute Values * Retrieve Clipboard Content Copied in Author Mode * Present Warning Messages * Refresh References for a DITA Map * Open a Specific Preferences Page Other * Support for XSLT 3.0 in Schematron Schemas * RNG Schema Updated for XSLT 3.0 * Support for SharePoint Online for Office 365 Sites that use ADFS Authentication * Enhances Support for XLIFF 2.0 Documents * Support for Executing XQuery Update Scripts Directly over Content in Author Mode * Configuring Content Completion Proposals * Convert Hexadecimal Sequence to its Corresponding Unicode Character * XPath Expressions in Formatting Preferences Accept Attribute Conditions * Enhanced Validation Support for XSL-FO Component Updates * DITA OT 2.1 * Calabash 1.1.14 * LESS 1.7.5 * Saxon 9.6.0.7 * TEI Schema 2.8.0 * TEI XSL 7.39 Please let us know if you encounter any problems with this beta build. All feedback is welcome. Best regards, Adrian Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.2020 Fax: +40-251-461482 support(a)oxygenxml.com

3 2