- oXygen-user - www.oxygenxml.com

"Job well done!" messages
by Wendell Piez 12 Jan '11

12 Jan '11

Hi, Of course, the usual thing with XML processors when validating has been to give error messages for syntax or validation errors, but to be coyly silent when no errors are found. The user is left to infer that everything is good based on the fact that there are no complaints. oXygen improves this state of affairs by having a little box that lights up green when a document is valid, plus a line that says (with admirable clarity) "Document is valid". However, some users wish for more. They'd like a trumpet fanfare or something analogous. (Wouldn't we all?) In particular, I have some users who have asked if they can have their Schematron tell them when there are no errors. I have explained that they will probably have to be content with the green light, and I don't think this is too much to ask of them. But I am also wondering whether oXygen might have hooks somewhere that could be used to pop up an alert box or something, with a congratulatory message of some kind. (This is a case, of course, when having an explicit Schematron report test when "not($a or $b or $c)" won't work, since the number of tests is in the double or triple digits.) What are the ramifications here and what would it take for these users to get what they want? If this were all done inside a processing pipeline I could Schematron the results of my Schematron to run the test; but it's not; nor do they want it to be since of course they like the fact that their error messages have live links back to the documents. I am imagining some kind of facility that could be associated, for example, with a validation scenario. Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

3 3

Possible to Graft Catalog Support to Trang Within Oxygen?
by Eliot Kimber 11 Jan '11

11 Jan '11

Trang as integrated with Oxygen is not catalog aware, which is a bit annoying when you want to generate XSDs from DITA map and topic types, which are all about the catalogs. Is it technically possible for Oxygen to add catalog support to Trang? Having that would be really really handy. Thanks, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

2 1

which Schematron processor?
by Syd Bauman 27 Dec '10

27 Dec '10

