From bogus@does.not.exist.com  Fri Apr  4 06:04:41 2008
From: bogus@does.not.exist.com (Robert Koberg)
Date: Fri, 04 Apr 2008 07:04:41 -0400
Subject: [oXygen-user] xml:space="preserve" and IDE space preserve
Message-ID: <1207307081.16660.61.camel@rkoberg-laptop>

Hi,

Let's say I have this is one page:

<div>
  <script xml:space="preserve">
if (true) {
  alert("boo");
}
  </script>
</div>

If I paste that with the xml:space *or* with the element included IDE's
Options Preference for 'Preserve Space elements (XPath)' the result of
the past is:

<div>
  <script xml:space="preserve">
    if (true) {
    alert("boo");
    }
  </script>
</div>

Is this a bug?

best,
-Rob
 



From bogus@does.not.exist.com  Fri Apr  4 09:10:37 2008
From: bogus@does.not.exist.com (George Cristian Bina)
Date: Fri, 04 Apr 2008 17:10:37 +0300
Subject: [oXygen-user] xml:space="preserve" and IDE space preserve
In-Reply-To: <1207307081.16660.61.camel@rkoberg-laptop>
References: <1207307081.16660.61.camel@rkoberg-laptop>
Message-ID: <47F636DD.9080609@oxygenxml.com>

Hi Robert,

The behavior is configurable.
You need to disable the "Indent (when typing) in preserve space 
elements" option from Options->Preferences -- Editor -- Format -- XML, 
Indent group.

Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina - http://aboutxml.blogspot.com/
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


Robert Koberg wrote:
> Hi,
> 
> Let's say I have this is one page:
> 
> <div>
>   <script xml:space="preserve">
> if (true) {
>   alert("boo");
> }
>   </script>
> </div>
> 
> If I paste that with the xml:space *or* with the element included IDE's
> Options Preference for 'Preserve Space elements (XPath)' the result of
> the past is:
> 
> <div>
>   <script xml:space="preserve">
>     if (true) {
>     alert("boo");
>     }
>   </script>
> </div>
> 
> Is this a bug?
> 
> best,
> -Rob
>  
> 
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user


From bogus@does.not.exist.com  Sun Apr  6 02:58:23 2008
From: bogus@does.not.exist.com (mozer)
Date: Sun, 6 Apr 2008 09:58:23 +0200
Subject: [oXygen-user] Format and Indent Problem
In-Reply-To: <21d9ade60707220447y25250067l4a42f7259983c028@mail.gmail.com>
References: <469DB173.1040206@asiatype.com> <46A0759E.9040502@oxygenxml.com>
	<21d9ade60707220447y25250067l4a42f7259983c028@mail.gmail.com>
Message-ID: <21d9ade60804060058o58d6d61av751c42c13f399d15@mail.gmail.com>

Dear,

Is there any chance to have such option soon in Oxygen XML ?

Regards,

Xmlizer

On Sun, Jul 22, 2007 at 1:47 PM, mozer <xmlizer at > wrote:

> Dear,
>
> May I propose (once again) a neutral form of indent for Oxygen
>
> <root id="2"
>  >  <element position="1">  space   are important   here </element
>  > <element position="2"> space   are also   important  here </element
>
> > </root>
> >
>
> The only thing you can allow or not is to convert newline and tabs to
> space as an option
>
> Regards,
>
> Xmlizer
>
>
> On 7/20/07, Sorin Ristache <sorin at > wrote:
>
> > Hello,
> >
> > There are no other workarounds yet. You have to specify the elements for
> > which you want to preserve whitespace in one of the two ways. If you
> > specify them in preferences you can store the Editor / Format /XML
> > preferences at project level to avoid adding all the elements for all
> > the projects in the same Preserve space elements table.
> >
> > We have this request already logged in our issue tracking system for a
> > future version of oXygen.
> >
> >
> > Regards,
> > Sorin
> >
> >
> > Jeff Sese wrote:
> > > 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
> > > _______________________________________________
> > > oXygen-user mailing list
> > > oXygen-user at 
> > > http://www.oxygenxml.com/mailman/listinfo/oxygen-user
> > _______________________________________________
> > oXygen-user mailing list
> > oXygen-user at 
> > http://www.oxygenxml.com/mailman/listinfo/oxygen-user
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20080406/6e63cd5d/attachment.html 

From bogus@does.not.exist.com  Sun Apr  6 09:44:59 2008
From: bogus@does.not.exist.com (mozer)
Date: Sun, 6 Apr 2008 16:44:59 +0200
Subject: [oXygen-user] Add XSLStyle by default in OxygenXML
Message-ID: <21d9ade60804060744n4d17443dje1489f08499ccd76@mail.gmail.com>

Dear,

I ask for a new integration to add by default XSLStyle inside OxygenXML

Regards,

Xmlizer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20080406/c70a43f5/attachment.html 

From bogus@does.not.exist.com  Tue Apr  8 06:38:34 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Tue, 08 Apr 2008 14:38:34 +0300
Subject: [oXygen-user] Format and Indent Problem
In-Reply-To: <21d9ade60707220447y25250067l4a42f7259983c028@mail.gmail.com>
References: <469DB173.1040206@asiatype.com> <46A0759E.9040502@oxygenxml.com>
	<21d9ade60707220447y25250067l4a42f7259983c028@mail.gmail.com>
Message-ID: <47FB593A.3080004@oxygenxml.com>

Hello,

I understand that your proposal is to normalize some text 
nodes (the text nodes with whitespace characters and non 
whitespace characters but not the text nodes with whitespace 
characters only) even if that leads to lines that exceed the 
maximum line length set in Preferences -> Editor -> Format. 
I consider breaking the lines that exceed the maximum length 
one of the main factors that make the pretty-printed 
document more readable. Without enforcing this maximum 
length the document will not be more readable after the 
pretty-print operation.

If I misunderstand your proposal please give a complete 
example of what you mean.


Regards,
Sorin


mozer wrote:
> May I propose (once again) a neutral form of indent for Oxygen
> 
> <root id="2"
>  >  <element position="1">  space   are important   here </element
>  > <element position="2"> space   are also   important  here </element
>> </root>
> 
> The only thing you can allow or not is to convert newline and tabs to
> space as an option


From bogus@does.not.exist.com  Tue Apr  8 10:15:00 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Tue, 08 Apr 2008 18:15:00 +0300
Subject: [oXygen-user] Add XSLStyle by default in OxygenXML
In-Reply-To: <21d9ade60804060744n4d17443dje1489f08499ccd76@mail.gmail.com>
References: <21d9ade60804060744n4d17443dje1489f08499ccd76@mail.gmail.com>
Message-ID: <47FB8BF4.3020107@oxygenxml.com>

Hello,

Do you mean the XSLT stylesheets package for documenting 
XSLT stylesheets? We will consider it as a possible XSLT 
documentation framework to be added in a future version of 
oXygen. However this integration is not trivial as we need 
to add support for adding/editing the documentation of the 
XSLT stylesheet elements inside the documented stylesheet 
using elements like xs:doc, xs:title, xs:template, xs:param 
from the namespace accepted by XSLStyle, that is 
"http://www.CraneSoftwrights.com/ns/xslstyle".


Thank you for your suggestion,
Sorin


mozer wrote:
> Dear,
>  
> I ask for a new integration to add by default XSLStyle inside OxygenXML
>  
> Regards,
>  
> Xmlizer


From bogus@does.not.exist.com  Tue Apr  8 10:14:55 2008
From: bogus@does.not.exist.com (Robert Koberg)
Date: Tue, 08 Apr 2008 11:14:55 -0400
Subject: [oXygen-user] Add XSLStyle by default in OxygenXML
In-Reply-To: <47FB8BF4.3020107@oxygenxml.com>
References: <21d9ade60804060744n4d17443dje1489f08499ccd76@mail.gmail.com>
	<47FB8BF4.3020107@oxygenxml.com>
Message-ID: <1207667695.6390.2.camel@rkoberg-laptop>

This would be pretty cool.

best,
-Rob


On Tue, 2008-04-08 at 18:15 +0300, Sorin Ristache wrote:
> Hello,
> 
> Do you mean the XSLT stylesheets package for documenting 
> XSLT stylesheets? We will consider it as a possible XSLT 
> documentation framework to be added in a future version of 
> oXygen. However this integration is not trivial as we need 
> to add support for adding/editing the documentation of the 
> XSLT stylesheet elements inside the documented stylesheet 
> using elements like xs:doc, xs:title, xs:template, xs:param 
> from the namespace accepted by XSLStyle, that is 
> "http://www.CraneSoftwrights.com/ns/xslstyle".
> 
> 
> Thank you for your suggestion,
> Sorin
> 
> 
> mozer wrote:
> > Dear,
> >  
> > I ask for a new integration to add by default XSLStyle inside OxygenXML
> >  
> > Regards,
> >  
> > Xmlizer
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user



From bogus@does.not.exist.com  Tue Apr  8 14:05:19 2008
From: bogus@does.not.exist.com (mozer)
Date: Tue, 8 Apr 2008 21:05:19 +0200
Subject: [oXygen-user] Format and Indent Problem
In-Reply-To: <47FB593A.3080004@oxygenxml.com>
References: <469DB173.1040206@asiatype.com> <46A0759E.9040502@oxygenxml.com>
	<21d9ade60707220447y25250067l4a42f7259983c028@mail.gmail.com>
	<47FB593A.3080004@oxygenxml.com>
Message-ID: <21d9ade60804081205t1d46a5a5w985fa02e3e8f5191@mail.gmail.com>

Not exactly

My proposal is, starting from an xml file to add space and carriage return
*INSIDE* tags

Doing this, the nature of space (ignorable or not) won't matter anymore
since it won't have any impact

Let me give a simple example

<root><a><b></b><c></c></a></root>

into
<root
 ><a
  ><b
  ></b
  ><c
  ></c
 ></a
></root
>
May it would make the will less readable than a full indent, but in some
case, it is just sufficient for debbugging and don't need further
parametrization

Regards,

Xmlizer


On Tue, Apr 8, 2008 at 1:38 PM, Sorin Ristache <sorin at > wrote:

> Hello,
>
> I understand that your proposal is to normalize some text nodes (the text
> nodes with whitespace characters and non whitespace characters but not the
> text nodes with whitespace characters only) even if that leads to lines that
> exceed the maximum line length set in Preferences -> Editor -> Format. I
> consider breaking the lines that exceed the maximum length one of the main
> factors that make the pretty-printed document more readable. Without
> enforcing this maximum length the document will not be more readable after
> the pretty-print operation.
>
> If I misunderstand your proposal please give a complete example of what
> you mean.
>
>
> Regards,
> Sorin
>
>
> mozer wrote:
>
> > May I propose (once again) a neutral form of indent for Oxygen
> >
> > <root id="2"
> >  >  <element position="1">  space   are important   here </element
> >  > <element position="2"> space   are also   important  here </element
> >
> > > </root>
> > >
> >
> > The only thing you can allow or not is to convert newline and tabs to
> > space as an option
> >
>  _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20080408/9bec731e/attachment.html 

