- oXygen-user - www.oxygenxml.com

duplicate element
by Roderik Dernison 25 Nov '14

25 Nov '14

Hi, I've created my own extension of DITA. Amongst others I have added an element "predicate", like this: <xs:element name="predicate"> <xs:annotation> <xs:documentation>A <predicate> element marks the predicate, e.g. GROOT(Jan). (TP-ELEMENT)</xs:documentation> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:extension base="predicate.class"> <xs:attribute ref="class" default="- ling-d/pred "/> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <xs:complexType name="predicate.class" mixed="true"/> Now when I create a new ling topic, oXygen tells me E [Xerces] cos-nonambig: predicate and predicate (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. My lingGrp.xsd contains: <xs:group name="predicate"> <xs:sequence> <xs:choice> <xs:element ref="predicate" /> </xs:choice> </xs:sequence> </xs:group> My lingDomain.xsd contains: <xs:group name="ling-d-pred"> <xs:choice> <xs:group ref="predicate" /> </xs:choice> </xs:group> And my ling.xsd contains: <xs:group ref="ling-d-pred" /> No other references are made to predicate. What am I doing wrong? Kind regards, Ing. Roderik Dernison ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ----------------------------------------------------------

2 1

Transforming without Entity placeholders
by Sascha Manns 19 Nov '14

19 Nov '14

Hello list, i have some XML files from a DocBook handbook project. The files are chunked into different chapter files. Now i would like to transform each chapter file that it outputs the same docbook code but with solved entity solution. So the result should be a clean DocBook file without entity placeholders. Has anyone done this already? Greetings Sascha -- Yours sincerly Sascha Manns

2 3

never mind on the ant build script question
by Tom Johnson 18 Nov '14

18 Nov '14

Never mind on the ant build script question. My temp folder didn't get deleted, so the script was only processing the files there. Tom --------------------- 801-822-2241 blog: idratherbewriting.com twitter: tomjohnson

2 1

Feature request - XML format preferences
by David Sewell 18 Nov '14

18 Nov '14

This is not very important, but if it would be easy to implement I think it is worth doing: In oXygen Preferences, under "Editor - Format - XML", in the section "Elements Spacing", the available options are "Add" and "Remove. Could "Edit" be added? David -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: dsewell(a)virginia.edu Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/

2 1

ant build.xml script processes only 10 items at a time?
by Tom Johnson 17 Nov '14

17 Nov '14

I have a question about the build.xml script located inside this folder: [Oxygen install directory]/Applications/oxygenAuthor_161/frameworks/dita/DITA-OT/plugins/h2d. When I have an HTML file in this directory and I run "ant" from the Terminal, the build.xml script kicks off and converts the first 10 HTML files to DITA topics. I have many more HTML files that I want included in the auto-conversion (more than 1). How can I have the build.xml script convert *all* of the HTML files in that directory? Tom --------------------- 801-822-2241 blog: idratherbewriting.com twitter: tomjohnson

1 0

get an ID on a page?
by Tom Johnson 14 Nov '14

14 Nov '14

