- oXygen-user - www.oxygenxml.com

Display of xref (DITA)
by Yan Périard 15 Jun '10

15 Jun '10

Hi, Is there a way to make Oxygen Author in Eclipse display the xrefs/links target titles in the author view instead of the link from the href? Sample DITA XML <concept id="id" xml:lang="en-us"> <title>A Title</title> <shortdesc>A shortdesc</shortdesc> <conbody> <p>An xref not rendered (No content in the element)</p> <p> <xref href="ame1273503188699.xml"/> </p> <p>Followed by a rellink (no content in the element)</p> </conbody> <related-links> <link href="ame1273503188699.xml"/> </related-links> </concept> Thanks Yan Périard

2 1

XML file comparison manual sync?
by Ingo Freitag 04 Jun '10

04 Jun '10

Hello, is it possible to place sync marks in the XML file compare tool? I'm comparing 2 xsd files and the tool gets out of sync and shows much too much differences. Best regards, Ingo

1 0

XSLT output root element force namespaces and attributes sequence
by Martijn Van der Graaff 26 May '10

26 May '10

Hi I need to generate a root element in a output file that contains some attributes and namespaces. It should like this: <?xml version="1.0" encoding="UTF-8"?> <enfinity xsi:schemaLocation="http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex catalog.xsd http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt dt.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:dt="http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt" major="6" minor="1" family="enfinity" branch="enterprise" build="6.3.1.2.5"> what I get is this: <enfinity xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex" xmlns:dt="http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt" xsi:schemaLocation="http://www.intershop.com/xml/ns/enfinity/6.1/xcs/impex catalog.xsd http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt dt.xsd" major="6" minor="1" family="enfinity" branch="enterprise" build="6.3.1.2.5"> How can I force in XSLT that (xmlns:xml="http://www.w3.org/XML/1998/namespace") is always added to the root element and how can I force on where the attributes are sorted. My xslt snippet is: <xsl:template match="/"... <xsl:element name="enfinity" namespace="http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex"> <xsl:attribute name="xsi:schemaLocation">http://www.intershop.com/xml/ns/enfinity/6.1/xcs/impex catalog.xsd http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt dt.xsd</xsl:attribute> <xsl:namespace name="xsi">http://www.w3.org/2001/XMLSchema-instance</xsl:namespace> <xsl:namespace name="">http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex</xsl:namespace> <xsl:namespace name="xml">http://www.w3.org/XML/1998/namespace</xsl:namespace> <xsl:namespace name="dt">http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt</xsl:namespace> <xsl:attribute name="major" select="$major"/> <xsl:attribute name="minor" select="$minor"/> <xsl:attribute name="family" select="$family"/> <xsl:attribute name="branch" select="$branch"/> <xsl:attribute name="build" select="$build"/> Yours, Martijn

3 3

Attribute name dt:dt
by Martijn Van der Graaff 26 May '10

26 May '10

Hi, I need to create an array of elements with several attributes: <a name="aa" dt:dt="string">aValue</a> dt is a namespace " "htttp://www.dt.com" By using xslt: <custom-attributes> <xsl:for-each select="$custom-attributes"> <xsl:variable name="markCode" select="string(lower-case(./@MarkCode))"/> <xsl:variable name="dtType">string</xsl:variable> <xsl:variable name="markCodeValue" select="./@MarkValue"/> <xsl:element name="custom-attribute" inherit-namespaces="no"> <xsl:attribute name="name" select="$markCode"/> <xsl:attribute name="dt" select="$dtType/text()"/> <xsl:value-of select="$markCodeValue/text()"/> </xsl:element> </xsl:for-each> </custom-attributes> I get in the result <custom-attribute xmlns:dt="http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt" name="brand" dt:dt="string">TITANFLX</custom-attribute> I need to get the xmlns:dt="http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt" out of the attribute, The result should be: <custom-attribute name="brand" dt:dt="string">TITANFLX</custom-attribute> Yours, Martijn

2 1

Getting locked out of a project
by Loreti, Wendy 24 May '10

24 May '10

