Editor variables - current archive file
Are you missing a feature? Request its implementation here.
Editor variables - current archive file
Hi folks.
Lovely work 12.2. Currently trying to get at least some of my publishing customers to buy copies for their EPUB QA teams.
Anyways... I may have failed to notice a way to do this but is there a way to retrieve the current archive (preferably as a URL) as an editor variable. It would be very useful to be able to pass it to XProc scenarios.
cheers
nic
Lovely work 12.2. Currently trying to get at least some of my publishing customers to buy copies for their EPUB QA teams.
Anyways... I may have failed to notice a way to do this but is there a way to retrieve the current archive (preferably as a URL) as an editor variable. It would be very useful to be able to pass it to XProc scenarios.
cheers
nic
Director, Corbas Consulting
XML and eBook consultancy and training
XML and eBook consultancy and training
Re: Editor variables - current archive file
Hello,
Unfortunately there is no editor variable that would retrieve the name or path of the current archive from the Archive Browser view.
We did have a previous request for something similar, I'll add your vote for this request on our issue tracking tool.
If I may ask, how do yo intend to use the provided URL? What are you trying to do with it in the XProc scenario?
Regards,
Adrian
Unfortunately there is no editor variable that would retrieve the name or path of the current archive from the Archive Browser view.
We did have a previous request for something similar, I'll add your vote for this request on our issue tracking tool.
If I may ask, how do yo intend to use the provided URL? What are you trying to do with it in the XProc scenario?
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
Re: Editor variables - current archive file
Hi Adrian
What we are running a series of QA scripts across EPUBs, mostly schematrons, wrapped in a single XProc to produce a report for clients. Rather like epubcheck but based on customer requirements rather the epub specification itselft.
Also (see the post I made elsewhere just now), we have an NCX renumbering script that we apply via XProc.
nic
What we are running a series of QA scripts across EPUBs, mostly schematrons, wrapped in a single XProc to produce a report for clients. Rather like epubcheck but based on customer requirements rather the epub specification itselft.
Also (see the post I made elsewhere just now), we have an NCX renumbering script that we apply via XProc.
nic
Director, Corbas Consulting
XML and eBook consultancy and training
XML and eBook consultancy and training
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