- oXygen-user - www.oxygenxml.com

Error: Invalid authority
by Shannon 25 Oct '10

25 Oct '10

Hello, I searched the site and mailing list archive for this error with no results. In the XML Databases perspective, the Data Source Explorer panel returns, "Error: Invalid authority" when I attempt to explore by expanding any one of the Connections, after briefly showing, "Pending…"--these are the same Connections that execute successfully in every other perspective for transforming, querying, and debugging. The Database Source is type MarkLogic. Running Oxygen 11.2 on OS X 10.6.4. Please let me know if you need more information, or what I am doing wrong, thanks, Shannon

2 1

Re: [oXygen-user] Trouble validating SVG document
by Reaves, Timothy 15 Oct '10

15 Oct '10

Thanks for all the info; I now understand what is going on. On Fri, Oct 15, 2010 at 7:31 AM, Chris Lilley <chris(a)w3.org> wrote: > On Friday, October 15, 2010, 11:03:26 AM, Radu wrote: > > RC> Hi Tim, > > RC> W3C describes the content of a <svg> document in a schema-independent > way. > RC> From what I know there are also XML Schemas which can be used to > RC> validate SVG files. > > Yes. > > Going forward, W3C plans to use RelaxNG to define the SVG grammar (and to > recommend NVDL for portioning out a multi-namespace document such that the > SVG parts are validated to the SVG RNG). > > RC> Indeed the usual way to validate a SVG file is by using the DTDs but > DTD > RC> as a grammar specification is not namespace aware and understands > RC> constructs like "xmlns:x" as usual attributes. > > Yes. > > It should not, but DTDs predate namespaces and are not aware of namespace > declarations. > > RC> Radu Coravu > RC> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > RC> http://www.oxygenxml.com > > RC> On 10/14/2010 6:00 PM, Reaves, Timothy wrote: > >> I'm confused then. From > http://www.w3.org/TR/SVG/struct.html#SVGElement > >> they reference to follow what is outlined > >> http://www.w3.org/TR/2006/REC-xml-names-20060816/#ns-decl . > > >> " > > >> An example namespace declaration, which associates the namespace prefix > >> *edi* with the namespace name |http://ecommerce.example.org/schema|<http://ecommerce.example.org/schema%7C> > : > > >> <x xmlns:edi='http://ecommerce.example.org/schema'> > >>  > >> </x> > > >> " > > Yes, that is fine. > > >> So the W3C is recommending something that is invalid? > > No. Its only invalid if using a substandard validation mechanism (DTDs). > Namespace-aware schema languages such as W3C XML Schema or RelaxNG have no > problem with namespace declarations. > > The definition of a conforming SVG fragment is here > http://www.w3.org/TR/SVG/conform.html#ConformingSVGDocuments > > If you want to use extensions in other namespaces and also want the > instances to be DTD valid, this part of the SVG specification explains how > to do that > http://www.w3.org/TR/SVG/extend.html#PrivateElementsAndAttribute > > Lastly, if using SVG files generated by Adobe Illustrator, it is wise to > check the output settings and ensure that the 'round trip' option is not set > (it includes an entire, base64-encoded PDF file into the SVG) and to ensure > that any Adobe extensions are > a) desired > b) actually used > Often, namespace declarations will be present but not actually used. > > A useful program to take SVG generated by various authoring tools and tidy > it up is Scour > http://www.codedread.com/scour/ > > > > >> On Thu, Oct 14, 2010 at 10:56 AM, Radu Coravu <radu_coravu(a)sync.ro > >> <mailto:radu_coravu@sync.ro>> wrote: > > >> Hi Tim, > > >> I will assume that the entities like "&ns_ai;" used in the attribute > >> values are defined in the DTD declaration used to validate the SVG > file. > > >> The problem is that SVG files are validated against DTD grammars. > DTD is > >> not namespace aware, it sees namespace binding attributes like > "xmlns:x" > >> like simple attribute names which need to be declared in the DTD in > >> order to be recognized. > > >> For example in the DTD used by default by Oxygen to validate DTDs > the > >> <svg> root element is defined as having the following attributes: > > >> <!ATTLIST svg > >> xmlns CDATA #FIXED "http://www.w3.org/2000/svg" > >> xmlns:xlink CDATA #FIXED "http://www.w3.org/1999/xlink" > >> %stdAttrs; > >> %testAttrs; > >> %langSpaceAttrs; > >> externalResourcesRequired %Boolean; #IMPLIED > >> class %ClassList; #IMPLIED > >> style %StyleSheet; #IMPLIED > >> %PresentationAttributes-All; > >> viewBox %ViewBoxSpec; #IMPLIED > >> preserveAspectRatio %PreserveAspectRatioSpec; 'xMidYMid meet' > >> zoomAndPan (disable | magnify) 'magnify' > >> %graphicsElementEvents; > >> %documentEvents; > >> version %Number; #FIXED "1.0" > >> x %Coordinate; #IMPLIED > >> y %Coordinate; #IMPLIED > >> width %Length; #IMPLIED > >> height %Length; #IMPLIED > >> contentScriptType %ContentType; "text/ecmascript" > >> contentStyleType %ContentType; "text/css" > > > >> So if you do not add an attribute definition for "xmlns:x" in the > >> attributes list, the DTD will think the attribute is undefined. > > >> Regards, > >> Radu > > >> Radu Coravu > >> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > >> http://www.oxygenxml.com > > >> On 10/14/2010 4:50 PM, Reaves, Timothy wrote: > >> > I have an SVG document where the openeing SVG element is: > >> > <svg version="1.0" xmlns:x="&ns_extend;" xmlns:i="&ns_ai;" > >> > xmlns:graph="&ns_graphs;" xmlns="&ns_svg;" > xmlns:xlink="&ns_xlink;" > >> > width="497.611" height="591.554" viewBox="0 0 497.611 > 591.554" > >> > style="overflow:visible;enable-background:new 0 0 497.611 > >> 591.554;" > >> > xml:space="preserve"> > >> > > >> > > >> > Validation fails on each of the xmlns attributes. This should be > >> valid. > >> > The errors look like: > >> > SystemID: /home/bv6679/Development/images/HSVG/99571_97YA_17.svg > >> > Engine name: Xerces > >> > Severity: error > >> > Description: Attribute "xmlns:x" must be declared for element > >> type "svg". > >> > Start location: 29:21 > >> > End location: 29:42 > >> > > >> > Any ideas? > >> > _______________________________________________ > >> > oXygen-user mailing list > >> > oXygen-user(a)oxygenxml.com <mailto:oXygen-user@oxygenxml.com> > >> > http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > >> _______________________________________________ > >> oXygen-user mailing list > >> oXygen-user(a)oxygenxml.com <mailto:oXygen-user@oxygenxml.com> > >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > > > RC> _______________________________________________ > RC> oXygen-user mailing list > RC> oXygen-user(a)oxygenxml.com > RC> http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > > -- > Chris Lilley Technical Director, Interaction Domain > W3C Graphics Activity Lead, Fonts Activity Lead > Co-Chair, W3C Hypertext CG > Member, CSS, WebFonts, SVG Working Groups > >