I'm getting this problem when I try to open my workspace. "Tree element '/hardware_help/hardware.ditamap' not found." The file is clearly there and completely healthy and valid. What might this mean otherwise? As a secondary question, how compatible are Oxygen versions with each other? Wendy Loreti Senior Technical Writer Vocollect, Inc. 703 Rodi Rd. Pittsburgh, PA 15235 www.vocollect.com <http://www.vocollect.com/> CONFIDENTIALITY NOTICE This message, together with any attachments, may be legally privileged and is confidential information intended only for the use of the individual or entity to which it is addressed. It is exempt from disclosure under applicable law including court orders. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender and delete this message, along with any attachments, from your computer.

2 1

Find ahead
by Karl Stubsjoen 24 May '10

24 May '10

What is the shortcut key for find ahead (I think that is what it is called). The find feature responds to your keystrokes and quickly jumps forward in the document highlight the first found result.

2 1

Re: [oXygen-user] Schema documentation from specific root element
by Adrian Buza 21 May '10

21 May '10

Hi, We already have the clean schema feature request added to our issue tracking tool. It will be implemented in the long term so it's going to take a while. I've added your vote for it. Regards, Adrian Adrian Buza Oxygen XML Editor support Ingo Freitag wrote: > Hi, > > thank you for your quick answer. > > The best solution would be something complete automatic, but it is also possible, that I remove the other root elements before. > > But one problem is, that the schema uses global types (simple and complex) very intensive, which means for me to manually remove all those elements as well. > This is a huge work. > > I already read in former posts, that you were asked to add a function to 'clean' a schema from unused types and other elements. > In my case such a function would do the trick very well :) So my vote to implement it as soon as possible. > > Best regards, > > Ingo > > -----Original Message----- > From: Adrian Buza [mailto:adrian@sync.ro] > Sent: Thursday, May 20, 2010 10:47 AM > To: Ingo Freitag > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific root element > > Hello, > > The schema documentation tool is not contextual, it generates the > documentation for the entire schema so I'm afraid you cannot simply > generate the documentation starting from a given root element. > > But there may be a few options that could help you break it down into > smaller parts. > For example if you generate HTML you can split the output in multiple > files by component(in the Output tab). Other than that there are the > generic filters from the Settings tab, but I'm not sure if they're > useful to you in this case. > > There's also the possibility to trim the schema and remove the unwanted > root elements before generating the documentation, but I'm guessing you > were looking for something automatic to do this. > > Regards, > Adrian Buza > Oxygen XML Editor support > > Ingo Freitag wrote: > >> Hi, >> >> I have a very huge schema file with several root elements included. >> Now I want to create a documentation out of one of those root elements only. >> >> Is this somehow possible? >> Of course all linked and referenced types shall also be included in the documentation. >> >> Ingo >> >> >> >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user >> >> > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user >

1 0

Use DITA 1.1 instead of 1.2?
by Yves Barbion 21 May '10

21 May '10

Hi again group I see that oXygen already supports DITA 1.2, which is great! However, this can be a problem in "mixed editor" environments as long as the other editors don't support DITA 1.2 yet. Is there an easy way in oXygen to make sure that the authors don't use the elements and attributes of the DITA 1.2 standard, for example <hazardstatement>, for the time being? Thanks -- Yves Barbion www.scripto.nu

2 1

Re: [oXygen-user] Schema documentation from specific root element
by Mark Baker 20 May '10

20 May '10

