- oXygen-user - www.oxygenxml.com

Accessing editor variables within a Java plugin
by Florent Georges 17 Nov '08

17 Nov '08

Hi, I looked for in the Javadoc, but didn't find any way to access editor variables (and their values) from within the code of a Java plugin for oXygen. For example to resolve $frameworks to its actual value. Is it possible? Regards, -- Florent Georges http://www.fgeorges.org/

1 0

Feature Request for Content Completion with East Asian Text
by Christian Wittern 17 Nov '08

17 Nov '08

Hi there, We are using oXygen mainly to edit Chinese or Japanese text. In this case, words are not separated by whitespace. For a project we are having here, I am setting up snippets that should be inserted using code completion. However, Code Completion fires only after a whitespace character, so we have to input a spurious whitespace character to kick this off, which then has to be deleted again at some point. Hence my feature request: When doing a Code Completion, look at the character before the insertion point and fire if either there is a whitespace, or a character in the Unicode ranges for East Asian characters. This should be fairly easy to implement and have no negative impact on the current functionality. All the best, Christian -- Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN

3 7

XProc with XSLT completion in oXygen
by Florent Georges 09 Nov '08

09 Nov '08

Hi, I've written an RNC schema that plug the schemas for XSLT into the schema for XProc. The goal was having completion in oXygen for both document types in the same buffer in the oXygen editor. Thought that could interest you: http://fgeorges.blogspot.com/2008/11/xproc-with-xslt-completion-in-oxygen.h… Regards, -- Florent Georges http://www.fgeorges.org/

1 0

Transform directory
by Florent Georges 07 Nov '08

07 Nov '08

Hi, I haven't found a way to transform a directory with XSLT in oXygen. What I am looking for is a tool you give a stylesheet and a directory to (and maybe a file glob in that directory) and it applies the stylesheet to every document in that directory in turn (or every document the name of which matches the file glob.) In other words, something like the first snapshot there: http://kernowforsaxon.sf.net/. Did I miss it in the doc and the menus? Regards, -- Florent Georges http://www.fgeorges.org/

3 4

XProc RNC schema not valid with oNVDL
by Florent Georges 07 Nov '08

07 Nov '08

Hi, I've downloaded the official XProc RNC grammar from: http://www.w3.org/TR/xproc/schemas/xproc.rnc http://www.w3.org/TR/xproc/schemas/steps.rnc When I open the main file (xproc.rnc) in oXygen, I get the following errors from oNVDL: an "element" pattern containing an "attribute" pattern with a non-null ID-type must have a name class that contains only "choice" and "name" elements conflicting ID-types for attribute "id" from namespace "http://www.w3.org/XML/1998/namespace" of element "catch" from namespace "http://www.w3.org/ns/xproc" Before sending a defect report to the WG, I would like to be sure this is not because a restriction of oNVDL. Best regards, -- Florent Georges http://www.fgeorges.org/

2 2

Can Tag Indent Be Configured On a Per-DTD/Per-Namespace Basis?
by Eliot Kimber 06 Nov '08

06 Nov '08

I work with some documents that should *never* be formatted and intended and some that I would like to always be. I didn't see a way to configure this in the options. For example, I often work with InCopy INCX XML, in which whitespace is both significant and fiddly (it uses things like Unicode paragraph break characters to signal formatting paragraph breaks--normalizing the whitespace breaks that). If there's no way to do this, can you add it as a feature request? It would be necessary to be able to bind the association by file extension, as well as namespace, schema, and DTD, since in the case of CS3 INCX, the documents are in no namespace but do have a distinct extension (.incx). Cheers, Eliot ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber(a)reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>

2 2

Code Templates table mixes up?
by Florent Georges 06 Nov '08

06 Nov '08

Hi, I've experienced strange behavior in the table presenting the Code Templates in the preferences Editor > Templates > Code Templates. For example, the first one in the table is "! / XSL Editor / not-!" but the preview shows: <xs:annotation> <xs:documentation>${caret}</xs:documentation> </xs:annotation> I tried the "Restore Defaults" button, but that doesn't change anything (besides loosing my changes :-p.) When I opened that window, I first tried to re-order the rows in the table (by Name, then Editor.) I don't know if this is related. I used the Export feature, and the result looks ok (at first glance.) Hope that helps, -- Florent Georges http://www.fgeorges.org/

