October 2008 - oXygen-user - www.oxygenxml.com

set an XML Schema for a directory?
by Robert Koberg 30 Mar '09

30 Mar '09

Hi, I haven't used project mode much, but I just created a new project and imported a directory structure into it. One of the folders contains content files that are supposed to adhere to one XML Schema. I see the 'validate selection with...' which allows me to validate the entire directory -- which is great. However, when I bring up an invalid file I would like to have the editor know which schema to use (the one I validated the dir against) so the editor will give the element/attribute options without having to assign the schema each time. Make sense? Is this possible? best, -Rob

2 2

Format and Indent Problem
by Jeff Sese 02 Mar '09

02 Mar '09

Hi, As I have read on previous posts, oXygen classifies mixed content based on the current contents of an element, is this correct? If so, is it possible for oXygen to classify elements based on the declarations made in the DTD or Schema it is associated to? I know that the work around for this is to specify the pattern of elements that you want to preserve the whitespace in the preferences or to manually insert an xml:space="preserve" attributes for these elements, but if an XML is associated with a DTD or a Schema then you can tell whether whitespace in that element is ignorable or not. Currently what I've been doing is for every project I have to specify in the pattern listing all the mixed content elements that are defined in the DTD/Schema so that when I do a pretty print the whitespace is preserved and this method is very troublesome. Is there anymore workaround for this other than the ones I mentioned above? Or can this be considered as an added feature for a future version of the product? Thanks, Jeff

3 16

Adding export to HTML for the graphical representation of Relax NG Schema
by mozer 05 Jan '09

05 Jan '09

Dear, Is it possible to add a feature to export the graphical representation of Relax NG schema to HTML ? Regards, Xmlizer

2 3

RE: [oXygen-user] html does not allow namespace declaration on the rootelement [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 26 Nov '08

26 Nov '08

Hi Xmlizer, I believe that the official reference to XHTML is to a DTD such as: <?xml version="1.0" encoding="iso-8859-1" ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> ... </html> You should be able to use this format. John -----Original Message----- From: oxygen-user-bounces(a)oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of mozer Sent: Thursday, 3 July 2008 2:40 AM To: Oxygen User Subject: [oXygen-user] html does not allow namespace declaration on the rootelement Dear, with the following file <?xml version="1.0" encoding="UTF-8"?> <html xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/1999/xhtml"></html> I have the following error E [Xerces] Attribute "xmlns:xsd" must be declared for element type "html". Can you explain me how to workaround this ? Regards, Xmlizer

2 2

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

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

Poor man's Calabash integration into oXygen
by Florent Georges 31 Oct '08

31 Oct '08

Hi, I wrote a few words on the subject, I thought that could interest people here. It is at: http://fgeorges.blogspot.com/2008/10/poor-mans-calabash-integeration-into.h… I think the most valuable feature would be the editing support of XProc definitions, including embedded XSLT stylesheets. But that is behind my knowledge of oXygen ;-) Regards, -- Florent Georges http://www.fgeorges.org/

2 3

Large File Viewer: Open dialog mistitled
by Lars Huttar 31 Oct '08

31 Oct '08

Hello, In Oxygen 10.0, I launch the Large File Viewer (LFV) via the Tools menu. When I press Ctrl+O in the LFV, a dialog opens. Expected: the dialog title would be "Open File" or something similar. Actual: the dialog title is "Save Results". However when I select a file in this dialog and press OK, the file is loaded, not overwritten. Possibly related context: before launching the LFV, in Oxygen I ran a transformation scenario and then saved the results via the right-click menu and the "Save Results..." menu item. Lars

2 1

RE: [oXygen-user] Oxygen verion 9.3 doesn't recognise XLST2.0 function "lower-case" [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 30 Oct '08

30 Oct '08

Hi All, Thanks for all your suggestions. I loaded the XSL that Sorin sent and it validated without errors. I checked my Options -> Preferences -> XSLT -> XSLT 2.0 options and I have selected Saxon-B 9.0.0.6. I then went back to edit the configuration transformation scenario and found the problem. For some unknown reason to logic I somehow had set the "Transformer" option to Saxon 6. Once I set this to Saxon-B 9.0.0.6 the translation worked. ;--) Sorry for causing you all to think about this problem. I should have thought to look at those settings. Instead of looking at the global settings. I'm sorry for the incompetence. ):--( Thanks to you all for the help. I love these support lists. I get great and accurate answers nearly every time. ;--) John > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Sorin Ristache > Sent: Thursday, 30 October 2008 11:34 PM > To: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Oxygen verion 9.3 doesn't > recognise XLST2.0 function "lower-case" [SEC=UNCLASSIFIED] > > > Hello, > > No, the default validator is Saxon 9 because the XSL editor > will detect > automatically the XSLT version from <xsl:stylesheet version="2.0" ... > > Your XSLT 2.0 code fragment is valid. I just tried that in > Oxygen. Just > to make sure the error refers to that code fragment please run the > action Validate Document (the Validate toolbar or the Document -> > Validate menu) on the attached stylesheet. Is there any > validation error? > > > Regards, > Sorin > > > Tommy Nordgren wrote: > > Check what xslt transformer is used for the actual > transformation. > > As far as I know, it's Saxon 6.5 , (which is an xslt 1.0 > transformer) by > > default. > >> A snippet of the XSL code is: > >> > >> <?xml version="1.0" encoding="UTF-8"?> > >> <xsl:stylesheet version="2.0" ... > >> ... > >

1 0

Oxygen verion 9.3 doesn't recognise XLST 2.0 function "lower-case" [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 30 Oct '08

30 Oct '08

Hi, I am running Oxygen9.3. I am trying to use an XSLT 2.0 function "lower-case()". For some reason the XLST doesn't recognise this function. I get the error: SystemID: G:\asdd\work\dif2anzlic\DIF-ISO-ANZLIC.xsl Location: 1378:0 Description: Error in expression lower-case(.): Unknown system function: lower-case I don't understand why this is not working. I have set my preferences to use Saxon-B 9.0.0.6 for XSLT 2.0 Validation. Is there some other setting that I need to make? A snippet of the XSL code is: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="2.0" ... ... <xsl:for-each select="dif:ISO_Topic_Category"> <gmd:topicCategory> <gmd:MD_TopicCategoryCode> <xsl:value-of select="lower-case(normalize-space(.))"/> </gmd:MD_TopicCategoryCode> </gmd:topicCategory> </xsl:for-each> ... Thanks. John

4 3