- oXygen-user - www.oxygenxml.com

Module name in errors with MarkLogic
by David Lee 15 Feb '12

15 Feb '12

When using an XQuery transformation against MarkLogic where the main module imports a module, if I get an error in the imported module the error printed by Oxygen does not report this. It reports the line number but no indication that the line refers to an imported module or which one. I know this information is available because I can get the full information including a stack traceback when using MarkLogic's CQ or query console. Any suggestions on how to get this info in Oxygen ? If not I'd like to suggest it as a feature for V(N+1) ---------------------------------------- David A. Lee dlee(a)calldei.com<mailto:dlee@calldei.com> http://www.xmlsh.org

2 1

Re: [oXygen-user] Learning Xml structure for XSLT authoring
by Adrian Buza 15 Feb '12

15 Feb '12

Hello Wendell and Karl, Wendell, If we decide to implement a solution that adds a performance penalty or clutters the interface, I can assure you that an option will be available to turn that feature off. Additionally there is another idea to provide content completion in XSLT from the associated DTD/schema(if one is available) of the XML file. Something similar could be used to implement your proposal("XSLT's content completion could aggregate the XML files it sees there"), a schema could be created dynamically from the XML files(similar to the Tools > Generate/Convert Schema) and that schema could be used for CC. BTW Wendell, I believe you have accidentally sent the reply only to me without CC-ing to the list. Karl, We could use an Oxygen PI in the XSL content to associate an XML with the stylesheet, similar to the association of a stylesheet with the XML. e.g. <?oxygen type="text/xml" href="myfile.xml"?> I've logged all your suggestions and the improvements of this feature will be discussed internally. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Karl Stubsjoen wrote: > How about this features: > > Similar to learning an Xml document, when editing an XSLT an option to > learn *any* Xml (ie., the Xml document I happen to have open). A > dialog box appears on Learn, (better: Associate) Xml to XSLT and then > you can pick one. > > Thanks! > Karl.. Wendell Piez wrote: > Hi Adrian and Karl, > > On 2/10/2012 3:51 AM, Adrian Buza wrote: >> Currently there is no other way to have content completion(CC) in the >> XSLT with the XML structure other than creating and associating a >> transformation scenario with the XSLT. If you create and associate a >> scenario with the XML file that does not affect the CC in the stylesheet >> mentioned in the scenario. >> The problem with detecting all scenarios that use an XSLT file is that >> it's possible to have a scenario that uses an XSLT but it's associated >> with various XML files. So in that case which XML would you want? >> One possibility is to have all of them, but that could prove to be >> excessive in some situations(e.g. very large XML files). >> >> I've logged this to our issue tracking tool as a feature request and it >> will be analyzed and implemented in a future version of Oxygen. > > I'm not sure I'd actually like that. I'd certainly like to be able to > turn it off, or (maybe better) for a feature like that to be > configurable. > > On the other hand, I'm not sure I understand the requirement, since > it's now perfectly possible to have one scenario bound to a document > A, which uses stylesheet X, and another bound to stylesheet X, which > uses document A. Then when you edit stylesheet X oXygen knows about > document A. > > The kernel of this idea, however, namely to have content completion in > a stylesheet informed by more than one XML document at a time, is very > interesting. Maybe if XSLT transformation scenarios were able to > process entire subdirectories (or a logical folder in a project) in > batch, then the XSLT's content completion could aggregate the XML > files it sees there. (Yes this would have performance implications.) > > Cheers, > Wendell > >> Karl Stubsjoen wrote: >>> I realize that if I setup a transformation scenario between the XSLT >>> and the Xml then when authoring the XSLT I get intellisense on the Xml >>> source but only if I create a transformation scenario where the XSLT >>> is used as the document to build a scenario from. So what if I create >>> a transformation scenario and I use my source Xml as the starting >>> point (typical for me)? I don't get the intellisense when in the >>> stylesheet. >>> >>> Besides the above, is there another way for the Xslt to learn the >>> Xml source? >>> >>> Thanks, >>> Karl.. >>> >>> >>> >> >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user >> >> >

