June 2017 - oXygen-user - www.oxygenxml.com

Multi-row tabs?
by Jostein Austvik Jacobsen 02 Oct '17

02 Oct '17

I often have a lot of XML-files open simultaneously. Is it possible to configure multiple rows of tabs? Something similar to this: http://winaero.com/blog/wp-content/uploads/2013/10/Firefox-with-multi-row-t… Jostein

5 9

[oXygen XML Editor Blog] - Checking terminology when editing in Oxygen XML Editor
by oXygen XML Editor Blog 17 Jun '17

17 Jun '17

oXygen XML Editor Blog /////////////////////////////////////////// Checking terminology when editing in Oxygen XML Editor Posted: 15 Jun 2017 11:28 PM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/OPQOXtUW3J8/checking… In this blog post I will try to give a general overview about the current possibilities you have available to impose your own language checking rules when working with Oxygen XML Editor. Builtin support Oxygen comes bundled with the popular Hunspell spell checker and besides the regular bundled dictionaries for English, German, Spanish and French it allows you to install new dictionaries, either for other languages or custom dictionaries (for example dictionaries of medical terms) which you can build separately: https://www.oxygenxml.com/doc/versions/19.0/ug-editor/topics/spell-dictiona…. Besides the spell checker, Oxygen also has support for Auto-correct and you can add your own Auto-correct pairs to Oxygen. Commercial alternatives Acrolinx is a very popular commercial tool for checking content for consistency and terminology. The plugins Acrolinx developed for Oxygen standalone, Oxygen Eclipse plugin and Oxygen Web Author allow you to run the Acrolinx checker directly from inside the application. HyperSTE is yet another popular commercial tool for checking content and terminology. They also have a plugin for Oxygen standalone. Open source alternatives LanguageTools is an Open Source proofreading program for English, French, German, Polish, and more than 20 other languages . There is an open source plugin for Oxygen available on GitHub. The DITA Open Toolkit terminology checker plugin from Doctales contains Schematron rules checking that various words adhere to the terminology dictionaries which are custom built using DITA. Building your own terminology checker The fastest and simplest way to build a simple terminology checker is by using Schematron rules. The Doctales plugin is a good example for this. At some point, as the terminology dictionary keeps growing you may encounter delays and slow downs when editing the documents and validating it using the custom Schematron rules. So an alternative to this is by using our Author SDK to build your own Oxygen plugin which can use our API to check the content and then add highlights. The LanguageTools open source plugin may be a good starting example for this. -- 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

[oXygen XML Editor Blog] - Batch converting HTML to XHTML
by oXygen XML Editor Blog 13 Jun '17

13 Jun '17

oXygen XML Editor Blog /////////////////////////////////////////// Batch converting HTML to XHTML Posted: 12 Jun 2017 02:03 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/aF0B0Z1Zw1I/batch-co… Let's say you have a bunch of possible not-wellformed HTML documents already created and you want to process them using XSLT. For example you may want to migrate the HTML to DITA using the predefined XHTML to DITA Topic transformation scenario available in Oxygen. So you need to create valid XML wellformed XHTML documents from the existing HTML documents and you need to do this in a batch processing automated fashion. There are lots of open source projects which deliver processors which can convert HTML to its wellformed XHTML equivalent. For this blog post we'll use HTML Tidy. Here are a couple of steps to automate this process: Create a new folder on your hard drive (for example I created one on my Desktop: C:\Users\radu_coravu\Desktop\tidy) and download there the HTML Tidy executable specific for your platform: http://binaries.html-tidy.org/. In the same folder with the Tidy executable create an ANT build file called build.xml having the following content: <project basedir="." name="TidyUpHTMLtoXHTML" default="main"> <basename property="filename" file="${file}"/> <target name="main"> <exec command="tidy.exe -o ${output.dir}/${filename} ${file}"/> </target> </project> Link in the Oxygen Project view the entire folder where the original HTML documents are located. Right click the folder, choose Transform->Configure Transformation Scenarios... and create a new transformation scenario of type ANT Scenario. Modify the following properties in the transformation scenario: Change the scenario name to something relevant like HTML to XHTML. Change the Working Directory to point to the folder where the ANT build file is located, in my case: C:\Users\radu_coravu\Desktop\tidy. Change the Build file to point to your custom build.xml, in my case: C:\Users\radu_coravu\Desktop\tidy\build.xml. In the Parameters tab add a parameter called file with value ${cf} and a parameter called output.dir with value the path to the output folder where the equivalent XHTML files will be stored, in my case I set it to: C:\Users\radu_coravu\Desktop\testOutputXHTML. Apply the newly transformation scenario on the entire folder containing the HTML documents. At the end in the output folder you will find the XHTML equivalents of the original HTML files, XHTML documents which can later be processed using XML technologies like XSLT or XQuery. -- 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

Saxon config file resources/fileExtension not supported
by Florent Georges 02 Jun '17

02 Jun '17

Hi, Not a big deal, but the element resources/fileExtension seems not to be supported when editing a Saxon config file. Some details there: http://saxon.markmail.org/thread/mdgdftkssbhbsjzr I just created a new file in oXygen, choosing "Saxon Config File". Regards, -- Florent Georges H2O Consulting http://h2o.consulting/

2 1