- oXygen-user - www.oxygenxml.com

feature request: copy file path
by Lars Huttar 22 Aug '08

22 Aug '08

Hello, I have a feature request: When I'm editing a file in Oxygen, often I need to go find that file in another application (such as Windows Explorer, or WinMerge, etc.). If the file has a long path, it takes a while to re-find it. Right now, the file's full path shows up in the Oxygen title bar, and in the tooltip for the editor buffer tab, but there is no apparent way to copy it to the clipboard. It would be very convenient to have a "Copy Path" or "Copy File Path" command on the right-click menu of the editor buffer tab, the red-circled area in the screenshot below. That way, the user does not have to re-navigate to a deeply-buried file. editor buffer tab Thanks, Lars

3 3

Intelligent editor support for DITA specialisations
by Hedley Finger 20 Aug '08

20 Aug '08

One of the advantages of DITA that was loudly proclaimed is that specialised topic files from one creator can be sent to another user and inserted into a document /without the specialised DTD being made available to that user/. The DITA OT will then produce some sort of readable (if badly formatted) output based on the parent element identified in the @class attribute. But it appears that none of the DITA-out-of-the-box editors which I have support specialisation in the absence of the specialisation DTD but barf in various interesting ways. Serna alone appears to make some attempt to support specialised elements. I have made a tiny tweak to <fig> to specialise it with a <credit> element based on , and an <anchor> element based on . This are subclassed in the approved manner, e.g. class=" topic/p topic/credit". It seems to me that a DITA editor on opening an unknown specialisation should be able to look at the inheritance tree in @class and temporarily rename the element to the nearest known ancestor. And, on save, it should write out the XML with the original element name restored from the leaf value in @class. As DITA is not a true object model and subclasses are merely renaming of ancestor elements for better semantic cueing, this does not appear to be a very difficult problem to solve. Anything would be better than the endless bleatings of Xalan error messages! I am basing my remarks on experience with Syntext Serna, <oXygen/>, XMLmind XML Editor (XXE), and FrameMaker v 8 with DITA-FMx 1.0. Perhaps XMetaL, Arbortext Author, and other editors already support this kind of compatibility. Regards, Hedley -- Hedley Finger 28 Regent Street Camberwell VIC 3124 Australia Tel. +61 3 9809 1229 Fax. (call phone first) Mob. (cell) +61 412 461 558 Email. "Hedley Finger" <hfinger(a)handholding.com.au>

1 0

Re: Whitespace Problem
by Philipp Steinkrüger 15 Aug '08

15 Aug '08

Hi, thanks for your answer, Sorin. I understand Oxygen Author-Mode is not able to do what i want, but i think it should be! There should be an option telling the renderer to just ignore line-breaks. I fail to see any reason why the transformation into whitespaces is necessary. Can this be added to the feature request list? Best, Philipp > Message: 2 > Date: Thu, 14 Aug 2008 18:05:51 +0300 > From: Sorin Ristache <sorin(a)oxygenxml.com> > Subject: Re: [oXygen-user] Whitespace Problem > To: oxygen-user(a)oxygenxml.com > Message-ID: <48A449CF.2070307(a)oxygenxml.com> > Content-Type: text/plain; charset=ISO-8859-15; format=flowed > > Hello, > > The whitespaces including line breaks are normalized when the XML > document is rendered in the Author mode. That means the line breaks > between <orig>E</orig> and <reg>e</reg>, between <reg>e</reg> and > </choice>, etc are replaced with a space character. If the Author mode > removes them without replacing them with a space character then the new > XML document is not the normalized version of the old one. > > The only way to display "Der Eerwirdigen" in the Author mode is to > remove the whitespaces yourself from the XML document before switching > to the Author mode: > > > > Der > <choice> > <orig>E</orig><reg>e</reg></choice>rwirdigen in > <choice> > ... > > > Regards, > Sorin > > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 14 Aug 2008 16:33:23 +0200 > From: Philipp Steinkr?ger <philipp.steinkrueger(a)uni-koeln.de> > Subject: [oXygen-user] Whitespace Problem > To: oxygen-user(a)oxygenxml.com > Message-ID: <48A44233.8060603(a)uni-koeln.de> > Content-Type: text/plain; charset=ISO-8859-15; format=flowed > > Hello! > > i am having a problem with white-spaces in Author mode. Here is what my > XML document looks like at the problematic passage: > > > Der > <choice> > <orig>E</orig> > <reg>e</reg> > </choice> > rwirdigen in > <choice> > <orig>G</orig> > <reg>g</reg> > </choice> > > > Now in Author mode, the linebreaks are transformed into whitespace, so > that the first part looks like "Der E e rwirdigen in" etc. But i would > like to have it look like "Der Eerwirdigen" etc. has the display > property: block, <choice>, <orig> and <reg> have display property inline, > and i think that exactly is the problem, because the manual says that if > the display-property is inline, non-whitespace (which my linebreak is, i > suppose) are transformed into normal white space. > Is there any way to have oxygen ignore the linebreak? > > Thank you very much, > Philipp > > > -- Philipp Steinkrüger M.A. Philosophisches Seminar der Universität zu Köln - Thomas-Institut - Universitätsstraße 22 50923 Köln Fon +49 221 4702394 Fax +49 221 4705011 philipp.steinkrueger(a)uni-koeln.de http://www.philosophie.uni-koeln.de http://www.thomasinstitut.uni-koeln.de UNIVERSITÄT ZU KÖLN GUTE IDEEN. SEIT 1388.