2 1

RE: [oXygen-user] Number of recursive levels in XML Instancegenerator in Oxygen 10.0 [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 06 Nov '08

06 Nov '08

Hi, I have Oxygen (Author) 10.0 on my PC and I have been looking for the Generate Sample XML Files option but I can't find it. Attached is a screen dump of the options that I have under the "tools" menu. Is there some setting that I need to make? Thanks. John > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Hockaday John > Sent: Tuesday, 28 October 2008 5:53 PM > To: george(a)oxygenxml.com > Cc: oxygen-user(a)oxygenxml.com > Subject: RE: [oXygen-user] Number of recursive levels in XML > Instancegenerator in Oxygen 10.0 [SEC=UNCLASSIFIED] > > > Hi George, > > Thanks for that information. It looks like I'll be going for > version 10.0 > ASAP. ;--) > > > John > > > -----Original Message----- > > From: George Cristian Bina [mailto:george@oxygenxml.com] > > Sent: Tuesday, 28 October 2008 5:29 PM > > To: Hockaday John > > Cc: oxygen-user(a)oxygenxml.com > > Subject: Re: [oXygen-user] Number of recursive levels in XML > > Instance generator in Oxygen 10.0 [SEC=UNCLASSIFIED] > > > > > > Hi John, > > > > See the Maximum recursivity level option on the Options page on the > > instance generator dialog: > > http://www.oxygenxml.com/doc/ug-oxygen/xml-schema-instance-gen > erator.html#d4e4823 > > Best Regards, > George > -- > George Cristian Bina > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > > > John.Hockaday(a)ga.gov.au wrote: > > Hi, > > > > I have noticed that a feature in Oxygen 10.0 is the XML > instance generator > > from W3C XML Schemas. I use the ISO 19139 W3C XML Schemas > with my work. > In > > these there is an element called "MD_Identifier" which has > an 'authority' > > element as one of its children. The 'authority' element is of type > > 'CI_Citation' which has a child element of 'identifier'. > This 'identifier' > > element is of type 'MD_Identifier' so you see that there is > a recursive > call > > on the 'MD_Identifier' element. > > > > If these W3C XML Schemas were used to generate an XML > document instance, > the > > resulting XML would just keep on being built until the > process was stopped > > unless there was a way of setting the number of times or > levels that an > > element is recursively called. Can this be set in Oxygen > 10.0? That is, > can > > I stop the recursive call of an element and its children > after so many > loops? > > > > Thanks. > > > > > > John > > _______________________________________________ > > 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 >

2 1

Schematron for each element validation
by Luis Costa 04 Nov '08

04 Nov '08

Hi all, My goal is to test if there is only one Element4 in each Root/Element. I try to do this validation with schematron "a" but the result I have got is the wrong one because "a" is testing if there is only one Element4 in all xml "b" and that is not my intend. Can anyone help me? a) <sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron"> <sch:title>XXX</sch:title> <sch:phase id="yyy"> <sch:active pattern="rrr" /> </sch:phase> <sch:pattern id="rrr"> <sch:rule context="Root/Element"> <sch:assert test="Element2[@name='Attribute1']/Element3/Element4 = 1">Attribute1 shall be single Element4</sch:assert> </sch:rule> </sch:pattern> </sch:schema> b) <Root> <Element> <Element2 name="Attribute1"> <Element3> <Element4>Smitty</Element4> </Element3> </Element2> <Element2 name="Attribute2"> <Element3> <Element4>Cleveland Clinic</Element4> <Element4>Parma Community</Element4> </Element3> </Element2> </Element> <Element> <Element2 name="Attribute1"> <Element3> <Element4>Dopplemeyer</Element4> </Element3> </Element2> <Element2 name="Attribute2"> <Element3> <Element4>Cleveland Clinic</Element4> <Element4>Berea Community</Element4> </Element3> </Element2> </Element> </Root> Thank you for your attention and best regards, Luís Costa Software Developer luis.costa(a)alert.pt www.alert-online.pt <http://www.alert-online.pt/> ALERT Life Sciences Computing, S.A. Edifício Lake Towers - pisos 7, 8 e 9 Rua Daciano Baptista Marques, n.º 245 4400-617 Vila Nova de Gaia Portugal Tel.: +351 22 832 89 80 Fax.: +351 22 832 89 82 info(a)alert.pt <mailto:info@alert.pt> This e-mail is privileged, confidential and contains private information. Any reading, retention, distribution or copying of this communication by any person other than its intended recipient is prohibited.

