- oXygen-user - www.oxygenxml.com

Namespace prefix unnecessarily added to elements in element list
by David Cramer 16 Feb '12

16 Feb '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, I'd like to report an annoyance in oXygen involving namespace prefixes in the element list. If you have a DocBook file that declares the following namespaces: <book xmlns="http://docbook.org/ns/docbook" xmlns:db="http://docbook.org/ns/docbook" version="5.0" xml:id="os-cs-devguide"> ... Then every DocBook element in the element list will be prefixed with db:. If you remove the xmlns:db="http://docbook.org/ns/docbook". It would be better if oXygen in this situation just ignored the xmlns:db declaration and displayed the DocBook elements in the element list with no prefix. I currently tell the writers to remove the declaration, but the whole issue confuses them. The problem is that we have developers who prefer to use emacs or whatever and have the habit of creating files with a bunch of namespaces, whether they need them or not (see example below). I haven't been able to break them of this habit. <book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:svg="http://www.w3.org/2000/svg" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:html="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook" version="5.0" xml:id="os-cs-devguide"> Thanks, David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPPIsRAAoJEMHeSXG7afUh14cIAIfuIfGC2KqhJmWhJctwcEbu 7YBjuLtFrmphRU8fgJPb6jHUodgw0ZfcEb9a5D0jvVPk3aL3//G+WGZhWPNAbfk9 otpfXDMV+o+kgcrvhgAyp0K+2VRE7pbP42pmKAayx5dGBnZOd8Cqlx9mLfS5tGtg RSnYkgT4rcQwyyopeHrW27kaUx7NNsJk6ZeQMWhaHgmDP2/lFCDpwEVABCz2sqW7 DfgWPrkn5nHyv+T22Y9kVboXkRetWA/lZ158HfyjWJfZ07DOSgcuvRQ+JwD9ivBB +P6iI645RSDdDWlxY7AUP3oYbpsvY+Q8oVOroem2Ml3L6pH5S1lw1uwRVkAQ58M= =1zWu -----END PGP SIGNATURE-----

2 1

CSS Validation problems
by David Lee 16 Feb '12

16 Feb '12

I'm editing a css file for use in Author mode. My default CSS validator is set for "CSS 3 with oxygen extensions" Content completion is working fine but somehow validating the CSS is finding errors where there should be none. Any suggestions ? It looks like the validator is using a different engine then the content complete. e.g. function { display:block; background-color:#EEEEFF; color:black; white-space:pre-line; ERROR HERE white-space-collapse:preserve-breaks; ERROR HERE margin-left: 1em; border-bottom-style:solid; margin-top:0; } Engine name: W3C CSS Validator (CSS3) Severity: error Description: Context : function in property : white-space pre-line is not a white-space value : pre-line Start location: 21:0 Engine name: W3C CSS Validator (CSS3) Severity: error Description: Context : function in property : white-space-collapse Property white-space-collapse doesn't exist : preserve-breaks Start location: 22:0 ---------------------------------------- David A. Lee dlee(a)calldei.com<mailto:dlee@calldei.com> http://www.xmlsh.org

3 3

Problems with XQuery indentation.
by David Lee 15 Feb '12

15 Feb '12

I'm having two problems with xquery editor indentation that I suspect are in some option somewhere but can't find them. 1) Tab size and spaces Can I set the Tab key to use Spaces and specify how many ? e.g. make Tab use 2 space characters. 2) Matching indentation of {} When I declare a function the closing } doesn't auto-match the indentation of the opening }, and to make it worse when I use Enter it does indent ... which makes it harder. e.g. Typing declare function local:test()<ENTER> {<ENTER> <TAB>foo()<ENTER> } Leaves me with declare function local:test() { foo() } ---> Indented here Maybe a minor point but when I see Oxygen matching to the open { why wont it match the indentation? Is there a way to get it to ? Thanks for any hints ---------------------------------------- David A. Lee dlee(a)calldei.com<mailto:dlee@calldei.com> http://www.xmlsh.org

2 1

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