Search found 13 matches

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: 977

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! :-)
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: 977

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: 977

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: 977

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/> </p:input> <p:xslt name="xsl-fo-test"> <p:input port="source"> <p:docume...
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: 977

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: 874

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: 874

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 fine. Does t...
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: 1736

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.oxygenxml.com/do...
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: 1736

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-document> in my stylesheet...
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: 1736

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 assume the latter had been overriding the...
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: 1736

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: 5
Views: 1293

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: 5
Views: 1293

${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...