- oXygen-user - www.oxygenxml.com

XSLT solutions
by Bernhard Kleine 13 Oct '17

13 Oct '17

It seems that I have mastered the XML elements which are needed for my book. The ebook transformed is already pretty nice. However, I would like to know how to manage XSLT in order to (for a start) 1. have the term of a variable list in bold on the same line as the list item 2. have title and legends of figures below the mediaobject and not above If you could point to me how to achieve that with Oxygen I would be very grateful. Regards Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

2 2

(Resent with a smaller attached PNG screen shot) Is there a known problem for the display of Tamil with Oxygen on a Mac?
by Jean-Luc Chevillard 10 Oct '17

10 Oct '17

Greetings from Pondicherry. I have been recently encouraging a student to use Oxygen for entering some historically important text on which she is working and which mixes Latin and Tamil. Howevever, we have encountered unexpected difficulties, concerning the display of the Tamil script, on her Mac Laptop (running Mac OS Sierra°, which are better explained by the comparison of two screen shots. the attached file "Mac_Tamil_Display_Problem.png" which is a screen shot taken from her laptop the attached file "Windows_Normal_display_for_Tamil.png" which is a screen shot taken from my laptop (running Windows 7) The text under display is a fragment of a text and a relevant sample is: <parag> <n>8</n> <l>8. குற்றியலிகரம். Abbreviatio literae இ. Voces,</l> <l>quae per ய incipiunt, assumere in principio possunt இ:</l> <l>sic யாழ் - இயாழ், யதி - இயதி, யமன் - இயமன்,</l> <l>யூகம் - இயூகம் etc. Quando autem ab hoc இ eliditur</l> <l>உ praecedens, quod sit குற்றியலுகரம், de qua infra,</l> <l>tunc இ vocatar குற்றியலிகரம் , i abbreviatum. Sic pro</l> <l>கொட்டு யானை, மாடு யாது it கொட்டியானை, மாடியாது</l> <l>etc et tunc இ habet dimidium tantum supra dictae</l> <l>mensurae; unde si metro opus sit, non consideratur in</l> <l>versu. Sic in வெண்பா post pedem விளம் dictum, debet</l> <l>sequi நேரசை, et tamen post குழலினி, id est கருவிளம்,</l> <l>sequitur இயாழ் , quod si consideraretur இ, esset நிரை</l> <l>யசை, unde eo non considerato, remanet யாழ் நேரசை.</l> <l>Pro quo videnda sunt, quae dicimus P. IV, caput I.</l> <l>Pariter est interjectio மியா, quae inservit pro secunda</l> <l>persona. Sic pro கேள், கேண்மியா, pro சொல், சொன் </l> </parag> When she opens the same file in her browser, there is no display problem. The problem occurs with the character combinations for which a glyph substitution is needed We have been trying to see whether the problem might fall under ... https://www.oxygenxml.com/doc/versions/19.0/ug-author/topics/bidirectional-… ... but without sucess. Any pointers would be appreciated Best wishes -- Jean-Luc Chevillard (in Pondicherry) https://univ-paris-diderot.academia.edu/JeanLucChevillard https://twitter.com/JLC1956 http://www.linguist.univ-paris-diderot.fr/~chevilla/sup/index_bis.html

2 1

DITA metrics report tool
by Ben McGinnes 09 Oct '17

09 Oct '17

Hello, This is really a question for the support team, but I suspect the answer will benefit others here, hence sending to the list. The metrics reporting tool that was in versions 19.0 and earlier here: {frameworks}/dita/report/report.xsl Has gone walkies. Does it now live somewhere else in the frameworks directory or has it been removed entirely? Obviously copying it back in works fine for now and in future I'll probably just have to modify those transformations to find it externally, If you're wondering, yes, I use it extensively, it's a wonderful ego boost for any writer. :) Regards, Ben -- | Ben McGinnes | Adversarial Press | Author and Publisher | | Writer, Trainer, Systems Administrator, Developer, ICT Consultant | | Twitter: @benmcginnes (personal) | @AdversaryPub (publishing) | | Web: http://www.adversary.org/ http://publishing.adversary.org/ | | ----------------------------------------------------------------- | | GPG Made Easy (GPGME) Python 3 API Maintainer, GNU Privacy Guard | | GPG key: 0x321E4E2373590E5D http://www.adversary.org/ben-key.asc | | GPG key fpr: DB47 24E6 FA42 86C9 2B4E 55C4 321E 4E23 7359 0E5D | | https://www.gnupg.org/ https://securetheinternet.org/ | | ----------------------------------------------------------------- |

2 4

Is there a known problem for the display of Tamil with Oxygen on a Mac?
by Jean-Luc Chevillard 09 Oct '17

09 Oct '17

Greetings from Pondicherry. I have been recently encouraging a student to use Oxygen for entering some historically important text on which she is working and which mixes Latin and Tamil. Howevever, we have encountered unexpected difficulties, concerning the display of the Tamil script, on her Mac Laptop (running Mac OS Sierra°, which are better explained by the comparison of two screen shots. the attached file "Mac_Tamil_Display_Problem.png" which is a screen shot taken from her laptop the attached file "Windows_Normal_display_for_Tamil.png" which is a screen shot taken from my laptop (running Windows 7) The text under display is a fragment of a text and a relevant sample is: <parag> <n>8</n> <l>8. குற்றியலிகரம். Abbreviatio literae இ. Voces,</l> <l>quae per ய incipiunt, assumere in principio possunt இ:</l> <l>sic யாழ் - இயாழ், யதி - இயதி, யமன் - இயமன்,</l> <l>யூகம் - இயூகம் etc. Quando autem ab hoc இ eliditur</l> <l>உ praecedens, quod sit குற்றியலுகரம், de qua infra,</l> <l>tunc இ vocatar குற்றியலிகரம் , i abbreviatum. Sic pro</l> <l>கொட்டு யானை, மாடு யாது it கொட்டியானை, மாடியாது</l> <l>etc et tunc இ habet dimidium tantum supra dictae</l> <l>mensurae; unde si metro opus sit, non consideratur in</l> <l>versu. Sic in வெண்பா post pedem விளம் dictum, debet</l> <l>sequi நேரசை, et tamen post குழலினி, id est கருவிளம்,</l> <l>sequitur இயாழ் , quod si consideraretur இ, esset நிரை</l> <l>யசை, unde eo non considerato, remanet யாழ் நேரசை.</l> <l>Pro quo videnda sunt, quae dicimus P. IV, caput I.</l> <l>Pariter est interjectio மியா, quae inservit pro secunda</l> <l>persona. Sic pro கேள், கேண்மியா, pro சொல், சொன் </l> </parag> When she opens the same file in her browser, there is no display problem. The problem occurs with the character combinations for which a glyph substitution is needed We have been trying to see whether the problem might fall under ... https://www.oxygenxml.com/doc/versions/19.0/ug-author/topics/bidirectional-… ... but without sucess. Any pointers would be appreciated Best wishes -- Jean-Luc Chevillard (in Pondicherry) https://univ-paris-diderot.academia.edu/JeanLucChevillard https://twitter.com/JLC1956 http://www.linguist.univ-paris-diderot.fr/~chevilla/sup/index_bis.html

1 0

Transformation failed: Oxygen 19.1 editor + markdown files
by Annette Nehrling 09 Oct '17

09 Oct '17

Hi all, Having installed the "new" 19.1 editor on Windows 10, all attempts to run a transformation scenario on a ditamap that includes markdown files, fail. Even the sample.xpr project for the Markdown project (garage.ditamap) from the dita/markdown-dita folder does not work. Error message is the following: Transformation failed. C:\Program Files\Oxygen XML Editor 19\frameworks\dita\DITA-OT2.x\plugins\org.dita.base\build_init.xml:156: Directory C:\Program Files\Oxygen XML Editor 19\samples\dita\markdown-dita\out\pdf creation was not successful for an unknown reason If I try to run my own markdown project the error message is a little bit more complex: Transformation failed. C:\Program Files\Oxygen XML Editor 19\frameworks\dita\DITA-OT2.x\plugins\org.dita.base\build_preprocess.xml:299: java.lang.IllegalArgumentException: Only file URI scheme supported: C:/DITA-OT/test_user_manual/TEST%20User%20Documentation/test_getting_started.ditamap Any idea how to fix this issue? Maybe I did sth wrong? Thank you all so much for your support! Best regards, Annette -- Avira Operations GmbH & Co. KG Kaplaneiweg 1 | 88069 Tettnang | Deutschland / Germany Telefon / Telephone: +49 7542-500 0 Telefax / Facsimile: +49 7542-500 3000 Facebook: https://www.facebook.com/avira Twitter: https://twitter.com/avira Blog: http://blog.avira.com Registergericht: Amtsgericht Ulm, HRA 722586 | USt.-IdNr.: DE 815289569 | Pers. haftende Gesellschafterin: Avira OP GmbH | Firmensitz: Tettnang | Registergericht: Amtsgericht Ulm, HRB 726712 | Gesch?ftsf?hrer: Travis Witteveen Commercial Register: Amtsgericht Ulm, HRA 722586 | VAT-ID: DE 815289569 | Personally Liable Partner: Avira OP GmbH | Headquarters: Tettnang | Commercial Register: Amtsgericht Ulm, HRB 726712 | Chief Executive Officer (CEO): Travis Witteveen

2 2

numbering not correct
by Bernhard Kleine 06 Oct '17

06 Oct '17

My document starts with <?xml version="1.0" encoding="UTF-8"?> <?xml-model href="http://docbook.org/xml/5.1/rng/docbook.rng" schematypens="http://relaxng.org/ns/structure/1.0"?> <?xml-model href="http://docbook.org/xml/5.1/sch/docbook.sch" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?> <!DOCTYPE chapter[ <!ENTITY % my-entities SYSTEM "../Myentities.ent"> %my-entities; ]> <chapter version="5.1" xml:id="Ch11.Circuits" xml:lang="de" xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink"> <title>Regulationsmuster</title> <para> In diesem Abschnitt ... </para> <sect1 xml:id="Ch11.S.FeedbackInhibition" xreflabel="ch11.S Feedback Inhibition"> <title>Rückkopplungen</title> (snip) however, the section numbering is shown as 0.1 AFAIC in Version 19 this was correct, but is a regression in 19.1 -- spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

2 1

Search and Replace with regular expression
by Bernhard Kleine 05 Oct '17

05 Oct '17

Hi, while porting from LaTeX to docbook5 I encounter numerous cases where a regular expression search and replace would be extremely helpfull. E.g. I have a citation as \citep{ABC65}. This should become <citation><biblioref linkend="ABC65"/></citation>. Is that possible in oxygen and how to achieve it? Regards Bernhard Kleine -- spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

4 8

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

Fast Create Keydefs
by Eliot Kimber 02 Oct '17

02 Oct '17

Now that there is Fast Create Topics I’d like to have “Fast Create Keydefs” that I can use to create multiple keydefs at once by filling in a tabular form. For example, I create key definitions for each external Web site referenced from my docs, of which there can be many in some of my open-source project documentation. It would be nice to have a dialog that provides a tabular input where the columns would be e.g.: Key | Target | Format Or maybe Target | Key | Format Makes more sense (since for this task my focus is on associating target URLs with keys. Likewise, the format value can be inferred from the target URI. I also create keys for each image or other media object, so it would be convenient to have a way to select multiple images or other media objects and do a “fast create keys” from all of them, e.g., use the filename as the base for the key and fill in the table so the user can then adjust the keys as needed. In both cases a I usually use a prefix to distinguish one type of key from another, so it would be use useful to be able to specify a prefix or suffix to be used for all the keys being created, e.g., “image-“ for image keys, “website-“ for Web site keys, etc. Cheers, E. -- Eliot Kimber http://contrext.com

2 1

Another Feature Request: Refactor Key Names
by Eliot Kimber 02 Oct '17

02 Oct '17

While I’m asking for things, another one I’d like is a refactoring action to rename keys that will update references to the key in any referenced topics or maps, analogous to the existing rename resource refactoring. Cheers, E. -- Eliot Kimber http://contrext.com

2 1

New Fast Create Topics Feature: Very Cool
by Eliot Kimber 02 Oct '17

02 Oct '17

Just tried the new Fast Create Topics feature in the Map Manager: very cool. That will save a lot of time. Cheers, E. -- Eliot Kimber http://contrext.com

2 1

Strange behavior with xls:message on oxygen 19
by Erik Zander 22 Sep '17

22 Sep '17

Hi, I have encountered a problem with xls:message in the xslt debugger, it work if I run a transformation scenario. The version I have is XML Editor 19.0, build 2017042020 And the problem is that the messages are empty. The problem doesn't seem to be present in 18.1 or 16.1 Have anyone else encountered this? Regards Erik Zander XML-Developer Studentlitteratur AB

2 1

Is Tamil among the languages for which a specific collation is available?
by Jean-Luc Chevillard 21 Sep '17

21 Sep '17

Greetings The title of this message says it all: Is Tamil among the languages for which a specific collation is available when using Oxygen? I have to sort items in the Tamil alphabetical order, but when I specify that « lang="ta" » as a parameter in my sort command, the order I obtain is the one which is based on the Unicode codepoint collation, which is not what one expects while sorting Tamil words The same thing happens if I define a parameter such as <xsl:param name="sorting-collation" select="'http://saxon.sf.net/collation?lang=ta'"/> and then use it in a sort command <xsl:sort select="." collation="{$sorting-collation}"/> To give a specific example the following short list is extracted from a much longer list which is part of an HTML file created by applying an XSLT file (containing SORT commands) to an XML file <ul> <li>அத்தத்தின் பெயர் [head-word ABOVE 7 items]</li> <li>அனந்தன் பெயர் [head-word ABOVE 1 items]</li> <li>அனற்பொறியின் பெயர் [head-word ABOVE 1 items]</li> <li>அனற்றிரளின் பெயர் [head-word ABOVE 1 items]</li> <li>அனுடத்தின் பெயர் [head-word ABOVE 7 items]</li> <li>அமரமாதர் பெயர் [head-word ABOVE 2 items]</li> <li>அரக்கர் பெயர் [head-word ABOVE 7 items]</li> <li>அருகன் பெயர் [head-word ABOVE 43 items]</li> </ul> HOWEVER, this is not the proper Tamil dictionnary order order, which should be: <ul> <li>அத்தத்தின் பெயர் [head-word ABOVE 7 items]</li> <li>அமரமாதர் பெயர் [head-word ABOVE 2 items]</li> <li>அரக்கர் பெயர் [head-word ABOVE 7 items]</li> <li>அருகன் பெயர் [head-word ABOVE 43 items]</li> <li>அனந்தன் பெயர் [head-word ABOVE 1 items]</li> <li>அனற்பொறியின் பெயர் [head-word ABOVE 1 items]</li> <li>அனற்றிரளின் பெயர் [head-word ABOVE 1 items]</li> <li>அனுடத்தின் பெயர் [head-word ABOVE 7 items]</li> </ul> Any suggestions would be appreciated -- Jean-Luc Chevillard (currently in Pondicherry, India) https://univ-paris-diderot.academia.edu/JeanLucChevillard https://twitter.com/JLC1956

2 4

Cursor tooltip
by Bernhard Kleine 14 Sep '17

14 Sep '17

Hi, when I don't move the mouse there appears always "Inherited architecture []" I have tried to stop this in the Options -> preferences dialog but failed. Can you please point me where to stop this? Thank you Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

1 0

Re: [oXygen-user] New Git plugin for Oxygen
by Pierre Attar 25 Aug '17

25 Aug '17

Alex, It works now. Thanks a lot, Pierre Le 23/08/2017 à 08:15, Alex Jitianu a écrit : > > Hello, > > We've released a new version (1.0.8) that should fix this problem. > Please try again and let us know how it goes. > > Best regards, > Alex > -- > Alex Jitianu > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > On 8/22/2017 6:19 PM, Pierre ATTAR wrote: >> 3 plugins are installed : >> Componize plugin >> A customization of the ditamap gui >> Xspec plugin >> >> Regards, Pierre >> >> >> Le 22 août 2017 14:49:20 GMT+02:00, Alex Jitianu >> <alex_jitianu(a)sync.ro> a écrit : >> >> Hello, >> >> Sorry about that... First of all let's make Oxygen start again. The >> first step is to identify Oxygen's options directory. Depending on the >> platform the options folder is located as follows: >> - Windows XP - [user-home-folder]\Application Data\com.oxygenxml >> - Windows Vista/7 - [user-home-folder]\AppData\Roaming\com.oxygenxml >> - Mac OS X - [user-home-folder]/Library/Preferences/com.oxygenxml >> - Mac OS X - ~/Library/Preferences/com.oxygenxml >> - Linux - [user-home-folder]/.com.oxygenxml >> >> Inside this directory search for and remove the directory: >> git.support <http://git.support>-1.0.7 >> >> Oxygen should now start again. >> >> Do you have, by any chance, any other plugins installed inside Oxygen? >> One of these plugins might be contributing a slf4j jar inside the main >> Oxygen ClassLoader. To find out which plugins are installed, please go >> to Options->Preferences... on the Plugins page. Nevertheless, we should >> take care of such situations so I will let you know as soon as we >> release a fix. >> >> Best regards, >> Alex >> >> >> -- >> Envoyé de mon truc mobile. Veuillez excuser ma brièveté. >

1 0

Re: [oXygen-user] New Git plugin for Oxygen
by Alex Jitianu 23 Aug '17

23 Aug '17

Hello, Sorry about that... First of all let's make Oxygen start again. The first step is to identify Oxygen's options directory. Depending on the platform the options folder is located as follows: - Windows XP - [user-home-folder]\Application Data\com.oxygenxml - Windows Vista/7 - [user-home-folder]\AppData\Roaming\com.oxygenxml - Mac OS X - [user-home-folder]/Library/Preferences/com.oxygenxml - Mac OS X - ~/Library/Preferences/com.oxygenxml - Linux - [user-home-folder]/.com.oxygenxml Inside this directory search for and remove the directory: git.support-1.0.7 Oxygen should now start again. Do you have, by any chance, any other plugins installed inside Oxygen? One of these plugins might be contributing a slf4j jar inside the main Oxygen ClassLoader. To find out which plugins are installed, please go to Options->Preferences... on the Plugins page. Nevertheless, we should take care of such situations so I will let you know as soon as we release a fix. Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 8/22/2017 1:24 PM, Pierre Attar wrote: > Hum, seems that there is a problem with the plugin, perhap's due to > franch language : unable to start oxygen since I install the plugin. > > Pierre > > Cannot start <oXygen/> XML Editor. > Due to:java.lang.reflect.InvocationTargetException > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) > at java.lang.reflect.Constructor.newInstance(Unknown Source) > at ro.sync.ui.application.ApplicationLauncher.d(Unknown Source) > at ro.sync.ui.application.ApplicationLauncher.launch(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at ro.sync.exml.Oxygen.main(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:65) > at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:101) > at > com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:26) > Caused by: java.lang.LinkageError: loader constraint violation: when > resolving method > "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" > the class loader (instance of ro/sync/util/k/e) of the current class, > org/slf4j/LoggerFactory, and the class loader (instance of > ro/sync/util/ib) for the method's defining class, > org/slf4j/impl/StaticLoggerBinder, have different Class objects for > the type org/slf4j/ILoggerFactory used in the signature > at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:299) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281) > at org.eclipse.jgit.util.FS.<clinit>(FS.java:160) > at org.eclipse.jgit.api.Git.open(Git.java:99) > at > com.oxygenxml.git.service.GitAccess.setRepository(GitAccess.java:134) > at > com.oxygenxml.git.view.WorkingCopySelectionPanel$1.itemStateChanged(WorkingCopySelectionPanel.java:104) > at javax.swing.JComboBox.fireItemStateChanged(Unknown Source) > at javax.swing.JComboBox.selectedItemChanged(Unknown Source) > at javax.swing.JComboBox.contentsChanged(Unknown Source) > at javax.swing.AbstractListModel.fireContentsChanged(Unknown Source) > at javax.swing.DefaultComboBoxModel.setSelectedItem(Unknown Source) > at javax.swing.DefaultComboBoxModel.addElement(Unknown Source) > at javax.swing.JComboBox.addItem(Unknown Source) > at > com.oxygenxml.git.utils.StagingPanelRefresh.addGitFolder(StagingPanelRefresh.java:108) > at > com.oxygenxml.git.utils.StagingPanelRefresh.checkForGitRepositoriesUpAndDownFrom(StagingPanelRefresh.java:99) > at > com.oxygenxml.git.utils.StagingPanelRefresh.execute(StagingPanelRefresh.java:48) > at > com.oxygenxml.git.utils.StagingPanelRefresh.call(StagingPanelRefresh.java:42) > at > com.oxygenxml.git.CustomWorkspaceAccessPluginExtension.applicationStarted(CustomWorkspaceAccessPluginExtension.java:42) > at ro.sync.exml.MainFrame.rvm(Unknown Source) > at ro.sync.exml.MainFrame.<init>(Unknown Source) > at ro.sync.exml.MainFrame.<init>(Unknown Source) > ... 18 more > > Le 22/08/2017 à 10:36, Alex Jitianu a écrit : >> Hello everyone, >> >> Those of you that are using Git might be interested to know that >> there is a new Git plugin for Oxygen [1]. If you want to give it a >> try, it can be quickly installed through Oxygen's add-on support >> [2][2.1]. In the beginning we focused on the essential functionality, >> the operations that are performed often, like committing, pulling >> changes etc. Another cool feature is the use of Oxygen's Diff tool >> [3] to highlight the changes. Moreover, if the file is in conflict >> (has been modified both by you and another), Oxygen's Three Way Diff >> [4] will show a comparison between the local change, the remote >> change, and the original base revision. >> >> Please let us know if you have any suggestions about how to make it >> better or what other functionality is worth adding. >> >> >> [1] https://github.com/oxygenxml/Oxygen-Git-Plugin#git-support-plugin >> [2] >> https://www.oxygenxml.com/doc/versions/19.0/ug-editor/topics/installing-and… >> [2.1] >> https://raw.githubusercontent.com/oxygenxml/Oxygen-Git-Plugin/master/build/… >> [3] >> https://www.oxygenxml.com/doc/versions/19.0/ug-editor/topics/file-compariso… >> [4] >> https://www.oxygenxml.com/doc/versions/19.0/ug-editor/topics/file-compariso… >> >> Best regards, >> Alex > >

2 2

Schematron Quickfix - selection?
by Wendell Piez 22 Aug '17

22 Aug '17

Hello oXygen friends, I need to build an ID-selector functionality into a Schematron Quickfix. That is, when an element fails validation against a Schematron (because an IDREF attrbute is missing or points to the wrong kind of element), I would like the user to be able to choose from IDs of available elements. Ideally, the Quickfix would acquire information from the elements being selected from, so the user would see not only their IDs but also certain values associated with them (to enable the correct selection). Not having found any hints in oXygen Help or in Quickfix documentation online, I suspect this isn't possible in the current version. (I'm using v19.0.) Am I wrong? If not, do any workarounds come to mind? Thanks, Wendell -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