2 1

Learning Xml structure for XSLT authoring
by Karl Stubsjoen 10 Feb '12

10 Feb '12

I realize that if I setup a transformation scenario between the XSLT and the Xml then when authoring the XSLT I get intellisense on the Xml source but only if I create a transformation scenario where the XSLT is used as the document to build a scenario from. So what if I create a transformation scenario and I use my source Xml as the starting point (typical for me)? I don't get the intellisense when in the stylesheet. Besides the above, is there another way for the Xslt to learn the Xml source? Thanks, Karl.. -- Karl Stubsjoen MeetScoresOnline.com (602) 845-0006

2 2

HTML5 doctype error
by Rob Koberg 10 Feb '12

10 Feb '12

Hi, I pasted the HTML5 boilerplate HTML5 into anew html file produces an error saying: Engine name: Xerces Severity: fatal Description: The markup in the document preceding the root element must be well-formed. Start location: 1:3 Line 1 looks like: <!doctype html> best, -Rob

2 2

minor: pretty printing CSS bug
by Rob Koberg 10 Feb '12

10 Feb '12

Hi, Given this CSS file text: body { font: 80%/1.5 Arial,Helvetica,sans-serif; } Pretty printing produces: body { font : 80% / 1.5Arial, Helvetica, sans-serif; } Note the spaces around the font-size and line-height forward slash and no space between 1.5 and Arial. best, -Rob

2 1

XPath expressions syntactically highlighted in XSLT
by Florent Georges 07 Feb '12

07 Feb '12

Hi, In 13.2, I discovered the new feature of highlighting the XPath expressions in the select attributes in XSLT. While this is a good idea I think, the result is not really clear in my humble opinion. It is hard to visually differentiate the value of the attributes (the XPath expressions) and the XSLT instructions themselves, as they use nearly the same colors. Something that could (probably) help would be to have the ability to add some grey-shading under the select attributes. Like a (very) light background color. So it would be possible to visually differentiate directly what's an XPath expression and what's the XSLT structure. Just some thought... Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

2 2

Improving the scenario dialog (organize 'em all)
by Florent Georges 07 Feb '12

07 Feb '12

Hi, I always found it quite difficult to organize my scenarios. After giving it some thoughts, I think 2 things could help here (especially the first one)... 1/ separating (for instance in 2 tabs, might be an optional feature) the global scenarios and the project scenarios 2/ allowing the user to categorize the scenarios, either in a tree hierarchy, or by allowing him/her to create new "scenario types" to belong in the dropdown list Just some thoughts... Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

2 4

Fill in attribute values automatically?
by Yves Barbion 06 Feb '12

06 Feb '12

Hi group When I insert an image into my DITA topic, I need to specify a number of attributes such as platform, otherprops etc. I have to do this for each and every image over and over again and the attribute values are always the same for all images. So, I was wondering: is there a way to have these attributes values filled in automatically? Thanks -- Yves Barbion www.scripto.nu

2 1

[Ann] New maintenance builds available for oXygen 13.2 (2012013115)
by Adrian Buza 03 Feb '12

03 Feb '12

Dear oXygen users, We are glad to announce the release of new maintenance builds for oXygen 13.2(Editor, Developer, Author). Build number: 2012013115 The build number can be verified in the Help -> About dialog from the application(next to the version number). You can download the new builds from our web site: http://www.oxygenxml.com/download.html The complete list of bug-fixes for these maintenance builds can be found here: http://www.oxygenxml.com/build_history.html#2012013115 Please let us know if you encounter any problems with these new builds. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

Validation of @class on non-DITA elements
by Eliot Kimber 01 Feb '12

01 Feb '12

It looks like the DITA Schematrons are validating @class on non-DITA elements (that is, elements within topic/foreign), e.g. @class on MathML elements. The Schematrons should ignore the non-DITA content of <foreign> elements. Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

2 2