2 1

Re: [oXygen-user] Setting up catalogs
by Radu Coravu 04 Nov '08

04 Nov '08

Hi David, We'll probably have this fix available by Oxygen 9.3 (couple of days). When the fix will be available all you will have to do will be to add your catalog to the Oxygen catalogs list and the DITA Maps Manager topic references will be solved through the catalog. Regards, Radu -- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com David Linton wrote: >> I understand that you use URN's in topicref href's and you want when a >> map is opened in the DITA Maps Manager view to see correctly the links >> to the hrefs (solved by catalog) and of course when double clicking a >> link to open in the editor the real location solved by catalog. >> Indeed Oxygen does not yet solve by catalog the topic references >> presented in the DITA Maps Manager but we can work on this. >> Is my understanding correct? >> > > Yes, that's right. > > >> You also speak something about Oxygen ignoring catalog entries at >> validation. What kind of validation are you referring to? >> > > I don't know - that's just the phrase you used in the user guide, where you > distinguished "validation" from "transformation". I figured they were the only two processes > involved, but I guess that was wrong. > > >> Also, how have you modified the DITA-OT toolkit to allow the URN's to be >> resolved at transformation time? >> > > DITA-OT isn't happy with map files which aren't at the top level so I ended up preprocessing all the > links into a temporary directory with some XSL; a side-effect of that process is that topicref hrefs > get resolved before they get to DITA-OT. > > Before I did that, it worked fine to replace the <xslt> ant task in DITA-OT with one that used saxon with the > apache commons resolver. > > rgds > dave > . > > >> I understand that you have an xml catalog which solves the URN's to real >> locations. Can you send us a sample from it? >> > > I use "uriStartString" to save writing out all the URNs, although I'm aware that the URNs > aren't quite compliant with the RFC, but it's not caused any problems so far. > > > > <group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/style/MAIN/dita-ot/"> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:xsl/" rewritePrefix= "xsl/" /> > <rewriteURI uriStartString= "urn:quative.tv:dita:xsl/" rewritePrefix= "xsl/" /> > > <rewriteSystem systemIdStartString= "http://docs.quative.tv/dita/xsl/" rewritePrefix= "xsl/" /> > <rewriteURI uriStartString= "http://docs.quative.tv/dita/xsl/" rewritePrefix= "xsl/" /> > </group> > > <group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/style/MAIN/"> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:extensions/dtd/" rewritePrefix= "dtd/" /> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:apiref/dtd/" rewritePrefix= "dtd/" /> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:javaapiref/dtd/" rewritePrefix= "dtd/" /> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:dtd/" rewritePrefix= "dtd/" /> > > <rewriteSystem systemIdStartString= "urn:quative.tv:style:" rewritePrefix= "" /> > <rewriteURI uriStartString= "urn:quative.tv:style:" rewritePrefix= "" /> > > <rewriteSystem systemIdStartString= "http://docs.quative.tv/style/" rewritePrefix= "" /> > <rewriteURI uriStartString= "http://docs.quative.tv/style/" rewritePrefix= "" /> > </group> > > <group xml:base="/build/dlinton/tmp/generated/"> > <rewriteURI uriStartString= "urn:quative.tv:docs:generated/" rewritePrefix= "" /> > <rewriteURI uriStartString= "http://docs.quative.tv/generated/" rewritePrefix= "" /> > </group> > > <group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/content/MAIN/cca-ccom/"> > <rewriteURI uriStartString= "urn:quative.tv:docs:cca-ccom/" rewritePrefix= "" /> > <rewriteURI uriStartString= "http://docs.quative.tv/authored/cca-ccom/" rewritePrefix= "" /> > </group> > > <group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/content/MAIN/"> > <rewriteURI uriStartString= "urn:quative.tv:docs:" rewritePrefix= "" /> > <rewriteURI uriStartString= "urn:quative.tv/docs/" rewritePrefix= "" /> > <rewriteURI uriStartString= "http://docs.quative.tv/" rewritePrefix= "" /> > </group> > > > > This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, discussion or disclosure by others is strictly prohibited. If you are not the intended recipient of this email, please contact the sender by return email and delete all copies of this email and its attachments, if any. >

3 4