- oXygen-user - www.oxygenxml.com

[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

oxygenxml and multitrans?
by Jakob Fix 01 Oct '15

01 Oct '15

Hello, I've been wondering whether there is some kind of API or a plugin available for OxygenXML with the translation workbench tool called MultiTrans. cheers, Jakob.

2 2

Free Webinar Today [DITA Glass]
by Radu Coravu 29 Sep '15

29 Sep '15

Hi everybody, Today, Sep 16 between 11:00 AM and 12:30 PM EDT Comtech and Oxygen are hosting a free webinar about dynamic content conversions, a feature we added in Oxygen 17.0. So if you want to find out more details or to join us please follow this link: http://comtech-serv.com//index.php?main_page=product_info&cPath=28_2_149&pr… Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

3 3

Xquery unit test framework
by Erik Zander 28 Sep '15

28 Sep '15

Hi all, In oxygen there's the template for creating xspec tests for XSLT and it can by looking at the XSLT file create some of the tests. I wonder if there's something similar for xquery? Best Regards Erik Zander

2 1

This might have been foolish, but ...
by Ben McGinnes 26 Sep '15

26 Sep '15

Hello, So I was poking around in the oxygen/templates/ directory and had a little look at the ePub 3.0 template in there. Given what I've said about ePub 3.0 and internal structure in the past, it was inevitable that I modify the template in there to add a version with subdirectories for assorted purposes and it certainly looks like it's behaving at least as far as being an additional global template. Obviously there would be no point in mentioning it here if I wasn't sharing. Anyone interested can find it here: https://github.com/adversary-org/epub-tools/tree/master/oxygen/templates In that directory you'll find the original template, mainly for comparison (and yes, making an oxygen/templates/ path in that repo is solely to make it obvious to others where to install/copy to). The template I'm referring to here is the one called "EPUB 3.0 DroidBook.epub.bin" and is so named for the embedded font I've dumped in there (Droid Sans Fallback Full). There's another template in there as well, "EPUB 3.0 BrythonBook.epub.bin" and you're welcome to play with it, of course, but I should warn you that it is *highly* experimental. It's basically built on the DroidBook template, but includes a complete implementation of Brython. Brython is an implementation of Python 3.3 for browsers and javascript. It allows you to use python code in the same way as one might normally use javascript and since ePub 3 is supposed to allow a subset of javascript I figured I'd see whether I could get this thing to work in an ePub too. I won't be too surprised if it goes nowhere and it's quite possible it might do Bad Things™ instead. On the other hand, there's nothing lost by trying it and seeing what breaks. Even if it doesn't play nicely with ePub, it ought to play quite well with regular HTML and XHTML projects. As is amply demonstrated on its website and described on GitHub: http://brython.info/ https://github.com/brython-dev/brython If anyone does decide to play with Brython and ePub, I'll be interested to hear how it goes; whether that be a success or a catastrophic failure. With regards to licenses; the original templates from oXygenXML followed fairly basic specifications from the IDPF, Brython uses a BSD license (the license file is in the ePub, in the resurced subdirectory with the README and the Droid Sans font). My bits barely qualify as needing a license, but if you must have one then my WTFNMF Public License ought to do the job nicely. You can find the terms of that here: https://github.com/adversary-org/wtfnmf Oh, yes, the manifest for the Brython experiment does include all the files for the implementation (you're welcome). So it should just be a matter of calling brython.js by its relative path in any HTML or XHTML file to make it work. At least in theory, there's been zero testing yet. Regards, Ben -- Ben McGinnes http://www.adversary.org/ Twitter: benmcginnes Writer, Systems Administrator, Trainer, ICT Consultant GPGME Python 3 API Maintainer, GNU Privacy Guard https://www.gnupg.org/ Encrypted email preferred, primary OpenPGP/GPG key: 0x321E4E2373590E5D OpenPGP/GPG key here: http://goo.gl/GVGwT and http://goo.gl/SDs0D OpenPGP/GPG key transition: http://www.adversary.org/keyswitch.txt.asc

1 0

Autumn conferences
by George Bina 22 Sep '15

22 Sep '15

Hi all, After some quiet time during the summer, we will have a busy schedule this autumn. First, we will be in San Jose, California, next week on Oct 1-2 at the Information Development World conference. You can meet us at the oXygen XML Editor stand in the exhibition area or attend or session on Friday, 2:00pm-2:45pm: Single-Source Publishing Across Multiple Formats https://www.eiseverywhere.com/ehome/113382/schedule/ After that, we will participate also this year at the TEI Members Meeting in Lyon, France. We will host a half day workshop on Oct 28 http://tei2015.huma-num.fr/en/workshops/#item3 If you attend TEI Members Meeting and you are interested in extending the TEI support in oXygen or to find the latest additions to oXygen please register to join us there: https://docs.google.com/forms/d/1Bd9fGF7CY9V5gh9o7ukKhLX-iVMezu3LV2wVOVucXu… November will be the busiest month, we start with the TCWorld conference by Tekom, taking place in Stuttgart, where we have 3 presentations in the main conference program, plus one product presentation, plus a larger stand where you are welcome to meet us http://conferences.tekom.de/tcworld15/conference-program/conference-program/ A few days after Tekom we move to Munich and we turn into hosts, as we organize the second edition of the DITA-OT Day event, a conference dedicated to the core engine behind DITA implementations, the DITA-OT open source project: http://www.oxygenxml.com/events/2015/dita-ot_day.html This is a free event but registration is required. We organize the DITA-OT Day in the pre-conference day of DITA Europe, and at the same location, so it should be really easy to attend both events - or event all 3 events in one trip: TCWorld, DITA-OT Day and DITA Europe. We plan to end the 2015 events with DITA Europe where we will have a stand where you can meet our team as well as two interesting presentations at the conference https://ditaeurope.infomanagementcenter.com/ Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

In-element whitespace and Author Mode
by Andreas Wagner 18 Sep '15

18 Sep '15

Dear list, I am sorry for bringing up yet another whitespace question. I almost believe that in XML the devil lives in the whitespaces. Also, it is quite possible that our problem is specific to our particular situation and of no interest to other projects. But then again, maybe someone is able to help nonetheless. We deal with TEI xml documents recording linebreaks that in many cases are not meant to represent a word boundary: <lb n="016_011"/>que con el pre<lb break="no" rendition="#noHyphen" n="016_012"/>sidente o juez que reside en la prouincia: puede <lb n="016_013"/>hazer thesoreros y receptores en su prouincia: In order to improve readability of the XML source, all our lines begin at the leftmost position of the line no matter the nesting level the current the paragraph is at. The exception is lines that begin with four spaces in order to align the @n-attribute with other lines and yet have the lb-element begin without intervening whitespace at the end of the preceding line/word fragment. But when I edit the document in author mode, it removes the linebreak within the element, so that the first of the following is a very long line and the snippet is only two lines long: <lb_n="016_011"/>que_con_el_pre<lb_break="no"_rendition="#noHyphen"_n="016_012"/>sidente_o_juez_que_reside_en_la_prouincia:_puede <lb n="016_013"/>hazer thesoreros y receptores en su prouincia: (Whitespace and indenting preferences are mentioned below.) Now our workflow relies on an external file providing links to certain places in the TEI file: <a href="W0004.xml#line=449;column=1">016_013</a> Therefore it is somewhat annoying that editing the TEI leads to ("hard") lines being drawn together and the external file increasingly pointing to wrong places. I understand that author mode parses the XML into a DOM tree and re-serializes it on save, so I don't know if this behaviour can be changed at all. But then what would you suggest how we should be approaching this problem? (Can we point to the relevant place based on the @n-attribute of the lb element? If we had to provide all the lbs with @xml:ids I think it would thwart our attempts to make the xml sources better readable. And all of this would help us with linking the two files, but the xml file would still end up with bad readability.) Thank you for any idea, Andreas P.S. I have selected the "Preserve empty lines", "Preserve text as it is" and "Preserve line breaks in attributes" in Options | Preferences | Editor/Format/XML and added "*" to the "Preserve Space" Elements. I also think I have deactivated pretty printing everywhere I could. In Editor | Edit Modes | Author | Format and indent, I have chosen "only the modified content". -- Dr. Andreas Wagner Project "The School of Salamanca" Academy of Sciences and Literature, Mainz and Institute of Philosophy Goethe University Frankfurt http://salamanca.adwmainz.de IGF HP 25 / R 2.455 Norbert-Wollheim-Platz 1 60629 Frankfurt am Main Tel. +49 (0)69/798-32774 Fax +49 (0)69/798-32794

2 1

copying tables from other sources
by Cwiklowski, Don 15 Sep '15

15 Sep '15

Whenever I copy a table from Word or Excel, or even HTML to a DITA reference topic all of the elements come across as <properties> (etc), but if I drop it into a Concept, Oxygen translates a table into the proper DITA elements. Does anyone know how to fix this since the majority of our Reference topics contain tables? Don Cwiklowski, Jr. Sr. Technical Communicator Customer Technical Communications | Operations and Technology MasterCard 2200 MasterCard Blvd | O'Fallon, MO 63366 tel 636-722-6802 don_cwiklowski(a)mastercard.com<mailto:don_cwiklowski@mastercard.com> [cid:image001.gif@01D0EF87.2A1DBDC0]<www.mastercard.com> Please think of the environment before printing this email. CONFIDENTIALITY NOTICE This e-mail message and any attachments are only for the use of the intended recipient and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient, any disclosure, distribution or other use of this e-mail message or attachments is prohibited. If you have received this e-mail message in error, please delete and notify the sender immediately. Thank you.

2 1

[oXygen XML Editor Blog] - A Short Story of Reuse
by oXygen XML Editor Blog 14 Sep '15

14 Sep '15

oXygen XML Editor Blog /////////////////////////////////////////// A Short Story of Reuse Posted: 07 Sep 2015 02:38 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/-bqdMBmNY0Q/a-short-… Give the smartest human in the world a piece of wood and ask him/her to make paper. Give him/her no prior tools and it will take years to come up with a decent process which would result in some brown almost usable thick piece of paper. This blog post is about reuse, not necessarily reuse of tools and materials, but reuse of knowledge. Humanity has evolved not because each generation is smarter than the last one but because we learned to reuse and pass knowledge to larger and larger audiences and from one generation to another. Almost all tools that we use today are made up of quite a complex set of components which interact with each other. There is no one person in a car assembly factory who still knows all the pieces and how they come together. Although using the tool is easier than interacting with all components which make it up, you still need knowledge to operate it and in this day and age having enough people to teach how a certain tool can be used is no longer an option. You need to pass knowledge in other forms, on paper or in some kind of digital form. So I would define technical communication as a means of passing knowledge about using tools to a larger audience. Reuse in technical communication can be structured on many levels: Reuse written content by publishing it to more than one format (PDF, HTML, EPUB, MS Word). It turns out that XML is perfect for publishing content in more than one format. XML is not designed to be consumed directly by end users and its benefit lies directly in this. Your XML content should contain all the data necessary for obtaining all the output formats. So if you are using XML in your technical content, no matter what standard or custom vocabulary, you can safely check the first and most important level of reuse. Create larger publications from existing ones. Either using an XML standard like XInclude or using standards with their own diverse and powerful methods of reuse like DITA, or by performing custom techniques you can merge XML content in larger publications. Reuse content written for a certain tool to document the functionality and behavior of a very similar tool. In most mature XML standards like DITA and Docbook there is this implemented concept of profiling which allows you to dynamically filter at publishing time content marked with certain attributes from your original XML project. In this way from the same XML content you can publish documentation for multiple similar tools. Reuse smaller pieces of common content in more than one publication. Again, using XML standards like XInclude or DITA specific standards like content references you can create and maintain small libraries of reusable XML content, then reuse these components across various publications. Reuse images and other binary resources in multiple publications. Because XML content does not embed binary resources, these resources are stored separately and thus they can be reused in multiple places. So these are what I consider to be the main selling points for using XML in technical documentation. As usual any feedback is welcomed. -- 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

3 2

About oXygen XML Editor
by oXygen XML Editor Blog 03 Sep '15

03 Sep '15

oXygen XML Editor Blog /////////////////////////////////////////// DITA 1.3 Branch Filtering - Next Generation of Reuse Posted: 02 Sep 2015 05:51 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/tZnLUSz5jiU/dita-13-… Thanks to the hard working OASIS DITA TC Group the DITA 1.3 standard is quite close to being released. Oxygen 17.1 which will be released probably in September this year will have experimental DITA 1.3 support. This will include publishing using a custom build of the latest DITA Open Toolkit 2.x engine in which the main developer Jarno Elovirta has already added incipient support for key scopes and branch filtering. In this blog post I'm going to give you a small example of how branch filtering can benefit two cases of reuse which could not be done previously. You can read more about branch filtering in the DITA 1.3 specs. Case 1 - Combine Two Profiles in the Same Publication Let's say you have a DITA Project about preparing and cooking vegetables. And your DITA Map looks like this:<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd"> <map> <title>Cooking vegetables</title> <topicref href="cleaningTableArea.dita" audience="novice"/> <topicref href="preparingVegetables.dita"/> <topicref href="addingExtraFlavor.dita" audience="expert"/> </map> You have some content common both for expert and novice users but you also have content which is specific for a target audience. You do not need to teach expert chefs how to clean the table and you do not want to teach novice cooks about enhanced flavoring techniques. All is fine until at some point you decide to produce a publication which contains merged inside both the novice and the expert map contents. And here's where branch filtering comes for help. You can create a main DITA Map which reuses your current DITA Map with two profiling contexts:<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd"> <map> <title>Cooking Vegetables.</title> <topichead navtitle="Cooking for Beginners" keyscope="novice"> <topicref href="vegetables.ditamap" format="ditamap"> <ditavalref href="novice.ditaval"/> </topicref> </topichead> <topichead navtitle="Cooking for Experts" keyscope="expert"> <topicref href="vegetables.ditamap" format="ditamap"> <ditavalref href="expert.ditaval"/> </topicref> </topichead> </map> Case 2 - Reusing Common Topics with Different Product NamesLet's say you have a simple DITA task in which you have described how a certain task can be performed for a certain product. In our case, the task describes peeling potatoes: The task works and at some point in your Vegetables Soup publication you realise you need to write a similar task about peeling cucumbers. The task is exactly the same, except the product name. So naturally you want to reuse the existing written task. For this we re-write the task so that instead of of the product potatoes it contains two consecutive profiled product names:Peeling <ph product="potatoes">potatoes</ph><ph product="cucumbers">cucumbers</ph>and include the task in the main DITA Map in two places with different ditaval filters applied:<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd"> <map> <title>Peeling Vegetables.</title> <topichead navtitle="Potatoes"> <topicref href="peeling.dita"> <ditavalref href="potatoes.ditaval"/> </topicref> </topichead> <topichead navtitle="Cucumbers"> <topicref href="peeling.dita"> <ditavalref href="cucumbers.ditaval"/> </topicref> </topichead> </map> This kind of usage will produce in the HTML output folder two topic HTML files from the single peeling.dita, one for each filter context. The DITA samples for this post can be downloaded from http://www.oxygenxml.com/forum/files/branchFilteringBlogSamples.zip. As usual any feedback is welcomed. If you would like to beta test Oxygen XML Editor 17.1 with experimental DITA 1.3 support please contact us: support(a)oxygenxml.com. -- 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

Odd webhelp with feedback error message
by Jim Henderson 01 Sep '15

01 Sep '15

I'm receiving the following e-mail from a testing server that I'm using feedback on: [73.53.13.170] - 2015-08-26 10:27:46: Unknown error type: [8] Undefined property: RecordSet::$m_CurrentRow on line 200 in file /var/www/html/PingID-API/oxygen-webhelp/resources/php/classes/db/RecordSet.php , PHP 5.4.16 (Linux) This happens when I submit a comment in the comment system. Doesn't seem to matter if I'm authenticated or not. I've tried this on CentOS 7.0 and SUSE Linux Enterprise 11 SP3, and both of them are generating this message for some reason. The output was generated with Oxygen 17. I've got other webhelp with feedback that works OK (in fact, I can use the same output set on another server and it works just fine). I've got mysql installed and the php mysql extension is present as well. I've set up the database fine, and I can see the comments in the UI, but the e-mails being sent only contain this error. I'm not even sure where to start to troubleshoot this - anyone have any ideas? Thanks, Jim -- [image: Ping Identity logo] <https://www.pingidentity.com/> Jim Henderson Technical Writer @ jhenderson(a)pingidentity.com [image: phone] +1 720.390.3443 Connect with us… [image: twitter logo] <https://twitter.com/pingidentity> [image: youtube logo] <https://www.youtube.com/user/PingIdentityTV> [image: LinkedIn logo] <https://www.linkedin.com/company/21870> [image: Facebook logo] <https://www.facebook.com/pingidentitypage> [image: Google+ logo] <https://plus.google.com/u/0/114266977739397708540> [image: slideshare logo] <http://www.slideshare.net/PingIdentity> [image: flipboard logo] <http://flip.it/vjBF7> [image: rss feed icon] <https://www.pingidentity.com/blogs/>

2 3

About oXygen XML Editor
by About oXygen XML Editor 28 Aug '15

28 Aug '15

About oXygen XML Editor /////////////////////////////////////////// DITA 1.3 Implementation Status in upcoming Oxygen XML Editor 17.1 Posted: 26 Aug 2015 10:48 PM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/yUZ8D06g8Zo/dita-13-… We plan to release Oxygen 17.1 in about a month or two, probably at the beginning of October this year. Starting with version 17.1, Oxygen includes experimental support for editing and publishing using some of the DITA 1.3 features. If you want to test this support and give us feedback please contact us directly to obtain an Oxygen 17.1 beta kit. To enable DITA 1.3 editing support in Oxygen 17.1 and use the custom bundled DITA Open Toolkit 2.1 for publishing, open the Preferences dialog box, go to DITA, and select the Built-in DITA OT 2.x radio button. The following table is a list of DITA 1.3 features and their implementation status: DITA 1.3 Features Implementation Status Feature Editing Publishing [Latest DITA Open Toolkit 2.x is used.] DITA 1.3 DTD, XML Schema, and Relax NG-based maps/topics/tasks/references, etc. New DITA 1.3 file templates. Also by default DITA topics and maps which do not specify version in the DOCTYPE declaration are also considered to be DITA 1.3. Specific annotations presented in the content completion window and documentation tooltips for all new DITA 1.3 elements. See below Learning Object and Group maps New file templates No specific support implemented Troubleshooting specialization Create and edit new troubleshooting topics No specific support implemented XML markup domain Validation and Content Completion Special rendering in PDF and XHTML-based outputs. Equation and MathML domain Validation and content completion Display and Insert equations Special rendering in PDF and XHTML-based outputs. SVG domain Validation and content completion Display referenced SVG content Special rendering in PDF and XHTML-based outputs. Other new DITA 1.3 elements (div, strike-through, overline, etc) Validation and Content Completion. Special rendering in PDF and XHTML-based outputs. Release management domain Validation and Content Completion No specific support implemented. Scoped keys Define key scopes Validate and check for completeness Resolve keyrefs and conkeyrefs taking key scopes into account. Partially implemented. Various issues may still be encountered. Branch filtering Display, create and edit ditavalref elements. Partially implemented. Various issues may still be encountered. Shorthand to address syntax that identifies elements in the same topic Properly resolved for validation, links, and conrefs. Implemented. Various table attributes (orientation, rotation, scope, and headers on cells) Not implemented in the Table Properties action support. But attributes can be changed from the Attributes view. Not implemented. New Map topicref attributes (cascade, deliveryTarget) Allow setting new attributes, propose proper values for them. Implemented. -- You are subscribed to email updates from "About oXygen XML Editor." 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

bug report: repeated schema-declared element content
by Syd Bauman 26 Aug '15

26 Aug '15

Assignment: write a RELAX NG schema for Keats _On first looking into Chapman's Homer_. I (deliberately) wrote a ridiculously literalist schema, attached. When I create a new XML document that uses this schema, oXygen properly inserts the required elements, including all 14 required <pLine> elements. When I ask for auto-completion (CTL-space) of the <head> or any of the @n, oXygen does the right thing and gives me the one and only correct choice as the only possible value in the pop-up. But when I ask for auto-completion of <pLine>s 2 through 14, the one and only possible value in the pop-up is the content for the first <pLine>! Worth noting that jing gets it right. After filling in the content using auto-completion, validation will say of <pLine> 2, e.g., character content of element "pLine" invalid; must be equal to "And many goodly states and kingdoms seen;" Details: <oXygen/> XML Developer 17.0, build 2015052917 Mac OS X 10.6.8 error occurs using XML syntax or compact syntax Also tested on: <oXygen/> XML Developer 17.0, build 2015051321 Ubuntu 12.04 only tested compact syntax start = element poem { element head { "On first looking into Chapman's Homer" }, element sonnet { element pLine { attribute num { "01" }, "Much have I travell'd in the realms of gold," }, element pLine { attribute num { "02" }, "And many goodly states and kingdoms seen;" }, element pLine { attribute num { "03" }, "Round many western islands have I been" }, element pLine { attribute num { "04" }, "Which bards in fealty to Apollo hold." }, element pLine { attribute num { "05" }, "Oft of one wide expanse had I been told" }, element pLine { attribute num { "06" }, "That deep-brow'd Homer rules as his demesne;" }, element pLine { attribute num { "07" }, "Yet did I never breathe its pure serene" }, element pLine { attribute num { "08" }, "Till I heard Chapman speak out loud and bold:" }, element pLine { attribute num { "09" }, "Then felt I like some watcher of the skies" }, element pLine { attribute num { "10" }, "When a new planet swims into his ken;" }, element pLine { attribute num { "11" }, "Or like stout Cortez when with eagle eyes" }, element pLine { attribute num { "12" }, "He star'd at the Pacific — and all his men" }, element pLine { attribute num { "13" }, "Look'd at each other with a wild surmise —" }, element pLine { attribute num { "14" }, "Silent, upon a peak in Darien." } } } -- Syd Bauman, EMT-Paramedic Senior XML Programmer/Analyst Northeastern University Women Writers Project s.bauman(a)neu.edu or Syd_Bauman(a)alumni.Brown.edu

4 5

About oXygen XML Editor
by About oXygen XML Editor 25 Aug '15

25 Aug '15

About oXygen XML Editor /////////////////////////////////////////// DITA 1.3 Key Scopes - Next Generation of Reuse Posted: 24 Aug 2015 03:34 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/eupu2DkD4is/dita-13-… Thanks to the hard working OASIS DITA TC Group the DITA 1.3 standard is quite close to being released. Oxygen 17.1 which will be released probably in September this year will have experimental DITA 1.3 support. This will include publishing using a custom build of the latest DITA Open Toolkit 2.x engine in which the main developer Jarno Elovirta has already added incipient support for key scopes and branch filtering. In this blog post I'm going to give you a small example of how key scopes can benefit simple cases of reuse which could not be done previously. Let's say you have a simple DITA task in which you have described how a certain task can be performed for a certain product. In our case, the task describes peeling a potato: The task works and at some point in your Vegetables Soup publication you realise you need to write a similar task about peeling cucumbers. The task is exactly the same, except the product name. So naturally you want to reuse the existing written task. For this we re-write the task so that instead of of the product potatoes it contains a key reference:<ph keyref="vegetable"/> Next we need to define in our DITA Map the vegetable key and bind it to a specific value in the potatoes context: <topicref href="potatoes_overview.dita" keyscope="potatoes">  <keydef keys="vegetable"> <topicmeta> <keywords> <keyword>potatoes</keyword> </keywords> </topicmeta> </keydef>  <topicref href="peeling.dita"/> </topicref>and add in our DITA Map another key scope with the overview and the task which deal with cucumbers peeling: <topicref href="cucumbers_overview.dita" keyscope="cucumbers">  <keydef keys="vegetable"> <topicmeta> <keywords> <keyword>cucumbers</keyword> </keywords> </topicmeta> </keydef>  <topicref href="peeling.dita"/> </topicref> As you may have noticed, we have not used the key scope names for anything. Just by defining the key scopes, we made the product name to be expanded differently in both contexts. But our Vegetables Soup publication may also contain a topic which lists all possible vegetables. This topic is defined in a context outside any key scope:<topicref href="vegetables_over.dita"/>and this overview topic can refer to each product name using the full keyscope key reference value:<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> <topic id="vegetables_over"> <title>Vegetables Overview</title> <body> <p>This is an overview of all vegetables necessary to make soup. You will learn how to use vegetables like <ph keyref="potatoes.vegetable"/> and <ph keyref="cucumbers.vegetable"/> to make a great starter soup.</p> </body> </topic> As stated before, this kind of reuse was not possible using the standard DITA 1.2 standard constructs. As it turns out, with DITA 1.3 we can also implement this kind of reuse using branch filtering. The DITA samples for this post can be downloaded from http://www.oxygenxml.com/forum/files/keyscopesBlogSamples.zip. As usual any feedback is welcomed. If you would like to beta test Oxygen XML Editor 17.1 with experimental DITA 1.3 support please contact us to support(a)oxygenxml.com. -- You are subscribed to email updates from "About oXygen XML Editor." 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

Mac OSX, single instance of diffFiles?
by Steven Anderson 21 Aug '15

21 Aug '15

I've got a Mac and I'd like to have a single instance of diffFiles running. I tried to add -Dcom.oxygenxml.MultipleInstances=false\ to the shell script invocation, but that didn't seem to help. Is there a way to specify this? -- Steve

2 2