- oXygen-user - www.oxygenxml.com

Selecting/Creating oXygen editor windows
by Michael Smith 03 Nov '10

03 Nov '10

Hello, I have recently been developing a standalone oXygen 12.0 workspace plugin that produces an XML document containing oXygen's track-change processing instructions. Currently this plugin can write its results either to an existing editor or to a file. In the latter case the file is opened in an oXygen editor once it has been written. In the former case, the editor is correctly updated but not selected as the current editor. Is there a way of selecting this output editor as the current editor from within the plugin? I would also like to allow the user to send the output to a "new" freshly constructed editor window with an appropriate "untitled #number" name, where the action of "saving" the document would prompt the user for the location to save the file in. There may be cases where the user just wants to view the result, rather than save it to a file. We generally know the type of document that is being generated (e.g. DITA, DocBook, general XML) so could supply this to the oXygen editor creation API, if this is helpful. Any pointers on how this - or something similar - could be achieved would be welcome. I am new to the oXygen plugin development and this mailing list; and have done my best to search both the API and archive for answers to the issues I have just raised. I apologise in advance for missing previous answers to these questions. Regards, Anthony.

2 2

Plugin access to frameworks and catalogs
by Nigel Whitaker 01 Nov '10

01 Nov '10

Hello, We're developing a workspace plugin which reads form either existing editors or on-disk files. We're using all the catalogs in the standard 12.0 release using this rather brute-force approach: <configProperty name="cat_dita" value="${install.dir}/../../../frameworks/dita/catalog.xml" /> <configProperty name="cat_docbook" value="${install.dir}/../../../frameworks/docbook/catalog.xml" /> ... <configProperty name="cat_xmlspec" value="${install.dir}/../../../frameworks/xmlspec/catalog.xml" /> <configProperty name="xml.catalog.files" value="${cat_dita};${cat_docbook};...${cat_xmlspec}" /> However, we dont know about any user defined frameworks. Is there a way of knowing the framework associations of editors/files so that we could use the specific catalog file (also reducing the possibility of conflicts between the catalogs). Alternatively access to a URI/Entity resolver appropriate for the type of file which we could use when parsing (xerces) may be useful. We know about XMLUtilAccess and its resolvePathThroughCatalogs method, but we'd like something we can use with the resolver/xerces directly. We've also seen some references to a 'grammarCache' object but are unsure how to use it. Is there something we can use to improve our catalog handling. Many thanks, Nigel & Anthony (working on a comparison plugin) -- Nigel Whitaker, DeltaXML: "Change control for XML" nigel.whitaker(a)deltaxml.com http://www.deltaxml.com Registered in England: 02528681 Reg. Office: Monsell House, WR8 0QN, UK

2 3

Can't uninstall/reinstall Eclipse plugin
by Ted Kuster 29 Oct '10

29 Oct '10

I need to reinstall Oxygen Author 12, in Eclipse 3.5.2 on Ubuntu 10.4. I have completely cleaned any traces of Oxygen from my Eclipse installation --a file search reveals no files with any form of the string "oxygen" anywhere in the file system. I have restarted Eclipse with the -clean option. No Oxygen-related options or settings are available anywhere in the Eclipse UI. However, when I try to use Help > Install New Software to install Oxygen, Eclipse refuses on the grounds that Oxygen is already installed. What am I doing wrong? -- Ted Kuster help.collab.net

3 5

GUI change request
by Shannon 26 Oct '10

26 Oct '10

Hi, please consider giving the user the option to hide the Text/Grid/Author controls to increase available space to the editor. I often use a tiny screen on a notebook and have configured a minimal layout--no toolbars or panels whatsoever--; since I never change the view, I'd like to get rid of those buttons too. Thanks, Shannon

2 1

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