Another, similar approach would be to support some kind of help content inside the framework, such that I could add something to map certain error to certain help, then Oxygen adds a help icon or link to the message opening the help content. A hot link is fine too, especially if it's also hot in the...

In my schematron message, I sometimes include hyperlinks to point the user to a source for more information about their problem: <sch:rule context="db:book|db:part|db:section|db:chapter|db:appendix|db:preface|db:table|db:figure|db:simplesect"> <sch:assert test="@xml:id">xml:id re...

Oh, the other place this shows up is in the variable ${frameworkDir(framework_name)}}. If anybody had made a transformation scenario as part of an xpr or whatever and used that variable, then changing the name breaks them.

Yes, I understand how the mechanism works. In our case, the framework originally had a name like "DocBook - Extension Whatever", so the default profile sets were in play when our extension was used. Users apparently built on those, keeping the existing pattern of "DocBook*". When...

I recently renamed my framework extension to a string that no longer starts with "DocBook". Unfortunately, this has broken the ability to use existing condition sets for all my users. Is there a graceful way to fix this, or is changing the name again so it starts with "DocBook" m...

It would be really cool if I could associate the code templates with namespaces, so if I'm in the xslt namespace, not matter what kind of document, I can use the xslt-related code templates. So if I'm editing an xproc file, I could use a code template to enter the following, and once I'm at ${caret}...

I'm a big fan of code templates and of course we all love namespaces. I notice that there's already a code template for the xsl namespace that's limited to the xslt editor. That's cool, but... Feature request #1: It should really be possible to define a code template as being for all xml editors (xm...

It ended up being easy to implement schematron-based validation for IDs and IDREFs by importing transclusion-fixup.xsl and reusing the functions and templates in my schematron rules (so if I change the logic in transclusion-fixup.xsl it will propagate to my schematron). Doing this in schematron turn...

On the root element of a .framework file is a version number corresponding to the version of Oxygen that created/edited the file: <serialized version="18.1" xml:space="preserve"> <serializableOrderedMap> ... We have users on more than one version of Oxygen, but for development it...

Ok, now I see what it's doing. In general, it's doing things that make sense. Often it splits elements. For example, if you insert a chapter in the middle of a para in the context /book/chapter/section/para, it closes the current chapter (closing the para, section, and chapter), and inserts a new ch...

Is there a way to do a Find within a diff/compare session but limit the scope to content that was added (or optionally removed)? Not a big deal, but would be handy just now.

Thanks,
David

I'm trying to figure out what the default behavior of Oxygen is and if I've broken something with a config or framework change. If you're in Author view editing a DocBook 5.x document, say in the middle of a para, and press return to bring up the content completion thing, you're presented with a lis...

We're using nvdl, so I can skip id/idref checking by omitting this option: Using nvdl (or something we're doing) might be borking other aspects of the framework, but I'll start another thread about that.

David

Unfortuantely, path="db:*" ends up being the same as omitting the path attribute and applies the rule to all elements. My goal is to hide these attributes from elements in the DocBook namespace, but to allow them on the xi:include element. These attributes must be legal on all elements tha...

A few questions about the XSLTOperation: How are entities treated? If I run my xslt over an element that includes an entity, will that entity be resolved in the result? How are xincludes treated? Are xincludes resolved or left in place? Will my xslt operate on the included document? Where can I find...

I think I'll wait for the bug fix rather than maintain my own meta-action and remapping everything in the gui to it, but those operations are handy to know about, especially the XSLTOperation. I can put that to good use elsewhere.

Thanks,
David

Thanks for taking care of that. Life is much easier when Oxygen and Calabash agree about things. The only thing requried to support things like db:idprefix is that attributes be passed down to the xincluded content. You can then implement arbitrary post-processing to fix ids, turn data into DocBook,...

Btw., I suppose all this implies an update to the xinclude insertion Action/wizard. At the very least you'll need a way to set the value for the set-xml-id attribute, perhaps with an "auto" option that defers to the ID Options? Maybe also a way to add other attributes that are allowed on x...

Correction, it works (the paras are added) for the Actions that have cellFragment for fragment arguments. I hadn't noticed that for each Action there are several Operations for different Activation XPaths. However it does NOT work when using the Insert Table dialog (whether inserting a table or info...

I'm trying to do what is described in this post https://www.oxygenxml.com/forum/post41634.html?hilit=cc_config.xml%20table#p41667 but for DocBook. When I edit the insert.table action, there's no cellFragment field available to modify the template markup used by the table wizard. It just defers to ro...

Ah, this looks like a very useful file. What I really want to do is the following to suppress these attributes on all elements in the docbook namespace: <elementProposals xmlns:db="http://docbook.org/ns/docbook" path="db:*" rejectAttributes="db:idfixup db:idprefix db:linksco...

I've pushed up an example illustrating the features from the xinclude 1.1 spec and the differences between the behavior of Oxygen and Calabash:

https://github.com/dwcramer/xinclude-at ... py-example

Ok, correction: Oxygen is passing down attributes to the xincluded content, but it's not doing any fixup of the duplicate ids. Initially, Oxygen was reporting validation errors due to my extra attributes on my xi:include element that were being passed down. This was apparently causing it not to repo...

I have a situation where I need certain attributes to be valid in my schema, but I do not want users to add this attribute manually or have them be confused the attributes cluttering up the Attributes View. Is there a way to configure my Document Type so that certain attributes do not appear in the ...

I'm experimenting with the xinclude 1.1 support in Oxygen 19.1 and want to understand how it works. I have a test document that xincludes the same section several times. When I validate this document in Oxygen 19.1, it no longer complains about the repeated xml:id attributes. Yea! What's not apparen...

Thanks for the explanation Radu. Given those challenges, using a fallback in these cases is a good approach for us.

I'm using an XProc pipeline with Calabash to resolve xincludes. In addition to supporting xinclude 1.1, this allows me to use the xpath() xpointer scheme like so: <xi:include href="../shared/content/content.xml" xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//db:section[xml:...

It appears this was a bug that disappeared between 18.1 and 19.0. I have several versions of Oxygen running to represent what our users have installed. A users reported the issue and I reproduced it one 18.0, but hadn't checked 19.0.

Thanks,
David

Hi there, I've got a request to notify users about updates to our framework and tools when they start Oxygen. I was thinking there might be a way to hijack the Tip of the Day box and load it with our own content. I'm not seeing anything in the docs or finding a tell-tale xml file loaded with the tip...

Hi Radu, Thanks for that explanation. We've experimented with adding standalone="yes". With that added to the xml declaration, Oxygen does indeed start reporting all undeclared entities, even those in attribute values, as fatal errors. However, it also reports other things as errors that I...