I think it should be noted that there is a big difference between schema documentation and doctype documentation. * A schema may define 0, 1, or many root elements, and therefore 0, 1, or many document types. Multiple document types defined by the same schema may have nothing in common with each other. * A document type may contain elements defined in one or more schemas, and even allow content that is not governed by any schema. For instance, a particular document type may allow the use of MathML or SVG within the document. The documentation of any one schema, therefore, would not constitute documentation for the entire document type. * A document type may reuse a complex type defined in a schema at different points in a document type while assigning substantially different document semantics to that type in each of the locations in which it is used. Schema documentation tools necessarily follow the structure of schemas. They describe the structure of the schemas themselves, but the structures of the document types defined by the schemas may be much more complex and varied than the structures of the schemas themselves (or vice versa -- a complex schema may define a simple document type). Generating schema documentation from one root element of a schema, therefore, is not at all equivalent to creating document type documentation for documents that have that root element. We produce a lot of document type references. We have two different document type reference composition and build processes for different types of document. (Data oriented document types and text oriented document types are significantly different in their documentation needs.) Schema documentation, generated by standard schema documentation tools, as good as some of them are, would not come close to meeting our user's needs. I think you may need to figure out if what you really need is document type documentation, rather than schema documentation. If so, you will need a different process to create it. Mark > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Ingo Freitag > Sent: May 20, 2010 12:07 PM > To: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific > root element > > Hi, > > thank you for your quick answer. > > The best solution would be something complete automatic, but > it is also possible, that I remove the other root elements before. > > But one problem is, that the schema uses global types (simple > and complex) very intensive, which means for me to manually > remove all those elements as well. > This is a huge work. > > I already read in former posts, that you were asked to add a > function to 'clean' a schema from unused types and other elements. > In my case such a function would do the trick very well :) So > my vote to implement it as soon as possible. > > Best regards, > > Ingo > > -----Original Message----- > From: Adrian Buza [mailto:adrian@sync.ro] > Sent: Thursday, May 20, 2010 10:47 AM > To: Ingo Freitag > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific > root element > > Hello, > > The schema documentation tool is not contextual, it generates > the documentation for the entire schema so I'm afraid you > cannot simply generate the documentation starting from a > given root element. > > But there may be a few options that could help you break it > down into smaller parts. > For example if you generate HTML you can split the output in > multiple files by component(in the Output tab). Other than > that there are the generic filters from the Settings tab, but > I'm not sure if they're useful to you in this case. > > There's also the possibility to trim the schema and remove > the unwanted root elements before generating the > documentation, but I'm guessing you were looking for > something automatic to do this. > > Regards, > Adrian Buza > Oxygen XML Editor support > > Ingo Freitag wrote: > > Hi, > > > > I have a very huge schema file with several root elements included. > > Now I want to create a documentation out of one of those > root elements only. > > > > Is this somehow possible? > > Of course all linked and referenced types shall also be > included in the documentation. > > > > Ingo

1 0

Re: [oXygen-user] Schema documentation from specific root element
by Adrian Buza 20 May '10

20 May '10

Hello, The schema documentation tool is not contextual, it generates the documentation for the entire schema so I'm afraid you cannot simply generate the documentation starting from a given root element. But there may be a few options that could help you break it down into smaller parts. For example if you generate HTML you can split the output in multiple files by component(in the Output tab). Other than that there are the generic filters from the Settings tab, but I'm not sure if they're useful to you in this case. There's also the possibility to trim the schema and remove the unwanted root elements before generating the documentation, but I'm guessing you were looking for something automatic to do this. Regards, Adrian Buza Oxygen XML Editor support Ingo Freitag wrote: > Hi, > > I have a very huge schema file with several root elements included. > Now I want to create a documentation out of one of those root elements only. > > Is this somehow possible? > Of course all linked and referenced types shall also be included in the documentation. > > Ingo > > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user >

2 1

Easiest way to add a header row to a table in a DITA topic?
by Yves Barbion 20 May '10

20 May '10

Hi group What's the easiest way to add a header row to a table in a DITA topic? Cheers -- Yves Barbion www.scripto.nu

2 1

Schema documentation from specific root element
by Ingo Freitag 20 May '10

20 May '10

Hi, I have a very huge schema file with several root elements included. Now I want to create a documentation out of one of those root elements only. Is this somehow possible? Of course all linked and referenced types shall also be included in the documentation. Ingo

1 0

Author : Number of characters
by Rogie Isabelle 12 May '10

12 May '10

Hi, Is it possible to know simply the number of characters in a xml file? I use Author version 10.2 on Mac OS X. Best Regards, _______________________________________ Isabelle Rogie Database Chief project Wolters Kluwer France

4 6

Looking to hire programmer for content-completion customization
by Тома Тасовац 12 May '10

12 May '10