1 0

Trouble validating SVG document
by Reaves, Timothy 15 Oct '10

15 Oct '10

I have an SVG document where the openeing SVG element is: <svg version="1.0" xmlns:x="&ns_extend;" xmlns:i="&ns_ai;" xmlns:graph="&ns_graphs;" xmlns="&ns_svg;" xmlns:xlink="&ns_xlink;" width="497.611" height="591.554" viewBox="0 0 497.611 591.554" style="overflow:visible;enable-background:new 0 0 497.611 591.554;" xml:space="preserve"> Validation fails on each of the xmlns attributes. This should be valid. The errors look like: SystemID: /home/bv6679/Development/images/HSVG/99571_97YA_17.svg Engine name: Xerces Severity: error Description: Attribute "xmlns:x" must be declared for element type "svg". Start location: 29:21 End location: 29:42 Any ideas?

3 2

Re: [oXygen-user] Trouble validating SVG document
by Radu Coravu 15 Oct '10

15 Oct '10

Hi Tim, W3C describes the content of a <svg> document in a schema-independent way. From what I know there are also XML Schemas which can be used to validate SVG files. Indeed the usual way to validate a SVG file is by using the DTDs but DTD as a grammar specification is not namespace aware and understands constructs like "xmlns:x" as usual attributes. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 10/14/2010 6:00 PM, Reaves, Timothy wrote: > I'm confused then. From http://www.w3.org/TR/SVG/struct.html#SVGElement > they reference to follow what is outlined > http://www.w3.org/TR/2006/REC-xml-names-20060816/#ns-decl . > > " > > An example namespace declaration, which associates the namespace prefix > *edi* with the namespace name |http://ecommerce.example.org/schema|: > > <x xmlns:edi='http://ecommerce.example.org/schema'> >  > </x> > > " > > So the W3C is recommending something that is invalid? > > > > On Thu, Oct 14, 2010 at 10:56 AM, Radu Coravu <radu_coravu(a)sync.ro > <mailto:radu_coravu@sync.ro>> wrote: > > Hi Tim, > > I will assume that the entities like "&ns_ai;" used in the attribute > values are defined in the DTD declaration used to validate the SVG file. > > The problem is that SVG files are validated against DTD grammars. DTD is > not namespace aware, it sees namespace binding attributes like "xmlns:x" > like simple attribute names which need to be declared in the DTD in > order to be recognized. > > For example in the DTD used by default by Oxygen to validate DTDs the > <svg> root element is defined as having the following attributes: > > <!ATTLIST svg > xmlns CDATA #FIXED "http://www.w3.org/2000/svg" > xmlns:xlink CDATA #FIXED "http://www.w3.org/1999/xlink" > %stdAttrs; > %testAttrs; > %langSpaceAttrs; > externalResourcesRequired %Boolean; #IMPLIED > class %ClassList; #IMPLIED > style %StyleSheet; #IMPLIED > %PresentationAttributes-All; > viewBox %ViewBoxSpec; #IMPLIED > preserveAspectRatio %PreserveAspectRatioSpec; 'xMidYMid meet' > zoomAndPan (disable | magnify) 'magnify' > %graphicsElementEvents; > %documentEvents; > version %Number; #FIXED "1.0" > x %Coordinate; #IMPLIED > y %Coordinate; #IMPLIED > width %Length; #IMPLIED > height %Length; #IMPLIED > contentScriptType %ContentType; "text/ecmascript" > contentStyleType %ContentType; "text/css" > > > So if you do not add an attribute definition for "xmlns:x" in the > attributes list, the DTD will think the attribute is undefined. > > Regards, > Radu > > Radu Coravu > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > > On 10/14/2010 4:50 PM, Reaves, Timothy wrote: > > I have an SVG document where the openeing SVG element is: > > <svg version="1.0" xmlns:x="&ns_extend;" xmlns:i="&ns_ai;" > > xmlns:graph="&ns_graphs;" xmlns="&ns_svg;" xmlns:xlink="&ns_xlink;" > > width="497.611" height="591.554" viewBox="0 0 497.611 591.554" > > style="overflow:visible;enable-background:new 0 0 497.611 > 591.554;" > > xml:space="preserve"> > > > > > > Validation fails on each of the xmlns attributes. This should be > valid. > > The errors look like: > > SystemID: /home/bv6679/Development/images/HSVG/99571_97YA_17.svg > > Engine name: Xerces > > Severity: error > > Description: Attribute "xmlns:x" must be declared for element > type "svg". > > Start location: 29:21 > > End location: 29:42 > > > > Any ideas? > > _______________________________________________ > > oXygen-user mailing list > > oXygen-user(a)oxygenxml.com <mailto:oXygen-user@oxygenxml.com> > > http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com <mailto:oXygen-user@oxygenxml.com> > http://www.oxygenxml.com/mailman/listinfo/oxygen-user > >