From bogus@does.not.exist.com  Fri Apr 11 07:01:01 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Fri, 11 Apr 2008 15:01:01 +0300
Subject: [oXygen-user] Format and Indent Problem
In-Reply-To: <21d9ade60804081205t1d46a5a5w985fa02e3e8f5191@mail.gmail.com>
References: <469DB173.1040206@asiatype.com>
	<46A0759E.9040502@oxygenxml.com>	<21d9ade60707220447y25250067l4a42f7259983c028@mail.gmail.com>	<47FB593A.3080004@oxygenxml.com>
	<21d9ade60804081205t1d46a5a5w985fa02e3e8f5191@mail.gmail.com>
Message-ID: <47FF52FD.4060509@oxygenxml.com>

Hello,

Do you mean debugging an XSLT transformation applied to an 
XML file formatted as in your example? I think an XSLT 
debugger is more useful for that and it does not depend on 
the text format of the XML file. For example when you click 
on a row in the Context view or in the XWatch view of the 
oXygen XSLT debugger the start tag of the corresponding XML 
element is highlighted in the XML editor panel. You need 
just to click in a view of the XSLT debugger to go directly 
to the corresponding XML element in the source editor.


Regards,
Sorin


mozer wrote:
> Let me give a simple example
>  
> <root><a><b></b><c></c></a></root>
>  
> into
> <root
>  ><a
>   ><b
>   ></b
>   ><c
>   ></c
>  ></a
>  ></root
>  >
> May it would make the will less readable than a full indent, but in some 
> case, it is just sufficient for debbugging and don't need further 
> parametrization


From bogus@does.not.exist.com  Fri Apr 11 09:19:22 2008
From: bogus@does.not.exist.com (mozer)
Date: Fri, 11 Apr 2008 16:19:22 +0200
Subject: [oXygen-user] Format and Indent Problem
In-Reply-To: <47FF52FD.4060509@oxygenxml.com>
References: <469DB173.1040206@asiatype.com> <46A0759E.9040502@oxygenxml.com>
	<21d9ade60707220447y25250067l4a42f7259983c028@mail.gmail.com>
	<47FB593A.3080004@oxygenxml.com>
	<21d9ade60804081205t1d46a5a5w985fa02e3e8f5191@mail.gmail.com>
	<47FF52FD.4060509@oxygenxml.com>
Message-ID: <21d9ade60804110719h21d220cby1807c74c2606e685@mail.gmail.com>

I'm sorry, if I'm not clear but I never spoke about XSLT

For it is an option of indenting a file which could be called "neutral
indenting", which would allow us to indent a one line xml file without
introducing nasty spaces

Regards,

Xmlizer

On Fri, Apr 11, 2008 at 2:01 PM, Sorin Ristache <sorin at > wrote:

> Hello,
>
> Do you mean debugging an XSLT transformation applied to an XML file
> formatted as in your example? I think an XSLT debugger is more useful for
> that and it does not depend on the text format of the XML file. For example
> when you click on a row in the Context view or in the XWatch view of the
> oXygen XSLT debugger the start tag of the corresponding XML element is
> highlighted in the XML editor panel. You need just to click in a view of the
> XSLT debugger to go directly to the corresponding XML element in the source
> editor.
>
>
> Regards,
> Sorin
>
>
> mozer wrote:
>
> > Let me give a simple example
> >  <root><a><b></b><c></c></a></root>
> >  into
> > <root
> >  ><a
> >  ><b
> >  ></b
> >  ><c
> >  ></c
> >  ></a
> >  ></root
> >  >
> > May it would make the will less readable than a full indent, but in some
> > case, it is just sufficient for debbugging and don't need further
> > parametrization
> >
>  _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20080411/95494377/attachment.html 

From bogus@does.not.exist.com  Fri Apr 11 10:09:34 2008
From: bogus@does.not.exist.com (George Cristian Bina)
Date: Fri, 11 Apr 2008 18:09:34 +0300
Subject: [oXygen-user] oXygen 9.2 beta
Message-ID: <47FF7F2E.7040808@oxygenxml.com>

Hi,

We are getting close to a new oXygen release. This will be a version 9 
maintenance release, oXygen 9.2.
We made available a beta build from the links below:

Windows
http://www.oxygenxml.com/update/9.2/Oxygen/Windows/VM/oxygen.exe
http://www.oxygenxml.com/update/9.2/Oxygen/Windows/NoVM/oxygen.exe

Linux
http://www.oxygenxml.com/update/9.2/Oxygen/Linux/VM/oxygen.sh

MacOS X
http://www.oxygenxml.com/update/9.2/Oxygen/MacOSX/oxygen.tar.gz

Eclipse 3.3 update site
http://www.oxygenxml.com/update/9.2/Oxygen/Eclipse/site.xml

What is new in 9.2... There are more than 450 issues that were recorded 
as fixed in 9.2 already and probably the number will grow near 500 when 
it will become generally available. I will try to enumerate a few from 
the most important additions below.

* oXygen Author
===============
There are people that are not developers or there are times when you are 
not interested in the development features of oXygen and you want just 
to do XML editing. The oXygen Author removes the development features 
offering a more simple interface for XML editing.
To start the oXygen Author you can use the author executable or the 
author batch script from your oXygen installation.
The oXygen Author is available also as a separate product, both as a 
standalone application and as an Eclipse plugin. The separate oXygen 
Author installation kits are below. The license key for oXygen works 
also with the oXygen Author:

Windows
http://www.oxygenxml.com/update/9.2/Author/Windows/VM/author.exe
http://www.oxygenxml.com/update/9.2/Author/Windows/NoVM/author.exe

Linux
http://www.oxygenxml.com/update/9.2/Author/Linux/VM/author.sh

MacOS X
http://www.oxygenxml.com/update/9.2/Author/MacOSX/author.tar.gz

All
http://www.oxygenxml.com/update/9.2/Author/All/author.tar.gz

Eclipse 3.3 update site
http://www.oxygenxml.com/update/9.2/Author/EclipseAuthor/site.xml

* Navigation support
====================
The visual editing (Author mode) supports now links. The links are 
specified in the associated CSS using a link property. oXygen will 
render them and will open the referred document when you click on a 
link. We updated the DITA, TEI and DocBook CSS stylesheets to add link 
support for the specific linking elements in each framework. The link 
support works also with DITA conrefs and XInclude.

* In place view of the included/referenced content
==================================================
The included content (with XInclude for instance) or the referred 
content is presented in place as a read only block that can be 
collapsed/expanded. This gives the view of the result document with the 
inclusions and references resolved.

* Inline tags - new visual rendering in Author
==============================================
In this rendering mode the block tags are hidden and the inline tags are 
presented. This is available from the Author toolbar and from the Author 
menu and gives a compact visual view while showing the inline elements' 
tags.

* DITA maps manager
===================
This allows viewing and editing DITA map files. It acts also similar 
with a project manager allowing to easily open different topics/concepts 
for editing.
You should get the DITA maps manager visible automatically if you open a 
.ditamap file in oXygen. It will appear as a tab in the same stack with 
the Project. The toolbar, the contextual menu and drag and drop actions 
will allow to easily edit the map content. Double click to open a 
referenced file for editing.

* Closely integration of the DITA Open Toolkit for transformations
==================================================================
This allows to easily configure and execute specific DITA 
transformations from the DITA Maps manager to different formats (XHTML, 
PDF, HTML, JavaHelp, Eclipse Help, DocBook, etc.). These are DITA 
specific using the DITA Open Toolkit and providing more options than the 
standard XSLT transformation scenarios, see the Filters and Advanced 
tabs when editing a scenario.

* DITA conref support
=====================
You can easily insert conrefs using the "Insert a DITA Content 
Reference" action from the DITA toolbar or from the contextual menu 
Insert->Insert Content Reference.

* Synchronize the end tag with the start tag changes
====================================================
If the start tag is changed oXygen will automatically change also the 
end tag, thus keeping the document well formed and saving you a few 
keystrokes.

* ISO Schematron improvements
=============================
Allowing foreign elements in ISO Schematron schemas is controllable from 
the oXygen Schematron options. These are useful for instance when you 
want to access an XSLT 2.0 function from a Schematron rule. Also it is 
possible to specify that Schematron should be executed with Saxon SA 
(schema aware) and thus be able to use schema aware checks inside the 
Schematron rules.

Internationalization improvements
=================================
The wrapping of CJK (Chinese Japanese Korean) text takes into account 
punctuation marks.
The Author and XML Source pages display on-the-spot the composed text 
(for instance when editing CJK text). The composed text is shown in the 
context of the document that it will eventually belong to, in a style 
that indicates that the text still needs to be converted or confirmed by 
the input method.

Latest Saxon 9
==============
oXygen 9.2 supports the latest version of Saxon 9.0.0.4.

Latest DocBook 5 schemas and stylesheets
========================================
The DocBook 5 final release schemas are included.
The stylesheets were updated to docbook-xsl-ns-1.73.2.

Latest XQDoc
============
XQDoc version 1.6 was integrated for generating XQuery documentation 
from within oXygen.


We have also 2 DITA video demonstrations showing the DITA Maps manager 
and the DITA editing:

http://www.oxygenxml.com/update/ditamapsmanager/ditaMapsManager.html
http://www.oxygenxml.com/update/ditaediting/ditaEditing.html

Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina - http://aboutxml.blogspot.com/
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


From bogus@does.not.exist.com  Fri Apr 11 10:37:20 2008
From: bogus@does.not.exist.com (Barton Wright)
Date: Fri, 11 Apr 2008 11:37:20 -0400
Subject: [oXygen-user] oXygen 9.2 beta
References: <47FF7F2E.7040808@oxygenxml.com>
Message-ID: <0E8C741725428C479EE6DB2780C89F8101803150@win2003-exc1.ad.streambase.com>

George,

My Oxygen 9.1 license inlcudes Syncro SVN Client 2.6. But SVN Client 3.1 is available on your web site. I was wondering if Oxygen 9.2 would include the latest Syncro SVN Client.

Thanks!

-----Original Message-----
From: oxygen-user-bounces at  [mailto:oxygen-user-bounces at ] On Behalf Of George Cristian Bina
Sent: Friday, April 11, 2008 11:10 AM
To: oXygenXML user list
Subject: [oXygen-user] oXygen 9.2 beta

Hi,

We are getting close to a new oXygen release. This will be a version 9 
maintenance release, oXygen 9.2.
We made available a beta build from the links below:

Windows
http://www.oxygenxml.com/update/9.2/Oxygen/Windows/VM/oxygen.exe
http://www.oxygenxml.com/update/9.2/Oxygen/Windows/NoVM/oxygen.exe

Linux
http://www.oxygenxml.com/update/9.2/Oxygen/Linux/VM/oxygen.sh

MacOS X
http://www.oxygenxml.com/update/9.2/Oxygen/MacOSX/oxygen.tar.gz

Eclipse 3.3 update site
http://www.oxygenxml.com/update/9.2/Oxygen/Eclipse/site.xml

What is new in 9.2... There are more than 450 issues that were recorded 
as fixed in 9.2 already and probably the number will grow near 500 when 
it will become generally available. I will try to enumerate a few from 
the most important additions below.

* oXygen Author
===============
There are people that are not developers or there are times when you are 
not interested in the development features of oXygen and you want just 
to do XML editing. The oXygen Author removes the development features 
offering a more simple interface for XML editing.
To start the oXygen Author you can use the author executable or the 
author batch script from your oXygen installation.
The oXygen Author is available also as a separate product, both as a 
standalone application and as an Eclipse plugin. The separate oXygen 
Author installation kits are below. The license key for oXygen works 
also with the oXygen Author:

Windows
http://www.oxygenxml.com/update/9.2/Author/Windows/VM/author.exe
http://www.oxygenxml.com/update/9.2/Author/Windows/NoVM/author.exe

Linux
http://www.oxygenxml.com/update/9.2/Author/Linux/VM/author.sh

MacOS X
http://www.oxygenxml.com/update/9.2/Author/MacOSX/author.tar.gz

All
http://www.oxygenxml.com/update/9.2/Author/All/author.tar.gz

Eclipse 3.3 update site
http://www.oxygenxml.com/update/9.2/Author/EclipseAuthor/site.xml

* Navigation support
====================
The visual editing (Author mode) supports now links. The links are 
specified in the associated CSS using a link property. oXygen will 
render them and will open the referred document when you click on a 
link. We updated the DITA, TEI and DocBook CSS stylesheets to add link 
support for the specific linking elements in each framework. The link 
support works also with DITA conrefs and XInclude.

* In place view of the included/referenced content
==================================================
The included content (with XInclude for instance) or the referred 
content is presented in place as a read only block that can be 
collapsed/expanded. This gives the view of the result document with the 
inclusions and references resolved.

* Inline tags - new visual rendering in Author
==============================================
In this rendering mode the block tags are hidden and the inline tags are 
presented. This is available from the Author toolbar and from the Author 
menu and gives a compact visual view while showing the inline elements' 
tags.

* DITA maps manager
===================
This allows viewing and editing DITA map files. It acts also similar 
with a project manager allowing to easily open different topics/concepts 
for editing.
You should get the DITA maps manager visible automatically if you open a 
.ditamap file in oXygen. It will appear as a tab in the same stack with 
the Project. The toolbar, the contextual menu and drag and drop actions 
will allow to easily edit the map content. Double click to open a 
referenced file for editing.

* Closely integration of the DITA Open Toolkit for transformations
==================================================================
This allows to easily configure and execute specific DITA 
transformations from the DITA Maps manager to different formats (XHTML, 
PDF, HTML, JavaHelp, Eclipse Help, DocBook, etc.). These are DITA 
specific using the DITA Open Toolkit and providing more options than the 
standard XSLT transformation scenarios, see the Filters and Advanced 
tabs when editing a scenario.

* DITA conref support
=====================
You can easily insert conrefs using the "Insert a DITA Content 
Reference" action from the DITA toolbar or from the contextual menu 
Insert->Insert Content Reference.

* Synchronize the end tag with the start tag changes
====================================================
If the start tag is changed oXygen will automatically change also the 
end tag, thus keeping the document well formed and saving you a few 
keystrokes.

* ISO Schematron improvements
=============================
Allowing foreign elements in ISO Schematron schemas is controllable from 
the oXygen Schematron options. These are useful for instance when you 
want to access an XSLT 2.0 function from a Schematron rule. Also it is 
possible to specify that Schematron should be executed with Saxon SA 
(schema aware) and thus be able to use schema aware checks inside the 
Schematron rules.

Internationalization improvements
=================================
The wrapping of CJK (Chinese Japanese Korean) text takes into account 
punctuation marks.
The Author and XML Source pages display on-the-spot the composed text 
(for instance when editing CJK text). The composed text is shown in the 
context of the document that it will eventually belong to, in a style 
that indicates that the text still needs to be converted or confirmed by 
the input method.

Latest Saxon 9
==============
oXygen 9.2 supports the latest version of Saxon 9.0.0.4.

Latest DocBook 5 schemas and stylesheets
========================================
The DocBook 5 final release schemas are included.
The stylesheets were updated to docbook-xsl-ns-1.73.2.

Latest XQDoc
============
XQDoc version 1.6 was integrated for generating XQuery documentation 
from within oXygen.


We have also 2 DITA video demonstrations showing the DITA Maps manager 
and the DITA editing:

http://www.oxygenxml.com/update/ditamapsmanager/ditaMapsManager.html
http://www.oxygenxml.com/update/ditaediting/ditaEditing.html

Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina - http://aboutxml.blogspot.com/
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
_______________________________________________
oXygen-user mailing list
oXygen-user at 
http://www.oxygenxml.com/mailman/listinfo/oxygen-user


From bogus@does.not.exist.com  Fri Apr 11 11:21:50 2008
From: bogus@does.not.exist.com (George Cristian Bina)
Date: Fri, 11 Apr 2008 19:21:50 +0300
Subject: [oXygen-user] oXygen 9.2 beta
In-Reply-To: <0E8C741725428C479EE6DB2780C89F8101803150@win2003-exc1.ad.streambase.com>
References: <47FF7F2E.7040808@oxygenxml.com>
	<0E8C741725428C479EE6DB2780C89F8101803150@win2003-exc1.ad.streambase.com>
Message-ID: <47FF901E.1010903@oxygenxml.com>

Hi Barton,

oXygen 9.2 includes the latest developments on the Syncro SVN Client. 
The Syncro SVN Client is part of oXygen and it is just a build script 
that packs it as a separate application.

Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina - http://aboutxml.blogspot.com/
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


Barton Wright wrote:
> George,
> 
> My Oxygen 9.1 license inlcudes Syncro SVN Client 2.6. But SVN Client 3.1 is available on your web site. I was wondering if Oxygen 9.2 would include the latest Syncro SVN Client.
> 
> Thanks!
> 
> -----Original Message-----
> From: oxygen-user-bounces at  [mailto:oxygen-user-bounces at ] On Behalf Of George Cristian Bina
> Sent: Friday, April 11, 2008 11:10 AM
> To: oXygenXML user list
> Subject: [oXygen-user] oXygen 9.2 beta
> 
> Hi,
> 
> We are getting close to a new oXygen release. This will be a version 9 
> maintenance release, oXygen 9.2.
> We made available a beta build from the links below:
> 
> Windows
> http://www.oxygenxml.com/update/9.2/Oxygen/Windows/VM/oxygen.exe
> http://www.oxygenxml.com/update/9.2/Oxygen/Windows/NoVM/oxygen.exe
> 
> Linux
> http://www.oxygenxml.com/update/9.2/Oxygen/Linux/VM/oxygen.sh
> 
> MacOS X
> http://www.oxygenxml.com/update/9.2/Oxygen/MacOSX/oxygen.tar.gz
> 
> Eclipse 3.3 update site
> http://www.oxygenxml.com/update/9.2/Oxygen/Eclipse/site.xml
> 
> What is new in 9.2... There are more than 450 issues that were recorded 
> as fixed in 9.2 already and probably the number will grow near 500 when 
> it will become generally available. I will try to enumerate a few from 
> the most important additions below.
> 
> * oXygen Author
> ===============
> There are people that are not developers or there are times when you are 
> not interested in the development features of oXygen and you want just 
> to do XML editing. The oXygen Author removes the development features 
> offering a more simple interface for XML editing.
> To start the oXygen Author you can use the author executable or the 
> author batch script from your oXygen installation.
> The oXygen Author is available also as a separate product, both as a 
> standalone application and as an Eclipse plugin. The separate oXygen 
> Author installation kits are below. The license key for oXygen works 
> also with the oXygen Author:
> 
> Windows
> http://www.oxygenxml.com/update/9.2/Author/Windows/VM/author.exe
> http://www.oxygenxml.com/update/9.2/Author/Windows/NoVM/author.exe
> 
> Linux
> http://www.oxygenxml.com/update/9.2/Author/Linux/VM/author.sh
> 
> MacOS X
> http://www.oxygenxml.com/update/9.2/Author/MacOSX/author.tar.gz
> 
> All
> http://www.oxygenxml.com/update/9.2/Author/All/author.tar.gz
> 
> Eclipse 3.3 update site
> http://www.oxygenxml.com/update/9.2/Author/EclipseAuthor/site.xml
> 
> * Navigation support
> ====================
> The visual editing (Author mode) supports now links. The links are 
> specified in the associated CSS using a link property. oXygen will 
> render them and will open the referred document when you click on a 
> link. We updated the DITA, TEI and DocBook CSS stylesheets to add link 
> support for the specific linking elements in each framework. The link 
> support works also with DITA conrefs and XInclude.
> 
> * In place view of the included/referenced content
> ==================================================
> The included content (with XInclude for instance) or the referred 
> content is presented in place as a read only block that can be 
> collapsed/expanded. This gives the view of the result document with the 
> inclusions and references resolved.
> 
> * Inline tags - new visual rendering in Author
> ==============================================
> In this rendering mode the block tags are hidden and the inline tags are 
> presented. This is available from the Author toolbar and from the Author 
> menu and gives a compact visual view while showing the inline elements' 
> tags.
> 
> * DITA maps manager
> ===================
> This allows viewing and editing DITA map files. It acts also similar 
> with a project manager allowing to easily open different topics/concepts 
> for editing.
> You should get the DITA maps manager visible automatically if you open a 
> .ditamap file in oXygen. It will appear as a tab in the same stack with 
> the Project. The toolbar, the contextual menu and drag and drop actions 
> will allow to easily edit the map content. Double click to open a 
> referenced file for editing.
> 
> * Closely integration of the DITA Open Toolkit for transformations
> ==================================================================
> This allows to easily configure and execute specific DITA 
> transformations from the DITA Maps manager to different formats (XHTML, 
> PDF, HTML, JavaHelp, Eclipse Help, DocBook, etc.). These are DITA 
> specific using the DITA Open Toolkit and providing more options than the 
> standard XSLT transformation scenarios, see the Filters and Advanced 
> tabs when editing a scenario.
> 
> * DITA conref support
> =====================
> You can easily insert conrefs using the "Insert a DITA Content 
> Reference" action from the DITA toolbar or from the contextual menu 
> Insert->Insert Content Reference.
> 
> * Synchronize the end tag with the start tag changes
> ====================================================
> If the start tag is changed oXygen will automatically change also the 
> end tag, thus keeping the document well formed and saving you a few 
> keystrokes.
> 
> * ISO Schematron improvements
> =============================
> Allowing foreign elements in ISO Schematron schemas is controllable from 
> the oXygen Schematron options. These are useful for instance when you 
> want to access an XSLT 2.0 function from a Schematron rule. Also it is 
> possible to specify that Schematron should be executed with Saxon SA 
> (schema aware) and thus be able to use schema aware checks inside the 
> Schematron rules.
> 
> Internationalization improvements
> =================================
> The wrapping of CJK (Chinese Japanese Korean) text takes into account 
> punctuation marks.
> The Author and XML Source pages display on-the-spot the composed text 
> (for instance when editing CJK text). The composed text is shown in the 
> context of the document that it will eventually belong to, in a style 
> that indicates that the text still needs to be converted or confirmed by 
> the input method.
> 
> Latest Saxon 9
> ==============
> oXygen 9.2 supports the latest version of Saxon 9.0.0.4.
> 
> Latest DocBook 5 schemas and stylesheets
> ========================================
> The DocBook 5 final release schemas are included.
> The stylesheets were updated to docbook-xsl-ns-1.73.2.
> 
> Latest XQDoc
> ============
> XQDoc version 1.6 was integrated for generating XQuery documentation 
> from within oXygen.
> 
> 
> We have also 2 DITA video demonstrations showing the DITA Maps manager 
> and the DITA editing:
> 
> http://www.oxygenxml.com/update/ditamapsmanager/ditaMapsManager.html
> http://www.oxygenxml.com/update/ditaediting/ditaEditing.html
> 
> Best Regards,
> George
> ---------------------------------------------------------------------
> George Cristian Bina - http://aboutxml.blogspot.com/
> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user