3 3

Strange error with oxygen xml editor 19
by Bernhard Kleine 09 Aug '17

09 Aug '17

Today I tried to add a figure as well as a table in the author modus using special adding as XML and got both times a validation error. This error was not apparent when the very same figure or table was added while in text modus. The respective code in text mode is not different whether you add a figure or a table in author or text mode while validation sees something different. This is obviously a bug. Still in the test phase I have not enquired yet where to send bug reports. Regards Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

2 1

olink verification
by Bernhard Kleine 26 Jul '17

26 Jul '17

The olinking does not work: I have a document and glossar. The links to the glossar are via olink. At some time this has been working, but I do not know what I have changed so that it does work any further. Linking to the Glossartest.xml document or to the xml:id="Glossartest" did not work either. What is wrong? the respective error messages: > [xslt] : Warning! Failure reading > file:/K:/BuchprojektSpringer/xlm/olinkdb.xml Cause: > java.io.FileNotFoundException: K:\BuchprojektSpringer\xlm\olinkdb.xml > (Das System kann die angegebene Datei nicht finden) > [xslt] Olink error: could not open target database 'olinkdb.xml'. > [xslt] Error: unresolved olink: targetdoc/targetptr = > 'Glossartest/glo.Bsx'. I have seen a faintly similar thread about olinking, but that did not help me. BTW Glossartest.xml and newbooktest.xml validate just fine. Regards Bernhard spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