2 1

Whitespace Problem
by Philipp Steinkrüger 14 Aug '08

14 Aug '08

Hello! i am having a problem with white-spaces in Author mode. Here is what my XML document looks like at the problematic passage: Der <choice> <orig>E</orig> <reg>e</reg> </choice> rwirdigen in <choice> <orig>G</orig> <reg>g</reg> </choice> Now in Author mode, the linebreaks are transformed into whitespace, so that the first part looks like "Der E e rwirdigen in" etc. But i would like to have it look like "Der Eerwirdigen" etc. has the display property: block, <choice>, <orig> and <reg> have display property inline, and i think that exactly is the problem, because the manual says that if the display-property is inline, non-whitespace (which my linebreak is, i suppose) are transformed into normal white space. Is there any way to have oxygen ignore the linebreak? Thank you very much, Philipp -- Philipp Steinkrüger M.A. Philosophisches Seminar der Universität zu Köln - Thomas-Institut - Universitätsstraße 22 50923 Köln Fon +49 221 4702394 Fax +49 221 4705011 philipp.steinkrueger(a)uni-koeln.de http://www.philosophie.uni-koeln.de http://www.thomasinstitut.uni-koeln.de UNIVERSITÄT ZU KÖLN GUTE IDEEN. SEIT 1388.

2 1

Re: Failed to read schema document
by Jing, Jenny 11 Aug '08

11 Aug '08

Hi, Sorin: We use eXist 1.2.3. I set up the config.xml validation=yes. I also copied our schema files into this folder: \eXist\webapp\WEB-INF\entities Then I add the name and uri in the catalog.xml: ( I just added the three lines of our own schemas in the <uri name= > in the default catalog.xml.) Catalog.xml  <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> <uri name="http://www.w3.org/XML/1998/namespace" uri="entities/xml.xsd"/> <uri name="http://www.w3.org/2001/XMLSchema" uri="entities/XMLSchema.xsd"/> <uri name="http://localhost:8080/exist/db/Test/common/schemas/work" uri="entities/works.xsd"/> <uri name="http://localhost:8080/exist/db/Test/common/schemas/about" uri="entities/about.xsd"/> <uri name="http://localhost:8080/exist/db/Test/common/schemas/common" uri="entities/common.xsd"/> <uri name="urn:oasis:names:tc:entity:xmlns:xml:catalog" uri="entities/catalog.xsd" /> </catalog> This is how I define in our xml record: <work xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://localhost:8080/exist/db/Test/common/schemas/work"> </work> But the setting doesn't seem work because the records are not validated by the schema at all. For example, if we delete a required field, the record is still validated. But if I tried to save a record, the error message appears. I don't know whether it's caused by eXist setting or by Oxygen, or the connection between them. Any suggestion is welcome! Thanks. Jenny -----Original Message----- From: oxygen-user-bounces(a)oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of oxygen-user-request(a)oxygenxml.com Sent: Friday, August 08, 2008 1:00 PM To: oxygen-user(a)oxygenxml.com Subject: oXygen-user Digest, Vol 59, Issue 3 Send oXygen-user mailing list submissions to oxygen-user(a)oxygenxml.com To subscribe or unsubscribe via the World Wide Web, visit http://www.oxygenxml.com/mailman/listinfo/oxygen-user or, via email, send a message with subject or body 'help' to oxygen-user-request(a)oxygenxml.com You can reach the person managing the list at oxygen-user-owner(a)oxygenxml.com When replying, please edit your Subject line so it is more specific than "Re: Contents of oXygen-user digest..." Today's Topics: 1. Failed to read schema document (Jing, Jenny) 2. Re: Failed to read schema document (Sorin Ristache) ---------------------------------------------------------------------- Message: 1 Date: Thu, 7 Aug 2008 23:21:07 -0400 From: "Jing, Jenny" <jjing(a)hbs.edu> Subject: [oXygen-user] Failed to read schema document To: "oxygen-user(a)oxygenxml.com" <oxygen-user(a)oxygenxml.com> Message-ID: <18EA3ABA6E54124EB3CE222C13F68A460127FCFE8F58(a)WINHBSMAIL01.hbs.edu> Content-Type: text/plain; charset="us-ascii" Hi, I'm trying to set up eXist to validate records with schema. But I keep getting error message when I tried to save a record in eXist. Cannot save the file. org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'file:/export/home/library/eXist/webapp//WEB-INF/entities/works.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. Does anyone know what might cause this error message? The schema's root is <xsd:schema> I am sure about that. Thanks. Jenny ------------------------------ Message: 2 Date: Fri, 08 Aug 2008 15:13:03 +0300 From: Sorin Ristache <sorin(a)oxygenxml.com> Subject: Re: [oXygen-user] Failed to read schema document To: "oxygen-user(a)oxygenxml.com" <oxygen-user(a)oxygenxml.com> Message-ID: <489C384F.2020402(a)oxygenxml.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello, I get this error when the schema used for validation cannot be found at the location specified in the XML document. In your case if there is a works.xsd file on the hard disk and the root element of the works.xsd file is xsd:schema the location is not specified correctly in the XML document. Does works.xsd exist in the directory specified in the XML document that you try to add to eXist? /export/home/library/eXist/webapp/WEB-INF/entities/works.xsd If it exists what is the version of your eXist server? Regards, Sorin Jing, Jenny wrote: > Hi, > > I'm trying to set up eXist to validate records with schema. But I keep getting error message when > I tried to save a record in eXist. > > Cannot save the file. org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'file:/export/home/library/eXist/webapp//WEB-INF/entities/works.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. > > Does anyone know what might cause this error message? > The schema's root is <xsd:schema> I am sure about that. > > Thanks. > > Jenny ------------------------------ _______________________________________________ oXygen-user mailing list oXygen-user(a)oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user End of oXygen-user Digest, Vol 59, Issue 3 ******************************************