From bogus@does.not.exist.com  Fri Apr 11 19:36:01 2008
From: bogus@does.not.exist.com (Steven Anderson)
Date: Fri, 11 Apr 2008 17:36:01 -0700
Subject: [oXygen-user] oXygen 9.2 Beta - ditamaps
In-Reply-To: <20080411161034.6A2EF11C239@editor2.oxygenxml.com>
References: <20080411161034.6A2EF11C239@editor2.oxygenxml.com>
Message-ID: <A5463BCCC135FF42B419DE8516122B222E9D73BE6F@EXSFM-MB02.internal.salesforce.com>

Love, love, love the new functionality in oXygen 9.2 related to DITA.  On first pass, I noticed three issues:

1. I couldn't figure out how to specify which JDK to use for DITA transforms to PDF.  This matters, because RenderX is much faster with JDK 1.6 than 1.5, but I need 1.5 for other tools.

2. The DITA transform doesn't appear to be sensitive to the catalog I've defined in my oXygen preferences, thus it uses the oXygen defaults for everything.

3. In the dita maps manager view, topicgroups, and their descendants, are not displayed.

Is this the right forum to post these kinds of issues/questions?

        Steve


From bogus@does.not.exist.com  Mon Apr 14 02:46:27 2008
From: bogus@does.not.exist.com (Radu Coravu)
Date: Mon, 14 Apr 2008 10:46:27 +0300
Subject: [oXygen-user] oXygen 9.2 Beta - ditamaps
In-Reply-To: <A5463BCCC135FF42B419DE8516122B222E9D73BE6F@EXSFM-MB02.internal.salesforce.com>
References: <20080411161034.6A2EF11C239@editor2.oxygenxml.com>
	<A5463BCCC135FF42B419DE8516122B222E9D73BE6F@EXSFM-MB02.internal.salesforce.com>
Message-ID: <48030BD3.5040106@sync.ro>

Dear Steven,

Thank you for the kind words and valuable suggestions.
See some answers below:

Steven Anderson wrote:
> 1. I couldn't figure out how to specify which JDK to use for DITA transforms to PDF.  This matters, because RenderX is much faster with JDK 1.6 than 1.5, but I need 1.5 for other tools.
>   
The DITA-OT ANT transformation is started using the same Java Virtual 
Machine as Oxygen does so starting Oxygen with a 1.6 Java Virtual 
Machine will also make the transformation use it.
See more about specifying the JVM for Oxygen here: 
http://www.oxygenxml.com/doc/ug-standalone/installation-instructions.html
We added an improvement request on our issues tracker to let the users 
choose a custom Java Home for running the DITA ANT transformation when 
editing the scenario in the "Advanced" tab.
> 2. The DITA transform doesn't appear to be sensitive to the catalog I've defined in my oXygen preferences, thus it uses the oXygen defaults for everything.
>   
For now the catalogs set in Oxygen are not used in any way during the 
DITA-OT ANT transformation.
The catalog file used for DITA-OT ANT transformations is located in 
"{OxygenInstallDir}/frameworks/dita/DITA-OT/catalog-dita.xml" and is 
referred directly from the "dost.jar" library.
You have to edit the catalog file and add your entries there.

> 3. In the dita maps manager view, topicgroups, and their descendants, are not displayed.
>   
This is indeed a mistake on our part as topic groups can have child 
topic refs which enter in the TOC.
We wanted to present the DITA Map tree in a simplified manner so we 
filtered part of the nodes.
If you or somebody else has suggestions for additional nodes which 
should appear in the tree please say so...

Regards,
Radu

-- 
Radu Coravu 
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com



From bogus@does.not.exist.com  Sat Apr 19 08:50:27 2008
From: bogus@does.not.exist.com (Peter Rushforth)
Date: Sat, 19 Apr 2008 09:50:27 -0400
Subject: [oXygen-user] using custom parser in saxon 9 transformation scenario
Message-ID: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>

Hi,

I'm new to oxygen, but I have written a custom uri resolver which
references a custom parser, for saxon 9.

The parser reads a binary format file, and returns xml events to
saxon.  It seems to work well
interactively; now I would like to use it in the oxygen xslt debugging
environment.

I have configured a transformation scenario with the appropriate classes on the
class path including both the resolver and the parser and classes upon
which they depend.

However when I invoke the transformation, I get "Content is not
allowed in prolog", which looks
to me like the parser isn't getting first crack at the binary data.

Does anyone have a suggestion to help with this?

Cheers,
Peter


From bogus@does.not.exist.com  Sat Apr 19 08:50:27 2008
From: bogus@does.not.exist.com (Peter Rushforth)
Date: Sat, 19 Apr 2008 09:50:27 -0400
Subject: [oXygen-user] using custom parser in saxon 9 transformation scenario
Message-ID: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>

Hi,

I'm new to oxygen, but I have written a custom uri resolver which
references a custom parser, for saxon 9.

The parser reads a binary format file, and returns xml events to
saxon.  It seems to work well
interactively; now I would like to use it in the oxygen xslt debugging
environment.

I have configured a transformation scenario with the appropriate classes on the
class path including both the resolver and the parser and classes upon
which they depend.

However when I invoke the transformation, I get "Content is not
allowed in prolog", which looks
to me like the parser isn't getting first crack at the binary data.

Does anyone have a suggestion to help with this?

Cheers,
Peter


From bogus@does.not.exist.com  Mon Apr 21 10:34:42 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Mon, 21 Apr 2008 18:34:42 +0300
Subject: [oXygen-user] using custom parser in saxon 9 transformation
	scenario
In-Reply-To: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>
References: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>
Message-ID: <480CB412.2040607@oxygenxml.com>

Hello,

First you should make sure that your custom URI resolver is 
configured correctly in the Editor perspective before trying 
it in the Debugger perspective. The custom URI resolver and 
all the Java classes referenced from the custom URI resolver 
including the custom XML parser must be set as XSLT 
extensions for your transformation. You set an XSLT 
extension in the dialog opened by the Extensions button of 
the scenario edit dialog:

http://www.oxygenxml.com/doc/ug-standalone/xslt-xquery-extensions.html

You have to set the full name of the Saxon 9 URI resolver 
class in the Saxon 9 Advanced settings available from menu 
Options -> Preferences -> XML -> XSLT/FO/XQuery -> XSLT -> 
Saxon -> Saxon 9 -> Advanced -- URI Resolver class name. If 
you type "uri" in the search field of the Preferences dialog 
you can locate this setting quickly.

Does the URI resolver work in a transformation applied with 
a transformation scenario in the Editor perspective?


Regards,
Sorin


Peter Rushforth wrote:
> Hi,
> 
> I'm new to oxygen, but I have written a custom uri resolver which
> references a custom parser, for saxon 9.
> 
> The parser reads a binary format file, and returns xml events to
> saxon.  It seems to work well
> interactively; now I would like to use it in the oxygen xslt debugging
> environment.
> 
> I have configured a transformation scenario with the appropriate classes on the
> class path including both the resolver and the parser and classes upon
> which they depend.
> 
> However when I invoke the transformation, I get "Content is not
> allowed in prolog", which looks
> to me like the parser isn't getting first crack at the binary data.
> 
> Does anyone have a suggestion to help with this?
> 
> Cheers,
> Peter


From bogus@does.not.exist.com  Mon Apr 21 18:38:19 2008
From: bogus@does.not.exist.com (Eric Jahn)
Date: Mon, 21 Apr 2008 16:38:19 -0700
Subject: [oXygen-user] importation of a remote schema problem
Message-ID: <200804212339.m3LNd2Iw026886@rs49.luxsci.com>

I have a schema here: 
http://www.hmis.info/schema/2_8/HUD_HMIS_2_8.xsd
which in turn imports this schema: 
http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd

If I copy the latter schemas locally and give a SchemaLocation to the
local copies, it validates fine.  However, if I remove the local
SchemaLocation statement, I get this validation error from Oxygen 9.1:
 
"[Xerces] src-resolve: Cannot resolve the name 'airs:tSiteService' to
a(n) 'type definition' component. @see:
http://www.w3.org/TR/xmlschema-1/#src-resolve
reposHUD/tags/HUD_HMIS_XML_2.8 HUD_HMIS_2_8.xsd line 828 1208818729409
195997"

Why can't Xerces/Oxygen validate against the remote copy of the imported
schema?  I tried declaring it in the XML Catalog in Prferences, but it
didn't help.  

Any insights are very appreciated.  Thank you! 

  




From bogus@does.not.exist.com  Mon Apr 21 18:47:32 2008
From: bogus@does.not.exist.com (Eric Jahn)
Date: Mon, 21 Apr 2008 16:47:32 -0700
Subject: [oXygen-user] importation of a remote schema problem
In-Reply-To: <200804212339.m3LNd2Iw026886@rs49.luxsci.com>
References: <200804212339.m3LNd2Iw026886@rs49.luxsci.com>
Message-ID: <200804212348.m3LNm2Ks010196@rs49.luxsci.com>