1 0

The entity "nbsp" was referenced, but not declared
by Yves Barbion 13 Oct '10

13 Oct '10

Hi group I know this topic has been discussed before, so I'm sorry to bother you with this again. I've got non-breaking spaces in my topics (&nbsp) and when I generate XHTML output with oXygen XML Author, my build fails and I get the message: "The entity "nbsp" was referenced, but not declared." I get a "build successful" with oXygen XML Editor though, so I must have fixed it there in some way, but I cannot remember how anymore. I also searched the archives, but to no avail. Can someone please refresh my memory? Thanks. -- Yves Barbion www.scripto.nu

2 1

Transform Scenarios for Archives
by Eliot Kimber 06 Oct '10

06 Oct '10

I have packaged my Word-to-DITA process as a Toolkit plugin. The input to this process is a DOCX file. My first instinct was to use Oxygen to apply the Toolkit to the DOCX file by setting up a transformation scenario, but then I saw that the Archive Browser doesn't provide its own transformation scenario option. Is it sensible for it to provide transformation scenarios? If it id, it would probably make sense to provide the option of controlling the unzipping of the archive. In my case the Ant process will do the unzipping, but it could be convenient to have Oxygen handle it. Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

2 1

Toggle perspectives layout in 1 click
by Yves Barbion 05 Oct '10

