Hi, I'm building DITA maps and topics with DITA Glass. However, DITA Glass short URLs are expanded inadvertently so often. Can we stop it? For example, Save a local copy of https://github.com/oxygenxml/dita-glass/ . Open its samples.xpr. Open presentationSamples/convertSamplesWithAlias.ditamap in DI...

Oops. Found it documented.

Thanks for the great news, Radu.
Could you show us an example @import line with the editor variables? In particular, I'm not sure if oxy_url() is necessary or not.

Per https://www.oxygenxml.com/forum/topic6804.html#p33369 In oXygen 16.1 we improved the inclusion mechanism when working with ISO Schematron modules by adding support for iso:extends element. This element allows you to include all the components defined in a Schematron schema (such as patterns or p...

I too would welcome this feature.
Currently I use Araxis Merge for it. But its expression filter is regexp-based; a bit fragile and not so much helpful.

Confirmed on 17.1 build 2015121117. Thanks for hearing us.

HomeGoods wrote:I think it is working at the first stage ("[xslt] Processing ....xspec to ....xsl") .

Uh, nope. I meant the second stage ("[java] ...").

I've a similar issue. I have saxon.custom.options =-catalog:http://... specified in the transformation scenario and I think it is working at the first stage ("[xslt] Processing ....xspec to ....xsl") . But it doesn't seem to take effect at this stage: [xslt] Processing ...-result.xml to .....

I'd second that.
Last week I had an active review session with a non-developer author. She complained about the required mouse move and eagerly wanted the equivalent of MS Word's "Accept and Move to Next" button.

Radu,
Thanks for the update. I confirmed that on the build 2015093018, U+3000 was not checked in the whitespace preference by default. I think that's the right decision.

And the consequence is...?

Not sure which level of "built-in" you're looking for. Anyway I sometimes find a wrapper XSLT with saxon:compile-stylesheet() and saxon:transform() is easier and more portable than XProc.

By default, Preferences - Editor - Format - XML - Whitespaces has U+3000 ticked. This looks too radical to me; even destructive. U+3000 is used on purpose in many cases. What's the specific reason to have it ticked by default? Well, I can just untick it and forget about it. So I'm rather just curious.

Yes, so IE shouldn't fall into compatibility view with build 2015071312 or later.

Forgot to mention that also you should not copy the 'install' directory.

Once configured, you need to be careful not to overwrite config.php, otherwise you lose your current configuration. Discussed http://www.oxygenxml.com/forum/post31962.html and http://www.oxygenxml.com/forum/post32449.html I sometimes overwrite it by mistake and hope for more foolproof file structure...

I guess this X-UA-Compatible position fix (build 2015071312) would prevent IE from compatibility view: http://www.oxygenxml.com/forum/post34166.html

Mihaela,
I do hope the improvement of DITA Maps Manager in the near future.
For the meantime, as you suggested, I'll see if Author mode CSS can be of help.

In DITA maps, @collection-type is an essential attribute of topicref. Currently, to see or verify the collection type in oXygen DITA Maps Manager, I open each topicref's properties and look for "Collection type" value. This is a tedious and error-prone task. Is there an easy way to know th...

And I can't subscribe the forum topics.

That's right. But since I'm extending (not branching) the base framework, I'll want to follow minor changes rather than to keep a snapshot at some point. In the given example (the format changed from GIF to PNG), I would rather like to notice the broken icon links immediately than be with GIF (possi...

Yes, icons. More specifically, trying a kind of *[class~='topic/note']::before(2) { content: oxy_url("${baseFramework}/", "img/note.png"); }.
Since I'm extending the base framework, it would be more natural to look up the base files than to duplicate them.

The ability to extend the base document type is an awesome feature. In an Author CSS of the extension framework, I would like to refer to a file in its base framework. However, oxy_url( "${baseFramework}/", "something" ) does not resolve the variable. Is it a syntax error? Or the...

Interesting approach. After adding a few more jdbf:setFeature() to disable loading DTD, it worked. Thanks for sharing it.
The catch is that the document at base-uri() must be in sync with the in-memory one.

An ingenious function. I like it.
Unfortunately enabling XSLT3 in the skeleton and switching from DTD to XSD would be overkill for me at the moment...

It worked. Ideally I'd prefer something global like Saxon -expand option. But hardcoding to remove @class will do in my current use case. Thank you for the practical workaround.

Validate this DITA topic body on oXygen: <body> <section> <title>test</title> <title><b>test</b></title> </section> </body> [oxygen]\frameworks\dita\resources\dita-1.2-for-xslt2-other.sch will report the warning "section should only contain one title element" and propose the quick fix to &...

I tried the suggested way and it worked with the HTTP Client 0.10.0.

Unfortunately 0.11.0 didn't work straightaway.
On 0.11.0, <xsl:sequence select="java:send-request($request)"/> generates a string "org.expath.httpclient.saxon.SaxonResult@[32bit hex]".

Yes. In fact I sometimes wish I could rename/move the topic files in the Project view just like renaming XSLT files with the "Update references of the renamed resource" feature.

[DITA Maps] - [Rename/Move resource] command is quite handy.
Could it be possible to perform the same operation on image files linked from image/@href?