Oh, okay, I figured it out.  I had to add the url to the validation
scenario after clicking the validation configuration button then edit.
Then revalidated and the error went away.  -Eric 



From bogus@does.not.exist.com  Mon Apr 21 21:25:26 2008
From: bogus@does.not.exist.com ()
Date: Mon, 21 Apr 2008 22:25:26 -0400
Subject: [oXygen-user] oXygen and EXSLT
Message-ID: <20080421222526.OKU0D.169224.imail@eastrmwml08.mgt.cox.net>

Hi,

I was wondering if it's possible to get oXygen 9.1 working with EXSLT?

I'm particularly interested in regExp, but when I try that, I get a debugger error "Unknown Saxon extension element: script".

If someone has been able to get this working, can you please share how you accomplished this?

Thanks,
Jim

P.S. I can't use XSLT 2.0 because it won't be available in another environment which is the target.




From bogus@does.not.exist.com  Tue Apr 22 04:34:47 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Tue, 22 Apr 2008 12:34:47 +0300
Subject: [oXygen-user] oXygen and EXSLT
In-Reply-To: <20080421222526.OKU0D.169224.imail@eastrmwml08.mgt.cox.net>
References: <20080421222526.OKU0D.169224.imail@eastrmwml08.mgt.cox.net>
Message-ID: <480DB137.9020804@oxygenxml.com>

Hello,

If you can't use XSLT 2.0 which has built-in support for 
regular expressions you have to import the EXSLT regexp 
extension in an XSLT 1.0 stylesheet but you have to use 
MSXML or Xalan in oXygen.

For MSXML the EXSLT stylesheets need a modification: import 
the MSXML stylesheet directly instead of the wrapper 
stylesheet that includes the MSXML stylesheet with a 
func:script element. For example for the EXSLT regexp 
replace stylesheet you have to import in your stylesheet 
directly regexp.replace.msxsl.xsl:

     <xsl:import href="regexp.replace.msxsl.xsl" />

instead of

     <xsl:import href="regexp.replace.xsl" />

which contains an element

    <func:script language="exslt:msxsl" 
implements-prefix="regexp" src="regexp.replace.msxsl.xsl"/>

as in the EXSLT example on the exslt.org website.

For Xalan you have to modify the EXSLT stylesheet to conform 
with the Xalan extension rules specified on the Xalan 
Extensions page:

http://xml.apache.org/xalan-j/extensions.html#basic-pattern

The JavaScript code from the EXSLT stylesheets (for example 
regexp.replace.js) must be adapted to Xalan as in the 
example which you can find on the same Xalan page:

http://xml.apache.org/xalan-j/extensions.html#ex-basic

You have to add bsf.jar (the Bean Scripting Framework) and 
js.jar (the Apache Rhino project) as XSLT extensions to the 
oXygen transformation scenario that processes your EXSLT 
enabled stylesheet with Xalan. These jar files are needed 
for adding a JavaScript extension to Xalan.

The oXygen User Manual describes how to set an XSLT 
extension in an oXygen transformation scenario:

http://www.oxygenxml.com/doc/ug-standalone/defining-new-transformation-scenario.html

http://www.oxygenxml.com/doc/ug-standalone/xslt-xquery-extensions.html


Regards,
Sorin


ohaya at  wrote:
> Hi,
> 
> I was wondering if it's possible to get oXygen 9.1 working with EXSLT?
> 
> I'm particularly interested in regExp, but when I try that, I get a debugger error "Unknown Saxon extension element: script".
> 
> If someone has been able to get this working, can you please share how you accomplished this?
> 
> Thanks,
> Jim
> 
> P.S. I can't use XSLT 2.0 because it won't be available in another environment which is the target.



From bogus@does.not.exist.com  Tue Apr 22 18:50:51 2008
From: bogus@does.not.exist.com (Eric Jahn)
Date: Tue, 22 Apr 2008 16:50:51 -0700
Subject: [oXygen-user] Validating XML instance with a Schema which imports
	another Schema
Message-ID: <200804222351.m3MNp2ie017910@rs49.luxsci.com>

I believe this is a bug with Oxygen 9.1, but please correct me if I'm
erring in my thoughts or configuration.

Here is the scenario:

I have a schema which imports a second remote schema.  I can validate
this schema with its remote schema by configuring a custom validation
scenario which declares the remote schema urls, as opposed to using
local copies with a SchemaLocation declaration.  If I declare local
SchemaLocations, this all works and there are no validation errors, so I
think I have isolated the problem to an Oxygen 9.1 bug.

Now, I wish to perform the next logical step and validate an XML
instance of this remote schema.  The XML is located here: 
http://www.hmis.info/schema/2_8/Example_HUD_HMIS_Instance.xml

Again, I set up an appropriate custom validation scenario declaring both
remote schema (the referred schema) at: 
http://www.hmis.info/schema/2_8/HUD_HMIS_2_8.xsd

and the one it imports at: 
http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd

When I run the Oxygen default validation, I get the following error:

"Message:src-resolve: Cannot resolve the name 'airs:tSiteService' to
a(n) 'type definition' component."

It's complaining about not finding the schema imported by the referred
schema.  It does find the referred schema aok.  This should not happen,
as I don't get this error when validating the referred schema, for which
Oxygen's validator locates the imported schema when the custom
validation scenario is declared.

Thanks for either confirming a bug or determining my error.  -Eric





From bogus@does.not.exist.com  Tue Apr 22 20:23:34 2008
From: bogus@does.not.exist.com (Peter Rushforth)
Date: Tue, 22 Apr 2008 21:23:34 -0400
Subject: [oXygen-user] using custom parser in saxon 9 transformation
	scenario
In-Reply-To: <480CB412.2040607@oxygenxml.com>
References: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>
	<480CB412.2040607@oxygenxml.com>
Message-ID: <1fd798f40804221823h731bce73u5a928436a408b6d@mail.gmail.com>

Hi,

I believe I've set the extension classes correctly.  An odd thing is that when I
try to run the same thing from the command line, when I *don't* use the -u
option I get the same message regarding content not allowed in prolog.

Where I look at the saxon command line documentation, I see that the -u
option is used to tell saxon that the files are "urls", unless they begin with
http: or file:, in which case they are taken as urls as is.

But I don't see anywhere in oxygen I can set the -u parameter.

Thanks for your help.

Cheers,
Peter

On Mon, Apr 21, 2008 at 11:34 AM, Sorin Ristache <sorin at > wrote:
> Hello,
>
> First you should make sure that your custom URI resolver is configured
> correctly in the Editor perspective before trying it in the Debugger
> perspective. The custom URI resolver and all the Java classes referenced
> from the custom URI resolver including the custom XML parser must be set as
> XSLT extensions for your transformation. You set an XSLT extension in the
> dialog opened by the Extensions button of the scenario edit dialog:
>
> http://www.oxygenxml.com/doc/ug-standalone/xslt-xquery-extensions.html
>
> You have to set the full name of the Saxon 9 URI resolver class in the Saxon
> 9 Advanced settings available from menu Options -> Preferences -> XML ->
> XSLT/FO/XQuery -> XSLT -> Saxon -> Saxon 9 -> Advanced -- URI Resolver class
> name. If you type "uri" in the search field of the Preferences dialog you
> can locate this setting quickly.
>
> Does the URI resolver work in a transformation applied with a transformation
> scenario in the Editor perspective?
>
>
> Regards,
> Sorin
>
>
>
>
> Peter Rushforth wrote:
> > Hi,
> >
> > I'm new to oxygen, but I have written a custom uri resolver which
> > references a custom parser, for saxon 9.
> >
> > The parser reads a binary format file, and returns xml events to
> > saxon.  It seems to work well
> > interactively; now I would like to use it in the oxygen xslt debugging
> > environment.
> >
> > I have configured a transformation scenario with the appropriate classes
> on the
> > class path including both the resolver and the parser and classes upon
> > which they depend.
> >
> > However when I invoke the transformation, I get "Content is not
> > allowed in prolog", which looks
> > to me like the parser isn't getting first crack at the binary data.
> >
> > Does anyone have a suggestion to help with this?
> >
> > Cheers,
> > Peter
> >
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>


From bogus@does.not.exist.com  Tue Apr 22 20:24:53 2008
From: bogus@does.not.exist.com (Peter Rushforth)
Date: Tue, 22 Apr 2008 21:24:53 -0400
Subject: [oXygen-user] using custom parser in saxon 9 transformation
	scenario
In-Reply-To: <480CB412.2040607@oxygenxml.com>
References: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>
	<480CB412.2040607@oxygenxml.com>
Message-ID: <1fd798f40804221824m3e901917o1a15c48bc0d4bb8a@mail.gmail.com>

Oh and no a regular transformation scenario doesn't work.  I was
trying to set that
up with a simple identity transformation on a simple binary file
before getting fancy.

Thx

On Mon, Apr 21, 2008 at 11:34 AM, Sorin Ristache <sorin at > wrote:
> Hello,
>
> First you should make sure that your custom URI resolver is configured
> correctly in the Editor perspective before trying it in the Debugger
> perspective. The custom URI resolver and all the Java classes referenced
> from the custom URI resolver including the custom XML parser must be set as
> XSLT extensions for your transformation. You set an XSLT extension in the
> dialog opened by the Extensions button of the scenario edit dialog:
>
> http://www.oxygenxml.com/doc/ug-standalone/xslt-xquery-extensions.html
>
> You have to set the full name of the Saxon 9 URI resolver class in the Saxon
> 9 Advanced settings available from menu Options -> Preferences -> XML ->
> XSLT/FO/XQuery -> XSLT -> Saxon -> Saxon 9 -> Advanced -- URI Resolver class
> name. If you type "uri" in the search field of the Preferences dialog you
> can locate this setting quickly.
>
> Does the URI resolver work in a transformation applied with a transformation
> scenario in the Editor perspective?
>
>
> Regards,
> Sorin
>
>
>
>
> Peter Rushforth wrote:
> > Hi,
> >
> > I'm new to oxygen, but I have written a custom uri resolver which
> > references a custom parser, for saxon 9.
> >
> > The parser reads a binary format file, and returns xml events to
> > saxon.  It seems to work well
> > interactively; now I would like to use it in the oxygen xslt debugging
> > environment.
> >
> > I have configured a transformation scenario with the appropriate classes
> on the
> > class path including both the resolver and the parser and classes upon
> > which they depend.
> >
> > However when I invoke the transformation, I get "Content is not
> > allowed in prolog", which looks
> > to me like the parser isn't getting first crack at the binary data.
> >
> > Does anyone have a suggestion to help with this?
> >
> > Cheers,
> > Peter
> >
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>


