Search found 19 matches
Search found 19 matches
• Page 1 of 1
- by Martin de la Iglesia
- Wed Jul 05, 2023 11:11 am
- Forum: Common Problems
- Topic: Error "Could not insert document fragment" in Oxygen 25
- Replies: 8
- Views: 839
Re: Error "Could not insert document fragment" in Oxygen 25
Thank you, Radu. I can confirm that it works now once I set the parameter to 'false'.
- by Martin de la Iglesia
- Wed May 31, 2023 11:24 am
- Forum: Common Problems
- Topic: Error "Could not insert document fragment" in Oxygen 25
- Replies: 8
- Views: 839
Re: Error "Could not insert document fragment" in Oxygen 25
OK, thank you, Radu. I'm looking forward to that release then.
- by Martin de la Iglesia
- Tue May 30, 2023 6:58 pm
- Forum: Common Problems
- Topic: Error "Could not insert document fragment" in Oxygen 25
- Replies: 8
- Views: 839
Re: Error "Could not insert document fragment" in Oxygen 25
Of course, double-encoding the ampersands or otherwise altering the source XML document is not a feasible solution to this problem.
- by Martin de la Iglesia
- Tue May 30, 2023 2:25 pm
- Forum: Common Problems
- Topic: Error "Could not insert document fragment" in Oxygen 25
- Replies: 8
- Views: 839
Re: Error "Could not insert document fragment" in Oxygen 25
Yes, &cetera would produce the desired result and throws no error.
- by Martin de la Iglesia
- Tue May 30, 2023 2:01 pm
- Forum: Common Problems
- Topic: Error "Could not insert document fragment" in Oxygen 25
- Replies: 8
- Views: 839
Error "Could not insert document fragment" in Oxygen 25
I have configured an Author action that inserts content from another XML file using a XSLTOperation and the Replace action. This works fine up to including Oxygen Editor version 24. In v. 25 however, when this action is executed, I get the error message "Could not insert document fragment. Caus...
- by Martin de la Iglesia
- Mon Jun 22, 2020 2:00 pm
- Forum: Feature Request
- Topic: Author mode: cut (and paste) XML
- Replies: 14
- Views: 10628
Re: Author mode: cut (and paste) XML
Has this feature been implemented as a standard operation yet? I am aware that this thread is quite old, but I am looking for a copy/cut/paste XML operation in Author mode and haven't found one.
- by Martin de la Iglesia
- Mon Oct 21, 2019 4:08 pm
- Forum: XSLT and FOP
- Topic: font-family not working when running XSL-FO via XProc
- Replies: 10
- Views: 6190
Re: font-family not working when running XSL-FO via XProc
Thank you, Radu, I had indeed downloaded the wrong version at first.
Now that I have the correct version installed, I can confirm that Calabash now finds the .xconf file, and my PDFs are finally rendered in the font that I wanted!
Now that I have the correct version installed, I can confirm that Calabash now finds the .xconf file, and my PDFs are finally rendered in the font that I wanted!
- by Martin de la Iglesia
- Mon Oct 21, 2019 2:53 pm
- Forum: XSLT and FOP
- Topic: font-family not working when running XSL-FO via XProc
- Replies: 10
- Views: 6190
Re: font-family not working when running XSL-FO via XProc
I just installed Oxygen 21.1, but I get essentially the same error message there:
Add-on for Calabash XProc Engine requires a Java Virtual Machine (JVM) version that is greater than or equal to 1.7.
Currently, oXygen is using JVM: 1.8.0_202.
- by Martin de la Iglesia
- Mon Oct 21, 2019 12:55 pm
- Forum: XSLT and FOP
- Topic: font-family not working when running XSL-FO via XProc
- Replies: 10
- Views: 6190
Re: font-family not working when running XSL-FO via XProc
Thank you, Norman and Radu. I'm not sure if this is what you meant, Radu, but I just downloaded the new xmlcalabash1-print-1.2.0.jar from https://github.com/ndw/xmlcalabash1-print/releases to replace the old xmlcalabash1-print-1.1.5.jar in the C:\Program Files\Oxygen XML Editor 20\lib\xproc\calabash...
- by Martin de la Iglesia
- Mon Jun 17, 2019 3:24 pm
- Forum: XSLT and FOP
- Topic: font-family not working when running XSL-FO via XProc
- Replies: 10
- Views: 6190
Re: font-family not working when running XSL-FO via XProc
Hi Radu, here's an XProc: <?xml version="1.0" encoding="UTF-8"?> <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" xmlns:c="http://www.w3.org/ns/xproc-step" version="1.0" name="myPipeline"> <p:input port="source"> <p:empty/> </...
- by Martin de la Iglesia
- Thu Jun 06, 2019 5:46 pm
- Forum: XSLT and FOP
- Topic: font-family not working when running XSL-FO via XProc
- Replies: 10
- Views: 6190
font-family not working when running XSL-FO via XProc
Hi, I have written an FO stylesheet to transform XML to PDF, which works fine when I execute it as an XSLT Transformation Scenario. Now I'd like to integrate this stylesheet into my XProc pipeline. However, when I invoke the exact same FO stylesheet via an XProc Transformation Scenario, the resultin...
- by Martin de la Iglesia
- Thu Nov 15, 2018 2:51 pm
- Forum: Common Problems
- Topic: Calabash XProc is not available anymore
- Replies: 3
- Views: 2231
Re: Calabash XProc is not available anymore
Thank you, Radu and Adrian, I can confirm that I works for me now that I have changed the processor setting in all my transformation scenarios. Of course, it is unfortunate that these scenarios now throw an error when applied in version 17.1 (or 19). This is problematic because my transformation sce...
- by Martin de la Iglesia
- Tue Nov 06, 2018 5:06 pm
- Forum: Common Problems
- Topic: Calabash XProc is not available anymore
- Replies: 3
- Views: 2231
Calabash XProc is not available anymore
Hi, I recently upgraded from Oxygen 17.1 to 20.1. When I want to apply a transformation scenario that includes XProc, I get the error message, "The transformer Calabash XProc is not available anymore. Please reconfigure the transformation scenario." In 17.1 the same scenario still works fi...
- by Martin de la Iglesia
- Thu Sep 07, 2017 12:53 pm
- Forum: Feature Request
- Topic: make XSLT overriding output specs in transformation scenario optional
- Replies: 7
- Views: 3857
Re: make XSLT overriding output specs in transformation scenario optional
I had specified it, and at first it didn't work. However, I just closed and re-opened oXygen, and now it works. So, thank you for the hint, Adrian. Still, I wish there was a short note, either displayed directly in the "Edit scenario" window or at least in the Help text (https://www.oxygen...
- by Martin de la Iglesia
- Thu Sep 07, 2017 12:28 pm
- Forum: Feature Request
- Topic: make XSLT overriding output specs in transformation scenario optional
- Replies: 7
- Views: 3857
Re: make XSLT overriding output specs in transformation scenario optional
If you want to open the output of a single xsl:result-document, you need to specify "Open in Browser/System Application" with "Other location" and specify there the location where the xsl:result-document writes the file. This doesn't work for me: when I have a <xsl:result-docume...
- by Martin de la Iglesia
- Thu Sep 07, 2017 10:29 am
- Forum: Feature Request
- Topic: make XSLT overriding output specs in transformation scenario optional
- Replies: 7
- Views: 3857
Re: make XSLT overriding output specs in transformation scenario optional
In the "Edit scenario" window (in oXygen 17.1 on Windows), all settings in the "Output" tab, such as "Prompt for file" and "Open in Browser/System Application", were ignored. This only changed when I removed the <xsl:result-document> from my stylesheet, so I a...
- by Martin de la Iglesia
- Wed Sep 06, 2017 4:16 pm
- Forum: Feature Request
- Topic: make XSLT overriding output specs in transformation scenario optional
- Replies: 7
- Views: 3857
make XSLT overriding output specs in transformation scenario optional
When I created a custom transformation scenario, the HTML output didn't work at first, and it took me some time to figure out that the <xsl:result-document> in my XSLT stylesheet was overriding the settings I had set in the transformation scenario editing window. Therefore I'd like to suggest adding...
- by Martin de la Iglesia
- Wed Aug 23, 2017 10:41 am
- Forum: Other Issues
- Topic: ${caret} ends up at wrong position
- Replies: 6
- Views: 3623
Re: ${caret} ends up at wrong position
Thank you for looking into this, Sorin. I'm using v. 17.1 and now that I've checked, I can confirm that it is indeed as you say: when I stay in Author mode, the caret is at the correct position; only when I switch to Text mode, the caret 'jumps' 5 characters to the left. So this problem isn't as bad...
- by Martin de la Iglesia
- Tue Aug 22, 2017 6:02 pm
- Forum: Other Issues
- Topic: ${caret} ends up at wrong position
- Replies: 6
- Views: 3623
${caret} ends up at wrong position
Hi, I'm new to the Author mode so I'm probably missing something obvious, but: I've created an InsertFragmentOperation Action with the fragment <ab> <lb/>${caret} </ab> However, when I execute this Action, after the fragment is inserted, the cursor is now positioned before the <lb/> tag. How do I co...
Search found 19 matches
• Page 1 of 1
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