Search found 96 matches
- by HomeGoods
- Sun May 22, 2016 4:51 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: DITA Glass: @href is expanded inadvertently
- Replies: 3
- Views: 2267
DITA Glass: @href is expanded inadvertently
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...
- by HomeGoods
- Thu May 05, 2016 7:29 pm
- Forum: Feature Request
- Topic: Editor variables support in CSS for author mode
- Replies: 9
- Views: 5601
Re: Editor variables support in CSS for author mode
Oops. Found it documented.
- by HomeGoods
- Thu May 05, 2016 7:08 pm
- Forum: Feature Request
- Topic: Editor variables support in CSS for author mode
- Replies: 9
- Views: 5601
Re: Editor variables support in CSS for author mode
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.
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.
- by HomeGoods
- Thu May 05, 2016 1:53 am
- Forum: Feature Request
- Topic: Schematron <extends> not supported by Master Files?
- Replies: 1
- Views: 2102
Schematron <extends> not supported by Master Files?
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...
- by HomeGoods
- Fri Feb 12, 2016 9:07 pm
- Forum: Feature Request
- Topic: Diff Files and Dirs: Add Ignore set of nodes defined by the XPath for XML documents
- Replies: 11
- Views: 7733
Re: Diff Files and Dirs: Add Ignore set of nodes defined by the XPath for XML documents
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.
Currently I use Araxis Merge for it. But its expression filter is regexp-based; a bit fragile and not so much helpful.
- by HomeGoods
- Sun Jan 24, 2016 6:03 am
- Forum: SDK-API, Frameworks - Document Types
- Topic: ${baseFramework} in CSS oxy_url()
- Replies: 6
- Views: 4425
Re: ${baseFramework} in CSS oxy_url()
Confirmed on 17.1 build 2015121117. Thanks for hearing us.
- by HomeGoods
- Fri Oct 30, 2015 2:07 pm
- Forum: Common Problems
- Topic: XSpec & catalogs
- Replies: 4
- Views: 2707
Re: XSpec & catalogs
Uh, nope. I meant the second stage ("[java] ...").HomeGoods wrote:I think it is working at the first stage ("[xslt] Processing ....xspec to ....xsl") .
- by HomeGoods
- Fri Oct 30, 2015 1:59 pm
- Forum: Common Problems
- Topic: XSpec & catalogs
- Replies: 4
- Views: 2707
Re: XSpec & catalogs
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 .....
- by HomeGoods
- Thu Oct 15, 2015 8:55 am
- Forum: Feature Request
- Topic: Please make accepting revision marks easier!
- Replies: 2
- Views: 2512
Re: Please make accepting revision marks easier!
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.
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.
- by HomeGoods
- Thu Oct 08, 2015 1:39 pm
- Forum: Common Problems
- Topic: Why treating U+3000 as whitespace by default?
- Replies: 4
- Views: 2110
Re: Why treating U+3000 as whitespace by default?
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.
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.
- by HomeGoods
- Thu Oct 08, 2015 1:07 pm
- Forum: Common Problems
- Topic: Why treating U+3000 as whitespace by default?
- Replies: 4
- Views: 2110
Re: Why treating U+3000 as whitespace by default?
And the consequence is...?
- by HomeGoods
- Fri Sep 11, 2015 7:38 pm
- Forum: Common Problems
- Topic: Sequence of transformations
- Replies: 5
- Views: 3390
Re: Sequence of transformations
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 HomeGoods
- Sat Aug 22, 2015 8:32 am
- Forum: Common Problems
- Topic: Why treating U+3000 as whitespace by default?
- Replies: 4
- Views: 2110
Why treating U+3000 as whitespace by default?
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.
- by HomeGoods
- Fri Aug 07, 2015 4:10 pm
- Forum: Common Problems
- Topic: Webhelp compatibility problem with Internet Explorer 11?
- Replies: 5
- Views: 3495
Re: Webhelp compatibility problem with Internet Explorer 11?
Yes, so IE shouldn't fall into compatibility view with build 2015071312 or later.
- by HomeGoods
- Wed Aug 05, 2015 4:53 am
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Refreshing WebHelp with Feedback deployment
- Replies: 8
- Views: 3903
Re: Refreshing WebHelp with Feedback deployment
Forgot to mention that also you should not copy the 'install' directory.
- by HomeGoods
- Wed Aug 05, 2015 4:49 am
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Refreshing WebHelp with Feedback deployment
- Replies: 8
- Views: 3903
Re: Refreshing WebHelp with Feedback deployment
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...
- by HomeGoods
- Tue Aug 04, 2015 8:08 pm
- Forum: Common Problems
- Topic: Webhelp compatibility problem with Internet Explorer 11?
- Replies: 5
- Views: 3495
Re: Webhelp compatibility problem with Internet Explorer 11?
I guess this X-UA-Compatible position fix (build 2015071312) would prevent IE from compatibility view: http://www.oxygenxml.com/forum/post34166.html
- by HomeGoods
- Tue Jul 28, 2015 5:28 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: DITA Maps Manager: Collection type GUI representation?
- Replies: 2
- Views: 1713
Re: DITA Maps Manager: Collection type GUI representation?
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.
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.
- by HomeGoods
- Tue Jul 28, 2015 12:55 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: DITA Maps Manager: Collection type GUI representation?
- Replies: 2
- Views: 1713
DITA Maps Manager: Collection type GUI representation?
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...
- by HomeGoods
- Tue Jul 21, 2015 5:44 pm
- Forum: Other Issues
- Topic: Bookmarks broken after oXygen website relaunch
- Replies: 2
- Views: 1787
Re: Bookmarks broken after oXygen website relaunch
And I can't subscribe the forum topics.
- by HomeGoods
- Thu Jul 09, 2015 12:22 pm
- Forum: SDK-API, Frameworks - Document Types
- Topic: ${baseFramework} in CSS oxy_url()
- Replies: 6
- Views: 4425
Re: ${baseFramework} in CSS oxy_url()
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...
- by HomeGoods
- Wed Jul 08, 2015 12:30 pm
- Forum: SDK-API, Frameworks - Document Types
- Topic: ${baseFramework} in CSS oxy_url()
- Replies: 6
- Views: 4425
Re: ${baseFramework} in CSS oxy_url()
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.
Since I'm extending the base framework, it would be more natural to look up the base files than to duplicate them.
- by HomeGoods
- Tue Jul 07, 2015 11:41 pm
- Forum: SDK-API, Frameworks - Document Types
- Topic: ${baseFramework} in CSS oxy_url()
- Replies: 6
- Views: 4425
${baseFramework} in CSS oxy_url()
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...
- by HomeGoods
- Fri Jul 03, 2015 3:16 pm
- Forum: XML Schemas
- Topic: Default attribute manifestation in Schematron Quick Fixes
- Replies: 7
- Views: 5602
Re: Default attribute manifestation in Schematron Quick Fixe
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.
The catch is that the document at base-uri() must be in sync with the in-memory one.
- by HomeGoods
- Wed Jul 01, 2015 11:24 pm
- Forum: XML Schemas
- Topic: Default attribute manifestation in Schematron Quick Fixes
- Replies: 7
- Views: 5602
Re: Default attribute manifestation in Schematron Quick Fixe
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...
Unfortunately enabling XSLT3 in the skeleton and switching from DTD to XSD would be overkill for me at the moment...
- by HomeGoods
- Mon Jun 29, 2015 4:54 pm
- Forum: XML Schemas
- Topic: Default attribute manifestation in Schematron Quick Fixes
- Replies: 7
- Views: 5602
Re: Default attribute manifestation in Schematron Quick Fixe
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.
- by HomeGoods
- Sat Jun 27, 2015 1:49 am
- Forum: XML Schemas
- Topic: Default attribute manifestation in Schematron Quick Fixes
- Replies: 7
- Views: 5602
Default attribute manifestation in Schematron Quick Fixes
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 &...
- by HomeGoods
- Fri Jun 19, 2015 11:38 pm
- Forum: XSLT and FOP
- Topic: HTTP - Client
- Replies: 3
- Views: 3381
Re: HTTP - Client
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]".
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]".
- by HomeGoods
- Wed May 27, 2015 10:03 pm
- Forum: Feature Request
- Topic: DITA: Rename/move non-topic files
- Replies: 6
- Views: 4773
Re: DITA: Rename/move non-topic files
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.
- by HomeGoods
- Tue May 26, 2015 11:42 pm
- Forum: Feature Request
- Topic: DITA: Rename/move non-topic files
- Replies: 6
- Views: 4773
DITA: Rename/move non-topic files
[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?
Could it be possible to perform the same operation on image files linked from image/@href?
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service