From bogus@does.not.exist.com  Wed Apr 23 05:02:16 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Wed, 23 Apr 2008 13:02:16 +0300
Subject: [oXygen-user] Validating XML instance with a Schema which imports
	another Schema
In-Reply-To: <200804222351.m3MNp2ie017910@rs49.luxsci.com>
References: <200804222351.m3MNp2ie017910@rs49.luxsci.com>
Message-ID: <480F0928.8050403@oxygenxml.com>

Hello,

The error is in the schema HUD_HMIS_2_8.xsd located at

http://www.hmis.info/schema/2_8/HUD_HMIS_2_8.xsd

This schema references the type airs:tSiteService, that is 
the type tSiteService from the namespace 
"http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd". 
The error is that the target namespace of the imported schema

http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd

is "http://cse.unl.edu/~bkutsch/3_0_draft_d5.xsd" which does 
not match the namespace used in the import element in 
HUD_HMIS_2_8.xsd (line 10). That means the type tSiteService 
defined in AIRS_3_0_draft5_mod.xsd in the namespace 
"http://cse.unl.edu/~bkutsch/3_0_draft_d5.xsd" cannot be 
matched with the type reference used on line 828 of 
HUD_HMIS_2_8.xsd which needs a type tSiteService from the 
namespace 
"http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd".

You do not need a validation scenario for a simple 
validation of an XML document against an XML Schema. It does 
not matter if the schema is local or remote. Oxygen will 
load it from the specified location. You should use a 
validation scenario in one of the two situations in which 
the User Manual recommends it but you are not in these 
situations:

http://www.oxygenxml.com/doc/ug-standalone/validation-scenario.html


Regards,
Sorin


Eric Jahn wrote:
> I believe this is a bug with Oxygen 9.1, but please correct me if I'm
> erring in my thoughts or configuration.
> 
> Here is the scenario:
> 
> I have a schema which imports a second remote schema.  I can validate
> this schema with its remote schema by configuring a custom validation
> scenario which declares the remote schema urls, as opposed to using
> local copies with a SchemaLocation declaration.  If I declare local
> SchemaLocations, this all works and there are no validation errors, so I
> think I have isolated the problem to an Oxygen 9.1 bug.
> 
> Now, I wish to perform the next logical step and validate an XML
> instance of this remote schema.  The XML is located here: 
> http://www.hmis.info/schema/2_8/Example_HUD_HMIS_Instance.xml
> 
> Again, I set up an appropriate custom validation scenario declaring both
> remote schema (the referred schema) at: 
> http://www.hmis.info/schema/2_8/HUD_HMIS_2_8.xsd
> 
> and the one it imports at: 
> http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd
> 
> When I run the Oxygen default validation, I get the following error:
> 
> "Message:src-resolve: Cannot resolve the name 'airs:tSiteService' to
> a(n) 'type definition' component."
> 
> It's complaining about not finding the schema imported by the referred
> schema.  It does find the referred schema aok.  This should not happen,
> as I don't get this error when validating the referred schema, for which
> Oxygen's validator locates the imported schema when the custom
> validation scenario is declared.
> 
> Thanks for either confirming a bug or determining my error.  -Eric


From bogus@does.not.exist.com  Wed Apr 23 09:45:21 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Wed, 23 Apr 2008 17:45:21 +0300
Subject: [oXygen-user] using custom parser in saxon 9
	transformation	scenario
In-Reply-To: <1fd798f40804221823h731bce73u5a928436a408b6d@mail.gmail.com>
References: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>	<480CB412.2040607@oxygenxml.com>
	<1fd798f40804221823h731bce73u5a928436a408b6d@mail.gmail.com>
Message-ID: <480F4B81.70200@oxygenxml.com>

Hello,

Now I think I understand. You want to apply an XSLT 
stylesheet to a stream of XML events generated by a custom 
parser from a binary file. You call the custom parser from a 
custom URI resolver that resolves the URL of the input XML 
file. You set the -u parameter for passing the URL of the 
input XML file through the custom URI resolver.

This cannot be done in the current version of Oxygen because 
Oxygen passes the URL of the input XML file only through a 
built-in resolver that tries to resolve the URL of the input 
XML file with the XML catalogs set in the user preferences. 
The Saxon custom URI resolver is used by Saxon internally 
only for URIs from the XSLT stylesheet because the stream of 
XML events from the input XML file is provided by Oxygen. A 
future version of Oxygen will pass the URL of the input file 
also through the Saxon custom URI resolver as if the -u 
parameter is always set when Saxon is used in Oxygen.

There is a very simple workaround: load the input file 
through your custom URI resolver directly from the XSLT 
stylesheet with the document() function, something like:

     <xsl:template match="/">
         <xsl:apply-templates 
select="document('URI-of-binary-file-resolved-by-custom-UR-resolver')"/>
     </xsl:template>

Of course you have to set the class name of your custom URI 
resolver in Options -> Preferences -- XML -- XSLT/FO/XQuery 
-- XSLT -- Saxon -- Saxon 9 -- Advanced -- URI Resolver 
class name.


Regards,
Sorin


Peter Rushforth wrote:
> I believe I've set the extension classes correctly.  An odd thing is that when I
> try to run the same thing from the command line, when I *don't* use the -u
> option I get the same message regarding content not allowed in prolog.
> 
> Where I look at the saxon command line documentation, I see that the -u
> option is used to tell saxon that the files are "urls", unless they begin with
> http: or file:, in which case they are taken as urls as is.
> 
> But I don't see anywhere in oxygen I can set the -u parameter.


From bogus@does.not.exist.com  Wed Apr 23 21:04:36 2008
From: bogus@does.not.exist.com (Eric Jahn)
Date: Wed, 23 Apr 2008 19:04:36 -0700
Subject: [oXygen-user] Validating XML instance with a Schema which
	imports another Schema
In-Reply-To: <480F0928.8050403@oxygenxml.com>
References: <200804222351.m3MNp2ie017910@rs49.luxsci.com>
	<480F0928.8050403@oxygenxml.com>
Message-ID: <200804240205.m3O252Rp028429@rs49.luxsci.com>

Sorin, thank you for taking a look at this.  I fixed the problem you
noted by bringing the namespaces into alignment, but validation of
http://hmis.info/schema/2_8/Example_HUD_HMIS_2_8_Instance.xml
still does not allow the imported schema to be referenced.  Response
below.

On Wed, 2008-04-23 at 13:02 +0300, Sorin Ristache wrote:
> The error is that the target namespace of the imported schema
> http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd
> is "http://cse.unl.edu/~bkutsch/3_0_draft_d5.xsd" which does 
> not match the namespace used in the import element in 
> HUD_HMIS_2_8.xsd (line 10).

I made the target namespace of the imported doc and the import statement
both refer to the same place:
http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd
But I still get the same "Cannot resolve the name 'airs:tSiteService' to
a(n) 'type definition' component." error.  Thanks in advance for any
further insights.  -Eric



From bogus@does.not.exist.com  Thu Apr 24 04:35:08 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Thu, 24 Apr 2008 12:35:08 +0300
Subject: [oXygen-user] Validating XML instance with a Schema which	imports
	another Schema
In-Reply-To: <200804240205.m3O252Rp028429@rs49.luxsci.com>
References: <200804222351.m3MNp2ie017910@rs49.luxsci.com>	
	<480F0928.8050403@oxygenxml.com>
	<200804240205.m3O252Rp028429@rs49.luxsci.com>
Message-ID: <4810544C.7010907@oxygenxml.com>

Hello,

The main schema

http://www.hmis.info/schema/2_8/HUD_HMIS_2_8.xsd

does not specify the location of the imported schema on line 
10. You have to add a schemaLocation attribute to the 
xsd:import element:

     <xsd:import 
namespace="http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd" 
schemaLocation="http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd"/>


Regards,
Sorin


Eric Jahn wrote:
> Sorin, thank you for taking a look at this.  I fixed the problem you
> noted by bringing the namespaces into alignment, but validation of
> http://hmis.info/schema/2_8/Example_HUD_HMIS_2_8_Instance.xml
> still does not allow the imported schema to be referenced.  Response
> below.
> 
> On Wed, 2008-04-23 at 13:02 +0300, Sorin Ristache wrote:
>> The error is that the target namespace of the imported schema
>> http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd
>> is "http://cse.unl.edu/~bkutsch/3_0_draft_d5.xsd" which does 
>> not match the namespace used in the import element in 
>> HUD_HMIS_2_8.xsd (line 10).
> 
> I made the target namespace of the imported doc and the import statement
> both refer to the same place:
> http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd
> But I still get the same "Cannot resolve the name 'airs:tSiteService' to
> a(n) 'type definition' component." error.  Thanks in advance for any
> further insights.  -Eric
> 


From bogus@does.not.exist.com  Thu Apr 24 18:30:15 2008
From: bogus@does.not.exist.com (Eric Jahn)
Date: Thu, 24 Apr 2008 16:30:15 -0700
Subject: [oXygen-user] Validating XML instance with a Schema
	which	imports another Schema
In-Reply-To: <4810544C.7010907@oxygenxml.com>
References: <200804222351.m3MNp2ie017910@rs49.luxsci.com>
	<480F0928.8050403@oxygenxml.com>
	<200804240205.m3O252Rp028429@rs49.luxsci.com>
	<4810544C.7010907@oxygenxml.com>
Message-ID: <200804250022.m3P0M2ix003704@rs49.luxsci.com>

Sorin,
Thanks for the help again.  That worked.  Quick response below.

On Thu, 2008-04-24 at 12:35 +0300, Sorin Ristache wrote:
...
> You have to add a schemaLocation attribute to the 
> xsd:import element:

I was afraid you were going to say that.  I had thought I could get away
with not specifying a schemaLocation, since it's the same place as the
imported namespace, so it looked redundant.  I also thought this because
schemaLocation is optional, and I thought this would be a situation
where it could be optional.  Instead it looks like the only time you can
skip specifying the schemaLocation is when the imported schema resides
in the same local directory as the current schema.  Oh well, I
learned.  :) -Eric



From bogus@does.not.exist.com  Thu Apr 24 18:30:15 2008
From: bogus@does.not.exist.com (Eric Jahn)
Date: Thu, 24 Apr 2008 16:30:15 -0700
Subject: [oXygen-user] Validating XML instance with a Schema
	which	imports another Schema
In-Reply-To: <4810544C.7010907@oxygenxml.com>
References: <200804222351.m3MNp2ie017910@rs49.luxsci.com>
	<480F0928.8050403@oxygenxml.com>
	<200804240205.m3O252Rp028429@rs49.luxsci.com>
	<4810544C.7010907@oxygenxml.com>
Message-ID: <200804250623.m3P6N2ca016472@rs49.luxsci.com>