2 1

Failed to read schema document
by Jing, Jenny 08 Aug '08

08 Aug '08

Hi, I'm trying to set up eXist to validate records with schema. But I keep getting error message when I tried to save a record in eXist. Cannot save the file. org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'file:/export/home/library/eXist/webapp//WEB-INF/entities/works.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. Does anyone know what might cause this error message? The schema's root is <xsd:schema> I am sure about that. Thanks. Jenny

2 1

OS X: Can not paste text as filename into save dialog.
by Jan Nylund 06 Aug '08

06 Aug '08

Hello! We just noticed that in both oxygen 9.2 and 9.3 it's not possible to paste text as the filename into a save dialog. Pasted text will instead appear in the document where you had the cursor placed before opening the save dialog. This may appear in other versions as well, we only tested what we had available. Br, Jan -- Jan Nylund Senior System Designer Citec Information Oy Ab

2 3

Add to Project
by Shannon Scott Shiflett 29 Jul '08

29 Jul '08

Hi, It would be most handy if I could drag a document tab and drop it in the Project pane to add it to the project. I know I can right-click and choose "Add to project" but the drag & drop choice just feels right. Thanks, __________________________________________________ Shannon Scott Shiflett, programmer/analyst with ROTUNDA, The University of Virginia Press, Charlottesville, VA USA http://rotunda.upress.virginia.edu

3 3

request: code templates for XSLT 2.0
by Lars Huttar 24 Jul '08

24 Jul '08

Hello, I use the code templates feature a lot when creating XSLT stylesheets. But now as I move more into XSLT 2.0, I notice the absence of code templates for the new elements. E.g. fegs: <xsl:for-each-group select="${caret}"> </xsl:for-each-group> rdh: <xsl:result-document href="${caret}"> </xsl:result-document> cg: current-group() and others. Any plans to add these? I will add some of my own for now, but I would welcome a full set that came with Oxygen. (I'm running Oxygen 9.3 standalone on Windows.) Regards, Lars

2 1

Problem validating XQuery documents
by John Kelly 22 Jul '08

22 Jul '08

Hello, I'm modifying an XQuery document under 9.3 and am not getting validation as I type. I tried manually running validation and got an error that says "The transformer Saxon9B XQuery is not available anymore. Please reconfigure the transformation scenario." I created a custom validation scenario with the "<default engine>" and go the same error. When I changed that validation scenario to specifically use "Saxon-B XQuery 9.0.0.6", it worked. Seems like there may be a bug in the default setup. . John

2 1