2 3

Fatal error when using refactoring action
by Lionel MOIZEAU 12 Jul '17

12 Jul '17

Hi, When I use a refactoring action such as Insert element, I get the following error ! Description java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace Severity Fatal System ID C:\Program Files\Oxygen XML Editor 19\refactoring\insert-element.xq<file:///C:\Program%20Files\Oxygen%20XML%20Editor%2019\refactoring\insert-element.xq> With the following trace. java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace at net.sf.saxon.query.StaticQueryContext.declareNamespace(StaticQueryContext.java:750) at net.sf.saxon.s9api.XQueryCompiler.declareNamespace(XQueryCompiler.java:365) at ro.sync.exml.xmlrefactory.c.c.d.p(Unknown Source) at ro.sync.exml.xmlrefactory.c.c.d.g(Unknown Source) at ro.sync.exml.xmlrefactory.c.d.k(Unknown Source) at ro.sync.exml.xmlrefactory.c.c.c(Unknown Source) at ro.sync.exml.xmlrefactory.c.c.b(Unknown Source) at ro.sync.exml.xmlrefactory.ui.i.j(Unknown Source) at ro.sync.exml.xmlrefactory.ui.i.k(Unknown Source) at ro.sync.exml.xmlrefactory.ui.i.i(Unknown Source) at ro.sync.exml.xmlrefactory.ui.i$_b.rhe(Unknown Source) at ro.sync.ui.application.nb.run(Unknown Source) I tried to add a <test> element under the <foo> element in a file like this: <?xml version="1.0" encoding="UTF-8"?> <root> <foo/> </root> Can you help me? Best regards, Lionel MOIZEAU Head of Technical Information Department L-Acoustics Tel : +33 1 69 63 23 99 www.l-acoustics.com<http://www.l-acoustics.com/>