I'm guessing that if I check the "Use Saxon EE (schema aware) for xslt2 query binding - If checked, Saxon EE will be used for xslt2 query binding." box in the "ISO Schematron" section of the XML / XML Parser preferences page, then oXygen will use Saxon EE to validate my documents against an ISO Schematron schema that uses xslt2 query binding. But what does oXygen use as an ISO Schematron validator if I *don't* check that box? (The documentation under the Help menu doesn't say.) As I side note, I'm asking because I'm getting warnings from the validation that I thought might really be indicative of a processor- specific problem, rather than a Schematron schema or validation error. Probatron does not complain, but oXygen warns that "The attribute axis starting at an attribute node will never select anything" and that "The child axis starting at an attribute node will never select anything". The rule that generates the complaint is <rule context="tei:*/@*"> ... </rule> So I'm guessing that the processor tried to convert this to some generic XSLT that included a match pattern that would never fire. So I tried switching processors to Saxon EE, but that just added an error to the warnings: "Cannot validate <TEI>: no element declaration available". It took a Google search to find out that setting oXygen to use Saxon's -vlax switch is how to deal with that. (Found http://www.oxygenxml.com/forum/topic4460.html.)

2 1

Oxygen - Cached/Paging XML with/without Backup/AutoSave
by McDonald, Shaun 23 Dec '10

23 Dec '10

Hello All, Recently, an Oxygen Author user has been experiencing rather large chunks of XML data being removed from documents on save. Aside from troubleshooting this particular issue, a larger issue arose given a particular scenario. Let's say the following parameters are in place: 1. Half our users are on Win XP, the other Win 7, 2. Half us Author v11.2, the other v12, 3. Windows Paging file initial and max values vary. SCENARIO 1. User checks out an XML file from a CMS repository (via an Oxygen Author plug-in) and edits the document, but 2. User gets interrupted with an unrelated task requiring one or more other apps. * The app(s) use a large amount of memory and write to Windows temp, 3. Memory is overtaxed and the Paging File is written to. 4. User returns to Author to check in the XML. Obviously, we have validation gates to reject ill-formed/invalid XML. But, theoretically, we would like to know exactly what might be checked in given the scenario, and 1. Memory and paging are maxed out already when a user makes an edit to some other document, and 1. Oxygen Backup and Automatic Save Preferences are off, 2. Backup Preferences are on, 3. Automatic Save is on and set to a low value 4. Both 2 and 3 are on. Thanks, Shaun

2 1

Networked Frameworks
by McDonald, Shaun 23 Dec '10

23 Dec '10

Hi, Are there any performance costs to networking a single framework for multiple users? Say, 10-20 users might simultaneously open disparate files that invoke the same DTA rule. This would be networked via Active Directory to Windows machines. Thanks, Shaun

2 1

Ghost Instance of Oxygen Running
by McDonald, Shaun 22 Dec '10

22 Dec '10

Hello All, I noticed that when I open Oxygen, my taskbar will show two instances (buttons). Only one of them would max/minimize the application on click. The version is 11.2. How can I fix this? Are there side effects on the JVM costs? Thanks, Shaun

2 1

XML AUTHOR + Docbook5: Problems with using custom HTML chunk scenarios (parameters conflict with customization layer)
by Robert Nagle 15 Dec '10

15 Dec '10

I have been having a persistent problem with doing HTML-chunk transformations with Docbook 5 and Oxygen 12. I think I had similar problems with Oxygen 11 too. I wrote a xsl customization layer rjstyle.xsl. Initially what I thought I could do was to duplicate the HTML-chunk scenario and change the XSL URL to rjstyle.xsl. But I discover that a few of my parameter settings are not working. That is because the parameter values I am giving in rjstyle.xsl are differing from the preset parameters in Oxygen's HTML chunk scenarios. Oxygen's parameter settings are overriding my own in rjstyle.xsl. QUESTION: Is there a way to tell your Edit Scenario dialog for the parameter settings in rjstyle.xsl to override whatever presets Oyxgen put into its out-of-the-box Docbook scenarios? The answer would seem to be to create a new scenario from scratch. However, whenever I do that, I seem to receive a lot of compiler errors. To give an example of what I mean by errors: 1)Engine name: Saxon6.5.5 Severity: error Description: ch01.html (Access is denied) Engine name: Saxon6.5.5 Severity: error Description: The system cannot find the path specified (With both types of errors, it works fine when I use the out-of-the-box docbook chunk scenarios. Also, I have torn out all the excess stuff from rjstyle.xsl except for: <xsl:import href="../../../1latest/docbook-xsl-1.76.1/html/chunk.xsl"/> 2)non-validating XHTML code. It won't show in the browser. (this is less common than the above two; might be a fluke with my current project). If I use Oxygen's chunk XSL defaults and add rjstyle.xsl as an additional XSLT stylesheet (an option in the Edit Scenario dialog), I get an error: SystemID: I:\My Documents\My Dropbox\xml\testbug2\index2.xml Engine name: Saxon6.5.5 Severity: error Description: Cannot apply cascading transformation. Reason: org.xml.sax.SAXParseException: A well-formed document requires a root element. One of the complicating factors here is that the Edit Scenario dialog (with 3 tags) has a lot of options. It's good that the Oxygen team can compress so many options into one dialog; on the other hand, it's hard to transfer settings into a New Scenario and be certain you have copied everything. QUESTION: Do you have any hints about creating Docbook transformations from scratch that avoid the Access is denied and system cannot find the path specified errors? I realize that I am not giving you enough information about my specific project. But I suspect that you may have some general ideas about what is wrong (besides, my brain is growing weary). By the way, you might be wondering why I am not content using an out-of-the-box chunk scenario. 1)I find it cumbersome to edit the parameter list (and don't have a way to save my settings in an easy-to-read format) and 2)It's easier for me to hard code the latest docbook xsl in a user directory rather than a system directory. -- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info

5 9

DocType Association & Insert Character Actions
by McDonald, Shaun 14 Dec '10

14 Dec '10

Hi, I'm building Author frameworks and would like to provide editors with a finite list of special characters to insert via a toolbar. I've noticed that defining a character's value as the letter itself is fine, but our data models require that only hex values be used in XML documents. I've tried inserting the hex value directly into the action definition, but this only produces text in the Author view. Example, an attempt to insert this, Á, results in &#xc1; in the XML. Of course, no frameworks feature is available in text view which seems to force the use of the Entity Panel. How can I create a DocType Association action for inserting hex entities? Thanks, Shaun

2 1

Disregard last Port: DocType Association & Insert Character Actions
by McDonald, Shaun 13 Dec '10

13 Dec '10

I found the problem.

1 0

Missing TagSoup Jar in Oxygen 12.0 to make p:unescape-markup of XProc work
by mozer 24 Nov '10

24 Nov '10

Dear all, During a training, I realize that TagSoup wasn't part of Oxygen 12.0 When we added it, Calabash just worked fine If I'm not wrong, there is no licence restriction here Hope this helps Xmlizer

2 2