I am using editor variable ${xpath_eval} within a transformation output scenario Save As box, because I want to tweak the base uri of the input before sending it to output. But when I do something like this... ${pd}/${xpath_eval(replace(base-uri(),'.+/(\w+).+','$1'))}.html ...I get an error. The lin...

I am experimenting with the expath-archive function library. So far, arch:*-map() functions in general seem to work fine, but whenever I invoke arch:extract-map($i, $j), I get this validation error: [Saxon-EE 9.8.0.12] There is more than one method matching the function call arch:extract-map, and th...

I just found the problem: in my Preferences > XML > XSLT-XQuery > XSLT > Saxon > Saxon-HE/PE/EE I had been pointing to a configuration file, which was overriding the options I had set up to handle saxon:validate(). Hope this helps someone else who stubs their toe on the same issue.

In an XSLT 3.0 stylesheet I want to invoke from the Saxon function library saxon:validate(). oXygen offers the function as part of the autocomplete options when I type. But once the function is in place, the stylesheet is marked as invalid, saying that it cannot find a 1-argument function named {htt...

Hi, it would be nice if, somewhere in the oXygen (I would guess preferences), one could save a Saxon configuration file that has the values that are currently set in the global or project options.

Hi, it would be nice if Options > Preferences > XML > XSLT-XQuery > > Saxon-HE/PE/EE had a checkbox allowing users to toggle between 1.0 and 1.1 for values of -xmlversion. I realize I can build my own configuration file, but that would be less convenient than playing with oXygen's preferences.

I have a frameworks file where I want, in the Author Actions, to specify an Activation XPath that applies to a <div> in one namespace but not another. It would be nice if in a framework I could declare namespace prefixes and use them, independent of what the user might have (or not have) listed at P...

In a project that was once upon a time validating fine on a Mac (oXygen v. 20), I am now (v. 21 on PC) getting the following message: [ISO Schematron] xsl:result-document is disabled when extension functions are disabled. For security reasons the external function calls have been disabled because th...

Update: when I switch to the Database perspective, I get the Information view just fine. But when I switch back to Editor perspective it disappears again.

I was moving a floating information window pane to a second monitor and through a poor drag of my mouse, it went off the screen. I now can't get it back, despite trying different things (removing the second monitor, resizing screen resolution). I completely reinstalled oXygen 20.1 and the info pane ...

Thank you, Alex. It turns out that I needed to do what you suggested, but in a different area. I document it here in case others stumble across this thread. The problem lay in the Ant Transformation Scenario I had already set up. I needed to go into Configure Transformation Scenarios and edit the ch...

I'm trying to do an ANT-based transformation of an ODD file and getting this error: Description Transformation failed. /Applications/Oxygen XML Editor/frameworks/tei/xml/tei/stylesheet/common/teianttasks.xml:389: java.lang.NoClassDefFoundError: ro/sync/basic/util/Crypto Severity Fatal Scenario TAN s...

I've gotten these results running oXygen 20.0 build 2018042410 on a Mac and 20.1 build 2018061313 on a PC. Sample code below. a.rnc: include "incl/b.rnc" { start = element test { xsd:double } } incl/b.rnc: include "c.rnc" { start = element test { xsd:double } } incl/c.rnc: start = element test { xsd...

Given the following files... a.rnc incl/b.rnc incl/c.rnc ...A includes B and B includes C. Validation is fine in all three files. But formatting the document (CTRL + SHIFT + P) works for only B & C. For A I get the following error: C:\Program Files\Oxygen XML Editor 20\incl\c.rnc (The system cannot ...

I find it just a bit of a hassle to go Options > Preferences > Editor > Document Checking to toggle auto validation on and off. It would be nice if there were a toolbar button to do this as well. Maybe that feature already exists and I can't find it?

In an XSLT 3.0 stylesheet I don't see the built-in json-to-xml() show up in the list of functions built via content completion. The function, hand-typed in, works fine. Any suggestions on how to get it in content completion? I didn't see anything in Preferences that seemed to answer this question.

I find that I've been using the editor variable ${ask('message', relative_url, 'value')} to prompt a user either to choose a place where to save output, or to select files for supplementary input. For the first need, it would be nice if users could pick just a directory, and not a file. For the seco...

Hi Sorin,

Hm, it seems that a little experiment I did showed that the problem is specific to my git repo, which has had several years of accumulation, and at one point the case difference and diacriticals threw a wrench in the normal git workflow. So ignore my complaint.

In the git plugin I'm getting a list of files for deleting and adding that don't match the list that exists when I run git status in the shell. These seem to have to do with cases where filenames have had changes in case, or in accentuation. If you want to look, I've just pushed a clean repo here . ...

The Git plugin / add-on is amazing, and very useful. Thank you! I realize that git has dozens of parameters that could be supported, so when I suggest this and others, I'm focusing only on those parameters in git that I tend to use. That said, it would be helpful to have an amend checkbox, to includ...

Small bug to report. I have some files that are named identically except for the last letter (before the extension). The ones ending in ς are superimposed upon the ones ending in σ. That leaves a gap in the file listings, and it makes it difficult or impossible to put the focus on the ones ending σ.

Thanks, Radu this makes sense. I didn't know about getting .xpr files into the editor via dragging. Now that I'm looking at my .xpr file, I'm wondering if, instead of a new menu option as I had earlier requested, there was a built-in project.sch file in frameworks/oxygen/ that did some basic checkin...

I have been developing a project that is now several years old, and the project .xpr file is now 3.5 MB. Recently I've been getting "Unable to save" messages when I change a transformation scenario for a file, and I'm wondering if the size is a problem (perhaps in tandem with Dropbox syncing). I'm s...

Thanks -- perfect! It might help future users if documentation made this suggestion more explicit.

Now that I'm using the validation tab, it's unclear to me what function the schema tab has. That is, what does the latter do that the former does not do?

In the Document Type Association > Schema Tab it would be nice if one could associate a document type with more than one pairing of schema type + schema URI.

In the Document Type Association > Schema Tab it would be nice if one could pick a Schema type that is pure Schematron (i.e., not mixed with other schema languages).

Low-level request: it would be nice if hitting ctrl+shift+alt+C for select content worked not just when the cursor is in a text node, but also when it is within an attribute value, to select everything between the quotation marks. Not sure if that's feasible, but it would be a nice convenience.

Oftentimes I find myself editing files that are either very large or involve some complicated Schematron rules. Sometimes these rules give tips or aids in editing, and I have to wait a long time to get contextual help via SQF or Schematron-based messages, because the engine is checking the entire fi...

Here's a sample. You'll see that color coding would be nice not just for a string, but for variables. <x:scenario label="Scenario for testing function matches"> <x:call function="tan:matches"> <x:param name="input" select="$regex-greek"/> <x:param name="pattern" select="'abcθ'"/> </x:call> <x:expect...

A nice feature would be to have color coding for xspec @select. It took me the longest time to diagnose an error, only because I thought (due partly to the color) that was the correct syntax for a string, when it should have been .