- oXygen-user - www.oxygenxml.com

wish: reindenting without rewrapping
by Lars Huttar 29 Oct '04

29 Oct '04

Dear Oxygen folks, I'm not sure if this is the right mailing list for feature wishes, but here's one. I love the pretty-printing ("Format and indent") feature as a way to fix indentation. However, I also like to include blank lines in my stylesheets to make them more readable, e.g. to separate one template from the next. But when I use Format-and-indent, the blank lines are eliminated. I also sometimes like to have comments following an XSLT instruction on the same line. So it would be nice to have a way to reindent without affecting line breaks. E.g. just a "reindent" command. (Ctrl+Alt+P? Ctrl+Shift+I?) It would be possible to offer this functionality as a Preferences option for the Format-and-indent command, but that would not be ideal since there are often times that you DO want to rewrap long lines and so on. Switching a preferences option on and off would be annoying. The ideal would be to have a separate command. Regards, Lars

2 2

Version 5
by Peter Charles 27 Oct '04

27 Oct '04

Does this require and upgrade license and if it does how do you disable the pop up window telling me there is an upgrade available? Thanks

2 1

Eclipse open external file bug
by Perez Carmona, David 11 Oct '04

11 Oct '04

Please, see this bug report I have made against the latest version of Oxygen: https://bugs.eclipse.org/bugs/show_bug.cgi?id=75877 You can contact me if you need further info. Best regards, David

2 1

Failure to properly start
by Peter Charles 11 Oct '04

11 Oct '04

Hello, Why is it that Oxygen sometimes fails to start? The process is running the splash screen is shown but the application window never opens. Very annoying. Peter -----<CDE/>----- Center for Document Engineering University of California, Berkeley cde.berkeley.edu

3 2

Failure to properly start
by Peter Charles 10 Oct '04

10 Oct '04

Oh and when it fails to start a message is flashed so fast that it is almost impossible to read. "can not transfer the parameter to the running ..." -----<CDE/>----- Center for Document Engineering University of California, Berkeley cde.berkeley.edu

2 1

Oxygen Eclipse plugin XPath evaluator not handling default namespaces...
by John O'Shea 01 Oct '04

01 Oct '04

Hi, I've got an XML doc that looks like this: <?xml version="1.0" ?> <EXAMPLE_COMMIT_NOTICE xmlns="http://example.com/services/b2b" xmlns:example="http://example.com/services/b2b"> <Partner_ID>abcdef</Partner_ID> <File_Name>abcdef</File_Name> <Transmission_Date>abcdef</Transmission_Date> <Commit_Notice_Detail> <Order_Number>abcdef</Order_Number> <Partner_Web_Order_Number>abcdef</Partner_Web_Order_Number> <Line_Number>abcdef</Line_Number> <Product_ID>abcdef</Product_ID> <Quantity_Committed>abcdef</Quantity_Committed> <Committed_Ship_Date>abcdef</Committed_Ship_Date> </Commit_Notice_Detail> </EXAMPLE_COMMIT_NOTICE> When editing in the Oxygen XML, if I choose the XPath Expression evaluator and enter: /example:EXAMPLE_COMMIT_NOTICE/example:Commit_Notice_Detail/example:Order_Number then I get an error dialog back from the oXygen plugin: "Exception ro.sync.goto.do Prefix must resolve to a namespace: example" despite the fact that the example prefix is correctly bound to a namespace. I've tried various tricks to get an XPath query that can find elements in this document but nothing will work. I've dropping the proxy of the default namespace and trying /:EXAMPLE_COMMIT_NOTICE/:Commit_Notice_Detail/:Order_Number but it gives the same erri (with nothing after the 'Prefix must resolve to a namespace: ' message. Note, if I do something like: <?xml version="1.0" ?> <EXAMPLE_COMMIT_NOTICE xmlns="http://example.com/services/b2b" xmlns:example="http://example.com/services/b2b"> <Partner_ID>abcdef</Partner_ID> <File_Name>abcdef</File_Name> <Transmission_Date>abcdef</Transmission_Date> <Commit_Notice_Detail xmlns=""> ^^^^^^^^ <Order_Number>abcdef</Order_Number> <Partner_Web_Order_Number>abcdef</Partner_Web_Order_Number> <Line_Number>abcdef</Line_Number> <Product_ID>abcdef</Product_ID> <Quantity_Committed>abcdef</Quantity_Committed> <Committed_Ship_Date>abcdef</Committed_Ship_Date> </Commit_Notice_Detail> </EXAMPLE_COMMIT_NOTICE> and then use a query string of '//Commit_Notice_Detail' it correctly returns '/EXAMPLE_COMMIT_NOTICE[1]/Commit_Notice_Detail[1]' However, that's of no use to me - all of the elements in the document must be from the default or a named namespace. Note the posting on the Oxygen message board at http://www.oxygenxml.com/forum/viewtopic.php?p=21 suggests this approach (proxying the default namespace) should work. Can you let me know what I've missed, or is this a know fault with the plugin (or Xalan)?????