Sorin,
Thanks for the help again.  That worked.  Quick response below.

On Thu, 2008-04-24 at 12:35 +0300, Sorin Ristache wrote:
...
> You have to add a schemaLocation attribute to the 
> xsd:import element:

I was afraid you were going to say that.  I had thought I could get away
with not specifying a schemaLocation, since it's the same place as the
imported namespace, so it looked redundant.  I also thought this because
schemaLocation is optional, and I thought this would be a situation
where it could be optional.  Instead it looks like the only time you can
skip specifying the schemaLocation is when the imported schema resides
in the same local directory as the current schema.  Oh well, I
learned.  :) -Eric



From bogus@does.not.exist.com  Fri Apr 25 05:04:51 2008
From: bogus@does.not.exist.com (Peter Rushforth)
Date: Fri, 25 Apr 2008 06:04:51 -0400
Subject: [oXygen-user] using custom parser in saxon 9 transformation
	scenario
In-Reply-To: <480F4B81.70200@oxygenxml.com>
References: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>
	<480CB412.2040607@oxygenxml.com>
	<1fd798f40804221823h731bce73u5a928436a408b6d@mail.gmail.com>
	<480F4B81.70200@oxygenxml.com>
Message-ID: <1fd798f40804250304r2af9ced5n4efb73ab5ea13829@mail.gmail.com>

Hi Sorin,

> Now I think I understand. You want to apply an XSLT stylesheet to a stream
> of XML events generated by a custom parser from a binary file. You call the
> custom parser from a custom URI resolver that resolves the URL of the input
> XML file. You set the -u parameter for passing the URL of the input XML file
> through the custom URI resolver.

That's right.

>
> This cannot be done in the current version of Oxygen because Oxygen passes
> the URL of the input XML file only through a built-in resolver that tries to
> resolve the URL of the input XML file with the XML catalogs set in the user
> preferences. The Saxon custom URI resolver is used by Saxon internally only
> for URIs from the XSLT stylesheet because the stream of XML events from the
> input XML file is provided by Oxygen. A future version of Oxygen will pass
> the URL of the input file also through the Saxon custom URI resolver as if
> the -u parameter is always set when Saxon is used in Oxygen.

I look forward to that.
>
> There is a very simple workaround: load the input file through your custom
> URI resolver directly from the XSLT stylesheet with the document() function,
> something like:
>
>    <xsl:template match="/">
>        <xsl:apply-templates
> select="document('URI-of-binary-file-resolved-by-custom-UR-resolver')"/>
>    </xsl:template>
>
> Of course you have to set the class name of your custom URI resolver in
> Options -> Preferences -- XML -- XSLT/FO/XQuery -- XSLT -- Saxon -- Saxon 9
> -- Advanced -- URI Resolver class name.

Did that.

I tried this but it didn't work either.  Still got the "Content not
allowed in prolog" message.


Thanks
Peter


From bogus@does.not.exist.com  Fri Apr 25 07:18:47 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Fri, 25 Apr 2008 15:18:47 +0300
Subject: [oXygen-user] using custom parser in saxon 9
	transformation	scenario
In-Reply-To: <1fd798f40804250304r2af9ced5n4efb73ab5ea13829@mail.gmail.com>
References: <1fd798f40804190650m29b78925l62f885a64b199317@mail.gmail.com>	<480CB412.2040607@oxygenxml.com>	<1fd798f40804221823h731bce73u5a928436a408b6d@mail.gmail.com>	<480F4B81.70200@oxygenxml.com>
	<1fd798f40804250304r2af9ced5n4efb73ab5ea13829@mail.gmail.com>
Message-ID: <4811CC27.50303@oxygenxml.com>

Can you send the XSLT stylesheet, a jar file with the custom 
parser, a jar file with the custom URI resolver and the 
expected result of the transformation?


Regards,
Sorin


Peter Rushforth wrote:
> Did that.
> 
> I tried this but it didn't work either.  Still got the "Content not
> allowed in prolog" message.


From bogus@does.not.exist.com  Fri Apr 25 07:51:29 2008
From: bogus@does.not.exist.com (Dot Porter)
Date: Fri, 25 Apr 2008 08:51:29 -0400
Subject: [oXygen-user] Apply one stylesheet to multiple XML files
	simultaneously
Message-ID: <96f3df640804250551i3eebb287rd126abb94ed25558@mail.gmail.com>

I'd like to apply a single XSLT stylesheet to an entire folder of XML
files at the same time. Is there a way to do this in oXygen? It
appears that you can only configure a stylesheet to process one XML
file at a time.

Thanks,
Dot

-- 
***************************************
Dot Porter, University of Kentucky
#####
Program Coordinator
Collaboratory for Research in Computing for Humanities
http://www.rch.uky.edu
Center for Visualization and Virtual Environments
http://www.vis.uky.edu
dporter at  859-257-1257 x.82115
***************************************


From bogus@does.not.exist.com  Fri Apr 25 08:07:58 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Fri, 25 Apr 2008 16:07:58 +0300
Subject: [oXygen-user] Apply one stylesheet to multiple XML
	files	simultaneously
In-Reply-To: <96f3df640804250551i3eebb287rd126abb94ed25558@mail.gmail.com>
References: <96f3df640804250551i3eebb287rd126abb94ed25558@mail.gmail.com>
Message-ID: <4811D7AE.3010703@oxygenxml.com>

Hello,

Add the folder of XML files to the current Oxygen project 
opened in the Project view, right click on the folder in the 
Project tree and select the action "Transform with ...". 
This action opens the list of transformation scenarios and 
applies the selected scenario recursively to each file of 
the folder.


Regards,
Sorin


Dot Porter wrote:
> I'd like to apply a single XSLT stylesheet to an entire folder of XML
> files at the same time. Is there a way to do this in oXygen? It
> appears that you can only configure a stylesheet to process one XML
> file at a time.
> 
> Thanks,
> Dot


From bogus@does.not.exist.com  Fri Apr 25 08:18:37 2008
From: bogus@does.not.exist.com (Dot Porter)
Date: Fri, 25 Apr 2008 09:18:37 -0400
Subject: [oXygen-user] Apply one stylesheet to multiple XML files
	simultaneously
In-Reply-To: <4811D7AE.3010703@oxygenxml.com>
References: <96f3df640804250551i3eebb287rd126abb94ed25558@mail.gmail.com>
	<4811D7AE.3010703@oxygenxml.com>
Message-ID: <96f3df640804250618o8b6e92fk4e85346dac7f11a@mail.gmail.com>

Perfect! Thank you.

Dot

On Fri, Apr 25, 2008 at 9:07 AM, Sorin Ristache <sorin at > wrote:
> Hello,
>
>  Add the folder of XML files to the current Oxygen project opened in the
> Project view, right click on the folder in the Project tree and select the
> action "Transform with ...". This action opens the list of transformation
> scenarios and applies the selected scenario recursively to each file of the
> folder.
>
>
>  Regards,
>  Sorin
>
>
>
>  Dot Porter wrote:
>
> > I'd like to apply a single XSLT stylesheet to an entire folder of XML
> > files at the same time. Is there a way to do this in oXygen? It
> > appears that you can only configure a stylesheet to process one XML
> > file at a time.
> >
> > Thanks,
> > Dot
> >
>  _______________________________________________
>  oXygen-user mailing list
>  oXygen-user at 
>  http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>



-- 
***************************************
Dot Porter, University of Kentucky
#####
Program Coordinator
Collaboratory for Research in Computing for Humanities
http://www.rch.uky.edu
Center for Visualization and Virtual Environments
http://www.vis.uky.edu
dporter at  859-257-1257 x.82115
***************************************


From bogus@does.not.exist.com  Mon Apr 28 08:09:00 2008
From: bogus@does.not.exist.com (=?ISO-8859-15?Q?Philipp_Steinkr=FCger?=)
Date: Mon, 28 Apr 2008 15:09:00 +0200
Subject: [oXygen-user] Insert empty elements using the elements view
Message-ID: <4815CC6C.5020500@uni-koeln.de>

Hi all,

i have a question concerning the elements-view in Oxygen 9.1. I want to 
insert empty elements
like <lb/> <cb/> etc. The elements-view lists <lb> among the elements 
which accoring to my schema
are allowed at the current cursor position, but when i double-click <lb> 
it inserts the following fragment:

<lb>lb</lb>

"lb" being highlighted for editing. I checked the preferences but i 
cannot find any definition of the <lb> element.
Where can I change such a behaviour? Any hints and pointers to 
documentation or solutions will be appreciated.

Thanks,
Philipp


From bogus@does.not.exist.com  Mon Apr 28 08:38:33 2008
From: bogus@does.not.exist.com (=?ISO-8859-15?Q?Philipp_Steinkr=FCger?=)
Date: Mon, 28 Apr 2008 15:38:33 +0200
Subject: [oXygen-user] line breaks again: oxygen author mode does not
	interpret <lb /> correctly
Message-ID: <4815D359.7060000@uni-koeln.de>

Sorry, i just realized that I was mistaken in my previous email. in 
fact, oxygen correctly inserts
<lb /> only into the xml-document. what still bothers me, and thats 
probably why i got confused,
is the behaviour in the Author mode. there, with "full tags turned on" 
<lb /> is display as <lb>lb</lb>
which seems to be an odd interpretation of the XML. anyway, changing to 
"block tags" and defining
lb in the css as inline-block looks like an acceptable solution if, and 
here is my problem, the line would
really break in the Author mode. But it doesn't. After the <lb /> 
element i can just continue to write.
How could i make Oxygen to interpret <lb /> correctly?

Thanks, and sorry again for my first post.
Philipp



From bogus@does.not.exist.com  Mon Apr 28 08:58:57 2008
From: bogus@does.not.exist.com (Dan Caprioara)
Date: Mon, 28 Apr 2008 16:58:57 +0300
Subject: [oXygen-user] line breaks again: oxygen author mode does not
	interpret <lb /> correctly
In-Reply-To: <4815D359.7060000@uni-koeln.de>
References: <4815D359.7060000@uni-koeln.de>
Message-ID: <4815D821.200@sync.ro>

Hello Phillipp,

You should try to use the following CSS rules for the <lb/> element:

lb {
    display:block;
}
lb:after{
    content:"";
}

The first rule will break the line. The second will inhibit the display 
of the name of the tag. (oXygen displays the name for the empty elements 
so you can identify their position. If an empty element has an 
associated pseudo element - the lb:before  for instance - the tag name 
is hidden).

Best regards,
Dan