Is there any way to get an ID on a page using DITA and transforming with the DITA OT? For example, I want to add something like this: <p id="toc"/> Even if I hack the Oxygen source to allow IDs to pass through, as I described here ( http://idratherbewriting.com/wpdita/toc_publishing/jquery_side_panel/) the ID gets prepended with the topic ID. This makes it difficult to trigger the jQuery script, which has a trigger of #toc. Each page's p id will change based on the page's topic ID. I tried using a class with the jquery plugin instead, but it doesn't seem to work. This is the TOC plugin: http://fuelyourcoding.com/scripts/toc/index.html. Thanks, Tom --------------------- 801-822-2241 blog: idratherbewriting.com twitter: tomjohnson

2 3

find references to topic before deleting them?
by Roderik Dernison 13 Nov '14

13 Nov '14

Hi, How can I quickly find references to a topic (in a ditamap or topics contained in that ditamap), before I delete it or remove it from a ditamap? Vriendelijke groet, Ing. Roderik Dernison Programmeur/ontwikkelaar INL * Schatkamer van de Nederlandse Taal Matthias de Vrieshof 2 * Kamer 106a * 2311 BZ Leiden Tel. +31 (0)71 527 2491 * www.inl.nl<http://www.inl.nl/> ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ----------------------------------------------------------

2 1

Oxygen Framework Builder
by Claudius Teodorescu 05 Nov '14

05 Nov '14

Hi, I developed an automatic builder for Oxygen frameworks which allows user to describe framework's behaviour by using only XQuery, HTML, and CSS, and automatically generate the framework archive ready to be deployed. A short tutorial can be found at [1]. I hope this plugin will be helpful. Claudius [1] http://kuberam.ro/oxygen-addon-builder/

1 0

IS_FEEDBACK_ENABLED
by Mary Anthony 04 Nov '14

04 Nov '14

Hi, I am using Oxygen 16.1 we use the Webhelp plugin to create help for our product and documentation on our public website. The look and feel of the help versus the public website is very different. In the help we use the standard search that comes with the plugin but on the website we will be using our website search. To transform our source using the Webhelp with Feedback. I'd like to use a <xsl:if> to test whether the generation is for Webhelp or Webhelp with feedback. The problem is I can't see to find a parameter to test against. I tried using IS_FEEDBACK_ENABLED but it depends on WEBHELP_PRODUCT_ID and that returns and error: *Variable WEBHELP_PRODUCT_ID has not been declared (or its declaration is not in scope)* Anyone know of a parameter or variable that will work as a test? (I could also use the editor variables if someone could give me an examples of accessing one from within an XSL stylesheet) Thanks, Mary

2 1

List of separate Oxygen plugin/framework projects
by Radu Coravu 04 Nov '14

04 Nov '14

Hi everybody, I'm trying to put together a list of separate projects which develop Oxygen plugins and frameworks: > http://blog.oxygenxml.com/2014/11/public-hosted-oxygen-plugin-and.html If anybody else knows projects which can be added to the list, please tell us. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

Re: [oXygen-user] integrate Oxygen output into build process?
by Sorin Ristache 29 Oct '14

29 Oct '14

Hello Tom, Please let us know if we can further help you. I am not particularly familiar with the Mercurial event hooks like post commit, but I suppose you would just plug into the post commit hook a shell script like the dita.sh attached to my previous message. I could find a list of the Mercurial hooks here: http://hgbook.red-bean.com/read/handling-repository-events-with-hooks.html http://hgbook.red-bean.com/read/handling-repository-events-with-hooks.html#… Best regards, Sorin <oXygen/> XML Editor http://www.oxygenxml.com Tom Johnson wrote: > Sorin, thanks, this is just the information I was looking for. Let me > process it and see if I can set something up. Ideally I want to just > fire everything off from the command line when I commit. > > Tom > > --------------------- > 801-822-2241 > blog: idratherbewriting.com <http://idratherbewriting.com> > twitter: tomjohnson > > On Tue, Oct 28, 2014 at 2:16 AM, Sorin Ristache <sorin(a)sync.ro > <mailto:sorin@sync.ro>> wrote: > > Hi Tom, > > In the Oxygen application a transformation can be started only > manually, for example with an action available on a toolbar or a > menu or with a custom Author mode extension action. A transformation > can be started automatically as in your case (registered as a hook > on a version control event) only outside the Oxygen application, as > an independent Java process or as a CLI shell command. > > For DITA files we provide only the WebHelp transformation as a > independent process (outside the Oxygen application). It is a > DITA-OT plugin which can be integrated in a DITA-OT > 1.6.x/1.7.x/1.8.x installation and which is available as a separate > product on the Oxygen website, which means it requires a separate > purchased license. The WebHelp pages created by this DITA-OT plugin > are the same as the ones created in the Oxygen application applied > to the same DITA files. I attach a README file with the DITA-OT > integration instructions and also a sample script for starting the > WebHelp transformation from a command line. If you need more details > please let me know. > > For other DITA transformations started outside the Oxygen > application I suggest running the built-in transformations which > come with the DITA-OT kit and which can generate PDF output, Windows > Help output, Eclipse Help output, etc. The DITA-OT documentation > includes instructions for starting a DITA transformation from a > command line: > > https://dita-ot.github.io/1.8/__readme/tranforming-dita-__content.html > <https://dita-ot.github.io/1.8/readme/tranforming-dita-content.html> > > > Best regards, > Sorin > > <oXygen/> XML Editor > http://www.oxygenxml.com > > > Mary Anthony wrote: > > Hi Tom, > > Most commercial companies would use a continuous integration > tool such as Bamboo, Hudson, or Buildbot to kick a build on > commit. I've used Bamboo myself to build such a system for > Javadoc and Webworks. Depends on your resources. > > A Mercurial post commit hook might be the way for you to go. I > quick google of "mercurial post commit hook build" gave me > several results. > Good luck, > > Mary > > On Mon, Oct 27, 2014 at 11:27 AM, Tom Johnson > <tomjohnson1492(a)gmail.com <mailto:tomjohnson1492@gmail.com> > <mailto:tomjohnson1492@gmail.__com > <mailto:tomjohnson1492@gmail.com>>> wrote: > > Does anyone know how to tell Oxygen to initiate > transformations when > I commit to a version control repository, specifically > Mercurial? > Just like Javadocs gets auto-kicked off when developers commit > source files, I'd like to do the same with Oxygen and my > DITA files. > > Tom > > > > INTRODUCTION > ============= > > This directory contains the Oxygen Webhelp plugin version > @@VERSION@@ for DITA Open Toolkit. The Webhelp output files are > exactly the same as for the DITA Webhelp transformations executed > inside the Oxygen XML Editor @@VERSION@@ application. The plugin > must be first integrated in the DITA Open Toolkit for adding the > following transformation types to the DITA Open Toolkit: > > webhelp - The Webhelp transformation for desktop output > > webhelp-feedback - The Webhelp transformation for desktop output > with a section for > user comments at the bottom of each XHTML output > page > > webhelp-mobile - The Webhelp transformation for mobile devices output > > > More details about all the Webhelp transformations are available on > the Oxygen website: > > http://www.oxygenxml.com/xml_editor/webhelp.html > > > LICENSE TERMS > ============== > > The license terms of the Oxygen Webhelp distribution are set forth > in the file EULA_Webhelp.txt located in the same directory as this > README file. > > > REQUIREMENTS > ============= > > The requirements of the Oxygen Webhelp plugin for DITA Open Toolkit > are the following: > > - Java Virtual Machine 1.6 or later > > - DITA Open Toolkit 1.6.x, 1.7.x or 1.8.x (the 'full easy install' > distribution) > > - Saxon 9.1.0.8 processor > > > INSTALL THE WEBHELP PLUGIN IN DITA-OT > ====================================== > > 1. Download and install a Java Virtual Machine 1.6 or later and a > DITA Open Toolkit 1.6.x, 1.7.x or 1.8.x (the 'full easy install' > distribution) if you don't have them already installed: > > http://www.oracle.com/technetwork/java/javase/downloads/index.html > > http://sourceforge.net/projects/dita-ot/files/DITA-OT%20Stable%20Release/ > > 2. Copy the parent directory of this README file, called > 'com.oxygenxml.webhelp', and the directory called > 'com.oxygenxml.highlight', in the 'plugins' subdirectory of the > install directory of the DITA Open Toolkit where you want to run the > Oxygen Webhelp transformation. > > 3. Run the following command in the directory of DITA Open Toolkit: > > ant -f integrator.xml > > The integrator.xml file is located in the DITA Open Toolkit install > directory. This will add two plugins to DITA-OT: Oxygen Webhelp > plugin (directory com.oxygenxml.webhelp) and Oxygen highlight plugin > (directory com.oxygenxml.highlight). > > 4. Download and unzip on your computer the saxonb9-1-0-8j.zip file > containing the Saxon 9.1.0.8 processor from: > > http://sourceforge.net/projects/saxon/files/Saxon-B/9.1.0.8/ > > > REGISTER YOUR OXYGEN LICENSE IN THE WEBHELP PLUGIN > =================================================== > > Create a text file called 'licensekey.txt' in the directory > [DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp. Copy and paste > in this file your Oxygen Scripting license key which you purchased > for your Oxygen Webhelp plugin. The Webhelp transformation will read > the Oxygen license key from this file. If this file does not exist > or it contains an invalid license key an error message will be > displayed. > > > RUN THE WEBHELP TRANSFORMATION in DITA-OT > ========================================== > > The following command will run the Webhelp transformation. This > command is available also as a script file in the same directory as > this README file, called dita.sh for Unix/Linux based system and > dita.bat for Windows systems. Just set the correct values of the > script variables at the beginning at the script file before calling > the script in an automated process or from a command line. > > > "[JVM-install-dir]/bin/java" -Xmx512m -classpath > "[DITA-OT-install-dir]/tools/ant/lib/ant-launcher.jar" > "-Dant.home=[DITA-OT-install-dir]/tools/ant" > org.apache.tools.ant.launch.Launcher -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/xercesImpl.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/xml-apis.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/xml-apis-ext.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/dost-patches.jar" > -lib "[DITA-OT-install-dir]" -lib "[DITA-OT-install-dir]/lib" -lib > "[Saxon-9.1.0.8-dir]/saxon9.jar" -lib > "[Saxon-9.1.0.8-dir]/saxon9-dom.jar" -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/license.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/log4j.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/resolver.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/ant-contrib-1.0b3.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/lucene-analyzers-common-4.0.0.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/lucene-core-4.0.0.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/xhtml-indexer.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.highlight/lib/xslthl-2.1.0.jar" > -lib > "[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/lib/webhelpXsltExtensions.jar" > -f "[DITA-OT-install-dir]/build.xml" > "-Dtranstype=[webhelp.transtype]" "-Dbasedir=[DITA-map-base-dir]" > "-Doutput.dir=[DITA-map-base-dir]/out/[webhelp.transtype]" > "-Ddita.temp.dir=[DITA-map-base-dir]/temp/[webhelp.transtype]" > "-Dargs.filter=[DITAVAL-dir]/[file.ditaval]" > "-Ddita.input.valfile=[DITAVAL-dir]/[file.ditaval]" > "-Dargs.hide.parent.link=no" "-Ddita.dir=[DITA-OT-install-dir]" > "-Dargs.xhtml.classattr=yes" > "-Dargs.input=[DITA-map-base-dir]/[input-DITA-map-file.ditamap]" > "-Dwebhelp.skin.css=[DITA-OT-install-dir]/plugins/com.oxygenxml.webhelp/predefined-skins/dita/oxygen/skin.css" > "-DbaseJVMArgLine=-Xmx384m" > > > where: > > - [JVM-install-dir] must be replaced with the path of the Java > Virtual Machine install directory > > - [DITA-OT-install-dir] must be replaced with the path of the DITA > Open Toolkit install directory > > - [Saxon-9.1.0.8-dir] must be replaced with the path of the > directory were the Saxon 9 archive file (saxonb9-1-0-8j.zip) was > unzipped > > - [webhelp.transtype] must be one of the values: webhelp, > webhelp-feedback, webhelp-mobile > > - [DITA-map-base-dir] must be replaced with the path of the > directory of the input DITA map file > > - [DITAVAL-dir] must be replaced with the path of the directory of > [file.ditaval] which sets the DITAVAL input filter > > - [file.ditaval] must be replaced with the name of the DITAVAL input > filter file that will be applied to the input map > > - [input-DITA-map-file.ditamap] must be replaced with the name of > the input DITA map file > > > The '-Dargs.filter' and '-Ddita.input.valfile' parameters are optional. > > The Webhelp output pages are generated in the directory that is set > in the parameter 'output.dir', by default > [DITA-map-base-dir]/out/[transtype]. > > The -Dwebhelp.skin.css parameter sets a skin CSS for the Webhelp > output pages. In the above example the predefined skin called > "Oxygen" was set. A set of predefined skins come with the Webhelp > kit in the directory predefined-skins. For building your own custom > skin please use the Webhelp Skin Builder from: > > http://www.oxygenxml.com/webhelp-skin-builder/ > > A company logo image can be optionally added to the main title in > the header area of the Webhelp output pages with the parameter: > -Dwebhelp.logo.image. A URL can be optionally set for the logo image > to point to using the parameter: -Dwebhelp.logo.image.target.url. > > > CONFIGURE DATABASE (ONLY FOR WEBHELP WITH FEEDBACK TRANSFORMATIONS) > ==================================================================== > > For the transformations that generate Webhelp pages allowing user > comments (webhelp-feedback) the database with the user comments must > be configured. This is done by opening the following file in a Web > browser and following the installation instructions from this file: > > [DITA-map-base-dir]/out/[transtype]/oxygen-webhelp/resources/installation.html > > > OTHER PARAMETERS OF WEBHELP TRANSFORMATION > =========================================== > > The Webhelp parameters that can be appended to the command line that > runs the Webhelp transformation: > > -Dwebhelp.copyright (text string value) - The copyright note that > will be added in the footer of the Table of Contents frame (the left > side frame of the WebHelp output). > > -Dwebhelp.footer.include (possible values: 'yes', 'no') - If set > to 'no' no footer is added to the Webhelp pages. If set to 'yes' and > the webhelp.footer.file parameter has a value, then the content of > that file is used as footer in each Webhelp output page. If > webhelp.footer.file has no value then the default Oxygen footer is > inserted in each Webhelp page. > > -Dwebhelp.footer.file (file path of XHTML file) - Specifies the > location of a well-formed XHTML file containing your custom footer > for the document body. Corresponds to XSLT parameter > WEBHELP_FOOTER_FILE. The fragment must be well-formed XHTML, with a > single root element. Common practice is to place all content into a > <div>. > > -Dwebhelp.product.id <http://Dwebhelp.product.id> (text string > value, required for the transformations with user feedback) - A > short name for the documentation target (product). All user comments > that will be posted in the Webhelp output pages and will be added in > the comments database on the server will be bound to this product > ID. Examples: 'mobile-phone-user-guide', 'hvac-installation-guide', > etc. Documentation for multiple products can be deployed on the same > server. > > -Dwebhelp.product.version (text string value, required for the > transformations with user feedback) - The documentation version > number, for example: 1.0, 2.5, etc. New user comments are bound to > this version. Multiple documentation versions can be deployed on the > same server. > > > Other DITA-OT parameters that are needed for a customization of the > Webhelp transformation can be appended to the above command line > following the model of the -D parameters like > 'args.hide.parent.link' and 'args.xhtml.classattr'. For example the > 'args.hdr' parameter can be appended in the form: > > "-Dargs.hdr=/path/to/directory/of/header-file.html" > > where [dir-of-header-file] will be replaced with the path of the > directory containing the header file.

1 0

How to transfer Oxygen from an old computer to a new one?
by Jean-Luc Chevillard 28 Oct '14

28 Oct '14

Dear list members, I have just discovered the existence of this list this morning and it is just possible that the question I am having has been asked one hundred times, in which case I apologize in advance. What is the correct procedure for transferring Oxygen from one computer to another one. Do I have to uninstall from the old computer and reinstall on the new? (as is the case for instance for Adobe Creative Suite). What happens if the old computer has become so unstable that it is difficult to access? I am having all the Oxygen licence numbers safely stored on some external hard disk. Thanks for any pointer. -- Jean-Luc Chevillard (CNRS, Paris)

2 1

integrate Oxygen output into build process?
by Tom Johnson 28 Oct '14

28 Oct '14

Does anyone know how to tell Oxygen to initiate transformations when I commit to a version control repository, specifically Mercurial? Just like Javadocs gets auto-kicked off when developers commit source files, I'd like to do the same with Oxygen and my DITA files. Tom --------------------- 801-822-2241 blog: idratherbewriting.com twitter: tomjohnson

3 2

Transforming scenario wiki
by Sascha Manns 24 Oct '14

24 Oct '14

Hello list, actually i'm trying to use a transforming scenario for docbook. It should use Docbook 4.4, 4.5 or 5 and export it to a wiki syntax. Ideally it should transform into the XWiki-Syntax (http://platform.xwiki.org/xwiki/bin/view/Main/XWikiSyntax) but if anyone already has done this with a similar syntax i can try to fix the rest of the syntax by myself. Has anyone tried it out? -- Yours sincerly Sascha Manns

2 1

[Ann] New maintenance build available for oXygen 16.1 (2014102117)
by Oxygen XML Editor Support (Adrian Buza) 24 Oct '14

24 Oct '14

Dear oXygen users, We announce the release of a new maintenance build (2014102117) for oXygen 16.1 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2014102117 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

Pick lists in Author mode
by Wendell Piez 17 Oct '14

17 Oct '14

Hi, I think the forms-like editing in Author mode is fantastic. One thing I like being able to do is having a pull-down listing valid values for element or attribute contents. One thing I have a need for -- to have the choice of valid values specified dynamically, in the document itself or close by. I can specify a rule in Schematron that checks whether arbitrary (key) relations hold in a document (or across two or more documents), but I wonder how I can get oXygen to read the permissible values (however they are defined and constrained, for example as a set of attribute values in metadata) and pop them up in a picklist. Essentially this is like an ID/IDREF requirement, only generalized, and specifiable using XPath. Is there any hope for me? Could I sneak some kind of function into the CSS that oXygen uses to configure the pick lists, and achieve this, using XPath? Regards, Wendell -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

3 2

Errors (Java) after update 16.0 -> 16.1
by Andreas Wagner 16 Oct '14

16 Oct '14

Hi all, I have upgraded to 16.1 and now I have some errors. There have also been changes to my Java environment but rolling these back and an alternative attempt with Oracle JDK 8 amounted to the same, so I think it's oXygen. Also, I can't find a download link to 16.0 anymore, and I need functionality not present in 15.2... The first error is when opening a WebDAV connection to an eXist database, I get a dialog "Could not initialize class org.apache.http.impl.conn.ManagedHttpClientConnectionFactory" Trying to open the same database with xmldb, I am asked to "check database configuration". The second error is a crash in the SVN client both launched as standalone and launched from within oXygen. The error message is attached at the bottom. In oXygen editor 16.1 for windows, everything is fine. I have tried with openJDK 7 and 8 and Oracle JDK 8. Even below the error message, I paste the system properties from the about box. Any help is appreciated... Andreas Die Anwendung hat einen Fehler festgestellt, der nicht automatisch behoben werden kann. Es ist möglich, dass der Fehler unkritisch ist und dass die Anwendung normal weiterläuft. Falls sich die Anwendung instabil verhält und nicht mehr normal geschlossen werden kann, können Sie den „Force Quit“ Button aus diesem Dialog verwenden. Beachten Sie, dass dann alle ungesicherten Änderungen in den geöffneten Dokumenten verloren gehen. Hier sind die Fehlerdetails: [ AWT-EventQueue-0 ] - java.lang.NoSuchFieldError: FOREIGN_COPY_BEGIN java.lang.NoSuchFieldError: FOREIGN_COPY_BEGIN at ro.sync.svn.f.ad.<init>(Unknown Source) at ro.sync.svn.j$_b.<init>(Unknown Source) at ro.sync.svn.j.<init>(Unknown Source) at ro.sync.svn.r.<init>(Unknown Source) at ro.sync.svn.SVNMainFrame.<init>(Unknown Source) at ro.sync.svn.SVNMainFrame.uul(Unknown Source) at ro.sync.exml.e.c$18$1.run(Unknown Source) at ro.sync.ui.l$1.run(Unknown Source) at java.awt.event.InvocationEvent.dispatch(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$200(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) at ro.sync.ui.l.e(Unknown Source) at ro.sync.ui.l.f(Unknown Source) at ro.sync.ui.l.b(Unknown Source) at ro.sync.exml.e.c$18.gzc(Unknown Source) at ro.sync.ui.application.d.m.actionPerformed(Unknown Source) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.AbstractButton.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$200(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue$4.run(Unknown Source) at java.awt.EventQueue$4.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) apple.awt.showGrowBox true apple.awt.window.position.forceSafeCreation true apple.laf.useScreenMenuBar true awt.dnd.drag.threshold 5 awt.toolkit sun.awt.X11.XToolkit awt.useSystemAAFontSettings on com.apple.macos.smallTabs true com.apple.macos.useScreenMenuBar true com.apple.mrj.application.apple.menu.about.name Oxygen com.oxygenxml.editor.home.url file:/opt/Oxygen%20XML%20Editor/ com.oxygenxml.editor.lib.dir /opt/Oxygen XML Editor/lib com.oxygenxml.editor.plugins.dir /opt/Oxygen XML Editor/plugins com.oxygenxml.is.eclipse.plugin false com.oxygenxml.language German com.oxygenxml.tree.readonly false exe4j.moduleName /opt/Oxygen XML Editor/oxygen16.1 file.encoding UTF-8 file.encoding.pkg sun.io file.separator / i4j.vpt true install4j.appDir /opt/Oxygen XML Editor/ install4j.exeDir /opt/Oxygen XML Editor/ install4j.jvmDir /opt/Oxygen XML Editor/jre install4j.launcherId 19 install4j.swt false java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.printerjob sun.print.PSPrinterJob java.class.path /opt/Oxygen XML Editor/.install4j/i4jruntime.jar:/opt/Oxygen XML Editor/lib/oxygen.jar java.class.version 51.0 java.endorsed.dirs /opt/Oxygen XML Editor/jre/lib/endorsed java.ext.dirs /opt/Oxygen XML Editor/jre/lib/ext:/usr/java/packages/lib/ext java.home /opt/Oxygen XML Editor/jre java.io.tmpdir /tmp java.library.path :/opt/java/jre/lib/amd64:/opt/java/jre/lib/amd64/server:/opt/java/jre/lib/amd64:/opt/java/jre/lib/amd64/server:/opt/java/jre/lib/amd64:/opt/java/jre/lib/amd64/server:/opt/java/jre/lib/amd64:/opt/java/jre/lib/amd64/server:/usr/java/packages/lib/i386:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_55-b13 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_55 java.vm.info mixed mode java.vm.name Java HotSpot(TM) Client VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.55-b03 javaplugin.proxy.config.type direct javax.xml.parsers.DocumentBuilderFactory org.apache.xerces.jaxp.DocumentBuilderFactoryImpl javax.xml.parsers.SAXParserFactory org.apache.xerces.jaxp.SAXParserFactoryImpl jide.tabs.dnd.drag.threshold 40 jna.platform.library.path /usr/lib:/lib line.separator \n org.eclipse.emf.ecore.EPackage.Registry.INSTANCE org.eclipse.emf.ecore.impl.EPackageRegistryImpl org.xml.sax.driver org.apache.xerces.parsers.SAXParser os.arch i386 os.name Linux os.version 3.16.4-1-ARCH path.separator : require.signed.ucf.jars false sun.arch.data.model 32 sun.awt.enableExtraMouseButtons true sun.awt.keepWorkingSetOnMinimize true sun.awt.nopixfmt true sun.boot.class.path /opt/Oxygen XML Editor/jre/lib/resources.jar:/opt/Oxygen XML Editor/jre/lib/rt.jar:/opt/Oxygen XML Editor/jre/lib/sunrsasign.jar:/opt/Oxygen XML Editor/jre/lib/jsse.jar:/opt/Oxygen XML Editor/jre/lib/jce.jar:/opt/Oxygen XML Editor/jre/lib/charsets.jar:/opt/Oxygen XML Editor/jre/lib/jfr.jar:/opt/Oxygen XML Editor/jre/classes sun.boot.library.path /opt/Oxygen XML Editor/jre/lib/i386 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command com.install4j.runtime.launcher.Launcher launch ro.sync.exml.Oxygen true false /opt/Oxygen XML Editor/error.log /opt/Oxygen XML Editor/output.log true true false true true 0 0 20 20 Arial 0,0,0 8 500 version 16.1 20 40 Arial 0,0,0 8 500 -1 sun.java.launcher SUN_STANDARD sun.java2d.noddraw true sun.jnu.encoding UTF-8 sun.management.compiler HotSpot Client Compiler sun.os.patch.level unknown sun.swing.enableImprovedDragGesture true svnkit.http.methods Basic,Digest,NTLM svnkit.http.ntlm jna svnkit.upgradeWC false svnkit.wc.17 true svnkit.wc.17only true swing.aatext true swing.crossplatformlaf com.sun.java.swing.plaf.gtk.GTKLookAndFeel swing.defaultlaf com.sun.java.swing.plaf.gtk.GTKLookAndFeel user.country DE user.dir /home/wagner user.home /home/wagner user.language de user.name wagner user.timezone Europe/Berlin -- 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 Grüneburgplatz 1 60629 Frankfurt am Main Tel. +49 (0)69/798-32774 Fax +49 (0)69/798-32794

2 2

Support for Markdown Authoring?
by Eliot Kimber 12 Oct '14

12 Oct '14

Now that I'm doing a lot of work with GitHub repos I'm writing a lot of markdown documents (readmes, wiki pages, etc.). Oxygen doesn't appear to have any out-of-the-box knowledge of markdown as a file type. I realize markdown files are fundamentally just text, but it would be nice if ".md" files were at least recognized as markdown files and there as a built-in file->new type of markdown. Cheers, E. ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

5 7

Re: [oXygen-user] oXygen-user Digest, Vol 48, Issue 8
by Cwiklowski, Don 10 Oct '14

10 Oct '14

Roderick, I'm not sure what it is you want the @rev to produce, but if you want create a revbar, or something similar, you can create a ditaval file that will produce a specific result based on the value you put it for @rev. That way, if you have three different specified values, you could have three different results. And if a writer goes against this, nothing will display. A transformation scenario can then be created to use the ditaval. Doing this will require no development for schema or xslt. In the dita spec look for Ditaval elements, and Flagging. It works great. You may have to do a bit of development if you're trying to impose a date to display, or something other than a revision bar, or stylized text. Don Cwiklowski, Jr. Senior 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 Please think of the environment before printing this email. -----Original Message----- From: oxygen-user-bounces(a)oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of oxygen-user-request(a)oxygenxml.com Sent: Friday, October 10, 2014 12:00 PM To: oxygen-user(a)oxygenxml.com Subject: oXygen-user Digest, Vol 48, Issue 8 Send oXygen-user mailing list submissions to oxygen-user(a)oxygenxml.com To subscribe or unsubscribe via the World Wide Web, visit http://www.oxygenxml.com/mailman/listinfo/oxygen-user or, via email, send a message with subject or body 'help' to oxygen-user-request(a)oxygenxml.com You can reach the person managing the list at oxygen-user-owner(a)oxygenxml.com When replying, please edit your Subject line so it is more specific than "Re: Contents of oXygen-user digest..." Today's Topics: 1. rev attribute in topircref (Roderik Dernison) 2. Re: rev attribute in topircref (Oxygen XML Editor Support (Radu Coravu) ) ---------------------------------------------------------------------- Message: 1 Date: Fri, 10 Oct 2014 09:35:31 +0200 From: "Roderik Dernison" <rdernison(a)xs4all.nl> To: oxygen-user(a)oxygenxml.com Subject: [oXygen-user] rev attribute in topircref Message-ID: <067e5510ed69e5c8a671d9142be5cff5.squirrel(a)webmail.xs4all.nl> Content-Type: text/plain;charset=iso-8859-1 Hi, I'm trying to modify the schema for the ditamap. I need to set three fixed values on the rev attribute of the topicref element in a ditamap. What element in what xsd file should I edit to accomplish this? -- Kind regards, Roderik Dernison ------------------------------ Message: 2 Date: Fri, 10 Oct 2014 11:22:28 +0300 From: "Oxygen XML Editor Support (Radu Coravu) " <support(a)oxygenxml.com> To: oxygen-user(a)oxygenxml.com Subject: Re: [oXygen-user] rev attribute in topircref Message-ID: <54379744.7030404(a)oxygenxml.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi Roderik, Instead of modifying directly the XSDs I would advise you to define a Subject Scheme Map which imposes those three values on the @rev attribute, the validation in Oxygen should report errors when the attribute has other values. > http://www.oxygenxml.com/doc/ug-oxygen/#topics/subject-scheme-map.html > http://www.oxygenxml.com/demo/DITA_Subject_Scheme.html Basically your Subject Scheme map would have the content: > <!DOCTYPE subjectScheme PUBLIC "-//OASIS//DTD DITA Subject Scheme > Map//EN" "map.dtd"> <subjectScheme> > <subjectHead> > <subjectHeadMeta> > <navtitle>Rev controlled attr values</navtitle> > </subjectHeadMeta> > </subjectHead> > <hasInstance> > <subjectdef keys="revSbjKey"> > <subjectdef keys="value1"> > <topicmeta> > <navtitle>First Value</navtitle> > </topicmeta> > </subjectdef> > <subjectdef keys="value2"> > <topicmeta> > <navtitle>First Value</navtitle> > </topicmeta> > </subjectdef> > <subjectdef keys="value3"> > <topicmeta> > <navtitle>First Value</navtitle> > </topicmeta> > </subjectdef> > </subjectdef> > </hasInstance> > <enumerationdef> > <attributedef name="rev"/> > <subjectdef keyref="revSbjKey"/> > </enumerationdef> > </subjectScheme> and it would be referenced in the main DITA Map like: > <topicref href="revSbjSchemeVals.ditamap" format="ditamap" > type="subjectScheme"/> As long as the main DITA Map will be opened in the DITA Maps Manager view Oxygen should also detect and propose those values when you use the "Edit Profiling Attributes" action or when editing the values in the Attributes view. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 10/10/2014 10:35 AM, Roderik Dernison wrote: > Hi, > > I'm trying to modify the schema for the ditamap. I need to set three > fixed values on the rev attribute of the topicref element in a ditamap. > What element in what xsd file should I edit to accomplish this? > > ------------------------------ _______________________________________________ oXygen-user mailing list oXygen-user(a)oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user End of oXygen-user Digest, Vol 48, Issue 8 ****************************************** 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.

1 0

rev attribute in topircref
by Roderik Dernison 10 Oct '14

10 Oct '14

Hi, I'm trying to modify the schema for the ditamap. I need to set three fixed values on the rev attribute of the topicref element in a ditamap. What element in what xsd file should I edit to accomplish this? -- Kind regards, Roderik Dernison

2 1

Detach a tab?
by Tom Johnson 09 Oct '14

09 Oct '14

How do you detach a tab? It seems like I'm inadvertently detaching tabs all the time when I don't want to. But I can't quite figure out exactly what I'm doing to detach the tab. I actually want to disable tab detaching. Sent from my iPhone

3 6

[ann] oXygen XML Editor 16.1
by George Bina 08 Oct '14

08 Oct '14

Hi everyone! We are happy to announce a new release of oXygen XML Editor, version 16.1! The full details of the new version can be read from http://oxygenxml.com/whatisnew16.1.html and you can download it from http://oxygenxml.com/download.html In this release we made incremental improvements in many areas. The Quick fixes support introduced in version 16.0 was extended to be available also from the Author page and new quick fixes were extracted for fixing XML validation errors when you validate against an XML Schema with Xerces. Next we will look into extending this to cover also Relax NG and DTDs as well as implementing Schematron based fixes where the fixes are provided by the schema author as possible solutions to the identified problems. HTML tooltips were already available for content completion proposals in some cases but schema annotations were still presented as text. Now, we identify if an element, attribute or value annotation contains XHTML fragments and in that case we present it rendered as HTML when that component is selected in the content completion window - this allows a nicer display and provides support for links, so you can immediately point the user to an external resource that provides more details about the current selected proposal from the content completion window. You can see this in action in the XSLT editor, as we updated all those annotations to use XHTML. The XPath execution was extended in version 16 to a specified scope like the project, the selected files, etc. In version 16.1 we extended this support to include also the current archive, the XPath being executed on all the files of an EPUB, OOXML, ODF or a ZIP archive and there is also an option to treat ZIP-based archives as folders, if such an archive is included in a scope you apply an XPath expression on. The track changes functionality covers in not only text content but also structure and attributes. The surround operation was a difficult one, because you either do not track that or you mark all the content as deleted and then inserted together with the new element that surrounds it. In 16.1 we introduced support for understanding a wrap operation and tracking only the element that wrapped the content. We worked on color profiles but now all that work was ready for 16.1 but we still managed to get support for high contract themes on Windows. More, the Author visual mode will create application specific media rules to allow you to specify styles that will apply on white or black background and we updated DITA and DocBook to react to these so that the Author mode also adjusts the colors when a high contract theme is applied on the editor. Saxon 9.6 was just released and so was a new version of Calabash but it was not possible to integrated them overnight, so we include the previous stable versions of both of them. However, work already started to integrate Saxon 9 and we can provide early access to this as soon as it is ready in case someone is interested. I think I can go on like this for another hour :). Please see the release notes linked above for all the details and do not hesitate to contact us if you want more details about any of them. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

Trying to debug a "non-deterministic" DTD
by Frank Arensmeier 07 Oct '14

07 Oct '14

Hello! First time poster. I hope this question hasn’t been up for discussion before – I was not able to find anything helpful in the archives. I have a DTD that I need to debug. The ”problem" is that Oxygen validates the DTD just fine, whereas some XML editors (e.g. XMetal) complain about a ”non-deteministic” content model. So, my question is, does Oxygen (15.2) has some kind of ”strict mode” DTD validation? Because I do not have access to some XMetal-debug-fo, I must use Oxygen to debug my DTD. Any help is greatly appreciated! /frank [cid:D69E52E6-83EC-4495-AFAC-6219CE5641B4] Frank Arensmeier | Expertinfo | Teknikinformation, XML-system och språkkonsulttjänster | frank.arensmeier(a)expertinfo.se<mailto:frank.arensmeier@expertinfo.se> | Älvtomtagatan 14 703 42 Örebro | Mobile +46 70 233 90 39 Please consider the planet before printing this e-mail.

4 3

FW: Custom CSS for EPUB and Kindle
by Khaled Aly 06 Oct '14

06 Oct '14

Hi Can we advise about the best practices for pre-transform CSS customization for EPUB and Kindle outputs, starting with oXygen's default stylesheet? Thanks & regards, Khaled ---------------------------------------------------------------- Khaled A.B. Aly, Senior Author & Analyst in ICT Technopsis Research; Cairo, Egypt (GMT+2) Technopsis.com/pro LinkedIn.com/in/kaaly +20 (0)12 2294 6280 Skype:ka.aly

2 2

Oxygen Author Mode as a Word-Processor; Was RE: Easy insertion of en/em-dash
by Robert Leif 03 Oct '14

03 Oct '14

I agree that author mode should have word-processor like features. Unfortunately, it lacks one major feature. It does not have the equivalent of a styles menu for body, paragraphs and fonts. Although, the underlying CSS page can contain all of the styling information in any order, the standard mode for a word-processor like Microsoft Word and preferably Adobe FrameMaker is to have separate menus for pages, paragraphs, fonts, etc. Since CSS has these levels, a CSS page can be and is often organized by them. Thus, a pull-down tree should be organized by them and at each level permit the user to change the style except when the style is read-only. The mechanism of making these changes should include fill-in suggestions. The result is an ultra-powerful web page and EPUB creation system that is much more powerful and versatile than Microsoft Word or Adobe FrameMaker. Robert (Bob) Leif, Ph.D. -----Original Message----- From: oxygen-user-bounces(a)oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Syd Bauman Sent: Thursday, October 2, 2014 6:38 AM To: <oxygen-user(a)oxygenxml.com> Subject: Re: [oXygen-user] Easy insertion of en/em-dash Good point. I concede that I meant in "text" mode, and don't care much what hapens in author mode. JK> I tend to disagree -- oXygen has two different products hidden below JK> "Text" and "Author" tabs. From author mode one would expect word JK> processor like features and current auto-correct options for smart JK> quotes can already be enabled/disabled. Of course in text mode JK> editor shouldn't mess with typed characters. LC> That depends on what mode you are using it under. If you are LC> editing a DocBook, DITA, TEI, etc. in Author mode, then it could be LC> considered a words 😉 processor. _______________________________________________ oXygen-user mailing list oXygen-user(a)oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user

4 5