- oXygen-user - www.oxygenxml.com

[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

Chemistry PDF: build fails Cannot convert string "" to xs:decimal: no digits in value;
by Yves Barbion 27 Apr '17

27 Apr '17

Hi I'm trying to create a PDF from DITA content, using Chemistry but my build fails. I get this error message: BUILD FAILED C:\Program Files\Oxygen XML Author 19\frameworks\dita\DITA-OT2.x\build.xml:45: The following error occurred while executing this line: C:\Program Files\Oxygen XML Author 19\frameworks\dita\DITA-OT2.x\plugins\com.oxygenxml.pdf.css\build.xml:194: The following error occurred while executing this line: C:\Program Files\Oxygen XML Author 19\frameworks\dita\DITA-OT2.x\plugins\com.oxygenxml.pdf.css\build.xml:132: Fatal error during transformation using C:\Program Files\Oxygen XML Author 19\frameworks\dita\DITA-OT2.x\plugins\com.oxygenxml.pdf.css\xsl\post-process.xsl: Cannot convert string "" to xs:decimal: no digits in value; SystemID: file:/C:/Program%20Files/Oxygen%20XML%20Author%2019/frameworks/dita/DITA-OT2.x/plugins/com.oxygenxml.pdf.css/xsl/post-process-tables.xsl; Line#: 100; Column#: 80 Any ideas? Thanks Yves

2 1

[oXygen XML Editor Blog] - DITA Inheritance Hierarchy
by oXygen XML Editor Blog 25 Apr '17

25 Apr '17

oXygen XML Editor Blog /////////////////////////////////////////// DITA Inheritance Hierarchy Posted: 24 Apr 2017 02:20 PM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/_uE1DzO51sg/dita-inh… The DITA standard is based on this concept of inheritance which allows extending or restricting the vocabulary while allowing the XML content to still be regarded as valid DITA. Even in the DITA standard there are various element which are specializations of others (for example "b" is a specialization of ph"). The XSLT styesheets which are used for publishing match all DITA elements by the value of their @class attribute so knowing how elements may extend each other may be useful when customizing the DITA XSLTs. A DITA inheritance hierarchy list for the base DITA specification is presented below. Would you consider it useful if a future version of Oxygen would have some kind of a tool to show such hierarchies even for custom DITA specializations? topic/copyryear topic/foreign mathml-d/mathml svg-d/svg-container topic/author topic/example topic/unknown topic/titlealts topic/linktext topic/category topic/data relmgmt-d/change-request-reference relmgmt-d/change-person relmgmt-d/change-request-id relmgmt-d/change-request-system relmgmt-d/change-completed relmgmt-d/change-started ut-d/sort-as relmgmt-d/change-item relmgmt-d/change-organization relmgmt-d/change-summary concept/data glossentry/glossPartOfSpeech glossentry/glossProperty glossentry/glossStatus relmgmt-d/change-revisionid topic/longdescref topic/audience topic/abstract concept/abstract glossentry/glossdef topic/related-links topic/body task/taskbody concept/conbody glossentry/glossBody troubleshooting/troublebody reference/refbody topic/ph hi-d/overline hi-d/line-through hi-d/sub pr-d/sep equation-d/equation-inline pr-d/repsep equation-d/equation-number hi-d/tt task/cmd pr-d/synph sw-d/userinput ut-d/coords pr-d/oper hi-d/sup pr-d/var sw-d/msgph pr-d/codeph ui-d/uicontrol hi-d/i hi-d/u sw-d/filepath sw-d/systemoutput pr-d/delim hi-d/b ui-d/menucascade topic/object topic/fig ut-d/imagemap pr-d/syntaxdiagram equation-d/equation-figure topic/featnum topic/lines topic/brand topic/state topic/source topic/link topic/vrm topic/sli topic/navtitle topic/figgroup pr-d/synblk pr-d/fragment ut-d/area pr-d/groupcomp pr-d/groupseq pr-d/groupchoice topic/note hazard-d/hazardstatement concept/note glossentry/glossScopeNote glossentry/glossUsage topic/ol task/substeps task/steps topic/stentry task/choption reference/propvalue reference/propvaluehd reference/propdeschd reference/propdesc reference/proptype reference/proptypehd task/choptionhd task/chdesc task/chdeschd topic/dlentry pr-d/plentry topic/vrmlist topic/entry topic/fn pr-d/synnote topic/xref mathml-d/mathmlref svg-d/svgref concept/xref glossentry/glossAlternateFor pr-d/synnoteref pr-d/fragref pr-d/coderef topic/component topic/series topic/bodydiv reference/refbodydiv troubleshooting/troubleSolution concept/conbodydiv topic/data-about topic/tgroup topic/keywords topic/boolean topic/critdates topic/strow task/chrow reference/property topic/simpletable reference/properties task/choicetable topic/linklist topic/revised topic/table topic/dt pr-d/pt topic/image hazard-d/hazardsymbol concept/image glossentry/glossSymbol topic/ul hazard-d/messagepanel task/choices task/steps-unordered topic/p concept/p glossentry/glossSurfaceForm troubleshooting/responsibleParty topic/q topic/linkinfo topic/dd pr-d/pd topic/lq topic/prodinfo topic/dl pr-d/parml topic/prolog topic/indextermref topic/copyright topic/div equation-d/equation-block topic/sthead task/chhead reference/prophead topic/tbody topic/searchtitle topic/colspec topic/created topic/tm topic/text topic/cite topic/li hazard-d/howtoavoid task/step task/substep hazard-d/consequence hazard-d/typeofhazard task/choice task/stepsection topic/permissions topic/no-topic-nesting topic/dlhead topic/prodname topic/index-base indexing-d/index-sort-as indexing-d/index-see indexing-d/index-see-also topic/indexterm topic/copyrholder topic/longquoteref topic/required-cleanup topic/ddhd topic/sl topic/draft-comment topic/section task/postreq task/result troubleshooting/remedy task/tasktroubleshooting concept/section glossentry/glossAlt task/context troubleshooting/cause task/steps-informal reference/refsyn task/prereq troubleshooting/condition topic/pre sw-d/msgblock pr-d/codeblock ui-d/screen topic/topic troubleshooting/troubleshooting concept/concept glossgroup/glossgroup glossentry/glossentry reference/reference task/task topic/platform topic/alt topic/keyword ui-d/shortcut markup-d/markupname xml-d/parameterentity xml-d/xmlatt xml-d/numcharref xml-d/xmlpi xml-d/textentity xml-d/xmlnsname xml-d/xmlelement pr-d/parmname pr-d/option sw-d/cmdname ui-d/wintitle ut-d/shape sw-d/varname pr-d/apiname pr-d/kwd sw-d/msgnum topic/thead topic/publisher topic/desc topic/term abbrev-d/abbreviated-form topic/title concept/title glossentry/glossShortForm glossentry/glossAbbreviation glossentry/glossSynonym glossentry/glossterm glossentry/glossAcronym topic/itemgroup task/steptroubleshooting task/tutorialinfo task/info task/stepxmp task/stepresult topic/row topic/linkpool topic/param topic/shortdesc topic/resourceid topic/dthd topic/metadata relmgmt-d/change-historylist topic/othermeta topic/prognum topic/sectiondiv -- 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 19.0 (2017042020)
by Adrian Buza 24 Apr '17

24 Apr '17

Dear oXygen users, We announce the release of a new maintenance build (2017042020) for oXygen 19.0 (XML Editor, XML Developer, XML Author, XML WebHelp). 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#2017042020 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

Announce: A UBL editing framework for the oXygenXML editor
by G. Ken Holman 17 Apr '17

17 Apr '17

Fellow UBL-Dev list members, For those of you who work with the http://www.oxygenxml.com editing tool, I have created a framework for three OASIS Universal Business Language (UBL) vocabularies: UBL 2.1 (ISO/IEC 19845:2015), UBL 2.2 csd01 (in development) and UBL 2.2 Pre-award csd02wd01pa01 (in development). The framework can be downloaded from here: http://www.CraneSoftwrights.com/resources/ubl/#oxygenubl I am planning improvements, so keep an eye out for any new releases of the tool here: http://www.CraneSoftwrights.com/resources/crane-resources.rss ... as I won't post notifications of updates to the mail list. Please let me know (off list) if you have any questions or issues with this. . . . . . . . Ken cc: UBL-Dev, UBL-TC, oXygen user list -- UBL introduction lecture - Exchange Summit - Orlando, FL - 2017-04-24 | Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/u/ | Check our site for free XML, XSLT, XSL-FO and UBL developer resources | Streaming hands-on XSLT/XPath 2 training class @ US$45 (5 hours free) |

2 1

foreign markup in ISO Schematron launched by NVDL
by Imsieke, Gerrit, le-tex 10 Apr '17

10 Apr '17

Hi, I’m calling an ISO Schematron from an NVDL in oXygen 19 which works fine so far. Now we were wondering whether we may also use foreign markup, in particular XSLT. But I don’t see an obvious way how to pass allow-foreign=true to the Schematron validator (not sure whether it is relying on the default XSLT2 ISO Schematron implementation anyway). This is not important for our current use case. Just asking out of interest and because Matthieu raised the question. Gerrit -- Gerrit Imsieke Geschäftsführer / Managing Director le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 110, Fax +49 341 355356 510 gerrit.imsieke(a)le-tex.de, http://www.le-tex.de Registergericht / Commercial Register: Amtsgericht Leipzig Registernummer / Registration Number: HRB 24930 Geschäftsführer: Gerrit Imsieke, Svea Jelonek, Thomas Schmidt, Dr. Reinhard Vöckler

5 6

Re: [oXygen-user] oXygen XML 19: import keyboard shortcuts from previous version?
by Franz-Josef Knelangen 07 Apr '17

07 Apr '17

Hi Yves, my keyboard shortcuts were updated somehow – my clunky Alt+Shift+E for “Select Element” works in oXygen 19 where I never defined it … Don’t know where/how these are stored. Best, Franz-Josef ________________________________ AKG Software Consulting GmbH Franz-Josef Knelangen Uhlandstraße 12 79423 Heitersheim Germany Tel.: +49 (0)7634 5612-611 Fax: +49 (0)7634 5612-300 E-Mail: fjk(a)akgsoftware.de Internet: www.akgsoftware.de<http://www.akgsoftware.de> Geschäftsführer: Dipl.-Ing. Artur K. Günther, Dipl.-Ing. Arno Brüggemann, Dipl.-Ing. (FH) Bernhard Feser, Dipl.-Ing. Jens Günther Sitz der Gesellschaft: Heitersheim, HRB 310383 (Amtsgericht Freiburg) Von: oXygen-user [mailto:oxygen-user-bounces@oxygenxml.com] Im Auftrag von Yves Barbion Gesendet: Freitag, 7. April 2017 11:34 An: oXygen User ML <oxygen-user(a)oxygenxml.com> Betreff: [oXygen-user] oXygen XML 19: import keyboard shortcuts from previous version? Hi oXy folks Is there a way (import/export maybe?) to get my keyboard shortcuts from previous versions into oXygen XML Editor/Author 19? Thanks Yves

2 1

A way to force catalog reload ?
by Christophe Marchand 07 Apr '17

07 Apr '17

Hello ! I use a per-project catalog, defining ${pdu}/catalog.xml in preferences / XML / Catalogs When I edit the catalog in Oxygen, or when the catalog is modified outside, the URI resolver is not updated. More, if I open another project, then re-open the project with the modified catalog, URI resolver still uses the previous version of the catalog. Is there a way to force the catalog reload, without stopping / starting oXygen ? Best, Christophe

2 2