2 1

Validate xref when XInclude
by Sean Wheller 28 Sep '04

28 Sep '04

Hi, I can't validate xref's when using XInclude. Though as I understand it should be possible with Apache Xerces-J. Comment out xref's and all is valid. When I transform the document the xref's (uncommented), are resolved correctly. Validation returns: "An element with the identifier "docbookxsl" must appear in the document. preface.xml" Any ideas? Following is relevant info from files. BOOK.XML --------------------------- <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ <!ENTITY % xinclude SYSTEM "/home/sean/apps/oxygen/docbook/dtd/xinclude.mod"> %xinclude; <!ENTITY % global_ents SYSTEM "global.ent"> %global_ents; ]>  <book> ... <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="preface.xml"> <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">FIX ME</xi:fallback> </xi:include> ... <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="biblio.xml"> <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">FIX ME</xi:fallback> </xi:include> </book> XREF IN PREFACE.XML --------------------------- <para>The first, "Docbook - The Definitive Guide" <xref linkend="docbookxsl"/> is about the Docbook Document Type Definition (DTD).</para> <para>The second, "Docbook XSL - The Complete Guide" <xref linkend="docbooktdg"/> is about the Docbook Stylesheets (XSL's).</para> BIBLIOENTRY in BIBLIO.XML --------------------------- <biblioentry id="docbookxsl"> <authorgroup> <author> <firstname>Bob</firstname> <surname>Stayton</surname> </author> </authorgroup> ... </biblioentry> <biblioentry id="docbooktdg"> <authorgroup> <author> <firstname>Norman</firstname> <surname>Walsh</surname> </author> <author> <firstname>Leonard</firstname> <surname>Muellner</surname> </author> </authorgroup> ... </biblioentry> .......................... Oxygen 4.2 Apache Xerces-J 2.6.2 Apache Xalan Java 2.5.1 SAXON 6.5.3 Apache FOP 0.20.5 OASIS DocBook XML DTD 4.2 DocBook XSL 1.64.1 -- Sean Wheller sean(a)enbaya.co.za http://www.enbaya.co.za

2 1

Character display problem
by T Reaves 22 Sep '04

22 Sep '04

Hello all. I have this problem of how a particular character combination is displayed. I'm using the Eclipse plugin. In an XML file I'll be typing a Java path like this: '.../model/Item' The problem is as soon as I type the '/' after the 'l', it is not displayed as 'l/' but as a single character. In the Outline view it displays correctly. Is this a know problem, and does it have a solution?

2 2

Saxon version and xsl:document
by Peter Charles 07 Sep '04

07 Sep '04

Hello, What version of saxon is distributed with Oxygen 4.2? The auto complete feature does not support xsl:document. Is that because the distributed version of saxon does not support xsl:document? Peter

3 2

Validating merged grammars
by Paul Everitt 07 Sep '04

07 Sep '04

Hi. The first example in the Relax-NG tutorial under 9.3 "Merging Grammars" looks like this: <grammar xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"> <define name="inline"> <zeroOrMore> <ref name="inline.class"/> </zeroOrMore> </define> <define name="inline.class"> <choice> <text/> <element name="bold"> <ref name="inline"/> </element> <element name="italic"> <ref name="inline"/> </element> </choice> </define> </grammar> However, <oxygen/> fails to validate, claiming it requires a <start> element. --Paul

2 3