You are right. I must have disabled it :-[ After enabling it, the images showed up just fine. I feel bad for taking up so many resources to solve such a simple problem. Does SyncRO Soft/oXygen have a donation link? On 8/23/06, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello Chris,
I think I finally figured out what you did wrong. Your movie does not show it but the only change in my configuration which duplicates your error (the XInclude is resolved but the base URI is not correct in the included fragment) is to enable XInclude processing in Preferences *but disable Base URI fix-up*. Can you check please that Base URI fix-up is also enabled in Options -> Preferences -> XML / XML Parser ? I do not really understand why you would want to disable it. When you enable XInclude the two related options are also enabled by default (Base URI fix-up and Language fix-up) so I think you disabled Base URI fix-up manually by unchecking the checkbox.
Best regards, Sorin
Chris Chiasson wrote:
I wish I could solve this problem :-[
At least the parameter detection routine in oXygen now shows the paramter value I've set, though I don't know why that changed.
The TestHarness.html and TestHarness.xhtml were made by executing the TestHarness HTML and XHTML transforms in oXygen.
I made a 7 MiB video of me using a tool to generate the XML, verifying the oXygen transformation, executing the transform, viewing the output (which didn't respect xml:base), exporting the project to a temp folder on my website, executing the same transform with xsltproc, and comparing both outputs. I can get xsltproc to work, but not oXygen :-(
I am hoping you will watch the video and be able to catch whatever I might have messed up.
http://chris.chiasson.name/temp/C38951408874-transcoded.avi
http://chris.chiasson.name/temp/Engineering_Optimization_Documentation.zip
http://chris.chiasson.name/temp/Engineering_Optimization_Documentation/
Thanks,
On 8/22/06, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello Chris,
The XSLT parameters and their default values are extracted from the stylesheet specified in the scenario in the XSL URL field. If that stylesheet specifies other value than the default value 1 set by the original DocBook stylesheet then that other value is listed in the Parameters dialog as default value. Default value means generally the value of the parameter if you do not set other value explicitly in the Parameters dialog, not the default set by the original DocBook stylesheet.
I downloaded
http://chris.chiasson.name/temp/Engineering_Optimization_Documentation.zip
and I applied your scenarios "TestHarness DocBook HTML" and "TestHarness DocBook XHTML" to TestHarness.xml with oXygen 7.2. I obtained a .html file and a .xhtml file which point to the low DPI images (html role) with correct paths (C:/path/to/Engineering_Optimization_Documentation/mote/*.png). That means the PNG images located in the Engineering_Optimization_Documentation\mout folder are displayed just fine. This happened in both oXygen standalone and in Eclipse. I see that in your files TestHarness.html and TestHarness.xhtml the paths do not contain the mout folder name. How did you generate these files ?
Best regards, Sorin
Chris Chiasson wrote:
After further reading of the help, it seems that the parameters and default listed in oXygen's transformation dialog are programatically extracted from the referenced xsl stylesheet. I notice that it always lists keep.relative.image.uris as 1, despite what my customization layer says in common.xsl.
The transformation still results in broken image uris.
oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user