Hi, I am looking for a programmer who is well-versed in Oxygen and various XML technologies to enable server queries for attribute value completion in Oxygen under certain, clearly defined conditions. e.g. <w lemma="" ana="">word</w> -- lemma and ana attributes need to be completed based on what the server returns when queried. The recommended procedure for this type of work would be like this: > If you want to search and show the custom attribute values on request when "Ctrl-Space" gets called in the attribute value (which is the way in which Oxygen content completion works) this can be done through the Oxygen Author SDK API: > > http://www.oxygenxml.com/developer.html#XML_Editor_Authoring_SDK > > In order to do this you usually have to define an external document type association for your XML file types in the Document Type Association preferences page. The document type association contains association rules for your XML documents, document templates, XML catalogs + in the "Extensions" tab you can contribute with a Content completion handler which implements the SchemaManagerFilter class. This class contains a method called: > > List<CIValue> filterAttributeValues(List<CIValue> attributeValues, WhatPossibleValuesHasAttributeContext context); > > which can be used to propose additional attribute values in a certain context. I have written a detailed specification of what I need, together with a sample XML file from which one can test server queries and responses. If you are interested in this type of work, please email me off the list and I will get in touch. All best, Toma ————————————————————— Toma Tasovac Center for Digital Humanities (Belgrade, Serbia) http://humanistika.org • http://transpoetika.org

1 0

bug-fixes in <oXygen/> XML Editor 11.2, build 2010031611
by Mark 10 May '10

10 May '10

Some time ago, I wrote mentioning that my java scripts would not run in <oXygen/> XML Editor 11.2, build 2010031611 and was given the workaround to save my script tags in two rather than one tag: <script src=....></script> as opposed to <script src=.../>. I was told this was a regressive bug and would be fixed. At the same time, I was given an URL to check for bug fixes. Unfortunately, my email files have been destroyed and I no longer have that reference. Has this bug been fixed? If so, where can I download it? Thanks, Mark

2 1

Couldn't find hyphenation pattern en_US
by jsbien＠mimuw.edu.pl 07 May '10

07 May '10

I experiment with transforming TEI to PDF using the file http://tei.oucs.ox.ac.uk/ENRICH/gBank/gBank.xml?style=raw The first error I get is --8<---------------cut here---------------start------------->8--- SystemID: /home/jsbien/ENRICH/all/gBank.xml Engine name: Saxon-B 9.1.0.7 Severity: error Description: The process 'FOP' ended with code: 1. The error was: 2010-05-04 14:32:51 org.apache.fop.hyphenation.Hyphenator getHyphenationTree SEVERE: Couldn't find hyphenation pattern en_US --8<---------------cut here---------------end--------------->8--- The problem seems independent of the current locale. What is the remedy? Best regards JSB -- , dr hab. Janusz S. Bien, prof. UW - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - Warsaw University (Department of Formal Linguistics) jsbien(a)uw.edu.pl, jsbien(a)mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/

2 3

is version 10.3 supposed to be usable in Debian Squeeze?
by jsbien＠mimuw.edu.pl 04 May '10

04 May '10

Hi! I've purchased oXygen a year ago but only now I have motivation to try to use it. However when I start to do something nontrivial, it becomes unusable. To be more specific, after reaching the point shown on the screen shot, it stops to react and even refreshing the window takes ages (as visible on the screen shot). I enclose below some information which might be relevant. Best regards JSB --8<---------------cut here---------------start------------->8--- /usr/sbin/update-alternatives --display java java - manual mode link currently points to /usr/lib/jvm/java-6-sun/jre/bin/java /usr/bin/gij-4.3 - priority 43 /usr/lib/jvm/java-6-openjdk/jre/bin/java - priority 1061 slave java.1.gz: /usr/lib/jvm/java-6-openjdk/jre/man/man1/java.1.gz /usr/lib/jvm/java-6-sun/jre/bin/java - priority 63 slave java.1.gz: /usr/lib/jvm/java-6-sun/jre/man/man1/java.1.gz /usr/lib/jvm/java-gcj/jre/bin/java - priority 1043 slave java.1.gz: /usr/lib/jvm/java-gcj/man/man1/java.1.gz Current 'best' version is '/usr/lib/jvm/java-6-openjdk/jre/bin/java'. --8<---------------cut here---------------end--------------->8--- --8<---------------cut here---------------start------------->8--- Package: sun-java6-jre Version: 6.20-dlj-1 Severity: normal -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sun-java6-jre depends on: ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy ii java-common 0.36 Base of all Java packages ii locales 2.10.2-6 Embedded GNU C Library: National L ii sun-java6-bin 6.20-dlj-1 Sun Java(TM) Runtime Environment ( Versions of packages sun-java6-jre recommends: ii gsfonts-x11 0.21 Make Ghostscript fonts available t Versions of packages sun-java6-jre suggests: pn sun-java6-fonts <none> (no description available) pn sun-java6-plugin | ia32-sun-j <none> (no description available) pn ttf-arphic-uming <none> (no description available) pn ttf-baekmuk | ttf-unfonts | t <none> (no description available) pn ttf-kochi-gothic | ttf-sazana <none> (no description available) pn ttf-kochi-mincho | ttf-sazana <none> (no description available) -- debconf information: * shared/accepted-sun-dlj-v1-1: true sun-java6-jre/stopthread: true sun-java6-jre/jcepolicy: shared/error-sun-dlj-v1-1: * shared/present-sun-dlj-v1-1: --8<---------------cut here---------------end--------------->8--- -- , dr hab. Janusz S. Bien, prof. UW - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - Warsaw University (Department of Formal Linguistics) jsbien(a)uw.edu.pl, jsbien(a)mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/

