- oXygen-user - www.oxygenxml.com

RE: [oXygen-user] "Invalid encoding name" when importing saml schema
by Julien Boeuf 29 Aug '05

29 Aug '05

Hi George, Thank you very much for your quick reply and for the workaround. Cheers, Julien. | -----Original Message----- | From: George Cristian Bina [mailto:george@oxygenxml.com] | Sent: Friday, July 29, 2005 9:42 AM | To: Julien Boeuf | Cc: oxygen-user(a)oxygenxml.com | Subject: Re: [oXygen-user] "Invalid encoding name" when | importing saml schema | | Hi Julien, | | We were able to reproduce the behavior, thanks for reporting | that. We will look into that and see what happens. | | In the meanwhile you can workaround the problem if you get a | local copy of the | http://www.oasis-open.org/committees/download.php/3408/oasis-s | stc-saml-schema-assertion-1.1.xsd | and set up a catalog that resolves that system identifier to | the local copy. | | For instance if you place the catalog and the schema in the | same folder then the catalog file content can be: | | | <?xml version="1.0"?> | <!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog | V1.0//EN" | "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"> | <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> | <system | systemId="http://www.oasis-open.org/committees/download.php/34 | 08/oasis-sstc-saml-schema-assertion-1.1.xsd" | uri="oasis-sstc-saml-schema-assertion-1.1.xsd"/> | </catalog> | | The catalog should be added in the catalog list from | Options->Preferences -- XML -- XML Catalog page. | | Best Regards, | George | --------------------------------------------------------------------- | George Cristian Bina | <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger | http://www.oxygenxml.com | | | Julien Boeuf wrote: | > Hi, | > | > I get an "Invalid encoding name" error whenever I import | the saml 1.0 | > schema. Here's an example: | > | > Code: | > <?xml version="1.0" encoding="UTF-8"?> | > <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" | > targetNamespace="urn:foo:bar" | > xmlns="urn:foo:bar" | > xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"> | > | > <xs:import namespace="urn:oasis:names:tc:SAML:1.0:assertion" | > | schemaLocation="http://www.oasis-open.org/committees/download. | php/3408/o | > asis-sstc-saml-schema-assertion-1.1.xsd"/> | > | > <xs:complexType name="FooType"> | > <xs:sequence> | > <xs:element ref="saml:Assertion"/> | > </xs:sequence> | > </xs:complexType> | > | > <xs:element name="Foo" type="FooType"/> </xs:schema> | > | > | > Are you able to reproduce the problem? The saml schema | itself validates | > OK... | > | > Thanks, | > | > Julien. | > | > PS I use Oxygen 6.1 for windows, build 2005072105. I have | > _______________________________________________ | > oXygen-user mailing list | > oXygen-user(a)oxygenxml.com | > http://www.oxygenxml.com/mailman/listinfo/oxygen-user | |

2 1

oXygen-6.1 xml:base woes
by Raymond 25 Aug '05

25 Aug '05

docbook-dtd-4.5b1 docbook-xsl-1.69.1 jdk-1.5.0_4, kubuntu-5.04 oXygen-6.1 saxon-6.5.4 Consider the following: <sect1 xmlns:xi="&w3XInclude;" xml:base=""> ... ... <mediaobject> <imageobject> <imagedata fileref="figures/foo.gif"/> </imageobject> </mediaobject> ... ... </sect1> generates the following html: ... ... <div class="mediaobject"> <img src="file:/home/raymond/docbook/foo/file:/home/raymond/docbook/foo/figures/foo.gif"> </div> ... ... Why is the image path not relative and duplicated? Thought xml:base="" as a document root attribute would implement relative paths, but this time to no avail. Note, xml:base="" works CORRECTLY in oXygen-6.0. Is this an issue with saxon-6.5.4 ? If so, what is the process to utilize saxon-6.5.3 in oXygen-6.1 ? Help please, this issue is breaking my current project !!! Raymond

3 5

feature enhancement: wsdl soap analyzer in modeless window??
by Robert Koberg 24 Aug '05

24 Aug '05

Hi, Would it be possible to have the wsdl soap analyzer window open as modeless so you can switch-to/edit/scroll other files in the main app window? best, -Rob

2 1

tab forward
by Linus Kamb 24 Aug '05

24 Aug '05

Can I configure Oxygen such that when I press the tab key, it will jump the cursor forward to the next "logical" insertion point, eg. if I am inserting attribute text, the tab key would jump the cursor out of the quoted text; if I am in the attribute part of the element, but not actually entering attribute text, the tab key would jump to the element content, etc.? Maybe this is already possible and I'm just doing it wrong, or it is configurable and I haven't been able to find it (my guess, actually, since I've missed things before :-/ ) or else it is a feature request. I see there are keyboard mappings to menu items, but that doesn't seem like where this would go. I also noted a request for key mapping in the forums a long time ago. Thanks, Linus

2 1

go to parent element
by Lars Huttar 19 Aug '05

19 Aug '05

Dear Oxygen team, A friend recently showed me the go-to-matching-tag (Ctrl+Shift+G) command in Oxygen. Very handy! Let me request another useful command: go-to-parent-(start-)tag. We have XML documents where some elements have many children, and there's no easy way (that I've found) to discover (the start tag of) the parent of a given element, which may be far away in the document. A suggested key binding would be Alt+LeftArrow. Thanks, Lars

2 4

Working with well formed document : indent not within elements
by mozer 19 Aug '05