Philipp Steinkr?ger wrote:
> Sorry, i just realized that I was mistaken in my previous email. in 
> fact, oxygen correctly inserts
> <lb /> only into the xml-document. what still bothers me, and thats 
> probably why i got confused,
> is the behaviour in the Author mode. there, with "full tags turned on" 
> <lb /> is display as <lb>lb</lb>
> which seems to be an odd interpretation of the XML. anyway, changing 
> to "block tags" and defining
> lb in the css as inline-block looks like an acceptable solution if, 
> and here is my problem, the line would
> really break in the Author mode. But it doesn't. After the <lb /> 
> element i can just continue to write.
> How could i make Oxygen to interpret <lb /> correctly?
>
> Thanks, and sorry again for my first post.
> Philipp
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user


From bogus@does.not.exist.com  Mon Apr 28 12:05:56 2008
From: bogus@does.not.exist.com (Karl Stubsjoen)
Date: Mon, 28 Apr 2008 10:05:56 -0700
Subject: [oXygen-user] FO Intellisense in XSLT document
Message-ID: <8dde156b0804281005p9d2f775y7f01a861e2e8c407@mail.gmail.com>

I'm not getting FO intellisense when working in an XSLT template.  Is
this possible?  I know, have read, that I'll get FO intellisense if my
document root element is fo:root, however my document root is
xsl:stylesheet.

Karl..


From bogus@does.not.exist.com  Mon Apr 28 13:46:28 2008
From: bogus@does.not.exist.com (George Cristian Bina)
Date: Mon, 28 Apr 2008 21:46:28 +0300
Subject: [oXygen-user] FO Intellisense in XSLT document
In-Reply-To: <8dde156b0804281005p9d2f775y7f01a861e2e8c407@mail.gmail.com>
References: <8dde156b0804281005p9d2f775y7f01a861e2e8c407@mail.gmail.com>
Message-ID: <48161B84.1040401@oxygenxml.com>

Dear Karl,

Yes, that is possible. By default oXygen offers also the XHTML elements 
when editing an XSLT document. You can change that to Formatting Objects 
  or to a specified schema or DTD from Options->Preferences -- Editor -- 
Content Completion -- XSL/Xpath -- "Include elements defined in the 
schema" option.

Best Regards,
George
--
George Cristian Bina
http://www.oxygenxml.com

Karl Stubsjoen wrote:
> I'm not getting FO intellisense when working in an XSLT template.  Is
> this possible?  I know, have read, that I'll get FO intellisense if my
> document root element is fo:root, however my document root is
> xsl:stylesheet.
> 
> Karl..
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user


From bogus@does.not.exist.com  Tue Apr 29 08:43:06 2008
From: bogus@does.not.exist.com (=?ISO-8859-15?Q?Philipp_Steinkr=FCger?=)
Date: Tue, 29 Apr 2008 15:43:06 +0200
Subject: [oXygen-user] hide/replace content of elements
Message-ID: <481725EA.4060206@uni-koeln.de>

Dear list,

i have yet another question concerning the hiding or replacing of 
elements, but this time regarding the
content. working in the author mode it would be helpful to hide certain 
elements, like <note> or <abbr>.
using display:none is not very helpful, though, because then the element 
gets completely removed, even from the
structure-view (which i think should be considered a bug, the structure 
view should not be affected by the css).
using visibility:hidden seems to be a better idea, but then the text is 
just invisible and the empty elements are producing
large gaps in the text. do you see any possibility to hide the text on 
the one hand, but display a label or something (showing the tags would
be perfectly fine). i also experimented with width=1px in the definition 
of the element in the css, but it doesn't work.

thanks in advance,
Philipp


From bogus@does.not.exist.com  Tue Apr 29 11:05:18 2008
From: bogus@does.not.exist.com (Karl Stubsjoen)
Date: Tue, 29 Apr 2008 09:05:18 -0700
Subject: [oXygen-user] Customer XML to Schema
Message-ID: <8dde156b0804290905w73e20cb9g6d165f2164025950@mail.gmail.com>

This is more than likely very easy to do!  I'd like to get some
intellisense from my customer's XML document when I'm editing xslt.
Is this posssilbe, or impossible?  There is no schema for the XML, so
I guess step 1 is to create a schema from their XML source, I didn't
see where to do this.

Karl..


From bogus@does.not.exist.com  Tue Apr 29 11:12:07 2008
From: bogus@does.not.exist.com (Karl Stubsjoen)
Date: Tue, 29 Apr 2008 09:12:07 -0700
Subject: [oXygen-user] Re: Customer XML to Schema
In-Reply-To: <8dde156b0804290905w73e20cb9g6d165f2164025950@mail.gmail.com>
References: <8dde156b0804290905w73e20cb9g6d165f2164025950@mail.gmail.com>
Message-ID: <8dde156b0804290912y49cdea54v7d1b9279cb9f1be8@mail.gmail.com>

Hmmm, it seems it is doing it!  But why?  Does the intellisense for
XML elements pick up automatically when the XML is open by the editor,
or is it because I have my transformation scenario wired up?

On Tue, Apr 29, 2008 at 9:05 AM, Karl Stubsjoen <kstubs at > wrote:
> This is more than likely very easy to do!  I'd like to get some
> intellisense from my customer's XML document when I'm editing xslt.
> Is this posssilbe, or impossible?  There is no schema for the XML, so
> I guess step 1 is to create a schema from their XML source, I didn't
> see where to do this.
>
> Karl..
>


From bogus@does.not.exist.com  Tue Apr 29 14:47:32 2008
From: bogus@does.not.exist.com (Karl Stubsjoen)
Date: Tue, 29 Apr 2008 12:47:32 -0700
Subject: [oXygen-user] Commenting and Documenting Customer XML
Message-ID: <8dde156b0804291247rf656cefn2c924e54011f3aa2@mail.gmail.com>

What options do I have in commenting and then documenting my
customer's XML using Oxygen?  I imagine the possiblity of both,
stating fact, and then posing questions, in an attempt to establish
rules, understanding, consistency, layout and semantics.  Hopefully
inline / embeded directly in with the XML, and then eventually
publishing a schema and or resource of my findings.

Hope that wasn't too vague of a question!

Karl..


From bogus@does.not.exist.com  Wed Apr 30 01:58:02 2008
From: bogus@does.not.exist.com (Sorin Ristache)
Date: Wed, 30 Apr 2008 09:58:02 +0300
Subject: [oXygen-user] Re: Customer XML to Schema
In-Reply-To: <8dde156b0804290912y49cdea54v7d1b9279cb9f1be8@mail.gmail.com>
References: <8dde156b0804290905w73e20cb9g6d165f2164025950@mail.gmail.com>
	<8dde156b0804290912y49cdea54v7d1b9279cb9f1be8@mail.gmail.com>
Message-ID: <4818187A.50903@oxygenxml.com>

Hello,

When you associate the input XML document of the 
transformation to the XSLT stylesheet by creating a 
transformation scenario the structure of the XML document is 
learned and passed to the content completion assistant to 
support the editing of the stylesheet. The XML document does 
not have to have an associated schema. The learned structure 
of the XML document is also available in the XSLT/XQuery 
Input view. You can drag and drop XML element nodes from the 
tree of this view to insert quickly in the stylesheet XPath 
expressions that are aware of the context node of the 
editing context in the XSLT stylesheet. For examples of 
inserting such XPath expressions please see the video 
tutorial "XSL Editing" available on the Documentation page 
and the User Manual section where the XSLT/XQuery Input view 
is explained:

http://www.oxygenxml.com/demo/XslEditing/XSLEditing.html

http://www.oxygenxml.com/documentation.html

http://www.oxygenxml.com/doc/ug-standalone/xslt-xquery-input-view.html


Regards,
Sorin


Karl Stubsjoen wrote:
> Hmmm, it seems it is doing it!  But why?  Does the intellisense for
> XML elements pick up automatically when the XML is open by the editor,
> or is it because I have my transformation scenario wired up?
> 
> On Tue, Apr 29, 2008 at 9:05 AM, Karl Stubsjoen <kstubs at > wrote:
>> This is more than likely very easy to do!  I'd like to get some
>> intellisense from my customer's XML document when I'm editing xslt.
>> Is this posssilbe, or impossible?  There is no schema for the XML, so
>> I guess step 1 is to create a schema from their XML source, I didn't
>> see where to do this.
>>
>> Karl..


From bogus@does.not.exist.com  Wed Apr 30 20:35:41 2008
From: bogus@does.not.exist.com (Karl Stubsjoen)
Date: Wed, 30 Apr 2008 18:35:41 -0700
Subject: [oXygen-user] Commenting and Documenting Customer XML
In-Reply-To: <8dde156b0804292230n7ee6f3alb0393480476ea3eb@mail.gmail.com>
References: <8dde156b0804291247rf656cefn2c924e54011f3aa2@mail.gmail.com>
	<f76a63a0804291636p61a3676bnbd2023cc640cca07@mail.gmail.com>
	<8dde156b0804292230n7ee6f3alb0393480476ea3eb@mail.gmail.com>
Message-ID: <8dde156b0804301835u15abbad8j24495e2f7f0eef7b@mail.gmail.com>

Ok, baby steps!
Using Trang Converter, I've created an XML schema from XML source.
The output I chose was W#C XML-Schema (recommendations for other
formats are welcome, I do not know the pros/cons here).  Now I am
going to mark up the schema with xs:documentation and xs:annotation.
Rigth so far?

Ok, how about this.  I have my stylesheet and I have the XML source.
Arbitrarily I have chosen to use a number of the elements in the
stylesheet.  Is it possible to create a USED and NOT USED resource of
elements and attributes from the 2 documents?  So a document outlining
the uses, maybe the count of occurences?  I could write another
transformation to figure this out, er, but if it is built into Oxygen
than that would be great.

Karl..

On Tue, Apr 29, 2008 at 10:30 PM, Karl Stubsjoen <kstubs at > wrote:
> Hmm... since I am new to Oxygen, I am unfamiliar with the
> possibilities before me.  I am interested in self-embeding
> comments/questions into my clients sample XML, then from this XML
> producing documentation, and possibly a schema which reflects on the
> existing nature of the XML plus the comments which I embed.  The
> xs:documentation and xs:annotation options sound like a great starting
> place!
>
> Thanks, I will keep you posted with my progress.
>
> Karl..
>
>
> On Tue, Apr 29, 2008 at 4:36 PM, seth park <babelgone at > wrote:
> > Is your purpose to streamline or clarify XML authoring?
> >
> > If so, shema allow for <xs:documentation/> within <xs:annotation/>.
> > Oxygen cues off of this content when authoring (at least in text mode;
> > I dont use author mode). This will define the purpose of certain
> > elements and attributes.
> >
> > For my client, I am creating document templates for their common XML
> > document types. When a user creates a new document, he/she uses a
> > template that has the required elements and comments that describe any
> > options they may have. See the Oxygen help for where to load custom
> > templates.
> >
> > Hope that helps....
> >
> > seth park
> >
>