2 5

Disabling XSLT documentation in a new stylesheets
by Jirka Kosek 04 May '10

04 May '10

Hi folks, it is possible to modify default template for new XSLT stylesheets. I need to get rid of XSLT documentation stuff there and I wasn't able to find right place to disable it. Thanks, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------

2 2

How to place log file in consistent directory?
by Michael Roberts 29 Apr '10

29 Apr '10

Oxygen-heads: I have a log4j.properties file for testing a plugin that integrates Oxygen and RSuite. I am currently using Mac OS X. log4j.appender.R.File=oxygen-rsuite-plugin.log If I use oxygenMac.sh from the command-line, the oxygen-rsuite-plugin.log file shows up in the current directory where I run the command. If I launch Oxygen from the "open" command on Mac OS X (from an applet in FireFox), then the current working directory is in some random place (that I cannot find). Log4j permits variable substitution in the log4j.properties, from system properties. Are there sysem properties set by Oxygen for the installation directory or some other place where I can locate the log file so it will be in a consistent place? I would like to be able to specify something like this in the log4j.properties file: log4j.appender.R.File=${oxygen.home}/oxygen-rsuite-plugin.log Thanks, Michael Roberts

2 2

DITA Map Manager
by Betty Harvey 26 Apr '10

26 Apr '10

Is there a trick to getting the titles resolved in the DITA Map Manager? The samples provided with Oxygen resolve the titles in the subdocuments, however I haven't been able to titles resolved in my Ditamap. The documents are still able to be opened when I click on the map link but only the href is displaying the Dita Map Viewer. TIA! Betty /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Betty Harvey | Phone: 410-787-9200 FAX: 9830 Electronic Commerce Connection, Inc. | harvey(a)eccnet.com | Washington,DC XML Users Grp URL: http://www.eccnet.com | http://www.eccnet.com/xmlug/ /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\\/\/ Member of XML Guild (www.xmlguild.org)

2 1

schemaLocation stil required?
by Eric Jahn 22 Apr '10

22 Apr '10

In the past versions of the Oxygen Schema editor, an import statement would not work unless a schema association was configured. The W3C guidelines on import statements, though, states that schemaLocation is optional. Presumably, it would be optional if the import uri is the same as the schemaLocation, which is the case in my situation. However, oxygen fails to import without a schemaLocation attribute. Here is my schema: http://www.hmis.info/schema/3_0/HUD_HMIS.xsd Thanks! -- Eric Jahn phone: 727.537.9474 3126 8th Ave N St. Petersburg, Florida 33713

3 2

11.2 XPath box in Find/Replace stuck?
by Markus Flatscher 20 Apr '10

20 Apr '10

Hi there, using oXygen 11.2, build 2010031611 on Mac OS X in text mode, I'm unable to activate the XPath constraint box in the Find/Replace dialogue (it seems to invariably stay grayed out). Is this a known bug, or am I overlooking something? Thanks, Markus P.S. (O/T): thanks much for all those quick-and-timely XProc updates! -- Markus Flatscher, Project Editor ROTUNDA, The University of Virginia Press PO Box 801079, Charlottesville, VA 22904-4318 USA Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903 Email: markus.flatscher(a)virginia.edu Web: http://rotunda.upress.virginia.edu/