19 Aug '05

Hello I'm regularly working with well formed document (but not valid) I love indent of oXygen but i did give me all i want because it adds whitespaces everywhere i love to find an option to indent such a way spaces WON'T be in the element example <A ID="1" REF="2"><B>foo</B><C>bar</C></A> becomes <A ID="1" REF="2" ><B>foo</B ><C>bar</C ></A> with unlimited size (only making one element per lines) for the moment, i must do it with another tool Is there a simple way to do it in Oxygen ? Xmlizer

2 6

feature request: go to definition
by Lars Huttar 18 Aug '05

18 Aug '05

When editing XSLT stylesheets, it would often be convenient to be able to jump automatically from <xsl:call-template name="my-template"> to the place where the template is defined, <xsl:template name="my-template"> More generally, this might also be used to jump from a $variable reference to the <xsl:variable> or <xsl:param> definition, or from an <xsl:import> element to the imported stylesheet. This would make it easier to find your way around large, complex stylesheets. Lars

3 3

validation failure with version 6.1
by Gary Gapinski 17 Aug '05

17 Aug '05

Version 6.1 (build 2005071905) of <oXygen/> appears to have broken validation. The attachment contains some files from NIST, one of which - ios-sample-1.0.xccdf.xml - has been slightly modified from the original (original files are available from http://csrc.nist.gov/checklists/xccdf.html) This file validates successfully in <oXygen/> v6.0, but not with <oXygen/> v6.1. v6.1 posts the following errors, which appear to be spurious: SystemID: null Location: 88:47 Description: E sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.w3.org/XML/1998/namespace,lang'. URL: http://www.w3.org/TR/xmlschema-1/#sch-props-correct SystemID: null Location: 95:48 Description: E sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.w3.org/XML/1998/namespace,space'. URL: http://www.w3.org/TR/xmlschema-1/#sch-props-correct SystemID: null Location: 104:45 Description: E sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.w3.org/XML/1998/namespace,base'. URL: http://www.w3.org/TR/xmlschema-1/#sch-props-correct SystemID: null Location: 111:41 Description: E sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.w3.org/XML/1998/namespace,specialAttrs'. URL: http://www.w3.org/TR/xmlschema-1/#sch-props-correct

2 3

Re: [oXygen-user] an extra blank page in the .pdf output + a new question
by Chip Wiegand 15 Aug '05

15 Aug '05

oxygen-user-bounces(a)oxygenxml.com wrote on 08/11/2005 08:41:32 AM: > Hello Chip, > > First read the introduction from: > > http://www.sagehill.net/docbookxsl/TitleFontSizes.html > > as I said before. Titlepage customization is a process with several > steps and first you have to be familiar with some special DocBook > concepts. From the above link you are linked to other relevant pages > that clearly explain the process. Please study them first. > Best regards, > Sorin > > > Chip Wiegand wrote: > >>Use the first method - customizing the titlepage specification file. You > >>have to customize the chapter title specification in > >>titlepage.templates.xml: in the *titlepage* element with the > >>*element="chapter"* attribute change the value of the *font-size* > >>attribute inside the *titlepage-content* element. First read the > >>introduction from: > >> > >>http://www.sagehill.net/docbookxsl/TitleFontSizes.html Hi, I've read that section several times now and it appears there are 3 ways to edit the title properties - customize the titlepage spec file or customize the attribute-set or customize the template So, it looks like the easiest way to get what I need done is to simply change the font-size in the titlepage spec, as you mention above. This is what I have now - <t:titlepage t:element="chapter" t:wrapper="fo:block" font-family="{$title.fontset}"> <t:titlepage-content t:side="recto" margin-left="{$title.margin.left}"> <title t:named-template="component.title" param:node="ancestor-or-self::chapter[1]" font-size="&hsize4;" font-weight="bold"/> The font-size was originally "&hsize5;", but the resulting .pdf file does not reflect the smaller size font in chapter titles, they are still size 5 even though the template is set to size 4 (or 3 or anything). I'm I interpreting the manual incorrectly? Regards, chip

2 2

Question on profile.revision with DocBook in oXygen
by sylvain＠europe-shareware.org 15 Aug '05

15 Aug '05

Hello, I am facing the following problem : My files (I am using DocBook as a DTD) : - I have a book.xml file with "book" as the root. - inside that file I have different "part" elements with some entities inside. - these entities are links to external files I want to include in the book.xml file Overview of book.xml : <!DOCTYPE book SYSTEM "file:/C:/Program%20Files/Oxygen/frameworks/docbook/dtd/docbookx.dtd" [ <!ENTITY % global_entities SYSTEM "global.ent"> %global_entities; ]> <book> <part> <title>My first part</title> &chapter1; &chapter2; </part> </book> Overview of chapter1.xml (file related to &chapter1; entity) : <chapter> <title>My chapter 1</title> <para>blablabla</para> </chapter> Overview of chapter2.xml (file related to &chapter2; entity) : <chapter revision="9.1"> <title>My chapter 2</title> <para>blablabla</para> </chapter> My oXygen transformation scenario : - in the "Parameters" window, I added the following entries : Name : "profile.revision" Value : "9.1" - of course I parameterized the docbook xsl as a cascading style sheet to process profile.xsl first The problem is that in the resulting PDF file I have the chapter1.xml file included but not the chapter2.xml file What did I miss ? In general profiling works well, this is the first time I face such a problem.

2 1