- oXygen-user - www.oxygenxml.com

[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