3 6

Modifying the dita2htmlImpl.xsl file
by Steve Matlock 20 Apr '10

20 Apr '10

I realize I'm probably asking for someone to explain the equivalent of string theory to a high school freshman, but I'm struggling to understand how to modify the dita2htmlImpl.xsl file so that the transformed files I get from Oxygen tag the <task> and <concept> entries in my <composite> files are tagged as "H2" headings and not "H3" headings. Example of my composite topic file <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE dita PUBLIC "-//OASIS//DTD DITA Composite//EN" "http://docs.oasis-open.org/dita/v1.1/OS/dtd/ditabase.dtd"> <dita> <topic id="MyTopic"> <title>My Composite Topic</title> <prolog> <metadata> <othermeta content="en_US" name="language"/> <othermeta content="US" name="country"/> </metadata> </prolog> <body> <p>This is the general introduction to this concept and task.</p> </body> </topic> <concept id="concept1" conref="../../shared/en-us/concept1.dita#concept1A"> <title>Concept title</title> </concept> <task id="task1 conref="../../shared/en-us/taskt1.dita#task1A""> <title>Task title</title> </task> </dita> Assuming that this "works" in the transform, I get content where each concept and task comes in tagged as "H1" I need these to be tagged "H2" instead. I realize that I can use <section> tags to mark sections as subordinate, but the <composite> type doesn't seem to support <section> tags where I need them. Conceptually it would be like this: <section> <title>Major Concept</title> <concept id="concept1" conref="concept1.dita#concept"> <conbody/> </concept> </section> <section> <title>Major Task</title> <task id="task1" conref="task1.dita#task"> <taskbody/> </task> </section> but of course this doesn't work. Also, I would end up getting the Title from the Section as well as the Task or Concept. So, do I somehow munge the dita2htmlImpl.xsl file to somehow make Tasks and Concepts "H2" entries, or can I somehow get the idea of a subordinate Concept or Task into a Topic/Composite Topic DITA file?

2 1

how to install on Ubuntu
by Syd Bauman 19 Apr '10

19 Apr '10

This may be a FAQ, in which case I apologize, please point me in the right direction. Situation: While I like to think of myself as technically reasonably savvy, I know absolutely nothing about Java, JREs, JDEs, JVMs, or other TLAs that start with J. (I've never even watched _JAG_ :-) I'm trying to install oXygen onto an Ubuntu 9.10 system. I downloaded the "Linux 64 bit (Includes Java VM 1.6.0_16)" .sh file from http://www.oxygenxml.com/download_oxygenxml_editor.html. The instructions say "Make sure you have in your PATH environment variable the correct location of the JRE." How do I know the location of the JRE? I tried executing the oxygen.sh command, but got | syd@Nimbus2000:~/Downloads$ sudo sh oxygen.sh | [sudo] password for syd: | Unpacking JRE ... | Preparing JRE ... | bin/unpack200: 1:ELF: not found | bin/unpack200: 4: Syntax error: word unexpected (expecting ")") | Error unpacking jar files. Aborting. | You might need administrative priviledges for this operation. | syd@Nimbus2000:~/Downloads$ [Note that there is an unprintable character that didn't survive the cut & paste -- perhaps a U+007F? -- in front of "ELF".] Is this because I don't have the right JRE in my $PATH (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games)?

4 4

MarkLogic's CQ integration
by Florent Georges 14 Apr '10

14 Apr '10

Hi, The developers I worked with on projects using MarkLogic were most of the time using MarkLogic's CQ web interface. Sometimes even though they had an oXygen licence. I think the main reason why it's because CQ automatically saves the session on the server so there is no need to save any file and the session is always available to the developer, regardless the machine he/she is actually using. So the idea: it would be very useful I think to have a similar mechanism in oXygen, to save a buffer automatically onto the ML instance each time this buffer is evaluated. Maybe even using directly the own CQ's sessions in order to integrate smoothly and collaborate easily with people using CQ on the same project. Just an idea... Regards, -- Florent Georges http://www.fgeorges.org/

3 4