05 Oct '10

Hi group I've got two "perspective layouts": - One for the tech writer with tags shown and the relevant panels and toolbars open - One for the SME with tags hidden and only the DITA Maps Manager and the Elements and Attributes panels open. When I want to select the other perspectives layout, I have to do this in Options > Preferences, and then also click the Full Tags/No Tags button. Is there a way to do both actions in 1 click? It would be nice to have a button (or a keybord shortcut) to switch between my layouts. Cheers -- Yves Barbion www.scripto.nu

2 1

New document in oXygen
by Wendell Piez 28 Sep '10

28 Sep '10

Hi, I'm also having trouble with the New Document option in v12. In my line of work, I'm frequently (very frequently) using a new schema provided by a client or associate. Say I want to create a document using it. In v11, I had the choice of saying File/New and then selecting the schema in a dialogue. Unless I'm missing it, I can't do that any more. What's more, if I go ahead and create a blank XML document, I can't bind it to a schema until I have a document element. Sometimes I'll know in advance what the type of that element should be (along with namespace etc.) -- but not always. Maybe the capability of starting a new document with an arbitrary schema binding is right in front of me somewhere? Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

3 2

Re: [oXygen-user] Compiling external HTML resources upon transform to CHM
by Radu Coravu 28 Sep '10

28 Sep '10

Hi Khaled, For DITA publishing Oxygen just runs an external ANT process on the DITA Open Toolkit. You will have to make modifications to the ANT build files in order to copy additional non-DITA resources to the output folder. Then, if the resources are in the output folder they should be incorporated in the CHM. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 9/28/2010 6:37 PM, Khaled Aly wrote: > Hi Radu > > Actually the html together with the common css and img folders resources > are placed outside both dita source and output files. They are > referenced via related-links > link element. This worked well for the > html since they need not be copied in this case (just referenced), but > when transforming to chm they cannot be compiled and that is normal > since they are not copied. So I was wondering if there is an oXygen > parameter to let the chm transformation scenario copy them and compile > them, or should this be done in the build file? > > Thanks & regards, > Khaled > > Technopsis.com > ICT Research & Documentation > Desk: +20 (0)2 2415 4164 > Mobile: +20 (0)12 294 6280 > Skype:ka.aly > > On 9/28/2010 1:36 PM, Radu Coravu wrote: >> Hi Khaled, >> >> So, if from the DITA Topic you refer to the HTML file like: >> <xref href="documentation.html" format="html"/> >> and the file is copied placed in the output folder relative to the >> DITA Topic which references it, then if you build the CHM it should >> incorporate inside also the html file. >> >> Regards, >> Radu >> >> Radu Coravu >> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger >> http://www.oxygenxml.com >> >> >> On 9/27/2010 1:13 PM, Khaled Aly wrote: >>> Hello oXygen users >>> >>> I had a problem getting the oXygen generated html documentation of XSL >>> files to be copied to output folder, being referenced from a link >>> element within a glossentry topic. I got over this by placing the shared >>> resources in a folder that's external to both dita source and output. >>> When transforming to chm, the html file referenced was not compiled and >>> hence could not be displayed in html help. >>> >>> Is there any oXygen transformatio nmenu parameter that could be set (or >>> added to be set) to enable chm to compile html resources that are >>> external to the transformation output folder? >>> >>> Thanks& regards, >>> Khaled >>> >> >>

1 0

Compiling external HTML resources upon transform to CHM
by Khaled Aly 28 Sep '10

28 Sep '10

Hello oXygen users I had a problem getting the oXygen generated html documentation of XSL files to be copied to output folder, being referenced from a link element within a glossentry topic. I got over this by placing the shared resources in a folder that's external to both dita source and output. When transforming to chm, the html file referenced was not compiled and hence could not be displayed in html help. Is there any oXygen transformatio nmenu parameter that could be set (or added to be set) to enable chm to compile html resources that are external to the transformation output folder? Thanks & regards, Khaled -- Technopsis.com ICT Research & Documentation Desk: +20 (0)2 2415 4164 Mobile: +20 (0)12 294 6280 Skype:ka.aly

2 1