3 4

[Ann] New maintenance build available for oXygen 19.0 (2017062918)
by Adrian Buza 05 Jul '17

05 Jul '17

Dear oXygen users, We announce the release of a new maintenance build (2017062918) 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#2017062918 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

Current ditamap editor variable
by Lionel MOIZEAU 05 Jul '17

05 Jul '17

Hi ! Is there a way to get the current ditamap as an editor variable ? By current map I mean the one open in the DITA Maps manager or selected in the Root map dropdown menu [cid:image001.png@01D2F598.961ECA00] It would be very helpful ! Best regards, Lionel MOIZEAU Head of Technical Information Department L-Acoustics Tel : +33 1 69 63 23 99 www.l-acoustics.com<http://www.l-acoustics.com/>

2 2

[oXygen XML Editor Blog] - DITA Linking Strategies
by oXygen XML Editor Blog 01 Jul '17

01 Jul '17

oXygen XML Editor Blog /////////////////////////////////////////// DITA Linking Strategies Posted: 30 Jun 2017 06:11 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/NkzlLkUcD9Q/dita-lin… This small tutorial is based on the "DITA Linking Strategies" presentations I made for the DITA Europe 2016 and DITA North America 2017 conferences. It's a general overview about DITA linking possibilities and best practices. Also, it's meant as a continuation of the DITA Reuse Strategies blog post. According to Wikipedia: "A link, is a reference to data that the reader can directly follow either by clicking, tapping, or hovering." Basically, we should regard linking as yet another form of content reuse, except that instead of presenting the content in place, it re-directs the end user to some other resource. I'll start with describing linking at DITA Map level. Map-Level Linking A DITA Map uses topic references to assemble the content of a publication. <topicref href="installation.dita"> <topicref href="server_installation.dita"/> <topicref href="client_side_installation.dita"/> </topicref> Depending on the output format, the topic reference may be a link in the table of contents for the XHTML-based outputs or it may be interpreted as a content reference for the PDF-based output that generates a single monolith document. So the role of the topicref is dual, it may sometimes be regarded as a link to a topic and sometimes as a content reference. Chunking DITA topic modules should be kept as small as possible, but sometimes the end user may need to read more than one topic to achieve a single task. So, when publishing to HTML-based outputs, you will end up asking yourself this question:Should I prefer larger HTML files or more links in the TOC? And you should always consider these two ideas: Links are disruptive. Ideally, users would not need to jump around in content to read the entire story they are searching for. Small topics that are usually read consecutively by the end user can probably get merged together. For example, if the installation of your product requires installing both a server-side and a client-side component, by using DITA chunking you can choose to have separate DITA topic modules for each of the installation procedures but merge the topics together in the web-based outputs:<map> <title>User Guide</title> <topicref href="installation.dita" chunk="to-content"> <topicref href="server_installation.dita" toc="no"/> <topicref href="client_side_installation.dita" toc="no"/> </topicref> </map> You can read more about chunking in the DITA 1.3 specification. The DITA Style Guide also has a good overview about why it is preferable to write small topics and then merge them together using the chunking mechanism. Topic-Level Linking Links that appear inside topics can be divided into various categories and I'll discuss each of these categories separately. In-Content Links In-content links are links added manually in the topic content:<li>See: <xref href="http://www.../" format="html" scope="external"/></li> You should keep in mind that this kind of link is disruptive to the reading experience because when end users encounter them, they need to decide weather to read further on or to follow the link. On the other hand, this may sometimes be a good thing. For example, one of the installation steps may require the end user to download a certain library from an external website before continuing. You can read more about links in general in the DITA 1.3 specification. The DITA Style Guide, written by Tony Self, also discourages the use of in-content links. Related Links Related links are placed at the end of the DITA topic and they allow the end user to explore additional resources after the current topic has been read.<related-links> <link href="http://tomcat.apache.org/" format="html" scope="external"/> </related-links> To minimize disruption when reading the content in general, the preferred place where to place links is at the end of the generated HTML page. You can read more about related links in the DITA 1.3 specification. Defining Related Links using Relationship Tables Related links do not need to be manually added at the end of each topic. You can define relationship tables in the DITA Map:<reltable> <relrow> <relcell> <topicref href="client_side_installation.dita"/> </relcell> <relcell> <topicref href="server_installation.dita"/> </relcell> </relrow> …….. </reltable> These tables can define associations between two or more topics, associations that automatically contribute to the related links creation in the generated HTML output. Here are some benefits of using relationship tables: A topic should have as few links as possible defined directly within. This makes it easier to reuse the topic in various contexts and keeps it as separate as possible for other parts of the DITA project, decreasing the possibility of broken links. By default, links defined in relationship tables are bi-directional, allowing users to land on any of the topics when searching for solutions and find their way to the related ones. Using a relationship table separates the task of writing topics from the task of finding relationships between topics. You can read more about relationship tables in the DITA 1.3 specification. The DITA Style Guide also recommends using relationship tables. Indirect Links (Key References) All the link samples we've look at so far have been direct links, links that point to the target using the @href attribute. Indirect links require two steps: Define a key in the DITA Map for the target.<keydef keys="client_installation" href="client_side_installation.dita"/> Use the defined key to reference the target resources.<xref keyref="client_installation"/> Here are some of the benefits of indirect linking: Offers the ability to reuse link target text and meta data. If you want to have custom text for a certain link, you can define it directly in the DITA Map:<keydef keys="dita_ot_website" href="http://www.dita-ot.org/" format="html" scope="external"> <topicmeta> <linktext>DITA Open Toolkit Web Site</linktext> </topicmeta> </keydef>and then add key references in all other places:<xref keyref="dita_ot_website"/> Easier conditional linking (including links to topics that sometimes may be missing). If you want your topic to link either to one target or to another depending on the filtering/profiling conditions, instead of adding profiling directly on the link, you can add the profiling conditions directly in the DITA Map: <topicref keys="slicing" href="slicing_vegetables_for_experts.dita" audience="expert"/> <topicref keys="slicing" href="slicing_vegetables_for_novices.dita" audience="novice"/> <keydef keys="slicing" audience="noLink"><topicmeta><keywords> <keyword>Slicing</keyword></keywords></topicmeta> </keydef>and then link to the key from each topic: <xref keyref="slicing"/> Easier link management. A good overview about all the outbound links in your project helps you maintain and control lists of allowed external web sites. With indirect references, you can define all references to external resources in a separate DITA Map. An example of a DITA project using indirect links to achieve separation of links by purpose can be found here: https://github.com/oxygenxml/dita-project-best-practices. Makes it easier to move/rename topics. When you move or rename a topic referenced via indirect links, only the link defined in the DITA Map will break, making it easier to fix broken links. There is an overview about indirect addressing on the DITA XML Org website. The DITA 1.3 specification also has a chapter about indirect links. Auto-Generated Links Until now, I've talked about manually added links, either in the topic or in relationship tables. Using the DITA @collection-type attribute, you can define relationships between parent and child topic references in the DITA Map, relationships that result in automatic links added between them: <topicref href="installation.dita" collection-type="sequence"> <topicref href="server_installation.dita"/> <topicref href="client_side_installation.dita"/> </topicref> There are 3 useful types of @collection-type values: Unordered - Links are generated from parent to children, and from children to parent. Family - Links are generated from parent to children, from children to parent, and from sibling to sibling. Sequence - Links are generated from parent to children, from children to parent, and from child to previous sibling (if applicable) and next sibling (if applicable). You can read more about auto-generated links in the DITA Style Guide. Conditional Links in Distinct Publications You may publish documentation for multiple products from the same DITA content. Also, you may want to have links point to various targets depending on the product for which you want to publish the documentation. Or, you may want to suppress links completely in certain publications. When using direct linking, you will need to profile each link depending on the publication:Find our more about slicing vegetables: <xref href="slicing_vegetables_for_experts.dita" audience="expert"/> <xref href="slicing_vegetables_for_novices.dita" audience="novice"/>.With indirect links, you can define the profiling attributes as DITA Map level: <topicref keys="slicing" href="slicing_vegetables_for_experts.dita" audience="expert"/> <topicref keys="slicing" href="slicing_vegetables_for_novices.dita" audience="novice"/>and thus, simplify the reference made in the topic content:Find our more about slicing vegetables: <xref keyref="slicing/>. Conditional Links in the Same PublicationUsing DITA 1.3 key scopes, you can reuse a topic multiple times in a DITA Map and have each referenced topic contain links to various target topics. For example, if my preparing_vegetables.dita topic has a link:<link keyref="slicing"/>you can define various key scopes in the DITA Map that bind the "slicing" key to various targets: <topichead navtitle="Cooking for Experts" keyscope="expert"> <topicref href="preparing_vegetables.dita" keys="preparing"/> <topicref href="slicing_vegetables_for_experts.dita" keys="slicing"/> </topichead> <topichead navtitle="Cooking for Novices" keyscope="novice"> <topicref href="preparing_vegetables.dita" keys="preparing"/> <topicref href="slicing_vegetables_for_novices.dita" keys="slicing"/> </topichead>This previous blog post contains more details about key scopes. Link Text When linking to an external resource or to a DITA topic or element, the publishing engine will attempt to deduce the link text from the target context. For example, the link to a DITA topic or element that contains a <title> will use that title as the link text. The link to an external resource (for example to http://www.oxygenxml.com) will, by default, use the HTTP location as the link text. You can also customize each link text individually. So, ask yourself this question: Should I leave the link text to be automatically computed or should I set a more friendly text? For internal links to elements that have a title, in general it is more flexible to not set a custom text and let the publishing engine decide one for you. For external links, you should usually specify your custom link text. Should I Link or Should I Reuse? Suppose you want to bring a certain paragraph, note, or section to the end user's attention. If that particular target element is not very large, you should always reuse it (using a content reference) instead of linking to it. Conclusions As with all large projects, managing links in a growing DITA project can be problematic, so you need to become organized. As an overview of what we've discussed so far, I suggest the following best practices: Linking is a form of reuse so: Reuse small pieces of content instead of linking to them Avoid too much linking (linking is disruptive) Use indirect links. It will allow you to reuse link text and make profiling/filtering easier while giving you a better overview of the outbound links for your project. If you want to experiment with the various linking strategies I discussed above, you can find some samples here: https://www.oxygenxml.com/forum/files/linking-strategies-samples.zip. -- 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] - 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